Develop Bugs

[Q] Soft-bricked One-V?

I seem to have soft-bricked my one-v and could really use some pointers.
The things I did to get the phone bricked:
- Unlock the bootloader
- Try to flash miui.
Since this attempt the phone only boots until the "quietly brilliant" screen appears (with a red "This build is for development purposes only..." warning, but I guess this just indicates the bootloader is unlocked right?)
Since then I have installed ClockWorkMod recovery image. This seems to work, I can get in recovery mode and do things like install specific zip files from sdcard.
Unfortunately whatever ROM I try to flash the result is the same: boot until the quietly brilliant screen and then nothing.
For instance, I tried to flash shpongle_primou_20130521.zip (the One-V is the GSM version) using the following steps:
- Download the above zip file
- Extract boot.img
- Copy the above zip file to sdcard using another phone (cannot boot with the one-v so I cannot use it to write to sdcard)
- Put the sdcard back into the One-V
- Start the phone in fastboot mode and connect to USB
- use fastboot to flash boot.img (flashboot flash boot boot.img)
- Switch to recovery mode
- Use ClockWorkMod to flash the zip file
- Reboot the phone
Result: hang in quietly brilliant screen. If I just let the phone alone it seems to reboot every 5 minutes or so.
I fear that I am doing something stupid due to a lack of understanding of some basic concept. Can you guys give me some pointers on how to proceed to unbrick the phone?

it seems u have not flashed the correct kernel for shpongle (the boot img inside zip doesnt work)
try this kernel (ONLY FOR SHPONGLE) http://www.mediafire.com/download/vj8vv8hjyhzg3xv/boot-HELLBOY-42-201305202359.img
Also do factory reset from recovery everytime u flash a rom( u can backup data via titanium backup)

Also, your command command should be fastboot flash boot boot.img.
Sent from my HTC One V using xda app-developers app

Awesome, I got SHPONGLE to work. Installing the correct boot.img and clearing all data did the trick.
Now I can try to install miui again but I have a stable situation (and backup ) to work with.
Thanks a lot!

I have the same issue with my HTC one V but it is the virgin mobile version ( I live in the east coast of U.S.A.)
Will I be able to use the same solution?
which is the right ROM and Kernel for me?

[Q] how to copy files to HTC ONE X thats stuck in boot loop

Hi Dudes and Dudettes.
PLease go easy on me - I am a noob.
Ive been handed a HTC ONE X (International version) that is stuck in aboot loop.
On power on, it simply goed to cyanogen load screen, and stays there forever (till the battery runs out or the phone is powered down)
I dont know what has been done to this phone, but I do know the following:
1. It seems to be rooted (Says UNLOCKED in Fastboot/bootloader screen)
2. Has CWM installed, can access it via Recovery.
3. Can not be restored via Backup/Recovery in CWM.
4. Does not have any roms on the device (tried zip file recovery - doesnt work)
5. Wiping of caches doesnt help.
6. Factory reset doesnt work either.
So I am thinking that I should prolly get a rom on the device and install it.
My question is HOW do I get a ROM on this phone if it is stuck in a loop?
Seem like windows picks it up (its visible in device manager) but doesnt show up as a drive in my computer.
Any help will be greatly appreciated.
Cheers!

heinrichvr said:
Hi Dudes and Dudettes.
PLease go easy on me - I am a noob.
Ive been handed a HTC ONE X (International version) that is stuck in aboot loop.
On power on, it simply goed to cyanogen load screen, and stays there forever (till the battery runs out or the phone is powered down)
I dont know what has been done to this phone, but I do know the following:
1. It seems to be rooted (Says UNLOCKED in Fastboot/bootloader screen)
2. Has CWM installed, can access it via Recovery.
3. Can not be restored via Backup/Recovery in CWM.
4. Does not have any roms on the device (tried zip file recovery - doesnt work)
5. Wiping of caches doesnt help.
6. Factory reset doesnt work either.
So I am thinking that I should prolly get a rom on the device and install it.
My question is HOW do I get a ROM on this phone if it is stuck in a loop?
Seem like windows picks it up (its visible in device manager) but doesnt show up as a drive in my computer.
Any help will be greatly appreciated.
Cheers!
Click to expand...
Click to collapse
flash this custom recovery link
then go into recovery
connect your phone to PC or laptop
select USB mass storage in recovery
copy rom file into sd card
and flash rom in recovery
extract boot.img from rom.zip file in pc or lappy
flash boot.img in fastboot mode
and good to go..!!:good:

