Develop Bugs

[RECOVERY] CWM 6.0.1.9 + [TOOL] Recovery Builder

Developer Koush has a tool to build from the latest sources for ClockworkMod Recovery. It gives you the most recent changes in code so you don't need to wait for an official build.
DISCLAIMER:
Neither myself nor Koush is responsible for any damages caused to your device. These are EXPERIMENTAL / BETA builds and include code that may or may not have been approved by the developer for your specific device. Proceed at your own risk.
11/28/2012
Here is the latest build that is supposed to be optimized for JB 4.2
CWM-6.0.1.9-touch-recovery.img
Just did minor testing and it works fine.
As always...use at your own risk. I am not responsible for the bad things that happen to you. That's just called karma.
Click to expand...
Click to collapse
Tool: http://builder.clockworkmod.com/
Go to the "Existing Devices" tab and select "crespo4g" and use the check-box to toggle the option for touch recovery.
Credit goes to Koush for his build tool and custom recovery.
OLD
CWM 6.0.1.3 w/ Touch for fastboot: CWM-6.0.1.3-touch-recovery.img
CWM 6.0.1.3 w/o Touch for fastboot: CWM-6.0.1.3-recovery.img
The new version includes the option to create a flashable .zip from your current ROM while preserving your privacy by leaving out the /data partition.
Click to expand...
Click to collapse

cant get this to install
andrewddickey said:
Developer Koush has a tool to build from the latest sources for ClockworkMod Recovery. It gives you the most recent changes in code so you don't need to wait for an official build.
DISCLAIMER:
Neither myself nor Koush is responsible for any damages caused to your device. These are EXPERIMENTAL / BETA builds and include code that may or may not have been approved by the developer for your specific device. Proceed at your own risk.
CWM 6.0.1.3 w/ Touch for fastboot: CWM-6.0.1.3-touch-recovery.img
CWM 6.0.1.3 w/o Touch for fastboot: CWM-6.0.1.3-recovery.img
The new version includes the option to create a flashable .zip from your current ROM while preserving your privacy by leaving out the /data partition.
Tool: http://builder.clockworkmod.com/
Go to the "Existing Devices" tab and select "crespo4g" and use the check-box to toggle the option for touch recovery.
Credit goes to Koush for his build tool and custom recovery.
Click to expand...
Click to collapse
This will not install for me for some reason. I keep trying with fastboot and it keeps failing some failed: write error or something likes that. i even put the img in a zip and it still wont flash it. I dont know what i am doing wrong

nwo122383 said:
This will not install for me for some reason. I keep trying with fastboot and it keeps failing some failed: write error or something likes that. i even put the img in a zip and it still wont flash it. I dont know what i am doing wrong
Click to expand...
Click to collapse
Which one? Touch or regular? I used the touch .img and flashed on my phone just fine.
Put it in the same folder as fastboot and rename it to "recovery.img"
Use the command:
fastboot flash recovery recovery. img

Both give me the same problem I can flash other recoveries this just will not work I'll try again tomorrow
Sent from my Nexus S 4G using Tapatalk 2

Hypothetically speaking, would this tool work on any recovery....for example, twrp....or a ps freedom port so I could use my ns4g as a ps3 factory service mode dongle?

Both give me the same problem I can flash other recoveries this just will not work I'll try again tomorrow<br />
<br />
<br />
Sent from my Nexus S 4G using Tapatalk 2
Click to expand...
Click to collapse
I'll check when I get to the office in the morning. Might be an issue with the upload. Might have to re-up again.

hp420 said:
Hypothetically speaking, would this tool work on any recovery....for example, twrp....or a ps freedom port so I could use my ns4g as a ps3 factory service mode dongle?
Click to expand...
Click to collapse
To the best of my knowledge...no.
Only for CWM since it syncs with Koush's code.

nwo122383 said:
This will not install for me for some reason. I keep trying with fastboot and it keeps failing some failed: write error or something likes that. i even put the img in a zip and it still wont flash it. I dont know what i am doing wrong
Click to expand...
Click to collapse
My stupid fat fingers hit thanks on the wrong post
I had no issues flashing this recovery thru flash image gui...
Sent from my Nexus S 4G using Tapatalk 2

Just a little side note. When flashing a recovery or boot image via fastboot, and you have problems, try the erase command first:
fastboot erase recovery
Then
fastboot flash recovery recovery.img
Just a good safety measure.
Later,
~WickiD~
-----
Sent from my phone
using my finger...
-----

wickid_d said:
Just a little side note. When flashing a recovery or boot image via fastboot, and you have problems, try the erase command first:
fastboot erase recovery
Then
fastboot flash recovery recovery.img
Just a good safety measure.
Later,
~WickiD~
-----
Sent from my phone
using my finger...
-----
Click to expand...
Click to collapse
I just tried this and still same error
FAILED (remote: Write Fail)
i just cant seem to get this recovery to load. i can flash any other recovery via fastboot except this one. i flashed earlier cwm and twrp. i also tried putting this in a flashable zip that didnt work and then i tried using flash image gui to get this to work and that did not work. i dont know what i am doing wrong.
i am going to try to redownlad the files and try to flash again maybe i got 2 bad downloads.
update: even after redownloading still getting that same error. but i can flash other recoveries this is perturbing me.

nwo122383 said:
i just cant seem to get this recovery to load. i can flash any other recovery via fastboot except this one.
Click to expand...
Click to collapse
Ditto. No info to provide as to why I am having trouble. No worries

