Database Users

upgraded to FRG83D and now Amon Ra will not load

upgraded to FRG83D and now Amon Ra will not load

Sounds like you might have lost root, can you confirm or deny?

I also lost root when updating sic to FRG83D. I was able to reinstall RA 2.0, make a Nandroid BU of the stock ROM, then reload CM-6.1. I'll wait for Gingerbread

krabman said:
Sounds like you might have lost root, can you confirm or deny?
Click to expand...
Click to collapse
confirmed 1,2,3,4,5,6,7,8,9,10

hommiedaklown said:
confirmed 1,2,3,4,5,6,7,8,9,10
Click to expand...
Click to collapse
Do you have unlocked bootloader?
If not, then...hmmmm :/
Does Super One Click work on FRG83D?

SuperOneClick was reported multiple times to work.
Reading through the front page of Q&A would have solved the OP his problem, together with leaving XDA some more free bytes in the cyberspace.

Of course you lost Amon RA, they probably create the two scripts which check for and restore stock recovery. If those two scripts are there at (boot time?) it restores stock recovery and you get the /!\ symbol.
So it restores the stock recovery and "unroots" the phone, but you can re-root with the Super One Click: http://forum.xda-developers.com/showpost.php?p=9369447&postcount=1323
Once you're root again, follow the instructions to install Amon. Don't just run flash_image, you gotta do the full set of instructions or it'll restore the stock recovery again.

ctbear said:
Do you have unlocked bootloader?
If not, then...hmmmm :/
Does Super One Click work on FRG83D?
Click to expand...
Click to collapse
yes i have an unlocked bootloader
Now I have HBOOT-0.35.0017
RADIO-04.06.00.12_7

hommiedaklown said:
yes i have an unlocked bootloader
Click to expand...
Click to collapse
Then just reflash the recovery.. The only reason you have to do anything "special" is if you don't want to unlock the boot loader.

btw: is it normal that you get the excmalation mark everytime you want to access the stock recovery?
i also lost amon ra during the frg83d update, but thats what i wanted because i only ust stock roms and want to have OTA functionality. (even though i found out this would have been possible with amon ra too).
i can't remember is the exclamation mark screen was normal for stock recovery...

Yes it's normal. To access the menu you hold the power button and hit vol+

When Superboot for 2.3.4(GRJ22) come out?

Here only for 2.3.3(GRI40),
android.modaco.com/content/google-nexus-one-nexusone-modaco-com/298782/08-mar-superboot-erd79-gri40-rooting-the-nexus-one/
When Superboot for 2.3.4(GRJ22) Release? Or any other way root Mexus one?

bleakwind said:
Here only for 2.3.3(GRI40),
android.modaco.com/content/google-nexus-one-nexusone-modaco-com/298782/08-mar-superboot-erd79-gri40-rooting-the-nexus-one/
When Superboot for 2.3.4(GRJ22) Release? Or any other way root Mexus one?
Click to expand...
Click to collapse
Never heard of superboot, but you can try my guide here: http://forum.xda-developers.com/showpost.php?p=13762825&postcount=17
It's not a 'one-click' solution, but that's how I kept my root with 2.3.4.

Any way Not need to return FRG33?

Or some version of Froyo, no, as of now you HAVE to. When Gingerbreak works (if it ever does) for 2.3.4, it will be hard to miss.

bleakwind said:
Any way Not need to return FRG33?
Click to expand...
Click to collapse
flash custom recovery via adb, flash su from recovery, then reboot. The stock ROM will erase the custom recovery and replace it with a stock image. Your phone will be the same as it would be with superboot. Stock, rooted ROM with stock recovery.

ATnTdude said:
flash custom recovery via adb, flash su from recovery, then reboot. The stock ROM will erase the custom recovery and replace it with a stock image. Your phone will be the same as it would be with superboot. Stock, rooted ROM with stock recovery.
Click to expand...
Click to collapse
Not quite, as superboot also replaces your boot image with an insecure boot image, which su does not.