Poojan Patel said:
flash this custom recovery link
then go into recovery
connect your phone to PC or laptop
select USB mass storage in recovery
copy rom file into sd card
and flash rom in recovery
extract boot.img from rom.zip file in pc or lappy
flash boot.img in fastboot mode
and good to go..!!:good:
Click to expand...
Click to collapse
Thanks, i am going to try that now.
Not sure how to flash the custom recovery, but sure ill figure it out.
Will let you know.
thanks!

Shot a lot mate!
Its working. Must have been the img file.
Thanks!!!

If you're HTC ONE X is bricked/soft bricked, try this

Requirements:
HTC ONE X (mine was international but you are free to try anyways )
UNLOCKED BOOTLOADER
PATIENCE.
1. Download Fastboot
If you have adb and fastboot already you can skip STEP 1 and STEP 2
2. Download adb
3. Download cm-10.2.1-endeavoru.zip (https://download.cyanogenmod.org/?device=endeavoru)
(I used this one , it's justs so you get your SD Card Working again and you can
put ROMS and everything on it again)
4. Download openrecovery-twrp-2.4.0.0-endeavoru-JB (http://techerrata.com/browse/twrp2/endeavoru)
(This one will be used because it has touch ability's and you can install ROMS with it )
4.1 Or you can download recovery-clockwork-touch-6.0.4.7-endeavoru.img (a.k.a Philz recovery)
(This one will be used because it has touch ability's and you can install ROMS with it )
( I used Philz recovery 5.15.9.img (provided by Mr Hofs -> who is a great guy btw)
5. Download openrecovery-twrp-endeavoru-2.1.7 (http://techerrata.com/browse/twrp2/endeavoru
(This one will be used for adb push commands, openrecovery-twrp-endeavoru-2.1.7 has a built
in ability for your sd-Card , adb can recoginze it but the problem is your touch will not work.)
6. Go into bootloader -> fastboot and do this:
6.1 fastboot flash recovery openrecovery-twrp-endeavoru-2.1.7.img
7. Go into recovery (Hboot -> recovery)
7.1 just open the recovery, your touch will probably not work. DONT LOCK IT JUST LEAVE IT OPEN
(ADB sideload didn't work for me so that's why we are going to do this)
IF YOUR TOUCH WORKS YOU CAN SKIP STEP 8
7.2 do this command: adb devices
If you don't find your devices in this then the next steps will not work.
YOU HAVE TO SEE YOUR DEVICE
7.3 do this command: adb push cm-10.2.1-endeavoru.zip /sdcard/
You can only do cm-10.2.1-endeavoru.zip if the zip file is located in the same folder your using
with command. I'm not sure about /sdcard/ . I cant remember anymore But this will put the
but this will put the zip Directly on your SDcard.
8. Go to bootloader -> fastboot
8.1 do this command: fastboot flash recovery openrecovery-twrp-2.4.0.0-endeavoru-JB.img
8.2 or do this command: fastboot flash recovery Philz recovery 5.15.9.img
Your touch wasn't working but it will work now.
9. Go to booloader -> fastboot
9.1 extract the boot.img from the Download cm-10.2.1-endeavoru.zip into the fastboot folder
9.2 do this command fastboot flash boot boot.img
9.3 fastboot erase cache
10. Go back to recovery
10.1 Wipe User Data
10.2 Wipe data cache
10.3 Go to advanced -> wipe Dalvik Cache
11. Install zip from sdcard
11.1 Choose cm-10.2.1-endeavoru.img
11.2 Install the zip WITH full wipe
12. After the install, reboot. You should have a full functional HTC ONE X now
13. Now but your ROM's(ZIP FILES)/Recovery(ZIP FILES)/Kernels and everything you want on your HTC because
You can see your HTC on your PC again!

Why are you flashing so many recoveries ?
Just flash Philz 5.15 for non kitkat roms or twrp2 for use with all roms. On those 2 recoveries all features work including touch on all hboot numbers. You don't need 2.4 at all !
And both recoveries support UMS inside the recovery. I think you only made it a bit hard on yourself this way. The rom (CM) didn't make your sdcard work again btw.....any rom does but it has to be installed all in the correct way
Sorry to say but your steps are a bit of a mess
I would have explained it like this....taking in mind that knowing fastboot is mandatory and common :
1: flash either Twrp2 or Philz 5.1.5 (for non kitkat roms)
2: enter the recovery and mount the sdcard in the mount menu, wait literally minutes to let the sdcard pop up
3: copy the desired rom
4: unmount and perform a full wipe (that means to wipe ALL except sdcard)
5: install the rom.zip
6: reboot to the bootloader and flash the boot.img from the desired rom
7: reboot
Done !

Mr Hofs said:
Why are you flashing so many recoveries ?
Just flash Philz 5.15 for non kitkat roms or twrp2 for use with all roms. On those 2 recoveries all features work including touch on all hboot numbers. You don't need 2.4 at all !
And both recoveries support UMS inside the recovery. I think you only made it a bit hard on yourself this way. The rom (CM) didn't make your sdcard work again btw.....any rom does but it has to be installed all in the correct way
Sorry to say but your steps are a bit of a mess
I would have explained it like this....taking in mind that knowing fastboot is mandatory and common :
1: flash either Twrp2 or Philz 5.1.5 (for non kitkat roms)
2: enter the recovery and mount the sdcard in the mount menu, wait literally minutes to let the sdcard pop up
3: copy the desired rom
4: unmount and perform a full wipe (that means to wipe ALL except sdcard)
5: install the rom.zip
6: reboot to the bootloader and flash the boot.img from the desired rom
7: reboot
Done !
Click to expand...
Click to collapse
The problem with this was that when I mounted my sdcard nothing popped up. (I litterly waited 30 minutes) I explain it this way because when following other threads explaining how to "unbrick" your phone. I got a lot of issues during the proces. Like SD-card not mounting, fastboot not working, adb not working, touch screen not working, promises of recovery's that your device wil be recognized for usb sideload, ... I ran into a lot of problems and I had to figure it out myself how I had to unbrick my HTC because I forgot to take a back-up. And these were the steps I did.I know your explanation is more 'ideal" but sometimes people can't follow the ideal path because of issues/bugs/problems and that's where my thread comes in

If it doesn't pop up its a pc driver issue

Mr Hofs said:
If it doesn't pop up its a pc driver issue
Click to expand...
Click to collapse
For me it wasn't I had properly installed all drivers. it just said endeavoru on my devices. And i couldn't connect. But once I installed the TWRP recovery it showed HTC ONE X and it worked

The twrp did nothing, as i said .... it was a driver issue. Once you booted to the bootloader it got picked up and drivers were added/modified correctly. If the drivers were installed properly it should say MYHTC .....

@vsp33ddyv MAAAAAAAAAN you saved me!!! I soft bricked my dad's phone by accidentally flashing the recovery to the boot partition as well as the recovery partition so the stock ROM was overwritten by the recovery. I wasn't planning on flashing any ROMs so there was no rom zip on my sdcard. I downloaded CM11, tried sideloading it through adb but it kept saying it didn't recognize the device. I tried USB storage mounting but that didn't work either (no matter how long I waited). I would have NEVER guessed that all I needed to do was download that broken (I say broken because touch doesn't work so basically nothing works) TWRP recovery img!!!! @Mr Hofs, sir, you were wrong. It wasn't the drivers. ADB didn't recognize my device, I changed my recovery and BAM it's suddenly there. I had already rebooted the device a million times so it's not like the drivers suddenly decided to get installed (there were no notifications either).
So thank you thank you thank you SO DAMN MUCH!

Thank you very much.
If it hadn't been for your tutorial i would've had to throw the phone.
Many thanks.

OnePlus 3 bootloader defaulting to recovery

Hello,
I am having a problem where my phone is only, as far as I can tell, willing to boot into recovery. From the system, doing a normal reboot ends up in recovery, from powered off it goes into recovery, rebooting from recovery to system ends up back in the recovery, and the fastboot menu's "Continue" option goes reboots to recovery. The only way I can get into the system is to boot via fastboot -- i.e.,
Code:
fastboot boot boot.img
Where boot.img is the one packaged with the rom I am currently running.
This is not convenient because I need to connect it to a computer!
Is there some way to tell the bootloader to not boot recovery by default?
I have tried simply flashing the boot.img from above with:
Code:
fastboot flash boot boot.img
Which doesn't have any noticeable effect.
I suspect I broke something last night kicking around. I flashed the Open Beta 10 Modem & Firmware, then flashed the Open Beta 10 recovery, before changing my mind and installing TWRP 3-28 and Resurrection Remix v5.8. Somewhere in there, fastboot -w got run, but I don't think I did anything else potentially destructive.
Thanks for reading!

Hmm... Try install boot into recovery partition and recovery into boot? I know it's sound like a joke, but it will probably help you while u wait for a beter solution or just solution to repair that problem.
Anyway - maybe try flash old MM firmware?

A solution for me...
For anyone who rolls along and sees this in the future, my fix was:
0. Take a backup of sdcard AND data -- Step 2 will wipe data and sdcard without asking
1. Download the official recovery for the OnePlus 3
2. Use fastboot to boot (I didn't even have to flash) the official OnePlus 3 recovery AGAIN: WARNING: This step wipes all data without asking for confirmation!!!
I have now installed TWRP-3.0.4.0 and Resurrection Remix v5.8.1-20170202 and everything seems to be working just fine.
Thanks to @sylviohneto for finding this fix here: https://forum.xda-developers.com/oneplus-3/help/critical-bootloader-boot-recovery-fresh-t3530283

I had same problem so for that just take nandroid backup of data and while in turn copy it to pc and any other backup of data you need then format all the partions and reinstall rom and restore data... And if your lock screen have security then check Google you will have to delete a file called locscreen.db from file manager in twrp to access your phone

Pixel Experience boot loop + string of stupid decisions: is there any way out?

Hi there,
I think I (soft? hard?) bricked my whyred today after trying to install Pixel Experience (Android 10). At this time, I'm left with a flashed PE Plus that is stuck at the Google logo animation (e.g. unable to access USB debug settings); stock MIUI recovery; and fastboot, which is not recognized by ADB as I haven't had a successful boot since I flashed PE, so I can't turn USB debug on. I think I've exhausted my options, but maybe someone has a smart solution.
For those who think they can help, let me describe in detail what I did:
0) I became a dev, turned USB debug on, installed Minimal ADB and Fastboot, latest Xiaomi drivers, moved flashable zips into internal storage etc.
1) I unlocked my bootloader through Mi Unlock.
2) I successfully flashed TWRP-3.3.1.0-whyred via ADB/Fastboot and rebooted. After getting back into MIUI, I booted into recovery, which was back to stock (MIUI seems to have overwritten my recovery). At that point (probably a big mistake) I gave up on flashing TWRP and went ahead to boot right into it via ADB instead, without flashing.
3) After a successful boot into TWRP 3.3.1.0, it asked me for a decryption password. Nothing worked, so I kept googling and found out that my version of android needs TWRP 3.3.1.1, which was not on the official TWRP website yet, to decrypt automatically. I booted into TWRP 3.3.1.1 via ADB (but didn't flash), made a backup of my stock ROM, did a wipe (art/dalvik cache, cache, data, system, vendor), flashed Pixel Experience and rebooted.
4) Bootloop, I was stuck on the Google loading animation for over 20 minutes, nothing happened.
5) I panicked.
6) I tried to flash TWRP 3.3.1.1 via ABD but my PC didn't recognize my phone - probably because, for lack of successful boots, I have not managed to turn on USB debug.
7) I tried to connect to Mi Assistant through stock recovery. It didn't recognize my phone, probably for the above reason.
8) I did a data wipe through stock recovery and rebooted, hoping for whatever issue kept PE from booting normally to get resolved.
9) I'm stuck on the same Google loading animation for over 40 minutes now, no progress.
Does any of you guys see a way out, or is this story over? To recap, I have: 1) PE Plus in bootloop, no access to dev settings, 2) stock MIUI recovery with options to reboot, wipe data or connect to Mi Assistant, 3) stock fastboot, 4) a backup of my previous system on internal storage, 5) ADB on my computer that doesn't recognize my phone - no USB debugging. I don't know where to turn. I don't care much about data, I have everything in the cloud, but I'd like to save the phone if possible.
Thanks a lot.
Edit: Problem resolved - even though the connected device didn't show up in ADB on PC (adb devices came back empty), the phone was still responsive to fastboot reboot and fastboot flash recovery via PC, so I could flash TWRP 3.3.1.1 & clean flash PE. For anyone struggling with PE bootloops: make sure to 1) use TWRP 3.3.1.1 to flash, 2) do a dalvik/cache wipe after flashing the ROM and 3) not to install the TWRP app before the first successful boot - it was neglecting either 2) or 3) that caused my bootloop. The ROM itself is amazing!