This recovery Success damaged my d720 after format sdcard system and data.. cwm cant mount it after reboot... even twrp can help or stock recovery will not recognized.. but folder is there if check via adb command.
Sent from my Galaxy Nexus using xda premium

6.0.1.9
Here is the latest build that is supposed to be optimized for JB 4.2
CWM-6.0.1.9-touch-recovery.img
Just did minor testing and it works fine.
As always...use at your own risk. I am not responsible for the bad things that happen to you. That's just called karma.

andrewddickey said:
Here is the latest build that is supposed to be optimized for JB 4.2
CWM-6.0.1.9-touch-recovery.img
Just did minor testing and it works fine.
As always...use at your own risk. I am not responsible for the bad things that happen to you. That's just called karma.
Click to expand...
Click to collapse
Hmm..I found that USB mount doesn't work in 6.0.1.9 (crespo)
So I guess there'll be same issue can be occured in crespo4g.
Sent from my Nexus S using Tapatalk 2

andrewddickey said:
Here is the latest build that is supposed to be optimized for JB 4.2
CWM-6.0.1.9-touch-recovery.img
Just did minor testing and it works fine.
As always...use at your own risk. I am not responsible for the bad things that happen to you. That's just called karma.
Click to expand...
Click to collapse
Karma would be the things that happen to you when ya have it coming...not things that happen due to glitched software and such. Have you tested the primary uses for the update you posted? Any negative results found? Just a matter of curiosity...
Sent from my Nexus S 4G using XDA Premium HD app
---------- Post added at 10:57 PM ---------- Previous post was at 10:55 PM ----------
Just asking as I would hate to have to send the whole night troubleshooting my device to sort out the bad karma lol
Sent from my Nexus S 4G using XDA Premium HD app

Thanks for clearing that up for me.
Working:
Flash
Backup
Restore
Wipes
Fix Permissions
Not Working:
Mount USB
Odd:
When you select "Reboot System", it asks if you want to disable ROMs from flashing a recovery. Just hit "Back" to reboot.
That's the extent of my testing. Will do more tomorrow.
He did remove all the extra "No"s when confirming selection. That's nice.

Is there a way to flash this from my phone?
Sent from my Nexus S 4G using Tapatalk 2
---------- Post added at 03:38 AM ---------- Previous post was at 03:18 AM ----------
Nm
Sent from my Nexus S 4G using Tapatalk 2

no matter how many recoveries i try to flash through fastboot, nothing stays, it always sends me to stock recovery. any tips?

lemonoid said:
no matter how many recoveries i try to flash through fastboot, nothing stays, it always sends me to stock recovery. any tips?
Click to expand...
Click to collapse
I think you have to change a file name to install.recovery.sh.old or something like that

where is the guide or tutorial?
where is the guide or tutorial?

[Q] CWM not replacing Android Recovery after newest OTA update / Lost Root

I recently purchased this SGS3, installed CWM and rooted it. Everything was going great - but then i was offered the most recent OTA update, so i reflashed the stock recovery via Odin, did the update which is:
4.0.4
T999EVLH2
same kernel
bld #: IMM76D.T999EVALH2
now, its saying the phone is no longer rooted (yet superSU is still there) but checkroot is saying that it isnt rooted, and no matter what i do, flashing CWM via Odin passes, but will not stick (as in, i boot into recovery mode and that damned stock recovery is STILL THERE, wtf?)
can anyone offer any assistance or insight into my issue.
Thanks
~Wikkid

Flash CWM v6. If that alone doesn't fix it, disable auto reboot in Odin, after flash, reboot phone manually into recovery mode.

Aerowinder said:
Flash CWM v6. If that alone doesn't fix it, disable auto reboot in Odin, after flash, reboot phone manually into recovery mode.
Click to expand...
Click to collapse
thats the version i've been using. tried to redownload, both touch and regular versions. tried disabling autoreboot and manually rebooting into recovery mode, but the recovery mode remains stock recovery. super weird.

mikewikkid said:
thats the version i've been using. tried to redownload, both touch and regular versions. tried disabling autoreboot and manually rebooting into recovery mode, but the recovery mode remains stock recovery. super weird.
Click to expand...
Click to collapse
Can you describe for me, in the greatest detail possible, how to reproduce your exact problem?
I've done it countless times in the past days, and it has worked every time.

Aerowinder said:
Can you describe for me, in the greatest detail possible, how to reproduce your exact problem?
I've done it countless times in the past days, and it has worked every time.
Click to expand...
Click to collapse
as have i, for myself and for others - this is the first time an Odin flash says pass but simply wont take.
Like i said, i flashed stock recovery onto phone using Odin3 1.78 while in download mode
rebooted and took OTA update a few days ago
now i tried to flash multiple versions of CWM v6, touch and regular using Odin and everything looks good, it says pass and everything.
when i reboot into recovery mode by holding powerup, home, and power - it takes me into stock recovery still.
its as if the recovery is either not being written to the right place or it is loading from another location on the device. i dont know how to make this issue happen on a phone, ive never seen it happen before myself. which is why i come to the pros seeking help - im no n00b myself, but i certainly am no developer.

mikewikkid said:
as have i, for myself and for others - this is the first time an Odin flash says pass but simply wont take.
Like i said, i flashed stock recovery onto phone using Odin3 1.78 while in download mode
rebooted and took OTA update a few days ago
now i tried to flash multiple versions of CWM v6, touch and regular using Odin and everything looks good, it says pass and everything.
when i reboot into recovery mode by holding powerup, home, and power - it takes me into stock recovery still.
its as if the recovery is either not being written to the right place or it is loading from another location on the device. i dont know how to make this issue happen on a phone, ive never seen it happen before myself. which is why i come to the pros seeking help - im no n00b myself, but i certainly am no developer.
Click to expand...
Click to collapse
Proper CWM Touch: http://forum.xda-developers.com/attachment.php?attachmentid=1287723&d=1346158787
Proper Odin: http://db.tt/jv6pHg8b

