Related
So I was messing with some kernel stuff when after flashing something I noticed I no longer was connecting to Sprint, It just would say "No Service" I figured that restoring a NAND backup would correct this issue but it hasn't. The issue has been persistent with any rom I tried. Another issue i noticed is that I couldn't connect my phone do a PC and transfer files, I soon came to the realization the reason was that when the system booted the sd card wouldn't mount. If i tried to "cd /sdcard" it would say "no such file or directory" So unsure of what to do I began to start the process of restoring stock with RUU. But unfortunately I couldn't make it through the process. Unfortunately my sdcard got formatted when I Re-unlocked my bootloader, this means I don't have any roms to flash, and when I try to use ADB from TWRP it says there is no device connected.
I really must have screwed something up and it seems to me this won't be a quick fix. to start off I was wondering if anybody could donate a system.img from their cyanogenmod installation just so I can flash via fastboot and get started or could point me in the direction of getting one.
Thanks for the help everyone, I hope I can get my One working again.
CyrodiilSavior said:
So I was messing with some kernel stuff when after flashing something I noticed I no longer was connecting to Sprint, It just would say "No Service" I figured that restoring a NAND backup would correct this issue but it hasn't. The issue has been persistent with any rom I tried. Another issue i noticed is that I couldn't connect my phone do a PC and transfer files, I soon came to the realization the reason was that when the system booted the sd card wouldn't mount. If i tried to "cd /sdcard" it would say "no such file or directory" So unsure of what to do I began to start the process of restoring stock with RUU. But unfortunately I couldn't make it through the process. Unfortunately my sdcard got formatted when I Re-unlocked my bootloader, this means I don't have any roms to flash, and when I try to use ADB from TWRP it says there is no device connected.
I really must have screwed something up and it seems to me this won't be a quick fix. to start off I was wondering if anybody could donate a system.img from their cyanogenmod installation just so I can flash via fastboot and get started or could point me in the direction of getting one.
Thanks for the help everyone, I hope I can get my One working again.
Click to expand...
Click to collapse
First, you need to Relock your bootloader, Unroot, then S-ON your devide , Then flash RUU rom via Command in PC ( fastboot , ADB )
Finaly : if you want Flash a custom Rom , you should unlock bootloader , Root your HTC ONE , Flash recovery and then Flash custom Rom
Hope this can help you , sorry for my bad in english , I'm VietNamese
I attempted to relock unroot RUU etc. via this method, but the process got stuck at Checking Headers.
Is there another way of doing this?
CyrodiilSavior said:
I attempted to relock unroot RUU etc. via this method, but the process got stuck at Checking Headers.
Is there another way of doing this?
Click to expand...
Click to collapse
Make sure you're running it on a Windows 7 PC.
I did use a windows 7 64bit machine yesterday when it got stuck on Checking headers. I also tried on my Ubuntu system using the manual Decrypted method. Upon typing "sudo fastboot flash /system newimage.img" it returned :
Code:
target reported max download size of 1520349184 bytes
Invalid sparse file format at header magi
sending sparse '/system' (1456350 KB)...
FAILED (status read failed (Bad file descriptor))
finished. total time: 33.855s
Any ideas as to why it cant do this?
I'm sorry for not being more descriptive, I have a pretty strong background in linux and android but this issue has really stumped me.
CyrodiilSavior said:
I did use a windows 7 64bit machine yesterday when it got stuck on Checking headers. I also tried on my Ubuntu system using the manual Decrypted method. Upon typing "sudo fastboot flash /system newimage.img" it returned :
Code:
target reported max download size of 1520349184 bytes
Invalid sparse file format at header magi
sending sparse '/system' (1456350 KB)...
FAILED (status read failed (Bad file descriptor))
finished. total time: 33.855s
Any ideas as to why it cant do this?
Click to expand...
Click to collapse
The decrypted version won't work; it's for developer use only (making ROMs etc). Try using a USB-OTG cable in TWRP to flash a ROM.
StormyNight said:
The decrypted version won't work; it's for developer use only (making ROMs etc). Try using a USB-OTG cable in TWRP to flash a ROM.
Click to expand...
Click to collapse
Last night I finally managed to flash a ROM through recovery. I booted into the os and everything works fine aside from the network. I still am unable to connect to the sprint network, It just says "No Service". I've done some research and it seems to me the best/only way to fix this issue is to flash it back to stock. Which I have been unable to succeed in doing.
Let me know what you think my next step would be, either if I should continue trying to go back to stock or to fix the network issue with my current ROM.
CyrodiilSavior said:
Last night I finally managed to flash a ROM through recovery. I booted into the os and everything works fine aside from the network. I still am unable to connect to the sprint network, It just says "No Service". I've done some research and it seems to me the best/only way to fix this issue is to flash it back to stock. Which I have been unable to succeed in doing.
Let me know what you think my next step would be, either if I should continue trying to go back to stock or to fix the network issue with my current ROM.
Click to expand...
Click to collapse
Flash the latest radio/baseband founf HERE
BD619 said:
Flash the latest radio/baseband founf HERE
Click to expand...
Click to collapse
I didn't notice this till now but the sdcard is not mounting. I have the ability to mount it in recovery but when booted into system no luck. I am thinking reflashing a new boot.IMG would correct the issue.
Good news, I did an adb push and flashed the radio and that fixed it, I now can connect to sprint and my Sdcard is now mounting.
Thanks so much to everyone for the help. I really appreciate it!
Hello i was using this guide :
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
to root my phone i went and finished fastboot oem unlock step
the problem is after it and booted the phone i extracted the root files and clicked on it
then realized it said oem is not enabled in developer option
so now when i boot the phone a message says"Your Device is Corrupt. It can't be trusted and may not work properly."
and after it like 1-2 sec it turns off
i can still boot in bootloader
PLEASE SOME ONE HELP ME
Also it says device is unlocked in the bootloader statues code 3
extra information i was using android marshmallow 6 latest firmware
oudric said:
Hello i was using this guide :
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
to root my phone i went and finished fastboot oem unlock step
the problem is after it and booted the phone i extracted the root files and clicked on it
then realized it said oem is not enabled in developer option
so now when i boot the phone a message says"Your Device is Corrupt. It can't be trusted and may not work properly."
and after it like 1-2 sec it turns off
i can still boot in bootloader
PLEASE SOME ONE HELP ME
Also it says device is unlocked in the bootloader statues code 3
extra information i was using android marshmallow 6 latest firmware
Click to expand...
Click to collapse
The same thing happened to me when I tried to use a rootkit method for rooting the phone when it apparently knew nothing about the most recent updates (MRA58N or MRA58R). I ended up having to manual flash each individual image file from the MRA58N factory image (the flash-all script in the factory image zip wouldn't work). Even so, when I rebooted it still displayed the Your Device is Corrupt message. Then I went through the manual root process again (flashed the modified boot.img through fastboot, then flashed the latest TWRP recovery via fastboot, and then used TWRP to flash the latest SuperSU. Only then did the Your Device is Corrupt message go away and I also had root with everything else working fine.
It definitely made for an un-Godly horrible first 24-hours with my new phone! I hope this helps you.
internetpilot said:
The same thing happened to me when I tried to use a rootkit method for rooting the phone when it apparently knew nothing about the most recent updates (MRA58N or MRA58R). I ended up having to manual flash each individual image file from the MRA58N factory image (the flash-all script in the factory image zip wouldn't work). Even so, when I rebooted it still displayed the Your Device is Corrupt message. Then I went through the manual root process again (flashed the modified boot.img through fastboot, then flashed the latest TWRP recovery via fastboot, and then used TWRP to flash the latest SuperSU. Only then did the Your Device is Corrupt message go away and I also had root with everything else working fine.
It definitely made for an un-Godly horrible first 24-hours with my new phone! I hope this helps you.
Click to expand...
Click to collapse
can you please tell me steps i am so afraid to do anything to my phone now and i think my problem is same as yours
i downloaded 6.0.0 (MRA58R) and i used option in toolkit flash stock it gave me an error
"failed (data transfer failure (unknown error))
Its not so easy to brick nexus, but make sure you don't lock bootloader before your phone is working right. You can find the guide how to flash it on XDA.
You will need to flash the missing files by hand.
I was able to fix the erro i got by flashing by :
setting up environmental variable
copy all the flash files, all.bat bootloaderXXX.img... etc to platform tools folder
made sure i connected into usb 2.0 port not usb 3.0
then i flashed the stock firmware XD now my phone to point zero again
oudric said:
I was able to fix the erro i got by flashing by :
setting up environmental variable
copy all the flash files, all.bat bootloaderXXX.img... etc to platform tools folder
made sure i connected into usb 2.0 port not usb 3.0
then i flashed the stock firmware XD now my phone to point zero again
Click to expand...
Click to collapse
You don't need to move the files to the platform-tools folder.
Go to Nexus 6 General > Sticky rol-up thread > Adb and fastboot. What is it?
This will tell you how to set up and use adb or fastboot properly.
Folks,
I recently purchased a preowned HTC One M9 in good shape. The phone does not appear to have been rooted, s-offed or any such thing. It looks bone stock. It currently has Android 6.0 on it. and software number 3.39.531.41
It has been over a month since t-mobile has rolled out the nougat update for the HTC One-M9 and I have not received any update on the phone. I constantly keep checking if the phone has an update available but the phone always says no update available. I gave up on the OTA being rolled out for the phone so I downloaded the Nougat RUU which is 4.27.531.6 .
When I follow the procedure for installing the update I got a signature error 132 . Now I know that error shows up when the phone is rooted or is s-off or any such thing but my phone seems to be completely stock. Does anyone know why I cant install the RUU or receive OTA updates to Nougat for my phone?
I think I figured it out. I contacted T-Mobile support who told me to contact HTC since the HTC servers are responsible for pushing out updates. So I contacted HTC customer support and shared my IMEI with the representative. She looked up some information on the HTC database using the IMEI number and told me that my phone was a store demo phone and that demo phones are blocked from receiving updates from the HTC servers. Oh well.
Hello,
Just got the same phone with same error. If someone provides me with 0PJAIMG.ZIP, I can test and see how it goes. So far update from phone >> didn't work; RUU update >> didn't work. same error
Thanks
I had the same problem some time a go what you have to do is to check if its relock and has stock recovery. If yes first flash 3.39.531.41 RUU before you can flash the 4.27.531.6 or the OTA. But my receives the OTA alright but could neither install that or RUU
amptronic said:
I had the same problem some time a go what you have do is to check if its relock and has stock recovery. If yes first flash 3.39.531.41 RUU before you can flash the 4.27.531.6 or the OTA.
Click to expand...
Click to collapse
So it has to be locked with stock recovery? Then flash ruu 3.49 ad then the newest version?
Thanks
dohcvtec said:
So it has to be locked with stock recovery? Then flash ruu 3.49 ad then the newest version?
Thanks
Click to expand...
Click to collapse
did it work?? I'm having same problem..
smilesintears77 said:
did it work?? I'm having same problem..
Click to expand...
Click to collapse
Did anyone get any solution for this error? I am having the same issue
Thanks
vbcomer said:
Did anyone get any solution for this error? I am having the same issue
Thanks
Click to expand...
Click to collapse
i think first decrypt RUU then manually flash whole Nougat ROM.
vbcomer said:
Did anyone get any solution for this error? I am having the same issue
Thanks
Click to expand...
Click to collapse
i found a way i have demo set when i use 4.27.531.6 RUU its saying signature error so this is what i did
i download OTA from link here http://fotadl-az.htc.com/secure/OTA_HIMA_UL_N70_SENSE80_TMUS_MR_TMOUS_4.27.531.6-3.39.531.41_release_497409trrpztkwvabkx6lv.zip
after that i just boot into recovery mode and then select an opton Updae via ADB
rename file to OTA.zip then open command prompt located to where file is and then run below command
adb sideload ota.zip
let the process finish it will take a while. especially when HTC logo appears it took 5 min but i finally have nougat
for detail how to apply OTA here is link http://www.theandroidsoul.com/how-to-install-ota-updates-manually-using-recovery-and-adb-sideload/
m_abbas25 said:
i found a way i have demo set when i use 4.27.531.6 RUU its saying signature error so this is what i did
i download OTA from link here http://fotadl-az.htc.com/secure/OTA_HIMA_UL_N70_SENSE80_TMUS_MR_TMOUS_4.27.531.6-3.39.531.41_release_497409trrpztkwvabkx6lv.zip
after that i just boot into recovery mode and then select an opton Updae via ADB
rename file to OTA.zip then open command prompt located to where file is and then run below command
adb sideload ota.zip
let the process finish it will take a while. especially when HTC logo appears it took 5 min but i finally have nougat
for detail how to apply OTA here is link http://www.theandroidsoul.com/how-to-install-ota-updates-manually-using-recovery-and-adb-sideload/
Click to expand...
Click to collapse
Hi,
Thanks for the info. However, I couldn't get into the recovery mode. Either from bootloader -> "Boot to recovery mode" or via command "adb reboot recovery", after the phone reboots, the screen will show a phone icon with triangle. Then after awhile the phone will restart normally. I can't get to step to do sideload the zip file.
I also put the above ota.zip on a micro SD card and load the card in the phone, then boot to download mode. In that mode, it shows the following 2 lines:
FILE /mnt/media_rw/ext_sd/0PJAIMG.zip
File NOT FOUND
Where do I find that missing file?
Thanks
vbcomer said:
Hi,
Thanks for the info. However, I couldn't get into the recovery mode. Either from bootloader -> "Boot to recovery mode" or via command "adb reboot recovery", after the phone reboots, the screen will show a phone icon with triangle. Then after awhile the phone will restart normally. I can't get to step to do sideload the zip file.
I also put the above ota.zip on a micro SD card and load the card in the phone, then boot to download mode. In that mode, it shows the following 2 lines:
FILE /mnt/media_rw/ext_sd/0PJAIMG.zip
File NOT FOUND
Where do I find that missing file?
Thanks
Click to expand...
Click to collapse
I think your recovery file is damaged. Thou i am novice in this but i think you should run RUU of existing rom it may repair your recovery then try this method.
OK,
I found the 0PJAIMG.zip for version 3.39.531.7 in this forum "https://forum.xda-developers.com/tmobile-one-m9/general/please-read-rooting-using-twrp-t3069022"
I put that on my SD card and was able to update the phone from Lollipop to Marshmallow.
However, after that update, the phone still won't update from Marshmallow to Nougat using the file RUU_HIMA_UL_N70_SENSE80_TMUS_MR_TMOUS_4.27.531.6 downloaded from htc website nor the OTA.zip downloaded from this thread. The phone keeps having the same Error [132] Signature Error. Or it won't go into the Recovery mode to do sideload of the OTA.zip. If the original Recovery file (from Lollipop) was bad/corrupt, wouldn't the Marshmallow update correct/fix that file?
So, do we have any other idea to upgrade the phone from Android 6.0 to 7.0? Does anyone have a 0PJAIMG.zip for 7.0?
Thanks
vbcomer said:
OK,
I found the 0PJAIMG.zip for version 3.39.531.7 in this forum "https://forum.xda-developers.com/tmobile-one-m9/general/please-read-rooting-using-twrp-t3069022"
I put that on my SD card and was able to update the phone from Lollipop to Marshmallow.
However, after that update, the phone still won't update from Marshmallow to Nougat using the file RUU_HIMA_UL_N70_SENSE80_TMUS_MR_TMOUS_4.27.531.6 downloaded from htc website nor the OTA.zip downloaded from this thread. The phone keeps having the same Error [132] Signature Error. Or it won't go into the Recovery mode to do sideload of the OTA.zip. If the original Recovery file (from Lollipop) was bad/corrupt, wouldn't the Marshmallow update correct/fix that file?
So, do we have any other idea to upgrade the phone from Android 6.0 to 7.0? Does anyone have a 0PJAIMG.zip for 7.0?
Thanks
Click to expand...
Click to collapse
In order to OTA to work which is in this forum you have to be in 3.39.531.41 first find RUU of this version run it then go for OTA.
Noted that you wont be able to update from marshmallow to nougat using RUU you have to use OTA but for that you must be in version 3.39.531.41 .
Ok. I was able to install 3.39.531.41. I will try the OTA now
m_abbas25 said:
In order to OTA to work which is in this forum you have to be in 3.39.531.41 first find RUU of this version run it then go for OTA.
Noted that you wont be able to update from marshmallow to nougat using RUU you have to use OTA but for that you must be in version 3.39.531.41 .
Click to expand...
Click to collapse
I updated to version 3.39.531.41 but I am still unable to get to Recovery mode on my phone. It keeps showing the red triangle with exclamation mark.
So, is that correct that I am now having two choices (besides obviously stay with Marshmallow)
1. Need to somehow fix the recovery mode on the phone? It is a demo unit so I don't know if that has anything with the recovery not working
2. Try to download the 0PJAIMG for 4.27 (Nougat) and install from sd card. I did find the file from AndroidFileHost website, but the phone gave error when it tried to load the zip file from download mode:
12 RU_ZIP_ERROR
FAIL 12 RU_ZIP_ERROR
Do you have a reliable source for the OPJAIMG file for Nougat?
I did a research on the 12 RU_ZIP_ERROR and found an instruction for AT&T from developer Blueberry who suggested "If you're on Marshmallow base, first of all you need to upgrade your firmware and then flash this 0PJAIMG zip file via download mode in otherwise you'll be getting "12 RU_ZIP ERROR" during the flash process. No Wipe Firmware Link: https://www.androidfilehost.com/?fid=745425885120692233"
The above was for AT&T but I found the no_wipe zip for TMobile, however, I don't know how to upgrade the firmware on my phone using one of these files
the firmware no_wipe files are here:
https://www.androidfilehost.com/?w=files&flid=134381
The file I downloaded is "firmware_tmous_4.27.531.6_NoWipe.zip", but like I said above, I don't know how to update the firmware.... Can someone give me some directions?
Update: I renamed the file "firmware_tmous_4.27.531.6_NoWipe.zip" to "0PJAIMG.zip" and tried to update from download mode, but the phone gave error: 8 RU_SIGNATURE_FAIL.
Another research indicated that since the phone is S-ON and Locked, these firmware wouldn't install because they were not signed. Where can I find signed firmware for this phone?
Thanks
vbcomer said:
I updated to version 3.39.531.41 but I am still unable to get to Recovery mode on my phone. It keeps showing the red triangle with exclamation mark.
So, is that correct that I am now having two choices (besides obviously stay with Marshmallow)
1. Need to somehow fix the recovery mode on the phone? It is a demo unit so I don't know if that has anything with the recovery not working
2. Try to download the 0PJAIMG for 4.27 (Nougat) and install from sd card. I did find the file from AndroidFileHost website, but the phone gave error when it tried to load the zip file from download mode:
12 RU_ZIP_ERROR
FAIL 12 RU_ZIP_ERROR
Do you have a reliable source for the OPJAIMG file for Nougat?
I did a research on the 12 RU_ZIP_ERROR and found an instruction for AT&T from developer Blueberry who suggested "If you're on Marshmallow base, first of all you need to upgrade your firmware and then flash this 0PJAIMG zip file via download mode in otherwise you'll be getting "12 RU_ZIP ERROR" during the flash process. No Wipe Firmware Link: https://www.androidfilehost.com/?fid=745425885120692233"
The above was for AT&T but I found the no_wipe zip for TMobile, however, I don't know how to upgrade the firmware on my phone using one of these files
the firmware no_wipe files are here:
https://www.androidfilehost.com/?w=files&flid=134381
The file I downloaded is "firmware_tmous_4.27.531.6_NoWipe.zip", but like I said above, I don't know how to update the firmware.... Can someone give me some directions?
Update: I renamed the file "firmware_tmous_4.27.531.6_NoWipe.zip" to "0PJAIMG.zip" and tried to update from download mode, but the phone gave error: 8 RU_SIGNATURE_FAIL.
Another research indicated that since the phone is S-ON and Locked, these firmware wouldn't install because they were not signed. Where can I find signed firmware for this phone?
Thanks
Click to expand...
Click to collapse
I don't know much now but we can try RUU of 3.39.531.41. It should solve your recovery. But the question is where you can download that?? Try finding a link mean while i am uploading it to my google drive then i will share link. Since i am in third world country it will take time. I will update you as soon as it is uploaded
vbcomer said:
I updated to version 3.39.531.41 but I am still unable to get to Recovery mode on my phone. It keeps showing the red triangle with exclamation mark.
So, is that correct that I am now having two choices (besides obviously stay with Marshmallow)
1. Need to somehow fix the recovery mode on the phone? It is a demo unit so I don't know if that has anything with the recovery not working
Thanks
Click to expand...
Click to collapse
To continue on to recovery mode, try this:
" If a device with a red triangle and exclamation point appears, Hold Power while pressing and releasing Volume Up to continue."
As for the 3.39.531.41 RUU, put the zip from this link into your external SD then boot into fastboot/download mode. From that point on the phone should automatically recognize the .zip and install from there.
https://www.androidfilehost.com/?fid=24438995911969398,
Thank you much! I will try everything you suggested now. I really appreciate your help!
dbs25 said:
To continue on to recovery mode, try this:
" If a device with a red triangle and exclamation point appears, Hold Power while pressing and releasing Volume Up to continue."
As for the 3.39.531.41 RUU, put the zip from this link into your external SD then boot into fastboot/download mode. From that point on the phone should automatically recognize the .zip and install from there.
https://www.androidfilehost.com/?fid=24438995911969398,
Click to expand...
Click to collapse
I downloaded the RUU from above link [https://www.androidfilehost.com/?fid=24438995911969398], but after installing, the phone went from 3.39.531.41 back to 3.39.531.7. Was the above zip file really the 531.41 version?
I tried to reinstall the 0PJAIMG for 531.41 downloaded earlier, but the phone said signature error.
I tried to install using the OTA zip from this link [http://fotadl-az.htc.com/secure/OTA_...kwvabkx6lv.zip] from Recovery mode but the phone said "E3001: Package expects build fingerprint of htc/himaul_tmous/htc_himaul:6.0/MRA58K/690290.41:user/release-keys or htc/himaul_tmous/htc_himaul:7.0/NRD90M/869604.6:user/release-keys; this device has htc/himaul_tmous/htc_himaul:6.0/MRA58K/690290.7:user/relea
E:Error in /sideload/package.zip (Status 7)
Installation aborted
You have any idea to go back to 531.41? Since the OTA message seemed to indicate it expected a 531.41 version?
Thanks
Ok. I was able to get back to 3.39.531.41 by getting the 0PJAIMG from AndroidFileHost.
After that, I went to Recovery Mode (using pwr + vol up after seeing the red triangle), chose Apply Update from SDCard, selected the OTA file for 4.27.531.6. This time It didn't give any error, at the end it appeared to get stuck for a long time at the line Script Succeeded Result was [/preload]. After about an hour, I turned off the phone and on again, now it is stuck at HTC logo splash screen.
Questions here:
1. Was the phone really stuck at the "script succeeded" line?
2. Didn't I wait long enough?
3. What should I have done at that time when it stopped at that "script succeeded" line?
4. What should I do at this splash screen? It has been like that for the last 10 minutes
Thanks
Hi, I think i've kinda bricked my honor 5C (nem-l51), and I really need help :
A few years ago I rooted my phone to make otg work.
It worked a little while, but then a system update came up, could not update because of the twrp, so I tried to unroot it (from supersu) to do the update, and the twrp stayed after the unroot.
I stayed with the phone like this, twrp installed and update pending (still trying to install the update from time to time) and then I had to use OTG again and tried to re-root my phone.
I tried to flash the supersu files I used the first time, but, even when the flashing worked, I couldn't see the supersu app on the phone, still unrooted.
Then I tried to change the twrp (via fastboot) and I realised that I couldn't : I get the "command not allowed" failure when the recovery should get written. I tried with numerous twrp versions, and stock recovery.
So my twrp right now is the twrp-3.1.1-0-venus "OpenKirin edition" one.
The phone says it's unlocked and the frp is locked, but I can't remember if it was already the case or not when I first rooted.
I unfortunately don't have anymore the bootloader unlock code that huawai gave me originally. I have no idea how to get it again, to try to re-lock/unlock the bootloader.
Back then when I first rooted my phone, I made a back up, so I tried to restore that back up. It failed, first with "cannot wipe the cust partition". Then I tried to restore without restoring the cust partition, and I got "extracttarfork() process ended with error 255" while the system was restoring.
After that, the phone wouldn't boot into android anymore. It would be stuck at the unlocked bootloader warning message and then reboot after a few minutes.
So, lastly, I tried to install the unofficial lineageOS port from here : https://forum.xda-developers.com/honor-5c/development/rom-lineageos-14-1-honor-5c-t3713911 with my twrp.
The installation went well, but the phone is stuck while first booting in lineageOS (I let it overnight, restarted it, re-installed it, tried with the first release, nothing).
TL;DR: My phone isn't booting and I can't flash any new recovery.
Please, help me to get my phone working again
Give me the
old build number on emui
Update build you received..
Twrp working?
Fastboot?
Erecovery?
I got access to erecovery, even if the "download latest version and recovery" doesn't work. (erecovery connects to wifi, and the first thing it tries to check/download fails)
I can boot into fastboot but can't flash recovery from there because of the command not allowed problem.
I can boot into twrp, but the back up I tried to restore and the lineageos rom I tried to install both failed, so maybe the twrp has a problem?
I'm sorry I'm not sure about the build number, I'm pretty sure I was on EMUI 5.0 and android 7.x, and I think I remember comparing current build number vs the update, and it was something like B350 or B351 for the current, and B355 or B375 for the update.
I've found this in my backup file 'recovery.log' ro.omni.version=6.0.1-20160703-nemo-HOMEMADE and ro.build.id=MOB30M . So, that mean that I had android 6.x when I did the backup, way back at the beginning.
I thought the update never got installed because each time the phone would reboot to complete installation, it would reboot into twrp. But I've still updated from android 6 to android 7 somehow ?
NEM-L51C432 or NEM-L51C10 ?
NEM-L51C432 and I'm sure of that ^^
Zhyrclew said:
NEM-L51C432 and I'm sure of that ^^
Click to expand...
Click to collapse
Flash this via twrp
http://update.hicloud.com:8180/TDS/...-L51_hw_eu/update_data_full_NEM-L51_hw_eu.zip
Once done, boot to twrp and flash this
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1581/g104/v82938/f1/full/update.zip
Reboot.
If you are unable to flash the 2nd link then just use the dload method to flash this. If you are not aware of dload method, link is given in my signature.
Note, this 2nd firmware will replace your twrp with stock recovery. You should boot to b350 version and it will be full stock. Reason for flashing data file first is it doesn't replace the recovery to stock but just flashes your data, settings, apps. And 2nd link is main full firmware which will replace your boot, recovery, vendor everything and should boot.
Good luck
I flashed the first one, no error.
The second one had multiple errors :
"[...]
write radio image...
32k crc checked failure
E:unknown command [errno]
update_huawai_pkg_from_ota_zip: update package from zip failed
Updater process ended with ERROR: 7
Error installing zip file '/sdcard/update.zip'
Updating partition details...
...done
"
So I tried the dload method, and the installation started and ended at 5% with this error :
"Software install failed!
Incompatibility with current version.
Please download the correct update package."
I guess it's because I couldn't tell you the exact build number, I'm sorry for not taking note of it.
If there is a way for me to get the build number despite the status of the phone, i'm ready to do it.
If not, I'm ready to try as many versions as it takes to find the good one.
PS: I've still access to the twrp, thank god ! That was my biggest fear, because I can't flash any recovery in the current state.
Zhyrclew said:
I flashed the first one, no error.
The second one had multiple errors :
"[...]
write radio image...
32k crc checked failure
E:unknown command [errno]
update_huawai_pkg_from_ota_zip: update package from zip failed
Updater process ended with ERROR: 7
Error installing zip file '/sdcard/update.zip'
Updating partition details...
...done
"
So I tried the dload method, and the installation started and ended at 5% with this error :
"Software install failed!
Incompatibility with current version.
Please download the correct update package."
I guess it's because I couldn't tell you the exact build number, I'm sorry for not taking note of it.
If there is a way for me to get the build number despite the status of the phone, i'm ready to do it.
If not, I'm ready to try as many versions as it takes to find the good one.
PS: I've still access to the twrp, thank god ! That was my biggest fear, because I can't flash any recovery in the current state.
Click to expand...
Click to collapse
You may try other higher versions like 360, 370 etc and see your luck. Twrp will be replaced only if the installation os successful for the main firmware. Its just a trial and error for you now but I am 99% sure you should be able to revive the phone via dload method
Thank you, it's reassuring. I will not give up until I test all the versions ^^
Could you help me a little bit to find other versions, please ? The only place I know where there is update packages for my phone is there : https://forum.xda-developers.com/ho...lota-upgrade-packages-models-nem-l51-t3473110 and there is only two versions.
Zhyrclew said:
Thank you, it's reassuring. I will not give up until I test all the versions ^^
Could you help me a little bit to find other versions, please ? The only place I know where there is update packages for my phone is there : https://forum.xda-developers.com/ho...lota-upgrade-packages-models-nem-l51-t3473110 and there is only two versions.
Click to expand...
Click to collapse
Firmware finder website
Wow, thank you, I downloaded the firmware finder software, it has everything.
Should I flash the firmware in two steps like you first made me, or should I just try with only the dload method with the fullOTA firmware ?
Zhyrclew said:
Wow, thank you, I downloaded the firmware finder software, it has everything.
Should I flash the firmware in two steps like you first made me, or should I just try with only the dload method with the fullOTA firmware ?
Click to expand...
Click to collapse
Check dload guide in my signature. You can follow that now. Good luck
I tried b355, b361, b375, b377, nothing changes, same error.
I noticed that I have something related to an update in my sd card AND internal storage->HwOUC->140783->( update.zip[1.32GB], update_data_full_public.zip[344MB], update_full_NEM-L51_hw_eu.zip[412MB] )
I don't know whether these files were there before I did all these attempted updates.
Could it be that my phone is not trying to install the files I put in sdcard->dload, because he finds these files in the internal memory first, and each time try to install these ?
Should I delete them, move them, unzip them in dload folder ?
Zhyrclew said:
I tried b355, b361, b375, b377, nothing changes, same error.
I noticed that I have something related to an update in my sd card AND internal storage->HwOUC->140783->( update.zip[1.32GB], update_data_full_public.zip[344MB], update_full_NEM-L51_hw_eu.zip[412MB] )
I don't know whether these files were there before I did all these attempted updates.
Could it be that my phone is not trying to install the files I put in sdcard->dload, because he finds these files in the internal memory first, and each time try to install these ?
Should I delete them, move them, unzip them in dload folder ?
Click to expand...
Click to collapse
Copy them on PC and then try dload of files you downloaded from Firmware finder website.
These are files your phone downloaded for OTA update but as you were on twrp, they never installed it amd stays there
I copied the updates my phone downloaded on PC and then deleted them both on internal storage and sd card.
Then I tried dload method with b355,b375&b377 from firmware finder, and also with the update.zip I found in the updates my phone downloaded.
Nothing worked, all of them got the error "Incompatibility with current version. Please download the correct update package."
Should I try even more firmware versions, or should I try something else ?
Btw, I noticed my phone, when connected to my PC, is labeled as huawei-P9-lite, and I don't think it was always like that, but it's probably just because the twrp-3.1.1-0-venus.img is originally for the P9 lite.
I came accross this thread, where somebody recommends to flash stuff from fastboot.
I have not tried it yet, I only tried to flash recovery from fastboot, and it is failing with the "command not allowed". But maybe I could try to flash some other things ? Any advice ?
For now, despite all my attempts to install stock OTA via dload method, the phone is still trying to boot into lineageOS, and failing.
I came across the "current" firmware version with a check with DC-unlocker : "NEM-L51C432B120"
So I downloaded full OTA firmware b120 on firmware finder software, and the dload method worked !
The installation went well, and after a few minutes of the first boot, I got into phone configuration.
I have one last problem, though : the phone configuration is looping.
There is only 4 languages to choose, so I have to choose english(US), then there is a weird list of countries, none in the EU, where I feel i have to choose united states, then after some steps I have to register to huawei ID thing.
If I try to skip it, it loops to the language selection.
If I try to log in to my original account, it says "device not supported for your location" and then loops to languages. (my original account is in french/France)
If I try to create a new account with new address mail, it works but then at the end says again that "device not supported for your location" and then loops to languages.
I tried with other countries it still loops.
The other languages seems to be Chinese and Japanese, but the configuration is looping too if I choose them.
I tried with/without sim, with/without wifi connected...
Dload the next firmware now and see if it works. Then set the phone
I downloaded and installed with dload method (by removing sd card and copying directly on it the files, because I don't know how to have access to the phone internal & external memory now) the next firmware (b130 version)
The phone booted, it launched a "system optimization" that was a few minutes long, and then the EMUI configuration poped up and looped through language selection, region(country), wifi connection (successful), terms and conditions, and WLAN+(switch between wlan and mobile data automatically).
I feel like the phone is working, the notification led is even blinking when I receive sms, but I have access to nothing because of this damned configuration.
Note: the connection to huawei ID isn't prompted again in the loop once I log in, from the original or the new account. In order to be prompted again to log in to the huawei ID, I have to go to erecovery and reset to factory the phone.
I need assistance as the title says. First up my bootloader is not unlockable, (believe me I've tried) and here is my situation. I cannot flash the next OTA, because of failed error in recovery upon trying to install. There is no full firmware to reflash the device, only an OTA that I obtained (and yes it is completely for my phone model) (XT1925DL). I would sideload the OTA or apply it from sdcard in the recovery, however the device is not detected on Windows via adb or on linux, after hitting the sideload zip option, and Sdcard cannot mount. I get (sdcard failed to mount, E: installation aborted in recovery). If someone knows an option to maybe allow me to use the OTA file to repatch the system, without having to resort to the recovery mode, or adb sideload option, it would be appreciated if you could help.
hydroman202 said:
I need assistance as the title says. First up my bootloader is not unlockable, (believe me I've tried) and here is my situation. I cannot flash the next OTA, because of failed error in recovery upon trying to install. There is no full firmware to reflash the device, only an OTA that I obtained (and yes it is completely for my phone model) (XT1925DL). I would sideload the OTA or apply it from sdcard in the recovery, however the device is not detected on Windows via adb or on linux, after hitting the sideload zip option, and Sdcard cannot mount. I get (sdcard failed to mount, E: installation aborted in recovery). If someone knows an option to maybe allow me to use the OTA file to repatch the system, without having to resort to the recovery mode, or adb sideload option, it would be appreciated if you could help.
Click to expand...
Click to collapse
Is it a TracFone? You're probably going to have to flash in Fastboot.
Download the most recent firmware here:
https://mirrors.lolinet.com/firmware/moto/ali/official/TRAC/
And use this guide to flash:
https://forum.xda-developers.com/moto-g6/how-to/guide-faster-updated-guide-to-root-t3914228
Ragarianok said:
Is it a TracFone? You're probably going to have to flash in Fastboot.
Download the most recent firmware here:
https://mirrors.lolinet.com/firmware/moto/ali/official/TRAC/
And use this guide to flash:
https://forum.xda-developers.com/moto-g6/how-to/guide-faster-updated-guide-to-root-t3914228
Click to expand...
Click to collapse
I appreciate the response. Unfortunately that site is not up to date with the TracFone firmware. The latest official one I have. And I can't flash it unfortunately because I'm on a newer firmware and it throws security downgrade errors when I try. If I could figure out how to get recovery mode to show up on my pc I would be ok.... Then I would be able to apply the OTA I need for the next one to complete successfully.
hydroman202 said:
I appreciate the response. Unfortunately that site is not up to date with the TracFone firmware. The latest official one I have. And I can't flash it unfortunately because I'm on a newer firmware and it throws security downgrade errors when I try. If I could figure out how to get recovery mode to show up on my pc I would be ok.... Then I would be able to apply the OTA I need for the next one to complete successfully.
Click to expand...
Click to collapse
Have you tried to run those Fastboot commands without:
Code:
[I]fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img[/I]
Should work if you exclude those two; that's what I did to downgrade from Pie back to Oreo.
You could also try Lenovo Moto Smart Assistant.
I just realized that I totally misread your original post and, man, I feel like a total dummy.
Is the OTA currently on the root of your phone's internal storage?
If it's an actual update.zip file and it's in the root of your internal storage, you could try going into Settings/Apps & notifications/Apps info (tap the down arrow and select Show system)/Moto Update Services and make sure that Storage permission is toggled on. After that, try to perform an update.
I had a similar error when trying to sideload with ABD and update from SD in recovery, but it turned out that I was trying to update using full firmware.
Can you link the update file you have?
Ragarianok said:
I just realized that I totally misread your original post and, man, I feel like a total dummy.
Is the OTA currently on the root of your phone's internal storage?
If it's an actual update.zip file and it's in the root of your internal storage, you could try going into Settings/Apps & notifications/Apps info (tap the down arrow and select Show system)/Moto Update Services and make sure that Storage permission is toggled on. After that, try to perform an update.
I had a similar error when trying to sideload with ABD and update from SD in recovery, but it turned out that I was trying to update using full firmware.
Can you link the update file you have?
Click to expand...
Click to collapse
Unfortunately I cannot not link it but the file size of the ota is roughly 1.47 GB. And the ota was a upgrade to pie. I'm still on that one. Needing to reflash it so I can correct a partition issue. That's preventing the next ota from succeeding. The reason the next one doesn't succeed is because it checks the modem partition and it unfortunately fails to verify it because I accidentally flashed the wrong one. The ota should patch the modem in the device now I'm thinking because the modem that is currently on the device is the one before the ota arrived. All other partitions are the ones meant for the current firmware.
hydroman202 said:
Unfortunately I cannot not link it but the file size of the ota is roughly 1.47 GB. And the ota was a upgrade to pie. I'm still on that one. Needing to reflash it so I can correct a partition issue. That's preventing the next ota from succeeding. The reason the next one doesn't succeed is because it checks the modem partition and it unfortunately fails to verify it because I accidentally flashed the wrong one. The ota should patch the modem in the device now I'm thinking because the modem that is currently on the device is the one before the ota arrived. All other partitions are the ones meant for the current firmware.
Click to expand...
Click to collapse
Hm.
You could try to use the Lenovo Moto Smart Assistant. It has a Rescue option that returns the phone to stock firmware. It also has an Upgrade option; I've tried it but there aren't any updates for my phone. You could Rescuing and then Upgrading. Or you could Rescue and then try the OTA again.
The only downside is that everything on your phone's internal storage will be erased.