Database Develop

I upgraded to official donut build and lost root, someone help :(

I lost my root access and have been unable to get it back and install my old cyanogen rom. someone please help me try to get it back, ive been trying everything.
is it possible to root donut build once uve installed the real one? it keep aborting any installations i try to do, and doesnt let me flash the recovery img either. i dont know what to do.

Yea the official update will do that... but all is not lost. You can follow the guide here and downgrade to RC29 to gain root
http://forum.xda-developers.com/showthread.php?t=442480
you can follow those steps to regain root on your phone, when choosing which rom you'd like to run, if you'd still like to have root access but prefer the official builds you can check out this thread
http://forum.xda-developers.com/showthread.php?t=538456

if you still have an engineering or death spl, you can just flash recovery from fastboot.
Boot your phone while holding the camera, then press back button, you should see "fastboot usb" on the screen. Download amon_ra's recovery (look for it in android development) and flash it doing "fastboot flash recovery recovery-RA-dream-v1.2.2.img". After it's done you should have recovery back and now you can restore your nandroid or flash another update.zip

I downgraded back to RC29 successfully, but now its not letting me install any apps from the sdcard or online to the phone, it just keeps saying Install unsucccessful on any app. Wat could be causing this?

i ended up rooting the phone the old way, using telnet. now its working again

Recovery died somehow after flashing official donut 1.6

Hi guys. I don't really know what happened here. I've flashed a few different versions of Cyanogen's builds onto my MT3G without any problems. Today I flashed the official 1.6 dev build of Donut before doing Cyanogen's 4.2.3.1 flash. Well, the 1.6 seemed to go smoothly, but after the reboot, the recovery would no longer load. It's now giving me a picture of the phone with an exclamation point when I try to load the recovery.
How can I fix this? Anyone? Please?

taken from cyanogens website site instructions.
If you boot the 1.6 image it will install the HTC stock recovery. Booting back to recovery will show the /!\[] symbol. THIS IS NOT LOSING ROOT. You can still flash update.zip files from this recovery. Also, you can still flash a nicer (CM-1.4) recovery with fastboot, or flash_image inside the CM install once you get it installed.
thats what sounds like happen to me

How do I do anything though? I don't have the ability to do anything, it just sits there on that screen.
<edit> Also, I can't re-flash the recovery. I've tried, but it gives me the error:
Flash FAILED: The command could not be run
After figuring out how to install ADB and trying to fix it via that, it appears that I have somehow lost root. It's giving me Permission Denied or remote device not allow when I try to flash or use fastboot.

Got it fixed. Took me forever, but I made a goldcard and flashed with the stock ROM. Now I'm good to go again after installing CM recovery 1.4.

Cannot flash any update.zip due to ADP1 1.6

I tried upgrading from 4.1.1.1.1. to Cyan's most recent ROM and have locked my phone to ADP1 1.6 do to my phone giving some error and rebooting when it wasn't supposed to. I cannot install Any update.Zip files it gives me the following error (Install aborted) after trying flash any update.zip, i am at stock recovery, and i get permission denied on various commands Via ADB but it tells me i have root still. On top of that Fast boot isn't letting me install any type of recovery image giving me an error (cannot load "cm-recovery-1.4.img"). Can anyone help me out of this funk i am in and again i am not able to unroot my phone to stock. Thanks for the help in advance
T-Mobile G1
Hard SPL
ADP1 1.6 ROM(dream_devphone-userdebug 1.6 DRC83 14721 testkeys)

After you flashed the ADP1 1.6 did you reboot the phone or did you flash the cyan rom? I don't actually know what happens if you reboot before flashing the cyan rom but apparently it's not a good idea since the wiki guide says, in bold, not to reboot until after you flashed the new rom.

Well yes i was aware that i wasnt supposed to reboot but as the phone was doing something to the radio it went black next thing i know the phone goes through its normal process to boot up. But this was while i was trying to install 4.2.3.1.

The answer you seek kinda sucks, but it also has a very clear solution: you lost root.
Your fix: re-root and follow the direct instructions for getting to 4.2.3.1.

[Q] S-off Bootloader won't unlock after failed Viper iynstall.

I have a Sprint HTC One. I previously unlocked the boot loader and installed clock work mod recovery. I achieved SU and partial Super CID. I tried flashing Viper ROM after relocking the boot loader, which failed. when I went to reboot the phone, I was in boot loader without a system ROM. so I installed the stock ROM and updated firmware. the phone now works. however, I lost su and my custom recovery. I tried to unlock the bootloader , reinstall Viper, but neither will work it fails every time. I am experienced at following instructions on this website, but I lack the knowledge to know exactly what I am doing with each action.
Please help me get either su, custom recovery or the boot loader unlocked. I still have S-off and I am at a loss. Thank you!

patrickgartner said:
I have a Sprint HTC One. I previously unlocked the boot loader and installed clock work mod recovery. I achieved SU and partial Super CID. I tried flashing Viper ROM after relocking the boot loader, which failed. when I went to reboot the phone, I was in boot loader without a system ROM. so I installed the stock ROM and updated firmware. the phone now works. however, I lost su and my custom recovery. I tried to unlock the bootloader , reinstall Viper, but neither will work it fails every time. I am experienced at following instructions on this website, but I lack the knowledge to know exactly what I am doing with each action.
Please help me get either su, custom recovery or the boot loader unlocked. I still have S-off and I am at a loss. Thank you!
Click to expand...
Click to collapse
... simply flash appropriate custom recovery from fastboot. boot into recovery and try to reboot from there and it will ask you if you want to root the device. root it. reboot normally and you will see SU app. open it and update binaries. thats it, you are rooted ...

Failure
Okay, so I appreciate the attention and help, but it fails to install recovery, flash roms, or unlock the bootloader from fastboot. I can flash firmware and run an RUU from my desktop. As well, I can run the Sprint OTA update from the phone, but I have not done that yet. I have hboot 1.55. I have tried to flash things from terminal emulator, but I'm having trouble. I can access and use the phone for Sprint, but the CID says 11111 and won't let me change carriers. Once again, I have S-off.
Thoughts:
Run Sprint update and try to start from scratch, if all else fails, sell it.
Can I flash SU from bootloader? I haven't tried that yet, although I doubt it will work given my other problems.

patrickgartner said:
Okay, so I appreciate the attention and help, but it fails to install recovery, flash roms, or unlock the bootloader from fastboot. I can flash firmware and run an RUU from my desktop. As well, I can run the Sprint OTA update from the phone, but I have not done that yet. I have hboot 1.55. I have tried to flash things from terminal emulator, but I'm having trouble. I can access and use the phone for Sprint, but the CID says 11111 and won't let me change carriers. Once again, I have S-off.
Thoughts:
Run Sprint update and try to start from scratch, if all else fails, sell it.
Can I flash SU from bootloader? I haven't tried that yet, although I doubt it will work given my other problems.
Click to expand...
Click to collapse
... slow down and calm down. i think you are hasting things. dont worry and do whatever you wanna do step by step. its not clear to me what you want to achieve, you wanna switch carriers ? want ota ? want custom rom ? you are s-off but cant flash recovery !!!! please explain exactly what you want and what errors are you getting and doing what
i think you cant have SU from bootloader and certainly terminal emulator doesnt flash recoveries and rom., fastboot does recovery and recovery flashes rom. dont play with your phone like this without proper knowledge. ask whatever doubts you have prior doing anything ...

Straight Talk
You're funny. Yes, I am in a hurry to use my new phone... Ultimately, I want to use it on straight talk. It is S-off, and the boot loader will not unlock, the phone won't flash a recovery and I have lost su. It's the weirdest thing! I haven't had this problem before. Usually you flash stock firmware and ruu and you're back at square one, but not this time.
I would pay you to visit my problem via Teamviewer? Interested?
-Patrick

patrickgartner said:
You're funny. Yes, I am in a hurry to use my new phone... Ultimately, I want to use it on straight talk. It is S-off, and the boot loader will not unlock, the phone won't flash a recovery and I have lost su. It's the weirdest thing! I haven't had this problem before. Usually you flash stock firmware and ruu and you're back at square one, but not this time.
I would pay you to visit my problem via Teamviewer? Interested?
-Patrick
Click to expand...
Click to collapse
... Dear if you wanna network unlock your phone, follow the steps exactly as described.
1. Flash this and only this RUU (first link - http://forum.xda-developers.com/showthread.php?t=2250904 ), no need to relock bootloader if unlocked as you are s-off.
2. Download the recovery for sprint variant and flash it in fastboot mode (fastboot flash recovery recovery.img) (link - http://forum.xda-developers.com/showthread.php?t=2651035).
3. Boot in to recovery and press reboot and then system, it will ask for your permission to root, root it. restart normally and open SU app and update its binaries. phone will reboot itself in recovery and back in normal mode. You will be rooted then. :victory:
then ping me for sim unlock ...

soft bricked htc one m7 from a suspected corrupt zip file

ok so i wanted to root my htc to install a custom rom. the process seemed to go fine i unlocked my bootloader and istalled the twrp recovery no problems there. the final step i was shown was to install supersu all through twrp, i did this it all seemed fine. once the phone booted back up all was fine and working no problem except that supersu was not finding the right binary file. i downloaded the newest version of supersu and againg using twrp i flashed it to the phone. since doing that the phone has stopped working completely it loads the htc booting screen and then nothing after that, i can still access bootloader and twrp but the phone is not recognized on pc anymore. i can gain access to it using command prompt and can also transfer files this way so im assuming that i have only soft bricked it.
i have read countless posts on here but i cant find any that have the exact same problem im having. ive tried all sorts like trying to put a custom rom on the phone using the adb sideload it goes over no problem the phone gets the file transfer but doesnt install.
i dont think the phone rooted properly from the start hence why i cant put a custom rom on it.
i think it obviously has something to do with the second supersu zip file i flashed onto the phone like i said all was ok before then except for supersu not working properly.
anyone have an ideas as to what actually has happened and if theres a fix?
thanks guys appreciate all yous do on this site.

Nibbler_87 said:
ok so i wanted to root my htc to install a custom rom. the process seemed to go fine i unlocked my bootloader and istalled the twrp recovery no problems there. the final step i was shown was to install supersu all through twrp, i did this it all seemed fine. once the phone booted back up all was fine and working no problem except that supersu was not finding the right binary file. i downloaded the newest version of supersu and againg using twrp i flashed it to the phone. since doing that the phone has stopped working completely it loads the htc booting screen and then nothing after that, i can still access bootloader and twrp but the phone is not recognized on pc anymore. i can gain access to it using command prompt and can also transfer files this way so im assuming that i have only soft bricked it.
i have read countless posts on here but i cant find any that have the exact same problem im having. ive tried all sorts like trying to put a custom rom on the phone using the adb sideload it goes over no problem the phone gets the file transfer but doesnt install.
i dont think the phone rooted properly from the start hence why i cant put a custom rom on it.
i think it obviously has something to do with the second supersu zip file i flashed onto the phone like i said all was ok before then except for supersu not working properly.
anyone have an ideas as to what actually has happened and if theres a fix?
thanks guys appreciate all yous do on this site.
Click to expand...
Click to collapse
What is your twrp recovery version, what rom and version are you trying to flash and what version of supersu are you using?