Aerowinder said:
Proper CWM Touch: http://forum.xda-developers.com/attachment.php?attachmentid=1287723&d=1346158787
Proper Odin: http://db.tt/sUJixYID
Click to expand...
Click to collapse
now THAT version of CWM worked, dunno why the one's i had worked a couple days ago and now they wouldn't, and even the ones that i downloaded fresh - must have been the wrong versions.
for the record, i did have Odin3 3.07 also, and i tried using that one as well, so it must have needed the newest CWM, which i obviously wasnt downloading. thanks alot mate!

mikewikkid said:
now THAT version of CWM worked, dunno why the one's i had worked a couple days ago and now they wouldn't, and even the ones that i downloaded fresh - must have been the wrong versions.
for the record, i did have Odin3 3.07 also, and i tried using that one as well, so it must have needed the newest CWM, which i obviously wasnt downloading. thanks alot mate!
Click to expand...
Click to collapse
Sure thing. If I were to guess, I'd go with incorrect permissions on recovery.img file. I learned that lesson the hard way.

Aerowinder said:
Sure thing. If I were to guess, I'd go with incorrect permissions on recovery.img file. I learned that lesson the hard way.
Click to expand...
Click to collapse
found what was probably causing the issue too - as you first suspected, but in greater detail on how to avoid this in the future:
"Apparently for those who have ran the official update by samsung are having this issue where the stock recovery is overwriting CWM recovery after reboot. Here is how to fix the issue. Credit to Max from Galaxys3root
You will need to rename or delete these two files.
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
I just renamed them. I'm thinking once there is a offical update such as jelly bean that I want to update too ill just rename them back so the stock recovery will reload and allow the update."

mikewikkid said:
found what was probably causing the issue too - as you first suspected, but in greater detail on how to avoid this in the future:
"Apparently for those who have ran the official update by samsung are having this issue where the stock recovery is overwriting CWM recovery after reboot. Here is how to fix the issue. Credit to Max from Galaxys3root
You will need to rename or delete these two files.
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
I just renamed them. I'm thinking once there is a offical update such as jelly bean that I want to update too ill just rename them back so the stock recovery will reload and allow the update."
Click to expand...
Click to collapse
Thanks a bunch for that information, I've been trying to get the CWM to stick and was getting extremely frustrated with it reverting after every boot. Deleting these files fixed it and I now have CWM v5.5.0.4 installed and surviving a couple boots. It took a few tries to delete the files, though, finally used ES file explorer and went in to settings to allow root acess.

You wouldn't have had any issues at all if you were using a version of CWM even somewhat recent. Because it prompts you to remove those files.

xanderman said:
Thanks a bunch for that information, I've been trying to get the CWM to stick and was getting extremely frustrated with it reverting after every boot. Deleting these files fixed it and I now have CWM v5.5.0.4 installed and surviving a couple boots. It took a few tries to delete the files, though, finally used ES file explorer and went in to settings to allow root acess.
Click to expand...
Click to collapse
this worked for me guys
http://www.droidviews.com/root-and-...-s4-sph-l720-and-t-mobile-galaxy-s4-sgh-m919/
---------- Post added at 01:37 AM ---------- Previous post was at 01:34 AM ----------
Aerowinder said:
You wouldn't have had any issues at all if you were using a version of CWM even somewhat recent. Because it prompts you to remove those files.
Click to expand...
Click to collapse
try these instructions
http://www.droidviews.com/root-and-...-s4-sph-l720-and-t-mobile-galaxy-s4-sgh-m919/

Thistleknot said:
this worked for me guys
http://www.droidviews.com/root-and-...-s4-sph-l720-and-t-mobile-galaxy-s4-sgh-m919/
---------- Post added at 01:37 AM ---------- Previous post was at 01:34 AM ----------
try these instructions
http://www.droidviews.com/root-and-...-s4-sph-l720-and-t-mobile-galaxy-s4-sgh-m919/
Click to expand...
Click to collapse
Umm, 2 things....
You realize this thread is over a year old and the last post was over 9 months ago?
And those links look like they are for the S4....
Sent from my SGH-T999V using Tapatalk 4

[Guide] Updated Rooting Instructions - Samsung Captivate Glide - SGH-I927

