Develop Bugs

[Q] Boot loader after every phone start, can´t run phone

Hi, I have a problem with my defy and I really short to deal with that. First my defy stopped on red M logo and done proceed to system start. So I go to service menu, set clear cache- cache were cleared for 30mins so I take out batery, then I set - format/factory reset. same problem, it goes without end so after batery goes off, I make McGiver style for bring pnone to life and go to boot loader, run firmware flash over RSD lite and wait......after that RSD give me this message - Phone [0000] Error verifiing code group 33 Checksums. File:0x8BAC,Phone:0x4805 . RSD do nothing, on phone were instaling. after our when I suppose this is and I take out batery from phone and try run it. Every time start boot loader with message :
Code Corrupt
Battery OK
OK to Program
Conect USB
Data Cable
I cant launch android recovery, and If i flashed firmware again a have the same and. Can you please somebody help me with that??
Thanks,
ps. sorry for my english I think is not perfect

new thing, new error mesage from RSD. he pass Checksums errors, than give me message - restarting device ( that is not happend, device were still on), afted while there is new message : Failed flashing proces. Failed plashing proces. phone [0000] Error geting subscriber unit checksum. Device API error: 0xe003003F Command : (RQRCS 0xe403203f); phone conected
result FAIL
I am really desperate.. anyone have experience with this??
Thanks for any advice.
NoDi

As I see probably nobody had this issue like I had. Tomorrow I try bring phone to seller (Vodafone), and than I have to pray for reflashing it from them. Anywhere I will post result from them after I get some, If somebody have the same problem in future like I had.
NoDi

Difrent SFB
try usuing difrent sfb f.
have similar problem at some time...
just try using another sfb and do factory reset each time

yea.. some sbf have higher or lower on img version which might prevent your phone from fully flashed.

I tried various different FW from here. Everytime the same results. Today I was bring phone to Vodafone, I wonder on verdict

you said you tried all firmware versions, can you try diffrent RSD Lite version, may be RSD lite having problem. I am using " RSD Lite 4.9.msi ".

so phone is back. In report from service were Changed bad SWAP module. In used parts were 1pcs of RF board. Anyway I brought phone back to Vodafone because he cant sign in other than 3G network, and many places in our country are sill only 2G.

Nexus 6 with Android N stops booting after entering start pin - bricked?

Scenario:
- I have a Nexus 6 (shamu) with Android preview: the version of the OTA is NPD90G. (Android beta)
- Yesterday it crashed right after it lost radio signal (this used to be a common problem for me but when it crashed it came back again fine for me)
- Now when it boots it asked for my personal pin, then the animation makes its first round and at the end of the second round it stops and it reboots.
-- This is what it looks like for a moment: www andreaundstefanhoehn de / nexusboothang.jpg (cannot post urls at the moment)
-- Removing the simcard has no effect
-- I wiped the cache partion
- Of course I do not have a backup of my data
- Of course the device is locked
- The last message in the log_kmsg is "SELinux: initialized...
What I did:
- I tried the famous "Fix Dead Android in Recovery Mode" but it doesn't help
- After many tries I understood I can update my device with "adb sideload"
-- after searching around a lot I even found the firmware NPD90G and I was successfully to reinstall the firmware.
-- For those who are desperately looking for that version as it seems not to be listed anywhere, here is the still working link: storage.googleapis.com /androiddevelopers/shareables/preview/ota/ shamu-ota-npd90g-06f5d23d.zip (cannot post urls at the moment)
-- Unfortunately even after reinstalling the firmware, it still stops at the same point
-- I tried to unlock the device with "fastboot oem unlock" but it tells me to check "allow oem unlock" in Dev Options which 100% likelyhood is not checked
- Run graphics test results quickly "error", then in a dead android image, then saying "erasing" and then saying "installing system update" but it doesn't fix the problem
Questions
- Does anyone know what the actual issue is that the device stops?
- Is there any newer OTA for shamu I could use? Is there maybe a final Android N for shamu somewhere available?
- Given the above situation, is there any chance I can access files on my device?
- Any other option I have, except factory reset (and wiping my data)?
I really put a lot of effort in it (and learned a lot) but I only got that far. I wished there are other options?
Thanks in advance for helping,
Stefan

