Here's the full story: a few months ago I unlocked the bootloader of my Huawei Y300-0100, rooted it and installed TWRP. Some days ago I wanted to try a custom ROM but I made the mistake of wiping system and cust along with the caches and data, I didn't really notice it as I did it too fast (without reading) and attempted to install the ROM, but the phone froze while doing so.
I turned the phone off and turned it back in to find a green screen with two rectangles, one red and one blue.
After many days of searching on the internet I found that the only way to fix my phone is to flash the stock ROM by copying dload/UPDATE.APP to the root of the SD card, and turning on the phone while pressing vol+-, but the update stops at the second step.
Taking a look at the update log I see that the error is related to CRC, which means the UPDATE.APP has somehow been modified, but that's not true as I have tried both the stock ROM that came with the phone and the official update from Huawei, as well as many other updates, and they all give me the same CRC update.
If I attempt the update without an SD card the phone goes into a pink/purple-ish screen, connecting the phone to the PC, Ubuntu recognizes it as a GSM device, but there's something strange, when I type lsusb in the terminal I see this:
Code:
Bus 001 Device 021: ID 12d1:1035 Huawei Technologies Co., Ltd. U8120
Which is completely incorrect as this phone is not an U8120.
I have tried many different methods, such as doing the procedure without a battery or using more than 5 different SD cards and now I have no idea what to do next, can anyone help me out here?
Related
Hello everyone,
Last month I rooted my LG G2, and installed cyanogenmod. Everything was going smoothly but for some reason I decided to restore my phone from a backup I made before installing cyan and then just continued using it like that. Two nights ago an android software update took place automatically overnight and when I woke up it was just stuck in the TWRP menu. I tried restoring from previous backups, wiping it and re installing the cyanogenmod that was still on the virtual SD card to no avail, and finally completely formatting the phone to see if I could get it to show up on the computer because it makes the connection noise but it doesn't show up as a device or hard drive.
So now when it boots up it shows the LG logo and then brings me back to TWRP but now I have no restore points on the phone. So is there anyway to get my computer to recognize it so I can add files and hopefully get a working backup on the phone? Or is there a way I can even just flash the stock firmware on it again? Or am I out of luck?
cj0435 said:
Hello everyone,
Last month I rooted my LG G2, and installed cyanogenmod. Everything was going smoothly but for some reason I decided to restore my phone from a backup I made before installing cyan and then just continued using it like that. Two nights ago an android software update took place automatically overnight and when I woke up it was just stuck in the TWRP menu. I tried restoring from previous backups, wiping it and re installing the cyanogenmod that was still on the virtual SD card to no avail, and finally completely formatting the phone to see if I could get it to show up on the computer because it makes the connection noise but it doesn't show up as a device or hard drive.
So now when it boots up it shows the LG logo and then brings me back to TWRP but now I have no restore points on the phone. So is there anyway to get my computer to recognize it so I can add files and hopefully get a working backup on the phone? Or is there a way I can even just flash the stock firmware on it again? Or am I out of luck?
Click to expand...
Click to collapse
so you formatted your sdcard too. (jokes aside, thats genius). Mind my sarcastic fun-poking, you will have to put your phone into emergency mode and use a tool to flash the stock rom. Usually you can navigate to the manufacturers support page and they will have an updater tool that can flash one of the updates. if not, then scour the forums for an unbrick guide that will flash the stock rom from emergency mode.
Hello, everyone! I'm in search of a hero who can help me resolve this (frustrating) issue! I'm sure you have heard it before: my phone will not boot fully; it is instead stuck permanently on the white VERIZON logo screen.
Model: SCH-I545
Carrier: VERIZON
Color: BLACK
Size: 16GB
The phone has not been rooted.
It does not have USB debugging enabled.
I have not installed any custom recovery software or mods.
There is no external SD card installed.
First, some back story. My phone asked me to perform a software update roughly a week ago. About a minute into the update, it told me the update failed. I assume this occurred because I was on the train and passed through a tunnel. Afterwards, my phone began acting up, rebooting itself randomly, and applications(such as web browser, text messaging) would randomly crash on me. I assumed another update would come to resolve the issue, but unfortunately yesterday(Sunday), my phone again rebooted itself, only this time it would not make it past the white VERIZON screen.
My goal is simply to recover my files from the device before either returning it or performing a factory reset. I have scoured the internet for hours trying to find a way to achieve this. I can boot my device into the stock recovery console and into ODIN download mode. I have tried clearing my phone's cache in recovery mode, which did not help. I have tried booting into safe mode by repeatedly tapping the menu screen, but it did not help.
I have ADB installed and a USB driver from Samsung and a USB driver from Google. I can get my phone to appear using ADB in sideload mode only while in the recovery console. Unfortunately, this is of limited use because apparently it can only be used to install software packages, and the phone seemingly rejects all attempts to install packages such as CWM and TWRK, which I had hoped would allow me to use the ADB pull command.
I have tried installing these mods using ODIN as well. Again, failure due to security apparently. :crying:
If anyone has any idea how I can retrieve the files from my phone, you'll be my hero forever!
BeefJerkyAddict said:
Hello, everyone! I'm in search of a hero who can help me resolve this (frustrating) issue! I'm sure you have heard it before: my phone will not boot fully; it is instead stuck permanently on the white VERIZON logo screen.
Model: SCH-I545
Carrier: VERIZON
Color: BLACK
Size: 16GB
The phone has not been rooted.
It does not have USB debugging enabled.
I have not installed any custom recovery software or mods.
There is no external SD card installed.
First, some back story. My phone asked me to perform a software update roughly a week ago. About a minute into the update, it told me the update failed. I assume this occurred because I was on the train and passed through a tunnel. Afterwards, my phone began acting up, rebooting itself randomly, and applications(such as web browser, text messaging) would randomly crash on me. I assumed another update would come to resolve the issue, but unfortunately yesterday(Sunday), my phone again rebooted itself, only this time it would not make it past the white VERIZON screen.
My goal is simply to recover my files from the device before either returning it or performing a factory reset. I have scoured the internet for hours trying to find a way to achieve this. I can boot my device into the stock recovery console and into ODIN download mode. I have tried clearing my phone's cache in recovery mode, which did not help. I have tried booting into safe mode by repeatedly tapping the menu screen, but it did not help.
I have ADB installed and a USB driver from Samsung and a USB driver from Google. I can get my phone to appear using ADB in sideload mode only while in the recovery console. Unfortunately, this is of limited use because apparently it can only be used to install software packages, and the phone seemingly rejects all attempts to install packages such as CWM and TWRK, which I had hoped would allow me to use the ADB pull command.
I have tried installing these mods using ODIN as well. Again, failure due to security apparently. :crying:
If anyone has any idea how I can retrieve the files from my phone, you'll be my hero forever!
Click to expand...
Click to collapse
Sounds like that upgrade definitely went wrong. Since you were upgrading to Kit Kat I'd say flash the No Wipe file from here http://forum.xda-developers.com/showthread.php?t=2735172
Your phone won't allow for CWM or TWRP recoveries since it's a build past MDK. Also if you want prior to using that Odin file go to play store and get the app " Samsung phone info" and run that app and take a screen shot of the bootloader section. Actually do that before hand anyways. I'll link you to it
Sent from my SCH-I545 using Tapatalk
---------- Post added at 06:39 AM ---------- Previous post was at 06:39 AM ----------
Here
https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo
Sent from my SCH-I545 using Tapatalk
hopefully people will learn by this NEVER take any update while traveling, too much can and will go wrong.............
Yea I think people have to much faith in Verizon. There not setup to handle anything but a perfect download and install when it comes to their OTAs. They're best done on WiFi at home
Sent from my SCH-I545 using Tapatalk
Reply
BeefJerkyAddict said:
Hello, everyone! I'm in search of a hero who can help me resolve this (frustrating) issue! I'm sure you have heard it before: my phone will not boot fully; it is instead stuck permanently on the white VERIZON logo screen.
Model: SCH-I545
Carrier: VERIZON
Color: BLACK
Size: 16GB
The phone has not been rooted.
It does not have USB debugging enabled.
I have not installed any custom recovery software or mods.
There is no external SD card installed.
First, some back story. My phone asked me to perform a software update roughly a week ago. About a minute into the update, it told me the update failed. I assume this occurred because I was on the train and passed through a tunnel. Afterwards, my phone began acting up, rebooting itself randomly, and applications(such as web browser, text messaging) would randomly crash on me. I assumed another update would come to resolve the issue, but unfortunately yesterday(Sunday), my phone again rebooted itself, only this time it would not make it past the white VERIZON screen.
My goal is simply to recover my files from the device before either returning it or performing a factory reset. I have scoured the internet for hours trying to find a way to achieve this. I can boot my device into the stock recovery console and into ODIN download mode. I have tried clearing my phone's cache in recovery mode, which did not help. I have tried booting into safe mode by repeatedly tapping the menu screen, but it did not help.
I have ADB installed and a USB driver from Samsung and a USB driver from Google. I can get my phone to appear using ADB in sideload mode only while in the recovery console. Unfortunately, this is of limited use because apparently it can only be used to install software packages, and the phone seemingly rejects all attempts to install packages such as CWM and TWRK, which I had hoped would allow me to use the ADB pull command.
I have tried installing these mods using ODIN as well. Again, failure due to security apparently. :crying:
If anyone has any idea how I can retrieve the files from my phone, you'll be my hero forever!
Click to expand...
Click to collapse
Hi BeefJerkyAddict,
I would reccomend to do a total full wipe with Odin, this usually solves all of your problems. All of your stuff should be clear for restoring once you do that. But after you do the full wipe, immediately go to settings and then software update because your phone will be on android 4.3 and not 4.4.2.
Here is the link with the instructions as well:
http://forum.xda-developers.com/showthread.php?t=2578209
You're welcome.
Yea I guess I'm just biased to updating straight to kit kat lol if the op has the chance to stay on mk2 he might as well. And I suggested no wipe first just so not to lose data. Up to the op though
Sent from my SCH-I545 using Tapatalk
Hi guys,
Just posting to say THANK YOU for the help. After a long download, I got ahold of the VRUFNC5 No-Wipe file and successfully installed it using ODIN3 v3.09 without a hitch! All of my pictures, videos, text messages, are all right where they were, and my operating system is upgraded.
Thank you so much for taking the time to point me in the right direction. I had nearly given up!
Hello, XDA forumites!
I've been lurking and reading a lot of threads in here for years, using all your knowledge to fix various phones. Today though is the day I first post and it is for good reason. I'm a guy who loves challenges but this one is making me go insane. I've spend the last two days looking for ways to fix this phone but NOTHING works.
So, the deal is that this phone turns on fine. It boots, it gets to the lockscreen and... it restarts itself. Again and again and again until the battery is removed. To fix it, I've tried the following:
- recovering/updating it through the Huawei official "firmware" supplied by the site: you put the file they supply on an SD card, inside a folder named "dload" and then hold vol up and down along with the power button to make the phone install the contents of that file, named UPDATE.APP. Needless to say it doesn't work. A menu appears with the options reboot system now, apply update from sdcard, apply update from cache, wipe/data factory reset, wipe cache partition and calibrate touch screen. Trying to apply update from sdcard only lets me browse the SD looking for the file but doesn't actually see the file itself, it just shows the dload folder empty (I've tried with 4 different versions of the file compatible with phones from Central America which is where I am ATM). Also, the factory reset does nothing (although it shows it wipes data), everything's there when I start the phone up.
- flashing it with SD Flash Tool: apparently partially works with the last version 3 of the tool (although nothing changes) while version 5 of SDFT doesn't even see the phone (drivers are correctly installed, adb detects it, more on this later). A problem that arises is that I can't flash the SEC_RO package on it (don't know why) nor the PRELOADER (not that one is supposed to normally, but I feel like it would fix my problem in this case).
- cleaning it in safe mode: booting it in safe mode made me notice that it was an app pretending to be Whatsapp causing the restarts (or, perhaps, the one that loads immediately after? The phone has several malware apps). In safe mode those apps didn't load so the phone stayed on. So I cleaned everything, activated USB debugging (for later use in adb mode) and restarted only to find everything as it was before I did the cleanup. I tried rooting it in safemode, cleaning again, still reverts to full "normality" after the restart. Same results when using the phone's proprietary SW HiSuite.
- installing CWM's recovery img through adb+fastboot: I installed all the possible - necessary or unnecessary - drivers (Google's, phone's official ones, PDANet ones) and the phone is correctly detected by the PC (visible in Device Manager) and is visible through the adb devices command. But as soon as I adb reboot bootloader it to fastload the CWM image, the phone stops being seen correctly and doesn't show up in fastboot devices, only showing "NEW: SAFE OLD:RISK" on a black background on its screen.
So, to recap: the phone restarts because of a malware at startup, reverts any and all changes made to it in safemode, doesn't wipe from the recovery menu, apparently has a corrupted bootloader and is impervious to normal flashing SW... Anyone got any more ideas on how to deal with it? The only option left that comes to mind is to fix it directly by flashing the internal memory using JTAG/RIFF but I don't have the equipment (nor do I intend to buy it).
Bump, hoping for some help...
One more bump, still stuck
First, don't get happy: I have no answer to your problem. Sorry. But I have a similar one. I was running a very efficient, rooted, stock ROM G730-U251, until I decided to switch from 'Ninjamorph Free' to 'Pro'. I've been made a lot of changes with Free version for a long time without any issues at all. Then, one day, when making a small, useless change with 'Pro', something went wrong; phone just rebooted and refused to get past bootanimation. With no custom recovery on hand, only solution for this is to flash ROM. Though I had no problem finding the official, stock UPDATE.APP, which flashed smoothly from the SD card to be fair. Mess came when, once flashed, I decided to install OTA update available, which I overlooked since phone was new. Big, BIG mistake. It just came with more restrictions than ever, letting me root, yes, but this time with 'Kingroot' only (as stock, I had no problem rooting with Framaroot) but soon discovered I wasn't able to use 'Super-Sume', 'Adaway' and 'Link2SD', because some system parts now CAN'T be mounted rw, even using ES File Explorer. To avoid any complication, decided to reflash UPDATE.APP just as I did before. No way I can do it this time. Don't know exactly why, but assuming it's not possible to update with a previous version of the 'same' ROM. So now I'm looking for a flashable stock ROM in order to try SP flash tool. Phone is in working state right now (not as yours), but I just don't feel comfortable with it as it is right now, because those apps are always the main reason why I actually root every single of my devices and simply because I like to have my stuff as my own way as possible. You know, truth is there's not much of an advanced support for this phone, not even here at XDA and I think that's because this is a Latin America version. We owners of G730-U251 devices are pretty much on our own, to say the least. Whatever, if the whole deal gets more complicated than it is, there's a strong possibility for me to end up getting rid of this phone. Sad. Really. It's actually a good phone. Though it WAS better...
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.
Hi hope someone can advise as I'm loosing the will to live
I've a mate 8 NXT-L29C636 which I believe is asia region although I've from the UK
I was running stock android 6 with EMUI 4.0
When I ask it to check for any update, it always came back with no updates.
I saw plenty of threads saying they had updated to android 7 and 8 and how they done it.
So I downloaded Firmware Finder from Google play and without too much difficulty managed to start installing firmware. That's when my problems started
This was two weeks ago and I've been spending 100+ hours trying to recover.
I think it failed a 5% or something and since then my phone will not boot properly.
I can only fastboot it and sometimes to erecovery and EMUI to wipe/factory reset
Searching forums it seems DC Phoenix was the only software that could help so I bought it.
So far I've tried flashing firmware from DC-Unlocker site in standard more but all goes ok with success for all the partitions but it requires the phone to put into upgrade mode, something my phone never does and I can't force it.
So that leaves me with advanced mode, again all successful but booting the phone just gives the huawei logo then reboots again
I've tried different stock roms NXT-L29C636 but they all claim successful but still can't boot my phone
I've followed the steps in DC-Phoenix instructions to no avail.
The last step today meant shorting a pin to ground to force the phone into a mode when it was seen as windows as Huawei USB COM device, which seemed to work.
The instructions claimed I can use any NXT board flash as they're all the same and again all successful i used
NXT-AL10_M00A102_Board Software_Global _Nonspecific_Android 6.0_EMUI 4.0_05021WLB_4.dtwork
but the log file now says build is;
Build number: HLNXTAL10BM00A102
Model: HUAWEI NXT-L29
Battery state: 3249mv
from
Build number: :NXT-L29C432B192
Model: HUAWEI NXT-L29
Battery state: 7035mv
So my question is am I using the wrong firmware? It is always successful so I don't think it's bricked but I can't work out what I'm doing wrong.
Other things to mention is pressing vol - and vol + and power with sd card and dload doesn't work either.
Sorry for long post and thanks for reading
Any help very much appreciated