Database Develop

Why did I lose root? Please help!

First off I would like to thank everyone on this amazing site for all the advice, guides and tutorials.
I unlocked my nexus bootloader and flashed a couple different roms. I really like the rom manager so I've used that to download roms and then flash them using that app.
When I downloaded the stock version of 91and flashed it, the phone no longer seemed to have root or clockwork recovery but my bootloader was still unlocked. When I downloaded rom manager, it could not get super user permissions, this being useless in flashing a backup or new rom. So I used universal one click root to gain root access and then rom manager was able to flash a backup.
I know this may be a dumb question but hope someone could explain to me why I needed to re-root and why I lost clockwork recovery...?
Thanks for the help in advance.

cwazynit said:
When I downloaded the stock version of 91and flashed it
Click to expand...
Click to collapse
Right theres your problem. stock roms dont have root built in you have to root them again. unless you download a prerooted stock rom. hope this helps.

cwazynit said:
I know this may be a dumb question but hope someone could explain to me why I needed to re-root and why I lost clockwork recovery...?
Click to expand...
Click to collapse
also it isnt a stupid question its that you didnt know and you wanted to know. when i started i didnt know either. lol.

krypticos said:
Right theres your problem. stock roms dont have root built in you have to root them again. unless you download a prerooted stock rom. hope this helps.
Click to expand...
Click to collapse
Yep this seems to be your problem. If you're wanting stock with the basic add-ons then the first link in this thread is your answer: Link.

Thanks very much. That does make sense. I thought unlocked bootloader meant I was rooted regardless of rom! I'm in way over my head lol. Looking forward to learning more...thanks for the new rom link as well
Sent from my Nexus One using XDA App

cwazynit said:
Thanks very much. That does make sense. I thought unlocked bootloader meant I was rooted regardless of rom! I'm in way over my head lol. Looking forward to learning more...thanks for the new rom link as well
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
The advantage of unlocking your bootloader means you can flash a custom recovery from Fastboot mode, without having to "root" the ROM. Next time this happens you can just boot into fastboot and flash clockwork from there like this:
fastboot flash recovery PATHTO\RECOVERYFILENAME.img
so say you download clockwork and save it to c:\sdk\fastboot named recovery.img from a command prompt you enter the following
cd \sdk\fastboot
fastboot flash recovery recovery.img
once it is done flashing you can do this
fastboot reboot recovery
and that should take you into clockwork where you can flash your favorite ROM (or restore a backup).

Thanks for the help. I will be sure to try that method out next time. Very helpful.

[Q] flashing custom recovery - frustrated!

Hi,
Upgraded to 2.3.3 and lost root.
Bored of mucking about with oneclick etc, I unlocked the bootloader. Easy(ish), cool!
Trying to flash amon ra with fastboot, everything goes well (appears as though it's flashed). But when I re-boot, it isn't there!
Padlock showing - so bootloader unlocked.
Nexus drivers installed, device showing with "fastboot devices".
Trying to flash amon ra 2.2.1.
Any suggestions?
Ta!
Andy

When you boot a stock rom it wipes custom recoverys and puts the stock one back.
Use the search feature on the forum.
Sent from my Nexus One using XDA App

Read my signature, look there for recovery installation guide w/ unlocked bootloader.

albundy2010 said:
When you boot a stock rom it wipes custom recoverys and puts the stock one back.
Use the search feature on the forum.
Click to expand...
Click to collapse
Thanks for your reply.
I've spent (literally) all day searching the forum (I'm in the uk - so hours and hours). There's so much, and some of it contradictory.
Ok, so I can't put a rom on without a custom recovery, but I can't put a custom recovery on because the stock rom wipes it?
I don't actually want a custom rom, simply a rooted stock phone. Which I have had previously.
Cheers! (driven to booze!)
Andy

