So guys, here I am, after hours of desperated tentatives and giving up on hope. Today I manually applied an OTA file to update my system to v4.1.2, and it succeeded. Everything worked fine, I restored my protected root with Voodoo OTA RootKeeper, reinstalled Boot Menu and backed everything up.
So I started playing with it and modified some system files. Now I got into a bootloop and somehow it seems that my system partition has been formated, cause I lost access to Boot Menu. I can acess stock recovery, but cannot apply the OTA file again cause I deleted a system *.apk and the asserting fails, so the update cannot be applied. I tried to modify the patching files in the OTA *.zip file, but it also fails, probably due to signature or integrity checking.
My phone already got into low battery status, so I'll spend the rest of the night trying to charge it, but I need help figuring out how to restore my system. I think I have left two possibilites:
1. Restoring system partition from a v4.0.4 fasboot file using moto-fastboot commands - I know cdt.bin was updated to a higher version so I can't flash a lower version, but perhaps I can grab the cdt.bin_signed from the OTA file to replace the one within the fastboot file, or something like this, so I can flash the package. It doesn't need to boot, I just need to restore the system partition so I can apply the OTA file again to get a working v4.1.2 system.
2. Erasing my cid. Some weeks ago I made a backup of my cid. Perhaps I can erase it through fastboot so I can flash a fastboot file for v4.1.2, cause here in LATAM region we currently only have an OTA avaliable. That's my last option, cause I'm assuming I'll no longer be able to have root access for now, so I won't be able to install Boot Menu. Handling a system without cid this way might get painful... But at least it's an option, it may work.
Any help would be really appreciated. Right now I'm trying to fastboot flash system system_signed, but it's failing, due to low battery and something related to preflash validation failure, which I can't exactly tell the reason. The same happened to fastboot flash boot. In the other hand, fastboot flash preinstall preinstall and fastboot flash recovery recovery_signed worked fine. But I'm kinda lost here...
Thanks in advance.
Here's what you need to do:
You need the system_signed out of the necessary Latam ICS Fastboot to flash this Leak.
Do it similar to this Thread
http://forum.xda-developers.com/showthread.php?p=39247094
Your Boot. img should still be on Latam JB. If it's damaged, someone who's running the Latam JB with Root & BMM installed should backup his Boot. img and upload it for you.
So:
Fastboot the Latam ICS system_signed
Fastboot the Latam JB Boot. img (if needed)
wipe Data / Cache & apply the OTA in the Recovery again.
To charge your Phone, try to turn it off > connect your Wall charger > Boot in AP and let it sit there while still connected to your Wall Charger for about an hour. If you got luck it will charge.
Gesendet von meinem XT890 mit Tapatalk 2
---------- Post added at 06:52 AM ---------- Previous post was at 06:46 AM ----------
BTW: Use the eternity project Moto - fastboot to flash the system_signed, when you fixed your Battery!
Gesendet von meinem XT890 mit Tapatalk 2
HSD-Pilot said:
Here's what you need to do:
You need the system_signed out of the necessary Latam ICS Fastboot to flash this Leak.
Do it similar to this Thread
http://forum.xda-developers.com/showthread.php?p=39247094
Your Boot. img should still be on Latam JB. If it's damaged, someone who's running the Latam JB with Root & BMM installed should backup his Boot. img and upload it for you.
So:
Fastboot the Latam ICS system_signed
Fastboot the Latam JB Boot. img (if needed)
wipe Data / Cache & apply the OTA in the Recovery again.
To charge your Phone, try to turn it off > connect your Wall charger > Boot in AP and let it sit there while still connected to your Wall Charger for about an hour. If you got luck it will charge.
Gesendet von meinem XT890 mit Tapatalk 2
---------- Post added at 06:52 AM ---------- Previous post was at 06:46 AM ----------
BTW: Use the eternity project Moto - fastboot to flash the system_signed, when you fixed your Battery!
Gesendet von meinem XT890 mit Tapatalk 2
Click to expand...
Click to collapse
I will never be able to thank you enough! You saved my phone. It took a whole day to charge it through the universal charger, but now I just flashed everything as you described and flashing the update file within stock recovery worked fine. Now my phone works perfectly. Too bad I lost root and there's no root procedure working on LATAM update yet, but at least I have a phone and let's hope a root method will pop up soon.
I took the script tool you posted earlier and replaced the files with the ones suitable for LATAM region phones so I could use it myself. As it finally worked, would be okay if I uploaded it as a bundle so others around me can use it if they need to? Of course all credits will be given to you.
Thanks in advance.
Ricardo Gonçalves.
Sure, this will help other Guys, like him
http://forum.xda-developers.com/showthread.php?p=40266883
Gesendet von meinem XT890 mit Tapatalk 2
ricardofago said:
I will never be able to thank you enough! You saved my phone. It took a whole day to charge it through the universal charger, but now I just flashed everything as you described and flashing the update file within stock recovery worked fine. Now my phone works perfectly. Too bad I lost root and there's no root procedure working on LATAM update yet, but at least I have a phone and let's hope a root method will pop up soon.
I took the script tool you posted earlier and replaced the files with the ones suitable for LATAM region phones so I could use it myself. As it finally worked, would be okay if I uploaded it as a bundle so others around me can use it if they need to? Of course all credits will be given to you.
Thanks in advance.
Ricardo Gonçalves.
Click to expand...
Click to collapse
friend what were the steps you took? I can send the files you flasheaste your phone, I agredeceria quite as no match for any side and the Latam JB System_signed Boot. img! and my cell takes days in disrepair, you help me a lot if you would send me those files
Esto.Vir said:
friend what were the steps you took? I can send the files you flasheaste your phone, I agredeceria quite as no match for any side and the Latam JB System_signed Boot. img! and my cell takes days in disrepair, you help me a lot if you would send me those files
Click to expand...
Click to collapse
Connect your phone to your PC in AP Fastboot mode and run the unbrick.bat from this package. It will flash the v4.0.4 system and v4.1.2 boot (this requires a LATAM device). Then restart your phone into stock recovery and you'll be able to apply again the update file for v4.1.2 that's supposed to be on your external microSD card (a factory reset and a wipe cache might be appropriated before doing so). When it finishes, reboot and your phone should boot fine, but you will lose all user data and root access.
ricardofago said:
Connect your phone to your PC in AP Fastboot mode and run the unbrick.bat from this package. It will flash the v4.0.4 system and v4.1.2 boot (this requires a LATAM device). Then restart your phone into stock recovery and you'll be able to apply again the update file for v4.1.2 that's supposed to be on your external microSD card (a factory reset and a wipe cache might be appropriated before doing so). When it finishes, reboot and your phone should boot fine, but you will lose all user data and root access.
Click to expand...
Click to collapse
thank you very much friend, I realize all the procedure correctly but when I enter the stock recovery restarts select it, as if there is recovery my phone.
You select Recovery with Vol. up? Don't use Power, this will just restart your Device.
When the Android is shown, hold Vol. down and press Vol. up to enter the Recovery.
Gesendet von meinem XT890
HSD-Pilot said:
You select Recovery with Vol. up? Don't use Power, this will just restart your Device.
When the Android is shown, hold Vol. down and press Vol. up to enter the Recovery.
Gesendet von meinem XT890
Click to expand...
Click to collapse
of how it will restart the phone, I get only the Motorola logo and when I try to enter recovery restarts: Crying:: Crying:: Crying:
Try to fastboot the ICS Recovery back
fastboot flash recovery recovery_signed
Sent from my XT890 using Tapatalk 4 Beta 2
HSD-Pilot said:
Try to fastboot the ICS Recovery back
fastboot flash recovery recovery_signed
Sent from my XT890 using Tapatalk 4 Beta 2
Click to expand...
Click to collapse
lo realize en varias ocaciones y flashea bien , pero al momento de reiniciar el celular muestra el primer logo de motorola dual core y se reinicia , puedo entrar solamente a las opciones de flash mode , pero al momento de seleccionar recovery se reinicia el celular : Crying:: Crying:: Crying:: Crying:: Crying:: Crying:
I did as u said but. On boot i says infopreflash validitation failed........pls help moto razr xt910k
Related
I try to restore my phone from this thread http://forum.xda-developers.com/showthread.php?p=26039594
but I got failure after trying the T-mobile ICS update file.
It comes up like this on screen:
" error in /tmp/sideload/package.zip
(Status 7)"
I have many ways try to wipe and restore data before and after the update file from sd card.
bootloader/ kernel is 0A.6C one screen
I have try different ways for 6 hours with no luck, grrrrr
My phone is now bricked, maybe i must sendt him to rep...
Helpfor a possible solution will good. Thanks
Sorry for my bad english
Edit: I was on T-Mobile ICS before I try to flash the new ICS EU
TheMask1 said:
Thank, thank you
I'm back on stock ICS T-mobile again
I will try too go for ICs EU version later.
Click to expand...
Click to collapse
What have you done after that?
Gesendet von meinem XT910
HSD-Pilot said:
What have you done after that?
Gesendet von meinem XT910
Click to expand...
Click to collapse
In this morning I try to flash the new ICS EU again.
I Fastboot flash the boot_ne.img and ffastboot flash the system.img.
But got failure: error in /tmp/sideload/package.zip
(Status 7) when I try to update ICS from sd card.
After that I have try to restore too T-mobile version with no luck
Just in mind > You got 2 Update zips on your SD now. You tried the right one for the new Leak?
Gesendet von meinem XT910
TheMask1 said:
I try to restore my phone from this thread http://forum.xda-developers.com/showthread.php?p=26039594
but I got failure after trying the T-mobile ICS update file.
It comes up like this on screen:
" error in /tmp/sideload/package.zip
(Status 7)"
I have many ways try to wipe and restore data before and after the update file from sd card.
bootloader/ kernel is 0A.6C one screen
I have try different ways for 6 hours with no luck, grrrrr
My phone is now bricked, maybe i must sendt him to rep...
Helpfor a possible solution will good. Thanks
Sorry for my bad english
Edit: I was on T-Mobile ICS before I try to flash the new ICS EU
Click to expand...
Click to collapse
You must wipe cache, then install the zip again. Of course you must flash the new leak, not T-Mo.
Edit: Otherwise you could extract the t-Mo ICS zip to your harddrive. The pick the cdt.bin_signed, devtree_signed, and all mbm-files and flash them via moto-fastboot. Then flash the t-mo 2.3.6 system_signed again and reboot into recovery, perform a full wipe and cache wipe. Then apply the ICS update.zip.
Or if you want to try the newest leak, just do the same steps using the 2.3.6 26 fastboot and the new ICS zip.
dtrail1 said:
You must wipe cache, then install the zip again. Of course you must flash the new leak, not T-Mo.
Click to expand...
Click to collapse
So this is a way to go to a newer ICS leak from the T-Mo leak? Just flash the zip from recovery after wiping /cache?
stangri said:
So this is a way to go to a newer ICS leak from the T-Mo leak? Just flash the zip from recovery after wiping /cache?
Click to expand...
Click to collapse
Read my edit above. But in normal case you must not wipe anything, just flash the system_signed from the 26 fastboot and then apply the update zip from the new leak.
Edit: Also the boot_new.img has to be flashed before applying the update.
Here it is: http://www.mediafire.com/?rh4flyvuo5lej9w
HSD-Pilot said:
Just in mind > You got 2 Update zips on your SD now. You tried the right one for the new Leak?
Gesendet von meinem XT910
Click to expand...
Click to collapse
Yes I know about that , and have format the SD card i tried again
Hey mate, I've tried by myself now. I got the same error like you described. Then I did directly a cache wipe and it succeeded!
dtrail1 said:
Hey mate, I've tried by myself now. I got the same error like you described. Then I did directly a cache wipe and it succeeded!
Click to expand...
Click to collapse
I try again and again here, Must have a look at the battery status in between. Charge it from exit fastboot mode.
dtrail1 said:
Hey mate, I've tried by myself now. I got the same error like you described. Then I did directly a cache wipe and it succeeded!
Click to expand...
Click to collapse
Hey mate. Have you lost the root permissions? Could you create a step by step?
I tried also to flash the boot_new.img with sdk tools.
Commande: fastboot flash boot boot_new.img
But got this failurebootloader) Preflash validation failure
Failed (remote: )
Something is wrong but what???
Put the etrj fastboot on your Desktop and use the Windows Terminal (cmd)
Works flawless for me...
Gesendet von meinem XT910
TheMask1 said:
I tried also to flash the boot_new.img with sdk tools.
Commande: fastboot flash boot boot_new.img
But got this failurebootloader) Preflash validation failure
Failed (remote: )
Something is wrong but what???
Click to expand...
Click to collapse
Normal fastboot won't work. Use the moto-fastboot or the eprj-mfastboot.
---------- Post added at 08:22 PM ---------- Previous post was at 08:20 PM ----------
SoulGraphicsBrand said:
Hey mate. Have you lost the root permissions? Could you create a step by step?
Click to expand...
Click to collapse
There is already a step-by-step in the other thread wehere you can get the files. And I had no root before so there wasn't anything to loose If you running on rooted leak, you shouldn't flash this one. Search the forums, there is one guy who successful flshed the ICS nandroid backup to his device. This will persist your root.
dtrail1 said:
Read my edit above. But in normal case you must not wipe anything, just flash the system_signed from the 26 fastboot and then apply the update zip from the new leak.
Edit: Also the boot_new.img has to be flashed before applying the update.
Here it is: http://www.mediafire.com/?rh4flyvuo5lej9w
Click to expand...
Click to collapse
Thanks, got the boot_new.img you've linked, but just to be safe (and because I'm confused by the OTA numbering) can you please post a link to the newest OTA I can grab the system_signed from and then use it for the update from recovery?
Also, should I temp unroot and then re-root with the rootkeeper as with the T-mo 4.0.4 OTA update? Is there other way to keep root?
BTW, I've seen you refer to the .26 fastboot (and saying it doesn't have the best radio for Germany where I am at the moment), but the latest leak I've seen mentioned in the other thread is Blur_Version.672.180.17.XT910.Retail.en.EU (Tue May 22 17:20:36 CST 2012). Is it the same build as .26?
Sorry, hit the Thanks Button in Tapatalk
The Radio seems to be better on this ICS. I was on 651.167.26 for an while and the Phone quality was not really good. Tested it today on the Leak and all seems to be fine now.
you need the system_signed from the 651.167.26 to flash the new Leak.
Flash the boot_new.img & the system_signed in AP Fastboot and after that boot in Moto Recovery and flash the Leak.
http://www.handy-faq.de/forum/motorola_razr_forum/249903-motorola_ics_leak_retail_22_05_2012_a.html
Maybe it helps..
YES YES I finished with flashing the new OTA update eu ICS: Blur_Version.651.167.26.XT910.Retail.en.EU
System version 672.180.17.XT910 on my phone.
This is what i do to solved my flashing problems:
1. Used Andriod SDK tool to flash boot_new.img
Command: fastboot flash boot boot_new.img
2. Flashed the SPDREM_U_01.6.5.1-167_SPU-15-M2-3_SIGNEuropeAustraliaEMEA_USASPDRRTGB_HWp2b_Service1FF_fastboot
with Kholks:
EternityProject's RSD Alternative for flashing OFFICIAL Motorola ROMs
Was some failure during the flashing, but system_signed was flashed. .
3. Then I try to install OTA update Blur_Version.651.167.26.XT910.Retail.en.EU directly but failed.
- Then I erased cashe, tried agian, but failed.
- At last I Wipe data and restore then install the update with succes.
I'M so Happy now.
Big big Thanks to HSD-Pilot, DTrail1, Whirleyes, and Spryte
It's a top forum, thanks to all.
Regards
Jan
do you have root?
pty.ltd said:
do you have root?
Click to expand...
Click to collapse
Not now, I flash and reflash so many times before I was up and go, so lost my root
But I'm happy with the newest ICS eu, so I can wait for a root metode later
hi, im trying to update my razr with 651.167.22.en.FR update, but i cant, i made that steps:
1º install via OTA (fail)
2º install via USB (fail)
3º get the file c:\programdata\motorola\sue\firmware, copy in SD and execute (fail)
in the log, the error is that i dont have the file arcvideoeditorlite.apk in \system\app, i was delete this app, but with root explorer i put it in \system\app with the same permissions and with systemcleanup i cahnger to system app, can you help me?
sorry about my english, im spanish
thanks
Flash it via fastboot. Done.
ok, can you say me how can i make it?
You have to download the right fastboot file (651.167.22), RSD lite 5.7 and if needed Motohelper USB drivers. Then unzip the fastboot file, run RSD and select the xml-file found in the unzipped fastboot folder. Plug your device to the computer via USB cable, click flash button in RSD, tge device will reboot into fastboot AP automatically and gets flashed. when finished it will reboot itself. Done. If something is not clear, search in the forums or google for RSD to get better instructions.
Gesendet von meinem XT910 mit Tapatalk 2
thank you, but i preffer to use the OTA option, you know what can i do for repair my phone?
in the case you said, i preffer to download a 4.0 image and have ICS in my phone
urrakis said:
thank you, but i preffer to use the OTA option, you know what can i do for repair my phone?
in the case you said, i preffer to download a 4.0 image and have ICS in my phone
Click to expand...
Click to collapse
To install an OTA you need to be on a specific version which vary with each OTA.
And if you removed bloatware of freeze the ota will failed. that's why dtrail told you to fastboot you can be sure it will work.
And if you want ICS you have to fastboot 651.167.26 then apply the right OTA. but be ware you can't roll back to Gingerbread.
ahm ok, thank you very much to you and dtrail1
i will make this, i hope i will have luck
I am in bootloop and cannot power off phone. I have tried to fastboot recovery, boot, cust, cache, system, userdata from B121. Still impossible to power off the phone.
Did you try to go back to B100? Your file could be corrupted :/
Envoyé de mon PLK-L01 en utilisant Tapatalk
Sideness said:
Did you try to go back to B100? Your file could be corrupted :/
Envoyé de mon PLK-L01 en utilisant Tapatalk
Click to expand...
Click to collapse
No, not yet. I cannot enter Recovery. I can enter in Bootloader only. There is no way to go into Recovery from Bootloader without powering off the phone.
If you can access the bootloader, you can repair your phone.
Try the step 5 from this post :
http://forum.xda-developers.com/honor-7/general/guide-beginners-how-to-root-update-fix-t3255452
You must have already tried with B121. But try with other versions like B100. Be careful to flash everything (System, recovery, cust, cache, ...).
If it stlll doesn't work, I don't have anything left, but someone else might ! Good luck
Sideness said:
If you can access the bootloader, you can repair your phone.
Try the step 5 from this post :
http://forum.xda-developers.com/honor-7/general/guide-beginners-how-to-root-update-fix-t3255452
You must have already tried with B121. But try with other versions like B100. Be careful to flash everything (System, recovery, cust, cache, ...).
If it stlll doesn't work, I don't have anything left, but someone else might ! Good luck
Click to expand...
Click to collapse
I am aware of the thread you mention, already tried everything in there. I left the phone overnight in Bootloader to drain battery, which happened, but after connecting charger bootloop remains, I still cannot power off the phone and reach Recovery. The only partition I did not rewrite is /data.
How to do it from fastboot? If I rewrite /data, does it rewrite also phone /sdcard?
UPDATE: getting tools to open phone and remove battery, there is no other way to brake bootloop.
flash TWRP and there is a poweroff option in [Reboot]
sminki said:
flash TWRP and there is a poweroff option in [Reboot]
Click to expand...
Click to collapse
did not work, I could not go to TWRP. As I wrote in separate thread, now I am in B130 with B170 BOOT and RECOVERY. I have tried to reflash TWRP, but is no coming up.
I also do not like small space on SDCARD, total available (root / plus local /sdcard) is only 3GB
were you on B140 when you applied the 170? was it the french B170 or the Indian B170? (different phones)
170 patches those "blackbox" partitons, which could cause earlier kernels to suffer
I haven't moved from 140. people (in general) are just flashing anything posted it seems and for no good reason...
B121 works with B170 bootloader/recovery, but not with B121 bootloader/recovery
at http://www.android-hilfe.de/thema/honor-7-downgrade-von-b170-auf-b121-loesungsfindung.742330/ we discussed about quite the same problem.
the solution can be found in post #20.
if you flash b121 system and b170 boot/recovery your system should boot and you should be able to enter recovery by power & vol+ as well as force upgrade by power & vol+/-
you have to put the update.app from the 313>121 downgrade packag on your sd-card or internal memory (dload folder) and start the update process. the update will fail at 95%, but the system will boot and the build-number is B300.
after that you have to copy the update.app from the full b121 to your sd-card/internal memory and start the update process. update will reboot at 100% and your phone is back to stock b121
sminki said:
were you on B140 when you applied the 170? was it the french B170 or the Indian B170? (different phones)
170 patches those "blackbox" partitons, which could cause earlier kernels to suffer
I haven't moved from 140. people (in general) are just flashing anything posted it seems and for no good reason...
Click to expand...
Click to collapse
Exactly, I was on B140 and applied French B170, but forgot to unroot, I have returned just the recovery, and then the hell on earth started
bamserl said:
B121 works with B170 bootloader/recovery, but not with B121 bootloader/recovery
at http://www.android-hilfe.de/thema/honor-7-downgrade-von-b170-auf-b121-loesungsfindung.742330/ we discussed about quite the same problem.
the solution can be found in post #20.
if you flash b121 system and b170 boot/recovery your system should boot and you should be able to enter recovery by power & vol+ as well as force upgrade by power & vol+/-
you have to put the update.app from the 313>121 downgrade packag on your sd-card or internal memory (dload folder) and start the update process. the update will fail at 95%, but the system will boot and the build-number is B300.
after that you have to copy the update.app from the full b121 to your sd-card/internal memory and start the update process. update will reboot at 100% and your phone is back to stock b121
Click to expand...
Click to collapse
My recovery story was like this:
first B130 from bootloader (all partitions: boot, system, recovery, cust, cache, userdata), disconnecting USB and manual reboot to bootloader and then fastboot partitions BOOT and RECOVERY from B170; reboot and I was out of bootloop; however the root and internal SDCARD was only 3 GB instead of normal 10 GB, so I have updated complete UPDATE.APP (B122) from EMUI placing it in external SDCARD in /dload; then factory reset from stock recovery and the I have now 10 GB total space;
I did not need the B313, however I have noticed that boot and recovery partitions from B313 stopped the short-period bootloop, it just got stuck at boot logo; in this config it allowed me to go to stock recovery GUI and once left there to discharge the battery, the phone finally powered off itself and once reconnected to charger it did not start, it has started to recharge battery
problem
Hi, I have the same problem!
Wholen said:
Hi, I have the same problem!
Click to expand...
Click to collapse
Then try the same cure: fastboot 121 partitions (see above), then fastboot BOOT and RECOVERY from B170 and you are out of booloop.
the problem is , no fastboot no recovery. I tried to press the 2 volume button + power , and the quick button in any combination, but nothing happens.
---------- Post added at 09:17 PM ---------- Previous post was at 09:16 PM ----------
and i updated from b140--- to b313
Hi there, same problem here as FearFac, exactly the same
My PLK_L01 operate only in fastboot mode, and B170 (boot + recovery) and B121 (system, cust) did not repair anything, still cant go in recovery mode :/
Wholen said:
the problem is , no fastboot no recovery. I tried to press the 2 volume button + power , and the quick button in any combination, but nothing happens.
---------- Post added at 09:17 PM ---------- Previous post was at 09:16 PM ----------
and i updated from b140--- to b313
Click to expand...
Click to collapse
you can enter fb by only pressing vol- and connecting your phone to your pc.
the method by flashing system 121 und boot/recovery 170 was found suitable for peple who tried to upgrade from 121/140 > 170.
if you have tried to upgrade from 140>313, it could be worth trying to use boot/recovery from 313 instead of 170.
the 3gb space is a result from flashing userdata.img by fastboot. you also can resolve this problem with a factory reset.
Finally, after battery has left its last % of charge, phone has power off and I was able to boot in Update mode and it works as described !
Now I booted in B121 and it works !
FabienZE said:
Finally, after battery has left its last % of charge, phone has power off and I was able to boot in Update mode and it works as described !
Now I booted in B121 and it works !
Click to expand...
Click to collapse
Great, you can smile again.
FearFac said:
Great, you can smile again.
Click to expand...
Click to collapse
Yes I do ! But I can't update to B140 for now, it simply fails. Tomorrow, I will reflash complete B121 update ?
FabienZE said:
Yes I do ! But I can't update to B140 for now, it simply fails. Tomorrow, I will reflash complete B121 update
Click to expand...
Click to collapse
Yes, complete reflash is a must, including factory reset from RECOVERY, this will delete USERDATA including local SDCARD
I really need help on this issue.
It got into a bootloop and the only thing available is fastboot. No recovery or erecovery. This happened when I was at B170 with unlock bootloader and un-rooted on my L01.
Since this, I´ve flashed
fastboot flash boot BOOT.img
fastboot flash system SYSTEM.img
fastboot flash recovery RECOVERY.img
fastboot flash cache CACHE.img
fastboot flash cust CUST.img
using Update.app from B100, B121 and B130. No erros with any of these.
I´ve read all the threads about similar problems and used other solutions like:
Change the order of fastboot flash;
Use Multitool-unbrick
Flash TWRP and oficial recovery with multitool but none worked
Remove sim tray
Connect fastboot to Hisuite, but the PC detects the phone, as it plays a sound, but the Hisuite says no phone is connected
Right now my phone is on at fastboot, because I cant even turn it off. It just restarts, vibes, shows Honor screen and restarts after a few seconds.
I really appreciate any help on this.
Hi!
I had a similar problem once. This was due to a bad recovery and boot partition flashed. You need to flash recovery.img and boot.img extracted from the update.zip from B170 (or B180?) update file.
In my case I was only able to access fastboot but not forced update with update.app (by holding VOL + and -) because the recovery wasn't good. If it's also your case, my solution above must be it.
Envoyé de mon PLK-L01 en utilisant Tapatalk
Sideness said:
Hi!
I had a similar problem once. This was due to a bad recovery and boot partition flashed. You need to flash recovery.img and boot.img extracted from the update.zip from B170 (or B180?) update file.
In my case I was only able to access fastboot but not forced update with update.app (by holding VOL + and -) because the recovery wasn't good. If it's also your case, my solution above must be it.
Envoyé de mon PLK-L01 en utilisant Tapatalk
Click to expand...
Click to collapse
Thanks a million, it worked oddly since I flash, like you said, recovery and boot from B170, but firmware version is B121.
Now it wont manual update to B313 or B121 or even have any OTA...
Is it because I have a unlocked bootloader ?
Edit: made a restore factory defaults with clean internal memory and reflashed B121 through update (local) menu. It now acknowledges B170 OTA. Urrraayyyy
Next step: re-lock bootloader?
Edit: Bootloader relocked using this post.
zinko_pt said:
Thanks a million, it worked oddly since I flash, like you said, recovery and boot from B170, but firmware version is B121.
Now it wont manual update to B313 or B121 or even have any OTA...
Is it because I have a unlocked bootloader ?
Edit: made a restore factory defaults with clean internal memory and reflashed B121 through update (local) menu. It now acknowledges B170 OTA. Urrraayyyy
Next step: re-lock bootloader?
Edit: Bootloader relocked using this post.
Click to expand...
Click to collapse
Hi !
A few months ago I unlocked my bootloader in order to root the phone. Last month I decided that I no longer needed root, so I flashed stock recovery and stock ROM. I updated yesterday to B180 without problem. You don't need to re-lock bootloader. It can stay unlocked without affecting the phone behaviour.
Sideness said:
Hi!
I had a similar problem once. This was due to a bad recovery and boot partition flashed. You need to flash recovery.img and boot.img extracted from the update.zip from B170 (or B180?) update file.
In my case I was only able to access fastboot but not forced update with update.app (by holding VOL + and -) because the recovery wasn't good. If it's also your case, my solution above must be it.
Envoyé de mon PLK-L01 en utilisant Tapatalk
Click to expand...
Click to collapse
Hi man, can you explain it more clearly pls? Having same problem even masters keeping silent,3 of them couldn't fix it.
---------- Post added at 06:44 AM ---------- Previous post was at 06:28 AM ----------
zinko_pt said:
Thanks a million, it worked oddly since I flash, like you said, recovery and boot from B170, but firmware version is B121.
Now it wont manual update to B313 or B121 or even have any OTA...
Is it because I have a unlocked bootloader ?
Edit: made a restore factory defaults with clean internal memory and reflashed B121 through update (local) menu. It now acknowledges B170 OTA. Urrraayyyy
Next step: re-lock bootloader?
Edit: Bootloader relocked using this post.
Click to expand...
Click to collapse
Hi Zinko
It seems to me you have a great experience fixing that type of problem,please share with me as well,I have Huawei Mate 7 and it's rebooting only after trying to upgrade to Marshmallow.
As Sideness said for sure it's due to a bad recovery and boot partition flashed.In my case it's most probably "boot partition".
Sideness said:
Hi!
I had a similar problem once. This was due to a bad recovery and boot partition flashed. You need to flash recovery.img and boot.img extracted from the update.zip from B170 (or B180?) update file.
In my case I was only able to access fastboot but not forced update with update.app (by holding VOL + and -) because the recovery wasn't good. If it's also your case, my solution above must be it.
Envoyé de mon PLK-L01 en utilisant Tapatalk
Click to expand...
Click to collapse
God thank you so much, 4 days i'm struggling with my Honor and now i flash the boot and recovery from the 170 update and IT BOOTS !
Thank you so much.
Now i just had to update to 170 (i was in 121) via OTA and the updates starts and ends properly (first time in big time).
Main thing to understand is that you don't need a matching system.img, just an proper boot and recovery to flash. (if anyone is bricked to hell just like i was)
Demeth said:
God thank you so much, 4 days i'm struggling with my Honor and now i flash the boot and recovery from the 170 update and IT BOOTS !
Thank you so much.
Now i just had to update to 170 (i was in 121) via OTA and the updates starts and ends properly (first time in big time).
Main thing to understand is that you don't need a matching system.img, just an proper boot and recovery to flash. (if anyone is bricked to hell just like i was)
Click to expand...
Click to collapse
I guess if you try to update from B170 to B313 it will mess the recovery.
To fix this, it is required to re-flash the recovery from B170, AND THEN go back to B121. After that it is up to you to go through B140 and jump to B313 or follow the Lollipop path until B180.
Im stuck with the same issue. I had trwp + root installed, the 180 update came, i derooted the device, installed 313 official recovery- rebooted- and installed the update. After this the phone would not boot again.
I have tried everything, and if i choose the B170 recovery from multi tool, i come to the "Huawei software installing" but it stops at 90%.... What can i do to fix this? are there any way to flash a stock rom with TWRP?
---------- Post added at 07:41 PM ---------- Previous post was at 06:59 PM ----------
flashing recovery.img and boot.img from the update.zip from (B170 to B180) update file worked! the phone starts on version b130! but im struggeling to update the phone any further? what do do?
leholtet said:
Im stuck with the same issue. I had trwp + root installed, the 180 update came, i derooted the device, installed 313 official recovery- rebooted- and installed the update. After this the phone would not boot again.
I have tried everything, and if i choose the B170 recovery from multi tool, i come to the "Huawei software installing" but it stops at 90%.... What can i do to fix this? are there any way to flash a stock rom with TWRP?
---------- Post added at 07:41 PM ---------- Previous post was at 06:59 PM ----------
flashing recovery.img and boot.img from the update.zip from (B170 to B180) update file worked! the phone starts on version b130! but im struggeling to update the phone any further? what do do?
Click to expand...
Click to collapse
Flash a complete B121 and then go all the way untill B180. The updates will show automatically, as you will have only to choose to update.
Here is my problem,
I have a BLN-L29, now:
running on Lineage OS Beta 4
unlocked bootloader
TWRP
Now my mission is to revert back to stock EMUI Firmware.
Apparently, many of you guys refer to this thread and this thread for solution.
However, i still cant understand the steps. Especially this:
Download Update ZIP
A. Get ROM update link through hwmt.ru. Click "filelist.xml".
B. Observe "update.zip" size, choose more than 1GB file size FULL OTA from previous step. Example ALP-L29 8.0.0.115 (C636) filelist Link, all three update files and path are in the filelist.xml content.
update.zip: Change URL last "filelist.xml" to "update.zip" download file.
update_data_public.zip: Change URL last "filelist.xml" to "public/update_data_public.zip" download file, and rename it to "update_data_public.zip"
update_all_hw.zip: Change URL last "filelist.xml" to "ALP-L29_hw_spcseas/update_ALP-L29_hw_spcseas.zip" download file, and rename it to "update_all_hw.zip"
I have downloaded three zip for BLA-L29C636b139 (8.0.0.139) that contains:
update.zip
BLA-L29_hw-spcseas/update_full_BLA0L29_hw_spcseas.zip
public/ update_data_full_public.zip
I hope there are the correct one needed to restore my phone back to stock.
Can anyone guide me please?
Hi, I was at LineageOS too.
I didn't need TWRP flash to install it.
I returned to Stock without problems, so my advice is to follow the next steps, but remember, it is you who decides to do it, I only offer you a solution that should NOT make things worse.
1. Stock recovery flashes from the version you were before Lineage, NONE other recovery version.
2. You go into recovery and do a Wipe Cache, and then a Factory Reset.
3. You restart Fastboot, and Syste.img flashes the version before Lineage.
4 Restart in recovery, and Reset Factory again, restart, and you're good to go.
To find the recovery and the Systen.img you should download the version that had your phone, download it, the full version, no other, unzip it, and with Huawei update Extractor, you get those two files that I told you.
I repeat, this should work if or if I'm not responsible for anything.
And above all, make sure first that you have the OEM Unlock, and the Bootloader open
Good luck
Translated with www.DeepL.com/Translator
Enviado desde mi BLA-L29 mediante Tapatalk
rey_lagarto said:
Hi, I was at LineageOS too.
I didn't need TWRP flash to install it.
I returned to Stock without problems, so my advice is to follow the next steps, but remember, it is you who decides to do it, I only offer you a solution that should NOT make things worse.
1. Stock recovery flashes from the version you were before Lineage, NONE other recovery version.
2. You go into recovery and do a Wipe Cache, and then a Factory Reset.
3. You restart Fastboot, and Syste.img flashes the version before Lineage.
4 Restart in recovery, and Reset Factory again, restart, and you're good to go.
To find the recovery and the Systen.img you should download the version that had your phone, download it, the full version, no other, unzip it, and with Huawei update Extractor, you get those two files that I told you.
I repeat, this should work if or if I'm not responsible for anything.
And above all, make sure first that you have the OEM Unlock, and the Bootloader open
Good luck
Translated with www.DeepL.com/Translator
Enviado desde mi BLA-L29 mediante Tapatalk
Click to expand...
Click to collapse
Thank you for your reply,
This is what i do:
downloaded a FULLOTA update for my phone
extracted system.img and recovery.img from UPDATE.APP using huawei update extractor
flash recovery using this command fastboot flash recovery_ramdisk recovery.img
factory reset
flash system.img using this comman fastboot flash system system.img
factory reset (lowlevel)
now it bootlooping
babadaba said:
Thank you for your reply,
This is what i do:
downloaded a FULLOTA update for my phone
extracted system.img and recovery.img from UPDATE.APP using huawei update extractor
flash recovery using this command fastboot flash recovery_ramdisk recovery.img
factory reset
flash system.img using this comman fastboot flash system system.img
factory reset (lowlevel)
now it bootlooping
Click to expand...
Click to collapse
latest update,
after the phone stuck at bootlooping,
i "fastboot flash system" the old lineage OS system img
now my phone is still in custom ROM.
back to square 1.
babadaba said:
Thank you for your reply,
This is what i do:
downloaded a FULLOTA update for my phone
extracted system.img and recovery.img from UPDATE.APP using huawei update extractor
flash recovery using this command fastboot flash recovery_ramdisk recovery.img
factory reset
flash system.img using this comman fastboot flash system system.img
factory reset (lowlevel)
now it bootlooping
Click to expand...
Click to collapse
If, your phone logs into bootloop, logs back into recovery, an option should appear to download the latest version available to you, it installs itself.
Anyway, if you have a bootloop problem, the terminal takes you to that step by itself, that's what happened to me when I installed Xposed Framework.
In any case, the first step should have been to do a Factory reset. I hope you can work it out.
Translated with www.DeepL.com/Translator
Enviado desde mi BLA-L29 mediante Tapatalk
---------- Post added at 10:41 AM ---------- Previous post was at 10:34 AM ----------
babadaba said:
latest update,
after the phone stuck at bootlooping,
i "fastboot flash system" the old lineage OS system img
now my phone is still in custom ROM.
back to square 1.
Click to expand...
Click to collapse
Okay, I didn't read that last one. You're back at TWRP? I hope not.
You should check to see if you have any objections to entering Recovery Stock. In case of no problems, you can try a Factory Reset again, and Wipe Cache, then just flash System.img, and again Factory Reset.
Those, and NOT others, are the steps I took, and I had no problems.
Perhaps as it is a different process from your move to Custom, it must also be different to return to Stock.
Translated with www.DeepL.com/Translator
Enviado desde mi BLA-L29 mediante Tapatalk
Hey, have you made any progress?
Greetings.
Enviado desde mi BLA-L29 mediante Tapatalk