Related
I've looked everywhere for answeres to no avail. So this is my problem, I have a mytouch 3G with out the 3.5mm jack [32B] that I rooted the easy way, Universal Androot. I went into recovery after renaming my rom update.zip, and on the recovery, clicked apply update.zip, but it said verification failed. I learned that the recovery screen i hav, the one with the triangle abd the exclamation point with the image of the phone is not the one I need, so I looked for different recovery screens. I tried ROM Manager to flash clockwork recovery, but it said an error occured while attempting to run privaledged commands, this appeared too when i tried the alternate recovery in ROM manager. Then i tried Recovery Flasher, but it said back up failed. I pressed the invisible button to skip this step, then tried flashing the recovery, flash failed. Please I need some answeres, I don't want to keep looking for more recoveries because i think that they wont flash too.
I rooted my HTC Desire CDMA from USCC okay, flashed a Froyo ROM with USCC stuff, and everything was okay. I made a nandroid backup, flashed CyanogenMod 7 RC4 and it seem to work okay, except I was having trouble entering my password when checking voice mail. Anyway, I decided to go back to Froyo. I used ROM Manager to restore the backup and got into ClockworkMod. However, none of the options work. If I go down to recovery, I go to the next screen, but no matter which option I select I end up with a black screen and nothing happens! I can't restore my backup! If I just try to press power on, I end up with the blue CyanogenMod screen and the arrow just goes round and round. Nothing happens. Please, if anyone has any suggestions, it would be greatly appreciated.
I remember hearing that because CM7 is a Gingerbread mod, it must use ClockworkMod v3 and to go back to your Froyo backup you'll need to downgrade to Clockwork Recovery 2.x. I'm not sure if things has changed, though, this was what I read a month or two ago.
Are you by any chance able to fastboot?
Reflash your CWM (if you are using NAND version) or get it again on your SD (if your are using SD version).
The problem is I can't do anything in ClockworkMod (version 2.5). Every option I select gives me a blank screen! I made a nandroid backup before flashing CyanogenMod, but I have no way of getting to my backup if I can't use ClockworkMod. Also, if I try to boot the phone, i just get the CyanogenMod 7 startup screen with the arrow going round and round. It will still be there 30 minutes later. I have to do a battery pull to start over with anything.
I was able to boot my phone after wiping all user data. I would like to use my nandroid backup to return to the previous ROM, but clockworkmod doesn't seem to work. I tried reflashing it in ROM manager and it only downloads a second or so and isn't really doing anything. I'm wondering if clockworkmod is defective. Is there any other way to flash it again without using ROM Manager?
If you are able to fastboot, you could try to restore a nandroid by flashing three files (boot.img, system.img, data.img) from your nandroid backup using:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata data.img
Disclaimer: I've not actually tried this procedure before! I got this info from here
You could use a similar procedure to flash a new ClockworkMod since your recovery may be corrupted: fastboot flash recovery recovery-clockwork-3.0.0.5-vision.img
You can download the image from Koush's website, under HTC G2.
This happened to me yesterday trying out the Alpha Build for the Fascinate. I was getting a dev block error and datadata would not mount. I had to go back to stock on heimdall. I don't know if this helps for your phone, but maybe somone with more knowledge can tell you if this may be happing to you and what the fix is, if that's not a fix for you.
Hey Guys,
I tried to root my Nexus S (GT-I9020), which somehow worked, but now I cant access the recovery anymore, which holds me from flashing other MODs.
Since I'm quite new to the flashing and rooting business, I do not really know how to describe the precise state of my Nexus S, so I'm going to tell what I did step-by-step, hoping that someone will find the error and help me fixing it.
I bought my phone and updated it via OTA to 2.3.4 (GRJ22).
I used this guide on nexusshacks.com to root my phone. The guide tells me to unlock the device and flash a custom recovery (clockwork-3.0.0.0.img) and a custom boot (rootboot.img). I got both images from this homepage.
After flashing these two images, I rebooted my phone and it stuck on the Google Logo (but with a opened lock underneath). Comments show, I was not the only one.
In the comments, the user "Taboom" proposes to download the official full rom of 2.3.4 (Downloaded from this XDA-Dev Post), and flash the boot.img from that. It helped, my system was able to boot and it was rooted.
Although I have a rooted system, which works perfectly fine, I cannot access my recovery anymore. So I downloaded the "ROM Manager" from the Market, let it download clockwork 5.0.1.0 and install it.
When I try to reboot to recovery, I see the following: "Google Logo with opened lock" then "White box with arrow out of box and little Android next to it" then the white box is being replaced by the "Street sign with the Exclamation Mark and the little Android next to it"
Please help me to get back a working recovery. I don't care whether the phone is being whiped or set back to stock status.
Basically, getting to stock status and having the opportunity to start all over again would be great.
My Phones Info is:
PRODUCT NAME - HEARING
HW VERSION - REV 11
BOOTLOADER VERSION - I9020XXKA3
BASEBAND VERSION - I9020XXKD1
CARRIER INFO - TMB
SERIAL NUMBER 3233E.....
LOCK STATE - UNLOCKED
I hope somebody can help me,
thank you in advance.
Jay
Jaikao said:
Hey Guys,
I tried to root my Nexus S (GT-I9020), which somehow worked, but now I cant access the recovery anymore, which holds me from flashing other MODs.
Since I'm quite new to the flashing and rooting business, I do not really know how to describe the precise state of my Nexus S, so I'm going to tell what I did step-by-step, hoping that someone will find the error and help me fixing it.
I bought my phone and updated it via OTA to 2.3.4 (GRJ22).
I used this guide on nexusshacks.com to root my phone. The guide tells me to unlock the device and flash a custom recovery (clockwork-3.0.0.0.img) and a custom boot (rootboot.img). I got both images from this homepage.
After flashing these two images, I rebooted my phone and it stuck on the Google Logo (but with a opened lock underneath). Comments show, I was not the only one.
In the comments, the user "Taboom" proposes to download the official full rom of 2.3.4 (Downloaded from this XDA-Dev Post), and flash the boot.img from that. It helped, my system was able to boot and it was rooted.
Although I have a rooted system, which works perfectly fine, I cannot access my recovery anymore. So I downloaded the "ROM Manager" from the Market, let it download clockwork 5.0.1.0 and install it.
When I try to reboot to recovery, I see the following: "Google Logo with opened lock" then "White box with arrow out of box and little Android next to it" then the white box is being replaced by the "Street sign with the Exclamation Mark and the little Android next to it"
Please help me to get back a working recovery. I don't care whether the phone is being whiped or set back to stock status.
Basically, getting to stock status and having the opportunity to start all over again would be great.
My Phones Info is:
PRODUCT NAME - HEARING
HW VERSION - REV 11
BOOTLOADER VERSION - I9020XXKA3
BASEBAND VERSION - I9020XXKD1
CARRIER INFO - TMB
SERIAL NUMBER 3233E.....
LOCK STATE - UNLOCKED
I hope somebody can help me,
thank you in advance.
Jay
Click to expand...
Click to collapse
you have to flash the recovery via fastboot, not via rom manager.
Like simms said you'd be best flashing through fastboot.
However, if you do want to flash through ROM manager, go into the settings and tick erase recovery before flashing.
On a side note I sent that guy a message a while back about removing an out of date boot.img from his site (as it's not necessary for "rooting") or at least add a disclaimer/notice but I see he still has not (leading to many people having a non bootable device). It's a shame he's so high in the Google search results.
Hey Guys,
thanks for your advices.
I used fastboot to flash the clockwork image I got from the CyanogenMOD Wiki [1].
Fun Fact:
When I flash the recovery, I can start it afterwards.
When I reboot to normal system und reboot again to recovery, it shows me the "Exclamation Mark and little Android" again.
But: Process is repeatable, so I can access my recovery once by flashing it.
Big (nooby) question now:
When I do a "wipe data/factory reset" and then flash the current CyanogenMOD, will this also flash a new boot.img?
Thanks,
Jay
[1] wiki.cyanogenmod.com/wiki/Nexus_S:_Full_Update_Guide
---------------
Edit:
Hey Guys,
I installed CyanogenMOD and now everything works fine. I'd like to thank you both for your help, it's now working as I desired!
"Fun Fact:
When I flash the recovery, I can start it afterwards.
When I reboot to normal system und reboot again to recovery, it shows me the "Exclamation Mark and little Android" again."
Flash recovery, boot into Android, use a root explorer, rename or delete (needs root) "install-recovery.sh" (it's in system/etc), boot into bootloader, flash recovery.
rentaric said:
"Fun Fact:
When I flash the recovery, I can start it afterwards.
When I reboot to normal system und reboot again to recovery, it shows me the "Exclamation Mark and little Android" again."
Flash recovery, boot into Android, use a root explorer, rename or delete (needs root) "install-recovery.sh" (it's in system/etc), boot into bootloader, flash recovery.
Click to expand...
Click to collapse
yea, that. itll stick and you wont have to reflash the recovery every time. then you can live in the recovery, just like me
Long time listener, first time caller.
I have the latest hboot 1.45.0013, S-On, Unlocked with HTC Dev Tool.
I used the Hasoon2000 tool to install SU, CWM, and a recovery image. I then used the instructions in the thread (http://forum.xda-developers.com/showthread.php?t=1508556) to install ICS and obtain root installing pyr-o-ice sense 1.1.1 (http://forum.xda-developers.com/showthread.php?t=1469615) Everything worked, created nandroid backup and installed titanium.
Some buttons didn't work, so I looked for updates and found Virtuous ROMs. So, I used CWM to clear dalvic, flashed boot image of the Virtuous Inquisition then used CWM to install zip. Bootloop. ROM just hangs on black screen with white V for 15 to 20 minutes.
MT4GS thread stated that Primadonna and Inquisition were comparable, so I followed the same proceedure, flashed Primadonna boot image then installed ROM through CWM. This time there was tmobile splash screen, but the same system hang.
At this point I tried to restore a recovery, but CWM could not find one. Used Astro to delete all boot images from SD root, assuming this may be the problem, and flashed a Virtuous ROM again. Same problem.
Based on this thread, I thought it might be the kernal, and tried flashing the pyr-o-ice boot image that worked initially. (http://forum.xda-developers.com/archive/index.php/t-1628171.html). No dice. CWM could not install the ROM (error 1)
So, at this point, I used CWM factory reset and wipe all data. And of course that made things worse, because the SD card with recoveries was wiped. I used adb to push the recoveries from Hansoon's toolkit, but stock recovery was not available (red triangle screen hang) and cwm could not mount the SD card.
So, at this point I used CWM to format SD card (blank anyway), and at this point adb failed to recognize the decive and I could no longer fastboot into recovery or hboot through adb. (volume down + power stopped working with pyr-o-ice install)
if i remove the battery and hold power + volume while using an adb reboot hboot command i can get into hboot about every 10th attempt. adb doesn't recognize the device ("waiting on device", or adb devices yields a blank list); however the phone in hboot will transfer to usb fastboot when connected with a cable.
i looked at pushing a zip file through adb to the sd root, but that was ineffective (adb does have write access to the sd root, maybe because i am s-on?). i purchased a second sd card, and copied the recovery images from hansoons toolkit and rebooted into recovery. still went to tmobile splash, followed by V-screen bootloop.
i looked at placing a stock ruu on the sd and naming the file PG59IMG.zip, but because i'm S-on i can't flash radios, so that's out.
So, here we are. Iffy access to fastboot, 2 sd cards, a lot of determination, and a persistent bootloop.
Can someone, PLEASE help me?
Thanks!
AFAIK, you cannot flash the boot.img with CWM if you are S-ON, you *MUST* use Fastboot to flash that. So, before you messed it all up, if you had just extracted the boot.img from the ROM and flashed it using Fastboot, it likely would have worked just beautifully.
Try booting into recovery and doing a regular flash of the ROM, THEN a fastboot flash of the boot.img.
SOLVED!!
Thanks to the folks heading up the HTC Unbricking Project (http://forum.xda-developers.com/showthread.php?t=1627881) ESPECIALLY Dexter93!! who patiently unraveled this for me, and Blue6IX for the Restore to Stock instructions in the Developers Reference Guide (http://forum.xda-developers.com/showpost.php?p=17424340&postcount=24) I'm back to stock, and ready to try it all again!
Can someone send me an apk that automatically clicks the thanks button for selected developers at regular intervals?
Thanks again!
Solved???
Fuzi0719, thanks for your reply. I may have written this inappropriately, but what coded in the command prompt was "fastboot flash boot boot.img".
The ROM zip file was placed on the SD card, and I rebooted into recovery, and used CWM to install zip from SD. I'm new to this so I may have used the wrong term for installing the zip through CWM, the boot image file was always handled through the above command.
I'm back to "stock" at this point, but when I boot into the bootloader, the phone looks for PG59DIAG.zip and PG59DIAG.nbh before PG59IMG.zip.
It then asks if I want to install the update. (This is after I have already installed the "update", and the phone reset itself even with my old wallpaper.) When I got to the home screen there was a white circle in upper left corner of the status bar, with "check content" message. Each time the screen locked (default 30 seconds) unlocking it took me to the mytouch splash screen with the green circle and white background for about 10 seconds before resuming.
Each time I check to see if the phone registers requiring any updates. It doesn't. Two installs of the PG59IMG.zip. "recovery" eliminates the unlock splashscreen, and wiped any customizations. However, the phone will not manually boot into the bootloader; I have to use adb. Hboot reinstalls the PG59IMG.zip as an update every time.
If I accept it reboots within seconds like a fresh doubleshot. If I decline the "update" it reboots to the Tmobile MyTouch 4G Slide text splash screen, then moved to the green circle screen for a few minutes before I get to the homescreen.
Blue6IX was looking for help with these last month (http://forum.xda-developers.com/showthread.php?t=1580077), so maybe they are just extraction files that HTC sends with the OTA update that would prevent my phone from trying to install the "update" every time?
In any case, my question at this point is after coming from such an unstable point with my phone, is this what every relocked bootloader does? Or, is this a problem that means something else is still wrong with the system? Because taking it back to stock has not solved this.
Thanks.
Thanks for clarifying, you wouldn't believe the number of people who fail to follow that one simple step of fastboot flashing the boot.img, so that's why I stated that. So, now you have the phone relocked, and running a stock ROM (the 1.55?), but with CWM 5.0.2.7? Were you wanting to update to the 1.63 ROM? I'm unclear on what it is you want to do. For one thing, if you've already flashed the PG59IMG then I would delete it off the sd card so it doesn't keep trying to load it.
Yup.
It was just that simple.
Mainly I wanted to make sure that my phone was stable before I went back to unlock the bootloader, etc.
Went back to HTC, got a new token (just in case), and I'm creating a nandroid backup right now. Thanks.
I really appreciate it.
Hopefully the next time I get stuck, it's just as simple to fix, but far less embarrassing.
I ran into some trouble trying to install a new ROM, and now have a hard time getting things up and running again.
Just figured I'd share a solution that took me an hour or 2 to figure out.
The Problem
The system didn't boot up any more. At some points I got stuck in a boot reloop, at others in the HTC screen (for development use only)
The Basic Facts
S4
Unlocked
Hboot 1.06.0000
Radio 1.06es.50.02.31
I could always boot into bootloader and into recovery (TWRP 2.3.3.0 - although that one always asks for a password, but when I click on Cancel, it does seem to work
The Things I Tried
I tried to install a ROM by first pushing it with quick adb pusher to the sd-card that was mounted in twrp, I then tried to install that zip file but got all sorts of 'mount' errors
I then tried to fash a stock RUU (I found RUU_Ville_U_ICS_40_S_TMOUS_2.35.531.7_Radio_1.08ts.50.02.16_10.08e.50.04L_release_279577_signed.exe), I relocked the phone with the one-in-all toolbox (which worked just fine), the phone went into bootloader, a White HTC sign appeared on the screen, it sent the file, then did 'updating signatures', but ended up with ERROR [130]: model ID error. I take it that is because it found a different Radio from the one expected
I then tried to flash the 'right' radio for the RUU I found (radio-1.08ts.50.02.16) by doing fastboot boot radio.img, but that gave the following error: "reproduce boot image with on-flash ramdisk error"
The Solution
I finally managed to install the ROM through the all-in-one toolbox. I selected under the 'ADB Sideload a ROM' option under 'Extras', the went into 'adb sideload' in twrp advanced and selected a rom I had downloaded (in my case ViperOneS). It started sending it properly (sending:'sideload' x%), it then showed the Team Venom logo and opened the aroma installer. I selected full install with a full wipe (to be on the safe side), and aroma then did its thing until it said "new ROM flashed successfully". I then rebooted and had to wait a few minutes for the first boot (as it had warned me), but I'm fully back up and running again! So If any of you experience a similar problem, you may want to try this out (and avoid the other things I tried.
Thanks for posting a solution. But I do want to point out that this is the development forum. As such, your post doesn't belong here. The General or Q&A forums are the correct ones.
Sent from my HTC One S using Tapatalk 2
Thanks Thanks Thanks !!!
I've been stuck on boot with every rom's that i've been trying to install!
I was becoming very concern about the problem !
I went from CM10 to the new Viper 2.0 but having troubles with WIFI I start testing others roms and than I become stuck!
Since I've TRW 2.3 and tool kit in my pc I give a shoot at your tutorial and it WORKS.
Thanks again,
Rui