Develop Bugs

[Q] HTC One V Recovery doesn't work, Phone Stuck

Hi Y'all, sometime lurker, first time poster.
I got an HTC One V (CDMA, Virgin Mobile) today and given the relative ease of rooting my old Droid Inc I thought it would be a breeze to do this phone as well, but I did not do enough research and messed it up. Here is what I did as best as I can recall:
I unlocked the bootloader without a problem using Fastboot.
Then I flashed CWM recovery through hasoon2000's all in one tool, but it didn't work. I believe I did not flash the correct CWM (CDMA). I tried reflashing stock recovery, and then CDMA CWM recovery, but I couldn't get past the white HTC with the red warning message.
Because I couldn't get recovery to work, I thought maybe I should flash the kernel. I was using hasoon2000's all in one tool, but I did not realize that it would try to boot into recovery in the middle of flashing the kernel (yeah, I'm a noob and an idiot).
So now it won't load into the standard ROM anymore, it just gets stuck on the HTC White screen with the Red Warning. I can get it to load the bootloader, and I tried flashing the kernel from the all in one tool through fastboot, but it didn't work.
Is there any way I can save my phone or am I out of luck?
Thanks for any help you can provide.

Get the stock boot.img and put it in your fast boot folder and go to cmd prompt and type
C:\fastboot
Fast boot flash boot boot.IMG
Make sure your in fastboot
Sent from my One V using xda app-developers app

Thanks XxlemonxX. I did that a few times and it didn't seem to stick.
But! While I was fastloading I went ahead and did the Superboot step found here:
http://forum.xda-developers.com/showthread.php?t=1598964
And the phone restarted! Huzzah! Now I just have to see if I can get a recovery actually working...

OK, so things got a little strange.
The phone booted up just fine, so I tried flashing CWM recovery again. It worked, and restarted into CWM recovery. The power button didn't seem to work for selecting various options for a while, it would just go to the screen with the cog and the top hat, until I held it down for a few seconds, after which the bottom buttons flashed, and at the bottom it said "back button enabled". Then the power button worked for selecting various options. (I'm not sure if this is how CWM recovery is supposed to work for the One V, as I can't find any definitive answers...). Anyways, ran a backup through recovery, but afterwards the phone wouldn't reboot again.
Since it worked before I ran the Superboot app through windows and bam, starts up again. Did a factory reset just to see if that would clear the rebooting problem, but it didn't. It did change, however. Now it goes to the white HTC screen with the red warning for a second, goes back to black, then goes to a really dark black with just the red warning barely visible for about 7~ seconds, then it powers down. The only way I can get a reboot into the ROM is to redo the Superboot app...
I'm a little nervous at this point. I tried flashing an MIUI rom through the CWM app but there was an error (I didn't write it down, sorry), and I can't find a reliable link to the stock RUU VM PrimoC Rom (jmz's links are down as far as I can tell). I just want a rom that will reboot without freezing, haha. Thanks again for any help.
tl;dr Phone only boots when Superboot app is flashed, try a different rom?

