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.
Related
Not sure how to fix it. Before it happened, I was rooted with a Cyanogen rom on 1.6. I also had a black and green theme on. I went to install a new rom called "OpenEclair". I downloaded it, placed it in my sdcard root folder, and tried to install it. I had an installation error and it aborted. At this point, I figured ok, I'll just reboot. It kept me at the G1 screen for over 25 minutes, so I knew something was wrong. So no matter what I did from here on out (trying to perform a backup restoration, flash a different rom, etc), I would be stuck on the G1 screen. Finally, I flashed a JesusFreke rom and it let my phone come back on, so I haven't tried anything since. However, this rom is ANDROID 1.1. It sucks. Is there any way I can get back to either where I started, or even get this OpenEclair 2.1 rom working properly? Any help would be greatly appreciated. When I try to install the OpenEclair rom (before and after downgrade) it will say
E:Can't chown/mod /system/xbin/librank
*No such file or directory)
D:Failure at line 221:
set perm 0 0 06755 SYSTEM:xbin/librank
Installation aborted.
Press Home+Back to reboot
I had this also. The problem went away after I installed DangerSPL which, as stated at the top of the OpenEclair thread, is required to install this on the G1.
If you don't have DangerSPL, OpenEclair will fail to install as it doesn't have enough room to place its files.
However, if you do have it...
I have noticed this with some of the 2.1 ROMs. I think the reason is that, since we flash using an "updater", it wont wipe the partition before flashing. This leaves the possibility that there are old files with different permissions that prevent the new ROM from properly taking.
Boot your phone into fastboot (for the G1, hold the camera button while powering up), set it into usb mode (by the "back" button, I think), then use the fastboot tool to clear the boot and system partitions:
/fastboot wipe boot
/fastboot wipe system
This will clear the "ROM" component from the phone, and you can then go and flash whatever ROM you want. Make sure to wipe the data partition via recovery.
If, after wiping the ROM and rebooting, the phone is stuck at the carrier screen and says "Fastboot USB", that means it tried to boot the usual way and found no data in the boot partition. You need to boot into recovery and flash a ROM. Using "fastboot reboot" or the reboot command from the phone's fastboot screen will cause this. Use the phone's fastboot "power off" button ("menu" in the G1), then boot it into recovery.
Also remember that any install that fails after the "verification" phase will destroy the existing ROM, since you will be left with a partially installed ROM on top of the older one.
Thanks a lot guys. will try all of this when I get off of work. Much appreciation!
Got everything worked out. Just had to install that danger spl :]
Just flashed FastTest rom, pretty freakin' nice I must say!
Is there a way to backup all my apps/contacts/texts before wiping and flashing a new rom?
I have the Nexus S from Telus.
It was rooted, unlocked, running CM7. However I've been having issues with it freezing and decided I want to go back to the stock rom.
I ended up downloading what I thought was stock ROM for my phone (Stock GRH78 Nandroid Backup in this Tutorial http://forum.xda-developers.com/showthread.php?t=884093) however after it flashed my phone, I ended up with a phone which was essentially stuck in Airplane mode, would not connect to Telus. I'm guessing that it has the wrong radio for my phone/carrier?
So then I ended up finding a zip file someone posted Stock-GRJ22-i9020A-unsigned which should have worked, I ended up flashing the zip file from recovery.
It said it installed fine. Rebooted, and now the phone just cycles the Samsung Loading screen endlessly.
I tried to go back to recovery, and it gives me yellow triangle with !.
Is there any way to flash the recovery image back to the phone?
I plug the phone in and the PC won't recognize a device.
I installed the Android SDK
Ran the command adb devices, no devices attached to the PC.
I tried fastboot devices - blank
I don't know how I'll be able to get files back onto the phone SD Card for flashing etc...
I had the exact problem two days ago...flashed an image that jacked my phone up. Wouldn't boot past the google logo. Sat there indefinitely.
Read this thread and see if you can get it work. In a nutshell, you need the PDA net drivers installed. Since PDA net can't install the app on your phone (because it's not booted into an OS) leave the install program in limbo and voila, fast boot will work. From there, push the recovery.img (google Clockworkmod recovery image), boot into recovery and you are off to the races.
This is, of course, assuming you already have a ROM image on your internal SD card you can flash to get back up and running. I'm not sure how to install a .zip image ROM if you can't gain access to your SD card.
http://forum.xda-developers.com/showthread.php?t=1303522
Good luck, I know the feeling. It blows.
Ah, just found out how to install a file on a phone that won't boot.
You do need to flash CWM recovery first though.
http://forum.xda-developers.com/showpost.php?p=18437305&postcount=2
Good news! I tried a factory reset/data wipe and rebooted the phone.
It doesn't hang anymore, all functions restored and the phone is working on Telus again!
I guess I had to format data, clear cache, before the flash of the rom.
So relieved.
Issue has been solved!
Hey Guys,
I tried pretty much everything and don't know what else to do. My phone just stays stuck on the android screen. I forget that the "SD card" in this phone is actually part of internal storage, I did a factory reset and lost everything.
I tried flashing different boot.img and getting nothing. I'm afraid I need to get a rom onto the sd card but how is that possible if I cant get my phone to boot up.
Any ideas?
Thanks!
volume down button+power button try this combination until u get in the bootloader then select recovery. once in recovery just restore a backup if you have one, you should have one
i dont have a backup and i have nothing on my "sd" to i can install. I have formatted the ROM and thats why it wont boot..
If you can get into Recovery (CWM) in the advanced settings if i remember, there's a "format sd card" to make it work with the installation of a custom ROM
I posted a tutorial for how to do this:
http://forum.xda-developers.com/showthread.php?t=1667929
brwetz said:
I posted a tutorial for how to do this:
http://forum.xda-developers.com/showthread.php?t=1667929
Click to expand...
Click to collapse
thanks for the guide but im getting error mounting /sdcard. and if i follow cannondale0815 solution for that problem when flashing the stock and cwm I cannot access recovery mode.
Clear Storage in fastboot and re-install CWM then try it. That's how I got mine to work
Ok if your bootloader is locked and you have a custom recovery first flash stock recovery then boot into fastboot and run "fastboot oem lock" After that restart your phone and boot back into fastboot. Then run the RUU for your model and cid. easy.
Follow the steps which might work
1, If you knows something about adb, you can just simply push a rom into the sdcard(You don't need to do this if there is already a flashable rom in the sdcard), flash the kernel in fastboot, go to the recovery, wipe and flash a new rom. Then everything(except your data) should be fine
2, If you are not able to use adb push, or you have never flashed a recovery/3rd-party rom/ or you have other issues:
Using the RUU updater might be safe and simple (of course everything except those in the sdcard will lost)
a, relock the hboot using "fastboot oem lock"(or the RUU will refuse to continue)
b, run the RUU updater, wait for ~10min, your phone will be "refreshed" to something like the 1st day you bought it, except the Hboot will say it is "RELOCKED s-on"(this should be LOCKED s-on at first)
c，unlock your phone again(if you have stored the .bin file for unlock, just push it to your phone in the fastboot mode which is enough already, it is not needed to do the whole process in HTCDEV again.)
IMPORTANT: the RUU updater and the phone must be the same area. for example an Europe's RUU can't be applid to an US's One S
This is also the only method to update the Radio software, unless the hboot is S-OFFed
Bure03 said:
Hey Guys,
I tried pretty much everything and don't know what else to do. My phone just stays stuck on the android screen. I forget that the "SD card" in this phone is actually part of internal storage, I did a factory reset and lost everything.
I tried flashing different boot.img and getting nothing. I'm afraid I need to get a rom onto the sd card but how is that possible if I cant get my phone to boot up.
Any ideas?
Thanks!
Click to expand...
Click to collapse
I used Hasoon2000's HTC All-In-One Kit to root my phone. That all worked.
The issue came when i flashed a new kernel. I placed the boot.img from King Kang's new ROM (http://forum.xda-developers.com/showthread.php?t=1959099)
Anyway, When i boot I get the HTC, quietly brilliant logo, and this in red letters "This build is for development purposes only. Do not distrubute... "
i can boot into recovery (pwr+ vol down)
And i get the ***TAMPERED*** AND ***unlocked*** tags at the top
I don't know where to go from here...
Thanks for the help.
Also, whenever i boot into recovery or factory reset, neither succeed.
This was probably known info, just wanted to add it.
ccamwilkins said:
Also, whenever i boot into recovery or factory reset, neither succeed.
This was probably known info, just wanted to add it.
Click to expand...
Click to collapse
You mentioned in your original post that you could boot into recovery, so is that not working now? Factory reset might've fubared the recovery piece, so you could do one of two things:
1) download the original RUU version for your phone, relock your phone, and flash the RUU and start over.
2) try reinstalling TWRP.
This whole thing sounds like trying to install a kernel or fastboot flash a boot.img without SuperSU correctly installed. This is what happened to me when I first unlocked my phone and tried to fastboot flash the CM10 boot.img after failing the flash from recovery twice. Without that super-user permission, bad things tend to happen. If you decide to continue on with reinstalling TWRP, make sure SuperSU.zip is flashed successfully from
TWRP, then try your rom/kernel combination again (or even a different combination if you're apprehensive).
BEWARE: sometimes partially flashing these things can corrupt your sd card. I had to reflash the original RUU to fix my phone BEFORE I rerooted and flashed a rom/kernel.
Have you fastbooted a SU to your phone after you rooted and unlocked? I'd imagine you did if you followed the toolkit.. So your on 2.20... Just download cleanrom 5.1 on your computer. Mount sdcard via recovery and drag cleanrom onto phone. Flash entire rom in recovery. I bet it works
Once your on a stable rom, download king kang from your phone. Download flashgui. Open flashgui app, navigate to king kang and let it find the boot img and flash it for you.. Once successful, immediately boot into recovery and flash entire rom through twrp.
Success
Sent from my One X using Tapatalk 2
Before I get into the gist of my current problem I think it might be relevant to provide some backstory. I decided I wanted to try and root my phone so I could install a new custom ROM. I had done some jailbreaking back when the iPod touches came out, back when jailbreaking was extremely ghetto and unreliable, so I figured I could teach myself this fairly easily. I unlocked bootloader using the htcdev method without an issue, and, following a guide, downloaded something called Rootboot to flash the phone. There was only one step to this portion, so I assumed it would be easy. Running the rootboot started rooting my phone, however after a couple of lines in the command prompt it said something about the adb, failed, and the phone was stuck in a boot loop with no roms on it at all. I stayed up all night with the damn thing attempting to fix it, and at one point, actually got it to load up the stock ROM from the computer using some combination of RUU's and fastboot commands. I have no clue how I did it, all I know is that it was not through adb sideload because the recovery I had at the time wouldn't work with adb sideload for whatever reason. It was the recovery that came with the All-In-One toolkit, for the AT&T / TELUS version. At this point I figured since the phone was working I would just install the VenomROM, and after a few hours of playing around with fastboot and the bootloader trying to get a ROM loaded, I figured I was familiar enough with all of them to load the ROM.
Which is what brings me to my current issue. I KNOW the boot.img is flashed to the device because I used the All-In-One Toolkit to do it, erased the cache, did it again using fastboot commands in the command prompt, erased the cache, and continued to use recovery to install the ROM. I got it to load and install, cleared the darvik cache, data, and cache, but when booting, the phone would get to the lock screen, upon which sliding to unlock, presented me with a white screen that says "htc" on it instead of a launcher. After a couple of seconds of waiting, it says, "setup has quit responding" and gives me the option to close or to wait. Either option results in the phone rebooting wherein I only see a black screen with the notification bar at the top displaying my battery and no internet/network connection. I have gone back and flashed the boot.img again and cleared cache, darvik cache, and data several times and just have no clue what I'm doing wrong to not get this phone to boot with the ROM. I can reflash at any point from my sideload.zip file and the installation process has an option to flash the kernel (boot.img) because it is included in the zip. Any help would be much appreciated. I highly doubt theres anything wrong with the ROM or boot.img, it is probably me just not doing it right.
I am using (or attempting to use) the 1.2.7 version of VenomXL+ on the HTC One X+ along with TWRP 2.5 as the recovery.