ok I lost root access some how flashing the update.
What i did was i flash the ere27 I downloaded from rom manager and then applied it through the gui and then flashed the froyo update through recovery.
I have froyo now but I lost my root along with custom recovery. How do I get my root back?
I tried to flash RA recovery and i get an error saying can not load. I'm lost and have no more ideas as to how to gain root.
MFK DGAF said:
ok I lost root access some how flashing the update.
What i did was i flash the ere27 I downloaded from rom manager and then applied it through the gui and then flashed the froyo update through recovery.
I have froyo now but I lost my root along with custom recovery. How do I get my root back?
I tried to flash RA recovery and i get an error saying can not load. I'm lost and have no more ideas as to how to gain root.
Click to expand...
Click to collapse
why don't you just start over, from the superboot blah blah blah. should only take 20minutes from scratch
which superboot do i use? sorry i've never used superboot before.
http://forum.xda-developers.com/showthread.php?t=688000
MFK DGAF said:
ok I lost root access some how flashing the update.
What i did was i flash the ere27 I downloaded from rom manager and then applied it through the gui and then flashed the froyo update through recovery.
I have froyo now but I lost my root along with custom recovery. How do I get my root back?
I tried to flash RA recovery and i get an error saying can not load. I'm lost and have no more ideas as to how to gain root.
Click to expand...
Click to collapse
Here is Modaco's 2.2, u will not loose Root (once u get it back ). http://android.modaco.com/content/g...o-com/309299/how-to-upgrade-your-n1-to-froyo/
Same issues
MFK DGAF said:
ok I lost root access some how flashing the update.
What i did was i flash the ere27 I downloaded from rom manager and then applied it through the gui and then flashed the froyo update through recovery.
I have froyo now but I lost my root along with custom recovery. How do I get my root back?
I tried to flash RA recovery and i get an error saying can not load. I'm lost and have no more ideas as to how to gain root.
Click to expand...
Click to collapse
Im having the same problem.. I've re flashed & rooted my phone from superboot in the process I've seen strange things happen.. Like home key not functioning & power button.. LOL.. I don't even have a recovery image once i upgrade to 2.2... the first time i installed 2.2 using Cyanogen advice everything went flawlessly I was even able to flash his kernel mod to get super user permission... Steps took: Rom manger used to flash ere27 and then stock 2.2.. I dam near bricked my phone making changes to my build.props to enable viewing of protected apps... Now I'm stuck on stock froyo with an outdated slow market place version 1.82
Related
I am in the UK. I wanted to root my G1 so I did the 1Click Root method. I had no problem at all except that I didn't get internal root only the external root needed for updating the Rom.
When I updated my Recovery with Rav.1.2.0g it gave me an excellent menu (that also helps with SD Partition) that was overwritten. I again updated the revovery wit Rav.1.2.1g and that to has been over written with the standard recovery. Perhaps I should have wiped first?
A few points that might help. I used quick format and the Dreaimg was not high case and there was no problem. The main problem I see is finding an RC7 or RC29 image that is not corrupted possibly during download.
I am unable to run apps that require root so how do I now get internal root. I am happy to go through the 1Click method as it is so good and easy.
Isn't Ra's recovery image for Magic 32A's? If so, you need to 1-click root again and keep your Cyanogen 1.4 recovery image, as that's what gives you good root.
Please this in the correct area(Q&A).
prettyboy85712 said:
Please this in the correct area(Q&A).
Click to expand...
Click to collapse
Moved to Q&A
Ra's recovery does work on the g1, I believe it is meant for the 32b's like the mytouch. Anyways....did you flash to a custom rom, if not than the stock update or roms will cause you to lose root by putting the security back on and rewriting the stock recovery. If you are on a modded rom, you should have superuser, to check if you have root go into terminal and type su, if it says permission denied than you don't have root, if you get a # than you do
Permission Denied
gridlock32404 said:
Ra's recovery does work on the g1, I believe it is meant for the 32b's like the mytouch. Anyways....did you flash to a custom rom, if not than the stock update or roms will cause you to lose root by putting the security back on and rewriting the stock recovery. If you are on a modded rom, you should have superuser, to check if you have root go into terminal and type su, if it says permission denied than you don't have root, if you get a # than you do
Click to expand...
Click to collapse
As I recall after doing the 1Click method I did check su and its was permission denied. That was why I did not update the Rom until I found out more about internal and external root. I did try the SuperUser app but it would not work on a non rooted G1.
As for the Rav Recovery image. Part of the unlockr 1Click states to ignore the recovery image supplied and use the Rav one as it is compatable with future updates.
My problem now then is how to back up what is on the phone?
Follow the guide in my sig for one click root ,if you have a g1/dream.
I have never used the one click but what what I hear, it does somehow overwrite the security so after you use it than go right into recovery and flash a custom rom right than and there or you will lose root<just my understanding from what I read and what I do know already> so reuse the recovery flasher again, make sure you got a rom ready to go and give it another shot, I would keep cyan's recovery or al least put it back on after you use ra's just so you have a terminal to cover your ass
OK, im losing it. I have a FRF91 Bootloader unlocked N1. I am trying to install the RA Recovery, so i can root. Everytime i have used ADB and installed RA recovery, i get the completed message, but when i attempt to run the recovery, i get stuck with the android and the !.
Will the RA Recovery that worked for EPE34B work with FRF91? Or is there another recovery version?
same issue, so I suspect its a fix somewhere on the forums. I shall go look and will post back here if I find something
EDIT: Its a rooted FRF91 found here. Appears to give root then RA should work. I'm trying it to see for myself...
Direct download: http://www.multiupload.com/L69XPNYDWP
thread: http://htcpedia.com/forum/showthread.php?t=3033
EDIT EDIT: Dont work if your already on FRF91. Nevermind then....we must wait for a Superboot to be released.
http://forum.xda-developers.com/showthread.php?t=686627
Use this, it should give you root back. Shouldn't matter what version of Froyo you are on.
Markdental said:
http://forum.xda-developers.com/showthread.php?t=686627
Use this, it should give you root back. Shouldn't matter what version of Froyo you are on.
Click to expand...
Click to collapse
The very last sentence on that post...
cyanogen said:
You need to reflash your recovery with Clockwork or Amon first if you installed from the OTA.
Click to expand...
Click to collapse
..my problem is that i cannot install Amon over my stock FRF91 ROM. That is the first step for root, and yet i cannot do it.
Are you flashing the recovery, then rebooting? Try it without rebooting.
When I did this last night with FRF91, I noticed that after flashing the stock recovery would return if I rebooted before actually running the Amon RA recovery I had just flashed.
You have to delete/rename 2 files in /system to stop the phone reverting to stock recovery. They are install-recovery.sh and recovery-from-boot.p
I have been trying to update my rooted 2.2 FRF50 to FRF91 for a day noe and all I get is error messages
E: not verified files
I just got an OTA and it's doing the same and stuck at RA recovery with same message. I reboot and still on FRF50. Any ideas?
Nexus One using XDA App
Oh for the love of jeebus, not again. You want OTA, lose the custom recovery.
Rusty! said:
You have to delete/rename 2 files in /system to stop the phone reverting to stock recovery. They are install-recovery.sh and recovery-from-boot.p
Click to expand...
Click to collapse
that might be pretty handy come the next OTA update. So as long as i remove the .sh and .p the phone shouldnt be able to find them to apply them when i reboot. Perfect.
Thanks!
..this should be somewhere in the stickies..
I was rooted and running CM6. I tried getting back to a stock 2.2 by flashing the stock image from Rom Manager. I downloaded the 2.2 update from google and it wouldn't update. In the system menu or bootloader I got a little format happy with boot/system and so on. Anyway, doing a nandroid now. Is there anyway to get this phone back to the kernel it shipped with?
You have to flash it with the stock recovery.
I've been using that Universal androot.http://www.androidappjudge.com/2010/08/one-click-root-application-universal_10.html I tried flashing stock 2.2 and I didn't read the two options, I just clicked them and kept going not realizing that I flashed the rooted, superuser version. Does this mean that I'm now rooted forever? When I try flashing stock 2.2 with rom manager It stops @ the android and /!\ symbol. Now it's even doing this with CM.
I'm now wondering how to get rid of whatever crap might be floating around on my phone and why it may not be flashing anymore?
there is nothing wrong, rooting allows you the ability to have super administrative rights. Since all you have done is grant yourself admin rights, the recovery should be the same.
Something is wrong. I can't Fix Permissions or flash anything.
Man, I should have just left it alone.
glwinkler said:
Something is wrong. I can't Fix Permissions or flash anything.
Man, I should have just left it alone.
Click to expand...
Click to collapse
Did you wipe? I used 1-click root and I hadn't flashed anything in over a year so I forgot to wipe and I boot looped until I pulled the battery, booted into recovery and wiped. Simple solution but it could be worth mentioning...
So you are saying that, you have the stock recovery now? Triangle with little android? If so, Just download a PASSIMG.zip and flash through bootloader. This will take you to stock.
I have an N1 with locked bootloader and when I wanted to go back to stock(Forgot to get a nandroid of unroot rom). I had to flash a stock recovery. then downloaded the PASSIMG.zip from here http://forum.xda-developers.com/showthread.php?t=717870&highlight=frf91+downgrade
This takes me back to ERE76. Then I download an OTA of FRF85B.
I think fix permissions fixed everything. Thanks for the tips!
THIS HELPED TOO:
http://forum.xda-developers.com/showthread.php?t=619153
I have nexus one. This is my story. I had rooted my phone using universial android. I installed cyanogen mod and was a very happy user until I saw the MIUI Rom and then I flashed that. Then I saw that it was to unstable so I restored to a backup I made of cyanogen. After I started using cyanogen mod again it was very unstable and had random reboots and lots of force closes. So I just decided I was done with the rooting business so I was gonna use a passimg. Acsently I flashed the Korean passimg and I can't flash any of the other ones(except the frg33one because i cant update to frg83 after and lose root) So on the Korean Rom I rooted and installed clockworkmod. Then I noticed I couldn't install any custom rom(i tried CM6, CM6RC3,MIUI)and I kept getting errors.So while I was in clockwordmod restored one of my old stockrom backups before i had flashed any roms and it worked. But still when went to go and try and flash a rom it still gave me errors. But the most ANNNOYING thing of all is i would flash clockwordmod in rommanager than i would touch reboot to recovery. It worked. I got into clockwordmod but then when i would try and go back again a second time it wouldn't be there. It would be the stock android recovery and even when i would go to recovery though the bootloader it would still be stock recovery. I dont know what to do. As i said my bootloader isnt unlocked because i dont want to void my warrenty. my inital plan was if i ever needed to return this ting i could just i could just run a passimg and restore to to stock everything and there would be no traces. If i have to return my phone it would have to be last resort because I live in Canada and I would have to play ridiculous duties and taxes on it. Now i just want to make sure im able to install gingerbread on when it comes out. Also i forgot to mention that everytime i try to update my phone to 2.2.1 it always fails even though im on stock recovery(although even when i go into recovery and it is the stock recovery rommanager still says im running clockwordmod) PLEASE HELP!!!
ps. Im only 13 but i consider myself to be pretty techsmart for 13. I wouldnt mind using cmd/terminal and im running ubuntu 10.10 on my laptop.
ajam100 said:
I have nexus one. This is my story. I had rooted my phone using universial android. I installed cyanogen mod and was a very happy user until I saw the MIUI Rom and then I flashed that. Then I saw that it was to unstable so I restored to a backup I made of cyanogen. After I started using cyanogen mod again it was very unstable and had random reboots and lots of force closes. So I just decided I was done with the rooting business so I was gonna use a passimg. Acsently I flashed the Korean passimg and I can't flash any of the other ones(except the frg33one because i cant update to frg83 after and lose root) So on the Korean Rom I rooted and installed clockworkmod. Then I noticed I couldn't install any custom rom(i tried CM6, CM6RC3,MIUI)and I kept getting errors.So while I was in clockwordmod restored one of my old stockrom backups before i had flashed any roms and it worked. But still when went to go and try and flash a rom it still gave me errors. But the most ANNNOYING thing of all is i would flash clockwordmod in rommanager than i would touch reboot to recovery. It worked. I got into clockwordmod but then when i would try and go back again a second time it wouldn't be there. It would be the stock android recovery and even when i would go to recovery though the bootloader it would still be stock recovery. I dont know what to do. As i said my bootloader isnt unlocked because i dont want to void my warrenty. my inital plan was if i ever needed to return this ting i could just i could just run a passimg and restore to to stock everything and there would be no traces. If i have to return my phone it would have to be last resort because I live in Canada and I would have to play ridiculous duties and taxes on it. Now i just want to make sure im able to install gingerbread on when it comes out. Also i forgot to mention that everytime i try to update my phone to 2.2.1 it always fails even though im on stock recovery(although even when i go into recovery and it is the stock recovery rommanager still says im running clockwordmod) PLEASE HELP!!!
ps. Im only 13 but i consider myself to be pretty techsmart for 13. I wouldnt mind using cmd/terminal and im running ubuntu 10.10 on my laptop.
Click to expand...
Click to collapse
If you installed the original passimg then you'll have 2 files you'll want to remove if you don't want the stock recovery to keep flashing back when you reboot
Remount /system rw and remove:
rm /system/etc/install-recovery.sh
rm /system/recovery-from-boot.p
Remove those, flash your custom recovery and you should be good to go.
With respect to the errors: Clear out the cache and dalvik-cache. Wipe and install your rom of choice, be it a stock repack, CM6, Enom etc.
With Amon's latest recovery *1.8.0.1 you can flash both signed (google) and signed (test) packages, so the official update will flash as well as a repack. If you flash the official 2.2.1 remember to pull remove those 2 files again or it will blow away your custom recovery on reboot.
A couple of months ago I rooted my N1 FRF91 with Universal Androot. Later I flashed psfMod (based on CMW) custom recovery using flash_image recovery.
Now I don't have any use for custom recovery or a rooted device anymore, and want to get back on track to be prepared OTA 2.3.
I have received notifications for 2.2.1 OTA (2-part update), but the device just locks up during the upgrade and gets back to rooted 2.2 after a reboot.
So how do I apply the 2.2.1 update? Could I just flash the original recovery with flash_image (and what file should I get in that case), unroot with androot and just use the OTA? Or is there any better/easier way?
The question feels kinda nooby, but the only guides I find is to get back to shipping conditions (Which I don't want to keep my settings and so on),using fastboot which I can't since my bootloader still is locked or assumed that you are using a custom ROM which I don't.
Thanks for your help!
There is no need to get rid of a custom recovery or root to apply those updates. This has been covered in many threads.
This is what I would do. Use flash_image to flash Amon_RA 1.9.0 recovery. Then download the update (make sure you download the correct one: there is one that is FRG83D from FRF91, which is what you will need if you are running FRF91)and save it to the root of your sdcard. Then boot into recovery, and flash the update. (You will lose root and your custom recovery, but just root again if you want.) That covers part 2 of 2 of the update.
If you want to flash the first part, dowload the HBOOT 0.35 update file (floating around the forums) and place it in the root of your sdcard. Boot into recovery and flash that. You may have problems flashing certain custom recoveries after you flash the 0.35 HBOOT.
Thanks for your reply. If I follow your steps, the 2.3 OTA will work when it eventually comes?
F-Forward said:
Thanks for your reply. If I follow your steps, the 2.3 OTA will work when it eventually comes?
Click to expand...
Click to collapse
If you keep a custom recovery, you will still get the notification, but you will have to manually apply it. If you keep the stock recovery, it should be able to apply it automatically. No word yet on if the newer HBOOT is a requirement for 2.3 or not.