PROCEED AT YOUR OWN RISK!
Here is a thread to root your phone that works also!
http://forum.xda-developers.com/showthread.php?t=1833579
What I did to root my phone, because I didn't follow the above post, --- because I didn't look hard enough in the forums!
Also, If you want to overclock your phone use this guide -
Download and the extract the boot image - i927R-boot-ardatdat-AA.img.tar
http://forum.xda-developers.com/attachment.php?attachmentid=807369&d=1323188479
Original Forum - http://forum.xda-developers.com/showpost.php?p=20041051&postcount=108
Put your phone in Download Mode:
Turn off the phone
Press volume UP and keeping the button pressed, press the power button
a screen should ask you if you wanna continue - press volume up to confirm
Launch Odin
in PDA, select the boot image you just extracted it is a tar file - i927R-boot-ardatdat-AA.img.tar
DON'T SELECT or UNSELECT ANYTHING ELSE
Press the start button
Wait for your phone to reboot
Reboot your device into download mode again (steps above)
Click to expand...
Click to collapse
- Credit to CarpeNoctem - Forum Guide - Here
Flash the STOCK ROOTED ROM using my (steps below)
1. Download Odin - Odin 3.07 --- Not a must for rooting but great tool to have!
2. Download CWM6 - There are newer versions but I know this works! - Thanks AndyYan - CWM6.0.1.2
Original thread - http://forum.xda-developers.com/showthread.php?p=34479219
3. Downloaded - Stock Rooted UCLJ3 ROM - STOCK ROOTED UCLJ3 ROM - Android 4.0.4
4. Place the zipped STOCK ROOTED folder on your External SD Card --- In the root of the sdcard --- what that means is don't put it in a folder! - You can do this by putting your card in your computer or laptop, if you have a media reader or usb adapter Buy One Here - once its on the external sd card place it back in the phone
5. Boot into CWM6 -
5a - Power off phone
5b - Power up phone while holding the down volume key - This boots you into CWM6
6. Once in CWM6 you can update to the ROOTED STOCK ROM
7. Select - Install zip from sdcard
8. Select - choose zip from external sdcard
9. Select - UCALJ3 - Stock.zip
From there just follow the prompts if any!
Once the update is done all should be well!
If I failed to credit anyone or their forum post please let me know!

Just an addition: if you're already on a stock ROM (without ROOT) and want to root without changing the ROM you're now using, just not flash the Stock UCLJ3 zip and instead flash the latest SuperUser or SuperSU zip found floating around the Internet.
Sent from Samsung Captivate Glide @ CM10.1.2

Yep hense the very first link in the post! That forum explains how to do that exact process.
Sent from my SGH-I927 using xda app-developers app

AndyYan said:
Just an addition: if you're already on a stock ROM (without ROOT) and want to root without changing the ROM you're now using, just not flash the Stock UCLJ3 zip and instead flash the latest SuperUser or SuperSU zip found floating around the Internet.
Sent from Samsung Captivate Glide @ CM10.1.2
Click to expand...
Click to collapse
Hi friend "AndyYan" then if I have a stock ROM installed as non-root in my case is that ICS 4.0.4 update through Kies, I can then just install direct CWM6 SD-card or necessarily need to use Odin.
Since I am not very clear because download Odin? supposedly the stock ROM if I will install directly to SD-card and run with CWM6 there?
Excuse my ignorance, but I'm too new, and I'm afraid to leave my phone useless?
Thanks
---------- Post added at 09:30 PM ---------- Previous post was at 09:23 PM ----------
Very very much for this excellent guide, and I've searched and searched and finally found this, because I wanted to try taking root, as many other stir all as assuming one knows.
Thanks friend "ll81702". :good::good:

skynet777 said:
Hi friend "AndyYan" then if I have a stock ROM installed as non-root in my case is that ICS 4.0.4 update through Kies, I can then just install direct CWM6 SD-card or necessarily need to use Odin.
Since I am not very clear because download Odin? supposedly the stock ROM if I will install directly to SD-card and run with CWM6 there?
Excuse my ignorance, but I'm too new, and I'm afraid to leave my phone useless?
Thanks
---------- Post added at 09:30 PM ---------- Previous post was at 09:23 PM ----------
Very very much for this excellent guide, and I've searched and searched and finally found this, because I wanted to try taking root, as many other stir all as assuming one knows.
Thanks friend "ll81702". :good::good:
Click to expand...
Click to collapse
Updated via KIES, right? Then you need Odin to flash CWM. You can't get CWM directly from SD.
Sent from Google Nexus 4 @ Android 4.4 KRT16M

Thanks, but what if I do the steps indicated by the friend "ll81702", because as I said I have already ICS 4.0.4, cause some conflict if I restart the UCLJ3 ROOTED STOCK ROM - Android 4.0.4 indicating the guide or only one set you need superuser or SuperSU and of course install with Odin the CWM6.0.1.2, which option would you recommend
Thanks...

I am not sure I understand your question. Can you rephrase?
Sent from my SGH-I927 using xda app-developers app

I think skynet is trying to say that because he already has the stock firmware, would the rooted one conflict with his current one, and he would like your input on whether to install the superuser.zip or the cwm via Odin.
Sent from my SGHI927 using Tapatalk

If you just want to root your phone you just need to load cwm6 using Odin then place the superuser zip on your sdcard. Boot into cwm6 and load the zip.
Sent from my SGH-I927 using xda app-developers app

Exactly as it says the friend "LaizureBoy", but what would happen if I use the method of the guide, I could return it to its normal state (without root), because as I see the method of Friend "ll81702" the UCALJ3-Stock.zip this is STOCK ROOTED, for as I understand this would only be root, then you can not remove the root
Thank you for your comments and support. :good:
PD: Excuse my English because I do not understand very well and use a translator ...
---------- Post added at 09:53 PM ---------- Previous post was at 09:03 PM ----------
:laugh: Hi again because in this other guide need a "CarrierIQ FREE kernel (zip file) or the overclocked version of it" and are not using the CWM or is that CarrierIQ is the same
http://forum.xda-developers.com/showthread.php?t=1378082

If you root your stock ROM it can be returned to unrooted at any time.
Sent from my SGH-I927 using xda app-developers app

Thank you II81702 and AndyYan. I have the SGH-I927... I originally used ODIN to flash the carrrier free kernal... but I noticed something strange- upon reboot, it just came up with the Samsung logo and stopped there.
I was then able go into download mode again and flashed the at&t rooted ROM from the OP on 12-6-11. When it rebooted, it got hung on the samsung logo as well.
I then flashed the CWM6 and then booted up in recovery mode.
I installed the Stock Rooted UCLJ3 ROM from the external sd card and then rebooted.
now when it first reboots, it starts out with the samsung logo then 10 sec later, it get brings up the word ANDROID and gets hung there...
So am back to square one. : crying:

