Related
Huawei recently shipped update B180.
They advised to unroot the phone first, but I have been stupid and updated with TWRP installed on the second recovery partition (e-recovery?) and the update failed.
My phone now won't boot. I can put it in fastboot/recovery mode and access TWRP, so I guess all I need is a stock ROM.
I cannot find anything useful for Honor 7 with Google, I would like a recent ROM (most recent I found is a B130).
I would also appreciate some advice on how to recover from this boot freeze.
Would flashing a stock ROM with TWRP be enough?
Thank you very much.
I'm kinda pissed since that phone is quite expensive.
You cannot flash a stock rom with TWRP.
You have to flash the stock recovery then a stock rom, using fastboot.
The more recent stock rom available is the B130, unfortunatly.
Have a look at my posts, I have done similar (although I had the normally recovery.img installed) you need to downgrade using the marshmallow downgrade ROM then to the full 121 or 130 ROM after putting the stock recovery back (for the version your phone was on before this happened I assume it was 170 if you were going to 180) once you are back on 130 you can then upgrade up to 180 through the usual process. I have done this a few times and it has been fine whilst experimenting with the device.
The current version of the phone appears to be burned in to it (I think curver.img is doing this inside the UPDATE.APP but I haven't found a way of flashing this file back to the phone to play around with downgrading without the MM downgrade ROM), this I think is what causes it to hang if it has a boot.img and recovery.img that does not match the version the phone thinks it is.
I am in the same boat with @rbuccia.
I can only access fastboot and recovery (twrp).
I also found that I must have something wrong with 3rdmodem because if i wipe form inside twrp I always get an error message on that partition.
Also I have a rom from Kangvip flashable with twrp but veven this has no effect.
I think that we cannot unbrick it without a completely and full stock rom but I think there is no one.
Any idea?
This method should work for the above, first we need to get your device to boot. The following should work... Extract UPDATE.APP from the B180 ROM and then extract boot.img and recovery.img using Huawei Update Extract. Now extract the UPDATE.APP from the full 130 ROM and extract system.img using the Huawei image extractor. Once you have them 3 files, place them in the same folder as your fastboot installation and do the following...
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
This should give you a working bootable phone, it will be a mess half 180 for Kernel etc... and the system itself will be 130 but it should boot. Then place the MM downgrade ROM into the dload folder on your SDCARD and run the update process, it will crash at 95% this is fine the phone will boot back up. Now place the UPDADTE.APP from 130 in the dload folder and run the update again, this should flash and give you a fully functioning normal system running version 130, then follow the update process to get back to 180.
The modem will get flashed as part of the 130 update package so hopefully that will resolve that issue for you as well.
james194zt said:
This method should work for the above, first we need to get your device to boot. The following should work... Extract UPDATE.APP from the B180 ROM and then extract boot.img and recovery.img using Huawei Update Extract. Now extract the UPDATE.APP from the full 130 ROM and extract system.img using the Huawei image extractor. Once you have them 3 files, place them in the same folder as your fastboot installation and do the following...
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
This should give you a working bootable phone, it will be a mess half 180 for Kernel etc... and the system itself will be 130 but it should boot. Then place the MM downgrade ROM into the dload folder on your SDCARD and run the update process, it will crash at 95% this is fine the phone will boot back up. Now place the UPDADTE.APP from 130 in the dload folder and run the update again, this should flash and give you a fully functioning normal system running version 130, then follow the update process to get back to 180.
The modem will get flashed as part of the 130 update package so hopefully that will resolve that issue for you as well.
Click to expand...
Click to collapse
Thanks for the tips, but
1. Where can i download the B180 full firmware?
2. I can't access the VOL+ VOL- POWer AKA updater mode, it just bootloops.
Thx :laugh:
Its on one of the threads at the top of General all the firmwares are there, no you don't need to do the vol+/- thing, just power power it down and then hold power up whilst plugging in to your PC. If this works the device will load up in fastboot and you should be able to flash what you need, to do the above the bootloader will need to be unlocked but you can do that from fastboot.
If your device is in a boot loop plug it in via USB to your PC and keep holding the volume up and when it reboots eventually it will go in to fastboot.
james194zt said:
Its on one of the threads at the top of General all the firmwares are there, no you don't need to do the vol+/- thing, just power power it down and then hold power up whilst plugging in to your PC. If this works the device will load up in fastboot and you should be able to flash what you need, to do the above the bootloader will need to be unlocked but you can do that from fastboot.
If your device is in a boot loop plug it in via USB to your PC and keep holding the volume up and when it reboots eventually it will go in to fastboot.
Click to expand...
Click to collapse
I must be blind, but i can only find the ota updates, not the full stock firmware :/
Thx tho, i'm starting to understand a bit better how it works and how i can fix it.
I'll just try to flash boot and recovery for B100 and B130 untill i cant make it work, for the system.app tho i can't take the B180 as i can't find it.
You need to use the system.img from B130 it is located here https://mega.nz/#!PlpXnLxD!azPTqEscNnwuSdrjpJJKO9zkyCpzAl7d6w3OpYx1se8 once you have this follow the above process and you should end up with a phone thats working and has the correctly matching firmware. Make sure you do it all though, just because it will boot with a mismatched boot loader and system.img doesn't mean you should keep it that way, it could be unstable and will cause issues with future upgrades.
james194zt said:
You need to use the system.img from B130 it is located here https://mega.nz/#!PlpXnLxD!azPTqEscNnwuSdrjpJJKO9zkyCpzAl7d6w3OpYx1se8 once you have this follow the above process and you should end up with a phone thats working and has the correctly matching firmware. Make sure you do it all though, just because it will boot with a mismatched boot loader and system.img doesn't mean you should keep it that way, it could be unstable and will cause issues with future upgrades.
Click to expand...
Click to collapse
Thx for the reply ! But that's what i said earlier, when i flash boot.img, system.img and recovery.img from the B130 update.app, the phone still bootloops.
I have access to the Huawei E-recovery if i do VOL+ POWER while the phone is plugged in the pc
I have access to the fastboot mode if i do VOL- POWER while the phone is plugged in he pc
I DON'T have access to the software mode upgrader if i do VOL+ VOL- POWER, no matter is the phone is plugged in or not
The phone still bootloops, plugged in or not.
:/
You need to flash boot.img and recovery.img from 180 and system.img from 130, sorry if that was not clear above! the boot loop is being caused because the boot.img doesn't match the version your phone thinks its on, if 180 doesn't work try the version before you upgraded i.e. 170 the system.img is just the android OS if you see HONOR glowing then you are booting system.img at that point but if it isn't glowing then you are still in the bootloader at that point so you need to sort out boot.img.
I've never been in 180, and as i said, i can't take the boot and recovery.img from the OTA update, i need a full stock firmware of B180 ! :/
Thx for the help tho.
I already tried to flash boot.img from B100 b121 and B130, and the phone still bootloops :/
http://forum.xda-developers.com/hon...dating-to-b180-fastboot-t3317249#post65420964
This fixed it!
Found this and it worked for me.
Download latest Official Full ROM from EMUI's site, HuaweiUpdateExtractor and adb / fastboot.
2. Unzip ROM and open UPDATE.APP with HuaweiUpdateExtractor.
3. Extract SYSTEM.img and RECOVERY.img (delete .header files that HuaweiUpdateExtractor generates you need only .img files) and put them in adb folder.
4. Boot in fastboot and conect to PC. (You can achieve this from TWRP to boot to bootloader, adb dosent work but fastboot will there is also key combination to get to bootloader/repair mode or what it is).
5. Open cmd.exe from adb folder and type (or copy-paste) the follow commands one by one:
Code:
fastboot devices
Code:
fastboot flash recovery RECOVERY.img
Code:
fastboot flash system SYSTEM.img
And finally where i had some trouble:
If you got no permissions try again or take usb cable off etc. Took me while to get back from same situtation. Few reboots to TWRP and to bootloader and USB replugging while in bootloader.
And for LINUX: i used split_updata.pl-master from github to extract the .APP/Firmware needed to sudo fastboot aswell.
Hiiiii guys
Please help me respected sir and other friends.
Anyone have twrp backup of stock rom ?
Because I want go back to stock rom and I have only twrp not pc please thanks in advance
Hi everyone,
I just replaced my home security panel into my old sgp311.
It is on stock 5.1.1, just rooted, with locked bootloader.
all things are just going fine and I'm finishing few very end steps, I made a wrong decision, which is install xposed without flashing zip file, I tried to copy/overwrite all the files from the ZIP to system and I thought if I simply make every files with right permission, I won't be messed up, yes I know it is not that easy.
Now I got a bootloop sgp311, I can put it into fastboot or download mode, I tried
Code:
fastboot boot twrp_various_versions.img,
hope it could boot into TWRP recovery and I can flash xposed ZIP and make it come back to earth again but, no.
Is there still a way?
Thanks.
Hak.
etann said:
Hi everyone,
I just replaced my home security panel into my old sgp311.
It is on stock 5.1.1, just rooted, with locked bootloader.
all things are just going fine and I'm finishing few very end steps, I made a wrong decision, which is install xposed without flashing zip file, I tried to copy/overwrite all the files from the ZIP to system and I thought if I simply make every files with right permission, I won't be messed up, yes I know it is not that easy.
Now I got a bootloop sgp311, I can put it into fastboot or download mode, I tried
Code:
fastboot boot twrp_various_versions.img,
hope it could boot into TWRP recovery and I can flash xposed ZIP and make it come back to earth again but, no.
Is there still a way?
Thanks.
Hak.
Click to expand...
Click to collapse
I think you have to reinstall everything from Flashtool (0.9.18.6) or restore with xperia-companion.
fastboot won't flash anything on a locked bootloader. It won't boot afterwards.
Rootk1t said:
I think you have to reinstall everything from Flashtool (0.9.18.6) or restore with xperia-companion.
fastboot won't flash anything on a locked bootloader. It won't boot afterwards.
Click to expand...
Click to collapse
Thank you.
I flashed with flashtool and leave checkbox "wipe userdata" blank, now seems everything but root is untouched.
Hak.
So it's my second attempt to flash lineage os (unofficial) on my Realme XT. First time I was a little careless and bricked my device (had to go to the service center for that). Second time I took all the precautions still I'm having almost same problem, but this time its not yet bricked.
I unlocked the bootloader. It went fine.
Flashed unofficial TWRP and booted back to stock os.
When I tried booting to TWRP again I realized it was reset back to stock recovery. So I flashed it again and made backup of all the partitions (stupidly on internal storage). Booted back to system to check that backup is showing on internal storage. Again booted to TWRP and wiped everything except internal storage, flashed lineage and gapps. Wiped dalvik/cache rebooted to system. I was greeted with system partition destroyed error screen.
I flashed vbmeta.img via fastboot, the error was gone but still i was not able to boot to lineage. (I directly flashed vbmeta.img via fastboot. Didn't use the "fastboot --disable-verity --disable-verification" command.)
Now I'm having a different kind of problem.
I can boot into TWRP but I can not boot to system (lineage os). Can't go back to stock as well because the internal storage is encrypted i think (all the folders have random names). After flashing vbmeta.img (via fastboot) now I am not able to connect my phone via fastboot.
Without fastboot TWRP backup is the only option for me to get it back in a working state. If anyone reading this has stock color os with TWRP, It would be great help if you could give me a TWRP backup of system.
Also, I would ilke to know where I messed up while unlocking/flashing, so that I can avoid this in the future.
Okay I managed connect it via fastboot again and flashed the stock fastboot image but it didn't help. I'm still stuck at fastboot mode and can boot to TWRP as well but not to system.
While flashing system.img and vendor.img i'm getting error "Invalid sparse file format at header magi".
If anyone can can provide me stock realme recovery, then I can flash official update ozip to get back to stock os (and get out of the bootloop).
naushad.016 said:
If anyone can can provide me stock realme recovery, then I can flash official update ozip to get back to stock os (and get out of the bootloop).
Click to expand...
Click to collapse
There is a flashable twrp stock rom.. in guides section. Flash it in twrp.
Thanks I'll try that!
naushad.016 said:
Okay I managed connect it via fastboot again and flashed the stock fastboot image but it didn't help. I'm still stuck at fastboot mode and can boot to TWRP as well but not to system.
While flashing system.img and vendor.img i'm getting error "Invalid sparse file format at header magi".
Click to expand...
Click to collapse
How you managed to get fastboot ?
naushad.016 said:
If anyone can can provide me stock realme recovery, then I can flash official update ozip to get back to stock os (and get out of the bootloop).
Click to expand...
Click to collapse
You cannot flash the StockRomXYZ.ozip file directly via TWRP or OrangeFox recovery but if you want to flash COLOR OS then use this link - https://forum.xda-developers.com/realme-xt/how-to/official-ota-update-rmx1921ex11-11-26-t3993041 to download and flash directly otherwise convert the .ozip file into .zip file before flashing. Try the steps mentioned in the link to convert - https://forum.xda-developers.com/realme-2-pro/how-to/convert-ozip-to-zip-installing-stock-t4065277 . After conversion, copy the .zip into storage and always use the Clean Flash method to flash the firmware.
Hope you got it.
Hello! This is my first thread on the forum;
I'm writing because I think I soft bricked my Xiaomi Mi Pad 4 LTE, let me explain from the very beginning.
It's a brand new device, bought today, and with a custom italian ROM which was sold with.
I just wanted to root it, and the bootloader was already unlocked because it was a custom ROM, so I tried to install TWRP (mocha version for Mi Pad) with Fastboot and then I wanted to install Magisk.
The issue is that, when I tried to flash TWRP to recovery with fastboot flash recovery twrp.img, it all went "OK" but then TWRP was not actually flashed and couldn't boot it with key combinations, it just looked like it wasn't there. I also tried to boot it without flashing, with fastboot boot twrp.img but it gave me
"Failed to load/authenticate boot image: 00000050" error
Looking on the web, I found someone who told to try fastboot flash boot twrp.img and so, without even thinking, I did it.
That's the main issue. I rebooted, and found that TWRP started, but now I couldn't boot my device anymore, because the default boot.img file was replaced by twrp.img. So, practically, TWRP replaced my device's default system (I think?).
Then, I tried to find a stock firmware for Mi Pad 4 (Clover) on the web, and I found it, so I flashed the stock firmware boot.img, fastboot flash boot boot.img, but when I rebooted, the device was stuck in the loading screen with three dots loading over a "Powered by Android" logo. I waited 20 minutes, nothing, it looks stuck, so this stock boot.img doesn't seem to work.
I can actually flash TWRP and that stock boot image both whenever I want and switch between them; the first works, the latter doesn't.
So, in poor words: I flashed twrp.img as boot.img and now I can't boot normally, but TWRP starts when turning on my device.
But I just want to get my default boot.img or system, or any other way to reaccess to my device. That's fine even if I have to hard reset or wipe everything, it's fine even if I am going to lose data, but please, just help me.
Can someone help me? I'm just a newbie in this world, please help me unbricking my device.
Thanks in advance.
Try installing twrp again and boot to it
Download custom rom.of your choice ( im using hovac and it been great for a year now )
Move it to your mipad via comouter
Format everything in twrp and install the rom and gapps
--- I just remembered havin same issue u having and if im not mistaking : u should reboot to recovery right after installing twrp ( you dont reboot to system )
Im not really sure about it cause it happened long time ago
@DanielVipx
Sorry, seems you tried that already. Did you try the mi flash tool?
This might help:
https://osdn.net/projects/xiaomifirmwareupdater/storage/Stable/V10/clover/
i know there are other threads on this topic. But after going through them I cant find the fix.
I unlocked bootloader and tried to root. Its seems to have worked, but the touchscreen no longer works.
I used lmsa to download the stock rom. installed magisk and ran the boot.img to get the patched boot. Then flashed the patched boot and when i rebooted the device...no touchscreen.
I tried to reflash the original boot.img but that didnt help.
I tried to use LMSA to rescue. but when i connect the phone it says "unable to match firmware. Some key information cannot be read from device."
The original adb fastboot was old. So I did update to the r30 version and tried flashing everything again. but it still boots up and no touchscreen.
Im obviously at a loss here. so any help would be appreciated. Just to even get it back to stock would be fine.
Or do I try to install twrp and throw a custom rom on? would that work. Again, at a loss...
TIA
UPDATE: ive gotten everything sorted. no more bootloop. touchscreen working. connecting to lmsa. and rooted. Thank you for all the responses.
I think what happened is that when i started all this i was not using the latest adb. That seemed to not be an issue for unlocking bootloader, but a major issue for rooting. When i tried to root,i got the no touchscreen. So I followed directions and went to manually flash the stock firmware. I didnt know how to do this and couldnt find instructions for the g power. but did find instructions for the g8 power and assumed it would be the same...its almost the same, but not, so i got the bootloop.
These are the instructions:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash super super.img_sparsechunk.9
fastboot flash super super.img_sparsechunk.10
fastboot flash super super.img_sparsechunk.11
fastboot flash super super.img_sparsechunk.12
fastboot flash super super.img_sparsechunk.13
fastboot flash super super.img_sparsechunk.14
fastboot flash super super.img_sparsechunk.15
I added fastboot flash super super.img_sparsechunk.15, because the g8 power only has 14 sparsechunks and thats why i kept getting the bootloop. very stupid mistake that was driving me nuts! Once i added that 15th line the phone booted up and touchscreen worked again.
Then i installed magisk manager. Took the boot.img file from my stock rom and put it on my phone. back in magisk i clicked on install a patch file, chose the boot.img and created a magisk_patched.img which i put back into the adb folder i previously used to flash the firmware.
Then went back to fastboot and flashed the magisk_patched.img and the phone is now working and rooted...THANK GOD
cnoevl21 said:
i know there are other threads on this topic. But after going through them I cant find the fix.
I unlocked bootloader and tried to root. Its seems to have worked, but the touchscreen no longer works.
I used lmsa to download the stock rom. installed magisk and ran the boot.img to get the patched boot. Then flashed the patched boot and when i rebooted the device...no touchscreen.
I tried to reflash the original boot.img but that didnt help.
I tried to use LMSA to rescue. but when i connect the phone it says "unable to match firmware. Some key information cannot be read from device."
The original adb fastboot was old. So I did update to the r30 version and tried flashing everything again. but it still boots up and no touchscreen.
Im obviously at a loss here. so any help would be appreciated. Just to even get it back to stock would be fine.
Or do I try to install twrp and throw a custom rom on? would that work. Again, at a loss...
TIA
Click to expand...
Click to collapse
Flash stock ROM manually, it will fix the problem
riyan65 said:
Flash stock ROM manually, it will fix the problem
Click to expand...
Click to collapse
The US stock ROM does not have a 'flash all' option. So i have no idea how to flash it. ugh
cnoevl21 said:
The US stock ROM does not have a 'flash all' option. So i have no idea how to flash it. ugh
Click to expand...
Click to collapse
I just ran into the same problem and asked you about it in the other thread. Right after, I tried the boot from XT2041-4_SOFIA_RETUS_10_QPMS30.80-51-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC and got my touchscreen back.
https ://mirrors.lolinet.com/firmware/moto/sofia/official/RETUS/
I found out more of what's going on and posted in the other thread:
I just did the same exact thing. LMSA gave me SOFIA_RETAIL_QPMS30.80_51_8. Lost touchscreen with the patched boot. Used the stock 30.80_51_8 boot and didn't fix it. Also tried the older QPMS30.80-51-3, no dice.
Oh and LMSA can't rescue... key information cannot be read from device.
I'd appreciate any help. Thanks.
UPDATE - found the boot from XT2041-4_SOFIA_RETUS_10_QPMS30.80-51-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC got the screen working again.
UPDATE 2 - patching -5 still left me no touchscreen. Went back to stock -5 and didn't work. Tried -8 and works again... I'm confused.
UPDATE 3 - when phone booted up, it notified me -8 was just installed... Patched -8 boot again and everything appears to be working fine. Moral of story - LMSA downloads the correct firmware if you give the phone enough time to finish auto-updating before rooting. SMH
haanjamin said:
I found out more of what's going on and posted in the other thread:
I just did the same exact thing. LMSA gave me SOFIA_RETAIL_QPMS30.80_51_8. Lost touchscreen with the patched boot. Used the stock 30.80_51_8 boot and didn't fix it. Also tried the older QPMS30.80-51-3, no dice.
Oh and LMSA can't rescue... key information cannot be read from device.
I'd appreciate any help. Thanks.
UPDATE - found the boot from XT2041-4_SOFIA_RETUS_10_QPMS30.80-51-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC got the screen working again.
UPDATE 2 - patching -5 still left me no touchscreen. Went back to stock -5 and didn't work. Tried -8 and works again... I'm confused.
UPDATE 3 - when phone booted up, it notified me -8 was just installed... Patched -8 boot again and everything appears to be working fine. Moral of story - LMSA downloads the correct firmware if you give the phone enough time to finish auto-updating before rooting. SMH
Click to expand...
Click to collapse
good info to know. but now ive gone i screwed my phone up even worse. cuz now im stuck in boot loop. i was trying 105-5, but ill try 51-5, then -8. maybe one of them is the right stupid firmware for my phone
Do not panic.
Follow this guide to flash correct ROM, and patch boot from the ROM to get root
https://forum.xda-developers.com/moto-g-power/how-to/moto-g-power-flashing-guide-t4159301
mingkee said:
Do not panic.
Follow this guide to flash correct ROM, and patch boot from the ROM to get root
https://forum.xda-developers.com/moto-g-power/how-to/moto-g-power-flashing-guide-t4159301
Click to expand...
Click to collapse
ive tried this. i either dont have (and dont know) which is the correct rom. or some other issue. i can get into fastboot mode, no problem. but when i type fastboot reboot fastboot i get that long list of commands, as if im typing in a bad command. and it does not go into fastbootd. i can, however, get into fastbootd through recovery. but every time i try to flash something there, it fails (no file or directory).
And i cant use LMSA cuz when i try to connect, it says the phone has incorrect firmware.