been postponing flashing a ROM for a while, and today i decided to take the big step.
follow everything by the book:
-un-locked the phone as per HTCDev instructions.
-installed twrp 2.6.0.0 recovery
-installed super-user
after all this phone rebooted into a fully restored stock OS.
downloaded CM10.2 (didn't want to mess around with nighties just yet) and copied to phone.
downloaded and copied compatible g-apps.
extracted cm 10.2 to get the boot.img file, and ran the command fastboot flash boot boot.img
didn't get any error messages.
ran the command fastboot reboot.
since then, phone is stuck in splash screen, and won't get past it, wont go into recovery, won't go into boot.....
if i try pressing the vol-down +power button, it will turn off after a while, and the indication light won't turn on if i connect it to the pc.
for the time being, i have managed to get the identification light on again, and put it in the charger.
any help would be appreciated.
------------------------------------------------------------
HTC one s s4
Same thing happened to me. I will tell you what I followed. It was not making any sense to me before but it worked so here it is.
Go into recovery wipe all data including caches 3 times. Now flash the ROM zip again and wipe cache and dalvic cache once. Now reboot.
Really worked for me.
Sent from my HTC One S using Tapatalk
Had the same thing. Nothing worked for me. Had to pay someone to restore to stock. The boot.img is the problem. It corrupts the phone.
Related
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!
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.
Please help, I tried to install and it failed, so I did a fastboot oem boot and now the phone works, but I cannot enter recovery, is there anything I can do. I am at a loss, whenever I restart the phone, I have to fastboot oem boot or it will stay stuck in 4 exclamations
I flashed the lboot from that zipfile available at , but now I also cannot enter boot loader.
Ok, I was able to fix all that, by reflashing the RUU again and was able to get it working and successful. Doing the OEM boot removed my twrp recovery, which I had to reflash, and also formatted my sd card.
This was stressful as hell and learned a ton about this phone. The learning experience was worth it, but the stress was not =/
EDIT: WIFI DOES NOT AUTHENTICATE
For those stuck with my problem these are the steps I did.
I reflashed the newer RUU and once everything was peachy, I did a factory reset, that seemed to have fixed everything that was going on with my phone. I then added twrp recovery and reflashed my rom of choice. And that was the end of a very stressful night lol.
nervana1 said:
For those stuck with my problem these are the steps I did.
I reflashed the newer RUU and once everything was peachy, I did a factory reset, that seemed to have fixed everything that was going on with my phone. I then added twrp recovery and reflashed my rom of choice. And that was the end of a very stressful night lol.
Click to expand...
Click to collapse
All the four corner triangle thing means is that it didn't flash the last RUU mode zip completely that was attempted. The phone is still in ruu mode with four triangles. You can simply flash the RUU mode version of TWRP and it will clear the four triangles.
I searched the forums before posting. 73 results came up and I read through and followed instructions of 7 different posts that seemed similar to mine (including the ones that appear when making a new thread), but nothing has worked or I haven't found a situation like mine.
Hi.
I have a HUGE problem and need help.
I was on Cyanogen OS 12.1 and decided to install the latest Cyanogen OS 13.1. I downloaded the flashable zip. Booted into TWRP recovery and installed the zip file. I had always allowed my phone to reinstall Super SU in the past with great succes, but it seems I shouldn't have done that according to someone in Oneplus forums. Now my phone is stuck on the bootup animation that says "Cyanogen MOD ready". I also cannot boot into the recovery or safe mode using hardware keys. Please help! I don't want to lose my phone or my data!
Thanks for any advice.
note: I used the signed flashable zip from here.
EDIT: I was able to boot into recovery using the command "fastboot boot recovery.img". I cleared dalvik cache and flashed COS 13.1 zip. Currently waiting for phone to boot. Hope it doesn't get stuck on the bootup screen again.
EDIT2: It looks like my phone has booted successfully and is now optimizing apps for COS update! If I don't follow up, it means everything worked out great again!
EDIT 3: My phone finished "optimizing" apps. I thought it would take me to my launcher as all other times I've updated. To my surprise, the phone seemed to reboot and was stuck on the "splash screen" (Cyanogen MOD ready). After that, I got the "Android is starting" "Optimizing app xx of xxx" message again, which is incredibly weird and I think my phone might be in a bootloop. PLEASE HELP!
EDIT 4: I remembered that I did a nandroid backup last February so I restored it with "restore" in TWRP. My phone has been stuck on the "Cyanogen" boot screen for about 40 minutes. I'm lost.
To recap everything:
1. I was trying to manually upgrade from COS 12.1 to COS 13.1
2. My phone was rooted, had TWRP recovery and ADB debugging was enabled in dev options. I can enter fastboot mode using hardware keys. I cannot enter recovery using hardware keys (shows a blank screen), but I can enter recovery using "fastboot boot recovery.img.
3. After I flashed COS 13.1, I was asked (in TWRP) if I wanted to install SU and I said yes and flashed it. This is when I was in a loop of being stuck on COS 13.1 splash screen for about 5-10 minutes and then my phone was "optimizing app xx of xxx" for 15 minutes and then rebooted and did everything all over again.
4. I tried to restored a nandroid backup using "restore" in TWRP, but phone is stuck in "cyanogen" splash screen for more than 40 minutes.
No replies...
Not sure what to do at this point.
I ended up wiping data and performing a factory reset through TWRP. Might try to upgrade again in the future.
So I updated to the latest version of KatKiss, did a wipe first (from Kang TWRP), everything seemed fine the tablet booted and everything was working. I powered off the tablet and went on with my day, when I turned it on again it's in a boot loop. I get the ASUS-logo (at least one time I also got the KatKiss-logo), it tries to boot and it returns to the ASUS-logo. I tried to do a wipe in recovery (Kang TWRP) but it doesn't complete, after around 30 seconds it jumps automatically to the ASUS-logo and tries to boot again.
Any solution greatly appreciated.
Glomgold said:
So I updated to the latest version of KatKiss, did a wipe first (from Kang TWRP), everything seemed fine the tablet booted and everything was working. I powered off the tablet and went on with my day, when I turned it on again it's in a boot loop. I get the ASUS-logo (at least one time I also got the KatKiss-logo), it tries to boot and it returns to the ASUS-logo. I tried to do a wipe in recovery (Kang TWRP) but it doesn't complete, after around 30 seconds it jumps automatically to the ASUS-logo and tries to boot again.
Any solution greatly appreciated.
Click to expand...
Click to collapse
Please try to get into "Fastboot Protocol" by holding the button volume down at the time before the boot loop starts newly again. Three icons will appear. The first one, RCK; is blinking. Press volume up and your TWRP should start. Hopefully you have Kang TWRP. If so you may install rom, gapps and SuperSU again by following exactly the install instruction by Timduru here: https://forum.xda-developers.com/tra...t/rom-t3453702.
(Don't forget to do "Format Data" through Kang TWRP as first of all. It takes up to one hour. Be patient and let it run.)
I'm sorry, but if you are really not able to boot into either fastboot or recovery the tablet is bricked for good!
Thank you for advice.
The tablet is up and running again. I wasen't able to boot into Kang TWRP, but I was able to use fastboot. I ran a lot of erase commands that I found in a guide, erase boot, erase recovery, erase userdata etc., afterwards I flashed stock rom. It still wouldn't boot, but I installed Kang TWRP with fastboot and I was able to use TWRP again so I was able to flash a custom rom and it booted up again.
Glomgold said:
Thank you for advice.
The tablet is up and running again. I wasen't able to boot into Kang TWRP, but I was able to use fastboot. I ran a lot of erase commands that I found in a guide, erase boot, erase recovery, erase userdata etc., afterwards I flashed stock rom. It still wouldn't boot, but I installed Kang TWRP with fastboot and I was able to use TWRP again so I was able to flash a custom rom and it booted up again.
Click to expand...
Click to collapse
Congratulations! You did a good job. Seems as if you did the well known "Buster99 Solution" successfully in order to get back on stock rom. Keep it in your mind for ever. It may be also helpfully in other cases of trouble.
odd loop.
Glomgold said:
So I updated to the latest version of KatKiss, did a wipe first (from Kang TWRP), everything seemed fine the tablet booted and everything was working. I powered off the tablet and went on with my day, when I turned it on again it's in a boot loop. I get the ASUS-logo (at least one time I also got the KatKiss-logo), it tries to boot and it returns to the ASUS-logo. I tried to do a wipe in recovery (Kang TWRP) but it doesn't complete, after around 30 seconds it jumps automatically to the ASUS-logo and tries to boot again.
Any solution greatly appreciated.
Click to expand...
Click to collapse
Randomly my tablet started doing the boot loop. It would show the Asus Logo, then the Kattkiss logo and it will go to a screen saying optimizing apps. It would go through and optimize all 1-75 then reboot and start the process again. I unhooked the dock and allowed it to do this until the battery was completely dead. Next day same thing. This tablet has been unchanged OS wise for about 2 years. only used for youtube videos. Super odd that it randomly broke.
It does have a good TWRP version installed v2.8.7.0. So I tried flashing the 7.1 rom, su, gapps and wiped cache/dalvik. Did not correct it. So then did factory reset. Still no go. Now i am doing a full wipe / format. After format i will reinstall katkiss 7.1, su, and gapps. Hopefully i get back to normal after that.
Absolutely no idea what spurred this or what caused the break. Has been completely normal for a very long time. Weird.
Anybody else see anything like this?
thereal35 said:
It does have a good TWRP version installed v2.8.7.0.
Click to expand...
Click to collapse
I don't think so. In order to get this Rom installed on your devise you need Kang TWRP as advised by @timduru https://forum.xda-developers.com/transformer-tf300t/development/recovery-twrp-t3046479.