https://github.com/StarKissed/ek-gc100_recovery
This recovery was made using the EK-GC110 recovery.img ramdisk from the latest firmware release. The CWM Touch 6.0.3.2 is from a Samsung Galaxy SGS3 (Same board), modified with the custom kernel for the EK-GC (stripped version from this forum). The original recovery was used to provide the corrected init and fatal values, but all other aspects are relatively identical to the SGS3.
The recovery functions work, and appear fully functional. Keep in mind this is still in the testing phase. Work is being done to rebuild the necessary device configuration files based on information about the EK-GC and SGS3. The only aspect untested is the sdcard formatting options.
StarKissed Galaxy Cam Recoveries
This brings custom recovery to the Galaxy Camera, which is accessible by holding the zoom toggle to the right (red indicator should be on +) and pressing the power button. The difference between recovery and download mode is whether or not the shutter button is also held. Keeping the shutter button pressed will result in launching the Odin download mode.
It gets better
Any idea if it works on the EK-GC100 (3G and Wi-Fi version) ?
Sent from my GT-N7100 using Tapatalk 4 Beta
RavenY2K3 said:
It gets better
Any idea if it works on the EK-GC100 (3G and Wi-Fi version) ?
Sent from my GT-N7100 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Should work on all variants. The radio isn't called by recovery so I see no reason it wouldn't.
I was thinking more along the lines of the partition tables, I wasn't sure whether there were differences in that respect between devices and, whether it makes a difference even if there was.
Sent from my GT-N7100 using Tapatalk 4 Beta
RavenY2K3 said:
I was thinking more along the lines of the partition tables, I wasn't sure whether there were differences in that respect between devices and, whether it makes a difference even if there was.
Sent from my GT-N7100 using Tapatalk 4 Beta
Click to expand...
Click to collapse
If you have a root file browser, they are in /dev/block/platform/dw_mmc/by-name and the partition names should list where they link.
System is p9, boot p5, data p13, recovery p6
If they don't match, it would only be calling the by-name links instead of specific numbers. I avoided that for extra stability, but it would still work properly. I use the by-name for mounts and flashing in the zips already.
Hey I can't get this to flash.. stuck at NAND write when I use the gz and Odin says the MD5 is incorrect if I unpack first.
Any help?
GriffinSauce said:
Hey I can't get this to flash.. stuck at NAND write when I use the gz and Odin says the MD5 is incorrect if I unpack first.
Any help?
Click to expand...
Click to collapse
Download the tar version without the md5. Once the md5 is written to the file it can't be removed, but goo provides md5s to verify locally. I've tried md5 -r and that didnt work, but apparently neither did the homebrew md5sum
twistedumbrella said:
Download the tar version without the md5. Once the md5 is written to the file it can't be removed, but goo provides md5s to verify locally. I've tried md5 -r and that didnt work, but apparently neither did the homebrew md5sum
Click to expand...
Click to collapse
I see only .img and .gz files. Tried unzipping and removing the MD5 check, no dice.
Odin hangs at "NAND write" now.. Luckily no problems after resetting the device (no cwm though )
GriffinSauce said:
I see only .img and .gz files. Tried unzipping and removing the MD5 check, no dice.
Odin hangs at "NAND write" now.. Luckily no problems after resetting the device (no cwm though )
Click to expand...
Click to collapse
That's what I get for trusting my script. It missed copying the basic tar to the folder to upload. It should be uploaded shortly. That one should solve it.
twistedumbrella said:
That's what I get for trusting my script. It missed copying the basic tar to the folder to upload. It should be uploaded shortly. That one should solve it.
Click to expand...
Click to collapse
Argh, that didn't work either so I took a good hard look and I see I have an EK-GC100 ...
Sorry for wasting your time so far.
Do you think it is possible to make it compatible? Can I supply my stock recovery for that?
GriffinSauce said:
Argh, that didn't work either so I took a good hard look and I see I have an EK-GC100 ...
Sorry for wasting your time so far.
Do you think it is possible to make it compatible? Can I supply my stock recovery for that?
Click to expand...
Click to collapse
It should have been already but with the stock one I can make sure it will be
Sent from my PG86100 using Tapatalk 4
twistedumbrella said:
It should have been already but with the stock one I can make sure it will be
Sent from my PG86100 using Tapatalk 4
Click to expand...
Click to collapse
https://www.dropbox.com/s/osyk8p05kjcicjg/recovery.img
This is the stock recovery of my device. Thanks for taking the trouble!
GriffinSauce said:
https://www.dropbox.com/s/osyk8p05kjcicjg/recovery.img
This is the stock recovery of my device. Thanks for taking the trouble!
Click to expand...
Click to collapse
I didn't forget about you. Tomorrow I should be able to get something together that will work.
Alright, I took the stock recovery that was posted and used the kernel image and modules from that, tweaked the partition tables a little more, and hopefully it should now work. Samsung is weird. Some have an internal_sd and external_sd, some have sdcard and this extSDCard, some have sdcard and sdcard1. No wonder apps always have issues with trying to use the card.
twistedumbrella said:
Alright, I took the stock recovery that was posted and used the kernel image and modules from that, tweaked the partition tables a little more, and hopefully it should now work. Samsung is weird. Some have an internal_sd and external_sd, some have sdcard and this extSDCard, some have sdcard and sdcard1. No wonder apps always have issues with trying to use the card.
Click to expand...
Click to collapse
Thanks again!
Still no go. I tried recovery.08-13-2013_08.42.tar and recovery.08-13-2013_08.42.tar.md5. Still halting at "NAND Write Start!"
Tried with Odin v3.07 and 1.3. Also did flash a stock rom via Odin the other day, so it should work..
Could there be some write protection on the recovery?
GriffinSauce said:
Thanks again!
Still no go. I tried recovery.08-13-2013_08.42.tar and recovery.08-13-2013_08.42.tar.md5. Still halting at "NAND Write Start!"
Tried with Odin v3.07 and 1.3. Also did flash a stock rom via Odin the other day, so it should work..
Could there be some write protection on the recovery?
Click to expand...
Click to collapse
There shouldn't be. I don't use Odin, though. I have a Mac, so I have a compiled version of the Heimdall or whatever that one is. The original flash was done with Odin, though. I wonder if its a lock from the service provider. Let me see if I can somehow get a proper md5 attached. That may help.
Ah but I can try Heimdall too. I'll try tonight.
Sent from my HTC One X using Tapatalk 4
GriffinSauce said:
Ah but I can try Heimdall too. I'll try tonight.
Sent from my HTC One X using Tapatalk 4
Click to expand...
Click to collapse
Alright. At least then I can try to zero in on the issue.
Sent from my Galaxy Nexus using Tapatalk 2
I fixed the problem.
Just unzip and flash this through Odin.
Reboot with power + zoom+
You're in CWM recovery, enjoy!
Delux9364 said:
I fixed the problem.
Just unzip and flash this through Odin.
Reboot with power + zoom+
You're in CWM recovery, enjoy!
Click to expand...
Click to collapse
What problem? What model? What was done? If it's anything more than signing with the right md5, you may want to submit a pull request.
Related
Intro
garyd9 originally ported ClockworkMod Recovery 5.0.0.x to the Tab 7 Plus (all variants) in late 2011. Gary's since moved on to bigger and better things, and so has ClockworkMod Recovery. As of ClockworkMod Recovery version 6.0.0.x backups and restores should be faster, take up less space (due to file-level deduplication), and there's a swanky new look (though a bit iOS-y).
wtf is "recovery" anyways?
Recovery mode is a minimal, alternative mode of booting which allows you to install software from zip files, backup/restore your device, and perform low-level operations like factory reset and formatting partitions. All Android devices have a recovery mode (it's part of the stock AOSP environment), but the default recovery mode is very limited. For example, it only allows you to flash zips which have been signed by the vendor's private key.
ClockworkMod Recovery was developed by Koushik Dutta (@koush), and is much more flexible... If you want to flash CyanogenMod, you MUST have a non-stock recovery. Right now that means ClockworkMod Recovery.
Download
P6200/P6201/P6200L
Heimdall-flashable image (6.0.2.7): goo.im (md5: 987b65a8213bffad46706a81ec31c073)
P6210/P6211/P6210L
Heimdall-flashable image (6.0.2.7): goo.im (md5: 6ac089744adaf09d3357e2738359799a)
T869
Heimdall-flashable image (6.0.2.7): goo.im (md5: 937de860e74623ddcafb33e1b0361812)
Flashing with Heimdall
I recommend flashing with Heimdall; it's open source and cross platform, whereas Odin is a leaked internal tool from Samsung, and only works on Windows. I absolutely cannot give guidance on using Odin. As of this time I recommend using Heimdall 1.3.1 (1.3.2 has a known bug which prevents flashing some files from completing successfully).
You can use the GUI (heimdall-frontend), or flash from the command line. In Linux it's easy:
Unplug your tablet from USB
Turn your tablet off
Hold Volume Down and press the power button, keep holding Volume Down for 5 seconds
Plug your tablet back into the computer
Type:
Code:
sudo heimdall flash --recovery p6200-clockworkmod-6.0.2.7.img
After that you should now have ClockworkMod Recovery installed.
Booting into CWM
There are a few ways to get into ClockworkMod Recovery:
Using adb, type: adb reboot recovery
From CyanogenMod's power menu: hold down the Power button for a few seconds, then navigate to Reboot -> Recovery.
With the tablet off, hold Volume Up and press power, keep holding Volume Up for 5 seconds
Disclaimer
I've tested backing up and restoring to CM9 and stock a few times, and it seems to work well. But please back up your stuff with other applications, like Go Backup or Titanium Backup just in case something goes wrong with restoring.
Mine!
Using Mobile Odin simply place the .tar.md5 in the recovery field and flash away!
Edit: There's something wrong with the .tar.md5 you posted for Odin for the 6210. I got an error about partitions when I tried to load it in Mobile Odin. I downloaded the .img file instead and went ahead and created a .tar.md5 from it. I was able to load the new .tar.md5 I created into Mobile Odin to flash the updated CWM. Thanks for this! Here's the mediafire download for the new .tar.md5 I used to flash:
Anyone has tried for mobile odin? Is it successfuly installed?
Any cwm flashable?
Thanks anyway
Nice work my bros.....
Sent from my GT-P6200 using xda premium
arfian said:
Anyone has tried for mobile odin? Is it successfuly installed?
Any cwm flashable?
Thanks anyway
Nice work my bros.....
Sent from my GT-P6200 using xda premium
Click to expand...
Click to collapse
I flashed it with Mobile Odin using the .tar.md5 I linked above.
Vivified said:
I flashed it with Mobile Odin using the .tar.md5 I linked above.
Click to expand...
Click to collapse
Is it compatible for me?
As i use p6200
Sent from my GT-P6200 using xda premium
where is recovery field?
---------- Post added at 05:37 AM ---------- Previous post was at 05:10 AM ----------
Vivified said:
I flashed it with Mobile Odin using the .tar.md5 I linked above.
Click to expand...
Click to collapse
hi i used your new file, but upon starting in odin it failed. i put it on phone box, is it the way it's supposed to be installed?
---------- Post added at 05:41 AM ---------- Previous post was at 05:37 AM ----------
oops you should put it in bootloader box
---------- Post added at 05:52 AM ---------- Previous post was at 05:41 AM ----------
cant mount sd card, vant install hot fix for wifi
Flashed mine 6210 with heimdall a few minutes ago and everything is working as expected.
*Just tried to mount the SD card, and it is failing
MrNo said:
Flashed mine 6210 with heimdall a few minutes ago and everything is working as expected.
*Just tried to mount the SD card, and it is failing
Click to expand...
Click to collapse
What do you mean "mount the SD card?" I have flashed a zip from both the internal storage as well as the removable sdcard...
maybe because im flashing from cm9. im reverting back to stock HC and see
Thanks again AORTH!
have you contacted The guys at Clcokwork to get this in the app, hopefull save a lot of people using the CWM recovery installer app, even though its a stickied thread warning.
thank you!
Just tried to flash with Mobile Odin and it says "Partition could not be found in file".
still no luck,
cant open location of sd card or internal memory.
ill try reverting back and installing the old clockworkmod via default recovery
I cannot mount the SD card on the computer from the recovery.
Perhaps it doesn't work that way from clockworkmod recovery, but if i remember correctly my nexus one and kindle allow that.
Flashed with Mobile Odin Pro.
Recovery works.
Will this work with ICS update?
Dushaine said:
Just tried to flash with Mobile Odin and it says "Partition could not be found in file".
Click to expand...
Click to collapse
The same to me. Hic hic.......
Can not flash!
Sent from my GT-P6200 using Tapatalk 2
i've tried to flash it with odin3 v.1.85 and failed. here's the log :
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> p6200-clockworkmod-6.0.0.8.tar.md5 is invalid.
<OSM> End...
Click to expand...
Click to collapse
Awesome - working CWM.
Too bade the names are changed - internal sd is external
k_t_b said:
Flashed with Mobile Odin Pro.
Recovery works.
Click to expand...
Click to collapse
Cool. P6210?
MrNo said:
I cannot mount the SD card on the computer from the recovery.
Perhaps it doesn't work that way from clockworkmod recovery, but if i remember correctly my nexus one and kindle allow that.
Click to expand...
Click to collapse
That never worked on our device. The internal storage cannot be USB mounted, and I've never seen an option to mount the removable one on the P6200/P6210. Can you clarify a bit?
derekbro said:
Will this work with ICS update?
Click to expand...
Click to collapse
Yes. I posted in the first page that I have tested backing up and restoring to/from the stock ICS release.
motosuki said:
i've tried to flash it with odin3 v.1.85 and failed. here's the log :
Click to expand...
Click to collapse
Ok, it's possible I made the file incorrectly. Like I posted in the first post, I do not use Odin, and never have. The only support I can offer is trying to create a new one and hoping that works. I suggest you try Heimdall in the mean time.
chrisrotolo said:
Thanks again AORTH!
have you contacted The guys at Clcokwork to get this in the app, hopefull save a lot of people using the CWM recovery installer app, even though its a stickied thread warning.
thank you!
Click to expand...
Click to collapse
I haven't contacted them. "They" don't have a "contact." It will happen eventually, I guess. Honestly I can't blame koush for being hard to reach, I bet n00bs bug him all day, every day with retarded questions.
I have a Galaxy Tab 2 VZW and was trying to install the ClearRom, but I guess I forgot to unlock bootloader, so now everytime I turn the tab on I get message statitng " System Software not authorized by Verizon Wireless has been found on your phone."
I have a backup from before I tried installing the ROM but don't know what to do with it
Any help will be appreciated
melog69 said:
I have a Galaxy Tab 2 VZW and was trying to install the ClearRom, but I guess I forgot to unlock bootloader, so now everytime I turn the tab on I get message statitng " System Software not authorized by Verizon Wireless has been found on your phone."
I have a backup from before I tried installing the ROM but don't know what to do with it
Any help will be appreciated
Click to expand...
Click to collapse
HOw did you make the backup? CWM? If so, then install CMW recovery and do a restore.
DigitalMD said:
HOw did you make the backup? CWM? If so, then install CMW recovery and do a restore.
Click to expand...
Click to collapse
I tried getting into recovery mode, but I get the following screen everytime, I think I need the Stock Firmware to flash with ODIN but I don't know where to find it.
<iframe src="https://skydrive.live.com/embed?cid=47A1A726F16BDCFD&resid=47A1A726F16BDCFD%212570&authkey=AE3MPZ8PewFeQos" width="180" height="320" frameborder="0" scrolling="no"></iframe>
Always, ALWAYS, follow directions exactly how they're laid out.
What you need to do is download the aboot.img to your sd card. Reboot into recovery, ADB Shell into your device (you may need linux for this part as Windows doesn't recognize the device in recovery mode). Once you ADB into recovery, make sure you are root (noted by # instead of $).
Then:
dd if=/sdcard/aboot.img of=/dev/block/mmcblk0p5
reboot download
This should unlock you bootloader so you can get by verizons pesky warning.
We can't see the picture you tried attaching.
MrHyde03 said:
Always, ALWAYS, follow directions exactly how they're laid out.
What you need to do is download the aboot.img to your sd card. Reboot into recovery, ADB Shell into your device (you may need linux for this part as Windows doesn't recognize the device in recovery mode). Once you ADB into recovery, make sure you are root (noted by # instead of $).
Then:
dd if=/sdcard/aboot.img of=/dev/block/mmcblk0p5
reboot download
This should unlock you bootloader so you can get by verizons pesky warning.
We can't see the picture you tried attaching.
Click to expand...
Click to collapse
I cannot get to recovery mode, only download mode, also ClearRom did not specify that the bootloader, that is why I did not even bother
melog69 said:
I cannot get to recovery mode, only download mode, also ClearRom did not specify that the bootloader, that is why I did not even bother
Click to expand...
Click to collapse
You'll more than likely have to send it back. There has been no official release of stock firmware, unfortunately (none that I have found at least). In the root thread there are steps 1 - 3 for a reason. 1 - Root, 2 - Unlock and Recovery, 3 - Custom ROM. Always follow directions.
MrHyde03 said:
You'll more than likely have to send it back. There has been no official release of stock firmware, unfortunately (none that I have found at least). In the root thread there are steps 1 - 3 for a reason. 1 - Root, 2 - Unlock and Recovery, 3 - Custom ROM. Always follow directions.
Click to expand...
Click to collapse
Well, thanks guys now I know what to do when it's fixed
melog69 said:
Well, thanks guys now I know what to do when it's fixed
Click to expand...
Click to collapse
Maybe try a stock 3100 rom? If the hardware is the same should work, just need to set APN etc.Then reroot, install recovery, install cuztom rom.
---------- Post added at 04:04 PM ---------- Previous post was at 03:54 PM ----------
acefsw said:
Maybe try a stock 3100 rom? If the hardware is the same should work, just need to set APN etc.Then reroot, install recovery, install cuztom rom.
Click to expand...
Click to collapse
Actually, according to here http://forum.xda-developers.com/showthread.php?t=1885558 you just need download mode to install the stock image and then follow the rest of the steps.
acefsw said:
Maybe try a stock 3100 rom? If the hardware is the same should work, just need to set APN etc.Then reroot, install recovery, install cuztom rom.
Click to expand...
Click to collapse
DO NOT INSTALL A P3100 ROM. It's not the same hardware (not really even close), so that would only make it worse.
imnuts said:
DO NOT INSTALL A P3100 ROM. It's not the same hardware (not really even close), so that would only make it worse.
Click to expand...
Click to collapse
I edited the post, read the link, it is for his device
imnuts is correct. These devices are extremely different and really does need it's own subforum so people don't keep getting confused. The i705 is closest to the i535 (s3), nearly identical actually.
MrHyde03 said:
imnuts is correct. These devices are extremely different and really does need it's own subforum so people don't keep getting confused. The i705 is closest to the i535 (s3), nearly identical actually.
Click to expand...
Click to collapse
Then wouldn't it be easier to flash an S Rom?
melog69 said:
Then wouldn't it be easier to flash an S Rom?
Click to expand...
Click to collapse
It still wouldn't work. boot, recovery, and system for the s3 are designed for the s3. The hardware is the same, but the software has it's differences. What differences, though, is beyond me.
I have the same issue, this is the first time I've ever "Bricked" a device. Thought I followed the instructions correctly, I can successfully flash recovery.tar.md5 on Mr.Hydes thread http://forum.xda-developers.com/showthread.php?t=1885558 but when it goes to reboot it gives me the Yellow ExclaTriangle "System software not authorized by Verizion , yadi, yadi ya da".
I can get into Download mode but NO RECOVERY, Tried flashing (With ODIN) CWM 6.0.1.9 located here http://forum.xda-developers.com/showthread.php?t=2044630 but ERROR with NAND WRITE FAIL.
Does anyone have a PIT file? I want give Heimdall a stab at it before I go throw it through Verizon's front window. Appreciate any help, like I said I understand the importance of following Instructions, I've done plenty of Android devices before including The Original GTab7, I dont mind cracking it open either, I've already had it apart to disconnect the battery but that did no help either, BTW it's really easy to open up.
Sounds like you didn't flash the unsecure bootloader
Sent from my SCH-I535 using XDA Premium HD app
MrHyde03 said:
Sounds like you didn't flash the unsecure bootloader
Sent from my SCH-I535 using XDA Premium HD app
Click to expand...
Click to collapse
I couldn't boot into Recovery to Flash, I'm Trying to flash now using Odin but get "Secure Check Fail". Any Ideas?
The bootloader needs to be flashed before the recovery using the dd command. Its listed first under step 2, before the recovery.
Sent from my SCH-I535 using XDA Premium HD app
MrHyde03 said:
The bootloader needs to be flashed before the recovery using the dd command. Its listed first under step 2, before the recovery.
Sent from my SCH-I535 using XDA Premium HD app
Click to expand...
Click to collapse
Yeah that's where I'm confused, I've had it rooted and unlocked since November following your original Development, I was on G3 not J1. Followed the Instructions and then crap.
Unlocked since Nov and it just now crapped? That doesn't make any sense.. When you boot into download mode right now, what orientation is the screen? Portrait or landscape? Landscape would mean a correctly flashed aboot.img (boot loader)
Sent from my SCH-I535 using XDA Premium HD app
iwSachin plain
MrHyde03 said:
Unlocked since Nov and it just now crapped? That doesn't make any sense.. When you boot into download mode right now, what orientation is the screen? Portrait or landscape? Landscape would mean a correctly flashed about.img (boot loader)
Sent from my SCH-I535 using XDA Premium HD app
Click to expand...
Click to collapse
I followed this thread of yours in the beginning of NOV. http://forum.xda-developers.com/showthread.php?t=1942674 I was rooted and unsecured bootloader, had CWM and SuperUser, but there weren't any ROMS out yet. Everything was fine until I went to install CleanRom the other day.
Portrait Orientation in Download mode.
https://mega.co.nz/#!K9x1USRJ!YnAw7R7_E8Ra0iCPAh4Siy1sNARO1AcoNko9Gxv5YqU
Need anything else - PM me. Original PIT is included. THIS IS NOT ODIN FLASHABLE, but the raw dump files. Includes modems (UEUAMFD).
[Edited for mirrors] Thanks @bmbm
For those who have a problem with downloading from MEGA, I made some mirrors:
http://xda.ftp.sh/i9505G_Full_Dump.rar
http://9505.eu/s4-google_edition/com..._Full_Dump.rar
crc checksums:
Code:
MD5
11865b66c248689bc2694c593ae361b7
SHA1
eb479b98bd4fc0a1f1777168f35f007bf2545e7d
sha256
f7c393e0e76998b54d4c615dd2dbb80db8ca8be0a190c00a590947faf0c79c28
Click to expand...
Click to collapse
donovanbrock said:
https://mega.co.nz/#!K9x1USRJ!YnAw7R7_E8Ra0iCPAh4Siy1sNARO1AcoNko9Gxv5YqU
Need anything else - PM me. Original PIT is included. THIS IS NOT ODIN FLASHABLE, but the raw dump files. Includes modems (UEUAMFD).
Click to expand...
Click to collapse
Any guide to flash the i9505 with this ?
MichelN said:
Any guide to flash the i9505 with this ?
Click to expand...
Click to collapse
That I have no idea. :|
MichelN said:
Any guide to flash the i9505 with this ?
Click to expand...
Click to collapse
It's not possible to flash the bootloader, modem and pit, but everything else should theoretically be directly flashable.
Theshawty said:
It's not possible to flash the bootloader, modem and pit, but everything else should theoretically be directly flashable.
Click to expand...
Click to collapse
theoretically yes. However, the mount points are different in the ROM. if you try and flash directly, you'll get stuck in a softbrick status. At least thats what happens on the 9505G when flashing a stock 9505 ROM.
Most likely gonna have to wait til someone can cook up a ROM based on this dump.
donovanbrock said:
theoretically yes. However, the mount points are different in the ROM. if you try and flash directly, you'll get stuck in a softbrick status. At least thats what happens on the 9505G when flashing a stock 9505 ROM.
Most likely gonna have to wait til someone can cook up a ROM based on this dump.
Click to expand...
Click to collapse
Someone should investigate why the bootloader, pit and modem cannot be flashed. The phones are identical.
donovanbrock said:
if you try and flash directly, you'll get stuck in a softbrick status.
Click to expand...
Click to collapse
Uh? It worked for @Aerys
how do we put these on our S4 I9505?
slikr said:
how do we put these on our S4 I9505?
Click to expand...
Click to collapse
Simply put: We can't.
Theshawty said:
Simply put: We can't.
Click to expand...
Click to collapse
Maybe Aerys can find that out, we have now the full dump.
Maybe write protection enable that we have in odin mode?
Sent from my HTC One using Tapatalk 4 Beta
Wonder what the chances are of flashing this (incluidng the modem) over to the tmobile m919 since its physically the same device as the i9505g.
So this may seem like a stupid question... but how would I be able to flash all of this back to my I9505G?
I did flash the other dumped files from before after I soft bricked mine but I still don't think it's back to 100% stock. I still think the recovery isn't correct (even though I tried flashing the other one). I guess my big question is, how do we go about making this a flashable Odin package?
I'm wondering if there's an issue with the PIT since the last thing I used that screwed something up was the "Quick Flasher" tool for the I9505 (to try to flash CWM recovery)... and I wonder if that screwed up my partitions.
mirror with checksums
For those who have a problem with downloading from MEGA, I made some mirrors:
http://xda.ftp.sh/i9505G_Full_Dump.rar
http://9505.eu/s4-google_edition/complete_dump_i9505G/i9505G_Full_Dump.rar
crc checksums:
Code:
MD5
11865b66c248689bc2694c593ae361b7
SHA1
eb479b98bd4fc0a1f1777168f35f007bf2545e7d
sha256
f7c393e0e76998b54d4c615dd2dbb80db8ca8be0a190c00a590947faf0c79c28
ack154 said:
So this may seem like a stupid question... but how would I be able to flash all of this back to my I9505G?
I did flash the other dumped files from before after I soft bricked mine but I still don't think it's back to 100% stock. I still think the recovery isn't correct (even though I tried flashing the other one). I guess my big question is, how do we go about making this a flashable Odin package?
I'm wondering if there's an issue with the PIT since the last thing I used that screwed something up was the "Quick Flasher" tool for the I9505 (to try to flash CWM recovery)... and I wonder if that screwed up my partitions.
Click to expand...
Click to collapse
So I'm quoting myself here, but I'm trying to figure out what went wrong originally...
Like I said, I used the Quick Flasher tool to attempt to flash CWM recovery, but it looks like that may have tried to flash it to the wrong partition. Looking at the QF utility, it tried to flash the Recovery to mmcblk0p21... but according to Donovan's other thread from the first system dump, p21 is apparently where the Boot partition is, not Recovery. So my partitions may still be screwed.
My head tells me that flashing this PIT with Odin and then flashing the System, Recovery, and Boot included here would get me back to normal. Thoughts??
ack154 said:
So I'm quoting myself here, but I'm trying to figure out what went wrong originally...
Like I said, I used the Quick Flasher tool to attempt to flash CWM recovery, but it looks like that may have tried to flash it to the wrong partition. Looking at the QF utility, it tried to flash the Recovery to mmcblk0p21... but according to Donovan's other thread from the first system dump, p21 is apparently where the Boot partition is, not Recovery. So my partitions may still be screwed.
My head tells me that flashing this PIT with Odin and then flashing the System, Recovery, and Boot included here would get me back to normal. Thoughts??
Click to expand...
Click to collapse
ack - weren't you able to restore with my other dump? if so, this will be no different. only addition to these files is the PIT and all the modems.
donovanbrock said:
ack - weren't you able to restore with my other dump? if so, this will be no different. only addition to these files is the PIT and all the modems.
Click to expand...
Click to collapse
I did... but my gut still tells me something's messed up (part of that is paranoia after soft bricking I think). The other part is that I still think my recovery is wrong. I'm pretty sure I booted into the stock recovery very early on to have a look and it didn't look like this (what mine is now)...
ack154 said:
I did... but my gut still tells me something's messed up (part of that is paranoia after soft bricking I think). The other part is that I still think my recovery is wrong. I'm pretty sure I booted into the stock recovery very early on to have a look and it didn't look like this (what mine is now)...
Click to expand...
Click to collapse
Thats the stock recovery. You're good to go brudda.
ack154 said:
I did... but my gut still tells me something's messed up (part of that is paranoia after soft bricking I think). The other part is that I still think my recovery is wrong. I'm pretty sure I booted into the stock recovery very early on to have a look and it didn't look like this (what mine is now)...
Click to expand...
Click to collapse
Your fine buddy :good:
donovanbrock said:
Thats the stock recovery. You're good to go brudda.
Click to expand...
Click to collapse
O Rly? That makes things a bit better then... thank you.
Still downloaded to save though...
Hello,
My One SV:
Android 4.2.2 Stock
Moonshine S-Off
HtcDev Unlocked
Custom recovery (TWRP 2.7)
Rooted
When my battery goes to 0% and the phone shuts down, when I plug the USB cable, the phone shows the battery charging sign and then starts in recovery mode, BUT the touchscreen doesn't work, the volume buttons don't work, only the power button works. I always have to wait a few minutes for it to charge up (showing in TWRP 3%+, otherwise it will not power on), remove the battery and the USB cable, put the battery in and power it on, then plug in the USB cable to continue charging.
I have to mention that this was happening also when it was:
Android 4.1.2 Saturn III something mod
S-On
HtcDev Unlocked
Custom recovery (clockworkmod)
Rooted
I've bought this phone second-hand, so I don't know how it behaved when was fully stock.
Thanks,
Sebastian.
The TWRP build you are using doesn't have the proper offmode charging binary. There is a TWRP version which has been built for your device that shall solve this problem for you but I unfortunately do not have the link since it is based on the international K2 variants and I am on a US version.
Another method would be to unpack the TWRP recovery, and unpack your stock 4.2.2 based recovery. Swap the kernel binary from stock recovery over to custom recovery. Then, decompress the ramdisk for both. Swap out the binaries inside the ramdisk as well.
Take note on what arguments you must use to rebuild your stock 4.2.2 based recovery because you must rebuild TWRP using those same arguments. If you do it correctly then this should also resolve your issue.
If you know how to build TWRP from source then I would update the source to reflect more so on 4.2.2. That would be the preferred method if necessary.
Modding.MyMind said:
The TWRP build you are using doesn't have the proper offmode charging binary. There is a TWRP version which has been built for your device that shall solve this problem for you but I unfortunately do not have the link since it is based on the international K2 variants and I am on a US version.
Another method would be to unpack the TWRP recovery, and unpack your stock 4.2.2 based recovery. Swap the kernel binary from stock recovery over to custom recovery. Then, decompress the ramdisk for both. Swap out the binaries inside the ramdisk as well.
Take note on what arguments you must use to rebuild your stock 4.2.2 based recovery because you must rebuild TWRP using those same arguments. If you do it correctly then this should also resolve your issue.
If you know how to build TWRP from source then I would update the source to reflect more so on 4.2.2. That would be the preferred method if necessary.
Click to expand...
Click to collapse
Well, mine is k2_u. Does that change anything?
fbpw131 said:
Well, mine is k2_u. Does that change anything?
Click to expand...
Click to collapse
Nope
Modding.MyMind said:
Nope
Click to expand...
Click to collapse
I've misunderstood, my bad.
Well, I've unpacked my TWRP image, it shows a lot of files, however, if I unpack my "recovery.img" stock recovery, it's "ramdisk" folder it's empty.
Bummer
fbpw131 said:
I've misunderstood, my bad.
Well, I've unpacked my TWRP image, it shows a lot of files, however, if I unpack my "recovery.img" stock recovery, it's "ramdisk" folder it's empty.
Bummer
Click to expand...
Click to collapse
So.. before I started installing ubuntu in dualboot with my windows, I checked old.splatterhand's posts, and as always, he posted the compiled version link in this post: http://forum.xda-developers.com/showthread.php?p=41456540#post41457062
Everything works nice now.
fbpw131 said:
So.. before I started installing ubuntu in dualboot with my windows, I checked old.splatterhand's posts, and as always, he posted the compiled version link in this post: http://forum.xda-developers.com/showthread.php?p=41456540#post41457062
Everything works nice now.
Click to expand...
Click to collapse
The version you have linked is for boost, not for k2u
old.splatterhand said:
The version you have linked is for boost, not for k2u
Click to expand...
Click to collapse
ooops, i guess that's why I lost all my data, it changed the partition somehow and it got wiped.
Yup, bad idea!
old.splatterhand said:
Yup, bad idea!
Click to expand...
Click to collapse
So I should flash the old recovery back, the one with the battery issue
At least that.
And pray that no important partition is wiped!
old.splatterhand said:
At least that.
And pray that no important partition is wiped!
Click to expand...
Click to collapse
Too late for praying, it's back on and seems fine. What should I check to make sure I'm ok?
The ones from here don't work: https://goo.im/devs/OpenRecovery/k2_u/
fbpw131 said:
The ones from here don't work: https://goo.im/devs/OpenRecovery/k2_u/
Click to expand...
Click to collapse
Use the twrp from 1. post of my thread you have linked.
And live with this bug, its only cosmetical. Or try to find someone who can fix it.
old.splatterhand said:
Use the twrp from 1. post of my thread you have linked.
And live with this bug, its only cosmetical. Or try to find someone who can fix it.
Click to expand...
Click to collapse
It's more than a visual bug. I need to pull out the battery for the phone to restart. I'll be living with it.
I've lost only some music and a bloons td 5 savegame but I could have lost much more. I have Sky/One Drive for my photos.
I'll wait and see if someone will ever build it. I should be able to compile it myself, but it's better if someone that really knows those config params do it. I'm done messing, this was as close to a brick as it can get. Lucky me!
fbpw131 said:
It's more than a visual bug. I need to pull out the battery for the phone to restart. I'll be living with it.
Click to expand...
Click to collapse
Don't put your phone off for charging. I never did and never noticed that bug
I'll wait and see if someone will ever build it. I should be able to compile it myself, but it's better if someone that really knows those config params do it. I'm done messing, this was as close to a brick as it can get. Lucky me!
Click to expand...
Click to collapse
I also think so, thats why i never messed with recoveries or kernels
old.splatterhand said:
Don't put your phone off for charging. I never did and never noticed that bug
Click to expand...
Click to collapse
It happens when my battery goes empty. This happens because of another bug.
Well, i don't know how often you use TWRP to flash things or make a backup. But a workaround could be, to use the stock recovery and only use TWRP when you need it.
So, where could find the stock recovery firmware?
Inside this firmware.zip - 33.62 MB
hi all, I've managed to brick my SM-P900.
Could someone point me to where I can get an Odin flashable rom please, with all the individual bits such as PDA / Phone / CSC.
I can't flash normal roms, it's not working with just the md5. Ideally stock, but happy with any rom as I can flash something else with TWRP.
I can't use any of the normal samsung sites as they're paid, and I'm broke =(
I would really appreciate it if you could help me fix this.
Many thanks
Google
SM-P900 - Samsung Firmware | Samsung Updated
---------- Post added at 03:14 AM ---------- Previous post was at 03:09 AM ----------
https://forum.xda-developers.com/galaxy-note-pro-12/general/firmware-firmware-t3038178
Where you able to solve your problem?
bmwdroid said:
Where you able to solve your problem?
Click to expand...
Click to collapse
x2 for me also
sp000n said:
x2 for me also
Click to expand...
Click to collapse
Sorry, don't understand.
Problems or just interested as well?
Nope, not solved, tried for ages, but ODIN doesn't flash it, just gets stuck on initialising.... I'm completely out of ideas!
Zophixan said:
Nope, not solved, tried for ages, but ODIN doesn't flash it, just gets stuck on initialising.... I'm completely out of ideas!
Click to expand...
Click to collapse
Did you get the multiple part ROM using samfirm_reborn tool?
bmwdroid said:
Did you get the multiple part ROM using samfirm_reborn tool?
Click to expand...
Click to collapse
Just tried downloading it and I get .tar.md5 file, not sure how i did it but from a previous attempt at fixing it, I have the same thing but in seperate files, with boot, cache, hidden, recovery s boot and system. Do i need to put them into odin? where do they go? I get stuck on initialising, tried pulling out cable and putting it back in, then it says it can't find a pit partition... tried flashing a pit file but still stuck on initiailising so pit doesn't flash.
@Zophixan the files you see, are in the opened archive.
Where did you get the file from?
You should have downloaded and decrypted 3 (P900) or 4-5(P905) separate files all ending md5 when using samfirm.
When there is only one you obviously have NOT the multiple part stock ROM.
Which Odin using?
bmwdroid said:
@Zophixan the files you see, are in the opened archive.
Where did you get the file from?
You should have downloaded and decrypted 3 (P900) or 4-5(P905) separate files all ending md5 when using samfirm.
When there is only one you obviously have NOT the multiple part stock ROM.
Which Odin using?
Click to expand...
Click to collapse
I've tried odin 3.07 and 1.85. I downloaded samfirm_reborn and upon use it downloaded just one file "SM-P900_1_20170222195126_gly008r5gf.zip" and inside it is the tar md5. Where can I get the separate items?
Even if I am not using the seperated one, shouldn't odin flash? It's always stuck on intiailising, I don't know if this matters but it says knox warranty 0500 on the download screen, and custom kernal / binary.
I remember having a similiar problem years ago on the same tablet but no idea how I fixed it, vaguely remember downloading seperate files to flash in each of the odin sections.
thanks.
EDIT, found the binary option nature option, will download now and try flashing each bit and report back...
bmwdroid said:
@Zophixan the files you see, are in the opened archive.
Where did you get the file from?
You should have downloaded and decrypted 3 (P900) or 4-5(P905) separate files all ending md5 when using samfirm.
When there is only one you obviously have NOT the multiple part stock ROM.
Which Odin using?
Click to expand...
Click to collapse
Still stuck on initializing, tried samsung drivers, even tried heimdall (and installed it's drivers), is there anything else I can try?
It says AP SWREV A1 and know warranty voide 0500, and current binary / system status as custom on the tablet.
Try a newer Odin.
I recommend at least 3.09.
What it says in DL mode is just information and no failure afaik.
bmwdroid said:
Try a newer Odin.
I recommend at least 3.09.
What it says in DL mode is just information and no failure afaik.
Click to expand...
Click to collapse
I tried both 3.10 and 3.09 but still stuck on initialisation... (do i need to do anything with CP or UMS field?),
does the current binary/ system status as custom ,or AP SWREV A1, or knox warranty mean anything?
Do you have any other suggestions, I can't think of anything else! =(
Knox was triggered when flashing other than stock.
Forget about it.
Other is shown on mine as well.
CP stays empty at WiFi models.
UMS I've never did anything with.
Try to use other cables and USB ports.