jimmymcsnakes said:
OK, so things got a little strange.
The phone booted up just fine, so I tried flashing CWM recovery again. It worked, and restarted into CWM recovery. The power button didn't seem to work for selecting various options for a while, it would just go to the screen with the cog and the top hat, until I held it down for a few seconds, after which the bottom buttons flashed, and at the bottom it said "back button enabled". Then the power button worked for selecting various options. (I'm not sure if this is how CWM recovery is supposed to work for the One V, as I can't find any definitive answers...). Anyways, ran a backup through recovery, but afterwards the phone wouldn't reboot again.
Since it worked before I ran the Superboot app through windows and bam, starts up again. Did a factory reset just to see if that would clear the rebooting problem, but it didn't. It did change, however. Now it goes to the white HTC screen with the red warning for a second, goes back to black, then goes to a really dark black with just the red warning barely visible for about 7~ seconds, then it powers down. The only way I can get a reboot into the ROM is to redo the Superboot app...
I'm a little nervous at this point. I tried flashing an MIUI rom through the CWM app but there was an error (I didn't write it down, sorry), and I can't find a reliable link to the stock RUU VM PrimoC Rom (jmz's links are down as far as I can tell). I just want a rom that will reboot without freezing, haha. Thanks again for any help.
tl;dr Phone only boots when Superboot app is flashed, try a different rom?
Click to expand...
Click to collapse
That is an old cwm. thats how it operates. Once your booted into the system you can install rom manager from play store and then you can update cwm so you wont have to enable the power button for use. But anyway seems you cant boot into a stable system right now. So If you are willing to follow theses instructions you can get back to factory conditions.
1. get the fastboot package if you dont have it. http://www.mediafire.com/?4dx982z93w8z7wk and put those files in a folder in the C drive.
2. Get the ruu from here its the top one if you are virgin mobile US. http://www.filefactory.com/f/0eafb9c43276c308/ look for RUU_PRIMO_C_ICS_40A_Sprint_WWE_VM_1.08.652.6_Radio_1.00.00.0521_2_NV_VM_3.46_0503_PRL61008_release_262414_signed.exe
3. This is how your going to get the stock recovery and stock kernel. run the ruu but dont do anything with it just yet. After the ruu is opened and is at the welcome screen just click and drag the window down out of the way and open ANY folder and type %temp% in the address bar of that folder and press enter. You will see a bunch of folders with titles like this "{B2B09672-51AB-4EF6-BDDF-50CB9719052B}" This is just an example. While in that temp folder just do a search for rom.zip and when you find it you can copy that file to your desktop and then just click cancel in the ruu welcome screen for now.
4. Open the rom.zip file with 7zip. You must use 7zip. The built in windows zip program wont work. Once its opened with 7zip, extract these two files 'recovery_signed.img' and 'boot_signed.img'. This is your stock recovery and stock kernel. Extract those to the fastboot folder.
5. You must somehow get your device into the bootloader again. I had the same symptoms as you did with the dark screen and dim red text. I just kept playing with the volume down during boot and eventualy got there. DO NOT USE VOLUME UP!!
6. Once your in the bootloader choose fastboot and plug your device in and it should now say fastboot usb at the top of the bootloader screen. Now run theses commands.
7. Commands to run.
fastboot flash recovery recovery_signed.img
fastboot reboot-bootloader
fastboot erase cache
fastboot flash boot boot_signed.img
fastboot reboot-bootloader
fastboot erase cache
fastboot oem lock
fastboot reboot-bootloader
fastboot erase cache
8. Now while in bootloader fastboot usb still just run the ruu and follow all instructions. Make sure you have atleast 30% battery while performing this. And if all goes well you will be back to square one.

[Q] Stuck in bootloop (pls move if I'm repeating a tousand other similar Q's!)

Hi there,
I've been a bit of a [email protected] and fudged my Huawei P6. I Was on South African Vodacom Stock Jelly Bean Rom, read this forum and got so excited about the world out there that i thought, why don't i try flashing a rom, i've only bricked a sgs2 and lg-g2 before... I should know what to do by now (never done a day's computer course in my life!)!
So flashed kitkat beta and then tried to flash Kit Kat... I have left the phone for about a week in the hopes I'd come back to it & it would miraculously work as I've read a lot of the forum posts on here and have a gut feeling I'm screwed so hoping one of you Huawei P6 XDA Guru's can Help. From what I remember I did this...
1) Rooted the phone with SRS Root or Root Genius
2) After a few attemps managed to install official kitkat beta from dload/update.app from external SD Card so I could then install official Chinese KiTKAT rom or HYDRO Rom.
3) Played with the kitkat beta for a while all working (bar the beta crashes etc) ( I think at that point I intalled CWMOD or TWRP)
4) It was very late, I should have gone to bed, I'd had a few beers, but no I carried on & was planning to install Hydrorom & (Mis)understood got mixed up with official chinese kit kat rom installation
5) Booted into recovery & flashed official chinense kitkat rom with GAAPS ticked to flash as well (maybe that will tell you guys if I was using CWM or TWRP!)
5.0117...c) If my memory serves me right I didn't (4am idiot/tired/few beers/rushing etc) wipe dalvic or any of that... just flashed from external sd card ZIP streight over kitkat beta (aaaarrgh!)
6) Phone is now stuck in bootloop with Huawei Ascend words first, then loading a Huawei flower logo. Goes no further, just stays on until battery flat...
7) Left phone plugged into power with screen on for a day hoping it was just taking a while to flash rom... & nothing happened
8) Tried the following but hope I'm doing them all wrong and you GURU's will have a giggle at my comlete lack of skills:
a) reboot phone - no luck​b) hold down power & +vol & -vol -... no luck just flower logo again​c) every combination of power and two volume buttons - no luck just flower logo​d) putting folder dload/update.app on external sd card and using b)method to flash update - no luck just flower logo​e) putting stock recovery.img on root of external sd card and doing b) - no luck just flower logo​f) putting all of extracted TWRP download " TWRP_Installer_20140414 on root folder of external sd card - no luck​g) spending 4 hours finding a "how to remove the battery from huawei P6" link and watched a russian guy remove battery on you tube. Did that as read that can reset boot loader/recovery.... no luck​h) downloaded various versions of Android SDK Tools. Phone shows up as a "please insert sd card" in windows file manager and appears "offline" when trying to access it from command prompt ADB etc​
checked that HiSuite was stopped in Task Manager etc, reinstalled drivers etc. One problem I'm hoping you'll all say is 100% to blame for SDK Tools not working is I'm on latest update of Windows 8.1 64bit...
Edit: Read other forum... I see the red led when turning phone on as well...
Edit: Just installed propper android sdk tools not small made up file and now phone changed from showing "offline" to "unauthorised" in adb...
So, please help.

