Related
Is there a way to remove the Cyanogen Recovery Console?
I'm quite new to Android myself but from my experience so far i'm sure you can 'replace' it with any recovery image - i went from cyanogens to the RA-hero-v1.2.3
If you're wanting to go back to stock recovery image you need to find the .img file for it then adb the file to your phone to replace the current recovery image. (just follow the process of installing the recovery image you currently have but using the new file)
Unfortunately i'm not sure where you can download the stock image.
Hope this helps!
i think in the ruu installer you can select what you want to overwrite/install. if so, just select recovery and there you go ;-)
the ruu installer can be found somewhere in development forum or on htc.com
There is one here frpm HTC Hero (Orange UK) also you will find nandroid in the shared folder. LINK
Hey Guys,
i want to remove recovery Build RA-hero-v1.6.2a but i have no idea how to ?
I thought with the RUU installer i could do it but it it doesn't work.
It tell me "no usb connexion".
Any help ?
Thanks !!!
To replace it with what?
with the original from HTC
So you're running the RRU file and its giving what error number?
It's error 170.
I think the recovery image block the process.
I'm running windows 7 64 bit, it may be help !
i think it can remove via fastboot .. simply erase it if you know how to use ADB
Run RUU under Windows XP SP3!
You should have looked at BTDAG's signature,...
Use [Guide] Drivers & RRU Errors Solved if your still having issues.
Yesterday i got a message of an OTA update for my Hero phone.
I installed it and from then i can't boot my phone.
It hangs at the HTC logo.
I tried fastboot to install the RAA recovery but i am getting the remote: not allowed error. Also i tried the hard reset but that also didn't work.
With the ruu rom file from htc i managed after loading it to get the rom.zip file.
I renamed it to HEROIMG and loaded it with the fastboot menu (back + power and then vol down).
Here i am getting an error that the version is not right.
I am really frustrated because i can't fix it.
I hope someone got an solution for this so i can bring my phone alive.
It seems that i can load roms with the microSD card with the heroimg file.
Hi, i think you had root access.
With the update you loose your root acces, you need to gett root acces back.
The only way to use your hero right now is the install with a ruu file. ( a official update from your provider.) There is a tread with all the htc hero official rom as *.exe.
Here http://forum.xda-developers.com/wiki/index.php?title=HTC_Hero#Official
Afterwords you need get root access to install custom rom's.
But maybe there is a other way.
Thanks,
I have tried the latest rom from the link
but it can't find my phone when i have booted it under fastboot.
I also tried to copy the rom.zip from this package.
and rename it to HEROIMG.zip
then i loaded it with the hboot mode.
It is loading and then its verifying and then i get an error that the version is older.
This seems to install but it still hangs.
Now i am downloading the 2.73.405.66 from:
http://forum.xda-developers.com/showthread.php?t=5596221
I did root my phone with the official firmware, but how can an update brick my phone because of the root?.
frustrating that i am not having an microSD reader.
I am writing it now with my Dingoo A320 gaming console
Finally with other drivers the ruu file is trying to update my phone.
But now i am getting an 140 error (bootloader version error)
I saw in a post that you need a golcard to fix this.
But i don't think that works because i don't have adb only flashboot
I got the HBOOT-1.76.0007 (HERO10000)
MICROP-010F
Radio-6.35.15.11
The phone screen says:
checking Main Version...
Update Fail!
I think i got a problem
I have the same problem after the install (hangs on the "HERO" logo on boot), even though I never rooted my phone nor installed anything not coming from the market.
Hi,
I traded a phone with someone and the rom they had was acting up.. the Infected Rom (cdma verizon)... When I got the phone, I told him he could keep his SD card and I could keep mine.. i guess the P something image file was on there and now Im just rooted with Teamwin recovery and not able to flash any rom or restore the Infected rom i nandroid backed up.
I have fastboot 1.50 S On but unlocked
Now imma be at work and not have a working phone. This isn't cool. PLEASE GET BACK TO ME IF YOU CAN HELP peeps. I would really appreciate it.
I also tried the unlocking method all over again but the Java SDK wont install.. it tells me to disable my virus protection (I did) and then it says unable to install it. This is just a mess man.
stepinmyworld said:
Hi,
I traded a phone with someone and the rom they had was acting up.. the Infected Rom (cdma verizon)... When I got the phone, I told him he could keep his SD card and I could keep mine.. i guess the P something image file was on there and now Im just rooted with Teamwin recovery and not able to flash any rom or restore the Infected rom i nandroid backed up.
I have fastboot 1.50 S On but unlocked
Now imma be at work and not have a working phone. This isn't cool. PLEASE GET BACK TO ME IF YOU CAN HELP peeps. I would really appreciate it.
I also tried the unlocking method all over again but the Java SDK wont install.. it tells me to disable my virus protection (I did) and then it says unable to install it. This is just a mess man.
Click to expand...
Click to collapse
If you're interested in reverting back to completely stock, the RUU files are available at http://www.goo-inside.me/shooter/ruu . Both the PG86IMG.zip and the .exe files are available there.
Interesting the device is flashed to verizon, at least you mention the device is on CDMA verizon. The only issues I can forsee here will be 3G data/MMS might not work via Verizon if using a stock Sprint ROM.
Of course, these *might* work and they can also be *tweaked* but I doubt, out of the box, they will work. Phone calls and SMS should work over verizon using the stock sprint ROM.
Here is my usual lecture, reading this will save you a lot of time and headache, regarding flashing a ROM and kernels on the EVO 3D with hboot 1.5 and htc's unlock method:
Essentially, if you're looking to flash a kernel or ROM (which many times also include a kernel), there are three basic methods (two seem the easier) with hboot 1.50 and htc's unlock method:
1) For Kernel Flashing: From Android mode, using my application, Flash Image GUI. Put the kernel .zip file on your sdcard, select from inside the application and flash.
For ROM Flashing: Pull out the kernel file (usually named boot.img) out of the ROM .zip and push to sdcard. Flash using Flash Image GUI.
If you're away from a computer and want to flash any kernel, this is a great tool!
2) Load the custom recovery, NOT using the traditional method (reboot recovery, bootloader -> recovery, etc), but a specific method for Hboot 1.5. From the prompt use: fastboot boot c:\downloads\cwm-recovery.img.
This will temporarily boot the custom recovery image and the HTC unlock method will grant it write access to the boot partition while in this mode.
In this temporarily booted recovery mode, when a full ROM (with kernel included) is flashed, the kernel will flash correctly.
3) Boot into recovery using the traditional methods, reboot recovery, bootloader -> recovery, etc, and after the custom recovery has loaded, flash the ROM. Reboot into fastboot mode and then separately flash the kernel from the computer: fastboot flash boot c:\boot.img.
Downside to this method would be if a zImage is included instead of the boot.img for the kernel, won't flash correctly.
Being without a phone is rough now a days! Hope that helps and points in the right direction!
so sorry.. i meant to say CDMA Sprint.. i probably was so frustrated and typed verizon. I am about to read what you post completly.
Thank you so much for the reply! I purchased the GUI App from the market a few days ago and I wasnt sure if it would work on my phone because that PG86IMG.zip wasn't on the root of my SD card (it's on the other guy's sd card) I will try your method to flash a ROM.
I was able to get the Rom restored from the nandroid backup someone last night.. I still need a new rom because this one has touch screen problems. Thanks again
Hi,
I have a UK Nabi2 which I used Nabilab2 to install TWRP+root+google apps a while back. I needed to do the new two part OTA update, for warranty reasons, so went to install my original backup, but could not find it. I used Nabilab2full and did the stock install, which removed root and returned the device back to stock. (This also changed my nabi to a US version with no serial, FW 2.1.29. which I later found out). & at that point I still had TWRP.
I did the first two of three OTA updates (which worked), the third update crashed during install. I retried the OTA twice more but each time it crashed. The device lost TWRP after this.
Upon entering recovery with ON/Vol+ I now get <3e> recovery. Running the root.zip file from sd card fails (I assume as I am not in the correct mode or have a bad file?). The OTA updates I grabbed from the nabi wiki page (and the thread, see below) also fail.
My device does not show in fastboot. Adb sees it but when using the command, C:\adb reboot recovery, the Nabi reboots and goes to the dead android (pushing -/+ to get into) <3e> recovery, and adb at that point no longer sees the device. The nabi also disconnects once adb shell is executed. I can intsall .apk files via adb command but I still need root access to run TWRP backup manager. I can run the root.zip file via an apk installer, but when running SU it gives a message 'There is no superuser binary installed, and superSU cannot install it. This is a problem!' ...Is there another way can I install root and/or the recovery.img to the Nabi2?
(I have been following the thread here, http://forum.xda-developers.com/showthread.php?t=2041224&page=10, as well as several hours worth of reading various adb, <3e> recovery, lost root etc q&a's in other places but cannot find an answer, or it's assumed that the adb reboot recovery command is working, which mine appears not to be).
Any help or pointers in the right direction would be very appreciated.
Regards,
Smirnofred
Hi,
I have quite a similar issue with this. I flashed custom recovery and forced gapps, but now cannot flash original recovery to perform OTA update. Cannot boot into custom recovery at all.
Done a system restore so now i have lost the gapps that were pushed and cant get into recovery to flash them again :crying:
Thank you for the reply mate, sorry to hear you are in the same situation more or less.
Further reading over at Stack overflow help forums seems to lead me to believe the tablet is bricked. Loss of su/root privileges means no r/w access via adb to put the required files where they need to be, or install or TRWP.
I'm not giving up on this... well not yet. I have a ton of other work related things going on right now that I need to clear down so I can look into this a bit more seriously. I'm away till the 17th April but will check in here when I can. And, if I find a solution I will post it here.
smirnofred ;0)
smirnofred said:
Hi,
I have a UK Nabi2 which I used Nabilab2 to install TWRP+root+google apps a while back. I needed to do the new two part OTA update, for warranty reasons, so went to install my original backup, but could not find it. I used Nabilab2full and did the stock install, which removed root and returned the device back to stock. (This also changed my nabi to a US version with no serial, FW 2.1.29. which I later found out). & at that point I still had TWRP.
I did the first two of three OTA updates (which worked), the third update crashed during install. I retried the OTA twice more but each time it crashed. The device lost TWRP after this.
Upon entering recovery with ON/Vol+ I now get <3e> recovery. Running the root.zip file from sd card fails (I assume as I am not in the correct mode or have a bad file?). The OTA updates I grabbed from the nabi wiki page (and the thread, see below) also fail.
My device does not show in fastboot. Adb sees it but when using the command, C:\adb reboot recovery, the Nabi reboots and goes to the dead android (pushing -/+ to get into) <3e> recovery, and adb at that point no longer sees the device. The nabi also disconnects once adb shell is executed. I can intsall .apk files via adb command but I still need root access to run TWRP backup manager. I can run the root.zip file via an apk installer, but when running SU it gives a message 'There is no superuser binary installed, and superSU cannot install it. This is a problem!' ...Is there another way can I install root and/or the recovery.img to the Nabi2?
(I have been following the thread here, http://forum.xda-developers.com/showthread.php?t=2041224&page=10, as well as several hours worth of reading various adb, <3e> recovery, lost root etc q&a's in other places but cannot find an answer, or it's assumed that the adb reboot recovery command is working, which mine appears not to be).
Any help or pointers in the right direction would be very appreciated.
Regards,
Smirnofred
Click to expand...
Click to collapse
You need to select fastboot protocol in the menu after booting with pwr/vol buttons. Then install fastboot driver, then install TWRP. From that point the thread you linked will work.
scotia_rfc said:
Hi,
I have quite a similar issue with this. I flashed custom recovery and forced gapps, but now cannot flash original recovery to perform OTA update. Cannot boot into custom recovery at all.
Done a system restore so now i have lost the gapps that were pushed and cant get into recovery to flash them again :crying:
Click to expand...
Click to collapse
Doesn't matter if you flash the original recovery, you need to flash the original system. TWRP can do the OTA but it will fail because there are a couple of system files that were changed that fail SHA-1 checks. Don't know what version you are on or if it's a UK or US or Disney/Nick version.
aicjofs,
Thanks for the pointers! ...its most appreciated.
After checking, I do see the nabi in device manager when its in fastboot mode, but its not installed properly (it says 'Android device' but has a 'fastboot' icon with an exclamation mark under it) which would be the root of my issue I would have thought. I was certain the fastboot drivers were installed too, obviously I was wrong.
*EDIT*
Success!
I had java disabled. I also had issues with device manager switching from 'Android device' to 'Unknown device' intermittently.
I started fresh by uninstalling everything nabi/sdk/adb related. Re-installed java, sdk and adb drivers, in that order, which resulted in no conflicts or driver issues! Then when I put the nabi into 'fastboot protocol' the second menu then appeared (which it was not doing previously). I flashed the 2.3.3.0 TWRP recovery image.
Now I have some more reading to do about what image I need to put back onto the nabi.
Thank you.
*EDIT*
Thanks again.
Smirnofed.
smirnofred said:
aicjofs,
Thanks for the pointers! ...its most appreciated.
After checking, I do see the nabi in device manager when its in fastboot mode, but its not installed properly (it says 'Android device' but has a 'fastboot' icon with an exclamation mark under it) which would be the root of my issue I would have thought. I was certain the fastboot drivers were installed too, obviously I was wrong.
*EDIT*
Success!
I had java disabled. I also had issues with device manager switching from 'Android device' to 'Unknown device' intermittently.
I started fresh by uninstalling everything nabi/sdk/adb related. Re-installed java, sdk and adb drivers, in that order, which resulted in no conflicts or driver issues! Then when I put the nabi into 'fastboot protocol' the second menu then appeared (which it was not doing previously). I flashed the 2.3.3.0 TWRP recovery image.
Now I have some more reading to do about what image I need to put back onto the nabi.
Thank you.
*EDIT*
Thanks again.
Smirnofed.
Click to expand...
Click to collapse
Somewhere in that post you linked I put a pretty good procedure for getting a UK Nabi to the latest OS, hopefully you will be up and running in no time.
I'm there, finally. Using the link to the three part install you posted. http://forum.xda-developers.com/showthread.php?t=2041224&page=10 post #98
I'm now @ 2.2.2 (I think), 4.1jb, with 2.6.3.0 twrp recovery. First thing I did was make a full backup (once it was all working 100%).
I had a minor issue with SU trying to install repeatedly once I put the 2.2+ stock image (+modded ota), which sent the nabi back to <3e> recovery. But I just flashed it back to 2.6.3.0 with fastboot.
Many thanks ;0)
smirnofred said:
I'm there, finally. Using the link to the three part install you posted. http://forum.xda-developers.com/showthread.php?t=2041224&page=10 post #98
I'm now @ 2.2.2 (I think), 4.1jb, with 2.6.3.0 twrp recovery. First thing I did was make a full backup (once it was all working 100%).
I had a minor issue with SU trying to install repeatedly once I put the 2.2+ stock image (+modded ota), which sent the nabi back to <3e> recovery. But I just flashed it back to 2.6.3.0 with fastboot.
Many thanks ;0)
Click to expand...
Click to collapse
Hi Smirnofred, I have similiar issues to you, and i'm wondering of you can help. The 2.2 file from dropbox is no longer available, have you still got it? and would you kindly upload it somewhere for me if you have time. It would be much appreciated. :good:
James
Hi everyone,
I was on Cyanogenmod and had disabled bootloader unlocking from development settings. After trying to update, I'm now stuck in recovery. While rebooting, the oneplus logo appears but later it just reboots to recovery. In fastboot, I can't flash anything because it says the bootloader is locked (I obviously can't fix that from settings because the phone won't boot). I'm able to get into TWRP so is there a way to enable bootloader unlocking using it?
tech_master said:
Hi everyone,
I was on Cyanogenmod and had disabled bootloader unlocking from development settings. After trying to update, I'm now stuck in recovery. While rebooting, the oneplus logo appears but later it just reboots to recovery. In fastboot, I can't flash anything because it says the bootloader is locked (I obviously can't fix that from settings because the phone won't boot). I'm able to get into TWRP so is there a way to enable bootloader unlocking using it?
Click to expand...
Click to collapse
Go to fastboot and boot into stock recovery, don't install. Just boot to recovery, command should be something like below.
fastboot boot recovery-name.img
If you can go to opx recovery, flash stock rom and see
tech_master said:
Hi everyone,
I was on Cyanogenmod and had disabled bootloader unlocking from development settings. After trying to update, I'm now stuck in recovery. While rebooting, the oneplus logo appears but later it just reboots to recovery. In fastboot, I can't flash anything because it says the bootloader is locked (I obviously can't fix that from settings because the phone won't boot). I'm able to get into TWRP so is there a way to enable bootloader unlocking using it?
Click to expand...
Click to collapse
Have you tried going through the steps for unlocking bootloader again?
Exodusche said:
Have you tried going through the steps for unlocking bootloader again?
Click to expand...
Click to collapse
That didn't work. Had to flash the stock rom, re-enable unlocking, unlock and flash.
tech_master said:
That didn't work. Had to flash the stock rom, re-enable unlocking, unlock and flash.
Click to expand...
Click to collapse
I have the same problem, stuck in recovery, can't unlock, but worse: For some reason I have Cyanogenmod recovery installed, not TWRP. Now, can't install any stock rom. Tried from SD card and by sideload, but it seems that it just doesnt "stick" to /system. So, I am stuck in recovery, can't install CM, and can't unlock, to install TWRP.
Any ideas, other than getting a new phone tomorrow morning?
Thanks
reebomber said:
I have the same problem, stuck in recovery, can't unlock, but worse: For some reason I have Cyanogenmod recovery installed, not TWRP. Now, can't install any stock rom. Tried from SD card and by sideload, but it seems that it just doesnt "stick" to /system. So, I am stuck in recovery, can't install CM, and can't unlock, to install TWRP.
Any ideas, other than getting a new phone tomorrow morning?
Thanks
Click to expand...
Click to collapse
Ah no. You'll probably need to find someone who can re-sign CM so that it'll flash.
Thanks for the answer, I have no idea how to do this, how is this done? I don't seem to find much info online...
Sent from my HUAWEI TAG-L21 using Tapatalk
reebomber said:
I have the same problem, stuck in recovery, can't unlock, but worse: For some reason I have Cyanogenmod recovery installed, not TWRP. Now, can't install any stock rom. Tried from SD card and by sideload, but it seems that it just doesnt "stick" to /system. So, I am stuck in recovery, can't install CM, and can't unlock, to install TWRP.
Any ideas, other than getting a new phone tomorrow morning?
Thanks
Click to expand...
Click to collapse
NO Need To Worry by following this procedure you are going to install stock recovery. first, you have to download this zip.
link - https://www.androidfilehost.com/?fid=24269982087019810
after downloading this zip copy and extract it on your desktop (PC or Laptop). now switch OFF your opx and connect it with your pc by pressing vol Up button, you will find that pc installing some drivers if it install the drivers then you are going right. now after connecting your opx to pc open the extracted folder and open "MsmDownloadTool V2.0" . on opening this you will see the list of attached devices (for ex. com device and if your device is not connected then it will show No device). If you your device is attached then you have to click on START Tab on left top corner. it takes 30 ~ 40 Sec to complete the whole process after that your opx restart with installed stock recovery. through this recovery you can flash H2OS and OOS. If you want to install TWRP first of all you have to install oos or H20s after flashing, you have to allow oem unlock in developer setting.
yuv93 said:
NO Need To Worry by following this procedure you are going to install stock recovery. first, you have to download this zip.
link - https://www.androidfilehost.com/?fid=24269982087019810
after downloading this zip copy and extract it on your desktop (PC or Laptop). now switch OFF your opx and connect it with your pc by pressing vol Up button, you will find that pc installing some drivers if it install the drivers then you are going right. now after connecting your opx to pc open the extracted folder and open "MsmDownloadTool V2.0" . on opening this you will see the list of attached devices (for ex. com device and if your device is not connected then it will show No device). If you your device is attached then you have to click on START Tab on left top corner. it takes 30 ~ 40 Sec to complete the whole process after that your opx restart with installed stock recovery. through this recovery you can flash H2OS and OOS. If you want to install TWRP first of all you have to install oos or H20s after flashing, you have to allow oem unlock in developer setting.
Click to expand...
Click to collapse
Thank you. I had tried this procedure previosuly, and didn't work. This time, since you insisted, I tried again, on another computer, and the phone was correctly detected, drivers installed and factory image installed on phone. I am happy again