Develop Bugs

Semi-bricked One X

Hy guys,
I have a international rooted One X. I decided to switch to a non sense ROM so I flashed Cyanogen 10 on it and now I'm having major problems...after I flashed it, I was stuck in a boot loop - the phone was constantly restarting at the Cyanogen logo. I went to Hboot, and tried to go into recovery to flash something else, but when I clicked recovery, the phone restarted and Cyanogen was working This is the only way to enter Cyanogen now, as a normal reboot or shut down will just get me into the boot loop and I cannot enter recovery at all...also, the phone is not charging when its turned on/cyanogen running...only charges when its shut down...I have no ideea what the hell happened...fastboot is not really woking either, most of the time its just stuck at "waiting for phone" part.
Please help me

did you erroneously flash the boot.img to the recovery partition? that would be the only thing that would cause that i'd think..
i would retry the following.
fastboot flash recovery clockworkmod-5.8.4.0.img
fastboot flash boot boot.img
fastboot erase cache
with boot.img being the kernel provided with your cm10 rom and clockworkmod-5.8.4.0.img being the name of your CWM recovery image.
as for fastboot working intermittently I would check to make sure the cable is snugly plugged into the computer and try another cable if possible.

Vorphs said:
Hy guys,
I have a international rooted One X. I decided to switch to a non sense ROM so I flashed Cyanogen 10 on it and now I'm having major problems...after I flashed it, I was stuck in a boot loop - the phone was constantly restarting at the Cyanogen logo. I went to Hboot, and tried to go into recovery to flash something else, but when I clicked recovery, the phone restarted and Cyanogen was working This is the only way to enter Cyanogen now, as a normal reboot or shut down will just get me into the boot loop and I cannot enter recovery at all...also, the phone is not charging when its turned on/cyanogen running...only charges when its shut down...I have no ideea what the hell happened...fastboot is not really woking either, most of the time its just stuck at "waiting for phone" part.
Please help me
Click to expand...
Click to collapse
I have just overcome a similar problem myself.
Start over, and do factory reset (after nandroid). Then flash the latest clockwork recovery to your phone (CWR 5.8.4.0) using
"fastboot flash recovery <filename.zip>" in the command line
then, boot into recovery, insert usb cable and choose mount usb. simply drop CM rom zip file onto your phone form the PC.
then unmount, go back to recovery menu and select install zip from sd card, then choose your zip file. after this, select reboot system from recovery. it should work fine.
I think you may have acidentally installed the CM10 rom as recovery using the wrong syntax in fastboot.
Hope that helps

Thx for the reply's, unfortunately whenever i try to flash something using fastboot, i get "error: cannot load imagename.img". Only the erase cache command works...

Fixed it using fastbootflasher!

LS990 TWRP Recovery Loop

So everything has been fine up until my device started hemoraging storage randomly, So i thought I would just reboot into recovery and wipe everything and just restart with CM13. I attempted to reboot into TWRP 3.0.2.0 and TWRP just looped over and over. I can still boot into the OS, DD'ing /dev/zero and then the recovery image doesn't seem to fix this issue though. and since we don't have fastboot mode I can't just boot the recovery image manually. Anyone have any solutions other than using ODIN since I use Linux on all my computers?

Loop when booting into TWRP

I'm having problems booting into recovery with twrp installed. When I try, TWRP gets as far as showing it's splash screen, but then restarts, repeatedly re-showing the splash screen every 2-3 seconds. I can access the phone with adb while this happens, and I can therefore easily reboot to bootloader or system. Just cannot get into twrp recovery mode.
Using
Code:
adb reboot bootloader
fastboot boot recovery.img
to boot temporarily into TWRP works like a charm. It's the permanent installation of the image that fails.
The TWRP image I'm using is the unofficial version 3.3 from this URL: https:// unofficialtwrp.com/twrp-3-3-root-moto-g7-play/ (sorry about the spaces in the formatting ... as new user I'm not allowed to insert outside-links)
My phone model is XT1952-1
Any suggestions are appreciated.

[SOLVED]Boot loop after flashing bad image with fastboot / No fastboot/adb/recovery

