This is my situation...
I recently rooted for my Wildfire using Unrevoked3, have no installed any custom roms whatsoever.
To install the new firmware (Update 1.25.405.1) i followed a guide which involved renaming it to update.zip and used clockmodrecovery to install update.zip from the SD card.
Update was successful however i lost the root (as expected)
I tried to rerun unrevoked 3 to reroot but all it does is reboot my device and it remains unrooted.
On the HBOOT recovery menu i now get a red triangle with an exclamation mark against a black background. i do power + volume up and it says android system recovery and in yellow 'E: Cant open/cache/recovery command'
How can i reroot my phone so i can use apps such as titanium backup once again? (and yes ive tried to install busybox and i get a failed error message)
I have looked around the forums and made lots of searches some of which address this question but i am yet to find a solution which works... Im sorry if this question is redundant as i am new to this sorta thing.
Thanks.
Did you follow this guide?
Update: What I did to succesfully install the update on a rooted phone
- unplug phone from USB, let it download update (it's about 13 Mb in size)
- phone will ask to reboot -> update will fail, you will be dumped in clockworkmod
- As always, do a Nandroid backup before doing anything that might possibly render your phone unusable.
- Select update from zip/sdcard (or similar), navigate to zip in downloads folder
- the update process will start
- reboot (this can be a longer boot than usual, took 10 minutes on my phone)
- phone will notify you that the update has succeeded! If you've upgraded from your stock ROM (like I did), the phone info screen should look similar to that in the attached image.
- (reflash needed for root)
It doesn't say to rename the file though.
I'm going to do this now (im guessing youre on TM too?)
thanks for the info, i'm just about to do the same thing, after trying [ROM][04/10] WildPuzzleROM v8.0.5; until i realised there are still problems, got scared and restroed nandroid backup Couldn't get marketplace to load?
when phone reboots after downloading the update, i guess its supposed to be installed by the recovery program, but i have clockworkmod, I tried apply sdcard:update; get error back with failed to open update.zip and sig veri failed.
Not sure what to do? Will try booting normally, checking sd theres a file called 'OTA_Buzz_TMO_UK_1.25.110.1_R-1.14.110.1_R_release31o90ome6fwgje76.zip' on the sd card under download folder. will try renaming to update.zip and placing in \sdcard root folder
otherwise i'm thinking rom manager to install, but mobilism is down it seems and can't get hold of it
EDIT: Just rename the update put it in the \sdroot. Boot into recovery and install update.zip. works fine, takes ages, very scarey process.
Will try going back to puzzle when i have more time! Lets hope 1.25 don't crash as frequently!
Yes, i did follow all those instructions and it still didnt work. However i have managed to reroot my wildfire haha so problem is resolved. It was a stupid problem, after i rooted the first time, i reinstalled htc sync to sync some stuff but forgot to uninstall. After uninstalling it again i was able to reroot.
Sorry guys... very silly mistake by me.
Just took the 6.3 OTA for my kindle thought I would share the steps.
1. Installed voodoo OTA rootkeeper protected root and temporarily unrooted to get the update within about 8 mins my kindle auto rebooted into twrp unpacked the update and installed it stayed at the boot animation for about 5 mins then started. 2. Restored root with rootkeeper and superuser it said succesful. 3. Used rootcheck pro to see if I was still rooted and busybox installed no go was unrooted and no presence of busy box ,wasnt to worried because I easily restored root to my daughters kindle previous to this. 4. Used KFU to check to see if I still had adb status all was good there. 6. Checked command prompt for attached device nothing so I ran the driver bat. file in KFU and I was just like so many others who`s kindle was no longer recognized by my computer whoops now I was worried because the only driver that was in the list was adb composite device. 7. So I rolled my computer back with system restore which brought back the full list of drivers. 8. checked KFU no adb status checked command nothing then realized I hadn`t plugged my kindle back in after the restore lol duh checked KFU adb good checked command prompt with the correct commands for connected devices all good. 9. Rooted in just a couple mins installed fff and twrp again good to go wheww!!!! Ok some of this was operator error but overall it went good. One interesting thing I would like to point out is installing the driver from KFU borked all my other drivers I would highly not recommend doing what I did and I was lucky that it was an easy fix Lots of others are having driver install issues probably did just what I did or close. Install your drivers manually avoid trying to do it through KFU it will save you a great deal of stress good luck hope my mistake helps you avoid one
Feel free to post questions I'll answer them if I can
I was using my N73G at home this evening and it spontaneously rebooted to the Google splash screen... and stayed there for well over 5 minutes. I tried long pressing power to reboot again, and it went back to the same screen.
TWRP is installed, and I am able to get into that. I tried wiping cache and dalvik, and it booted straight back to the splash screen again, solid for 3 minutes before I went back into TWRP. In the file manager my files all appear to be safe and sound. I am currently running a nandroid backup before I futz with it any further. TWRP has not given me any errors over the course of the backup.
I should note that I have had some trouble connecting to TWRP over ADB although I can use ADB when booted into the OS. So if I need to go fishing for files over USB, I hope I won't come up empty. If necessary I could try flashing CWM recovery instead, as I may be able to get my files more easily that way.
Anyway, ideas are welcome. I was running a bake of the Modaco custom ROM, and the zip for that ROM is still on the device, so I was thinking I might try reflashing that. But first I should try and get my nandroid off the slab.
As fortune would have it, I have already ordered an RMA device swap due to issues with the speaker blowing out. So if I fail to resuscitate it, help is already on the way. But I would like my tab to work again by the time I go back to work Monday
Update: Figured out the ADB recovery driver problem. Nandroid backup was successful. I'm now pulling the backup image to my desktop. Will try a ROM reflash next.
UPDATE UPDATE: The weirdest thing. I noticed while it was plugged into my machine, still stuck on the Google boot logo, that I was able to see the tab in ADB devices. So I typed in adb logcat and found some message about /system/xbin/busybox missing.
I browsed with ADB shell and found there is a busybox in /system/bin. So I did ADB remount, and then copied busybox from bin to xbin. Entered a reboot command, and bam! Five seconds on the Google splash, and then right to the booting X.
Why in the world would this have happened... maybe the busybox installer app got an upgrade and botched an attempt to upgrade busybox?
cmstlist said:
UPDATE UPDATE: The weirdest thing. I noticed while it was plugged into my machine, still stuck on the Google boot logo, that I was able to see the tab in ADB devices.
Click to expand...
Click to collapse
The adb daemon - adbd - is started by init as a service so long as you have previously enabled adb debugging. So, it happens before the whole android reboot sequence kicks off (checking that all .apks without odex files have up-to-date .dex entries in dalvik cache, permission checks, etc.) You can access it on devices that are "stuck" in the late stage of booting.
TWRP - for better or worse - does not claim the same USB vid/pid ID that is used by the N7's ADB facility, even though the exact same driver can be used for either adb mode ... so long as you manually went into the driver install package and add the "universal" vid/pid values used by TWRP to the driver's .inf file. I think this is done simply to minimize the effort keeping up with new device identifiers by the TWRP team. It does create the impression that separate drivers are needed - but only because neither of the two drivers (Google vs. Universal) have the "other's" vid/pid pair listed as matching devices in their .inf files.
Anyhow, you got it all sorted out - congrats.
Thanks! I had been worried maybe the whole file system was corrupted, so in comparison this was a relief.
Sent from my Galaxy Nexus using Tapatalk 2
I'm NOT responsible if you bork your tablet because you can't follow simple instructions!
I've just made a simple batch file with adb, and the recovery file all in one zip for y'all.
Make sure you've unlocked your bootloader by following instructions HERE
1) Download Chainfires latest root and copy to Your Internal SD card on your tablet
2) Download and install DRIVERS
3) Download and extract nexus7_2013_recovery_A+.zip to a folder on your PC.
4) Open folder where you extranted nexus7_2013_recovery.zip
5) Make sure your tablet is powered on, and connected to the PC, then click on "Nexus7.bat" and follow instructions. (If your PC is installing drivers once it boots into fastboot, WAIT until the drivers are installed before clicking next!)
6) Be ready and hold volume up as the tablet will restart automatically, keep holding volume up until you reach the TWRP screen
7) Once in TWRP flash SuperSU/UPDATE-SuperSU-v1.43.zip
8) when you reboot Superuser will be updated automatically by the Play Store
Enjoy!
BIG thanks to Chainfire for his root, and team win recovery project for their fast work on the recovery!
07/30/13 Updated SuperSu link to latest revision (ver 1.51).
07/29/13 Updated SuperSu link to latest revision (ver 1.50).
For those that couldn't find their azzes if a target was painted on it, here's a link to the video.
http://www.youtube.com/watch?feature=player_embedded&v=UpcTMTu-5Qc
I'm NOT responsible if you bork your tablet because you can't follow simple instructions!
I got through the first 5 steps. However the tablet rebooted to the OS. At step 6 how do you reboot into recovery?
Ravynmagi said:
I got through the first 5 steps. However the tablet rebooted to the OS. At step 6 how do you reboot into recovery?
Click to expand...
Click to collapse
ADB reboot recovery
Thank you very much for this, worked for me on the second try. Might I be so bold to suggest these changes to your steps to make them more clear? If not I will edit my post.
Edit - Didn't see you had a video. It didn't boot me into fastboot. I'm sure I did something wrong. Thanks again!!!
evodon84 said:
Thank you very much for this, worked for me on the second try. Might I be so bold to suggest these changes to your steps to make them more clear? If not I will edit my post.
Make sure you've unlocked your bootloader by following instructions HERE
1) Download Chainfires latest root and copy to SD card
2) Download and install DRIVERS
3) Download and extract nexus7_2013_recovery_A+.zip to a folder on your PC.
4) Open folder where you extranted nexus7_2013_recovery.zip
5) Power off your device.
6) Once powered down, hold Volume Down and Power. (this will boot you into fasboot)
7) Make sure your tablet is connected to the PC, then click on "Nexus7.bat" and follow instructions. (If your PC is installing drivers once it boots into fastboot, WAIT until the drivers are installed before clicking next!)
8) Be ready and hold volume up as the tablet will restart automatically, keep holding volume up until you reach the TWRP screen
9) Once in TWRP flash SuperSU/UPDATE-SuperSU-v1.43.zip
10) when you reboot Superuser will be updated automatically by the Play Store
Click to expand...
Click to collapse
Umm thanks, but the bat file boots you into fastboot...watch the video
When you say copy chainfire's SU to the SD CARD you mean to the root of the directory you get when you connect via MTP, right? Where the Alarms/Download/Movies/Music etc directories are, right?
I see this syntax used a lot "copy to SD card" when there's not really an SD card, so it's a bit confusing (not just here). Especially since there's no obvious SDcard directory exposed when you connect via MTP to a PC.
greenmky said:
When you say copy chainfire's SU to the SD CARD you mean to the root of the directory you get when you connect via MTP, right? Where the Alarms/Download/Movies/Music etc directories are, right?
I see this syntax used a lot "copy to SD card" when there's not really an SD card, so it's a bit confusing (not just here). Especially since there's no obvious SDcard directory exposed when you connect via MTP to a PC.
Click to expand...
Click to collapse
Yes, you may want to create a folder in there for organizing all your flashable zips
greenmky said:
When you say copy chainfire's SU to the SD CARD you mean to the root of the directory you get when you connect via MTP, right? Where the Alarms/Download/Movies/Music etc directories are, right?
I see this syntax used a lot "copy to SD card" when there's not really an SD card, so it's a bit confusing (not just here). Especially since there's no obvious SDcard directory exposed when you connect via MTP to a PC.
Click to expand...
Click to collapse
Yes, your INTERNAL SD CARD
Thanks guys, I haven't done much rooting / flashing with devices without SD cards before. I used the Nexus 7 toolkit to root the old Nexus 7. Everything I rooted before that had a real SD card to dump zips on - wanted to make sure where TWRP could access.
Looks like I'm still stuck at step 6. After running ADB reboot recovery, the tablet reboots and I see the dead Android with the red triangle. So I'm guessing Recovery didn't get flashed right.
So I rebooted it again. Ran the Nexus7.bat. It boots to Fastboot okay, and seems to be successfully after pressing enter a couple times. But ADB reboot recovery results in the red triangle again.
evodon84 said:
Thank you very much for this, worked for me on the second try. Might I be so bold to suggest these changes to your steps to make them more clear? If not I will edit my post.
Edit - Didn't see you had a video. It didn't boot me into fastboot. I'm sure I did something wrong. Thanks again!!!
Click to expand...
Click to collapse
I'm ammending the video now to reflect your suggestion about booting right into recovery afterwards...thank you
Ravynmagi said:
Looks like I'm still stuck at step 6. After running ADB reboot recovery, the tablet reboots and I see the dead Android with the red triangle. So I'm guessing Recovery didn't get flashed right.
So I rebooted it again. Ran the Nexus7.bat. It boots to Fastboot okay, and seems to be successfully after pressing enter a couple times. But ADB reboot recovery results in the red triangle again.
Click to expand...
Click to collapse
What error message are you getting at the end of the flash, or does it say success...watch the screen as it's flashing.
I just ammended the video, follow along
Ravynmagi said:
Looks like I'm still stuck at step 6. After running ADB reboot recovery, the tablet reboots and I see the dead Android with the red triangle. So I'm guessing Recovery didn't get flashed right.
So I rebooted it again. Ran the Nexus7.bat. It boots to Fastboot okay, and seems to be successfully after pressing enter a couple times. But ADB reboot recovery results in the red triangle again.
Click to expand...
Click to collapse
Try going directly into recovery right after the batch file finished and restarts your device. I had the same problem if I let my device boot and then reboot into recovery.
ATGAdmin said:
I'm ammending the video now to reflect your suggestion about booting right into recovery afterwards...thank you
Click to expand...
Click to collapse
Cool, glad I could be of some small assistance.
Rooted just fine, thanks! Saved me typing some adb commands and such.
evodon84 said:
Try going directly into recovery right after the batch file finished and restarts your device. I had the same problem if I let my device boot and then reboot into recovery.
Click to expand...
Click to collapse
Yes, that was the problem. I started doing the steps manually and instead of letting it reboot after flashing the recovery.img, I went straight to Recovery from Fastboot and it worked fine. Thanks.
Ravynmagi said:
Yes, that was the problem. I started doing the steps manually and instead of letting it reboot after flashing the recovery.img, I went straight to Recovery from Fastboot and it worked fine. Thanks.
Click to expand...
Click to collapse
I dont know what happened but this did not work, I can still boot my device, but now I have no recovery installed. If I attempt to boot into recovery, i get the red triangle underneath it says *No command* I have tried to research the problem here but no luck in getting TWRP to flash.
Just curious why was this moved out of development? I'm glad I caught it yesterday before it was moved. All the past android devices I've owned have had their root instructions under a development forum here on XDA. I would have assumed since this device was so new the root instructions where not available yet. I admit it would have been my fault for not searching but as I said the precedence has been search the development forum for root guide. Just a thought, I know you moderators are obviously forum gurus..but I think a good portion of the community is used to finding them their. Even the OP thought it was the proper location.
samg77 said:
Just curious why was this moved out of development? I'm glad I caught it yesterday before it was moved. All the past android devices I've owned have had their root instructions under a development forum here on XDA. I would have assumed since this device was so new the root instructions where not available yet. I admit it would have been my fault for not searching but as I said the precedence has been search the development forum for root guide. Just a thought, I know you moderators are obviously forum gurus..but I think a good portion of the community is used to finding them their. Even the OP thought it was the proper location.
Click to expand...
Click to collapse
There's no telling why they do what they do. I don't question it anymore lol
Sent using XDA premium on my Nexus 7 (2) tablet.
ATGAdmin said:
There's no telling why they do what they do. I don't question it anymore lol
Sent using XDA premium on my Nexus 7 (2) tablet.
Click to expand...
Click to collapse
Well honestly I posted the question mainly to have an intellectual conversion regarding allowing this to be in development until a alternate root method is posted.I mean I am not an android developer but I am a systems engineer for twenty years (by this I'm just simply pointing out I am of above average technical skill) and simply because I've always my root method for the past ...I'd estimate about a dozen android models I've rooted found root under development. So some others might miss it too
samg77 said:
Well honestly I posted the question mainly to have an intellectual conversion regarding allowing this to be in development until a alternate root method is posted.I mean I am not an android developer but I am a systems engineer for twenty years (by this I'm just simply pointing out I am of above average technical skill) and simply because I've always my root method for the past ...I'd estimate about a dozen android models I've rooted found root under development. So some others might miss it too
Click to expand...
Click to collapse
You're preaching to the choir bro, I'm with ya.
Sent using XDA premium on my Nexus 7 (2) tablet.
Hello,
This isn't my first Nexus 7 (my kids had 2012's and I had a 2013: they were all unlocked and rooted). This year I got my oldest a 2013 model, and promptly set to unlocking it and rooting it. TWRP is my normal go-to for ROM jumping ease.
This time; I used CF-AutoRoot to get it rooted, I used the simple fastboot oem unlock and fastboot flash recovery twrp.img .. all appeared to have went fine. UNTIL; I booted into TWRP and none of the directories had any files. So I rebooted back to the OS, installed Astro file manager, looked around and sure enough; all the .zip files for trying out the ROMS were there (along with some gapps files).
So I installed twrp via the PlayStore, and fired it up. It can not see the files either!? (It also said BusyBox wasn't installed; I installed a couple (and un-installed them) to see if it would see them; it did not and doesn't appear to install what it needs even when it asks if I want to install it). I installed UPDATE-SuperSU-v2.46.zip earlier in the process also.
Ideas? I did use adb to push the files to / and again to /sdcard .. I can see they went via Astro, but when I'm in TWRP nothing is there? What gives?
Thank you,
P.S. I'm running 6.0.1, bone stock except for being rooted and unlocked.
67comet said:
Hello,
This isn't my first Nexus 7 (my kids had 2012's and I had a 2013: they were all unlocked and rooted). This year I got my oldest a 2013 model, and promptly set to unlocking it and rooting it. TWRP is my normal go-to for ROM jumping ease.
This time; I used CF-AutoRoot to get it rooted, I used the simple fastboot oem unlock and fastboot flash recovery twrp.img .. all appeared to have went fine. UNTIL; I booted into TWRP and none of the directories had any files. So I rebooted back to the OS, installed Astro file manager, looked around and sure enough; all the .zip files for trying out the ROMS were there (along with some gapps files).
So I installed twrp via the PlayStore, and fired it up. It can not see the files either!? (It also said BusyBox wasn't installed; I installed a couple (and un-installed them) to see if it would see them; it did not and doesn't appear to install what it needs even when it asks if I want to install it). I installed UPDATE-SuperSU-v2.46.zip earlier in the process also.
Ideas? I did use adb to push the files to / and again to /sdcard .. I can see they went via Astro, but when I'm in TWRP nothing is there? What gives?
Thank you,
P.S. I'm running 6.0.1, bone stock except for being rooted and unlocked.
Click to expand...
Click to collapse
Good day and welcome to XDA-Developers.
Your inquire has been reviewed.
Within moments your thread will be moved to the correct device location within the forum.
There your issues will be addressed by users whom know and understand your device.
Regards,
XDA Assist Team
Hello and thank you for using Q/A,
after touching on "install" you should see a field where you can enable ZIP. This button is located next to the flashing-bar.
Kind regards
Trafalgar Square
Trafalgar Square said:
Hello and thank you for using Q/A,
after touching on "install" you should see a field where you can enable ZIP. This button is located next to the flashing-bar.
Kind regards
Trafalgar Square
Click to expand...
Click to collapse
Okay; I went ahead and put a post on my site so I can show pictures on here ..
I've been using TWRP to install miscellaneous ROMS on my devices since my Nexus One (think I used CWM back then though). I have rooted all of my phones (Except my Kyocera piece of junk) and tablets with little to no issues (the occasional soft brick when learning, but that's normal in my book).
I've uploaded the screens I experience as I go alone with explanations on my openlug (.) com site. I've shut comments off since it is a server in my house that handles the sites, e-mail isn't available via my home server (haven't figured out how to bypass my ISP's restrictions).
I haven't posted enough to XDA to allow any external links (eg: images from my site). So please head to openlug (.) com and see what I wanted to show.
Time to go find something to post about so I can get past that 10 post limit ..
Thanks for any and all help; never had this happen before. I'm using Linux to work on my devices, so any .exe ideas w/not work.