Related
Hi there Android people.
I am having some issues with running the current Cyanogen *4.2.11.1*.
Phone: G1 Drea100 PVT 32B with stock 1GB SD
using anmon RA 1.5.2 recovery image
-wipe all available in menu.
-created a new partition- FAT32, Ext1 (upgraded to 4), Swap 32MB
-wiped all again.
-repair SD: ext
-flash signed-dream-devphone-userbug-ota-14721
-Once the flash above completed I did not restart, I simply flashed to update-cm-4.2.11.1
-reboot
Once it boots, my home process stops responding if I touch anything. This last for about 15 seconds, after that it seems to responds fine, but the browser and market place seems to auto-close on me from time to time, and I get random phone reboots, after a few reboots my phone simply stops turning on. I have to wait about 10 minutes to get into recovery and try to flash all over again.
I tried fix_permissions in the terminal, no luck.
I did some reading and noticed a lot of people are running different Radio/SPL versions other than stock, I am no super user, so I don't know if any of this effects ROMs, or if I should be flashing either for any sort of benefits I am missing out on? could this be the issue? Current SPL/Radio below:
HSPL10.95.3000
CDLP-4
Radio-2.22.19.261
Any input would be much appreciated.
Thanks,
D3AD PIX3L said:
Hi there Android people.
I am having some issues with running the current Cyanogen *4.2.11.1*.
Phone: G1 Drea100 PVT 32B with stock 1GB SD
using anmon RA 1.5.2 recovery image
-wipe all available in menu.
-created a new partition- FAT32, Ext1 (upgraded to 4), Swap 32MB
-wiped all again.
-repair SD: ext
-flash signed-dream-devphone-userbug-ota-14721
-Once the flash above completed I did not restart, I simply flashed to update-cm-4.2.11.1
-reboot
Once it boots, my home process stops responding if I touch anything. This last for about 15 seconds, after that it seems to responds fine, but the browser and market place seems to auto-close on me from time to time, and I get random phone reboots, after a few reboots my phone simply stops turning on. I have to wait about 10 minutes to get into recovery and try to flash all over again.
I tried fix_permissions in the terminal, no luck.
I did some reading and noticed a lot of people are running different Radio/SPL versions other than stock, I am no super user, so I don't know if any of this effects ROMs, or if I should be flashing either for any sort of benefits I am missing out on? could this be the issue? Current SPL/Radio below:
HSPL10.95.3000
CDLP-4
Radio-2.22.19.261
Any input would be much appreciated.
Thanks,
Click to expand...
Click to collapse
Why did you use "signed-dream-devphone-userbug-ota-14721"
I'm no pro but I used the base image that cyanogen recommends on his wiki page. The DRC83 defanged located here:
http://wiki.cyanogenmod.com/index.php/Latest_version#Defanged_DRC83
staunty said:
Why did you use "signed-dream-devphone-userbug-ota-14721"
I'm no pro but I used the base image that cyanogen recommends on his wiki page. The DRC83 defanged located here:
http://wiki.cyanogenmod.com/index.php/Latest_version#Defanged_DRC83
Click to expand...
Click to collapse
He used that because it is the proper image to use. A defanged file simply means that it has been rendered safe to download with no fear of infection. The link on his site is to the file used by the OP, so no worries there. Also, your radio is good, so do not worry about that either.
I have to ask, because you did not mention part of the process that should be happening. You flash the HTC image, then you do not reboot and flash the CyanogenROM. At this point you reboot. What happens? It should flash the radio, go to an HTC screen, stay for awhile, then reboot itself back to recovery where it gives a message regarding the cache being cleared. At this point you reboot for the actual boot process. Is this not happening for you?
cloverdale said:
He used that because it is the proper image to use. A defanged file simply means that it has been rendered safe to download with no fear of infection. The link on his site is to the file used by the OP, so no worries there. Also, your radio is good, so do not worry about that either.
I have to ask, because you did not mention part of the process that should be happening. You flash the HTC image, then you do not reboot and flash the CyanogenROM. At this point you reboot. What happens? It should flash the radio, go to an HTC screen, stay for awhile, then reboot itself back to recovery where it gives a message regarding the cache being cleared. At this point you reboot for the actual boot process. Is this not happening for you?
Click to expand...
Click to collapse
You are correct- after flashing CM the phone will flash the radio and reboot to the recovery screen where I will reboot again. Sorry for not including that detail.
Home process hanging in the beginning is not a problem, most people have that happenning. Eventhough home screen is shown, Android is still booting up, you just have to wait a little bit for everything to finish up.
Problems with stock apps usually indicate that something went wrong with instalation of the rom (i.e HTC 1.6 rom was not installed properly) so you may want to re-flash that again followed by CM rom of your choice.
Next time you phone reboots itself, try to get a log (there's more on how to do it in Cyan's thread), it's the only way to find out what happens.
Last, but not least, stock 1GB card is not advised for swap/apps2sd because if it's slow speed (it's class 2). Get one that's faster (class 6 preffered) and try that out, it may be the source of your problems after all.
Good luck.
how do i install this Cyanogen on my G1 with 1.6 firmware ?
simple007 said:
how do i install this Cyanogen on my G1 with 1.6 firmware ?
Click to expand...
Click to collapse
http://tinyurl.com/yjuy6u3
But in all seriousness
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod
This would work. Please use search, this is such a n00b question.
Did another fresh install, so far no issues.
I will get a log the next time I install to see if I can track down the issue.
Also had time to install Enoch 4.2.11.2 theme. <3 this theme.
I will be heading to Frys today to pick up some cooling fans for the old PC, I will take a look for new mini SD
thank you to everyone that responded.
Just got home from Frys Electronics.
Purchases an A-DATA 8GB Class 6 microSD.
wiping/flashing again.
I am having a hard time learning about the swap file part of all this... I can find guides on how to create a Swap Partition, but not sure how to make it work and/or optimize it.
So I created a 32MB Swap- Previously I read the commands to enable Swap through the terminal- "linux_swap_en=1" I have used this and it does indeed turn on swap, but is there some sort of command to optimize? I believe tweaking the swap files is adjusting the "swappiness"?
The other way I enabled the Swap file was from the spare parts menu- Enabling Compache enabled my Swap file. Does this need adjustment? for size? or any other parameters? Or is this kind of an auto on for Swap?
Sorry I am a total noob, and want to know if I am missing out, I just keep loving this phone more and more.
I will be buying Cyanogen some beer soon ^_^
I've played with swap a long time ago and never quite understood it neither. As of lately, I've been running 10mb hack (in the developement section) and it works great. If you're inclined to get the swap thing going I suggest you read this thread. This will give you an idea of how to enable and tweak swap-related tasks.
Glad to hear that you have original problems taken care of (so far at least).
Good luck.
I think I just may have bricked my phone...
I did all the steps stated in my first post while flashing to 4.2.12.2 and got things going great. Flashed Enoch's Theme 4.2.12.2. Everything was rocking.
Then today, it shut it self off, I rebooted. Got to Enoch load screen then shut off, tried it again, and it won't even get past the G1 splash screen. I have had this happen a few times before, where it would power off randomly and I had to pull the battery, wait like 5 minutes and then get into recovery and clear/flash again. Now I am getting into recovery but after a minute or so it just shuts itself off again.
Can't wipe, Can't flash, cant even get into Cam+power to flash back to previous RC...
Not really sure what to do at this point...
If I do manage to get it running again, I do wonder why its doing this.
I use Cachemate to clear my catche and task killer to kill apps. Could Cachemate be the culprit in this mess, its the only app that I own that uses root? Not sure what else to blame it on other than the G1 one being one big POS and is only good if you can even get a ROM to run on it. I am 5 minutes away from ordering a Nexus.
once again thanks in advance for any input you can provide.
D3AD PIX3L said:
I think I just may have bricked my phone...
I did all the steps stated in my first post while flashing to 4.2.12.2 and got things going great. Flashed Enoch's Theme 4.2.12.2. Everything was rocking.
Then today, it shut it self off, I rebooted. Got to Enoch load screen then shut off, tried it again, and it won't even get past the G1 splash screen. I have had this happen a few times before, where it would power off randomly and I had to pull the battery, wait like 5 minutes and then get into recovery and clear/flash again. Now I am getting into recovery but after a minute or so it just shuts itself off again.
Can't wipe, Can't flash, cant even get into Cam+power to flash back to previous RC...
Not really sure what to do at this point...
If I do manage to get it running again, I do wonder why its doing this.
I use Cachemate to clear my catche and task killer to kill apps. Could Cachemate be the culprit in this mess, its the only app that I own that uses root? Not sure what else to blame it on other than the G1 one being one big POS and is only good if you can even get a ROM to run on it. I am 5 minutes away from ordering a Nexus.
once again thanks in advance for any input you can provide.
Click to expand...
Click to collapse
This sounds like a hardware issue, and not a bricking. Try a new battery, this may fix it, otherwise I am not sure.
cloverdale said:
This sounds like a hardware issue, and not a bricking. Try a new battery, this may fix it, otherwise I am not sure.
Click to expand...
Click to collapse
I will try the other battery I have at home in my other G1 and report back
D3AD PIX3L said:
I will try the other battery I have at home in my other G1 and report back
Click to expand...
Click to collapse
I tried it.
Same issue.
I did noticed that the batter pins were abnormal... One was sticking out more which was normal according to my other G1, the other 2 were shoved down. I tried to mess with the 2 to get them to pop back up to their normal position with no luck.
I am thinking about ordering a replacement.
okay, so tonight I am going to take the G1 apart and see if I can get those pins straightened out. Not sure if it will help, but its better than declaring it a paper weight.
will post the outcome.
Just out of curiousity (and I don't exactly know where I'm going with this) will your phone turn on and stay on if you plug it in (usb or charger)?
borodin1 said:
Just out of curiousity (and I don't exactly know where I'm going with this) will your phone turn on and stay on if you plug it in (usb or charger)?
Click to expand...
Click to collapse
It does not.
I think i will take both phones apart and swap out the screen since that is why I don't use the one. I watched a visual walkthrough seems easy enough
Has anyone disassembled their G1 and reassembled successfully? any tips?
Started to take apart the non-cracked bricked G1.
Once I removed the motherboard and started on the next step, I realized how bad it would be to end up getting the parts swapped and then have it not work... Put it back together and loaded up the latest Cyanogen on my working cracked G1.
*shrugs* it will do for now.
Waiting till the end of next month to order my Nexus 1, then I will have fun ripping apart both G1's and hopefully end up with one great looking, fully functional G1 to possibly sell or keep as an extra phone...
thanks to all who replied!
Howdy all,
My phone broke, so I'm back on the hero. I forget any and all stuff of how to's on this phone so bear with me. Basically, I'm a noob for the hero now.
So, recently, I followed the Cyanogenmod Full Update wiki guide, rooting it with the rageagainstthecage exploit. However, after my first time, my phone would eventually be so slow that it would seem to freeze. It's just so so so so slow. It's unusable. The lockscreen would come up, and i would touch the lock icon, which would vibrate. I would slide to unlock, but the screen doesn't react. at all. then it would vibrate, indicating an unlock, but the screen doesn't change at all. Occasionally, I'm able to accidentally enter an app, but I cannot read texts, answer calls, or reply to texts. Or do anything else.
Occasionally, I'll get a "app is unresponsive" message, but I can't force close/wait.
Oh, btw, when this happens, I can't get into my recovery (CWM 3.0.0.5). Also, I don't see the boot animation.
I have done an RUU stock reset, which fixed it once. The problem occurred again while on CM7, and I did another RUU reset, but the problem is now consistent throughout the stock sense. Omigawd what do i do?
Since I am now on stock that has usb debugging disabled, I can no longer access adb.
I am currently on absolute stock (fresh-out-of-the-box like), not rooted, and have S-OFF.
I am fairly well versed in fastboot and adb commands. When I try to access the recovery, I am sent to a black screen. When I plug in while in recovery and do "adb devices," I get my model number with the message "offline."
I AM OUT OF IDEAS! Someone. Please helpppp.
Thank you for reading. Thank you for helping.
Try a re-root with regaws rooter (the old version if you can get it) i swear by it. or Z4 root. once you have reestablished root, get Rom manager and flash the 2.4.0.7 recovery. then in rom manager go to downloads and get the cyanogen mod download of your choice( myself i prefer 7.0.3) and flash. you should be good to go from there.
as far as your adb it looks like your pc either isnt recocnizing your phone or you dont have the proper drivers installed.
Bout all i can tell ya ,one noob to another,,,
BTW, if you want to start completly from scratch, since your s-off,you can get a HERCIMG.img i think in the development sectin of this forum that is flashable from fastboot,,,try that ,,,Later man and good luck
Luckily you are S-Off. Can you put a HERCIMG.zip on the root of your sd card with a recovery (even CWM 2.5.0.7 will do) and then maybe try downloading another rom. Maybe you have a bad download. I am a big fan of Jaybob's TeamHeroc Rom which is a great CM7ish type of rom. Make sure that you format boot, cache, data, and system (I do it 3 times for each to make sure that it is really wiped) before you flash whatever rom you choose. You might have some leftover stuff that is causing some issues. Just wiping data and cache might not be enough. Here is a HERCIMG with a 4.0.1.4 recovery that you can load from H-Boot. I'm pretty sure that it's the Orange Recovery that I use.
hugabu said:
Howdy all,
My phone broke, so I'm back on the hero. I forget any and all stuff of how to's on this phone so bear with me. Basically, I'm a noob for the hero now.
So, recently, I followed the Cyanogenmod Full Update wiki guide, rooting it with the rageagainstthecage exploit. However, after my first time, my phone would eventually be so slow that it would seem to freeze. It's just so so so so slow. It's unusable. The lockscreen would come up, and i would touch the lock icon, which would vibrate. I would slide to unlock, but the screen doesn't react. at all. then it would vibrate, indicating an unlock, but the screen doesn't change at all. Occasionally, I'm able to accidentally enter an app, but I cannot read texts, answer calls, or reply to texts. Or do anything else.
Occasionally, I'll get a "app is unresponsive" message, but I can't force close/wait.
Oh, btw, when this happens, I can't get into my recovery (CWM 3.0.0.5). Also, I don't see the boot animation.
I have done an RUU stock reset, which fixed it once. The problem occurred again while on CM7, and I did another RUU reset, but the problem is now consistent throughout the stock sense. Omigawd what do i do?
Since I am now on stock that has usb debugging disabled, I can no longer access adb.
I am currently on absolute stock (fresh-out-of-the-box like), not rooted, and have S-OFF.
I am fairly well versed in fastboot and adb commands. When I try to access the recovery, I am sent to a black screen. When I plug in while in recovery and do "adb devices," I get my model number with the message "offline."
I AM OUT OF IDEAS! Someone. Please helpppp.
Thank you for reading. Thank you for helping.
Click to expand...
Click to collapse
I like Regaw's for rooting too. I used it the last time I did an RUU.
Isnt that what I said just before you ??? Lol
BTW Pilot, Where have you been? One of the most active members of the Heroc forum and all of a sudden ,poof, gone like a fart in the wind ! And then as if by magic, Poof, your back.I knew youd return, they always always return to the ol reliable Heroc. Good to see you around again bud, Later man,,,
Sent from my HERO200 using xda premium
hey guys just got back from vacation. Thanks for all your feedback. I switched phones to a temporary one now. I don't really feel like switching back to the hero cuz it costs money to activate phones. Also, I talked to an app developer about my problems. He told me that 1. the phone is way to old to be running gingerbread. Some nasty software probably carried over from my last flash onto the stock RUU flash. and that 2. whenever the problem occurs, I should let the battery drain before I do anything. Turns out, whenever the problem happens nowadays, I just let the battery drain and its all fixed. OKAY WTF. But all smiles now. Its my ipod-touch-like device now. I used regaws root.
THANKS GUYS SO MUCH.
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 had a problem a few days ago that i was having problems after rooting my phone so i brought it back to stock using RSD Lite and then tried to flash a new rom on the phone and it said my phone was not unlocked so i downloaded The Myth Tools and unlocked it that way but I am wondering if i messed it up because i did not really know what i was doing i just tried to see if i could figure it out and it seemed like it worked until today. I flashed Touchwiz on there a couple days ago and it worked fine i made a backup wiped the cache,dalvik cache and system now today it randomly freezes and is now stuck on the bootloader unlocked screen. I can hold down power and volume up and boot into recovery which is ClockworkMod Recovery v6.0.3.6 touch and it also says under that in the bottom right of the screen Warning No file_contexts now i dont know if it has always said that since i flashed this recovery or just started. I also once again tried wiping the cache and dalvik cache because i read it on another post of someone stuck on this screen so i tried that and rebooted it still the same result stuck on bootloader screen. At this point i have no idea what to do. If i have to start over from stock because i messed up unlocking it or completely wipe it again and reflash touchwiz or another rom. I have had nothing but problems since rooting this phone I have gone through atleast 6 to 8 roms because every single one of them gives me a problem somehow. The most common is when i make a call or recieve one and i put the phone up to my ear I know the sensor turns off the screen but when i take it away to end it or do something its completely off or apps force closing all the time still after i did the stock reflash. I am starting to wonder if its just my phone because everyone else i read about has no problems with there phones mine nothing but problems. Please if someone could help me or walk me through this process it would be greatly appreciated I love the things it can do with custom roms but i just wish it would run smooth.
bpc87 said:
I had a problem a few days ago that i was having problems after rooting my phone so i brought it back to stock using RSD Lite and then tried to flash a new rom on the phone and it said my phone was not unlocked so i downloaded The Myth Tools and unlocked it that way but I am wondering if i messed it up because i did not really know what i was doing i just tried to see if i could figure it out and it seemed like it worked until today. I flashed Touchwiz on there a couple days ago and it worked fine i made a backup wiped the cache,dalvik cache and system now today it randomly freezes and is now stuck on the bootloader unlocked screen. I can hold down power and volume up and boot into recovery which is ClockworkMod Recovery v6.0.3.6 touch and it also says under that in the bottom right of the screen Warning No file_contexts now i dont know if it has always said that since i flashed this recovery or just started. I also once again tried wiping the cache and dalvik cache because i read it on another post of someone stuck on this screen so i tried that and rebooted it still the same result stuck on bootloader screen. At this point i have no idea what to do. If i have to start over from stock because i messed up unlocking it or completely wipe it again and reflash touchwiz or another rom. I have had nothing but problems since rooting this phone I have gone through atleast 6 to 8 roms because every single one of them gives me a problem somehow. The most common is when i make a call or recieve one and i put the phone up to my ear I know the sensor turns off the screen but when i take it away to end it or do something its completely off or apps force closing all the time still after i did the stock reflash. I am starting to wonder if its just my phone because everyone else i read about has no problems with there phones mine nothing but problems. Please if someone could help me or walk me through this process it would be greatly appreciated I love the things it can do with custom roms but i just wish it would run smooth.
Click to expand...
Click to collapse
You can enter Recovery, right? What happens if you install a .zip? Right now your phone is stuck in the Motorola logo?
it wouldnt even go to the motorola symbol it just stayed in the first screen where it said your bootloader was unlocked. It would go into recovery and i tried to reboot it and it gave me the same screen. So i wiped it completely cache, dalvik cache and system and shut it off. Last night i plugged it into my comp to put it back to stock and it started up like normal and booted into a rom like i just installed one where you have to fill in all that info and setup wifi if you choose too which was weird because it wouldnt do anything before. Anyways i used RSD Lite and put it back to stock and thats where it is now. I am reading the Atrix HD Beginners Guide written by skeevydude right now and I am thinking about trying to root it again with the help of that article and maybe I will have better luck doing it that way hopefully haha maybe I can finally get a rom to run the way everyone else says they run smooth and fast. Any input though to help me would be much appreciated i am definitely new at this and want to learn its something that interests me alot ever since a friend rooted my phone the first time i cant stop playing with it I was trying to make it as fast as I can I had ProBam on there i think its called ive had touchwiz, motoblur, carbon, liquidsmooth, MIUI, and a couple others I cant remember also had a custom kernel i flashed on there and Pure performance so as you can see I have been trying everything.
bpc87 said:
it wouldnt even go to the motorola symbol it just stayed in the first screen where it said your bootloader was unlocked. It would go into recovery and i tried to reboot it and it gave me the same screen. So i wiped it completely cache, dalvik cache and system and shut it off. Last night i plugged it into my comp to put it back to stock and it started up like normal and booted into a rom like i just installed one where you have to fill in all that info and setup wifi if you choose too which was weird because it wouldnt do anything before. Anyways i used RSD Lite and put it back to stock and thats where it is now. I am reading the Atrix HD Beginners Guide written by skeevydude right now and I am thinking about trying to root it again with the help of that article and maybe I will have better luck doing it that way hopefully haha maybe I can finally get a rom to run the way everyone else says they run smooth and fast. Any input though to help me would be much appreciated i am definitely new at this and want to learn its something that interests me alot ever since a friend rooted my phone the first time i cant stop playing with it I was trying to make it as fast as I can I had ProBam on there i think its called ive had touchwiz, motoblur, carbon, liquidsmooth, MIUI, and a couple others I cant remember also had a custom kernel i flashed on there and Pure performance so as you can see I have been trying everything.
Click to expand...
Click to collapse
Good to know that is working now. I would recommend you to take it easy. Don't flash it everyday, use and know a ROM, then you can decice which one is better for you. Be sure to have a backup if something fails, also save a .zip (ROM) in the SD card. Just FYI, I haven't come across a ROM that is 100% smooth (Not even HoloBlur). They are very good, but maybe not the smooth level that you think.
Hey bpc87, I was wondering if you were able to get a custom ROM up & running after all that & if so, how?
I've had the same issue whenever I tried installing a ROM. It would install & boot okay the first time, but when rebooting, it would get stuck at the "bootloader unlocked" warning screen. I went back to stock using Myth Tools & now, after installing a ROM, a reboot leaves me stuck at the "Motorola Dual Core" screen.
Any help from you & the community would be awesome!
bsmitty said:
Hey bpc87, I was wondering if you were able to get a custom ROM up & running after all that & if so, how?
I've had the same issue whenever I tried installing a ROM. It would install & boot okay the first time, but when rebooting, it would get stuck at the "bootloader unlocked" warning screen. I went back to stock using Myth Tools & now, after installing a ROM, a reboot leaves me stuck at the "Motorola Dual Core" screen.
Any help from you & the community would be awesome!
Click to expand...
Click to collapse
dude i havent even tried to since i flashed it back to stock because i dont want the same thing to happen. The last time I just went to turn on bluetooth and it just rebooted on its own. Not too mention the other problems I had I am not going to mess with it again until I read more on how to root it because it is either that or my phone.
Yeah, I understand. Hopefully then some other users who run into the same problem will investigate & figure out what's goin on. I've seen several other threads of people who've encountered the same thing but unfortunately no answer. For me, this is the determining factor as to whether I end up keeping the AHD or not.
Thanks
I have the same problem. Everytime in moto logo after rebooting, but with stock firmware all ok. Is there any solution for this problem?
ok, so i rooted my htc one to stock, using an ruu that was suggested by a user on here last weekend. it all seemed good, but on sunday, while i was working my phone rebooted itself, for no reason, however i thought it might have been because of a root app i had installed. i had to put it in recovery mode, and wait until i was off work to fix it, by reflashing it(i hadnt had a chance to make a backup in twrp). well i now have a backup of my phone, so yay, but and it hadnt forced a reboot until just now. the thing is it had been good all day today, and i had tried installing the MIUI Rom following a thread on here. the rom worked and all, but it also had issues such as data not wanting to connect, freezing up etc, so i went and returned to my backup i made today(when everything was perfect) and i made a phone call, and after the call the phone rebooted. and its back to its old ways. im restoring again to see if it helps, but does anyone know why it does that?
when my phone did that it was cause I had the unknown baseband issue. Could be worth a try to see if thats your issue.
raynefr said:
ok, so i rooted my htc one to stock, using an ruu that was suggested by a user on here last weekend. it all seemed good, but on sunday, while i was working my phone rebooted itself, for no reason, however i thought it might have been because of a root app i had installed. i had to put it in recovery mode, and wait until i was off work to fix it, by reflashing it(i hadnt had a chance to make a backup in twrp). well i now have a backup of my phone, so yay, but and it hadnt forced a reboot until just now. the thing is it had been good all day today, and i had tried installing the MIUI Rom following a thread on here. the rom worked and all, but it also had issues such as data not wanting to connect, freezing up etc, so i went and returned to my backup i made today(when everything was perfect) and i made a phone call, and after the call the phone rebooted. and its back to its old ways. im restoring again to see if it helps, but does anyone know why it does that?
Click to expand...
Click to collapse
Link to the MIUI ROM? Only install ROMs that you see in the Sprint HTC One section, not in the International HTC One section. Try flashing the latest radio to fix the phone call problem.
If that root app was SuperSU, then flash this zip.
StormyNight said:
Link to the MIUI ROM? Only install ROMs that you see in the Sprint HTC One section, not in the International HTC One section. Try flashing the latest radio to fix the phone call problem.
If that root app was SuperSU, then flash this zip.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2523987
the rom i use is from the sprint htc one m7 forums, it worked and i was able to make a call, but the screen hung alot and my buttons became unresponsive due to the assist thingy. upon a restart, i didnt have data connections. im kind of nervous about messing with my radio, because even though my signal sucks where i live, i dont want to mess up and not have a signal. i updated the SuperSU (i was using 1.87 and i flashed it to 2.02) hopefully i see no issues, but it usually takes a day and a half.
raynefr said:
http://forum.xda-developers.com/showthread.php?t=2523987
the rom i use is from the sprint htc one m7 forums, it worked and i was able to make a call, but the screen hung alot and my buttons became unresponsive due to the assist thingy. upon a restart, i didnt have data connections. im kind of nervous about messing with my radio, because even though my signal sucks where i live, i dont want to mess up and not have a signal. i updated the SuperSU (i was using 1.87 and i flashed it to 2.02) hopefully i see no issues, but it usually takes a day and a half.
Click to expand...
Click to collapse
Flashing radio is your best bet. Verify the md5 before flashing and you'll be fine.
Sent from my kangaroo powered Inverted ViperONE using Tapatalk 2