Fixed it
Ok managed to fix this and hope it will help others. Was up till 2am last night after deciding to give it another go after getting no replies! The main problem here must have been that as device was seen as unrecognized on PC and I couldn't get past boot screen so there was no way to allow debugging/authorize I.e. No pop up on phone as stuck in Hauwei flower screen.
Previously I Couldn't get fastboot or adb on PC to do anything, just kept saying phone was offline or unauthorized.
Rebooted phone from boot loop screen of huawei flower on screen holding power and - vol button for a long time until only boots to huawei ascend words logo (phone still plugged into PC), let go of both. PC makes sound to show there is USB device, now it doesn't boot the huawei flower screen just stays on the Hauwei ascend screen (I think normally this would open recovery etc), so maybe it is in recovery just not showing on screen... I don't know?!
Adb devices says no device however... And obviously no adb commands work at all...
However, fastboot commands for some reason work even though devices still shows nothing... so I tried various commands but what worked for me was typing the following in command promt on PC:
Fastboot flash boot boot.img (Stock)
Where all the img,zip,app files I was flashing were were in the platform-tools folder where adb and fastboot are.
Then
Fastboot flash recovery recovery.img. (Stock)
Then I think what did it, I was obviously on a broken twrp recovery... Was I flashed
Fastboot flash recovery twrp_2_6_3_3_recovery.img
To my amazement twrp touch recovery loaded and I could then go about wiping dalvik etc and reflashing all the correct files.
So I'm now finally running HYDROROM_V7
All the files I used are on the hydro rom page here so thanks to them for that! :
http://forum.xda-developers.com/showthread.php?t=2630208
Hope this works for all of you stuck in bootloop etc as I really thought my phone was stuffed!
Ciao

