Upgrading to Jellybean OTA, Red Triangle fix! - Asus Transformer TF700

This is the same guide I posted in the OTA failure thread, but it got buried, so I decided to make it its own thread.
This will fix the red triangle when installing the OTA, when it is caused by a missing or mismatched /system file. Android OTAs usually check the integrity of /system, because when installing, it doesn't do a full wipe, just updates the parts that need to be updated. This guide reflashes the .30 update so you ill have all proper apks and other /system files (build.prop). You could extract each individual file from the blob, but if you have more than one file that needs replacing its a painstaking process of attempting the flash, getting an error and replacing it, this method just replaces all files in /system to stock.
Once you fail the OTA, you won't be able to receive it from the asus servers again, so you have to manually copy the update file (dlpkgfile) to the proper place, and create the correct command. I have heard that wiping cache and data on DMClient and CMClient will fix that issue, but it didn't work for me.
Another misconception is that doing a factory reset will fix the issue. It will fix not being able to download the OTA, but you will still won't be able to install it. A factory reset simply wipes /data, which all downloaded apps, and settings are stored, it doesn't affect /system or magically reinstall the apps in system.
I'm pretty sure you need a microSD card for this, but not 100% sure.
I had deleted(not frozen) some apks on .30, and when I got the ota it had the red triangle. I then tried copying dlpkgfile to /cache and doing it that way, it also gave the red triangle(because I hadn't restored the apps). After a few hours of fiddling with the .30 firmware I finally got it back to stock then used the dlpkgfile method. You also don't lose any data this way!
Steps 1-5 restores stock .30 if you have deleted any apps or can't figure out what changes are causing it to get the red triangle. Steps 6-11 are actually for installing Jellybean.
1. Download your SKU of .30 from the Asus Site
2. Unzip it once and place it on the external microSD card
3. Rename it to EP201_768_SDUPDATE.zip
4. Power off the device, then turn it back on while holding volume down
5. When the text appears hold down volume up to boot into recovery, it should recognize the .30 firmware and install it
6. Root your device, you will need this to copy files to cache, if you want to keep root, download SuperSU, run it, let it update the binary, then install and backup SU with OTA Rootkeeper
7. To install the Jellybean OTA, find a download link for your version of the dlpkgfile (Here is the US version, http://d-h.st/W8Y Thanks to bartleyg82 )
8. Copy to /cache and rename to dlpkgfile, if not already named that, NO EXTENSION
9. Create a file called command, under /cache/recovery, with the following text --update_package=/cache/dlpkgfile (I did this by doing echo "--update_package=/cache/dlpkgfile" >> /cache/recovery/command )
10. Power down the devices and power up using teh same volume down volume up technique as before
11. You should have Jellybean!
Sent from my ASUS Transformer Pad TF700T using xda premium

Can you give a little more explanation for "Create a file called command, under /cache/recovery, with the following text update_package=/cache/dlpkgfile (I did this by doing echo "update_package=/cache/dlpkgfile" >> /cache/recovery/command )"
Is this a simple .txt file?
Do you think you could upload the file you used?
I am having this same problem updating to jelly bean and I am hoping your fix will cure... Thanks!

I finally managed to find my mistake ...
I always tried to use the WW SKU dlpgkfile, because I bought it with WW SKU...
Just realized my tf700 changed from WW to US?? How is this even possible??
Can you give a little more explanation for "Create a file called command, under /cache/recovery, with the following text update_package=/cache/dlpkgfile (I did this by doing echo "update_package=/cache/dlpkgfile" >> /cache/recovery/command )"
Is this a simple .txt file?
Do you think you could upload the file you used?
I am having this same problem updating to jelly bean and I am hoping your fix will cure... Thanks!
Click to expand...
Click to collapse
You have to use ES Explorer. ( for free in Play Store)
Just navigate to "Cache/recovery" and add a new file.
Name this file "command"
Open and edit it with ES-Explorer to "--update_package=/cache/dlpgkfile"

Thank you very much for this guide !
Firmware upgrade to JB for WW versions (upgraded from .30)
(Thanks to Cryptopone, original post)

moah909 said:
4. Power off the device, then turn it back on while holding volume down
5. When the text appears hold down volume up to boot into recovery, it should recognize the .30 firmware and install it
Click to expand...
Click to collapse
its nice to see that it works 4 many people ... but i get stucked on point 5 .. starting and after 3-5 sec. red triangle ..
made everything: tried with factory reset, DM/CM .. really everything that is mentioned in forum .. fact is that a cant install .30 .. with and without root, with and without rootkeeper etc. ... no changes made on apps, no freeze etc. .. everytime this $%&// triangle
any suggestions?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Are you using an external microSD the errors appear to be about not being able to find /sdcard
Sent from my XT894 using xda premium

leberkas said:
its nice to see that it works 4 many people ... but i get stucked on point 5 .. starting and after 3-5 sec. red triangle ..
made everything: tried with factory reset, DM/CM .. really everything that is mentioned in forum .. fact is that a cant install .30 .. with and without root, with and without rootkeeper etc. ... no changes made on apps, no freeze etc. .. everytime this $%&// triangle
any suggestions?
Click to expand...
Click to collapse
try reformatting the sd card to fat32 the copy the EP201_768_SDUPDATE.zip back onto it.
this silly step has suddenly allowed me to reflash .30. Last night I tried many times to reflash to .30 and nothing worked.

moah909 said:
This is the same guide I posted in the OTA failure thread, but it got buried, so I decided to make it its own thread.
This will fix the red triangle when installing the OTA, when it is caused by a missing or mismatched /system file. Android OTAs usually check the integrity of /system, because when installing, it doesn't do a full wipe, just updates the parts that need to be updated. This guide reflashes the .30 update so you ill have all proper apks and other /system files (build.prop). You could extract each individual file from the blob, but if you have more than one file that needs replacing its a painstaking process of attempting the flash, getting an error and replacing it, this method just replaces all files in /system to stock.
Once you fail the OTA, you won't be able to receive it from the asus servers again, so you have to manually copy the update file (dlpkgfile) to the proper place, and create the correct command. I have heard that wiping cache and data on DMClient and CMClient will fix that issue, but it didn't work for me.
Another misconception is that doing a factory reset will fix the issue. It will fix not being able to download the OTA, but you will still won't be able to install it. A factory reset simply wipes /data, which all downloaded apps, and settings are stored, it doesn't affect /system or magically reinstall the apps in system.
I'm pretty sure you need a microSD card for this, but not 100% sure.
I had deleted(not frozen) some apks on .30, and when I got the ota it had the red triangle. I then tried copying dlpkgfile to /cache and doing it that way, it also gave the red triangle(because I hadn't restored the apps). After a few hours of fiddling with the .30 firmware I finally got it back to stock then used the dlpkgfile method. You also don't lose any data this way!
Steps 1-5 restores stock .30 if you have deleted any apps or can't figure out what changes are causing it to get the red triangle. Steps 6-11 are actually for installing Jellybean.
1. Download your SKU of .30 from the
2. Unzip it once and place it on the external microSD card
3. Rename it to EP201_768_SDUPDATE.zip
4. Power off the device, then turn it back on while holding volume down
5. When the text appears hold down volume up to boot into recovery, it should recognize the .30 firmware and install it
6. Root your device, you will need this to copy files to cache, if you want to keep root, download SuperSU, run it, let it update the binary, then install and backup SU with OTA Rootkeeper
7. To install the Jellybean OTA, find a download link for your version of the dlpkgfile (Here is the US version, ] Thanks to bartleyg82 )
8. Copy to /cache and rename to dlpkgfile, if not already named that, NO EXTENSION
9. Create a file called command, under /cache/recovery, with the following text update_package=/cache/dlpkgfile (I did this by doing echo "update_package=/cache/dlpkgfile" >> /cache/recovery/command )
10. Power down the devices and power up using teh same volume down volume up technique as before
11. You should have Jellybean!
Sent from my ASUS Transformer Pad TF700T using xda premium
Click to expand...
Click to collapse
trying to update using this method. still not working no matter what i do. tried putting files in /cache and even at the root of my sdcard. still nothing. i am rooted locked up tight and running .30 firmware. havent added or deleted anything just did a factory reset and everything. HELP PLEASE!

Keeps failing
I reloaded .30 with no problems and then tried the JB update manually. It fails every time.

Aski1 said:
I finally managed to find my mistake ...
I always tried to use the WW SKU dlpgkfile, because I bought it with WW SKU...
Just realized my tf700 changed from WW to US?? How is this even possible??
You have to use ES Explorer. ( for free in Play Store)
Just navigate to "Cache/recovery" and add a new file.
Name this file "command"
Open and edit it with ES-Explorer to "--update_package=/cache/dlpgkfile"
Click to expand...
Click to collapse
THIS worked, finally. The OP is missing the -- before update_package. I kept failing step 9 repeatedly.
If you are using ADB to create that command file it would be:
echo "--update_package=/cache/dlpkgfile" >> /cache/recovery/command
I sincerely thank the OP for the guide, but I was pulling my hair out trying to figure out what I was dong wrong... the file was missing those -- because I was copying and pasting the command from the OP.

moah909 said:
Are you using an external microSD the errors appear to be about not being able to find /sdcard
Sent from my XT894 using xda premium
Click to expand...
Click to collapse
using external SD .. tried to make a fresh format fat32 .. tried another SD .. same triangle .. i am just a littlebit unamused hmm
complete log of my last try .. my knowledge is not big enough to solve this .. and sry 4 the image, 2nd post, so not allowed to insert links ..

oh, I'm sorry for all the hair loss! Thanks for pointing it out, fixed it in the OP.
Sent from my XT894 using xda premium

moah909 said:
oh, I'm sorry for all the hair loss! Thanks for pointing it out, fixed it in the OP.
Sent from my XT894 using xda premium
Click to expand...
Click to collapse
LOL. Thanks. No problem at all. (I'm actually quite folliclely impaired already... so it was really tough to find hair to pull out of my head anyway. TLDR: I'm balding already, hence the joke.)
I was being sincere about the thank you for posting those instructions. They helped a lot... once I figured out what was missing.

cant explain it .. BUT: .. was still on .30 .. market gave me an update for "[email protected]" .. try 23. .. suddenly: .30 stock update ..
changed NOTHING .. only the update of this app ... now 15min later on JB ... root missing, but thats my fault, will come back sometimes ... so .. thanks 4 letting my cry ^^

Video
make a video showing all steps and you'll be a star

Related

non-NAND root without ADB, a photographic guide

THIS IS ONLY FOR NON-NAND, TheBiles should put one out for NAND rooting soon.
Here's a guide for people who either don't have a PC or don't want to use one.
You will need the following files:
PC36IMG.zip
Update.zip (listed below)
A rom image of your choice
put all these files on your SD card root then power off your phone.
THIS CAN WIPE YOUR DEVICE, IF YOU NEED TO BACKUP DO STEPS 1-13 HERE
1. Hold volume down and power, keep holding volume down till the white screen appears
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2. Wait for it to search for PC36IMG.zip on the sd card then hit yes when it asks if you want to update
http://www.flickr.com/photos/mrono/4694475803/
3. Wait for it to finish(it takes awhile) then press yes to reboot
http://www.flickr.com/photos/mrono/4694475829/
YOU NOW HAVE ROOT
now we will flash a custom rom
4. When the white "Evo 4g" screen appears, pull the battery
http://www.flickr.com/photos/mrono/4695109532/
5. Hold volume down and power, keep holding volume down till the white screen appears
http://www.flickr.com/photos/mrono/4695109576/
6. Press no to updating, then no to rebooting
http://www.flickr.com/photos/mrono/4694475803/
7. Select recovery and press power
http://www.flickr.com/photos/mrono/4695109576/
8. Wait for the red triangle
http://www.flickr.com/photos/mrono/4694475545/
9. Hold vol up and press power, wait for the menu, then select apply sdcard:update.zip and press power again
http://www.flickr.com/photos/mrono/4695109674/
10. Select install zip from sd card
http://www.flickr.com/photos/mrono/4695109714/
11. Select choose zip from sd card
http://www.flickr.com/photos/mrono/4695109744/
12. Select your rom of choice and hit power
http://www.flickr.com/photos/mrono/4695109770/
13. Wait for it to install
http://www.flickr.com/photos/mrono/4695109790/
14. Select -go back-
http://www.flickr.com/photos/mrono/4694475723/
15. Select reboot system now
http://www.flickr.com/photos/mrono/4694475763/
16. Enjoy your custom rom and rooted device!
http://www.flickr.com/photos/mrono/4695109864/
All the credit goes to:
toast: without him we wouldn't have root http://forum.xda-developers.com/showthread.php?t=690762
Koush: for the fake-flash recovery http://forum.xda-developers.com/showthread.php?t=699043
I'm glad you wrote this up. I performed root the exact same way. I still don't know anything about adb, sdk, shell, or whatever. But this way is truly rooting for dummies!, and totally without a PC. I also used rom manager to download my first rom that i flashed. But then downloaded a new one. I plan on using dcupdater for new updates.
This should be a sticky. Rooting for dummies! No PC required.
Sticky this for all of us root wanting fools that have no sense of adb.
This is sooo what I just posted, only you have photos of the recovery screen.
TheBiles said:
This is sooo what I just posted, only you have photos of the recovery screen.
Click to expand...
Click to collapse
Lol we should just combine them, feel free to combine mine into yours
Re: Rooting without ADB, a photographic guide
mrono said:
Lol we should just combine them, feel free to combine mine into yours
Click to expand...
Click to collapse
That would be great, and it would save me a lot of time. I will do that first thing tomorrow. Thanks!
-------------
Sent from my HTC EVO 4G using Tapatalk Pro.
Thanks for this. Helped me get past a step I got hung on for hours tearing my hair out.
Aparently my web server is down >.> that's why the images arn't appearing.
Re: Rooting without ADB, a photographic guide
If you post them in a .zip I will upload them to mine with the rest of my pics.
-------------
Sent from my HTC EVO 4G using Tapatalk Pro.
TheBiles said:
If you post them in a .zip I will upload them to mine with the rest of my pics.
-------------
Sent from my HTC EVO 4G using Tapatalk Pro.
Click to expand...
Click to collapse
Sure, here you go.
Woot, will be doing this soon.
I hope a 100% Senseless rom comes out.
Thanks for this method with all the images. But, I have been trying all night to gain root. First using Toast's version and adb, and now with your method on my sdcard. Using either method, I never get to a screen where I can choose to update, in step 2. I have the searching for PC36IMG.zip, with the blue progress bar, but it dumps me into this screen:
HBOOT
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select
FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK
HBOOT USB
I've downloaded the file at least twice, but I get the same result. I also flashed the stock RUU between trying Toast's version with adb and yours from the sdcard.
Do you have any idea where I went wrong? Also, is your update.zip Clockwork? (Just curious.) I'm not a complete beginner at this, as I have a Hero and was able to flash custom ROMs to it...
Thanks for any help you can give.
smarcin said:
Thanks for this method with all the images. But, I have been trying all night to gain root. First using Toast's version and adb, and now with your method on my sdcard. Using either method, I never get to a screen where I can choose to update, in step 2. I have the searching for PC36IMG.zip, with the blue progress bar, but it dumps me into this screen:
HBOOT
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select
FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK
HBOOT USB
I've downloaded the file at least twice, but I get the same result. I also flashed the stock RUU between trying Toast's version with adb and yours from the sdcard.
Do you have any idea where I went wrong? Also, is your update.zip Clockwork? (Just curious.) I'm not a complete beginner at this, as I have a Hero and was able to flash custom ROMs to it...
Thanks for any help you can give.
Click to expand...
Click to collapse
This is happening to me too.. Though I think it's because I'm already rooted? I did go through Toast's method and looks like I'm rooted, wish there was a way to tell. Also If I load a ROM then check ROM manager to see which rom I'm currently running, nothing is there -just blank.
Settings, About phone, Software information will tell you if it is rooted. Look at build number, should be Fresh Evo 0.2 by flipz or whatever ROM you used.
Mine says Fresh Evo 0.2 but during the root process it skips [8] TP and bypasses [9] TP, wondering if something is wrong with the root process? Also my sd card seems to have lost all my backup data and when I connect to pc it says my card has issues. Do I have a problem?
Did it, worked 100% easy.
Thanks man.
Are you supposed to be able to open (explore) the PC36IMG.ZIP file through Windows? I have downloaded it 12 times from 4 different places and the message says the file is invalid. I haven't put it on my SD yet, this is just on my PC.
Edit: Well, I tried doing the update to root with the downloaded PC36IMG.ZIP file and all I get is a non-rooted wiped clean EVO after it does the update.
Can someone please download load PC36IMG file "now" (not try a previous version) and see if it corrupt and also see if you can open already downloaded one through windows as a zip file.
Thanks....
MisterEdF said:
Are you supposed to be able to open (explore) the PC36IMG.ZIP file through Windows? I have downloaded it 12 times from 4 different places and the message says the file is invalid. I haven't put it on my SD yet, this is just on my PC.
Edit: Well, I tried doing the update to root with the downloaded PC36IMG.ZIP file and all I get is a non-rooted wiped clean EVO after it does the update.
Can someone please download load PC36IMG file "now" (not try a previous version) and see if it corrupt and also see if you can open already downloaded one through windows as a zip file.
Thanks....
Click to expand...
Click to collapse
I think that's what I have too: "a non-rooted wiped clean Evo." I never had the prompt to say yes to update or yes to reboot. I'm not a total n00b at this. I was able to successfully root and put Fresh's ROM on my Hero. I thought maybe it was adb drivers, but I can use my Evo in disk mode, and run HTC Sync. (I have no use for HTC Sync.)
I'd love to try d/ling the file, but my dsl is down. I've spent the last 2 hours troubleshooting it and arguing with Qwest. They've finally agreed it might be their problem and are coming out to fix it. I NEED root so I can us WiFi tether!
MisterEdF said:
Are you supposed to be able to open (explore) the PC36IMG.ZIP file through Windows? I have downloaded it 12 times from 4 different places and the message says the file is invalid. I haven't put it on my SD yet, this is just on my PC.
Edit: Well, I tried doing the update to root with the downloaded PC36IMG.ZIP file and all I get is a non-rooted wiped clean EVO after it does the update.
Can someone please download load PC36IMG file "now" (not try a previous version) and see if it corrupt and also see if you can open already downloaded one through windows as a zip file.
Thanks....
Click to expand...
Click to collapse
I just tried to open my pc36img.zip file off my sd card, the one that I used to root and it says that it's inva'id. I think it's because it's not really a zip file. The one your downloading is fine.
smarcin said:
I think that's what I have too: "a non-rooted wiped clean Evo." I never had the prompt to say yes to update or yes to reboot. I'm not a total n00b at this. I was able to successfully root and put Fresh's ROM on my Hero. I thought maybe it was adb drivers, but I can use my Evo in disk mode, and run HTC Sync. (I have no use for HTC Sync.)
I'd love to try d/ling the file, but my dsl is down. I've spent the last 2 hours troubleshooting it and arguing with Qwest. They've finally agreed it might be their problem and are coming out to fix it. I NEED root so I can us WiFi tether!
Click to expand...
Click to collapse
Why don't you just download the unrevoked root till you get your DAL back online.
http://m.unrevoked.com
Hey guys, I want to flash to another Rom with this method. Do I just do all the steps all over again?
Zardos66 said:
Hey guys, I want to flash to another Rom with this method. Do I just do all the steps all over again?
Click to expand...
Click to collapse
no, just get into recovery, you don't have to flash the .img file

[Program] SimpleRoot .1 ---- 3 Click Root w/ nand unlock!!

First things first...
Credits:
Mast3rpyr0 - Original creator of a simple one click root. Most the code used here is based on his work with some tweeks. [ Link ]
webs05 - For the outstanding help he has provided to those who were having issues using Simple Root!!! Thanks!
toastcfh - For root and nand unlock. [ Link ]
Koush - Recovery image [ Link ]
maejrep - For helping with the code to remove sendkeys!! Thanks alot!!
If I forgot anyone that I should have mention, let me know....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Automatic updates and create update patches with wyBuild.
After hours of trying to figure out a way to make Mast3rpyr0's batch files work correctly, I noticed it had problems sending certain commands. So I decided to use some of his batch file codes, and create a VB.NET application along with batch files. I have unrooted and rooted my personal phone multiple times trying to get this to work. I tested the app 3times!! Each time Unrooting my phone! All three times its has been successful!
What exactly does this do?
Exactly what it say, Root your EVO in 3 Steps.
How do you use it?
Make sure your phone is on USB Debug mode. (MENU > Settings > Applications > Developement > USB debugging = Checked ) Click the buttons starting from Step 1.
Why the large file size?
This includes all the .img and .zip files that are needed to root. (2 PC36IMG.zip @ ~ 170MB = 340mb) and a couple of other smaller files. I decided to add them to make things more simple and avoid having to explain where to get these files.
Youtube Example
sorry for all the video splits...not my fault, blame youtube.
Video quality might be bad, give them a few to process 720p version
Part 1-1 - http://www.youtube.com/watch?v=GAqTEAWxh7U
Part 1-2 - http://www.youtube.com/watch?v=578jDEJ6M_c
Part 2-1 - http://www.youtube.com/watch?v=I-FbYqPOrpg
Part 2-2+3 - http://www.youtube.com/watch?v=qk7lBDpSp-A
AndroidPolice.com Review + Tips
​
Download:
Megaupload - had to put this up, account suspended due to the amount of downloads =( they want my to go dedicated smh...
Official Page | Full (Download this if you never used this program before)
If you have downloaded this program before, please read this
Note: Its recommended to flash a custom ROM. Reason I say this is because for whatever reason, the eng-image doesnt allow proper SU permission!!
Requires: Dot Net Framework 4 and HTC SYNC
I would try it if I didn't fully root yesterday. But props to you guys for putting that together. Seems like a one step jailbreak. Very nice.
WOW! Great work. This will unlock NAND too? If so you might want to update your thread title....
jiqqaman said:
First things first...
FOLLOW THE DIRECTIONS!! IF IT SAYS DONT MOVE YOUR MOUSE, DONT CLICK ANYTHING, DONT TOUCH YOUR KEYBOARD... THEN DONT!!!!
The reason for this is because for some reason a batch file cant send the command
Code:
adb shell cat sdcard/flash_image > /data/flash_image
The only way I found to get around that was using Sendkeys. I know, send keys is lame, and poor programming, but its the only way that I could get this to work.
Basically, Sendkeys sends keystokes to a targeted window, as if you were typing. You might see your keyboard NumLock, Caps light blink while this is being used, which is perfectly normal. (Enjoy the light show)
Click to expand...
Click to collapse
That's because the windows shell interpreter parses the redirect as belonging to the Windows system, not the android system. So it's trying to redirect the output to c:/data/flash_image or some such nonsense. Since Windows doesn't do / for it's directory structure, but instead uses \ it gacks trying to find the directory to put it in (which would be wrong even if it worked, since it would be on your hard drive, not the phone). You can change the cat line to this:
Code:
adb shell cp /sdcard/flash_image /data/flash_image
and it should work just as well. Anytime you use a redirect in a batch script like that it's going to try and redirect to Windows. If it wasn't my day off and I wasn't so tired I might figure out a fix for that, but the code I posted above should do the trick well enough. I wasn't sure initially why people wanted to to read the file into another one in the first place, but I did it with cp when I rooted and it worked fine. I suggest testing it, and then possibly changing your program. That way you can get rid of sendkeys and people breaking root by clicking something when it's running
this is amazing. too bad noobs like myself could not wait to root and unlock nand. but the process was well worth it. great job, i hope this save someone a headache
Re: [Program] SimpleRoot .1 ---- 3 Click Root!!
smw6180 said:
That's because the windows shell interpreter parses the redirect as belonging to the Windows system, not the android system. So it's trying to redirect the output to c:/data/flash_image or some such nonsense. Since Windows doesn't do / for it's directory structure, but instead uses \ it gacks trying to find the directory to put it in (which would be wrong even if it worked, since it would be on your hard drive, not the phone). You can change the cat line to this:
Code:
adb shell cp /sdcard/flash_image /data/flash_image
and it should work just as well. Anytime you use a redirect in a batch script like that it's going to try and redirect to Windows. If it wasn't my day off and I wasn't so tired I might figure out a fix for that, but the code I posted above should do the trick well enough. I wasn't sure initially why people wanted to to read the file into another one in the first place, but I did it with cp when I rooted and it worked fine. I suggest testing it, and then possibly changing your program. That way you can get rid of sendkeys and people breaking root by clicking something when it's running
Click to expand...
Click to collapse
Thanks, I'll see how that works later on, and if it works ill just upload a zip file with the updated code. Don't like the whole sendkeys thing,...I'd like to figure out on making it work without batch files... but I no pro code lol
Sent from my HTC EVO using Tapatalk
If I am already rooted can I skip right to Unlock Nand? I did root using the toast method.
cmdauria said:
If I am already rooted can I skip right to Unlock Nand? I did root using the toast method.
Click to expand...
Click to collapse
It wont hurt to re-root just run the whole thing. make sure you backup of course
thanks OP great work I'm sure it will get even better and easier once you get rid of key presses
STICKY!!!!
would you mind just posting a zip with the main files and not the roms?
im running low on space and wouldnt mind saving 300 megs
Damn after I followed the 50 step-by-step and wish I had seen this earlier nice work might try this on my older bros in a few days
Sent from my Sprint HTC EVO 4G. via tapatalk
cmdauria said:
If I am already rooted can I skip right to Unlock Nand? I did root using the toast method.
Click to expand...
Click to collapse
Yes, but you must run on the pushfiles.bat file before you goto step 2.
CYBERxNUKE said:
would you mind just posting a zip with the main files and not the roms?
im running low on space and wouldnt mind saving 300 megs
Click to expand...
Click to collapse
http://www.megaupload.com/?d=N6GV5NNP - no .img or .zip files
make sure you have the first PC36IMG.zip from the first root tutorial and the 2nd PC36IMG.zip from the nand unlock rename it eng-PC36IMG.zip or else you'll break it =(
Hi,
If I do this method will I be able to load custom Roms following these steps? I found these on another site and I am a noob so this one step thing would be great for me to get my feet wet...but the whole reason I would root is so that I could try another ROM...
Here are the steps I found...earlier it said I needed adb and sdk tools so I'm not sure if below will work if I don't have that installed on my computer.
Choose a ROM you want to try. Download it and save it to your computer (do NOT extract it, leave it as a .zip)
2. Plug the phone in via USB cable and mount the sd card so we can transfer files to it.
3. Copy the ROM .zip file and save it to the root of the sd card (NOT in any folders just on the sd card itself). Once it is done copying, unplug the phone from the usb cable.
4. Turn off the phone, then turn it back on by holding down Volume Down and Power until the white bootloader screen comes up (if it finds the PC36IMG.zip on your sd because you didn’t delete it, just say NO when it asks you if you want to update). Now using the volume buttons select Fastboot, then select Recovery and wait for the phone to boot into recovery mode.
5. Scroll to Wipe Data, select wipe data/factory reset and then select wipe dalvik cache.
6. Now scroll to Apply .zip from sd card and select the ROM .zip file we saved to the sdcard and wait for it to finish flashing. Once it is done, hit reboot and you are all set! Enjoy!
OP theres an updates restore image much better options from armon .02 works for people who have bad sectors ALLOT of us have
but 01 is for those who dont try that first
http://forum.xda-developers.com/showthread.php?t=705026
ken987 said:
Hi,
If I do this method will I be able to load custom Roms following these steps? I found these on another site and I am a noob so this one step thing would be great for me to get my feet wet...but the whole reason I would root is so that I could try another ROM...
Here are the steps I found...earlier it said I needed adb and sdk tools so I'm not sure if below will work if I don't have that installed on my computer.
Choose a ROM you want to try. Download it and save it to your computer (do NOT extract it, leave it as a .zip)
2. Plug the phone in via USB cable and mount the sd card so we can transfer files to it.
3. Copy the ROM .zip file and save it to the root of the sd card (NOT in any folders just on the sd card itself). Once it is done copying, unplug the phone from the usb cable.
4. Turn off the phone, then turn it back on by holding down Volume Down and Power until the white bootloader screen comes up (if it finds the PC36IMG.zip on your sd because you didn’t delete it, just say NO when it asks you if you want to update). Now using the volume buttons select Fastboot, then select Recovery and wait for the phone to boot into recovery mode.
5. Scroll to Wipe Data, select wipe data/factory reset and then select wipe dalvik cache.
6. Now scroll to Apply .zip from sd card and select the ROM .zip file we saved to the sdcard and wait for it to finish flashing. Once it is done, hit reboot and you are all set! Enjoy!
Click to expand...
Click to collapse
1. The program includes adb, just download, unzip and run Simple Root.exe
2.Yes you will be able to install custom roms after you have completed the all the steps.
3. Those are not complete steps, but its sorta on the right track... have you done the first part of root?
great job on making this easy guys.... To bad I couldnt wait longer than a week to root.
jiqqaman said:
1. The program includes adb, just download, unzip and run Simple Root.exe
2.Yes you will be able to install custom roms after you have completed the all the steps.
3. Those are not complete steps, but its sorta on the right track... have you done the first part of root?
Click to expand...
Click to collapse
Thanks for the quick reply. No, I am a new EVO owner and this is my first android phone. I was an iPhone user but I have come over to the Android side. No regrets. I have basically a new EVO with the OTA update installed. So my goal would be to run your one click method and then learn how to load roms. I also read that people have some kind of rom loader on their phone that sounded pretty easy so I need to do more searching on the forums here so I can learn.
Ken
This would have saved me 3 hours....
Thanks dude though this seems awesome.
Videos are titled "Hero 4g" btw.
Part 1 worked for me but part 2 doesn't. When I click yes on part 2 I get a screen that says "Unhandled exceptin has occured" and it gives me a option to continue or quit and I click continue and it closes out.
Does this method work if I already have the .6 stock rom on my device?

[No-Brick Method]New All-in-One D2G recovery & Root CD for .629 update(EzSbf method)

[No-Brick Method]New All-in-One D2G recovery & Root CD for .629 update(EzSbf method)
I have put together a modified version of 1KDS EzSbf CD's, combining the necessary tools to unbrick and root devices that have taken the .629 update.
I have tested it several times on my own phone, and it has worked well.
As with everything, I have done my best on this, but can provide no guarantees that it will work for you. It worked well for me, and others have used all of these tools, but like everything else here, use this at your own risk.
The CD is a combination of the tools from the following sites.
EzSbf from http://www.droidforums.net/forum/droid-2-global-hacks/170060-tool-ezsbf-d2g.html
phifc's preinstall method from http://rootzwiki.com/topic/29930-new-root-method-for-stock-234-621622-found-droid2-r2d2/
Suggested reading before starting:
http://www.droidforums.net/forum/droid-2-global-hacks/170060-tool-ezsbf-d2g.html
http://rootzwiki.com/topic/29930-new-root-method-for-stock-234-621622-found-droid2-r2d2/
Instructions: (all instructions are on the CD prompts)
This is ONLY for the Droid 2 Global, and more specifically only for the Droid 2 Global that has already had the 4.5.629 OTA update. If your phone has not had the OTA update to .629, I recommend you do not use this.
If using a CD, burn ISO to disc, and boot from that. It will come to a prompt with instructions.
If using USB stick.
Use Unetbootin (http://unetbootin.sourceforge.net/) to install ISO to USB drive, and when booting choose the Slitaz option.
If you need to flash the SBF, you will need to have the phone in bootloader mode, if you need to root, you will need to start the process with the phone turned on and usb debugging enabled. You will then need to put the phone in bootloader mode when prompted.
Credits:
I did not develop any of the software used, I just compiled it into one location.
Credit should go to:
1KDS for developing the EzSbf method, and for helping me as I was putting the CD together
phifc and the method he posted at
http://rootzwiki.com/topic/29930-new-root-method-for-stock-234-621622-found-droid2-r2d2/
djrbliss, and the others who developed the symlink method
Skrilax_CZ, and his Motorola Android Firmware (De)packer
Here is a link to download the ISO if you would like to try it. I don't expect anyone to have troubles with it, but as with everything, I have done my best on this, but can provide no guarantees that it will work for you. It worked well for me, and others have used all of these tools, but like everything else here, use this at your own risk.
Updated CD:
Thanks to phifc and the method he posted at
http://rootzwiki.com/topic/29930-new-root-method-for-stock-234-621622-found-droid2-r2d2/
we have an improved method available to root the D2G, and no longer need to brick our phones (presuming all goes well) in order to root them. Since there is now a direct rooting method of .629 available, I put it together with an EzSbf style CD of the full .629 SBF.
One item of note with this CD, it does require at least 1GB of RAM in order to work properly. Also, if you only have 1GB of memory, and you need to both SBF and root your phone, it will be necessary to reboot the computer after flashing the .629 SBF. If you are unsure of the amount of RAM that you have, go ahead and reboot to be on the safe side.
Also, I noticed that I neglected to put instructions for putting your phone in bootloader in the SBF Step. To put your D2G in bootloader mode, power down and power on while either holding both volume buttons, or the up arrow on the keyboard.
SBF and Root CD
The CD is available at
https://rapidshare.com/files/2650843793/D2G_4.5.629_SBF-and-RootCD.iso
and the MD5 is
579d7d5095fc2560205033456db150a2
Root Only Multi-Device CD
There is also a root only CD available, that covers multiple devices (Droid 2, Droid 2 Global, Droid X, and Droid X2).
It is a little over 50 Meg in size, so if all you want to do is root your phone, it might be a handier option.
the link for it is
http://www.mediafire.com/?mim304k214kl41h
and the md5 is
7baee9c34f6ef7ad0b4fa219ae387c68
Additional Mirror:
Rapidshare has had some trouble recently, but thanks to themib/sd_shadow for putting up a mirror that has most of these CD images as well. They can be found at
https://docs.google.com/document/d/1-Oj1a1wNZKhZMPUqU_6KzzYzQJ2RKzvvumTx-41f3h4/edit#
If anyone finds a CD helpful, and would like to upload it to a mirror, they are welcome to. If they give me the link to a mirror, I will be glad to add it to this post.
Older items still working but obsolete
Hopefully these have served their purpose, but should now be superseded.
I uploaded it to Rapidshare at
https://rapidshare.com/files/1957071604/D2G_629Recovery-and-Root_CD-With_OTA-Update.iso
and the md5 checksum for the iso is
45dff90da46bd30c33f005c853e058d1 (Updated CD including the OTA Update
Here is also a clean Nandroid backup of rooted .629.
This would be useful for the band unlockers (those want to use this phone on AT&T or T-Mobile), or for those that would prefer to restore a backup instead of taking the OTA update. Once you have rooted the .608, you bootstrap recovery, and restore this nandroid backup.
You will need to extract it, and place the folder in the sdcard\clockworkmod\backup folder. Hope this is helpful for someone.
The link to download the file is
https://rapidshare.com/files/782850895/2012-06-10_Rooted_629-Nandroid.7z
and the MD5 checksum is
c43101a5b01d7c69887a0668be24e5c9
more details
updated many times see change log
created by phifc modified by bhigham
2 options mirror links posted Magic MD5 Root 2.3.4 for D2, R2D2, D2G, DX and 2.3.5 for DX2 - Google Docs
Multi-Device Root (54mb)
D2G_4.5.629_SBF-and-RootCD.iso (219MB)
How this works
Originally Posted by phifc
There's an exploit in loadpreinstall.sh. It compares md5 sum files of preinstalled apps and if they're different, copies the md5 to the local cache. The preinstall just has an empty file in app/ so it will parse the md5 for it. Instead of an md5 sum, it contains a local.prop that allows adb root shell. So the system thinks it's copying the md5sum to the cache when it bounces off the symlink and overwrites the /data/local.prop, giving adb root on next reboot
Click to expand...
Click to collapse
what is ezSBF?
original [TOOL] ezSBF (not for 2.3.4)
1KDS said:
Don't let the word Linux scare you, this is just a cd you burn, nothing installs to your pc. Once you burn this CD you are ready to SBF flash anywhere you have a computer, no net connection needed to download any files.
This is an .iso file. It is a complete Linux operating system that you will download, burn to CD (or USB) then boot your pc from CD or USB, this allows your pc to reboot into a different operating system.
Click to expand...
Click to collapse
1KDS said:
Instructions (Mac):
Download .iso
Use Disk Utility (built in) to burn iso file to a CD (instructions)
Shut computer down
Hold c key, push power and hold c until you see the Linux OS start
Hit enter at the yellow "boot baby... boot" screen
You will see yellow dots for 3-5 minutes then the script will start
Instructions (Windows):
Download .iso
Burn iso image to a disk (Instructions, Windows 7 - Vista and XP) or (Load to a USB flash drive)
Reboot PC
Hit F12 (sometimes F8 or esc) during boot to go to boot menu (possibly google search how to boot your specific pc from CDROM)
Select boot from CDROM (or USB if you used a flash drive)
Hit enter at the yellow "boot baby... boot" screen
You will see yellow dots for 3-5 minutes then the script will start
Live USB Instructions (Windows):
(Instructions from pendrivelinux.com)(thanks)
Download UNetBootin for Windows
Download your favorite Linux ISO
Double click the Unetbootin Executable to start the program
(1) Click the Diskimage radio box
(2) browse to select your ISO
(3) Set your target USB drive
(4) click OK to start the creation
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(5) After the USB drive is done select reboot.
(6) During boot enter the boot menu and change USB to boot first, save and reboot.
(7) When booting from UNetbootin select SliTaz
________________________________________________
You will now be in the script and ready to flash.
Click to expand...
Click to collapse
select D2G for multi device root cd or /select root for the SBF-and-Root CD
don't use numbers on right side of you keyboard, just use the ones above qwerty
turn phone on, connect to pc with usb cable
on phone check usb debugging (settings/apps/development)
on phone select charge only usb mode
on pc press continue
program will use adb to push
Code:
data/local.prop /data/preinstall_md5/magic.md5
program will prompt you to
manually reboot phone to bootloader
program will flash repacked sbf (less than 50mb)
program will reboot twice, very important (reboot just replaces the local.prop, but the old local.prop is still in memory, till second reboot)
adb pushes su,superuser, and busybox
program will reboot to recovery,
manually press both volume buttons when you see !, triangle, & android andy
manually select wipe cache
manually select reboot
rooted
error info
when running program you may see these errors
rm failed for /data/preinstall_md5/magic.md5 no such file or directory
no root.img.gz no such file or directory
rm failed for /data/preinstall_md5/magic.md5 read only file system
that is fine, it will still work
by bhigham -One item of note with this CD, it does require at least 1GB of RAM in order to work properly. Also, if you only have 1GB of memory, and you need to both SBF and root your phone, it will be necessary to reboot the computer after flashing the .629 SBF. If you are unsure of the amount of RAM that you have, go ahead and reboot to be on the safe side.
Also, I noticed that I neglected to put instructions for putting your phone in bootloader in the SBF Step. To put your D2G in bootloader mode, power down and power on while either holding both volume buttons, or the up arrow on the keyboard.
Click to expand...
Click to collapse
if you plan on creating nandroid backups or flashing roms read
[HOW TO] Install/Use Droid 2 Bootstrap
Band unlock Droid 2 Global with 629 instructions
original D2 thread New root method for stock 2.3.4 (621/622) found (Droid2, R2D2) - Droid 2 / R2D2 / Milestone 2 / Droid 2 Global - RootzWiki
30 Aug 2012 added links
02 Oct 2012 added mac info
09 Dec 2012 major rewrite
Click to expand...
Click to collapse
If anyone has been able to try this out, please let me know how it goes, so I can update the post. Once others have verified it works well for them, I will post more complete and detailed instructions for those who don't have experience.
I also have a clean .629 Nandroid backup available for Band Unlockers, who would like to cut down on the number of steps necessary to get their phones on AT&T or T-Mobile, and will post detailed instructions for that as well.
i try this but wifi can't connect ..just at obtaining ip adress only...
please help...
Sent from my DROID2 GLOBAL using xda premium
WiFi won't work until you take the OTA update.
Make sure to protect root using Voodoo OTA rootkeeper first, rootkeeper should already be installed and in your list of applications.
CONFIRMED, I have .629 ROOTED, and working WIFI, GREAT job , many thanks.
but i feel the the WIFI is become weak in catching the signal, in addition to the phone signal now become -2 all the day,
and how can I remove the Verzion app, as i use the phone outside USA
---------- Post added at 01:05 PM ---------- Previous post was at 01:04 PM ----------
sd_shadow said:
nice work, hope it works well for other D2Gs
Click to expand...
Click to collapse
Did u find any method to enable the GSM on MIUI or CM7 ???
Glad it worked for you, as far as removing apps, I haven't really done any of that, I have used Titanium backup to freeze the ones I don't want running.
Does putting the old .608 on (step 1) wipe the phone? My only root experience was a one click HTC. The only reason I want to root the d2g is to do a backup of app data to move to a droid4, because after that I will be putting the d2 in a drawer.
Thanks for the info.
flashing a SBF, doesn't wipe data, just flashes the system
but normally wiping data in android recovery, is recommended to prevent bootloops
bhigham said:
WiFi won't work until you take the OTA update.
Make sure to protect root using Voodoo OTA rootkeeper first, rootkeeper should already be installed and in your list of applications.
Click to expand...
Click to collapse
i already install dude..but nothing happen..
you may have to wipe data again
Thanks OP! The CD worked great, and Murphy must have been on vacation today because I was able to get through it without clearing data, which meant I could back up the phone with TBP. :good:
Okay So I Tryed Once Already & The Disk Leads Me To This:
Disk Err 01, AX = 4200, Drive A0
Im Running A W7 64Bit Laptop, Any Help?
did you verify the md5 checksum before burning iso to cd?
Sent from my DROID2 using xda app-developers app
sd_shadow said:
did you verify the md5 checksum before burning iso to cd?
Sent from my DROID2 using xda app-developers app
Click to expand...
Click to collapse
Please Explain This, I Don't Know What Your Talking About.
How long do you have to hold down X key + power button to see recovery triangle screen?
When I do that, I immediately see the bootloader Err:A5,70,70,00,1F screen?
I've held it down for 30sec and doesn't change?
UPDATE:
Even though I didn't get the recovery triangle, I did the .629 repack update anyway on the bootloader error screen and it worked!
Thanks for this awesome post!
fyi: to boot to android recovery, start with phone power down
then x and power
it's in the wiki
Sent from my MB870 using xda premium
wiping data is only recommended, not always required, as it prevents bootlooping
Sent from my MB870 using xda premium
Got It.
Thanks So Much! ;3
8o8OhBby said:
Got It.
Thanks So Much! ;3
Click to expand...
Click to collapse
sorry that i didn't get back to you about md5
did you figure it out? it's in my links page

[Q] Nexus 7 Bricked No OS stuck on Google screen

Good Afternoon
The other day I was having an issue with my Nexus 7 so I inadvertently went into TWRP on my device and wiped everything including the OS so when it starts up I just get the Google screen with the unlocked padlock on it.
I have tried several things so far
I have downloaded Nexus root Toolkit 1.7.3 and several stock images, I choose the option to flash stock + Unroot but it doesn't seem to do anything I just get the following screen as per attached screenshot, from looking around it looks like it should run something before I get that screen but nothing happens.
I really don't know where to go from here I have tried so many different things but just don't seem to be getting anywhere, any help would be soooooooo much appreciated, I can’t even send it back as I have unlocked it and I believe that voids the warranty.
I have managed to get into the TWRP section by choosing the custom recovery in the advanced section menu but when it loads up it asks me for a password on my Nexus and the password I had it keeps on saying password failed.
Is there anything I can do, I have literally spent hours searching around and I cant seem to get anything to work, as I say I have inadvertently wiped everything!!!!!!:crying:
davechampion said:
Good Afternoon
The other day I was having an issue with my Nexus 7 so I inadvertently went into TWRP on my device and wiped everything including the OS so when it starts up I just get the Google screen with the unlocked padlock on it.
I have tried several things so far
I have downloaded Nexus root Toolkit 1.7.3 and several stock images, I choose the option to flash stock + Unroot but it doesn't seem to do anything I just get the following screen as per attached screenshot, from looking around it looks like it should run something before I get that screen but nothing happens.
I really don't know where to go from here I have tried so many different things but just don't seem to be getting anywhere, any help would be soooooooo much appreciated, I can’t even send it back as I have unlocked it and I believe that voids the warranty.
I have managed to get into the TWRP section by choosing the custom recovery in the advanced section menu but when it loads up it asks me for a password on my Nexus and the password I had it keeps on saying password failed.
Is there anything I can do, I have literally spent hours searching around and I cant seem to get anything to work, as I say I have inadvertently wiped everything!!!!!!:crying:
Click to expand...
Click to collapse
Try reflashing TWRP first, then reply if you still have the password problem. We can work from there. Remember, you have a N7 - nexus devices are practically unbrickable (if you know what I mean)
Nexus 7 2013
Thanks for that will give it a try later.
I have also come across the website below
forums.androidcentral.com/google-nexus-7-2012-rooting-roms-hacks/191477-guide-nexus-7-factory-image-restore.
It gives a guide on how to reinstall the stock software, the only thing that I can see they have that I dont are a few files and I dont know where you get them from.
the files in the guide are
Bootloader-Grouper 3.34
Flash-all.sh
Flash-Base.sh
The image file I am fine with as I downloaded that from the site below.
developers.google.com/android/nexus/images
sorry I dont have enough privaleges to include link have to paste it manually
Nexus 7 2013
Also in regards to you last comment about TWRP
could you give step by step instructions on how to reinstall it, I am just paranoid that I may do something wrong again, I cant activate usb debugging so would need to do it via the bootlader and Command prompt ideally.
Nexus 7 2013 Re flash TWRP
Not to worry about steps I have managed to find some that will do the job
theunlockr.com/2013/03/25/how-to-install-twrp-recovery-on-the-asus-nexus-7/
davechampion said:
Thanks for that will give it a try later.
I have also come across the website below
forums.androidcentral.com/google-nexus-7-2012-rooting-roms-hacks/191477-guide-nexus-7-factory-image-restore.
It gives a guide on how to reinstall the stock software, the only thing that I can see they have that I dont are a few files and I dont know where you get them from.
the files in the guide are
Bootloader-Grouper 3.34
Flash-all.sh
Flash-Base.sh
The image file I am fine with as I downloaded that from the site below.
developers.google.com/android/nexus/images
sorry I dont have enough privaleges to include link have to paste it manually
Click to expand...
Click to collapse
Have you used 7z to unpack the files? Google puts all the files within an archive which is within another archive. In case you aren't able to successfully follow your guide, let me know and I will post steps. And btw, using CMD is actually quite easy once you get used to it... You just need to put in the effort! :good:
[GUIDE] How to install/reinstall/flash stock Nexus 7 Image from Google
I just saw your other thread mate! Seems like you're really worried about your device. And so I thought I'll give you step by step instructions;
1) Install, then open and navigate 7-zip to the location where you have the factory image file downloaded from google with the ".tgz" extension.
2) Unpack the .tgz file by selecting it and clicking extract (with the big blue negative sign).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3) Now, navigate to the extracted folder, you will see another file with the extension ".tar"
4) Repeat step 2 for the ".tar" file.
5) Now open this folder using windows. You should see the following files in your directory;
6) From here, you can either follow the instructions on the webpage you have or follow these instruction (using CMD and fastboot);
* Remember, after doing this you will not have any files/setting left on your N7.
1) Boot your N7 into bootloader.
2) Open cmd.exe and enter the following commands;
3) cd "put here without quatation marks, the directory of where the .img files are" (the last pic above)
4) fastboot devices (note: after entering this command your device should be displayed below)
5) fastboot erase boot
6) fastboot erase system
7) fastboot erase recovery
Perform steps 8 & 9 only if you have the 3G version of the N7:
8) fastboot erase radio
9) fastboot flash radio "put here without the quotation marks, the FULL name of a file that will look similar to this: radio-razor-m9615a-cefwmazm-2.0.1700.84.img"
10) fastboot update -w image-razor-jss15q.zip
11) fastboot reboot
Remember, because you have freshly flashed your N7, it will take little longer than usual to boot up.
​
Thank You!!!!!!!!!!
Thank you so much you are a LEGEND - I am all up and running again, just a quick question I re flashed the standard stock file which was listed as JSS15J (it wasn’t on the official factory image website) but my Nexus root toolkit seems to be playing ball after a re install, can I flash a later version over what I have without causing issues as I assume they have bug fixes.
I am unable to do an OTA update as I am in an unlocked state.
I have seen online that you can use the following code in CMD to flash newer factory images without wiping data, Is this correct?
here is the code they suggest to use
Code:
fastboot update <Filename>.zip
I suppose you could back up all data first and then re flash.
Again a massive thank you for all you help:victory:
[GUIDE] Reinstall/Update Android without loosing your Userdata (media Directory)
davechampion said:
Thank you so much you are a LEGEND - I am all up and running again, just a quick question I re flashed the standard stock file which was listed as JSS15J (it wasn’t on the official factory image website) but my Nexus root toolkit seems to be playing ball after a re install, can I flash a later version over what I have without causing issues as I assume they have bug fixes.
I am unable to do an OTA update as I am in an unlocked state.
I have seen online that you can use the following code in CMD to flash newer factory images without wiping data, Is this correct?
here is the code they suggest to use
Code:
fastboot update <Filename>.zip
I suppose you could back up all data first and then re flash.
Again a massive thank you for all you help:victory:
Click to expand...
Click to collapse
I'm glad to be of assistance. If you want to update your rom without loosing your data, I recommend you follow these steps (however, there is a catch: read the second last paragraph);
1) Boot into TWRP and wipe everything except "Internal Storage".
Reboot into bootloader and erase the following using CMD:
2) fastboot erase system
3) fastboot erase boot
4) Now unpack the <filename>.zip file. You will find that there are a multitude of <filename>.img files in there.
Flash two of the files named system.img and boot.img (this contains the Kernel) using CMD (remember CMD must be open in the folder containing these files):
2) fastboot flash system system.img
3) fastboot flash boot boot.img
And the other file (again is if you have the mobile version of the N7), is to flash the radio as given in my previous instructions (remember to erase radio first before flashing it).​
When you're done, you will have updated your N7 without losing your data (i.e. the files you see when you plug your N7 to the computer). However, following this method, you will not retain any Apps or settings (remember: Backing up apps and restoring them to a different ROM is a BAD idea). I have to say also that given you cannot use OTA, I am not aware of any other method that will keep your apps and settings untouched. I may be wrong, and if I am please do let me know. :good:
Finally as a personal note, I wouldn't flash anything to a Nexus but the latest stock files provided from Google until they stop providing updates to that particular device.
..
..