d1david said:
Thank you II81702 and AndyYan. I have the SGH-I927... I originally used ODIN to flash the carrrier free kernal... but I noticed something strange- upon reboot, it just came up with the Samsung logo and stopped there.
I was then able go into download mode again and flashed the at&t rooted ROM from the OP on 12-6-11. When it rebooted, it got hung on the samsung logo as well.
I then flashed the CWM6 and then booted up in recovery mode.
I installed the Stock Rooted UCLJ3 ROM from the external sd card and then rebooted.
now when it first reboots, it starts out with the samsung logo then 10 sec later, it get brings up the word ANDROID and gets hung there...
So am back to square one. : crying:
Click to expand...
Click to collapse
You are not stuck it can take 15 mins or more to get past the android screen.
If you did not do a clean wipe of your phone it will take a very long time to load.

ll81702 said:
You are not stuck it can take 15 mins or more to get past the android screen.
If you did not do a clean wipe of your phone it will take a very long time to load.
Click to expand...
Click to collapse
Thanks!! I re-wiped, re-flashed the ROM and it booted up in 5 min.
Now when I turn on the phone it has the Samsung symbol and the yellow turned to blue exclamation point and then the usual boot up after that..
seems to be fine besides that. Many thanks for your posts! :good:

d1david said:
Thanks!! I re-wiped, re-flashed the ROM and it booted up in 5 min.
Now when I turn on the phone it has the Samsung symbol and the yellow turned to blue exclamation point and then the usual boot up after that..
seems to be fine besides that. Many thanks for your posts! :good:
Click to expand...
Click to collapse
Very normal!
The kernel you're using is an overclock kernel, its the same one i use!

Hi sorry for asking this, have heard of software called "UnlockRoot Pro" according to this by simply connecting the device to the software that makes root or unroot the device is a paid software, but actually works on a SGH-i927 (Captivate Glide) .
Thanks...

Why pay for something you can get for free?
Sent from my SGH-I927 using xda app-developers app

ll81702 said:
Very normal!
The kernel you're using is an overclock kernel, its the same one i use!
Click to expand...
Click to collapse
Gps doesn't seem to work ... trying google navigation... keeps saying "searching for GPS".....
Does anyone know of any fixes

d1david said:
Gps doesn't seem to work ... trying google navigation... keeps saying "searching for GPS".....
Does anyone know of any fixes
Click to expand...
Click to collapse
I do not have this issue......not sure why you would be......

ll81702 said:
I do not have this issue......not sure why you would be......
Click to expand...
Click to collapse
It ended up working fine. It just took about 8 minutes for the phone to locate the gps... then it was ok after that.... did some research and I will try do some mods to the gps/sysconf files and see if it helps it find the gps faster.
Thanks again for all your work

[Q] [HELP] Trying to flash TWRP on V50020b

Im trying to flash TWRP on my v50020b but cannot seem to do it. Its currently on the stock 4.4.2 GB rom. Please can someone advise me how to do this.
Thank You.

You can use dd to write the aboot.img of 4.2.2 back. This will allow the old Loki flash method.
Sent from my LG-V500 using Tapatalk
---------- Post added at 01:25 AM ---------- Previous post was at 01:07 AM ----------
http://forum.xda-developers.com/showthread.php?t=2698267 Step 3
Sent from my LG-V500 using Tapatalk

bloommax said:
You can use dd to write the aboot.img of 4.2.2 back. This will allow the old Loki flash method.
Sent from my LG-V500 using Tapatalk
---------- Post added at 01:25 AM ---------- Previous post was at 01:07 AM ----------
http://forum.xda-developers.com/showthread.php?t=2698267 Step 3
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
i tried doing this couldn't get it to work.. i have of done it wrong?
could you post the steps in noob style?
or does anyone know of a guide on how to install a custom recovery on a V50020b running stock 4.4.2 (i managed to root just need recovery)

