Related
Ok so I think I've bricked my Nexus One. Everything was working perfect until I re-rooted it (to have SetCPU to work). I am now stuck at the loading animation screen (Google Nexus One "X"). It just keeps going and going and going. I've even tried loading my Nandroid backup and still does the same and won't work. Also I've wiped to factory default settings and tried to reinstall Modaco's 1.3 rom.
Someone please help me out...
Flash bacon add-on on top
bye!
So reinstall Modaco's 1.3, then install Bacon Add-On, and then reboot?
Yep That's the solution for some users
ok cool I'll give it a shot right now... I really appreciate it
ok at this moment it's still stuck on the animated screen... now I really don't know what to do...
Try flashing the stock rom
if u have the sdk installed, the run ddms. power on the phone usb connected to pc and see the log in ddms, paste-bin here
I have no idea on how to do that... I'm pretty much stuck at this point
try not flashing Modaco's Rom,
just flash CM's bacon
i think there is a confusion because Modaco's rom is in the rooting threat (made me believe you HAVE to use Modaco's superboot and then go to CM's bacon.
reality is you don't need modaco's superboot. after bootloader unlocking and flashing Amon Ra's recovery image you can go straight flashing CM's Makin' Bacon.
It seems people have been successful with CM's
maybe just go straight back to the start, check that bootloader is unlocked, flash amon ra's recovery, then flash Makin' Bacon
good luck
shmigao said:
try not flashing Modaco's Rom,
just flash CM's bacon
i think there is a confusion because Modaco's rom is in the rooting threat (made me believe you HAVE to use Modaco's superboot and then go to CM's bacon.
reality is you don't need modaco's superboot. after bootloader unlocking and flashing Amon Ra's recovery image you can go straight flashing CM's Makin' Bacon.
It seems people have been successful with CM's
maybe just go straight back to the start, check that bootloader is unlocked, flash amon ra's recovery, then flash Makin' Bacon
good luck
Click to expand...
Click to collapse
WOW, I really appreciate it and that just worked for me. Thank you to the both of you guys!
if you can get into bootloader mode (this is the lowest level mode you can boot into), you can not brick. Even more so if you can get into recovery (which is usually always possible if you can get to bootloader)
Good you found a way to get out of your situation.
Like i said in Android 101, you CAN NOT brick the phone unless you are updating SPL and Radio. All other stuff is just a minor inconvenience.
risterdid said:
WOW, I really appreciate it and that just worked for me. Thank you to the both of you guys!
Click to expand...
Click to collapse
haha, i am glad it worked! I don't even have my Nexus One in my hands (my biz trip to the States has been delayed again ), but i spend the waiting time doing my research... it's a bit like the Holiday Season, just that the gift giving day gets pushed out further and further...
glad it worked and it confirmed my research - so i can go at it with ease once i can
This is good news. OP, you should update your thread titled with the prefix [SOLVED].
ahh how'd I miss that 101 sticky... thanks for the heads up again guys.
Edited title =)
Am I bricked?
Ok, my issue is that I cant boot into bootloader or recovery (I tried booting with rollerball pushed in, booting with down volume, abd-mac reboot recovery, abd-mac reboot bootloader) and it just goes right into my OS which is crashing every few minutes, and my radio wont work. Any suggestions? If I am bricked, can I send it to HTC even though its rooted and bootloader is unlocked? I dont care if I have to pay for fixing it.
DrBlast33 said:
Ok, my issue is that I cant boot into bootloader or recovery (I tried booting with rollerball pushed in, booting with down volume, abd-mac reboot recovery, abd-mac reboot bootloader) and it just goes right into my OS which is crashing every few minutes, and my radio wont work. Any suggestions? If I am bricked, can I send it to HTC even though its rooted and bootloader is unlocked? I dont care if I have to pay for fixing it.
Click to expand...
Click to collapse
First of all, if your phone boots at all, it isn't bricked. A brick is a paperweight - it doesn't do anything. Second, this thread of 5 months old. Third, people have talked A TON about sending phones in to HTC with an unlocked bootloader, do a bit of searching.
And finally, it is very peculiar that your phone doesn't boot into bootloader or recovery. Try plugging your phone into your computer, opening your command prompt, navigate to your adb install direction, typing "adb wait-for-device reboot bootloader", and turning on your phone. Best of luck!
People should be banned for bumping 5 month old threads with posts not even related to the OP's post. Ridiculous.
@rcxquake: thanks for your suggestion. That didnt work, it just rebooted the OS. Ill keep searching for my solution and how to send to HTC if I cant find the solution.
@GldRush98: Sorry for ruining your day. I put in a google search for what I was experiencing and this was one of the top result of anyone remotely close to my issue. Yes, this is an old post, but maybe someone had this issue months ago, and had a solution I wasnt aware of.
And like I said, I found this post, although not exactly my same issue, was as related as Ive been able to find. I didn't find it so ridiculous.
If you can find my same issue on another post, then please help by pointing me to it so I can find my solution. I didn't mean to cause any issues.
Thanks
I for one am glad you posted. I don't know whether this is a solution for you or not, but I'm sometimes only able to get to the bootloader after I've had the phone off the charges, with the battery out, for some time. It varies for me between a few minutes and many minutes. It is hard to say because when I try and it doesn't work, I don't know if I've reset the time by having tried.
Anyhow, I found this thread because I'm having trouble with an N1, and one of the earlier posts may help me. Thanks for bumping the thread for my benefit.
Before you tell me to 'Google it' (which I have, and leads me to 1000 posts of people telling other people with the same problem to 'Google it'), please read.
I will PayPal anyone $20 with working instructions of how to resolve this
Phone: HTC Hero w/ chin
Carrier: Alltel
Story:
Switched from WM6 Palm Treo Pro to HTC Hero. Came with 2.1 and needed apps2sd. Want CM7 stable.
-Rooted using AndRoot.
-Installed SuperUser and Root Checker. Root Checker said I was good to go. SuperUser would not show any apps in the list this whole time.
-Installed Titanium Backup which said I needed BusyBox, but it would fail to install. Tried to install busybox and it said I was not rooted. Alright...
-Installed ClockworkMod and flashed recovery. Tried to reboot into clockwork recovery, but when I clicked it, it did nothing. When I clicked rom from sd card, and clicked the CM7, it said 'going to reboot now' but again, nothing happened.
I booted into recovery manually, but it was still in Android system recovery. Apparently there was some sort of rooting problem, so I tried z4root. Permanent root was stuck on 'rebooting', and temporary root said successful, but something was still wrong as BusyBox installer would say I was not rooted, and SuperUser app didn't show any programs to allow permissions.
I turned the phone off, and back on. It goes to the white 'HTC' screen, reboots, and then comes to a black page with a picture of a Hero and a red triangle and exclamation mark. I hold home and hit power, and it takes me into the Android system recovery. I wiped data and cleared cache, rebooted, and it does the same thing.
- - -
Now i've done many hours of research, and found nothing to help me. I guess i'm a bit confused on what the SDK does and how to use it, because it won't connect to my phone since I can't even boot my phone into the OS. I tried to download the RUU and rename it update.zip, but it says signature verification failed or not found in android recovery. I've done the clear data method by holding home, back, and power, but still nothing.
I need a clearcut answer for getting back to a stock Alltel 2.1 OS on my phone. I am more advanced than a basic user, and have flashed many roms on Windows Mobile, but remember I might not exactly understand everything.
I'm a silent browser on these forums but now I come to you guys for help. I hope to grow into a dev and hopefully help someone in the future in my position.
I read somewhere to wipe EXT2, but still confused on that process as it seems I don't know how to get into adb command line on my computer.
Try reflashing the cwm recovery. Sounds like you have no recovery image.
-----
Sent from my CDMA Hero. I got some hot Gingerbread-on-Hero action here!
Dumb question...did you flash a ROM? Maybe I missed it in your post, but I see you installed Clockwork, SuperUser and all that, but don't see that you flashed a ROM. *EDIT* I see you did...
So...worst case scenario, if you can't even boot your phone, just start over from scratch...
Download the original AllTel ROM from here.
If you don't have HTC Sync set up and can't restore from your computer, use this method to flash it...your phone should now boot...
Then try to reroot, using this (preferred) or this.
Download ROM Manager from the Market and install ClockworkMod Recovery
Boot to recovery (hold home and power at the same time).
Once in recovery, wipe cache, system, data and boot (make sure you don't wipe your sd card! Do it twice for good measure)
Select install .zip from SD card, select zip and you should be good to go with a rooted phone and a new ROM.
I think that should cover it...
Ok, on your first link to flash my phone, the step says:
"With phone powered on, do "adb reboot bootloader" to enter fastboot."
How do I get the command prompt on my computer to communicate with the phone? That was my biggest problem when reading other people's posts. I guess i'm a bit lost. I installed the r10 android sdk which I believe is the first step? And when my phone is connected to the computer to enter these commands, is it okay if it is sitting at that screen with the red triangle?
Thanks for your help btw your steps sound simple, and simple is nice. One step closer!
Do you have HTC Sync set up? If you do, you should be able to restore from that to get you back to official AllTel...That's going to be the easiest way to get you back to stock I think.
And...I am on a Mac So, helping someone on a PC is not my forte with ADB
I'd try setting up HTC Sync and get yourself back to stock that way.
EDIT - To get it to communicate, you need to set up ADB and all that. Then just use command prompts...Try this thread for help/instructions.
I actually got it to load that rom with vol down + power but eventually got to 'CID incorrect! Update fail!', so i'll try connecting to sync.
damienisxcore said:
I actually got it to load that rom with vol down + power but eventually got to 'CID incorrect! Update fail!', so i'll try connecting to sync.
Click to expand...
Click to collapse
What ROM? The AllTel one?
I have to take off until about 8:30 or so...get yourself set up with HTC Sync and get the USB drivers and all that set up, first thing you need to do is get your computer to talk to your phone...download the official AllTel RUU and restore to stock. That's task 1
Then we'll get ya rooted
I think I found a rom that worked. Currently rebooting. I can follow the rest and if I need anymore help, I'll give you a hollar. I should have had it right the first time, but I was following about 5 sets of different directions and mixing them around to avoid certain programs. I like yours though.
Send me a PM with your paypal e-mail and I can send it over. Least I could do.
OP, glad you got it. What rom?
Ranger, nice!
sent from a series of tubes.
il Duce said:
OP, glad you got it. What rom?
Ranger, nice!
sent from a series of tubes.
Click to expand...
Click to collapse
He flashed CM7. Gotta get him on aospCMod
damienisxcore said:
I think I found a rom that worked. Currently rebooting. I can follow the rest and if I need anymore help, I'll give you a hollar. I should have had it right the first time, but I was following about 5 sets of different directions and mixing them around to avoid certain programs. I like yours though.
Send me a PM with your paypal e-mail and I can send it over. Least I could do.
Click to expand...
Click to collapse
It's tough sometimes to follow things...and as much as we always tell people to search, ya know, the search kinda sucks I searched for all the threads I linked for you, but I knew what I was looking for. If you don't know what to look for, searching is kinda tough. Glad you got it!
Now...if you want a real ROM, I'll just toss this one out there In all actuality, CM7 and aospCMod are quite similar, I am just partial to aosp's builds.
Let me know if you need any more help.
guys i was able to s-off and root my IS last night with help from alpha rev x.
i then attempted to install custom rom using CWM recovery.
inside recovery i can install the rom fine, it says its installed, aswell as no-sense 1.5 - there are no errors.
but when i go to reboot again, it just sits on the htc boot screen and i have to pull battery to get back into recovery.
please help
is it possible ive bricked my phone??
djbenny1 said:
guys i was able to s-off and root my IS last night with help from alpha rev x.
i then attempted to install custom rom using CWM recovery.
inside recovery i can install the rom fine, it says its installed, aswell as no-sense 1.5 - there are no errors.
but when i go to reboot again, it just sits on the htc boot screen and i have to pull battery to get back into recovery.
please help
is it possible ive bricked my phone??
Click to expand...
Click to collapse
I think it's to do with the radio, someone said that in the alpharevx chat.
did they say how to fix?
is it in the alpharev x thread?
can you link?
how long do you wait for the white htc screen?
I took quite a while for it to load, ill say try reboot and wait for 30 mins
and make sure u have ext4 if the rom require ext4
and i dont think that your phone is bricked
same here...
hi, i am in the same boat as you are. I s-offed through alpharevx, great work btw! I also rooted through superoneclick by means of gingerbreak, also great work! thank these guys so much. Here comes the problem. I downloaded rom manager from the market and installed clockworkmod recovery through that. and i attempted to load a custom rom through the recovery tool. it went fine without any error. however, when i try to reboot, i get the htc logo on white background.... I flashed partition using ext4 formatting tool from here, http://forum.xda-developers.com/showthread.php?t=1088498 , i also flashed the radio specified in this post....but same thing, stuck at "htc"... help...
you have to install 4EXTRecovery_v1.0.6_modded_CWMR_v4.0.0 first. you can find the steps here: http://forum.xda-developers.com/showthread.php?t=1104765. when I tried with just Format_data_partition_EXT4 I got the same results as you
Thank you! I tried the other recovery you mentioned. worked like a charm! Thanks.
once you've flashed, let me know if you still have earpiece volume with the custom rom. And if you do, did you flash a new radio?
gmarcoux said:
once you've flashed, let me know if you still have earpiece volume with the custom rom. And if you do, did you flash a new radio?
Click to expand...
Click to collapse
I lost the earpiece volume too, no matter How I change different Radio, still cannot get it back, now I got a phone cannot make a phone call
kakawong said:
I lost the earpiece volume too, no matter How I change different Radio, still cannot get it back, now I got a phone cannot make a phone call
Click to expand...
Click to collapse
Thats not right ... which rom? If its ARHD ... then did you try the AU radio linked in the first post?
That will surely give you sound on ARHD ...
Sent from my Incredible S using XDA App
Ok, so I ran into a VERY weird issue and was wondering if anyone else has experienced this or has a better solution then what I found.
My Nexus7 was running stock JRO03D. I had it rooted, using the Motley kernel with CWM Recovery - but outside of that, everything else was pretty stock. Anyway, I decided to upgrade to the 4.1.2 image. I pulled the one it downloaded automatically out of /cache and looked at the updater-script to see what it did. I noticed it replaced a lot, including the boot image, so I figured it would be better just to let it do everything and revert my custom stuff later. So I replaced the kernel with the stock JRO03D kernel and, using CWM, flashed the upgrade. Everything seemed to go perfect and it completed the upgrade. Prior to rebooting it, I also flashed the "unofficial" motley 4.1.2 kernel posted on XDA. I rebooted the device, and CWM warned me that 'su' needed to be fixed (how nice!) and made it suid again. It rebooted and after android "updated", everything was up and running. I confirmed in settings that it was on 4.1.2 with the custom kernel. SU was suid root as well. Perfect!
Not quite.
I decided to try rebooting into recovery to make sure CWM was still there, or flash it back if it wasn't. I opened up a terminal emulator, removed the new recovery-recovery image in /system, and did "reboot recovery". The Nexus7 rebooted, but rebooted right back into normal operation. Very weird. So I hooked it up to my computer, figuring CWM was gone, and tried to fastboot flash it back. Fastboot said it did, but I still wasn't able to reboot into recovery. I tried three different versions of CWM and even TWRP, but no dice. Every time I tried rebooting into recovery (using terminal emulator, adb shell or bootloader method) it just went right back into the normal boot process.
I spoke to some people on IRC who recommended reflashing the stock image from Google (without wiping user data). I reflashed the bootloader and then did a fastboot update <stock image>, and it said it replaced boot, recovery, system, etc. It rebooted automatically, and I tried going into stock recovery. That still did NOT work. Instead, I got a very sick looking android guy who was lying down with a red triangle with an exclamation point over him. I was a bit worried and upset at this point. I tried reflashing CWM/TWRP again, but nothing. When I did this, I no longer got the unhappy android image, but it just booted up normally.
I decided to try and doing a more thorough wipe, using fastboot to wipe cache/boot/recovery/system manually. Then I reflashed the bootloader and stock image. Still no recovery (stock or custom).
As you can imagine, I was getting even more concerned now. Especially since I was no without root and no way to get it back (since I couldn't get into recovery to flash the zip for it).
I tried every other thing I could think of to flash recovery back, but nothing worked. It wouldn't load at all.
Finally, I was about to do a complete factory reset and wipe/reflash of everything, but one last thought crossed my mind. I found the older (JRO03D) bootloader and flashed that. Reloaded bootloader and selected "Recovery". Voila, I was in TWRP Recovery Mode! (which was the last one I tried installing). I was able to reinstall my SU.zip and get everything back up and running.
SO, long story short, I'm now on 4.1.2, running the newer unofficial motley kernel and have su back. But I'm also stuck on the older 3.34 bootloader. If I try upgrading it back to 3.41, I won't be able to get into recovery.
Has this happened to anyone else? It doesn't seem like it. Is there a HW issue with my device causing this problem? I can't believe it's software related since I tried two different copies of the 3.41 image. Does anyone have any other suggestions on how I can upgrade the bootloader while keeping the ability to get into recovery mode?
Also, while everything *seems* to be working OK using 3.34, do you think it will cause other problems since I'm using 4.1.2?
Thanks.
*MOD EDIT* please don't quote the entire OP
Thanks for the bootloader info. I was in the same boat, and once I found your post, I went back to JRO03D and my recovery has returned.
Again, thanks, you F'n rule!!!
That android with the red triangle sounds like the stock recovery... so I think you actually got it to work, but you just didn't have a custom recovery...
Then again I don't think I've ever seen the stock recovery. Haha
Sent from my Galaxy Nexus using xda premium
MetalWych said:
Thanks for the bootloader info. I was in the same boat, and once I found your post, I went back to JRO03D and my recovery has returned.
Again, thanks, you F'n rule!!!
Click to expand...
Click to collapse
No problem. I'm glad to hear that my solution above helped someone else, and also that I'm not the only one experiencing the problem. I assume you mean you only went back to the JRO03D bootloader and not the whole image, right?
What I'm most concerned about is that it seems like my N7 (and possibly yours as well) is defective. I'm not an uber-expert on Android, but I'm fairly knowledgeable. With a stock system, outside of userdata, that I reflashed multiple times from multiple sources, to have any type of recovery (stock or custom) not work is a bit upsetting. Since it works fine on the older bootloader, it definitely seems to be an issue with that. But since most people do not have the same issue, the only variable I can see being the difference is hardware.
Metallice said:
That android with the red triangle sounds like the stock recovery... so I think you actually got it to work, but you just didn't have a custom recovery...
Then again I don't think I've ever seen the stock recovery. Haha
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
It looked more like a warning symbol that something went very wrong then a stock recovery screen.
I've gone into stock recovery on other Android devices before, and it looked similar to CWM. There was a menu that allowed you to install "authorized" update.zip files, factory reset the device, etc. There was no menu here, just a very pissed off and sick looking android guy .
I believe I am having the same issue. Would you mind linking me to the bootloader which worked for you? Tried searching but couldn't find it. Thanks, and great post!
Sent from my SCH-I535 using xda premium
There's a big thread around here somewhere with people having the same problem as the op. Unfortunately, staying with the 3.34 bootloader is the only 'fix' I've read about. I still can't figure out why some people run into this problem and some don't. I used twrp to flash the update when it became available, and twrp continued to work afterwards.
spongers said:
I believe I am having the same issue. Would you mind linking me to the bootloader which worked for you? Tried searching but couldn't find it. Thanks, and great post!
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
It took me a long time to find the old full JRO03D update, since Google only has the latest one on their page. I uploaded the bootloader out of it and you can download it here:
http://core.routed.com/bootloader-grouper-3.34.img
Reboot the Nexus7 into bootloader mode and run:
fastboot flash bootloader bootloader-grouper-3.34.img
fastboot reboot-bootloader
and then you should be able to flash recovery and get into it.
Metallice said:
That android with the red triangle sounds like the stock recovery... so I think you actually got it to work, but you just didn't have a custom recovery...
Then again I don't think I've ever seen the stock recovery. Haha
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
The android with the red triangle does not sound like the stock recovery, it is THE stock recovery.
Under JB 4.1.2 you do not need anymore to connect the N7 to a computer - like it had to be under JB 4.1.1 - to access the bootloader and then the recovery.
Now, pressing volume + power brings the bootloader , the up volume, one press, and then power press put the N7 to recovery. The recovery is the android with the red triangle. To enter in the recovery menu pressing power + volume up brings the menu with the following options:
i) reboot system now,
ii) apply update from ADB,
iii) wipe data/factory reset,
iiii)wipe cache partition.
Concerning specifically the OTA update for an unlock and root N7 there should be no problem during the process using stock recovery or CWM 6.0.1.0 as long as OTA Rootkeeper is set, before the installation, in order to keep root.
the fact that you were able to do volume down + power button into bootloader, then select recovery, makes me know its working. and the android guy on his back is the stock recovery... so everything is working fine. you said you flashed motley kernel, it may have something to do with that, and a few other things. you really need to understand how the N7 works, and what it will do if you do not do certain things.
what u should try is, fastboot flash recovery, then fastboot boot recovery
flash a different rom, i prefer Paul's Jr8 as its close to stock with nice little tweaks and see if your issue continues.
at the end of everything, i honestly find this more user error then device related. not everyone understands what the N7 is doing, and why.
smirkis said:
the fact that you were able to do volume down + power button into bootloader, then select recovery, makes me know its working. and the android guy on his back is the stock recovery... so everything is working fine. you said you flashed motley kernel, it may have something to do with that, and a few other things. you really need to understand how the N7 works, and what it will do if you do not do certain things.
what u should try is, fastboot flash recovery, then fastboot boot recovery
flash a different rom, i prefer Paul's Jr8 as its close to stock with nice little tweaks and see if your issue continues.
at the end of everything, i honestly find this more user error then device related. not everyone understands what the N7 is doing, and why.
Click to expand...
Click to collapse
Smirkis, my initial thought was that something went wrong in the upgrade process, possibly with the kernel like you suggested, so, as I mentioned in the OP, I flashed everything back to stock 4.1.2. I used flashboot to manually erase boot, cache, recovery and system. I then reinstalled the bootloader from Google's update tarball. I then used fastboot to update to image-nakasi-jzo54k.zip. At this point, outside of wiping sdcard, everything was stock 4.1.2.
While I will admit that I didn't realize that the dead-looking android meant stock recovery (and that's good to hear), subsequently flashing a custom recovery (CWM or TWRP) would continually fail to load it. In fact, I couldn't even boot into the recovery manually without flashing it. While using 100% stock, I attempted to flash three different versions of CWM and one version of TWRP. It claimed it updated, but I was not able to get back into recovery - either through bootloader, adb or "reboot recovery".
I know it's easy for people to always jump to the "user error" answer, but I fail to see how that is the case here. Based on your response, I don't think you actually read what I did and just jumped to the wrong conclusion, especially since I already tried your recommendation and much more. I am not running any custom ROM - everything was always stock outside of recovery, root and kernel. If you can explain your reasoning for thinking I did something wrong in all of my numerous attempts to get it working, I would appreciate it since maybe that would provide a solution. While I did attempt to use a custom kernel originally, that obviously isn't the issue if going back to stock didn't fix it.
Additionally, reverting back to the older bootloader magically fixed everything, while all other attempts failed. Subsequently reinstalling the custom kernel didn't break anything either. So if it wasn't the bootloader and something else was broken, I would assume it would be broken in both versions of the bootloader. The fact that this problem is affecting others, granted a small number, and the same solution works for them, leads me to believe that there is either a bug in the bootloader affecting some N7s or some rare HW defect causing a few of us problems.
There is a conversation about the new android update the boot-loader update and A Power management chip on the nexus 7.. It seems this chip is being changed out. The new chip functions the same as they have been using but Its not compatible with the old boot-loader . The above is the reason for the boot-loader change.. Google is aware of the troubles everyone in this thread is having . I would be looking for a new very tiny update in the near days. Just a guess im wondering if the truth is they are gearing up for the 3g version of nexus .maybe the pm chip being changed has a issue with the added radios. They did say ITS NOT A Chip upgrade but will not say why they are making the switch .
sorry i do not have a link . but everyone knows how to get to google groups ..
Happy Reading..
I just got another N7 in the mail today, gonna unlock n root it when i get off work. hopefully i end up in your situation so i can attempt to assist in resolving this. why the old bootloader works for you, and never worked for the rest of the world is beyond me. they updated it for a reason lol, i even called google the first week i got mine in july to tell them about the bootloader and they "said" they would forward that info to the development team. it took almost 3 months for them to fix it.
if the old one works for you, then use the old one. the only difference really is the fact that reboot to recovery thru bootloader actually works. if it works for you, don't upgrade.
mine on the other hand, couldn't get into recovery via bootloader. i was dieing for that upgrade, and when it came i was beyond relieved. i did a RMA this week because my first one had screen lift since the 2nd day i owned it lol, so i'll report back when i get home in an hour or so on my results.
smirkis said:
I just got another N7 in the mail today, gonna unlock n root it when i get off work. hopefully i end up in your situation so i can attempt to assist in resolving this. why the old bootloader works for you, and never worked for the rest of the world is beyond me. they updated it for a reason lol, i even called google the first week i got mine in july to tell them about the bootloader and they "said" they would forward that info to the development team. it took almost 3 months for them to fix it.
if the old one works for you, then use the old one. the only difference really is the fact that reboot to recovery thru bootloader actually works. if it works for you, don't upgrade.
mine on the other hand, couldn't get into recovery via bootloader. i was dieing for that upgrade, and when it came i was beyond relieved. i did a RMA this week because my first one had screen lift since the 2nd day i owned it lol, so i'll report back when i get home in an hour or so on my results.
Click to expand...
Click to collapse
Just to clarify, going from bootloader->recovery never worked for me either. Whenever I needed to get into recovery mode, I just opened up a terminal, su'd to root and then ran "reboot recovery", or occasionally doing it via adb. However, those methods always worked for me until I upgraded to the latest bootloader. Then, no custom recoveries would load via any method.
My Nexus7 was first generation. I actually picked it up in Sams Club the day before they were officially released. So if Google made any HW changes in the different revisions, that might explain the difference in results on 4.1.2. Though I imagine most people on XDA also picked theirs up out of the first batch, so I don't think that could be the case. What seems more likely is that there are minor hardware differences that are causing some people's to fail with the 3.41 bootloader, while most don't have that issue. It will be interesting to see if you experience the same issue on your new one though.
gunner1937 said:
Concerning specifically the OTA update for an unlock and root N7 there should be no problem during the process using stock recovery or CWM 6.0.1.0 as long as OTA Rootkeeper is set, before the installation, in order to keep root.
Click to expand...
Click to collapse
It didn't worked for me. I've tried Rootkeeper apk, but it was useless.
This was driving me crazy until I've found this topic! I've tried resetting it to original settings, using rootkeeper and traditional methods, nothing, zero!
At last, phonic saved my life, and finally I a could root my Nexus 7!
I never responded but my RMA worked as it should. but the issue has been resolved with recovery updates from the developers. the rest of the world who had issues should be good to go. I ended up selling my 16gb unit and got a 32 and it works as it should as well. are we all happy campers now?
Sent from my Nexus 7 using xda premium
I've had similar experiences where the way certain kernels install zips are packaged, the wipe custom recoveries at install. In that situation, I've never wiped anything from system, but rebooted into bootloader and fastboot boot recovery "recovery.img". Then from there install the recovery.zip. The worst is when this happens when you get flash happy away from home and the kernel doesn't work. No way to fix without a comp w/SDK. Glad you're back up and running.
(I cannot be held responsible if the aforementioned damages your device; do the research and own the process.)
I am so glad to have found this thread. This problem was beginning to drive me nuts.
I've rooted my Nexus One a long long time ago, and eventually reverted to it's original state. Let's skip ahead a year..
I wan't to use my Nexus One again until I can get my hands on a Nexus 4. I'm trying to root this bad boy, but run into a problem with every method. I got the one click method to work, but it wouldn't boot up. And when I try to go into Bootloader for recovery, it checks for the PASSIMG.ZIP file and then updates. If I click no, it makes no difference, it doesn't let me do anything. Updating will restore the phone to stock(unrooted). So I deleted PASSIMG.ZIP from the SD card. Ever since, I can actually click on Recovery, but I run into trouble(see further below). S is ON btw, I don't remember what this was, but I'm sure I had it OFF before? I have been using an iPhone for the past year and a half, so I apologize for being a noob. I'm not to tech savvy when it comes to these terms, either.
Short explanation:
One Click Root - I can root it, but when I go to Bootloader Recovery it shows the Android guy and a triangle around !
Using the old school method using Windows terminal, recovery-clockwork-5.0.2.0-passion.img was flashed without problem.
But I can't access Recovery!
In the end I'm trying to at least have an ICS ROM, or Jellybean(Really wanna try Google Now or whatever) if possible.
Check the Wiki for instructions on how to bootloader unlock your phone. Much easier. You can then flash everything you want using fastboot (so make sure you have the fastboot driver installed correctly).
Btw, the triangle means you still have stock recovery.
tommert38 said:
Check the Wiki for instructions on how to bootloader unlock your phone. Much easier. You can then flash everything you want using fastboot (so make sure you have the fastboot driver installed correctly).
Btw, the triangle means you still have stock recovery.
Click to expand...
Click to collapse
The unlock padlock icon means the bootloader is unlocked, correct? I've done that. And I actually went through that, and flashed the custom Recovery, still the same result. I'll retry it again.
I figured it out, but I don't get it...
I did this in kind of a different route, so just incase someone runs into a similar problem some how:
I rooted the phone using the one click root software on a windows PC, the N1 was successfully rooted.
However, same error recovery, even after adb flashing recovery(followed wiki and unlockr tutorial).
What I did different to fix the issue, was after the root, I downloaded Rom manager(yes I've done this before too, but...), I flashed the recovery via Rom Manager. After it didn't work(sadface).
I tried it again, but just out of frustration I re-flashed it after flashing. So I flashed the recovery twice, back to back. And poof, I check bootloader, go into recovery, and there it is(just like it used to be).
Close this I guess, (an embarrassing)problem has been solved.