Hi guys,
I tried to flash TWRP on my Wiko Lenny 4 earlier.
I used adb and fastboot to flash it, however the touchscreen wouldn't work and I was stuck at the "swipe to allow kernel modifications" screen in TWRP. No problem, I reboot in recovery mode, and switched to fastboot mode.
I found another TWRP image and, after flashing with
-> fastboot flash recovery twrp.img
I typed another command,
- >fastboot boot twrp.img.
Since then I am stuck at the Wiko boot screen, saying:
Orange State
Your device has been unlocked and can't be trusted (initially I unlocked OEM)
Your device will boot in 5 seconds
Whatever combination of power+vol up/down I try to use, it only reboots to this screen.
adb won't reconize any device, as well as fastboot. And both are up-to-date.
Perhaps there exists a recovery image that I can put on my sd card, and hopefully it will automatically boot on the sd card as I don't have any control right now.
If someone has an idea, please tell me.
thanks
[EDIT] Solved
Using this link https://aiomobilestuff.com/how-to-unbrick-wiko-stock-firmware-via-wiko-official-site/
I was able to download Wiko's recovery tool from https://customer-world.wikomobile.com/
After unzipping and starting the software, it automatically installed drivers (I guess, if it does not, mediatek usb wiko drivers can be used instead) and downloaded the software into the phone which works now.

Device State: Error! (stuck in Fast boot mode after Android 11 update)

Hi All
Apologies if this already has a thread, noob here.
Okay so I updated to Android 11 about 45 mins ago, Phone restarted seemingly fine and asked for my pin number so I typed it in...
Wrong Pin (definitely typed the right pin)
Okay so I've has this issues before post updating but I couldn't remember how I fixed it so I jumped on Google and searched for a fix. Someone suggested restarting in safe mode. Okay so I hold the power button then hold on restart until it asked me if I want to restart in safe mode. Yes please. Fastboot starts, I get the options to start but everything I select loops me back to fastboot mode along with the following worrying messages:
NOS Production: Error
Device State: Error!
Enter Reason : failed to load/verify boot images
I've seen in another thread the suggestion to leave the battery to drain overnight then to try booting . Can anyone confirm if this is the only solution or if there is alternative option?
Thanks

If I were you, I would download the full factory image for android 11 and do an install from fastboot. It seems the boot partition is corrupted.
Remember to remove the "-w" flag from flash-all.sh so your data is not deleted. Let me know if it works. The fact that you can access fastboot is a good sign!

Push
I got same issue, any solution?!

i have this problem too when i update to android 11 via OTA or flash stock image from fastboot ,
always get back to fastboot with "error setup KM" or "failed or load/verify boot images"
the solution for me is to flash android 10 image via fastboot, so i can't update to android 11

miku1024 said:
i have this problem too when i update to android 11 via OTA or flash stock image from fastboot ,
always get back to fastboot with "error setup KM" or "failed or load/verify boot images"
the solution for me is to flash android 10 image via fastboot, so i can't update to android 11
Click to expand...
Click to collapse
Did you ever figure this out? android 11 seems to have messed up my boot_a and boot_b, boot b seems to work fine I can enter recovery on it, but I can't switch to boot a it says directory not found or something, and when booting up I get fastboot mode: error boot prepare on boot a. how do I just completely reset everything and start clean? or do I gotta go back to android 10?

paradoxiumwind said:
Did you ever figure this out? android 11 seems to have messed up my boot_a and boot_b, boot b seems to work fine I can enter recovery on it, but I can't switch to boot a it says directory not found or something, and when booting up I get fastboot mode: error boot prepare on boot a. how do I just completely reset everything and start clean? or do I gotta go back to android 10?
Click to expand...
Click to collapse
I think this related to emmc defect, because when i ask vendor to replace with new unit the problem gone, there's nothing you can do instead go back to android 10 or try flash android 12 beta and see it can boot

nikhilnangia said:
If I were you, I would download the full factory image for android 11 and do an install from fastboot. It seems the boot partition is corrupted.
Remember to remove the "-w" flag from flash-all.sh so your data is not deleted. Let me know if it works. The fact that you can access fastboot is a good sign!
Click to expand...
Click to collapse
quoting from your answer , is it true that removing -w in the command will not delete existing data?