pommiesa said:
Ok managed to fix this and hope it will help others. Was up till 2am last night after deciding to give it another go after getting no replies! The main problem here must have been that as device was seen as unrecognized on PC and I couldn't get past boot screen so there was no way to allow debugging/authorize I.e. No pop up on phone as stuck in Hauwei flower screen.
Previously I Couldn't get fastboot or adb on PC to do anything, just kept saying phone was offline or unauthorized.
Rebooted phone from boot loop screen of huawei flower on screen holding power and - vol button for a long time until only boots to huawei ascend words logo (phone still plugged into PC), let go of both. PC makes sound to show there is USB device, now it doesn't boot the huawei flower screen just stays on the Hauwei ascend screen (I think normally this would open recovery etc), so maybe it is in recovery just not showing on screen... I don't know?!
Adb devices says no device however... And obviously no adb commands work at all...
However, fastboot commands for some reason work even though devices still shows nothing... so I tried various commands but what worked for me was typing the following in command promt on PC:
Fastboot flash boot boot.img (Stock)
Where all the img,zip,app files I was flashing were were in the platform-tools folder where adb and fastboot are.
Then
Fastboot flash recovery recovery.img. (Stock)
Then I think what did it, I was obviously on a broken twrp recovery... Was I flashed
Fastboot flash recovery twrp_2_6_3_3_recovery.img
To my amazement twrp touch recovery loaded and I could then go about wiping dalvik etc and reflashing all the correct files.
So I'm now finally running HYDROROM_V7
All the files I used are on the hydro rom page here so thanks to them for that! :
http://forum.xda-developers.com/showthread.php?t=2630208
Hope this works for all of you stuck in bootloop etc as I really thought my phone was stuffed!
Ciao
Click to expand...
Click to collapse
Hey very good that you managed to fix your problem, when I first read your question I didn't had any ideas on how to fix it. But you had a bootloop I think and when you press power and vol- until it reboots you come in the bootloader, on our device it only shows the bootlogo so its seems that it is stuck but actually you are in the boot loader and can use fastboot commands. So glad you fixed your problem.
Gesendet von meinem P6-U06

(STUCK) Kindle goes into "fastboot mode" screen even when entering recovery

