I've been getting help on this over at Hovatek, but it's extremely slow going; I first posted there on December 11 and it's still not resolved. This phone is a former Lifeline phone, and I've been trying to get it rooted so that I can use the Tello SIM I obtained. The problem the phone was having is that it refused to do any updates, so Tello's troubleshooting as to why it wasn't detecting the SIM was completely halted.
I did finally get to the point of rooting it. The major problem I have now is that it will only boot to fastboot mode. I can get it into recovery mode, but I get the dead android with "no connection" under it, and I've tried everything the internet has suggested to get past that, and it won't. Additionally, any fastboot command (apart from "fastboot devices") I try in ADB returns "FAILED (remote: 'unknown command'). I don't know how to get it into EDL mode from fastboot. I've tried every button combo possible, and the only one that does anything different is power + volume up, which changes it to a bright white screen. At this point I just want to do a hard reset so I can take another go at the rooting process, but the phone doesn't seem to want to allow me to. I would appreciate any help with this; I don't have a working phone at the moment because of these issues.
https://forum.xda-developers.com/t/trouble-rooting-umx-u683cl.4518007
Yes, that's my original post from back in November. That post is no longer my problem, though I will set your response there aside for when I hopefully get the phone to do anything besides fastboot.
it's clearly same topic, you must not open new thread. add your second post to previous one so mods can delete this thread.
It's clearly not. It's the same phone, but a different problem. The old post was seeking help with rooting it (and got no action, you may note), this one is about getting it out of fastboot mode so I can reset the damn thing and try again.
you bricked that device as a result of trouble with rooting. all info belongs to the previous thread, so others can read the history that caused this situation. I am not arguing any further here. answer in other thread and close this one.
somnomania said:
I've been getting help on this over at Hovatek, but it's extremely slow going; I first posted there on December 11 and it's still not resolved. This phone is a former Lifeline phone, and I've been trying to get it rooted so that I can use the Tello SIM I obtained. The problem the phone was having is that it refused to do any updates, so Tello's troubleshooting as to why it wasn't detecting the SIM was completely halted.
I did finally get to the point of rooting it. The major problem I have now is that it will only boot to fastboot mode. I can get it into recovery mode, but I get the dead android with "no connection" under it, and I've tried everything the internet has suggested to get past that, and it won't. Additionally, any fastboot command (apart from "fastboot devices") I try in ADB returns "FAILED (remote: 'unknown command'). I don't know how to get it into EDL mode from fastboot. I've tried every button combo possible, and the only one that does anything different is power + volume up, which changes it to a bright white screen. At this point I just want to do a hard reset so I can take another go at the rooting process, but the phone doesn't seem to want to allow me to. I would appreciate any help with this; I don't have a working phone at the moment because of these issues.
Click to expand...
Click to collapse
Here is the full firmware for the U683CL. Be sure to wipe the userdata and cache because I dumped the firmware from the same phone from a guy for $5 and it still has the guy's data and it contains pretty weird things...
BE SURE TO USE EDL CLIENT!
EDL CLIENT IS ONLY SUPPORTED ON LINUX SO MAKE A VIRTUAL MACHINE!
EDL CLIENT DOES NOT REQUIRE ANY RAWPROGRAM0.XML OR PATCH0.XML FILE!!
Link (I will make sure this link is never taken down and if it is, I'm reuploading the link no matter what): https://www.mediafire.com/file/js8ynkg8uum9ql0/u683cl_february_patch.zip/file
Related
i was trying to root a phone for someone and after odin completed it said it had failed.
the phone is a telus samsung t959d running froyo.
I followed the instructions from (I would post the url for the link but i am not allowed to.)cyanogenmod's wiki, after it failed I rebooted the phone and it got stuck on the screen in the attached pic. I have tried to boot back into download mode to no avail. From the screen it's stuck on I cannot get any tool to register the device as being present, adb, heimdall, zdiag, etc... I even tried fastboot out of desperation.Before I used odin I tried to get the phone to boot into the bootloader but it only ever went to either recovery or a normal boot and I tried every button press combo I could think of and found and nada.
Even running adb reboot bootloader just made the device boot normally. I think that if I could get it to boot to fastboot usb i could then try fastboot. I am new to rooting devices and have successfully rooted my HTC EVO3D and got s-off and simlock removed for any carrier. So I do know how to follow instructions properly, why flashing the recovery.bin failed I don't know and every fix I seem to find says BOOT TO DOWNLOAD MODE. if I could do that I wouldn't be having this problem lol. Anyway can someone please help me figure this out. Thanks. ANd if you need any further info please let me know. I don't want to have to give my friend my phone due to a software issue.
And YES I did pick PDA not anything else.
machv5 said:
i was trying to root a phone for someone and after odin completed it said it had failed.
the phone is a telus samsung t959d running froyo.
I followed the instructions from (I would post the url for the link but i am not allowed to.)cyanogenmod's wiki, after it failed I rebooted the phone and it got stuck on the screen in the attached pic. I have tried to boot back into download mode to no avail. From the screen it's stuck on I cannot get any tool to register the device as being present, adb, heimdall, zdiag, etc... I even tried fastboot out of desperation.Before I used odin I tried to get the phone to boot into the bootloader but it only ever went to either recovery or a normal boot and I tried every button press combo I could think of and found and nada.
Even running adb reboot bootloader just made the device boot normally. I think that if I could get it to boot to fastboot usb i could then try fastboot. I am new to rooting devices and have successfully rooted my HTC EVO3D and got s-off and simlock removed for any carrier. So I do know how to follow instructions properly, why flashing the recovery.bin failed I don't know and every fix I seem to find says BOOT TO DOWNLOAD MODE. if I could do that I wouldn't be having this problem lol. Anyway can someone please help me figure this out. Thanks. ANd if you need any further info please let me know. I don't want to have to give my friend my phone due to a software issue.
And YES I did pick PDA not anything else.
Click to expand...
Click to collapse
I kept reading other threads and sadly I din't pully the battery first before disconnecting the usb and repartition may have been checked as I see that it does the as default for my version. Also i turned off ODIN as I was hoping a reboot of my computer might help. I will keep trying to find an answer till someone gets back to me. this post may not even show up if I can't do a second post if no one has replied first.
Everyone was a nub at one time wasn't it FUN hahahahahaha sob cry
machv5 said:
I kept reading other threads and sadly I din't pully the battery first before disconnecting the usb and repartition may have been checked as I see that it does the as default for my version. Also i turned off ODIN as I was hoping a reboot of my computer might help. I will keep trying to find an answer till someone gets back to me. this post may not even show up if I can't do a second post if no one has replied first.
Everyone was a nub at one time wasn't it FUN hahahahahaha sob cry
Click to expand...
Click to collapse
I tried a jig and that didn't work. There must be some way of getting the device to give up on completing a task i no longer can give it due to ODIN being shut off.
Why is it that the "how to root/unlocks" never have the "if x fails then do these steps etc..." Had the how to had "pull the battery before disconnecting USB and don't reset or shut off ODIN" I wouldn't be in this mess. I realize that it's user beware but a few important steps like that in case of a fail would go a long way to you guys not shaking your heads. Instead of "silly nub hahahahahaha". No offence but I get that a lot and try to remember that when I teach someone how to use a computer. I am new at phones not at everything.
Further Developments Please can someone help?
I was giving someone a new memory card and they had a Samsung SGH-I896 it has an EB575152VA battery and the one I have the T959D has an EB575152VU battery. I exchanged my battery for hers by accident somehow and when I plugged my phone in it didn't go to the phone triangle computer logo screen it booted to recovery and said it couldn't charge the battery and kept rebooting to recovery. I got my battery back and it booted back to the phone triangle computer logo again. Grrrr....
The other thing I saw while the recovery screen was an error message that said
Code:
E:/data/fota not accessible
(may not be 100% accurate I don't have the battery to check right now but can get it again if need be) anyway I now see that there may be some light at the end of the tunnel. i have the correct stock firmware for the device I tried flashing it while in recovery but the phone kept rebooting before anything got done. My question is how can I get the dang phone to stop asking for Odin and go to recovery so I can flash stock firmware and ROM back to it? As I cannot as far as I know give it what it wants because I reset Odin and nothing seems to see that the phone is connected to the computer. I am going to try the other battery on a full charge to see what that does.
I am new at all this and want to get it fixed. I cannot afford to send it off to a service center and besides that I want to do it myself as I want to become a developer and droid technician. I would gladly donate to anyone but am still trying to get Google to accept my pay-as-you-go credit card and I don't have PayPal either. Which is really frustrating when it comes to giving back. I posted a Q&A on how to without PayPal or CC but as of the last time I checked no one has gotten back to me about it.
The CyanogenMod guide is flat out WRONG. I've tried to change it, but anything I do is reverted in an instant. I also tried to use it to install the ROM only, ended up bricking my phone and it took me hours to unbrick. That's how I became acquainted with XDA.
So, to get this straight:
1. you're using the stock USB cable
2. you remove the battery
3. you hold volume down
4. you plug in the usb cable
5. after a few seconds, you release volume down
6. the screen does not display a yellow triangle with an android
Posted from my Galaxy Tab with CM10
MultipleMonomials said:
The CyanogenMod guide is flat out WRONG. I've tried to change it, but anything I do is reverted in an instant. I also tried to use it to install the ROM only, ended up bricking my phone and it took me hours to unbrick. That's how I became acquainted with XDA.
So, to get this straight:
1. you're using the stock USB cable
2. you remove the battery
3. you hold volume down
4. you plug in the usb cable
5. after a few seconds, you release volume down
6. the screen does not display a yellow triangle with an android
Posted from my Galaxy Tab with CM10
Click to expand...
Click to collapse
That is correct. If you think that my idea below is a bad one or if I downloaded the wrong firmware package please let me know and /or you have a fix that will work? ty
I have though come up with an idea that may work. I am going to charge the "wrong" battery in erm the right phone lol and then use it to trick the device into booting into recovery instead of the cellphone triangle computer (CTC, for want of a better acronym) The I896 battery ends in a V not an ? (sorry can't rem don't have it on me) from the I896 model I think it is, plugging it into USB with the power off sends it to recovery with the "battery cannot be charged " message instead of the CTC screen.
I tried it but the charge in the battery was too low and rebooted. I am hoping that with a full charge (as long as I don't power on the phone first as this will make it go to CTC logo again.
I am hoping that I can install the update.zip that I made by first unzipping the T959UVJFD_firmware.tar I downloaded then unpacked and then repacked into an update.zip as I don't think that it will read the package as a tar file and if it's not called update.zip The recovery is still stock. If I get the phone working I am not going to try unlocking and rooting it again. I will just post two separate adverts one as a carrier locked device and the other one (higher of course to cover buying the unlock from Telus) as carrier unlocked and then I will buy the unlock code if the blah blah you get the drift. sorry for rambling on.
oh and I can't rem if I said this or not, In recovery it "E:/data/fota not accessible" I don't know what that means yet I have been busy with other things and haven't looked it up yet.
Since you can get into at least some version of recovery, your bootloader is intact and you should be able to unbrick it. You ought to be able to get into download mode using a download jig. You can get one on ebay for a few bucks or you can make one yourself. There's a guide floating around here somewhere that lets you make one from a microusb cable.
Posted from my Galaxy Tab with CM10
when i open into recovery and go into twmp and i go to reboot>recovery it says no os installed. my recovery is completely gone. what do?
Ok so I was searching, a lot, and found that I can turn the phone back to OEM. unfortunately every guide I have read says it needs to be s-off using firewater. When i do the "adb reboot" function it gets stuck at the htc boot screen and I cannot perform the second step in making the phone s-off. what do I do? Is my phone legitimately bricked? Like hard bricked forever?
I also ran the RUU. It goes through and when it gets to step 1 of 7 it stops and says "unknown error occurred" I go through the error recovery steps and it still does not work. Just trying to keep all the info here so you understand the situation I'm in. It also boots into recovery mode, obviously, with the power button and volume down button.
got it. could go ahead and delete post.
Don't have the thread deleted, but instead explain how you finally solved the problem so others may learn from your experiences...
-Sent from a payphone...
tttomdemaria said:
Ok so I was searching, a lot, and found that I can turn the phone back to OEM. unfortunately every guide I have read says it needs to be s-off using firewater. When i do the "adb reboot" function it gets stuck at the htc boot screen and I cannot perform the second step in making the phone s-off. what do I do? Is my phone legitimately bricked? Like hard bricked forever?
Click to expand...
Click to collapse
I know you've already sorted it out. But first, this phone is not bricked if the screen comes on. Recovering is usually not hard at all, just a matter of knowing how to do it.
Second, were you referring to a warranty claim for a phone being not bootable due to mods that you did? That isn't covered under warranty, and is immoral. Take responsibility for your actions; and don't jump the gun and think you have to get a new phone after just a couple hours of unsuccessful attempts to get the phone running. If you want to root and mod these devices, you are going to have to learn to be patient and work through little quirks like this.
Lastly, the phone needs to be bootable to perform firewater s-off.
Thanks. yea my only two friends that do this kind of **** are like seriously the most pessimistic, negative assholes I have seriously ever met in my life. They kinda just scared me into thinking it was easy to brick a phone and totally mess it up. After some research i just found all I had to do was run an RUU and make sure the phone was relocked.
seriously. they are real negative nancies.
Ok for those of you who may ever be in the situation I was in I will write up how i fixed it. very simple and took probably about 20 minutes start of download of tools to finish. This was done on windows 7 but i'm sure it is pretty similar on windows 8 as well.
In order to do this you will need to know that holding the power button AND the volume up button simultaneously emulate a battery pull and that holding the power button AND the volume down button enter recovery mode. If you are stuck in a boot screen or splash screen like I was you will need to emulate a battery pull and them immediately switch to enter recovery without actually removing your finger from the power button.
Then you need to make sure you have the right tools. you can find them at these locations.
RUU- http://forum.xda-developers.com/showthread.php?t=2757462
ADB- http://www.mediafire.com/download/5s2nfws9wkj9gyq/adb-fastboot.zip
Now you need to make sure your phone is either "***LOCKED*** or ***RELOCKED*** when you enter the recovery mode.
You can do this very easily. Plug your phone into your computer and enter recovery mode. Make sure the phone is in Fastboot USB mode and not Hboot. Open the folder titled "Android" in the adb kit you downloaded from the link above. Shift + right click anywhere on that folder(not on a file) and choose "Open command window here" type in the command window "fastboot oem lock". It will show as "relocked" after you do this and it reboots. This will allow you to run the RUU without any issues. Always make sure the phone is in "Fastboot USB" mode.
Now run the RUU executable and it will automatically pick up your phone assuming all of your drivers are in order. Just hit yes to everything and it will run through what it needs to. If you do not have a progress bar on your phone's screen as well as your computer then you messed up somewhere. start over.
If you try to do this on the At&T htc one (m8) without actually relocking it first the RUU will fail at step 1 of 7.
Good luck.
tttomdemaria said:
Thanks. yea my only two friends that do this kind of **** are like seriously the most pessimistic, negative assholes I have seriously ever met in my life. They kinda just scared me into thinking it was easy to brick a phone and totally mess it up. After some research i just found all I had to do was run an RUU and make sure the phone was relocked.
seriously. they are real negative nancies.
Click to expand...
Click to collapse
Then stay away from those guys! Sounds like they don't really know that much, wrong attitude, and you are probably already on your way to knowing what they know, if not more.
This phone is pretty hard to brick. As long as you aren't flashing hboot or radio, and don't flash anything intended for another device, its pretty difficult to brick this phone by modding it. The condition you were in was not a brick, and not even close. Some call this a "soft brick" but in my opinion, there is no such thing, its either bricked (requires opening the phone to recovery, such as JTAG or replacing motherboard) or its not. What I call it is "something is wrong with the phone and you just need to do the right steps to get running again".
---------- Post added at 11:22 AM ---------- Previous post was at 11:16 AM ----------
tttomdemaria said:
Ok for those of you who may ever be in the situation I was in I will write up how i fixed it. very simple and took probably about 20 minutes start of download of tools to finish.
Click to expand...
Click to collapse
Glad you sorted it out, so nice job.
Although RUU was probably a little overkill. RUU is a useful recovery tool, although a bit of a nuclear option. But good last resort. Since you RUU'ed, you will need to unlock the bootloader again, and flash custom recovery to get back to where you were originally (phone setup for mods) if that is the intention. If the intent was to go back to stock and stay there, RUU is a great way to do that.
You probably could have just gotten back up and running by using adb to wipe cache, re-install custom recovery and flash a ROM.
Hi.
I'm new here so pardon any error...
someone advised me to post this problem here/ tterox
i was trying to unlock the network using a tutorial i found online.
but after editing the "mmcblk0p4" file the phone shuts down and won't come on. i tried plugging it to pc and it shows a "qhusb_dload" driver window. i tried using linux also and it shows it in qdl mode.
I don't know what to do because i''ve tried so many options adb and fastboot can't detect the phone. any useful information will be appreciated.
thanks.
Sorry to say but most every time that a device gets into Qualcomms download mode you have a brick. There are a few times that people have hit this mode momentarily and got out but I suspect that you were playing with a partition that is needed to boot thus cannot boot.
Usually the only thing to do know is JTAG or return to the factory for RMA
Sorry for the bad news
demkantor said:
Sorry to say but most every time that a device gets into Qualcomms download mode you have a brick. There are a few times that people have hit this mode momentarily and got out but I suspect that you were playing with a partition that is needed to boot thus cannot boot.
Usually the only thing to do know is JTAG or return to the factory for RMA
Sorry for the bad news
Click to expand...
Click to collapse
well, i read in a post that it was possible to push firmware to an android device in that mode...i tried it and i was able to view my partitions but i dont know how to reflash the hboot.
Hi hello
So here’s a head scratcher I hope someone can help me with that won’t involve replacing my main board.
Got myself the p20 lite (ANE-LX1 C432) - Single Sim.
I unlocked the bootloader with Huawei just before they stopped handing out the codes. All was good and happy with the world.
Rooted with Magisk and Was busy messing around With Termux, Linux deploy, Mobile Terminal and some pretty basic stuff. I’ve been out of the android scene for a while so was getting reacquainted with the scene.
Anyway. I was messing around in the terminal in a root shell just fixing basic permissions after messing up my termux environment as root. Phone randomly rebooted (I must’ve messed with the wrong folder -no idea which) came back on and my IMEI and baseband were gone.
No worries, I thought. Happened tonnes of times with my previous Devices (looking at you Samsung) just a quick restore or flash and all will be happy again.
Yeah, not quite.
Note that up until this point I hadn’t touched the system partition (probably besides the mobile terminal mishap -no idea)
So over the last week or so I have tried everything. Restore from Twrp backup. Flashed stock through fastboot, through erecovery. Those flashed ok but didn’t fix it.
Putting numerous different update.app FULL & OTA updates in dload folder on SD and internal all failed. Only used my builds version of course and only ones firmware finder deemed compatible/available
Then I got desperate (read: stupid) Decided to take the unpacked firmware files and flash whichever ones twrp would let me. First tried just the modem files. Didn’t help. Then just went through the list and flashed all I could.
I think the kicker came in when I installed the Trustfirmware.img because once I did that I rebooted and now I was stuck in an endless boot loop. No way to get into recovery. Not with their ton combo nor adb/fastboot.
I still had access to fastboot at this point at least and started doing every single thing suggested all over the net just trying to get back to stock.
Tried the unbrick option on The Huawei Multi-Tool. Flashed ok. Phone still wouldn’t boot. Did it a few times with 3 approved versions. Nothing. Only access to fastboot otherwise I was in a boot loop with error mode error no 15 and the verification failure (Attached below)
Last thing I tried after reading online was to relock my boot loader and flash stock. So I locked it with Huawei Multi-Tool. Reboot......
Now I don’t even have access to fastboot. My PC’s (windows and Linux) don’t even acknowledge it and holding volume down in all the weird and wonderful ways and times does nothing. All I get is startup Huawei Logo, Error Mode as per pic Below and then reboot. That’s it.
I’m assuming it’s trying to do a factory reset after relocking the bootloader (if it even locked properly, can’t check) but it can’t get into recovery/erecovery. I dunno ?
That’s my essay of where I’m at. Warranty is already void so not an option and I don’t want to buy a new mainboard (may as well buy a new phone).
So here I am. Is this my life now or does anyone have any magic tricks to possibly suggest?
Pyrolectic13 said:
Hi hello
So here’s a head scratcher I hope someone can help me with that won’t involve replacing my main board.
Got myself the p20 lite (ANE-LX1 C432) - Single Sim.
I unlocked the bootloader with Huawei just before they stopped handing out the codes. All was good and happy with the world.
Rooted with Magisk and Was busy messing around With Termux, Linux deploy, Mobile Terminal and some pretty basic stuff. I’ve been out of the android scene for a while so was getting reacquainted with the scene.
Anyway. I was messing around in the terminal in a root shell just fixing basic permissions after messing up my termux environment as root. Phone randomly rebooted (I must’ve messed with the wrong folder -no idea which) came back on and my IMEI and baseband were gone.
No worries, I thought. Happened tonnes of times with my previous Devices (looking at you Samsung) just a quick restore or flash and all will be happy again.
Yeah, not quite.
Note that up until this point I hadn’t touched the system partition (probably besides the mobile terminal mishap -no idea)
So over the last week or so I have tried everything. Restore from Twrp backup. Flashed stock through fastboot, through erecovery. Those flashed ok but didn’t fix it.
Putting numerous different update.app FULL & OTA updates in dload folder on SD and internal all failed. Only used my builds version of course and only ones firmware finder deemed compatible/available
Then I got desperate (read: stupid) Decided to take the unpacked firmware files and flash whichever ones twrp would let me. First tried just the modem files. Didn’t help. Then just went through the list and flashed all I could.
I think the kicker came in when I installed the Trustfirmware.img because once I did that I rebooted and now I was stuck in an endless boot loop. No way to get into recovery. Not with their ton combo nor adb/fastboot.
I still had access to fastboot at this point at least and started doing every single thing suggested all over the net just trying to get back to stock.
Tried the unbrick option on The Huawei Multi-Tool. Flashed ok. Phone still wouldn’t boot. Did it a few times with 3 approved versions. Nothing. Only access to fastboot otherwise I was in a boot loop with error mode error no 15 and the verification failure (Attached below)
Last thing I tried after reading online was to relock my boot loader and flash stock. So I locked it with Huawei Multi-Tool. Reboot......
Now I don’t even have access to fastboot. My PC’s (windows and Linux) don’t even acknowledge it and holding volume down in all the weird and wonderful ways and times does nothing. All I get is startup Huawei Logo, Error Mode as per pic Below and then reboot. That’s it.
I’m assuming it’s trying to do a factory reset after relocking the bootloader (if it even locked properly, can’t check) but it can’t get into recovery/erecovery. I dunno ?
That’s my essay of where I’m at. Warranty is already void so not an option and I don’t want to buy a new mainboard (may as well buy a new phone).
So here I am. Is this my life now or does anyone have any magic tricks to possibly suggest?
Click to expand...
Click to collapse
Check the second post in this thread:
https://forum.xda-developers.com/honor-7x/help/help-stuck-error-mode-screen-t3735067
kilroystyx said:
Check the second post in this thread:
https://forum.xda-developers.com/honor-7x/help/help-stuck-error-mode-screen-t3735067
Click to expand...
Click to collapse
Thanks for this.
The battery discharged fully about two days ago.
I haven’t tried plugging it in and out as/if it turns on immediately (though even though it shows dead without charger it still comes on immediately).
I’m gonna get a weaker lower amp charger and see if that maybe helps. Fml ?
***UPDATE***
Been at it for hours. Battery is completely flat. But h second I plug it in the the Black Huawei logo comes up ten a few seconds later it’s on the same error screen for a little longer then boot loops like that constantly.
The error isn’t the same as the post in that link though. And I am FRP unlocked.
Eh.
Pyrolectic13 said:
Thanks for this.
The battery discharged fully about two days ago.
I haven’t tried plugging it in and out as/if it turns on immediately (though even though it shows dead without charger it still comes on immediately).
I’m gonna get a weaker lower amp charger and see if that maybe helps. Fml ?
***UPDATE***
Been at it for hours. Battery is completely flat. But h second I plug it in the the Black Huawei logo comes up ten a few seconds later it’s on the same error screen for a little longer then boot loops like that constantly.
The error isn’t the same as the post in that link though. And I am FRP unlocked.
Eh.
Click to expand...
Click to collapse
I guess your previous error was related to ramdisk...
Now what is your current situation?
-What error is showed in the Error mode?
-Can you reach FASTBOOT&RESCUE MODE menu?
-What is your current recovery?
kilroystyx said:
I guess your previous error was related to ramdisk...
Now what is your current situation?
-What error is showed in the Error mode?
-Can you reach FASTBOOT&RESCUE MODE menu?
-What is your current recovery?
Click to expand...
Click to collapse
As it stands I cannot enter fastboot or recovery mode. Update from SD also doesn’t do anything. Battery is completely discharged. And if I leave it on the charger it doesn’t charge, only boot loops.
So with all that the ONLY thing this phone does now is:
- Starts up Showing Huawei logo
- Error Mode Screen with Func No: 15 (bl31 image) & Error No: 1 (security verify failed)
- Reboots
Ths happens whether it’s plugged into the pc’s usb or the charger. Tried all combinations of buttons too.
It has stock recovery as I flashed that back when trying to revert back to stock.
I lost access to fastboot after I locked the bootlaoder again using the Huawei Multi Tool. It’s like it trying to do the factory wipe that it usually would after locking/unlocking the bootloader but is unable to due to the error mode screen.
Sent from my iPhone using Tapatalk
Pyrolectic13 said:
As it stands I cannot enter fastboot or recovery mode. Update from SD also doesn’t do anything. Battery is completely discharged. And if I leave it on the charger it doesn’t charge, only boot loops.
So with all that the ONLY thing this phone does now is:
- Starts up Showing Huawei logo
- Error Mode Screen with Func No: 15 (bl31 image) & Error No: 1 (security verify failed)
- Reboots
Ths happens whether it’s plugged into the pc’s usb or the charger. Tried all combinations of buttons too.
It has stock recovery as I flashed that back when trying to revert back to stock.
I lost access to fastboot after I locked the bootlaoder again using the Huawei Multi Tool. It’s like it trying to do the factory wipe that it usually would after locking/unlocking the bootloader but is unable to due to the error mode screen.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
I see, it is really bad
My last hope is to be able to do a forced Firmware upgrade. Press power button and VOL + and VOL- simultaneously. Do you see the same as the attached image?
kilroystyx said:
I see, it is really bad
My last hope is to be able to do a forced Firmware upgrade. Press power button and VOL + and VOL- simultaneously. Do you see the same as the attached image?
Click to expand...
Click to collapse
Ah man, I wish it would even do that. It makes no attempt to even pretend to see the sd card update. If I hold all the buttons in it still only comes up with the error mode and reboots.
I popped it open and connected a charger up battery to see if that would help but it doesn’t.
Do you maybe know the pin layout on the inside or know where I could get schematics? Been looking everywhere.
I’m almost done building my own Jtag box and am hoping to bring it back to life by writing straight to the damn thing.
Sent from my iPhone using Tapatalk
Pyrolectic13 said:
Ah man, I wish it would even do that. It makes no attempt to even pretend to see the sd card update. If I hold all the buttons in it still only comes up with the error mode and reboots.
I popped it open and connected a charger up battery to see if that would help but it doesn’t.
Do you maybe know the pin layout on the inside or know where I could get schematics? Been looking everywhere.
I’m almost done building my own Jtag box and am hoping to bring it back to life by writing straight to the damn thing.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
That is sad!!!
With JTAG and schematics stuff I cannot help you.
What I found recently and it was new for me (I didn't tested yet) is a possibility to install firmware via "dload" folder, but to start installation the stock recovery have to be full functional.
If I found something interesting for you I'll post here.
kilroystyx said:
That is sad!!!
With JTAG and schematics stuff I cannot help you.
What I found recently and it was new for me (I didn't tested yet) is a possibility to install firmware via "dload" folder, but to start installation the stock recovery have to be full functional.
If I found something interesting for you I'll post here.
Click to expand...
Click to collapse
To my knowledge the recovery is installed. Well erecovery. It was working up until I locked the bootloader again and it went into a boot loop instead of doing the factory reset.
Is there any other way to force sd update other than with the dload folder?
Thanks for tying to help, I appreciate it.
Pyrolectic13 said:
To my knowledge the recovery is installed. Well erecovery. It was working up until I locked the bootloader again and it went into a boot loop instead of doing the factory reset.
Is there any other way to force sd update other than with the dload folder?
Thanks for tying to help, I appreciate it.
Click to expand...
Click to collapse
You can check the official documentation about that.
Please let us know how you solved this problem.
kumarsid7 said:
Please let us know how you solved this problem.
Click to expand...
Click to collapse
Still unsolved as of yet.
I’ve finished building my own version of the Riff/Octoplus box as well as a makeshift Jtag. I’m still trying to find and piece together some firmware files and other board software I think I need.
Also, if anyone has any idea where the test point is on this board I’d really appreciate you pointing it out. I cannot find the schematics or any solid documentation anywhere.
I will attach the pics I have of both sides of the board as soon as I get home.
Sent from my iPhone using Tapatalk
in first picture youle see many circles golden 2 smallest is testpoint good luck
Pyrolectic13 said:
Still unsolved as of yet.
I’ve finished building my own version of the Riff/Octoplus box as well as a makeshift Jtag. I’m still trying to find and piece together some firmware files and other board software I think I need.
Also, if anyone has any idea where the test point is on this board I’d really appreciate you pointing it out. I cannot find the schematics or any solid documentation anywhere.
I will attach the pics I have of both sides of the board as soon as I get home.
View attachment 4579956
View attachment 4579957
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
in first picture youle see many circles golden 2 smallest is testpoint good luck
well, try to restore your device using dload method. It needs you to copy the UPDATE.APP in dload folder of an external sd card(formated in NTFS format) and then just press both vol up+down along with power button for a few seconds. It will auto launch huawei e-recovery and will try to flash the UPDATE.APP you stored in ext sd card. This should definitely work.
Dload method doesn't need you to unlock your device or bootloader.
Maybe?
I know it’s a long shot but I still have this phone. If anyone maybe knows if there’s been a way to fix this as of yet please let me know. ?
Lol. Still got this damn thing. Been searching around and seen a few people reporting similar errors. Never find out if they ever solve it though.
So. Anyone maybe have any knowledge to share? Anything at all.
I don't know if you still have your device, but I had the exact same issue with a P10 (VTR-L09)
I was able to fix fastboot using https://github.com/mashed-potatoes/PotatoNV
That tool was designed to unlock the bootloader, but I noticed that It actually flashes a slightly modified version of fastboot.
PotatoNV can also unlock P20 lite bootloader, so you should give it a shot.
Good luck!
If it works, you should be able to flash stock recovery image and then restore the system using the dload folder.
you can Repair it with Software Testpoint and Full Bootloader Unlock ,and then flash a Board Software via Software Testpoint, that helps 100%!!!
use this Firmware Download ANE-LX1
use the Software with logins and you have all what you need.
you must start the Software Testpoint so!!
VIDEO : how to start Software Testpoint P20 Lite
than in Software Testpoint you flash the included Board Software with DC-Phoenix and after that use the included dload update via sdcard and eRecovery mode and your Phone is running!!!
I would unlock the bootloader via Software Testpoint with DC-Phoenix, then the FBLock is unlocked and you can flash as you wish!!!! And the great thing about it is that you don't need an UnlockKey either, you can then read this with HCU client software, the only thing that's stupid is that you need a time-based license for the two programs, which you have to buy.
HCU client download
https://hcu-client.com
DC Phoenix download
https://forum.dc-unlocker.com/forum/modems-and-phones/huawei/155916-dc-phoenix
Since I accidentally bought a 3-day license twice and my P20 Lite is now completely rooted on Lineage 19.1, I can give away 2 access data, which are still valid for 2 days.
you can edit your smartphone with it.
username : bl26457
password : kKncnkMj
username : bl26390
password : JDAZqnkN
Then I wish you a lot of fun with it, hope it helps you if someone else is active in this thread.
Hello
Let me preface this by saying: I'm not experienced in the world of rom flashing. I know very little.
I flashed my OnePlus Nord N10 5G with Lineage OS a few months ago, it was working fine until yesterday, when it got stuck in an infinite bootloop.
Whenever I start the phone, it shows the unlocked bootloader warning, then hangs infinitely on the Lineage boot animation.
I have tried multiple unbricking tutorials from this forum, and other websites. Nothing is working, because I don't think I had USB debugging enabled. My PC won't detect the Nord as a phone, so ADB and MSM won't recognize a device. Because of this I can't use ADB or MSM to install TWRP or flash a new image. I can get into Fastboot on the phone, that's all I can do.
Is there anything I can do to flash a stock rom, or any other way to restore factory settings? I don't need to save any of the data.
Thanks!
Well... if you can get to fastboot, you aren't bricked. EDL mode will let you flash a factory image over... the problem is that 100% kills anything you had on the phone.
If something "hangs infinitely", it might be possible it boots far enough to bring up ADB- meaning you could use logcat to see if there is something obvious with the startup that you might be able to fix.
I'm not familiar enough with Lineage to know how to recover it 100%... but based on the thread in XDA on this (e.g. the unofficial Lineage port) you start with flashing the Lineage recovery from fastboot. Does that not work? What fails? Most recoveries (e.g. TWRP) will unencrypt partions so you can at least copy them to SDCard and get your data off. Some of them will allow the phone side of ADB to boot, so you could do it with ADB PULL from 'puter side, too.
If you are indeed a n00b, make sure you learn the A/B thing- I can't do it justice here, but it WILL mess you up for reasons you won't understand until you've fought it many times (e.g. flash a recovery, but it does nothing because it is booting A and you flashed B).
After you have all your data off, I wouldn't bother trying to recover unless you are really bored... just EDL it to factory, then start anew if you want to go back to a custom ROM. FWIW, I found debloating and degoogling easier for me on this phone than trying to get everything else working. I am working now on CalyxOS on a Pixel 5G since it has all the proprietary blobs available to make all the hardware work, with a from-source-compiled-OS with re-lockable bootloader (when boot integrity works FOR you, it is a beautiful thing). Calyx is starting to futz with OnePlus phones, but they don't have a N10 image last I checked so I can't endorse it here... yet.
SomeRandomGuy said:
Well... if you can get to fastboot, you aren't bricked. EDL mode will let you flash a factory image over... the problem is that 100% kills anything you had on the phone.
If something "hangs infinitely", it might be possible it boots far enough to bring up ADB- meaning you could use logcat to see if there is something obvious with the startup that you might be able to fix.
I'm not familiar enough with Lineage to know how to recover it 100%... but based on the thread in XDA on this (e.g. the unofficial Lineage port) you start with flashing the Lineage recovery from fastboot. Does that not work? What fails? Most recoveries (e.g. TWRP) will unencrypt partions so you can at least copy them to SDCard and get your data off. Some of them will allow the phone side of ADB to boot, so you could do it with ADB PULL from 'puter side, too.
If you are indeed a n00b, make sure you learn the A/B thing- I can't do it justice here, but it WILL mess you up for reasons you won't understand until you've fought it many times (e.g. flash a recovery, but it does nothing because it is booting A and you flashed B).
After you have all your data off, I wouldn't bother trying to recover unless you are really bored... just EDL it to factory, then start anew if you want to go back to a custom ROM. FWIW, I found debloating and degoogling easier for me on this phone than trying to get everything else working. I am working now on CalyxOS on a Pixel 5G since it has all the proprietary blobs available to make all the hardware work, with a from-source-compiled-OS with re-lockable bootloader (when boot integrity works FOR you, it is a beautiful thing). Calyx is starting to futz with OnePlus phones, but they don't have a N10 image last I checked so I can't endorse it here... yet.
Click to expand...
Click to collapse
I'm fine with killing anything on the phone, nothing important on there. I've tried getting into EDL mode and using MSM Tool, but MSM doesn't see the phone when it's plugged in
When I try adb and enter "adb devices" in cmd prompt, no devices are listed. I also tried fastboot recovery via cmd prompt but after entering the command, it returns "<waiting for device>", so it's not seeing the phone either.
All I want to do is flash a factory image over, but I have no clue how to do that when the phone isn't being detected by any Windows program that can flash..
Thanks for your quick response, it would be incredible if you could help me sort this out!
Ok, so I assume you've read about the MSM tool here and maybe elsewhere, too, about 30 times? (Not being condescending, that's what it took me to get all of it, and I've been doing this for quite a while...).
My takeaways as I remember them:
- You need Windows. Yuck. If you are another OS, Virtualization is your friend, but make sure your USB passes through; in Linux that means some security adjustments.
- There is a SPECIAL qualcomm driver needed for Windows to see the EDL mode. This is hard to make sure you have installed correctly, but trips a lot of people- it is different than the phone/fastboot/ADB ones.
- The boot [physical] key combination only works for like 3 seconds or so to go to EDL - otherwise it will try to boot normally. That means get everything perfect, MSM running, mouse over "begin" (or whatever it is called), before you hold the keys and plug in the cable. Watch for it to appear, then quickly start once it is seen. Don't drop the keys until it says beginning firehose something or other. At that point sit back and relax.
- Make sure if you are loading a Win10 VM for this you cut it off the internet. Your friends in Redmond may try to auto-update including rebooting you in the middle of the download, which will not work out well for you.
If something goes south be specific, and I will try to help. Just remember, it is nearly impossible to brick a OnePlus due to EDL, so take your time and it will work
Oh yeah, while this is probably obvious, lemme say it for the record: (1) MSM puts it back to literal factory, so you have to re-unlock bootloader all over again to begin the quest of root/customization (2) this will absolutely wipe anything on the device data wise. SD cards are your friend.
SomeRandomGuy said:
Ok, so I assume you've read about the MSM tool here and maybe elsewhere, too, about 30 times? (Not being condescending, that's what it took me to get all of it, and I've been doing this for quite a while...).
My takeaways as I remember them:
- You need Windows. Yuck. If you are another OS, Virtualization is your friend, but make sure your USB passes through; in Linux that means some security adjustments.
- There is a SPECIAL qualcomm driver needed for Windows to see the EDL mode. This is hard to make sure you have installed correctly, but trips a lot of people- it is different than the phone/fastboot/ADB ones.
- The boot [physical] key combination only works for like 3 seconds or so to go to EDL - otherwise it will try to boot normally. That means get everything perfect, MSM running, mouse over "begin" (or whatever it is called), before you hold the keys and plug in the cable. Watch for it to appear, then quickly start once it is seen. Don't drop the keys until it says beginning firehose something or other. At that point sit back and relax.
- Make sure if you are loading a Win10 VM for this you cut it off the internet. Your friends in Redmond may try to auto-update including rebooting you in the middle of the download, which will not work out well for you.
If something goes south be specific, and I will try to help. Just remember, it is nearly impossible to brick a OnePlus due to EDL, so take your time and it will work
Click to expand...
Click to collapse
I was able to fix the issue by booting into EDL mode correctly, thank you so much for your help!
Glad to hear. Like I said, it took me many times reading over and over again, along with trial and error, before I made it happen the first time. But now that you're past it, have no more fear, flash away!
If something wasn't obvious to you, add a response to this or the OP article with your insight. It may help for many generations of phones to come.