mkohan said:
Hi there,
I think I (soft? hard?) bricked my whyred today after trying to install Pixel Experience (Android 10). At this time, I'm left with a flashed PE Plus that is stuck at the Google logo animation (e.g. unable to access USB debug settings); stock MIUI recovery; and fastboot, which is not recognized by ADB as I haven't had a successful boot since I flashed PE, so I can't turn USB debug on. I think I've exhausted my options, but maybe someone has a smart solution.
For those who think they can help, let me describe in detail what I did:
0) I became a dev, turned USB debug on, installed Minimal ADB and Fastboot, latest Xiaomi drivers, moved flashable zips into internal storage etc.
1) I unlocked my bootloader through Mi Unlock.
2) I successfully flashed TWRP-3.3.1.0-whyred via ADB/Fastboot and rebooted. After getting back into MIUI, I booted into recovery, which was back to stock (MIUI seems to have overwritten my recovery). At that point (probably a big mistake) I gave up on flashing TWRP and went ahead to boot right into it via ADB instead, without flashing.
3) After a successful boot into TWRP 3.3.1.0, it asked me for a decryption password. Nothing worked, so I kept googling and found out that my version of android needs TWRP 3.3.1.1, which was not on the official TWRP website yet, to decrypt automatically. I booted into TWRP 3.3.1.1 via ADB (but didn't flash), made a backup of my stock ROM, did a wipe (art/dalvik cache, cache, data, system, vendor), flashed Pixel Experience and rebooted.
4) Bootloop, I was stuck on the Google loading animation for over 20 minutes, nothing happened.
5) I panicked.
6) I tried to flash TWRP 3.3.1.1 via ABD but my PC didn't recognize my phone - probably because, for lack of successful boots, I have not managed to turn on USB debug.
7) I tried to connect to Mi Assistant through stock recovery. It didn't recognize my phone, probably for the above reason.
8) I did a data wipe through stock recovery and rebooted, hoping for whatever issue kept PE from booting normally to get resolved.
9) I'm stuck on the same Google loading animation for over 40 minutes now, no progress.
Does any of you guys see a way out, or is this story over? To recap, I have: 1) PE Plus in bootloop, no access to dev settings, 2) stock MIUI recovery with options to reboot, wipe data or connect to Mi Assistant, 3) stock fastboot, 4) a backup of my previous system on internal storage, 5) ADB on my computer that doesn't recognize my phone - no USB debugging. I don't know where to turn. I don't care much about data, I have everything in the cloud, but I'd like to save the phone if possible.
Thanks a lot.
Click to expand...
Click to collapse
I'm new to this phone as well (but not to Android). Try the following:
Download TWRP from here -> https://androidfilehost.com/?fid=6006931924117884758
Download Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip from here -> https://zackptg5.com/downloads/Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip
Power off phone. Hold down volume down and power button to boot into fastboot
Give the command fastboot flash recovery twrp-3.3.1-1-whyred.img to flash the recovery you downloaded earlier.
Boot into recovery
Flash Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip that you downloaded earlier
The above steps will at least ensure that you retain TWRP and it doesn't get overwritten by stock MIUI recovery
After that, check whether or not your phone/ROM has anti-rollback enabled and take appropriate steps accordingly.

Ok so i flashed PE 10 plus today and was met with the same problem.
Heres how i solved it
Goto fastboot option by pressing volume down and power button
Connect to pc (If it doesnt recognize, reinstall Adb drivers and phone drivers)
If it asks for decryption password just press cancel
Wipe data/internal/vendor (wont be able to wipe dalvik as it wont mount)
Flash PE 10 Plus and nothing else.
It should boot just fine.
However i run into bootloop if i flash latest magisk so i cant root my phone :/
Hope this helps

mkohan said:
Edit: Problem resolved - even though the connected device didn't show up in ADB on PC (adb devices came back empty), the phone was still responsive to fastboot reboot and fastboot flash recovery via PC, so I could flash TWRP 3.3.1.1 & clean flash PE. For anyone struggling with PE bootloops: make sure to 1) use TWRP 3.3.1.1 to flash, 2) do a dalvik/cache wipe after flashing the ROM and 3) not to install the TWRP app before the first successful boot - it was neglecting either 2) or 3) that caused my bootloop. The ROM itself is amazing!
Click to expand...
Click to collapse
hey read your post
actually adb and fastboot are two different things.
and recovery is flashed using fastboot commands not adb.
sometimes if a rom is not booting it may have issues with encryption.