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.
Related
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.
Alright, hello everyone,
I'm having a pretty weird issue here. I've flashed my DUK-L09 and the C432B183 EU Firmware, everything was running fine.
I couldn't make a backup of the /data/ partition though, someone told me to wipe the data to decrypt it, but nothing came good after this.
So I tried to flash back the old recovery image by extracting it, flashing it via fastboot, as I would normally do; enter the factory reset, run it.
Everything is good, it goes up to 100% pretty fast, less than 2 minutes. I then enter the setup wizard the NFC is acting weird. It keeps activating
and deactivating illogically. So, ignoring this issue, I kept up configuring the phone then once I'm logged in Google and sync'd, pops a Huawei ID
logging page really really fast then goes back to the EMUI menu at the beginning of the Setup, in an infinite loop.
Useful information to let you help me better:
- Many firmwares. Currently trying to flash back to B120a and NoCheck from OldDroid and Morph. (Edit: Didn't work)
- Phone unlocked, TWRP accessible.
- Getting a weird "Error 9" when trying to run Update.zip from TWRP.
- Sideload working, but not transferring anything.
- Cannot find any B182 or B130 stock firmware. Everything seems to be gone from Huawei's servers.
- The loading logo isn't Honor anymore but Android, for a reason I can't yet understand.
- Restoring a clean backup (without /data/, since I couldn't back it up) did not fix the problem.
- Trying to update with the 3 buttons do not work, even with the right firmware (C432B183) (Software install failed)
- Factory reset works with the right ROM, but gets me to the setup loop issue.
- The loop occurs when I am supposed to see the Huawei ID setup page. If I do not put any SIM card, or WiFi
I am prompted to choose which way to restore data; if I skip this step, it blinks and doesn't do anything.
- I tried to restore via WiFi (Google's cloud stored data from my account), but it does the same thing as mentioned
earlier. It blinks multiple times rapidly the "Huawei ID" setup page then goes back to the first Setup screen w/o
me being able to do anything about that.
I'll be glad if you knew the answer to this, because I'm all lost right now.
Greetings, Kameyuu.
UP !
After many tries and a LOT of hard work, and spent an entire night (was about to spend the second night on this), I found the culprit and now I know what the issue is, it sounds completely legitimate.
So here are the reason and the solution to this issue:
Actually, my CUST was somehow broken. I never flashed it back because no one told me to flash the CUST.img back. They told me to flash BOOT, SYSTEM, and RECOVERY only.
So, after I downloaded a software called HUAWEI Multi-Tool (From hwmt.ru) I noticed they were also asking for the CUST.img and USERDATA.img (<- this one was apparently optional)
So, trying my luck I flashed it. Did a factory reset, and all, it acted weird and failed, then I tried again and it succeeded. So, with all my hope I booted the phone to the system, started configuring... And it worked !
I was able to set up the phone. For a -yet- unknown reason, some apps look missing and the NFC is still blinking on and off repeatedly and randomly, but I'm investigating that.
If you have any question on the precise steps feel free to send me a PM or ask in the thread directly I'll be glad to sort your issue out.
[EDIT]
Sorry, double post I don't know why my message was posted twice. Feel free to delete this message @moderators
Hello Guys
My friend ask me for get a Lineage OS to his H815 with Nougat. I agreed as I made few successful changes from stock to Lineage OS with Samsungs and older LGs (like L3 E400). But G4 is really more complicated, more than I expected . Firstly I wanted to unlock this phone with FWUL, so I download a VirtualBox emulated image with FWUL and after it boots I opened SALT program and it detects the phone. I made a basic backup and then I choosed Unlock G4 (UsU). After that some windows pop up. Last window was a pre-checking, when the bar gets to the end window closed and nothing more was happening. So after almost hour of waiting I just turned off the phone - I thought its all. After that while phone is booting I have those messages in the left top corner:
[820]-----------------------
[870]
[920] Secure boot error!
[970] Error code : 1009
[1020[ OFFICIAL !!
[1070]
[1120]-----------------------
Its booting, but only sometimes its normal boot, most starts are with bootloop, sometimes its start after 10 restarts, sometimes after 2nd restart, sometimes after plug in/plug out USB cable it starts boot normally (connecting cable only to phone, not to PC), sometimes only thing that helps is to take out the battery. I made full wipe to be sure that its not a software problem, but only thing I achived with that is fact that phone has a Nougat and now it have a Marshmallow. It is (was?) H815, but now model name is LGLS991 (?), it gets very long until it shows software version (V20g), IMEI is unknow, even when I type *#06# I get the null response.
I can get into recovery, can put phone into download mode. But i'm not able to do anything to get LOS or a least Nougat.
I've read many, many tutorials how to get G4 working properly after unsuccessful unlock, but nothing helps. What I've tried:
1. Flashing stock Nougat for H815 with LGUP, installed USB drivers, proper DLL, set com to 41, but when I trying to flash, after a 4% i get error: KDZ file is invalid. Downloaded few KDZ firmwares, dont belive that every single one is invalid, there is something wrong with LGUP or with settings, but I cant find what
2. Flashing with LG Flash Tool 2014: tried both normal flash and cse flash and always stoping in the same moment, with "Connection to server failed. Try again in a moment". Read many tutorials about this error, none was helpful in my case.
3. Flashing with LG Flash Tool v1.8.1.1023 and a TOT file, but after select of dll and tot file and press the yellow arrow I get an error: "Failed PreviousLoad()"
Tried all this methods on second computer but without a luck.
What else can I try to get this G4 working properly? Maybe try to install some rom from stock recovery? But which rom will be ok and dont get things worst?
If you need more info dont hesitate to ask. Would be very greatful for any advices .
you definitely didn't read enough... go to read again the UsU thread and as you've read the whole tutorial, you can also read the whole FAQ and the OP, because 90% of what you pointed out in your publication (which incidentally is in the wrong section) is explained there.
A quick advice: Don't try to flash any KDZ/TOT again.
Greeting you. This device firstly was stuck at "Mi" logo where "Android..." was loading. I left it may be week. Then I could get to fastboot mode. However, now it`s not going out from it. I can't unlock bootloader because it says to me "go so miui settings-> sign in" and etc. I cant even turn this phone on. If I could, I wouldn't even need this things.
So Mi Flash tool either not works. Firstly it says "mismatching device and..". So I've deleted that line from flash_save data_.. - named bat file. It now gave me next error. "erase boot error". So I took and deleted this one too). To see what happens. It gave me next error - which is in next line and all around. What a system! So, any ideas where even I am?
Well you can't flash it with fastboot without bootloader unlocked. You could try to get to edl mode. And then you can it with miflash. But U need authorized account for this. I don't have one but there are some guys that offers help for some payment. But be careful cause they want money first. You will all the necessary files to be download like firmware, miflash... Team viewer installed. He will log on his authorized account and flash it. I've seen a method without 3rd person help. But it requires some payment as well. Just search for flash without authorized account. To get to edl you will have take the back cover off. There are 2 pins to shortcl circuit. You will find the instructions on internet. And I don't know if this will help in your case of course. Maybe motherboard is broken.
I remember that I left it for a long time. Then I was able to hard reset it (may be?). Thank you for response.
Good morning, afternoon or evening depending on where you are reading me from. As the title says, it seems that my LG G8 Verizon has become a paperweight since it remains in a recovery loop. My LG G8 has the bootloader unlocked with Firehose and QFIL (https://forum.xda-developers.com/t/...nlock-and-magisk-root-using-firehose.4221793/), I followed the guide (https://forum.xda-developers.com/t/...wos-12-1-for-lg-g8-alphaplus-alphalm.4354847/) months ago to install the Arrow OS rom and everything worked correctly.
Now the matter in question, days before this week most of my accounts were tried to be violated by a hacker, I don't know where I could have caught the ware but it's done already. Today after several hours in front of the laptop I moved all my accounts, changed passwords and started with one and only gmail and outlook account. To finish everything I decided to factory reset my device, everything seemed to be going well until I saw that it started in the recovery and not in the typical screen after a factory reset. I have little experience in flashing custom roms, the previous times I've flashed everything went as it should and I lived without any problem so right now I don't know what to do.
Every time I enter recovery I get a message on the bottom log saying
"E:failed to clear bcb message: failed to open /dev/block/bootdevice/by-name/misc: no such file in directory".
When I try to make a factory reset from the recovery it says
"Wiping data...
Formatting /data...
E:/system/bin/mke2fs failed with status 1
E:format_volume: Failed to make ext4 on /dev/block/bootdevice/by-name/userdata
Success
Formatting /metadata
E:/system/bin/mke2fs failed with status 1
E:format_volume: Failed to make ext4 on /dev/block/bootdevice/by-name/metadata
Success
Data wipe failed.
E: failed to clear bcb message: failed to open /dev/block/bootdevice/by-name/misc: no such file in directory".
I really don't know what the problem could be, I already tried to use LGUP to try to go back to my original rom but it stops at 4% and the executable closes. Days before, I deactivated the developer options since it was a requirement of the Malwarebytes app and I know that it is partly my fault for not having activated it again. I can go into download mode by pressing volume up but to the best of my knowledge without debugging and oem unlocked I can't do much. [Edit: Reading the firehose and qfil guide hours later I discovered that the Verizon variant doesn't mention as necessary to turn the oem unlock so maybe a little hope?]
If it helps, I still have the backups of sysnand_00.bin, essential.exefs and some others I made before unlocking the bootloader with firehose and qfil, as well as a zip called "Arrow36backup1647621938922" with a .bak named "launcher_backup_main".
Right now I have no way to upload images of the recovery log that is in the advanced settings of the arrow recovery, I will try to do it later but notice that it is quite long.
I sincerely hope that someone has the slightest idea that it could be happening and I will gladly read it and appreciate your time for giving me a hand.
At the end of it all it wasn't that hard to solve my problem, it was just that I was afraid of messing it up even more.
After rereading the guides that I had followed months ago and also the various comments, I came to the conclusion that LGUP could solve it, only that I had done it wrong before. It was thanks to this thread that I was able to download a better version of the tool (https://forum.xda-developers.com/t/lgup-1-16-3-patched-found-and-works-with-lg-wing.4357211/) and after following the instructions everything was like new on my device.
If someone else is going through the same problem as me, you can write to me and I will help you with what worked for me.