Ran "Fix Permissions" in TWRP - Everything is missing

I can see my SDcard in Recovery and I can copy stuff off via MTP from recovery...
But after I ran Fix Permissions I rebooted. The system hung on the boot animation so I force power off.
I figured the permissions got screwed up for some reason so I decided to just reflash the system.img from fastboot.
So, I did that and rebooted.
On boot it didn't hang but it acted like I was setting up a brand new phone. I finally got to the desktop and while all my apps are installed still, everything is missing. I can't see anything on the sdcard and stuff seems generally screwed up. If I go in to the settings and look at storage it still showes I have 20-something gb's used up.
Ugh... I don't know what to do... sort of panic'ing right now.
Anyone got any ideas?
edit: something is royally hosed up. Even if I boot up in and go to es file explorer and try and create a new folder on my new "blank" sdcard space it gives a failed to create folder error. I think the fix permissions option royally screwed things up. Not sure if there is any coming back from this one
Read the /sdcard sticky in general
Thanks rootSU.
Yeah, something is definitely funky between current recoveries and Lollipop.
What I found out last night:
-I cut my losses and decided to hard wipe everything. I was able to DOWNLOAD files off my phone from TWRP 2.8.1.0
-I wiped, reflashed, got the half storage issue, flashed stock recovery, factory reset, all better
-Booted Lollipop, signed in, it autoinstalled my ~130 apps (this took a long time)
-I still had all my "sdcard" files I'd downloaded. My phone wasn't recognizing in windows mtp while booted in Lollipop so I decided to copy files BACK over in TWRP
-Copied over my 16gb worth of files in TWRP (this took a very long time). Once copied over it looked good in recovery and windows mtp
-Rebooted back in to Lollipop
-All of the files I had copied over in Recovery to my phone were unreadable. Folders were showing up as "?" icons in ES File Explorer. So, all that time I'd spent copying files over from recovery was ****.
-Went back to recovery, could see files again in TWRP. Since Lollipop couldn't read them, I decided I had to just delete them from recovery and just copy them over WIFI
-Deleted in recovery, booted back to Lollipop, copied over via wifi (took >2 hours to copy over wifi)
So... in summary, TWRP + Lollipop are definitely NOT playing nice together.
It was DEFINITELY the "Fix Permission" function that totally screwed me.
And the kicker...
I was running it because on every boot I'd see the "Android is Upgrading" message flash up for a couple seconds. I googled it and someone had recommended the fix permission function.
And it's still doing it now. I now believe it is caused by the current root method from chainfire and will have to live with it until it is fixed I guess.
Sigh.... what an incredibly long night.
And just discovered that the current TWRP folder on my phone is in this messed up state.
TWRP created this folder and it can only be viewed in recovery.
Even a root shell can't get in to it from ADB in Lollipop:
Code:
[email protected]:/sdcard # cd TWRP
cd TWRP
tmp-mksh: cd: /sdcard/TWRP: Permission denied
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yeah, I also have problems. Due to habit, I used "Fix Permissions" in TWRP - caused bootloop. Luckily i had just made a TWRP Backup, so I wiped the phone and restore it - worked fine again.
Guess I have to stay away from the feature until a fix.
I rooted my n5 lollipop.... But some rooted apps fail to get root access...like es file manager (root exp)...xmodgames...etc
In es it says failed test...and xmod shows device is not rooted
Sent from my Nexus 5 using XDA Free mobile app
Redux90 said:
Yeah, I also have problems. Due to habit, I used "Fix Permissions" in TWRP - caused bootloop. Luckily i had just made a TWRP Backup, so I wiped the phone and restore it - worked fine again.
Guess I have to stay away from the feature until a fix.
Click to expand...
Click to collapse
Yup, something is broken. I found out the hard way
myliferockkss said:
I rooted my n5 lollipop.... But some rooted apps fail to get root access...like es file manager (root exp)...xmodgames...etc
In es it says failed test...and xmod shows device is not rooted
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
This is completely unrelated to the topic of this thread. It's a known issue. Apps need to update how they're calling su.
GldRush98 said:
Yup, something is broken. I found out the hard way
This is completely unrelated to the topic of this thread. It's a known issue. Apps need to update how they're calling su.
Click to expand...
Click to collapse
Okay sorry boss *noob here*
Sent from my Nexus 5 using XDA Free mobile app
I too am in the same boat, I was able to restore to a previous backup but there are issues with some apps and my storage is messed up.
GldRush98 - I was a bit confused by your post, may you please clarify
I am thinking of copying my files over to me desktop via MTP in windows. Wiping and re-flashing. Then, I plan on copying over the files - Is this what gave you issues? or was it just the TWRP folder.
or would this idea work: Wipe, re-flash then restore a backup (before i fixed permissions)?
Thank you for your input
manny.m said:
I too am in the same boat, I was able to restore to a previous backup but there are issues with some apps and my storage is messed up.
GldRush98 - I was a bit confused by your post, may you please clarify
I am thinking of copying my files over to me desktop via MTP in windows. Wiping and re-flashing. Then, I plan on copying over the files - Is this what gave you issues? or was it just the TWRP folder.
or would this idea work: Wipe, re-flash then restore a backup (before i fixed permissions)?
Thank you for your input
Click to expand...
Click to collapse
If you copy files back in android it should be fine. Don't use adb or TWRP MTP. See my first post
Thank you for the quick response! I have been away from these forums for a while now and I'm not able to located the said sticky under General. One more question, besides abd or TWRP MTP what other options would I have?
Thanks again!!
rootSU said:
If you copy files back in android it should be fine. Don't use adb or TWRP MTP. See my first post
Click to expand...
Click to collapse
Yup, this is correct.
In my haste I totally misread rootSU's post. I got all my stuff out with Windows MTP, flashed the factory images and now I'm good!
Thanks again!
Same issue on nexus4.
I wasn't able to create a file/folder on the phone.
Tried fix permission and bootloop happened.
I don't want to re-wipe everything, maybe a only rom flash from twrp will help me?
mcgyver83 said:
Same issue on nexus4.
I wasn't able to create a file/folder on the phone.
Tried fix permission and bootloop happened.
I don't want to re-wipe everything, maybe a only rom flash from twrp will help me?
Click to expand...
Click to collapse
You can try the restorecon command from a terminal if you can get back in to Android.
Code:
su
restorecon -FR /data/media/0
reboot
I've seen others post that it is a potential fix.
Thank you man,I flashaed again the stock rom with data wipe.
I lost all my files but now all is working.
Many thanks
Hi guys, I have the same problem. Is there a solution to fix it, with full wipe? I can use just Odin because I can't get anywhere in the phone. I'm now trying stock room so hopefully it will work. If someone know the correct way to get working phone again let me know.
Thanks
Hello Everyone,
I fell victim to this issue and am a total noob when it comes to this. I was actually trying to remove the root and flash back to the stock software and accidentally ran the fix permissions expecting it to fix an issue that was arising. I have a ROM to restore but TWRP wont pick it up and I cannot seem to locate the proper directory folder. I already backed up all my data previously to starting and am ok with wiping everything but pretty much at this point I am at a loss.
If someone could help me out my email is [email protected]
I know it too late for you, but that is one feature I stay well away from. Never use it if you are reading this. Took me days to sort my phone out.

Categories

Resources