I "reposted" the question to the forum here. Not sure how to move delete it in the the other forum. Sorry.

Mod Edit
Duplicate post
Thread Closed.
jackeagle
Forum Moderator

Soft Bricked - Unable to Sideload OTA

Hi all,
My Nexus 5x (16gb - all stock.) went and soft bricked today. Not sure why - just seemed to start wanting to constantly restart - never making it past the white google text part of the boot process. Not sure if it's an update or hardware. No trauma or dropping of the phone - which makes me think s/w rather than h/w.
I have attempted to install a rescue OTA update (instructions I followed are from technobill - don't have enough posts to add a link). However, when running "adb sideload <file>" I get a "failed to read command" error. Have tired multiple cables/ports however to no avail.
(Recovery screen shows the following build details: 7.0/NBD90W/3239497)
Any ideas?
Thanks.
Somewhat Irked

SomewhatIrked said:
Hi all,
My Nexus 5x (16gb - all stock.) went and soft bricked today. Not sure why - just seemed to start wanting to constantly restart - never making it past the white google text part of the boot process. Not sure if it's an update or hardware. No trauma or dropping of the phone - which makes me think s/w rather than h/w.
I have attempted to install a rescue OTA update (instructions I followed are from technobill - don't have enough posts to add a link). However, when running "adb sideload <file>" I get a "failed to read command" error. Have tired multiple cables/ports however to no avail.
(Recovery screen shows the following build details: 7.0/NBD90W/3239497)
Any ideas?
Thanks.
Somewhat Irked
Click to expand...
Click to collapse
Did your phone just reboot in the middle of doing something innocuous then start bootlooping? Were/Are you on total stock with bootloader locked? If both yes, it is probably hardware issue you are encountering.
Regarding sideloading, did you place your Android recovery in sideload mode?
Did you verify adb can "see" your device using "adb devices"?

SomewhatIrked said:
Hi all,
My Nexus 5x (16gb - all stock.) went and soft bricked today. Not sure why - just seemed to start wanting to constantly restart - never making it past the white google text part of the boot process. Not sure if it's an update or hardware. No trauma or dropping of the phone - which makes me think s/w rather than h/w.
I have attempted to install a rescue OTA update (instructions I followed are from technobill - don't have enough posts to add a link). However, when running "adb sideload <file>" I get a "failed to read command" error. Have tired multiple cables/ports however to no avail.
(Recovery screen shows the following build details: 7.0/NBD90W/3239497)
Any ideas?
Thanks.
Somewhat Irked
Click to expand...
Click to collapse
Well luckily I made this post today.

The more this goes on, the more I believe it to be hardware ...
@sfhub - reasonably innocuous. Had just opened one or 2 apps that morning. Not sure what had updated overnight app/os wise. Not anything interesting as far as I can tell. Once I managed to get it into recovery "adb devices" was returning the phone.
@bardhi92 - I saw that once I got in. However, I couldn't get it to see my phone.
Updated things I have tried and why I've all but thrown in the towel:
After the OTA rescue sideload failed I started trying a few different things. It stopped taking me into recovery mode more frequently, at least it seemed that way - it would just keep bootlooping. My main issue is that I has a locked bootloader, which stopped me whacking TWRP on and loading on a custom rom - just to see if that worked.
I thought it might let me sideload on a factory default img file. Turns out nope.
However I used NRT to "Flash Stock + Unroot" (with "Soft Brick/Bootloop" checked) which for some reason, then allowed me to get back into recovery mode. I had also removed the sim card/tray at this point. May have been either or neither of those that allowed me to get into recovery mode. Can't say for certain.
I cleared /cache and /data and then attempted the OTA rescue update again. This time it failed at 45% (according to my cmd prmpt) with the error: "* failed to read command: No error". I'm not sure text was on the phone at the time. But it did manage to boot into Android. I quickly stepped through the various intro steps (putting in the sim, adding my mail google account details).
I went to get a beer. Only to find it boot looping again.
Not to be deterred, I vowed to try again. Same steps as before (remove sim, nrt voodoo). This time however the OTA rescue worked and fully completed. I went through the intro steps again. This time I quickly turned on dev options, enabled usb debugging and sorted out the OEM bootloader. I thought this would be smart, just in case it hapened again. Once I chose to unlock ("fastboot reboot", selected yes), it decided to start boot looping again.
The main annoyance is: I don't think I have any proof of purchase, even though it's in warranty. That, and I now live in Dubai - so shipping back to the UK where I brought it is going to be killer. But I think it's the path of least resistance at the moment.

SomewhatIrked said:
The more this goes on, the more I believe it to be hardware ...
@sfhub - reasonably innocuous. Had just opened one or 2 apps that morning. Not sure what had updated overnight app/os wise. Not anything interesting as far as I can tell. Once I managed to get it into recovery "adb devices" was returning the phone.
@bardhi92 - I saw that once I got in. However, I couldn't get it to see my phone.
Updated things I have tried and why I've all but thrown in the towel:
After the OTA rescue sideload failed I started trying a few different things. It stopped taking me into recovery mode more frequently, at least it seemed that way - it would just keep bootlooping. My main issue is that I has a locked bootloader, which stopped me whacking TWRP on and loading on a custom rom - just to see if that worked.
I thought it might let me sideload on a factory default img file. Turns out nope.
However I used NRT to "Flash Stock + Unroot" (with "Soft Brick/Bootloop" checked) which for some reason, then allowed me to get back into recovery mode. I had also removed the sim card/tray at this point. May have been either or neither of those that allowed me to get into recovery mode. Can't say for certain.
I cleared /cache and /data and then attempted the OTA rescue update again. This time it failed at 45% (according to my cmd prmpt) with the error: "* failed to read command: No error". I'm not sure text was on the phone at the time. But it did manage to boot into Android. I quickly stepped through the various intro steps (putting in the sim, adding my mail google account details).
I went to get a beer. Only to find it boot looping again.
Not to be deterred, I vowed to try again. Same steps as before (remove sim, nrt voodoo). This time however the OTA rescue worked and fully completed. I went through the intro steps again. This time I quickly turned on dev options, enabled usb debugging and sorted out the OEM bootloader. I thought this would be smart, just in case it hapened again. Once I chose to unlock ("fastboot reboot", selected yes), it decided to start boot looping again.
The main annoyance is: I don't think I have any proof of purchase, even though it's in warranty. That, and I now live in Dubai - so shipping back to the UK where I brought it is going to be killer. But I think it's the path of least resistance at the moment.
Click to expand...
Click to collapse
So, you flashed the .TOT file, sideloaded the given OTA within the stock recovery bootloader that comes with the .TOT file, and cleared cache/factory reset?
Please condense it. If you managed to start up the phone, that's a huge success for people who have not been able to yet.

bardhi92 said:
So, you flashed the .TOT file, sideloaded the given OTA within the stock recovery bootloader that comes with the .TOT file, and cleared cache/factory reset?
Please condense it. If you managed to start up the phone, that's a huge success for people who have not been able to yet.
Click to expand...
Click to collapse
In short:
OTA rescue failed during adb sideload,
Tried bullhead-nbd90w-factory-d2f11c5f.zip & removed sim tray - seemed to allow access to recovery mode,
OTA rescue claims to have failed at 47% during adb sideload- still booted into android. However briefly. Went back to bootloop,
Tried bullhead-nbd90w-factory-d2f11c5f.zip & removed sim tray - seemed to allow access to recovery mode,
OTA rescue completed via adb sideload,
Turned on dev options (usb debug, oem unlock),
Booted to fastboot - unlocked bootloader. Now back to bootlooping
@bardhi92 - I could not get the LG utility to detect my phone. Will attempt again tomorrow.

SomewhatIrked said:
@bardhi92 - I could not get the LG utility to detect my phone. Will attempt again tomorrow.
Click to expand...
Click to collapse
IMO you shouldn't flash the TOT file. If you end up bootlooping again, your phone will be stuck in bootloader locked mode with no ability to unlock it.
If you were able to get your phone to boot into android once, there is really nothing the TOT file will do for you that you can't do from TWRP or bootloader, whereas once it locks your bootloader, there are problems you can no longer fix like EFS corruption (which likely isn't your problem).
In the end, you probably do have eMMC that is slowly starting to fail. There is usually error correction on the eMMC that can lock out bad blocks but if it gets to serious, it'll fail. This is why reflashing stuff over and over sometimes works.

Need OTA file for Cheryl-ckh (three carrier version!)

Hello there!
I just bought a Razer Phone from a guy who said that it has a bad motherboard...I bought it pretty cheap and tried to revive it, because why not, i ve done this to other phones.
The phone was somehow reset, it boots until the setup wizard, where i can set the language , emergy call or maginification without problems...
The problem is that if i press " Get Started ", it popps a message like "setup wizard keeps stopping" and so on...i cant pass that screen, the message appears everytime i press "get started" button.
So, i tried flashing... The phone boots like is an unlocked one, but no fastboot/adb ?!
So, the only chance was adb sideload. I pushed different roms / factory images... Nothing.
Hardly, i found an OTA.ZIP file, and tried to sideload it. It worked till 47% ... Then, it said that "PACKAGE IS FOR CHERYL BUT EXPECTED CHERYL-CKH"... not a single rom/factory image worked like this... It loads near 50%, when the other stop right after start.
Later, i discovered i have the US carrier version cheryl-CKH ... And i cant find it's OTA...if one of you can provide me, i ll be very grateful, even buy you a beer or smth.
Thank you ! And please help me...
Edit: i also tried with EDL mode, with Qualcomm Flash Image Loader , but i dont have/know the Programmer Path & Search Path.

I'd advise to unlock the bootloader following the instructions here; make sure to unlock the critical partition as well.
https://developer.razer.com/razer-phone-dev-tools/general-instructions/
Then flash the stock factory image of your choice from here;
https://developer.razer.com/razer-phone-dev-tools/factory-images/
When you unzip these factory images, there is a flash_all.bat file to double click and it should do it all for you.
The phone should be good to go after this. I did this recently on my razer after spending some time flashing some of the 9.0 pie GSI images and it worked great.

[SOLVED] Soft brick (?) on Z1C-based ZPG handheld

SOLVED: I figured out the issue. As mentioned in this thread, downgrading to an older version of flashtool successfully got me past the bundle mismatch error, allowing me to flash stock US firmware onto the device. Still not exactly sure why that's the case, but it worked for me.
Hey folks,
Hope you're all doing well! I have a bit of an odd situation. I recently picked up a Z-Pocket Game, a handheld built using the internals from a torn down Z1 Compact.
A few days ago, I decided to see if I could poke around and install a custom ROM onto the device, given how many are available for the source hardware (Z1C). The device already came pre-installed with XZDualRecovery and was running a custom ROM in Chinese built off Lollipop.
I'm a novice when it comes to flashing and custom ROMs, so I tried to learn more about the process before getting started. Evidently, however, I'm in over my head - fully my responsibility, of course, but over my head nonetheless.
Long story short, I tried to install Lineage OS 17.1 onto the device via the version of TWRP already installed on the device. As per the installation instructions detailed here, I did an advanced wipe before attempting the install, selecting "Dalvik," "System," "Cache," and "Data." When I actually attempted the process, however, it errored out almost immediately, leaving me with a wiped system and no ROM (TWRP warned me about this prior to rebooting).
When I now power on the device, it's stuck on the "Sony - XPERIA" screen, and the LEDs don't light up at all. I can't seem to access TWRP or Philz on the device with the normal key presses. I can force the device off by holding Power and Volume Up, and it also seems able to enter fastboot mode (with a solid blue LED) and flash mode (the LED flashes green, then turns off). I've tried a number of different things to try and fix it, but all of them haven't worked in one way or another. Providing a brief overview to the best of my recollection here, but happy to try again and give more detail if needed:
Using fastboot via the command line to flash a new recovery onto the device gives me an error indicating I can't write the file to the device, and things just end there.
Trying to flash a stock US ROM to the device via flashtool gives me an error indicating the device does not match the bundle, and things just end there.
Trying to restore the device using Xperia Companion first gives an error requesting permission to access the device, then when I select "My Device Cannot Be Detected or Started" and follow the instructions, it tells me that "an error occurred while repairing this device," and provides this small blurb of device info:
UEGetPhoneInfoMissingInfo
Z-POCKET GAME 3579 1279-6978 R2D 14.6.A.1.236
2.11.6.0 / Windows 10 64 bit / Win32 / US / /
So I'm a bit stumped. It seems as though enough of the device is working to get everything back into a workable state, but I'm not sure of how to go about that. Any thoughts or leads would be greatly appreciated!

edit_duplicate said:
SOLVED: I figured out the issue. As mentioned in this thread, downgrading to an older version of flashtool successfully got me past the bundle mismatch error, allowing me to flash stock US firmware onto the device. Still not exactly sure why that's the case, but it worked for me.
Hey folks,
Hope you're all doing well! I have a bit of an odd situation. I recently picked up a Z-Pocket Game, a handheld built using the internals from a torn down Z1 Compact.
A few days ago, I decided to see if I could poke around and install a custom ROM onto the device, given how many are available for the source hardware (Z1C). The device already came pre-installed with XZDualRecovery and was running a custom ROM in Chinese built off Lollipop.
I'm a novice when it comes to flashing and custom ROMs, so I tried to learn more about the process before getting started. Evidently, however, I'm in over my head - fully my responsibility, of course, but over my head nonetheless.
Long story short, I tried to install Lineage OS 17.1 onto the device via the version of TWRP already installed on the device. As per the installation instructions detailed here, I did an advanced wipe before attempting the install, selecting "Dalvik," "System," "Cache," and "Data." When I actually attempted the process, however, it errored out almost immediately, leaving me with a wiped system and no ROM (TWRP warned me about this prior to rebooting).
When I now power on the device, it's stuck on the "Sony - XPERIA" screen, and the LEDs don't light up at all. I can't seem to access TWRP or Philz on the device with the normal key presses. I can force the device off by holding Power and Volume Up, and it also seems able to enter fastboot mode (with a solid blue LED) and flash mode (the LED flashes green, then turns off). I've tried a number of different things to try and fix it, but all of them haven't worked in one way or another. Providing a brief overview to the best of my recollection here, but happy to try again and give more detail if needed:
Using fastboot via the command line to flash a new recovery onto the device gives me an error indicating I can't write the file to the device, and things just end there.
Trying to flash a stock US ROM to the device via flashtool gives me an error indicating the device does not match the bundle, and things just end there.
Trying to restore the device using Xperia Companion first gives an error requesting permission to access the device, then when I select "My Device Cannot Be Detected or Started" and follow the instructions, it tells me that "an error occurred while repairing this device," and provides this small blurb of device info:
UEGetPhoneInfoMissingInfo
Z-POCKET GAME 3579 1279-6978 R2D 14.6.A.1.236
2.11.6.0 / Windows 10 64 bit / Win32 / US / /
So I'm a bit stumped. It seems as though enough of the device is working to get everything back into a workable state, but I'm not sure of how to go about that. Any thoughts or leads would be greatly appreciated!
Click to expand...
Click to collapse
Glad that you find out yourself.
And thanks for sharing!