Yesterday was my first time rooting a Kindle Fire, and the root process went very smoothly when I followed this guide which uses saferoot: http://forum.xda-developers.com/kindle-fire/development/how-to-kindle-fire-1-update-6-3-3-t2814955
While I made use of this guide for flashing FFF and TWRP: http://forum.xda-developers.com/showpost.php?p=54124313&postcount=3
After successfully rooting it, I wanted to try the OtterX ROM/TWRP/Bootloader, since I read the comments and saw it would be good to try it out. After flashing the bootloader (otterx-u-boot_v2.05), the kindle kept rebooting showing the logo and the option to 'press power to enter boot menu'. I thought this was normal so I didn't mind it. (During this time, I could still enter recovery.) I proceeded to Step 2 which was flashing TWRP for OtterX (I downloaded zip-otterx-twrp-2.8.2.0-recovery.zip and installed it using the previous TWRP I flashed: openrecovery-twrp-2.2.2.1-blaze.img).
I wasn't able to remember what I did next, but I know I was already having issues. I was getting anxious and sleepy at the same time, I remember exploring the boot menu and foolishly/stupidly tried the EMMC Corruption Fix, without even trying to research about it beforehand, so now I'm stuck at the "fastboot mode" screen (I've attached a photo of the screen). Whenever I turn on the device, it shows the kindle fire logo and the option to enter boot menu. If I let it be for a while, it goes into the "fastboot mode" screen, the same thing happens when I try to choose "continue boot" or "recovery boot". Windows doesn't recognize it anymore whenever I try to connect it too (I'm using Windows 8.1 by the way.)
Please help, I've tried reading about how I could restore the kindle to the state it used to be after I rooted it, but no luck, I couldn't find anyone encountering the same problem as me since I think I'm the only one stupid enough to apply that EMMC corruption fix without knowing or reading what it actually does. Thanks in advance to anyone who could help.

Try
Download adb/fastboot files, if you have not yet.
Power off Kindle
In command prompt
Run command to flash recovery
Power on kindle
See [Video] Flashing TWRP in OtterX bootloader

THANK YOU SO MUCH for your reply. I tried it as soon as I woke up. I found out that the problem was the driver, I reinstalled it and flashed the recovery using the fastboot command.
Sent from my C5502 using XDA Free mobile app

Tried flashing CM13, now can't enter normal boot

So I already had a rooted (and I'm pretty sure unlocked bootlader) version of the stock Asus and wanted to put CM13 nightly on there. Everything was going smooth until I got to the stage where I have to load into TWRP and I got the error screen with the little dead alien and the red symbol.
Now I can't enter normal boot, but entering recovery mode seems to work. I tried the option to side load a package from ADB on that screen but nothing worked (.zip files extracted, but I got an error on the phone).
As you can tell, I'm really new to this so any help would be greatly appreciated. I tried looking around, but it seems the more common issue is people not being able to enter recovery mode or something similar.
Thanks

Looks like your doing it wrong. Being rooted does not necessarily mean that your bootloader is unlocked.
By the looks of it your in recovery mode with the dead robot with the "error" message. That is normal. To reboot back into system you either have to press (I don't remember) power button and volume up or down button. Then you should see some options with reboot to system. Or if that does not work you can hold the power button till it turns off.
Then you get back into Android, download the official bootloader unlock tool from ASUS and install it on your device. NOTE: If you updated to MM then this will not work and this will void your warranty.
Run the tool and press unlock and it should reboot into fastboot where it should begin the unlocking process. I believe it should automatically reboot and you should see that the Asus logo is now black instead of white. If not, repeat the process.
You can now proceed to flash twrp recovery. Boot into fastboot/bootloader mode either with "adb reboot bootloader" or hold a specific set of buttons while off to go directly into fastboot.
On the computer, connect your device and type in "fastboot flash recovery (path to twrp IMG without brackets)"
When done you should be able to reboot into twrp recovery where you can flash the cm13 zip.
Hope this helped.

Phone might be bricked. Need help to find a solution!

Hello everyone! Complete dumbass here!
I was following the guide to root my razer phone. I've had it for a couple months, and decided to root it. I followed the guide here https://forum.xda-developers.com/razer-phone/how-to/twrp-magisk-fullproof-guide-razers-wifi-t3756137
After a couple bumps in the road, such as fastboot commands not working, not being recognized, etc. I finally was able to unlock bootloader and install twrp. But it was #9 that got me stuck again.
"9.) Once in recovery, go to the install button, and select Install Zip, and select Magisk-v16.0.zip."
In recovery, adb devices and fastboot devices yielded no devices attached. Doing a search, I came across another forum post where it states the sdcard is encrypted and can't be accessed in twrp, and the fix is to do something like "Wipe>Wipe Data> Type Yes" and that should factory set the card. I did this and rebooted the device. I waited for a half hour for the animated PixelFloatingInACircle logo to be done with it's floating in a circle, but ended up going to bed and letting it die. Woke up this morning, plugged it in, got the razer logo splash screen with the orange text telling me of my impending doom, then went back to the animation. I let my dog out and came back and it was still on. I unplugged it and am letting it die again to see if there's another solution.
I'm wondering if anyone else came across this issue, and if so, how did they fix it? Any help would be appreciated.

Use the factory images in the developer portal. You have to manually install the fastboot driver or you won't see the phone in fastboot devices. After that you can flash_all.bat.
PS: if you just want root you can use magisk installer to patch the boot image (from the factory images) and then flash the patched_image.img. That's it, now you have root via magisk

waiflih said:
Use the factory images in the developer portal. You have to manually install the fastboot driver or you won't see the phone in fastboot devices. After that you can flash_all.bat.
PS: if you just want root you can use magisk installer to patch the boot image (from the factory images) and then flash the patched_image.img. That's it, now you have root via magisk
Click to expand...
Click to collapse
The problem is when I try to enter download/recovery mode after charging the battery a little, it doesn't go to that menu. Instead, it skips right to the particle logo, and that's where it hangs.
The only guide I saw was the one I listed. Is there a guide for this magisk installer?(Ya know, in case I figure the first problem out, so I might try my hand at potentially creating another)

i think there is a way to hard reboot the phone, so you can do that and then hold the vol- key to start in bootloader mode when it reboots.
gonna check the correct buttons.
Edit: the button combination is power+vol+ for about 10-15 seconds, and the phone will reboot. You have to connect the phone via usb cable (before rebooting) to the computer (the only thing i'm not sure is if you have to have the fastboot drivers in the pc installed previously or if you can do it after entering fastboot) and just after the screen goes black while hard rebooting you have to release all the buttons and then press and hold the vol- button. The combination of vol- and the usb cable on boot seems to trigger fastboot mode.
I think the guide is in the guides forum, but the way it worked for me was without twrp:
- install magisk manager from this link -> https://github.com/topjohnwu/MagiskManager/releases/download/v5.7.0/MagiskManager-v5.7.0.apk
- push your boot.img (the easiest way is getting it from the factory image corresponding to the firmware you are using) to the sdcard
- open magisk manager -> install -> patch image only -> boot.img
- this will generate a patched_boot.img in /sdcard/MagiskManager
- copy that file to your pc
- go to fastboot and flash that patched image: fastboot flash boot patched_boot.img
- enjoy root, and you can use magisk hide for apps that don't like root
Regards

waiflih said:
i think there is a way to hard reboot the phone, so you can do that and then hold the vol- key to start in bootloader mode when it reboots.
gonna check the correct buttons
Click to expand...
Click to collapse
Tried this originally after I let it die the first time. It still boot to the animation logo.

Bloodeagle said:
Tried this originally after I let it die the first time. It still boot to the animation logo.
Click to expand...
Click to collapse
Read the edit, I found that the trigger is having the usb cable connected to the pc. Try that, or you can also try to adb while the device is booting (particles logo). Sometimes adb is responsive even when booting. There you can try to adb reboot bootloader

waiflih said:
i think there is a way to hard reboot the phone, so you can do that and then hold the vol- key to start in bootloader mode when it reboots.
gonna check the correct buttons.
Edit: the button combination is power+vol+ for about 10-15 seconds, and the phone will reboot. You have to connect the phone via usb cable (before rebooting) to the computer (the only thing i'm not sure is if you have to have the fastboot drivers in the pc installed previously or if you can do it after entering fastboot) and just after the screen goes black while hard rebooting you have to release all the buttons and then press and hold the vol- button. The combination of vol- and the usb cable on boot seems to trigger fastboot mode.
I think the guide is in the guides forum, but the way it worked for me was without twrp:
- install magisk manager from this link -> https://github.com/topjohnwu/MagiskManager/releases/download/v5.7.0/MagiskManager-v5.7.0.apk
- push your boot.img (the easiest way is getting it from the factory image corresponding to the firmware you are using) to the sdcard
- open magisk manager -> install -> patch image only -> boot.img
- this will generate a patched_boot.img in /sdcard/MagiskManager
- copy that file to your pc
- go to fastboot and flash that patched image: fastboot flash boot patched_boot.img
- enjoy root, and you can use magisk hide for apps that don't like root
Regards
Click to expand...
Click to collapse
Progress! Got it into download mode. I have the boot.img I got from razer, should I push that and see if it boots normally?

Bloodeagle said:
Progress! Got it into download mode. I have the boot.img I got from razer, should I push that and see if it boots normally?
Click to expand...
Click to collapse
As you already wiped the data partition, you should use the flash_all script. But yes, you can try flashing each partition

waiflih said:
As you already wiped the data partition, you should use the flash_all script. But yes, you can try flashing each partition
Click to expand...
Click to collapse
I moved the flash_all script into the tools folder and after a little while, the phone booted up into setup! After a couple taps, I've realized the wifi isn't working, which I know is a known issue. I'm gonna let it sit for the night and finish it in the morning!
EDIT : Soooo, I know I said I was going to bed, but I decided to fix the wifi issue, which in turn, also rooted my phone. I've downloaded the root checker, and it confirms it! Thanks so much Waiflih! You rock!

Hi guys, it seems I'm having the same problem and basically after unlocking my bootloader and flashing twrp to both of my slots I'm stuck on "Your device has been unlocked and can't be trusted" booting up infinitely.
The USB plug in and holding the volume - button doesn't bring up "download mode" and no matter what buttons I try and press on my phone my computer doesn't recognize ANYTHING connected to it anymore.
Bloodeagle, how did you manage to get "download mode" back onto your phone? it seems like mine refuses to do anything like download mode.

saberhashemi said:
Hi guys, it seems I'm having the same problem and basically after unlocking my bootloader and flashing twrp to both of my slots I'm stuck on "Your device has been unlocked and can't be trusted" booting up infinitely.
The USB plug in and holding the volume - button doesn't bring up "download mode" and no matter what buttons I try and press on my phone my computer doesn't recognize ANYTHING connected to it anymore.
Bloodeagle, how did you manage to get "download mode" back onto your phone? it seems like mine refuses to do anything like download mode.
Click to expand...
Click to collapse
Have you tried holding few combinations of different butt9ns for a minute or two to see if that results in you getting in downl9ad mode?