gklute said:
i tried doing this couldn't get it to work.. i have of done it wrong?
could you post the steps in noob style?
or does anyone know of a guide on how to install a custom recovery on a V50020b running stock 4.4.2 (i managed to root just need recovery)
Click to expand...
Click to collapse
I had the same problem until I ran across this post: http://forum.xda-developers.com/showthread.php?t=2698267 {Acually the same you quoted}
If you'll go down to the download Step #3 and copy that zip file to your computer and unzip it and run the bat file it will install TWRP v2.7. Of course you'll have to install the LG USB drivers and install from your computer. (Won't work otherwise) Also be sure and use the second down connection for USB on your tablet - M-something, but not the charging one.
Also - get a good reboot app so you won't have to hold the buttons.

ruhelking1 said:
Im trying to flash TWRP on my v50020b but cannot seem to do it. Its currently on the stock 4.4.2 GB rom. Please can someone advise me how to do this.
Click to expand...
Click to collapse
You're being vague! Which TWRP?

Cal said:
I had the same problem until I ran across this post: http://forum.xda-developers.com/showthread.php?t=2698267 {Acually the same you quoted}
If you'll go down to the download Step #3 and copy that zip file to your computer and unzip it and run the bat file it will install TWRP v2.7. Of course you'll have to install the LG USB drivers and install from your computer. (Won't work otherwise) Also be sure and use the second down connection for USB on your tablet - M-something, but not the charging one.
Also - get a good reboot app so you won't have to hold the buttons.
Click to expand...
Click to collapse
I also have this version V50020b and this method didn't work.
When boot to recovery there's still the android recovery!!
What am I doing wrong?
Thanks in advance.

luisbraz said:
I also have this version V50020b and this method didn't work.
When boot to recovery there's still the android recovery!!
What am I doing wrong?
Thanks in advance.
Click to expand...
Click to collapse
You're quoting an old post (way back in April 2014).
1st - Do you have a recovery installed?
2nd - If so, you should update to at least TWRP 2.800
I may be confused about exactly what you are doing...now if you're only booting with the buttons (power-sound down, sound up) that is the message you get and you have to push 'power' 2 times to enter recovery. Are you doing that when you see the display of android recovery after using the cold boot, then the volume and power buttons?? And you are expecting to see TWRP opening, but instead of going straight to TWRP recovery - you're getting what you say 'Android Recovery', or Factory Reset?
Post back so we will understand please. Hope I'm not being confusing in my answers...

Cal said:
You're quoting an old post (way back in April 2014).
1st - Do you have a recovery installed?
2nd - If so, you should update to at least TWRP 2.800
I may be confused about exactly what you are doing...now if you're only booting with the buttons (power-sound down, sound up) that is the message you get and you have to push 'power' 2 times to enter recovery. Are you doing that when you see the display of android recovery after using the cold boot, then the volume and power buttons?? And you are expecting to see TWRP opening, but instead of going straight to TWRP recovery - you're getting what you say 'Android Recovery', or Factory Reset?
Post back so we will understand please. Hope I'm not being confusing in my answers...
Click to expand...
Click to collapse
I know that is an old post. I was trying to flash the TWRP recovery without any downgrade of the software, since this method was suposed to work with the software version V50020b.
I simply want to flash TWRP recovery, the tablet is all stock with root (TowelRoot), but I just realised that I have to downgrade the software (http://forum.xda-developers.com/showpost.php?p=58198471&postcount=44), and wanted to avoid this! I already softbricked the tablet with only 3h of usage, and now I'm a little afraid! lol
Do you now any method that works without the downgrade trick?
Thanks.

Flash TWRP with flashify (root) - (from Play Store).
This *should* work & if not I think no harm will come ... Flashify.app just won't 'work' if things are not correct.
Good luck!

Cal said:
Flash TWRP with flashify (root) - (from Play Store).
This *should* work & if not I think no harm will come ... Flashify.app just won't 'work' if things are not correct.
Good luck!
Click to expand...
Click to collapse
I did that. That's what softbricked the tablet!

luisbraz said:
I did that. That's what softbricked the tablet!
Click to expand...
Click to collapse
I would shut the tablet completely down.
You should be able to use the 'buttons' to get to 'Factory Reset'. Do what you know: Power/+down then all 3. If you can't get to TWRP, it must not be installed.
Check with a command window. Be sure & use 'su'. Ask a guru 'how'...I may not be 'expert' enough!

ruhelking1 said:
Im trying to flash TWRP on my v50020b but cannot seem to do it. Its currently on the stock 4.4.2 GB rom. Please can someone advise me how to do this.
Thank You.
Click to expand...
Click to collapse
Hi, i had the same problem as yours with v50020d 4.4.2
first i rooted with ioroot http://forum.xda-developers.com/showthread.php?t=2776198
second install step 3 http://forum.xda-developers.com/show....php?t=2698267
you have to run "runme.bat" from the zip. If did not install here is a post that helped me http://forum.xda-developers.com/showpost.php?p=54027265&postcount=9
then flash witch recovery you want with flashify or twrp app
if you have any questions message me.
good luck

Stuck on Restart

After 3 yrs on custom ROMs, I've managed to screw up my Note 2, and I'm lost as to how to restore my phone.
I've been on the Jedi Touchwiz ROM for ages, and about a year ago, changed over to Cyanogen.
I went from the Cyanogen 0825-Nightly to the latest 1017-Nightly by:
-backing up my data in Titanium Root,
-going into Recovery and doing a Wipe Data/Factory Reset,
-install the new 1017-Nightly image
-install GAPPS for Android 5.1
then reboot.
All is good on reboot, and I enter my Google info, mount desktop. I then install the Titanium Root app, and it reports that I've lost Root.
So I try to update SuperSU, and it fails to do it directly, and trying to do it with CWM Recovery fails as well.
I then use Recovery to Wipe Data/Factory Reset again,
reinstall 1017-Nightly and GAPPS 5.1
and reboot, thinking I must have missed something.
Now... I'm stuck on the Cyanogen Loadscreen (pulsing Blue Head). I haven't let it go longer than 10mins, but I don't think it should take that long.
I tried going back to my 0825-Nightly after this point, and no luck, I'm stuck on the Loadscreen.
Here are my questions:
1. I do not understand what being stuck on the Loadscreen means... what do I need to fix? Can I do it via Recovery?
2. How do I obtain Root again? The methods I originally used were for Jellybean... are there updated methods now?
3. What prevents SuperUser from updating?
Thanks for any help guys... I need my phone back!

on your second attempt you got stuck on boot screen??
i think you can wait for some more time and check..
remove battery re-insert and check whether it boots or not.. or else do a factory reset n check whether it boots or not..
if not do a factory reset and re flash the CM to check.
. if all failed then flash n7100 stock firmware via odin ..
about rooting.. if you have a custom recovery you can try to re root via custom recovery.. simply flash supersu.zip in your custom recovery...
https://download.chainfire.eu/696/SuperSU

Hi Tornado,
BTW, Tornados, esp the IDS variant, are great planes. Nice to see your avatar :good:
I had a comment from elsewhere, so I tried this:
-wipe data/factory reset inside CWM Touch Recovery
-formatted /system partition
-installed the 20151007 CM 12.1 Snapshot
-installed GAPPS 5.1
and then let it reboot. LOL, I've been worried about screen burn in, but I left it run for over an hour... no joy. It never left the loadscreen.
Just for grins, I tried the older CM11 version, and whilst the loadscreen problem still persisted, I did recognize the older boot animation.
At this point, am convinced I have soft-bricked the phone, since I have Recovery and Bootloader (thank goodness) still working, but something else is either not clearing or is corrupted.
I'm definitely thinking about flashing stock firmware again, but not sure if I should go back to Jellybean? or find an Android 5 image?
Am also looking into ADB commands to see if there is something deeper I can flush out, but I really don't want to make things worst.
I'm hoping that someone else has run into a similar situation... cheers for your suggestions!
tornado92 said:
on your second attempt you got stuck on boot screen??
i think you can wait for some more time and check..
remove battery re-insert and check whether it boots or not.. or else do a factory reset n check whether it boots or not..
if not do a factory reset and re flash the CM to check.
. if all failed then flash n7100 stock firmware via odin ..
about rooting.. if you have a custom recovery you can try to re root via custom recovery.. simply flash supersu.zip in your custom recovery...
https://download.chainfire.eu/696/SuperSU
Click to expand...
Click to collapse

Enter custom recovery.. and find mount and unmount area.. and select mount system then restart phone n tell me result

I went into Recovery:
-selected Mount System
-Reboot
Phone stayed on Loadscreen for 30 mins. After that, I yanked the battery.
I'm going to go into Bootloader, and swap out CWM for TWRP to see if that makes a difference. If any changes, will report back.
tornado92 said:
Enter custom recovery.. and find mount and unmount area.. and select mount system then restart phone n tell me result
Click to expand...
Click to collapse

UGH. Still no joy.
Changed out CWM Recovery to TWRP,
-did Full Reset
-Advanced Wipe of System, Data, Int Storage
-install 1007 Snapshot of CM12.1
-install GAPPS 5.1
then reboot.
After 35mins of loadscreen, yanked the battery.
I can change Recovery images like a Boss now at least :silly:
motionmonk said:
I'm going to go into Bootloader, and swap out CWM for TWRP to see if that makes a difference. If any changes, will report back.
Click to expand...
Click to collapse

Best option for you now is to unbrick your device to official stock firmware... and then try to install custom rom again... i can make ur device boot normally at this stage.. but ur phone will boot on factory imei..meaning wont detect sim .. so first unbrick your device to be at safer place to avoid further corrupting the efs.. hahahaaa
---------- Post added at 12:05 PM ---------- Previous post was at 11:56 AM ----------
Install official firmware.. and enter stock recovery.. and try to reeset ur phone.. if u get a error code e/failed.to.mount efs.. ur efs is.messed up which is preventing ur phone from booting.. but if dont get any error your phone will boot normally
---------- Post added at 12:06 PM ---------- Previous post was at 12:05 PM ----------
tornado92 said:
Best option for you now is to unbrick your device to official stock firmware... and then try to install custom rom again... i can make ur device boot normally at this stage.. but ur phone will boot on factory imei..meaning wont detect sim .. so first unbrick your device to be at safer place to avoid further corrupting the efs.. hahahaaa
---------- Post added at 12:05 PM ---------- Previous post was at 11:56 AM ----------
Install official firmware.. and enter stock recovery.. and try to reeset ur phone.. if u get a error code e/failed.to.mount efs.. ur efs is.messed up which is preventing ur phone from booting.. but if dont get any error your phone will boot normally
Click to expand...
Click to collapse
Keep updating me. I will guide u further

Just so I don't dig a deeper hole, I want to clarify a few points...
1. by going back to stock firmware, do you mean a certain OS version? If I find a stock Android 5 version, is that ok? or would going back to like Jellybean be better?
2. you mentioned that the factory imei will not detect my sim, so the radio won't work? If so, there is a way to fix this?
3. again for stock firmware... my phone is an American N7100 GSM (T-Mobile) version. About 2 years ago, it became an Int'l N7105 LTE mod, since I liked the feature set more, plus one of my past ROMs (Jedi-X?) I think changed it to the N7105.
-should I go back to a pure N7100 stock firmware, or a N7105 firmware?
Will start looking for firmware options in the meantime.
tornado92 said:
Best option for you now is to unbrick your device to official stock firmware... and then try to install custom rom again... i can make ur device boot normally at this stage.. but ur phone will boot on factory imei..meaning wont detect sim .. so first unbrick your device to be at safer place to avoid further corrupting the efs.. hahahaaa
Install official firmware.. and enter stock recovery.. and try to reeset ur phone.. if u get a error code e/failed.to.mount efs.. ur efs is.messed up which is preventing ur phone from booting.. but if dont get any error your phone will boot normally
Keep updating me. I will guide u further
Click to expand...
Click to collapse

There is no 5.0 stock firmware for n7100 . Latest is 4.4.2 if your phone model is n7100 in download mode. Then your phone isnt tmobile.. and about factory imei .. first unbrick your device to check the status of your imei.. it could be fine also...right now phone not booting up.. so i cant tell...

Understood, grabbing 4.42 Stock Images.
From this page: http://forum.xda-developers.com/showthread.php?t=2740496
I grabbed the first 2x Installers.
-KitKat 4.4.2. Stock Rom by robalm
-4.4.2 DN3 (Ditto Note 3) Rom from E-Team
Both are these are .zip files; the one by robalm suggests using Odin for install. The 2nd one by Electron Team using custom Recovery (CWM/TWRP).
Will try Electron Team first, and if nothing happens, will try Odin and 1st one.
tornado92 said:
There is no 5.0 stock firmware for n7100 . Latest is 4.4.2 if your phone model is n7100 in download mode. Then your phone isnt tmobile.. and about factory imei .. first unbrick your device to check the status of your imei.. it could be fine also...right now phone not booting up.. so i cant tell...
Click to expand...
Click to collapse

As u wish buddy. I recommend odin one first as its a stock firmware

Tried the Ditto Note3 ROM; no luck.
Inside TWRP Recovery, I did:
-Factory Reset
-Format Data
-inside Mount settings, verified EFS, cache, System, Data, Ext_SDCard were selected
-install Zip FAILED:
Error flashing zip ‘/external_sdcard/N7100XXUFND3_N7100OXAFND3_XEF.zip'
updating partition details…
…done
That is the extent of the error reporting. Tried 2x, both had same error log.
Yanked battery, went into Recovery again and re-installed the CM12 1007 Snapshot. I am back to the same loadscreen loop issue.
Moving on to Odin and the KitKat 4.4.2 ROM by robalm
motionmonk said:
Understood, grabbing 4.42 Stock Images.
Will try Electron Team first, and if nothing happens, will try Odin and 1st one.
Click to expand...
Click to collapse

Something happening with your partitions probably, listen the advice of tornado and flash it via odin.
Sent from my GT-N7100

Oh bugger me. Can't think straight.
I installed the wrong ROM. I copied the 'robalm' 4.4.2 KitKat ROM to my ext SD card by mistake. No wonder it failed.
Tried the correct DittoNote4 ROM; it failed.
This is from the TWRP recovery log:
minzip: Error writing 8192 bytes from zip file from 0xbe88da44: No space left on device
minzip: Process function elected to fail (in inflate)
minzip: Can't extract entry to file.
minzip: Error extracting "/system/usr/srec/en-US/g2p_fst"
about to run program [/tmp/floating_message.sh] with 1 args
- Symlinking files
set_perm: chown of /system/xbin/busybox to 0 1000 failed: No such file or directory
set_perm: chmod of /system/xbin/busybox to 755 failed: No such file or directory
script aborted: set_perm: some changes failed
set_perm: some changes failed
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/external_sdcard/DN4_v2.1_by_E-Team.zip'
Error flashing zip '/external_sdcard/DN4_v2.1_by_E-Team.zip'
Updating partition details...
I: Data backup size is 6MB, free: 11168MB.
Still going to give the "robalm" ROM a try in Odin.
motionmonk said:
Tried the Ditto Note3 ROM; no luck.
Inside TWRP Recovery, I did:
-Factory Reset
-Format Data
-inside Mount settings, verified EFS, cache, System, Data, Ext_SDCard were selected
-install Zip FAILED:
Error flashing zip ‘/external_sdcard/N7100XXUFND3_N7100OXAFND3_XEF.zip'
updating partition details…
…done
That is the extent of the error reporting. Tried 2x, both had same error log.
Yanked battery, went into Recovery again and re-installed the CM12 1007 Snapshot. I am back to the same loadscreen loop issue.
Moving on to Odin and the KitKat 4.4.2 ROM by robalm
Click to expand...
Click to collapse

Heeehe guide line
1: must have a working brain hahahah buddy

YAY! I'm in!
I used N7105XXDMA6_Deodex_Rooted_01_28_13-teshxx.zip and flashed via TWRP Recovery.
I was able to enter Google info in Samsung setup, and am up on device desktop.
Insert SIM Card, check About Device, I have this for a Status Check...
Network-unknown
Mobile Network Type-unknown
Service State-Out of service
Roaming-not roaming
Mobile network state-disconnected
My phone number-Unknown
IMEI-Unknown
IMEISV-Unknown
At least it's not the Loadscreen is all I can say!
Ok, gone for a few for a late lunch.
Will let the device settle in, and will check back for any further suggestions.
Thanks again Tornado!

WOT?
Life has an... Operations Manual?
hehe
tornado92 said:
Heeehe guide line
1: must have a working brain hahahah buddy
Click to expand...
Click to collapse

Your not in buddy.. ur efs partition is probably screwed up whats the use of a phone if it doest detect sim :s
---------- Post added at 11:06 PM ---------- Previous post was at 11:04 PM ----------
Flash stock firmware via odin to check whether imei comes back or not.. and dont mess too much with phone.. imei repair is not a easy thing.. ahaahah my advice for u
---------- Post added at 11:12 PM ---------- Previous post was at 11:06 PM ----------
whats ur actual model number.. is it n7100 or n7105 .. if ur phone is n7100 dont use n7105 firmwares.. a both are different hardware wisely yet your imei corrupted now due to different modem in n7105 firmware...

Am still here, been trying to track down valid firmware images.
I believe my phone is a N7100. Somewhere in replacing ROMs in the past, I think I installed an Int'l N7105 TouchWiz ROM (Jedi-X) and stuck with that using a T-Mo modem file.
Found a stock 4.3 for my SGH-T889 T-Mobile GSM phone today. So, tried an install using JODIN, an open-source Odin app, but it didn't reboot the phone, so not sure if it took.
Going to install a Windows partition, load KIES and true ODIN and try again tomorrow. Will update then.

@motionmonk buddyy go to download mode(pres volume down +power+ home) and post screen shot of it..
Sent from my GT-N7105 using Tapatalk