Granted, but I highly doubt the OP really needs insecure boot given that he thinks downgrading is too much of a hassle. Without more info, I assume he just wants root in order run Titanium Backup , or Drocap, AdFree or some other market app that needs root to work for (what I also assume is) legit, non pirating reasons.
Just going from my own experiences, the easy one-click nature of superboot is a safe first step into modding and rooting for those afraid to brick their phone. I get the attraction and understand the reasoning, but you have to take the training wheels off eventually.

I was successful root nexus one...
And I use install-recovery.sh put app to ext(4G), And everything looks well...
http://forum.xda-developers.com/showpost.php?p=14106175&postcount=60

[Q] OTA update.zip

Anyone have an OTA update.zip? I've got a bricked N7 that will not successfully boot after flashing back to stock, custom ROMs or after flashing factory images. Last thing to try is to see if the stock recovery will flash an official update.zip.

slickie88 said:
Anyone have an OTA update.zip? I've got a bricked N7 that will not successfully boot after flashing back to stock, custom ROMs or after flashing factory images. Last thing to try is to see if the stock recovery will flash an official update.zip.
Click to expand...
Click to collapse
Here ya go.
signed-nakasi-JRO03C-from-JRN84D.zip
signed-nakasi-JRO03D-from-JRO03C.zip

Thanks, wmoore. Tried both of them and I'm still unable to unbrick this thing.

slickie88 said:
Thanks, wmoore. Tried both of them and I'm still unable to unbrick this thing.
Click to expand...
Click to collapse
Have you seen this guide?

Boot into stock recovery and do a wipe

wmoore said:
Have you seen this guide?
Click to expand...
Click to collapse
Yeah, I've already been through all of that. I can flash back to stock using any of the factory images and it still results in a never ending boot animation loop. ADB, using any of the kits out there, it doesn't matter.

Lennyuk said:
Boot into stock recovery and do a wipe
Click to expand...
Click to collapse
Thanks for the suggestion, but I've already been there done that more times that I can count. At least now I know ADB like the back of my hand. I've flashed stock and relocked the bootloader and have a replacement coming this week. I've truly bricked an unbrickable device.

Back to Factory with no computer access.

I everyone!
I just tried to connect my Nexus 4 to my windows 8.1 laptop and the phone is not recognised by the PC. It gives me Code 43 error, I tried everything, form fresh driver install to cable change. I also tried on another W7 laptop and nothing pops up there. The phone charges but in Device Manager it is not listed under Google ADB devices but appears with an exclamation mark under USB controllers saying Device Descriptor Request Failed. I fear it is an hardware problem and RMA is the only option left. However, my phone is Rooted, Stock but with modified build.prop, with TW touch recovery and unlocked. Since I have no access to ADB I cannot use the Android SDK tools or anything to flash the factory img. Is there any way in which I could flash back the sock image and lock the bootloader via recovery only?
Thanks everyone :crying::crying:

you dont need adb to flash the factory img. you need fastboot to flash it, via your bootloader. but, fastboot still needs to see your device, so thd driver still nedds to be installed.

Wouldnt it be possible to flash the 4.3 stock rom zip in his custom recovery, root it and flash the stock recovery with flashify, and then unroot the device?
Sent from my Nexus 4 using xda app-developers app

Thibaultvw said:
Wouldnt it be possible to flash the 4.3 stock rom zip in his custom recovery, root it and flash the stock recovery with flashify, and then unroot the device?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
This was what I was thinking, however, the main issue would be locking the bootloader again
simms22 said:
you dont need adb to flash the factory img. you need fastboot to flash it, via your bootloader. but, fastboot still needs to see your device, so thd driver still nedds to be installed.
Click to expand...
Click to collapse
I dont think is a driver problem, I had driver issues before but i got different errors and solved them easily. I do believe is an hardware failure this time

c0sk said:
This was what I was thinking, however, the main issue would be locking the bootloader again
I dont think is a driver problem, I had driver issues before but i got different errors and solved them easily. I do believe is an hardware failure this time
Click to expand...
Click to collapse
READ THIS 1st
http://forum.xda-developers.com/showthread.php?t=2010312
Scroll down to the 2nd post.