Jack_R1 said:
Read my signature, look there for recovery installation guide w/ unlocked bootloader.
Click to expand...
Click to collapse
Thanks.
Yes, that's what I've been doing. There's a mistake in that part of the faq:
Faq states at the end "reboot recovery"
Should be "reboot-bootloader"
That works, but as soon as I then reboot into 2.3.3 - it wipes the custom recovery (which is why I'm in the q + a).
The other problem I'm having is that my phone doesn't appear rooted from within the o/s (apps that require root don't work), but the padlock is there ans the bootloader is unlocked. I can install su and busybox installer from the market, but neither work.
Back to the beer!
Andy

I can't explain all in detail while on my phone.
Do this. Grab a preroooted stock rom from the dev section and put it on SD card.
Boot into fastboot and flash the custom recovery.
Then load up that recovery without booting up the os.
Flash the rom you downloaded.
There are other ways to fix your issue but this is probably the simplest for you.
Sent from my Nexus One using XDA App

albundy2010 said:
There are other ways to fix your issue but this is probably the simplest for you.
Click to expand...
Click to collapse
Thanks, that makes sense - and I agree with your statement above (simplest for me)!
I had (mistakenly) thought that unlocking the bootloader, then installing busybox and su from the market gave me a rooted phone.
I'll give it a go, when my wife regains her patience ;-)
Andy

andynx1 said:
Thanks.
Yes, that's what I've been doing. There's a mistake in that part of the faq:
Faq states at the end "reboot recovery"
Should be "reboot-bootloader"
That works, but as soon as I then reboot into 2.3.3 - it wipes the custom recovery (which is why I'm in the q + a).
Click to expand...
Click to collapse
Damn, you're right. The guide is missing the part of removing 2 files that the other guides have. I'll try adding that.

Jack_R1 said:
Damn, you're right. The guide is missing the part of removing 2 files that the other guides have. I'll try adding that.
Click to expand...
Click to collapse
Guide fixed. I've uploaded and linked the file that removes the stock recovery restoring files from the stock ROM.
You can repeat the guide and include the new part - it should prevent stock recovery from being restored on reboot.
Please try and write your feedback.

cheers! i've done what was suggested tho', and its worked a treat.
thanks again.
Andy

CWM Recovery problem

Hi, I followed the guide to install CWM and it seemed to go fine, but when I power on the phone and tap the vol-down key nothing happens, I do get the vibrations as I'm doing it though. Is CWM really necessary to install a custom rom? Cos I might just skip it.

You can't flash a custom rom without cwm recovery.
Sent from my C2104 using XDA Free mobile app

karthikys1 said:
You can't flash a custom rom without cwm recovery.
Sent from my C2104 using XDA Free mobile app
Click to expand...
Click to collapse
O lol, I guess I need to solve this then. I thought I just used FlashTool to flash the rom and viola, rom is on.
Does anyone have any ideas what I might be able to try to figure out why CWM isn't working? Any way to see if CWM is actually on my phone? (Maybe it's just not there, rather then not working).
Edit: Rom Manager seems to think I have CWM installed, also I did a Nandroid Backup which seemed to be configured to use CWM so I don't know if it's there or not, or working or not

Which guide did you follow? And how did you make a Nandroid Backup?

I followed this guide.
I downloaded Nandroid Backup Root, it created the backup without rebooting the phone, so it never needed to boot into CWM.

Astralogic said:
I followed this guide.
I downloaded Nandroid Backup Root, it created the backup without rebooting the phone, so it never needed to boot into CWM.
Click to expand...
Click to collapse
That's what I thought. The fact that it can create a backup doesn't mean it has a recovery installed, it doesn't use a recovery to create it. If the LED is lighting up at boot, and it is vibrating, and it doesn't get back in, I don't know what the problem would be. I'd try reinstalling CWM, and FYI, you should use V8; V9 has issues.
At the very least, if it really is installed, you should have a "recovery.tar" and "chargemon" file in /system/bin/.

Antiga Prime said:
That's what I thought. The fact that it can create a backup doesn't mean it has a recovery installed, it doesn't use a recovery to create it. If the LED is lighting up at boot, and it is vibrating, and it doesn't get back in, I don't know what the problem would be. I'd try reinstalling CWM, and FYI, you should use V8; V9 has issues.
At the very least, if it really is installed, you should have a "recovery.tar" and "chargemon" file in /system/bin/.
Click to expand...
Click to collapse
I don't have those files so CWM is not installed. I can't find v8 of CWM for Xperia T but I found this file "CWM4XperiaT_v8i_JB.zip", is that it?

Astralogic said:
I don't have those files so CWM is not installed. I can't find v8 of CWM for Xperia T but I found this file "CWM4XperiaT_v8i_JB.zip", is that it?
Click to expand...
Click to collapse
It clearly says "Xperia T" in the name of that file... yes, that's it. Now I'm wondering what you installed, if you didn't install that one, or V9.

Antiga Prime said:
It clearly says "Xperia T" in the name of that file... yes, that's it. Now I'm wondering what you installed, if you didn't install that one, or V9.
Click to expand...
Click to collapse
V8 works perfectly, it's installed fine.
I am going to follow this guide to install cyanogenmod, do I need to obtain a bootloader unlock code? Or should I just skip right to installing the ROM?
Edit: Oops forgot the link: http://wiki.cyanogenmod.org/w/Install_CM_for_mint

Astralogic said:
V8 works perfectly, it's installed fine.
I am going to follow this guide to install cyanogenmod, do I need to obtain a bootloader unlock code? Or should I just skip right to installing the ROM?
Edit: Oops forgot the link: http://wiki.cyanogenmod.org/w/Install_CM_for_mint
Click to expand...
Click to collapse
First of all, yes, you need an unlocked bootloader. You can't flash custom kernels on a locked bootloader. Secondly, I've never tried that tutorial (I have a TX), but I'm assuming it should work fine, but, personally I'd either go with FXP, or one of the OMNI builds here in XDA, since, as far as I know, developers here have more fixes than what I've seen on FXP and/or CM.
Also, there are a easier ways to flash your ROM, since you already have a custom ROM. I don't think it's necessary to have to fastboot the kernel first.
Edit: The Carbon ROM I'm on also has a T version. The reason I'm on this ROM (and previously OMNI) was because FXP/CM roms have/had a battery drain that was never fixed, something that was fixed here on XDA.

Antiga Prime said:
First of all, yes, you need an unlocked bootloader. You can't flash custom kernels on a locked bootloader. Secondly, I've never tried that tutorial (I have a TX), but I'm assuming it should work fine, but, personally I'd either go with FXP, or one of the OMNI builds here in XDA, since, as far as I know, developers here have more fixes than what I've seen on FXP and/or CM.
Also, there are a easier ways to flash your ROM, since you already have a custom ROM. I don't think it's necessary to have to fastboot the kernel first.
Edit: The Carbon ROM I'm on also has a T version. The reason I'm on this ROM (and previously OMNI) was because FXP/CM roms have/had a battery drain that was never fixed, something that was fixed here on XDA.
Click to expand...
Click to collapse
There's a problem My bootloader is not unlockable... does this mean I've been wasting my time?
Edit: There is this guide, it makes no mention of unlocking the bootloader so it might work?

Astralogic said:
There's a problem My bootloader is not unlockable... does this mean I've been wasting my time?
Edit: There is this guide, it makes no mention of unlocking the bootloader so it might work?
Click to expand...
Click to collapse
No, that tutorial won't work. Never follow a guide for flashing ROMs that wasn't meant for your phone. Your phone didn't even exist yet when that guide was written.
If you can't unlock your bootloader then there is no way you'll ever be able to flash a custom ROM, because, like I mentioned earlier, custom ROMs have custom kernels, and custom kernels need an unlocked bootloader.
I wouldn't consider it a waste, it's always useful to have a recovery installed; with it you can at the very least backup and restore, flash deodexed/zipaligned stock ROMs, such as this one, flash files, and even have access to ADB if your phone doesn't boot up, which can save you from having to wipe everything, etc., so not a complete waste of time.

Antiga Prime said:
No, that tutorial won't work. Never follow a guide for flashing ROMs that wasn't meant for your phone. Your phone didn't even exist yet when that guide was written.
If you can't unlock your bootloader then there is no way you'll ever be able to flash a custom ROM, because, like I mentioned earlier, custom ROMs have custom kernels, and custom kernels need an unlocked bootloader.
I wouldn't consider it a waste, it's always useful to have a recovery installed; with it you can at the very least backup and restore, flash deodexed/zipaligned stock ROMs, such as this one, flash files, and even have access to ADB if your phone doesn't boot up, which can save you from having to wipe everything, etc., so not a complete waste of time.
Click to expand...
Click to collapse
Ok, well, I learned a bit in the process, and I still have an Xperia SP bootloader to unlock, then flash cyanogenmod, so I'm in a better position to handle that now, thanks for all the help guys.

HTC Desire 510 64 bit unable to boot after OTA update

Hello
After trying to do an OTA update which failed my phone won't boot normally. If I just turn it on it boots into stock recovery and if I reboot it from there it just boots back into recovery.
I have tried to do a factory reset but it won't work, it seems like the system partition has been messed up.
I keep reading that I just need to "run the RUU" but I have no idea where I can find a RUU for my phone, it's a EU 64Bit version with no carrier. The htcdev site just lists kernel sources for my device.
Any idea how I can fix this and get back to a stock system?

henning_ said:
Hello
After trying to do an OTA update which failed my phone won't boot normally. If I just turn it on it boots into stock recovery and if I reboot it from there it just boots back into recovery.
I have tried to do a factory reset but it won't work, it seems like the system partition has been messed up.
I keep reading that I just need to "run the RUU" but I have no idea where I can find a RUU for my phone, it's a EU 64Bit version with no carrier. The htcdev site just lists kernel sources for my device.
Any idea how I can fix this and get back to a stock system?
Click to expand...
Click to collapse
Download this...
http://dl4.htc.com/RomCode/Source_and_Binaries/a11ul-3.10.28-g930be6d.zip

Thanks for the reply but the link just takes me to the general download page, could you tell me what filter you used to find the correct download?

henning_ said:
Thanks for the reply but the link just takes me to the general download page, could you tell me what filter you used to find the correct download?
Click to expand...
Click to collapse
Just enter the desire 510 skip the carrier and version just EU in the region and download the first one.

MrMike2182 said:
Just enter the desire 510 skip the carrier and version just EU in the region and download the first one.
Click to expand...
Click to collapse
Ok, but those are all just kernel sources, that's the problem, I can't use any of those to restore my device.

henning_ said:
Ok, but those are all just kernel sources, that's the problem, I can't use any of those to restore my device.
Click to expand...
Click to collapse
Well the only way I think you're gonna be able to fix it now is to follow the thread that shows you how to root the phone and install a recovery called philz touch recovery for 64 bit and then you'll be able to install the back up recovery that other users have posted.

MrMike2182 said:
Well the only way I think you're gonna be able to fix it now is to follow the thread that shows you how to root the phone and install a recovery called philz touch recovery for 64 bit and then you'll be able to install the back up recovery that other users have posted.
Click to expand...
Click to collapse
Thanks, I just did this, but I installed an old backup I had made before rooting the phone earlier this year. Now I'm back!

henning_ said:
Thanks, I just did this, but I installed an old backup I had made before rooting the phone earlier this year. Now I'm back!
Click to expand...
Click to collapse
Glad you got it fixed because I couldn't find anything for you about the RUU for 64 bit... So I was pretty sure you could fix it by rooting it!

Rooting H81110n with low effort root possible?

Sorry im fairly new to forums. In just curious because i tried to root my G4 H81110n with the low effort root but the only available software version is the H81110h. Will folling the instructions of H81110h brick my phone?

Da harrow said:
Sorry im fairly new to forums. In just curious because i tried to root my G4 H81110n with the low effort root but the only available software version is the H81110h. Will folling the instructions of H81110h brick my phone?
Click to expand...
Click to collapse
It will absolutely brick your phone if you try to go to H!
There is an n version available somewhere around here, prerooted and ready for flashing. Here it is:
http://forum.xda-developers.com/showthread.php?t=3191038

waylo said:
It will absolutely brick your phone if you try to go to H!
There is an n version available somewhere around here, prerooted and ready for flashing. Here it is:
http://forum.xda-developers.com/showthread.php?t=3191038
Click to expand...
Click to collapse
Pew.. Just bought the phone yesterday. That could have been a disaster! Thanks a lot!!

Rooting worked out just fine. So I went ahead and attempted to install CyanogenMod 12.1 (h811 nightly build). Now my phone keeps rebooting in recovery. I attempted to push a file through adb but my device is offline. Is there anyway to get around this or am I screwed?

Da harrow said:
Rooting worked out just fine. So I went ahead and attempted to install CyanogenMod 12.1 (h811 nightly build). Now my phone keeps rebooting in recovery. I attempted to push a file through adb but my device is offline. Is there anyway to get around this or am I screwed?
Click to expand...
Click to collapse
Download any of the @MicroMod777 Roms + Bootstack file and flash those 2 files, First the Bootstack and then the Rom....
this is taking in account you are rebooting in TWRP Custom Recovery.

DrakenFX said:
Download any of the @MicroMod777 Roms + Bootstack file and flash those 2 files, First the Bootstack and then the Rom....
this is taking in account you are rebooting in TWRP Custom Recovery.
Click to expand...
Click to collapse
Unfortunately I am in Cyanogen Recovery and the only thing I can do is sideload. When I attempt to do anything is sideload I get an error: protocol fault (no status).
Update: Went out an bought a micro sd card. Since abd wont work i'll just flash a rom through the card.
Update2: Everything is fixed thanks for all the support!