mrhiab said:
READ THIS 1st
http://forum.xda-developers.com/showthread.php?t=2010312
Scroll down to the 2nd post.
Click to expand...
Click to collapse
Thanks, exactly what I was looking for! :victory:
However, since I am already on stock andshould have a backup of the build.prop (i just added a line to get rid of the on screen buttons) would you recommend flashing everything again or just lock bootloader, unroot and flash stock recovery only?

c0sk said:
Thanks, exactly what I was looking for! :victory:
However, since I am already on stock andshould have a backup of the build.prop (i just added a line to get rid of the on screen buttons) would you recommend flashing everything again or just lock bootloader, unroot and flash stock recovery only?
Click to expand...
Click to collapse
Restoring the original build.prop, locking the bootloader, remove root and flash stock recovery will be just fine.

efrant said:
Restoring the original build.prop, locking the bootloader, remove root and flash stock recovery will be just fine.
Click to expand...
Click to collapse
Ok! I did a very stupid thing, I did restore my build.prop but without any backup files. The system does not boot up now! Root has been removed and bootloader locked, however, the custom recovery is still there and I did not copy the stock image! Is there any other way in which I could restore the stock recovery or am I screwed??

c0sk said:
Ok! I did a very stupid thing, I did restore my build.prop but without any backup files. The system does not boot up now! Root has been removed and bootloader locked, however, the custom recovery is still there and I did not copy the stock image! Is there any other way in which I could restore the stock recovery or am I screwed??
Click to expand...
Click to collapse
When you restored your build.prop, did you set the proper permissions, i.e., 644? If not, does your recovery allow you to do so? Try it and see if you boot.
Sent from my Nexus 5 using Tapatalk 2

efrant said:
When you restored your build.prop, did you set the proper permissions, i.e., 644? If not, does your recovery allow you to do so? Try it and see if you boot.
Sent from my Nexus 5 using Tapatalk 2
Click to expand...
Click to collapse
I fixed that problem in a different way, more barbaric but effective. I booted it up and managed to get JDQ39 files on the phone via dropbox: odexed image, boot and recovery. I flashed the first 2 (wanted to keep the recovery for safety and flash the stock one at a second stage). Booted successfully and removed root via SuperSu settings. Once flashed stock recovery, am I right to assume it will be completely stock and therefore ready for RMA? Moreover, can I accept OTA since is fully stock?
Thanks!!!!!
edit: Su installer app was there after flashed recovery and did factory reset

c0sk said:
I fixed that problem in a different way, more barbaric but effective. I booted it up and managed to get JDQ39 files on the phone via dropbox: odexed image, boot and recovery. I flashed the first 2 (wanted to keep the recovery for safety and flash the stock one at a second stage). Booted successfully and removed root via SuperSu settings. Once flashed stock recovery, am I right to assume it will be completely stock and therefore ready for RMA? Moreover, can I accept OTA since is fully stock?
Thanks!!!!!
edit: Su installer app was there after flashed recovery and did factory reset
Click to expand...
Click to collapse
The way you removed SuperSU must have not worked properly. (I've never tried doing it from the SuperSU settings.) In any case, there's nothing more you can do now, so might as well send it in for RMA.

[Q] Since 4.4 upgrade, can't reboot into TWRP from Goo.IM

Has anyone else had this problem? I am still able to get into recovery with the power and volume button.

thorin33 said:
Has anyone else had this problem? I am still able to get into recovery with the power and volume button.
Click to expand...
Click to collapse
Did you OTA?, if you OTA 4.4 or sideload you loose root and custom recovery. You need to root again and install Custom recovery.

zcucurullo said:
Did you OTA?, if you OTA 4.4 or sideload you loose root and custom recovery. You need to root again and install Custom recovery.
Click to expand...
Click to collapse
I re-rooted and installed the custom recovery. I think I may unroot and go back to stock, reset and start again.

thorin33 said:
I re-rooted and installed the custom recovery. I think I may unroot and go back to stock, reset and start again.
Click to expand...
Click to collapse
That did the trick. Not sure what happened before.

probably didnt install the custom recovery right, happens all the time if you didnt flash the image via command lines......
I bricked my device a couple times trying to be lazy and use apps to install recovery, BAD IDEA, now i am sticking with command lines