Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!!
Mohammadreza76646 said:
Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!!
Click to expand...
Click to collapse
Doing the update second time is fine, and best way to restore full stock. But you needed to use Oreo version of no-check recovery and the Oreo partition to flash it to.
So if still able to get into twrp, can try with correct no-check recovery and correct partition it's flashed to.
Also
With multi tool , make sure you put check mark on emui 8. Up in upper right corner. That way it uses Oreo partition names and file not nougat.
The partition length over message usually means nougat file or partition name used on Oreo system
mrmazak said:
Doing the update second time is fine, and best way to restore full stock. But you needed to use Oreo version of no-check recovery and the Oreo partition to flash it to.
So if still able to get into twrp, can try with correct no-check recovery and correct partition it's flashed to.
Also
With multi tool , make sure you put check mark on emui 8. Up in upper right corner. That way it uses Oreo partition names and file not nougat.
The partition length over message usually means nougat file or partition name used on Oreo system
Click to expand...
Click to collapse
Thank you for your answer.
But I try to extract update.app (oreo version) but its failed! huawei update extractor cant open it and 7zip cant extract it with (unexpected error...)!
And unfortunately my TWRP dos not work anymore
Mohammadreza76646 said:
Thank you for your answer.
But I try to extract update.app (oreo version) but its failed! huawei update extractor cant open it and 7zip cant extract it with (unexpected error...)!
And unfortunately my TWRP dos not work anymore
Click to expand...
Click to collapse
I give my phone to a friend to work on it. If he can't fix it I try new multi tools version to flash phone.
Mohammadreza76646 said:
Thank you for your answer.
But I try to extract update.app (oreo version) but its failed! huawei update extractor cant open it and 7zip cant extract it with (unexpected error...)!
And unfortunately my TWRP dos not work anymore
Click to expand...
Click to collapse
On the extractor app. On options tab uncheck the verify header option, it should extract then.
Then perhaps first do these three partitions.
Kernel.img
Ramdisk.img
Then
twrp_ramdisk or for stock use recovery_ramdisk
Mohammadreza76646 said:
Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!!
Click to expand...
Click to collapse
I ever have similiar problem with you dude, but it's solved now, if you always stuck on " its OK but when my phone want to start its stuck on google page "just a sec...", its call google accont verification, i'll by bypass with this script, save as to .bat and put on adb folder
adb devices
adb shell content insert --uri content://settings/secure --bind name:s:user_setup_complete --bind value:s:1
adb shell am start -n com.google.android.gsf.login/
adb shell am start -n com.google.android.gsf.login.LoginActivity
pause
in fastboot type:
fastboot -w
after all it's works to me to bypass google account verification
and if now your problem is
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
i solve with re-flash system from this
https://androidfilehost.com/?fid=673956719939830152
fastboot flash system system.img
and doing TWRP Flashing
https://forum.xda-developers.com/devdb/project/?id=25826#downloads
fastboot flash recovery_ramdisk complete_twrp_ramdisk.img
and voila my problem solved..
mrmazak said:
On the extractor app. On options tab uncheck the verify header option, it should extract then.
Then perhaps first do these three partitions.
Kernel.img
Ramdisk.img
Then
twrp_ramdisk or for stock use recovery_ramdisk
Click to expand...
Click to collapse
Hello again dude.
Finally I flashed my phone and I got the system installed.
But now my phones IMEI is lost. and I cant put sim on it!!!
what should I do now???
FRP is locked! (
Mohammadreza76646 said:
Hello again dude.
Finally I flashed my phone and I got the system installed.
But now my phones IMEI is lost. and I cant put sim on it!!!
what should I do now???
FRP is locked! (
Click to expand...
Click to collapse
So now is locked frp. Does phone have twrp or stock now.?
I think when you tried to install the oreo update for second time, you followed same tutorial as the first time. And that made you problem worse. The tutorial has you flash no-check recovery to 2 partition by block number. 22 & 29. On nougat that is "recovery" and "recovery2". On Oreo partion table it is "reserved2" & "erecovery_vendor"
I don't know how to fix imei. Have hope that if to ucan have a full ota install , maybe can be fixed.
There is available a "service rom" (used to fix most all problem) for Europe region with l21.
I can share link to site with service rom if you want , but I have not used it myself so not gonna be much help with it.
Link is to rusian language page. Google should translate for you.
https://4pda.ru/forum/index.php?showtopic=879524&view=findpost&p=73818595
mrmazak said:
So now is locked frp. Does phone have twrp or stock now.?
I think when you tried to install the oreo update for second time, you followed same tutorial as the first time. And that made you problem worse. The tutorial has you flash no-check recovery to 2 partition by block number. 22 & 29. On nougat that is "recovery" and "recovery2". On Oreo partion table it is "reserved2" & "erecovery_vendor"
I don't know how to fix imei. Have hope that if to ucan have a full ota install , maybe can be fixed.
There is available a "service rom" (used to fix most all problem) for Europe region with l21.
I can share link to site with service rom if you want , but I have not used it myself so not gonna be much help with it.
Link is to rusian language page. Google should translate for you.
https://4pda.ru/forum/index.php?showtopic=879524&view=findpost&p=73818595
Click to expand...
Click to collapse
It have stock recovery.
Mohammadreza76646 said:
It have stock recovery.
Click to expand...
Click to collapse
in summery. because i have been going back and forth in multiple different groups, multiple problem, i cant remember it all.
you have broken system, from failed root attempt, followed by failed update.
device condition is as follows.
--system not booting
--stock recovery loads
--fastboot/bootloader loads, but is in frp lock status
options are limited, at best.
I think "dload" method with service rom is best.
other option is maybe paid service like dc-unlock. But I can recall some note on there service about frp-unlock, that can only be used on device with working system. (of course if was working system, wouldn't need dc-unlock)
mrmazak said:
in summery. because i have been going back and forth in multiple different groups, multiple problem, i cant remember it all.
you have broken system, from failed root attempt, followed by failed update.
device condition is as follows.
--system not booting
--stock recovery loads
--fastboot/bootloader loads, but is in frp lock status
options are limited, at best.
I think "dload" method with service rom is best.
other option is maybe paid service like dc-unlock. But I can recall some note on there service about frp-unlock, that can only be used on device with working system. (of course if was working system, wouldn't need dc-unlock)
Click to expand...
Click to collapse
No. System boot successfully!
I will send you screenshot:
Mohammadreza76646 said:
No. System boot successfully!
I will send you screenshot:
Click to expand...
Click to collapse
here you are
Mohammadreza76646 said:
here you are
Click to expand...
Click to collapse
what about the "about phone" screen
what does it show for version?
If is all stock you should be able to go into deveolper options and enable "oem unlock". If it is greyed out and cannot switch it. Try First to remove google account (all accounts ). and reboot. See if can change then. If not, try Second to do "fastboot oem relock [enter your bootloader code here]
after relock and rebooted oem switch should be enabled again.
****RELOCK IS ONLY ADVISED IF 100% STOCK ROM****
otherwise relock could make more trouble.
Still not sure how to get IMEI back even if unlocked frp though.
**And please stop posting in other threads , the same problem , because you are getting help here.
your post in recovery thread is off topic to that thread and just makes the forum harder to maintain.
mrmazak said:
what about the "about phone" screen
what does it show for version?
If is all stock you should be able to go into deveolper options and enable "oem unlock". If it is greyed out and cannot switch it. Try First to remove google account (all accounts ). and reboot. See if can change then. If not, try Second to do "fastboot oem relock [enter your bootloader code here]
after relock and rebooted oem switch should be enabled again.
****RELOCK IS ONLY ADVISED IF 100% STOCK ROM****
otherwise relock could make more trouble.
Still not sure how to get IMEI back even if unlocked frp though.
**And please stop posting in other threads , the same problem , because you are getting help here.
your post in recovery thread is off topic to that thread and just makes the forum harder to maintain.
Click to expand...
Click to collapse
Thanks )
I'm so sorry for my posts, it's because I don't have a stable connection and I can't see notification of my thread.
I gave my phone to friend an he fix IMEI (I don't know how)
But OEM is steel lock.
I think he did it with using special box.
Mohammadreza76646 said:
Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!![/QUOTE
Are u able.to boot into twrp ?
Click to expand...
Click to collapse
Hello I have a Huawei Mate-SE (with bootloader unlocked and rooted with magisk v16). I have been using the android custom rom RRO v6 (RR-O-v6.0.0-20180401-bnd-OpenKirin) for around a month now. I got this exact same problem about the White Screen saying "ERROR MODE Attention...." since I updated the Magisk to latest version (from the installed application) and rebooted my phone. SInce I rebooted I am getting that same error which makes the phone loops into it for a few times and then it loads the Huawei eRecovery that offers me some options that I am not sure what would do to my phone.
I have been trying to connect to adb tools/fastboot but it doesn't detect the phone and im pretty sure I have the device drivers installed on my computer since nothing have changed in my pc for a month now since I flashed RRO on it.
Is there any other mode besides recovery that would allow me to connect adb/fastboot to it? Or does anyone knows how should I proceed?
IonDEfeso said:
Hello I have a Huawei Mate-SE (with bootloader unlocked and rooted with magisk v16). I have been using the android custom rom RRO v6 (RR-O-v6.0.0-20180401-bnd-OpenKirin) for around a month now. I got this exact same problem about the White Screen saying "ERROR MODE Attention...." since I updated the Magisk to latest version (from the installed application) and rebooted my phone. SInce I rebooted I am getting that same error which makes the phone loops into it for a few times and then it loads the Huawei eRecovery that offers me some options that I am not sure what would do to my phone.
I have been trying to connect to adb tools/fastboot but it doesn't detect the phone and im pretty sure I have the device drivers installed on my computer since nothing have changed in my pc for a month now since I flashed RRO on it.
Is there any other mode besides recovery that would allow me to connect adb/fastboot to it? Or does anyone knows how should I proceed?
Click to expand...
Click to collapse
I have seen where the magisk update screwed up and patches the kernel intead of the ramdisk.
Power off , long press power button.
Hold volume down and plug in USB from PC.
This should cause it to boot into fastboot mode.
Then flash the stock kernel. And the stock or first patched ramdisk. (From earlier root)
mrmazak said:
I have seen where the magisk update screwed up and patches the kernel intead of the ramdisk.
Power off , long press power button.
Hold volume down and plug in USB from PC.
This should cause it to boot into fastboot mode.
Then flash the stock kernel. And the stock or first patched ramdisk. (From earlier root)
Click to expand...
Click to collapse
Hi thank you I was able to finally detect the device now. I am unsure about the kernel is that the recovery.img or system.img files I downloaded (i saved every file i used when I installed the rom) or do I need to look for the kernel somewhere else? I do have the complete_twrp_ramdisk.img file though.
Edit, I did more research and found the stock kernel is withing the boot.img file which I dont have so I looked up for the official BND-L34 oreo update and im currently downloading to extract the stock boot.img from the update.zip and flash it. Since that download was going to take me a while anyway i tried flashing the twrp recovery file without success (didn't changed anything) so i guess I should follow the instructions you gave me by flashing the kernel first then the twrp recovery.
mrmazak said:
I have seen where the magisk update screwed up and patches the kernel intead of the ramdisk.
Power off , long press power button.
Hold volume down and plug in USB from PC.
This should cause it to boot into fastboot mode.
Then flash the stock kernel. And the stock or first patched ramdisk. (From earlier root)
Click to expand...
Click to collapse
Do you know what the boot.img files name is after extraction?
I have extracted all 3 update zips and cannot find anything called boot.img
By the way, thank you.. After updating magisk I have been dealing with failed recovery and failed boot for over a week and this is the first reply anywhere that looks promising
IonDEfeso said:
Hi thank you I was able to finally detect the device now. I am unsure about the kernel is that the recovery.img or system.img files I downloaded (i saved every file i used when I installed the rom) or do I need to look for the kernel somewhere else? I do have the complete_twrp_ramdisk.img file though.
Edit, I did more research and found the stock kernel is withing the boot.img file which I dont have so I looked up for the official BND-L34 oreo update and im currently downloading to extract the stock boot.img from the update.zip and flash it. Since that download was going to take me a while anyway i tried flashing the twrp recovery file without success (didn't changed anything) so i guess I should follow the instructions you gave me by flashing the kernel first then the twrp recovery.
Click to expand...
Click to collapse
if you were on oreo. then there is not a boot.img, instaed there is seperate ramdisk.img and kernel.img.
i have all the files already extracted for oreo and a backup from nougat as well.
https://androidfilehost.com/?w=files&flid=265998
make sure you know what you are doing before flashing.
for example. on oreo the boot and recovery share one kernel image. SO if kernel is messed up you will not be able to boot "boot" or "recovery"
Related
Hey all,
So I received a notification for a system update to 4.4.3, and I had survival mode in SuperSU checked, so I went ahead and followed the procedure. Turns off, then reboots into TWRP. From there I reboot again using the TWRP option, and it boots into android just fine. Notification is gone, still with root. But then I go to settings >> about to find that I'm still running on 4.4.2. Manually check for update, says there isn't one available. Give it a day or so and the notification comes up again. Repeat, and same thing. I'm stuck with the notification again.
So, how do I get rid of the notification, or more preferably, how to I update to 4.4.3 keeping the root? Thanks.
UnfriendlyTurtle said:
Hey all,
So I received a notification for a system update to 4.4.3, and I had survival mode in SuperSU checked, so I went ahead and followed the procedure. Turns off, then reboots into TWRP. From there I reboot again using the TWRP option, and it boots into android just fine. Notification is gone, still with root. But then I go to settings >> about to find that I'm still running on 4.4.2. Manually check for update, says there isn't one available. Give it a day or so and the notification comes up again. Repeat, and same thing. I'm stuck with the notification again.
So, how do I get rid of the notification, or more preferably, how to I update to 4.4.3 keeping the root? Thanks.
Click to expand...
Click to collapse
You can't update the "normal way" like that with a custom recovery. When you try to do that, it tries to boot into the stock recovery to update, but since you have a custom recovery, it will fail everytime if you do it that way. What you have to do is flash the OTA zip using TWRP. You can find the OTA zip in /cache on your device. Or you can just download the update zip from these forums.
UnfriendlyTurtle said:
Hey all,
So I received a notification for a system update to 4.4.3, and I had survival mode in SuperSU checked, so I went ahead and followed the procedure. Turns off, then reboots into TWRP. From there I reboot again using the TWRP option, and it boots into android just fine. Notification is gone, still with root. But then I go to settings >> about to find that I'm still running on 4.4.2. Manually check for update, says there isn't one available. Give it a day or so and the notification comes up again. Repeat, and same thing. I'm stuck with the notification again.
So, how do I get rid of the notification, or more preferably, how to I update to 4.4.3 keeping the root? Thanks.
Click to expand...
Click to collapse
Since 4.4.4 is out, just download the full firmware package from Google and flash system, boot. Only those two.
If you don't know how to do that, the Nexus 5 forums has some great stickies that are mostly relevant to this device.
charesa39 said:
You can't update the "normal way" like that with a custom recovery. When you try to do that, it tries to boot into the stock recovery to update, but since you have a custom recovery, it will fail everytime if you do it that way. What you have to do is flash the OTA zip using TWRP. You can find the OTA zip in /cache on your device. Or you can just download the update zip from these forums.
Click to expand...
Click to collapse
Right, thanks for the information. So I repeated and booted into TWRP again. Tapped 'Install', navigated to /cache, saw a couple of folders named 'back up', 'lost+found', and then a file name of a large string of letters followed by the recognisable "razor KTU70 from KOT49H", so I went ahead and flashed the latter, checking 'verify signature'. Runs through a few commands and in a few seconds comes back as failed, so I reboot into the OS.
Any ideas?
Aerowinder said:
Since 4.4.4 is out, just download the full firmware package from Google and flash system, boot. Only those two.
If you don't know how to do that, the Nexus 5 forums has some great stickies that are mostly relevant to this device.
Click to expand...
Click to collapse
I think I have an idea, but I'll check just to be sure. Thanks for the direction.
Exactly the same for me. Installing the ota sent me to my TWRP recovery. Reboot - > still in 4.4.2.
Reading this thread, I went to TWRP recovery, installed the update from cache and like you, it failed.
Any suggestions? Did your idea work?
Where do I find the 4.4.4 mentioned here and how do I flash it in TWRP? Is install the same as flash in TWRP?
Thanks.
Anderson2 said:
Exactly the same for me. Installing the ota sent me to my TWRP recovery. Reboot - > still in 4.4.2.
Reading this thread, I went to TWRP recovery, installed the update from cache and like you, it failed.
Any suggestions? Did your idea work?
Where do I find the 4.4.4 mentioned here and how do I flash it in TWRP? Is install the same as flash in TWRP?
Thanks.
Click to expand...
Click to collapse
If it fails look to see what the specific error is. It would help to know that. If you pulled it from your cache then I assume it was downloaded by itself and should be the correct OTA. I do NOT have the "Zip file signature verification." box checked or "Enable MD5 verification of backup files." but I am extremely careful to flash/install the correct files. The OTA installed fine for me two days ago using TWRP 2.7.1.0. The 4.4.4 mentioned earlier is the factory image. You will need adb and fastboot installed on your computer to flash the factory image or any image that is pulled from inside the factory image. Wug's toolkit will work also, I think, but I've never used any toolkits. Eventually there will be a stock 4.4.4 rom that you can flash/install in TWRP but I'm not aware of one right now.
You can take the normal updates with root and TWRP (I did), but a custom kernel will prevent them from installing.
I retried to install the downloaded ota file from cache, but this time I checked zip file verification and got the error message that zip verification failed.
File name was
df43279bcf6bb6a0ae403249c3e6f314d0a7eb77.signed-razor-KTU84L-from-KOT49H.df43279b.zip
So it seems the downloaded ota file may be corrupted. How do I get my Nexus 7 2013 to re-download a new one?
(The ota download for my Nexus 5 installed with no problems - but I think it didn't go through TWRP even though TWRP is installed there too).
Thanks
---------- Post added at 04:05 AM ---------- Previous post was at 03:59 AM ----------
Further
I renamed the ota file and in settings checked for system update and got a response that my system is upto date. But it is still 4.4.2.
Need to re-download the ota. How?
Changed the system date to 2 weeks earlier and succeeded in re-downloading the ota file.
So I retried installing it and it again took me to my TWRP recovery screen. I again installed the ota from cache and again the zip verification failed : 1
And the update failed again.
Still on 4.4.2
Did not change any system files as far as I know.
Need help.
Why don't you guys download the stock firmware from Google (link in my signature), and use fastboot to flash system.img, boot.img (DO NOT run the batch file)? If it's a lack of knowledge, all you need do is ask, and I or someone else would be happy to teach you how to use it (fastboot). If you're going to be modifying your Nexus device, you need to learn fastboot. You guys have got to learn the proper way to do things.
You've put forth so much effort to fix a system that is not meant for modified (rooted, customized) phones. You can't fix it, stop trying. Just do it the proper way. And do not use a toolkit. They don't teach you anything, they spoon-feed.
Aerowinder said:
Why don't you guys download the stock firmware from Google (link in my signature), and use fastboot to flash system.img, boot.img (DO NOT run the batch file)? If it's a lack of knowledge, all you need do is ask, and I or someone else would be happy to teach you how to use it (fastboot). If you're going to be modifying your Nexus device, you need to learn fastboot. You guys have got to learn the proper way to do things.
You've put forth so much effort to fix a system that is not meant for modified (rooted, customized) phones. You can't fix it, stop trying. Just do it the proper way. And do not use a toolkit. They don't teach you anything, they spoon-feed.
Click to expand...
Click to collapse
I don't use a toolkit and would be happy to flash the system.Img and boot.img but need instructions on how to do it. You said the stock firmware link is in your signature but it isn't.
I would like to skip 4.4.3 and go directly from 4.4.2 to 4.4.4. I'm talking about a nexus 7 2013 wifi.
So I need the following information to proceed .
1. The Link to download system.img and boot.img for the nexus 7 2013 wifi. Which files exactly?
2. I have fastboot and adb installed on my windows 7 laptop because I used them (once) to root but I don't remember how I used them that one time. How exactly do I use fastboot to flash 4.4.4 ?
3. I presume I will lose root. How do I regain it after the above.
Thank you.
Anderson2 said:
I don't use a toolkit and would be happy to flash the system.Img and boot.img but need instructions on how to do it. You said the stock firmware link is in your signature but it isn't.
I would like to skip 4.4.3 and go directly from 4.4.2 to 4.4.4. I'm talking about a nexus 7 2013 wifi.
So I need the following information to proceed .
1. The Link to download system.img and boot.img for the nexus 7 2013 wifi. Which files exactly?
2. I have fastboot and adb installed on my windows 7 laptop because I used them (once) to root but I don't remember how I used them that one time. How exactly do I use fastboot to flash 4.4.4 ?
3. I presume I will lose root. How do I regain it after the above.
Thank you.
Click to expand...
Click to collapse
1. The Google firmware link in my signature is the one you want. You say you have the 2013 wifi model, aka flo, aka razor. "Factory Images "razor" for Nexus 7 [2013] (Wi-Fi)" is the proper section for you. You want 4.4.4 (KTU84P), and that's at the bottom of the razor section. Click the link to download.
2. Download the most up to date ADB/Fastboot from the link in my signature (19.0.2 (API 19)). Don't extract it yet.
3. You will lose root. Download SuperSU from my signature. 2.00 is the current version. After you download that, you can put it on your device so you can flash it in recovery in a few minutes.
The firmware you downloaded is razor-ktu84p-factory-b1b2c0da.tgz. This is a compressed archive, and you will need to extract it. If you don't know how, 7-Zip should work.
So, you've extracted the files. Delete flash-all.bat, flash-all.sh, flash-base.sh (so you don't accidentally run them).
Now, all you have left is bootloader-flo-flo-04.02.img and image-razor-ktu84p.zip.
Extract image-razor-ktu84p.zip to the current directory, so you will now have bootloader-flo-flo-04.02.img, boot.img, cache.img, recovery.img, system.img, userdata.img, android-info.txt, image-razor-ktu84p.zip in your folder.
Delete userdata.img, flashing this on accident will wipe your data. Delete image-razor-ktu84p.zip, android-info.txt, cache.img, recovery.img (this is stock recovery, you want TWRP).
Now you have boot.img, bootloader-flo-flo-04.02.img, system.img.
Remember the ADB & Fastboot zip you downloaded from my signature? Extract it to the directory with bootloader-flo-flo-04.02.img, boot.img, system.img. All 4 files. This directory now contains 7 files.
Back out of the razor-ktu84p folder. Just one step back. Now, hold shift the right-click the razor-ktu84p folder. Select Open command window here.
Reboot your device to bootloader mode. Do so by shutting it down. Then while the power is off, hold volume down and press the power button. Release these buttons when you see the big green Android.
In your command window, type the command: fastboot devices
Your device with it's serial number should show up on the list. If it does not there is a problem and you need to stop here.
If the device shows up, let's update it.
fastboot flash bootloader bootloader-flo-flo-04.02.img
<wait for it to finish>
fastboot reboot-bootloader
<wait for it to reboot>
fastboot flash system system.img
<wait for it to finish>
fastboot flash boot boot.img
<wait for it to finish>
fasboot reboot-bootloader
Done with fastboot.
At this point, enter recovery (TWRP) and wipe cache and Dalvik under advanced wipe.
Remember the SuperSU you downloaded earlier and put on your device for later? Flash that now.
Reboot, all done. Most of this is just juggling files around. If you have any questions ask.
You are wonderful aerowinder. This is just what I needed to go ahead. Thank you so much.
About your signature, it doesn't show the links when viewed in my Tapatalk version, but I went to the Web view and got it from there. (just FYI if others ask about your links).
is it possible to just flash the system img in fastboot? It's still the same bootloader, not updated? Could I just flash the whole zip by sideloading in adb and TWRP? Just a lottle confused. Thanks!
droider137 said:
is it possible to just flash the system img in fastboot? It's still the same bootloader, not updated? Could I just flash the whole zip by sideloading in adb and TWRP? Just a lottle confused. Thanks!
Click to expand...
Click to collapse
If you were already on 4.4.3, all you need to do is fastboot flash system.img, that is correct.
No, you can't flash that firmware zip in recovery.
thanks
Hi Aerowinder
Thanks again for the excellent instructions. Everything went like clockwork until it didn't ?......
I got to the point where I issued the command fastboot devices which did show the tablet serial number. But my next command to flash the bootloader img gave me the error:
Cannot open 'bootloader-flo-flo-04.02.img
(I had copy pasted the command from your instructions).
The subdirectory below the command window contains that file (one of 7 files)
Sorry. What should I do?
In case you need the info, the device screen showed
Fastboot mode
Product name - flo
Variant - flo 32G
Hw version - rev_e
Bootloader version - flo-04.02
Carrier info = none
Serial number - xxxx
Signing - yes
Secure boot enabled
Lock state - unlocked
Thanks again.
Aerowinder, you are not only an expert but an excellent teacher. Your instructions above should be a sticky.
I'm all done. Everything is fine.
The problem I had above was a file path problem. Not sure why you told me to open the command window in the parent folder. When I opened it in the folder containing the seven files all your commands worked fine. (Except for your last one where you had a spelling mistake: fasboot instead of fastboot).
Thank you very much.
EDIT 8/2/19: I do not own this device anymore. So i cannot and dont know if anything changed about the procedures unlocking rooting etc. BUT if you are getting any trouble i might can help you. Comment your thoughts below
Hey guy, i saw a lot of guys here wondering how to root and flash twrp recovery on thier devices . Today i am gonna show you how to do that.
First of all make sure 3 things :
1. backup your images, contacts, music tracks etc on a external SD CARD, or on your computer.
2. You MUST have the BOOTLOADER unlocked. To do that, read this guide http://en.miui.com/thread-202290-1-1.html
3.Charge your device to 80%+
HOW TO FLASH TWRP AND ROOT MI MAX
1. Go to Settings-About phone-Find the MIUI VERSION, and tap on it for 5-10 times.
2. Go back to settings, sellect adittional settings. click on Developer options, and select enable
3. Find the option USB Debugging and enable it.
4. Download the TWRP recovery from the link
5. rename the file to 'recovery.img'
6. Move the image to the same file where the ADB was installed ( it should be on Computer-> C: -> Adb )
7. Open the adb folder
8. Press and hold the shift key and right click in the folder
9. click on the option "Open command window here"
10. Boot your device on fastboot mode by turning it off, pressing Power and the Volume Down buttons together, and then connect it with your computer
11. First type this command "fastboot devices" to check if your device is into fastboot mode
12. Enter the command "fastboot flash recovery recovery.img"
13. Enter the command "fastboot boot recovery.img"
14. Your phone is now in TWRP recovery mode ( if it is not, the write on ADB: reboot recovery )
15. select Install Zip and click on 'SuperSu.zip'
16. corfirm the flash
17. reboot your device
18. DONT PANIC IF YOU DEVICE WONT TURN ON. Sometimes need to wait 10-20 secs.
DOWNLOADS
1. ADB- (https://forum.xda-developers.com/showthread.php?t=2588979)
2. XIAOMI MI MAX HYDROGEN DRIVERS (http://xiaomiadvices.com/download-xiaomi-usb-drivers/)
3. TWRP RECOVERY IMAGE https://dl.twrp.me/hydrogen/ LATEST VERSION IS twrp-3.2.3-0
4. BetaSuperSu 2.74 http://www13.zippyshare.com/v/OFQGvIyA/file.html
RESERVED
The thread must be removed to XIAOMI MI MAX GUIDES, NEWS, & DISCUSSION
Hallo Friend!
I am about to test your guide. I think it is most decent among other guides on the net...
Could you please just tell me if it's gonna work on:
Android 6.0.1 MMB29M
MIUI 8.2.1.0 (MBCMIDL) Stable
kernel 3.10.84-perf-gfe86e7b
bootloader UNLOCKED
Is superSU by default included in the TWRP you gave? No need to download it additionally from somewhere?
What about warning about "dm-verity" on official TWRP website?
This device uses dm-verity!
This means that swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel. In order to bypass dm-verity's boot prevention, you will have to install a kernel that has dm-verity disabled in the fstab.
Click to expand...
Click to collapse
Should this be any concern that the phone will not boot up again? Should this be disabled first?
Is it better to use the TWRP version you provided (3.0.3.0? not listed on official TWRP website? why?) or the lastest 3.1.0.0?
noob456 said:
Hallo Friend!
I am about to test your guide. I think it is most decent among other guides on the net...
Could you please just tell me if it's gonna work on:
Android 6.0.1 MMB29M
MIUI 8.2.1.0 (MBCMIDL) Stable
kernel 3.10.84-perf-gfe86e7b
bootloader UNLOCKED
Is superSU by default included in the TWRP you gave? No need to download it additionally from somewhere?
What about warning about "dm-verity" on official TWRP website?
Should this be any concern that the phone will not boot up again? Should this be disabled first?
Is it better to use the TWRP version you provided (3.0.3.0? not listed on official TWRP website? why?) or the lastest 3.1.0.0?
Click to expand...
Click to collapse
hello, please write again your problem. I can understand what do you mean.
StonebridgeGr said:
hello, please write again your problem. I can understand what do you mean.
Click to expand...
Click to collapse
Ok just two questions then, because I'm not sure what you can't understand. Please explain.
1) What Android, MIUI and kernel did you root?
2) Do you have SuperSu.zip in TWRP 3.0.3 by default? You didn't say anything in your guide about downloading it and from where + what version.
noob456 said:
Hallo Friend!
I am about to test your guide. I think it is most decent among other guides on the net...
Could you please just tell me if it's gonna work on:
Android 6.0.1 MMB29M
MIUI 8.2.1.0 (MBCMIDL) Stable
kernel 3.10.84-perf-gfe86e7b
bootloader UNLOCKED
Is superSU by default included in the TWRP you gave? No need to download it additionally from somewhere?
What about warning about "dm-verity" on official TWRP website?
Should this be any concern that the phone will not boot up again? Should this be disabled first?
Is it better to use the TWRP version you provided (3.0.3.0? not listed on official TWRP website? why?) or the lastest 3.1.0.0?
Click to expand...
Click to collapse
This twrp. Img it's for all the versions but only for mi max. Not the prime . This twrp doesn't contain superSU. If I remember correctly. But if on the TWRP contain the super su. Don't say yes. Just flash it like I saying on the guide. Maybe they upload a newest version. You can use the new. I think I put the official website . I will check it.
Ok thanks for the answer. Please check from where I download SuperSu - which version would be best.
Please tell me your Android, kernel and MIUI version that you rooted.
noob456 said:
Ok thanks for the answer. Please check from where I download SuperSu - which version would be best.
Please tell me your Android, kernel and MIUI version that you rooted.
Click to expand...
Click to collapse
LOL I forgot to add the superSU link...
That's what I told you. Then please do.
noob456 said:
That's what I told you. Then please do.
Click to expand...
Click to collapse
ok on the first post you can find all the links. if i miss something please tell me here !
Is this beta version of SuperSU reliable? Did you use it? Not better to use a stable version?
noob456 said:
Is this beta version of SuperSU reliable? Did you use it? Not better to use a stable version?
Click to expand...
Click to collapse
It's compatible with mi max. You will not have any problem. Don't worry
noob456 said:
Is this beta version of SuperSU reliable? Did you use it? Not better to use a stable version?
Click to expand...
Click to collapse
Waiting to tell me if everything went fine with the installation and the flashing
Hey, tried following Your guide to install a new rom last night. Great guide for noobs like me, but it may be worth renaming the thread to something like "How to flash whatever makes You happy on to Your Mi Max". These instructions seem to work fine regardless of what's being flashed. Great job, mate!
So I finally tried it and it was successful for me as well! But I used the latest version of TWRP (3.1.0) and SuperSu (2.79-20161205). Please add a point in your tutorial to upload SuperSU.zip to the phone first, because out of emotion, I forgot... So I flashed TWRP, booted it and then... ups... no SuperSu So I wanted to reboot the phone to upload SuperSU but since only SuperSU patches dm-verity (the thing I was afraid of the most - I told you before), my phone got into boot-loop and didn't want to start. So I just uploaded SuperSU to a memory card, entered Fastboot Mode again with key-combination, plugged the cable, typed "fastboot reboot-bootloader" command and was again in TWRP to flash SuperSu from my memory card.... ufff.
So I would reedit it a bit:
0. Copy SuperSU.zip to the phone/memory card!
1. Go to Settings-About phone-Find the MIUI VERSION, and tap on it for 5-10 times.
2. Go back to settings, sellect adittional settings. click on Developer options, and select enable
3. Find the option USB Debugging and enable it.
4. Download the TWRP recovery from the link
5. rename the file to 'recovery.img'
6. Move the image to the same file where the ADB was installed ( it should be on Computer-> C: -> Adb )
7. Open the adb folder
8. Press and hold the shift key and right click in the folder
9. click on the option "Open command window here"
10. Boot your device on fastboot mode by turning it off, pressing Power and the Volume Down buttons together, and then connect it with your computer
11. First type this command "fastboot devices" to check if your device is into fastboot mode
12. Enter the command "fastboot flash recovery recovery.img"
13. Enter the command "fastboot boot recovery.img" - the phone will get disconnected from your PC automatically
14. Your phone is now in TWRP recovery mode (it takes about 30-60 seconds before FastBoot screen switches into TWRP - wait patiently)
15. select Install Zip and click on 'SuperSu.zip'
16. corfirm the flash
17. reboot your device
18. DONT PANIC IF YOU DEVICE WONT TURN ON. Sometimes need to wait 10-20 secs.
Hey, I just got connected with WiFi and new MIUI 8.2.3.0 MBCMIDL wants to be installed, although the phone is rooted with bootloader unlocked. Is it safe to apply the update? Is it goona remove root so that I have to go over the process again?
So I tried the update. First time it said it failed, second time it downloaded the whole ROM after which it rebooted device and TWRP started doing "something" - I don't know what. After that the phone didn't want to boot, and what's even better didn't want to run recovery (TWRP), instead it went into fastboot. What I had to do was to use MiPhoneDrivers from this topic: https://forum.xda-developers.com/mi-max/how-to/guide-install-global-miui8-root-t3435594 (including MiFlash 2015, because 2016 version didn't want to work properly on my PC) and follow the instruction from official MIUI website to flash from scratch the new ROM MIUI 8.2.3.0 which I did. After that my phone was alive again. I installed TWRP and rooted the phone again. Now I've got MIUI 8.2.30 rooted. :] End of the story so far. My settings left untouched - icons, wallpaper etc. So that would be the way to update MIUI if they prepare a new one.
Is there anyway to root the phone without connecting it to pc?
noob456 said:
So I tried the update. First time it said it failed, second time it downloaded the whole ROM after which it rebooted device and TWRP started doing "something" - I don't know what. After that the phone didn't want to boot, and what's even better didn't want to run recovery (TWRP), instead it went into fastboot. What I had to do was to use MiPhoneDrivers from this topic: https://forum.xda-developers.com/mi-max/how-to/guide-install-global-miui8-root-t3435594 (including MiFlash 2015, because 2016 version didn't want to work properly on my PC) and follow the instruction from official MIUI website to flash from scratch the new ROM MIUI 8.2.3.0 which I did. After that my phone was alive again. I installed TWRP and rooted the phone again. Now I've got MIUI 8.2.30 rooted. :] End of the story so far. My settings left untouched - icons, wallpaper etc. So that would be the way to update MIUI if they prepare a new one.
Click to expand...
Click to collapse
Thanks for saving me the trouble.
Can someone help with a better method of applying updates?
Will downloading the zip (1.4GB approx) and flashing via TWRP help?
:crying:Last night, I installed the Android 8 update package on the forum.
Halfway through, an error is displayed and then exit.
I tried eRecovery and Hisuite, but all failed.
I tried it and found that the original recovery partition became recovery_ramdisk. It looks like the partition has changed.
What can I do to be able to return to emui5?
I have imagined "fastboot flashall", but I do not know how? Forgive my lame English
zzkeier said:
:crying:Last night, I installed the Android 8 update package on the forum.
Halfway through, an error is displayed and then exit.
I tried eRecovery and Hisuite, but all failed.
I tried it and found that the original recovery partition became recovery_ramdisk. It looks like the partition has changed.
What can I do to be able to return to emui5?
I have imagined "fastboot flashall", but I do not know how? Forgive my lame English
Click to expand...
Click to collapse
recovery_ramdisk. is the new name of recovery partition. EMUI8/Oreo flashing has started means the partitions etc have changed already so right now you can't go back to EMUI 5 as rollback images are not available yet. You can try to flash again properly with proper download for your specific model. I guess you are missing some echo commands.
thank you very much
SVR said:
recovery_ramdisk. is the new name of recovery partition. EMUI8/Oreo flashing has started means the partitions etc have changed already so right now you can't go back to EMUI 5 as rollback images are not available yet. You can try to flash again properly with proper download for your specific model. I guess you are missing some echo commands.
Click to expand...
Click to collapse
I extract the update.app(oreo) file and then i flash the system.img. Now it works..Thank you
hey how did you did that?
zzkeier said:
I extract the update.app(oreo) file and then i flash the system.img. Now it works..Thank you
Click to expand...
Click to collapse
I also have similar problem I installed different model rom using firmware finder and now I can only use my phone when I unlock bootloader when I lock it it will not open directly go into the erecovery and nothing is working I tried everything twrp,erecovery,force updating nothing worked all failed.please help
shrey2204 said:
I also have similar problem I installed different model rom using firmware finder and now I can only use my phone when I unlock bootloader when I lock it it will not open directly go into the erecovery and nothing is working I tried everything twrp,erecovery,force updating nothing worked all failed.please help
Click to expand...
Click to collapse
well,I flash the system.img by fastboot,and then make a factory reset.Bootloader unlock needed.
i have the same problem
I tried to upgrade phone to Oreo after unlock, in update progress it got error and restart phone! Now it shows:
Code:
Error Mode
Attention!
Please update system again
Error!
Func No : 11 (recovery image)
Error No : 2 ( load failed )
I just have access to fastboot
i did flash system.img and tried install twrp on ramdisk recovery. but always same
:crying::crying::crying::crying:
Hi
After updating to EMUI 8.0 from this tutorial everything went well. Got Oreo working fine, so started to root with magisk = Ok; Xposed=Nok... Bootloop.
First - clean Data and Cache+Dalvik, still Bootloop
Entered to fastboot and tried to flash this file to rollback to 8.0, but...
I nottest that it said on the screen:
Bootloader UNLOCKED (in RED) and FRP Locked (In Green)
Confusing colors, cause it seems that i can't flash anything with unlocking the FRP... but i don´t have access the the system....
Also cant format System partition cause its read only, unable to flash other recovery files thought fastboot....
It s a f*cking MESS....
Can anyone please advice on this?
What can i do to recover this piece of sh*t??
Please........
Thank you, people
==============================
Well, got it figured out... But had to pay for it....
First of all:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You SUCK. Thanks for NOTHING
Lastly:
Thank YOU!!!
Long story short, i've solved it but have to pay for it.
Went to HUAWEI Service Center here in Portugal, and they told me that they couldn't do anything since the phone was not marketed for Europe (??????) [ASS Os]
I've discovered this service, and as with any other service online, i get suspicious for a while, asked a lot of questions and decided:
Bought a Month Pass for 50 EUD (45 Euros), and voila, in the first try unbricked the phone
Now i have the rest of the month to play with it...
Thanks for the people of FunkyHuawei for the kind attention (mostly pacience) they had with me.
I recommend it :good::good::good::good::good:
RSGI said:
Hi
After updating to EMUI 8.0 from this tutorial everything went well. Got Oreo working fine, so started to root with magisk = Ok; Xposed=Nok... Bootloop.
First - clean Data and Cache+Dalvik, still Bootloop
Entered to fastboot and tried to flash this file to rollback to 8.0, but...
I nottest that it said on the screen:
Bootloader UNLOCKED (in RED) and FRP Locked (In Green)
Confusing colors, cause it seems that i can't flash anything with unlocking the FRP... but i don´t have access the the system....
Also cant format System partition cause its read only, unable to flash other recovery files thought fastboot....
It s a f*cking MESS....
Can anyone please advice on this?
What can i do to recover this piece of sh*t??
Please........
Thank you, people
Click to expand...
Click to collapse
Do you still have access to twrp?
It could be only hope.
I had frp lock problem after unlocking bootloader. I had hit reset to default setting while inside developer options menu. That flipped the oem unlock switch.
I had to use twrp to flash back the stock boot.img and stock recovery.img then i was able to oem relock (my code).
And boot into room and reflip oem unlock toggle
thanks for replying
Not sure that i can access TWRP cause every time i force the recovery it appears the EMUI recovery (probably the NoCheck version that i used to update to Oreo)
Isn't it possible to reverte back to EMUI 5.1? Maybe with the 'dload' methode??
Is there any way to reset/unlock FRP from fastboot? I tried to relock bootloader with my own key but got an error (can't remember now what...)
I can't access the ROM itself...
This was because i installed Xposed....
If i could access TWRP again, perhaps i could delete the xposed files (in a recovery with the system as read-only)...
But i just dont know what to look for....
In older systems i knew that was the app_process file... Now i just dont know....
Thanks again for your reply!
help
download multi tool in pc and flash oreo beta via bootloader
i phase the same problem and it fixed my problem
RSGI said:
thanks for replying
Not sure that i can access TWRP cause every time i force the recovery it appears the EMUI recovery (probably the NoCheck version that i used to update to Oreo)
Isn't it possible to reverte back to EMUI 5.1? Maybe with the 'dload' methode??
Is there any way to reset/unlock FRP from fastboot? I tried to relock bootloader with my own key but got an error (can't remember now what...)
I can't access the ROM itself...
This was because i installed Xposed....
If i could access TWRP again, perhaps i could delete the xposed files (in a recovery with the system as read-only)...
But i just dont know what to look for....
In older systems i knew that was the app_process file... Now i just dont know....
Thanks again for your reply!
Click to expand...
Click to collapse
If you tried to install exposed from twrp, it should still be there
try dload method with emui 5 rom package, it may downgrade, no harm in trying.
Sudeep Duhoon said:
try dload method with emui 5 rom package, it may downgrade, no harm in trying.
Click to expand...
Click to collapse
Please can you explain that in detail?
Cause that might be the only way to save this (#"))&%&(/)&....
So, here is my situation:
- No TWRP access (recovery_ramdisk might be empty or damage... hopefully just empty)
- Bootloader Unlocked but FRP Locked
- eRecovery only presents 3 choices: Shutdown, Reboot and "Download latest version and recovery"*
- The System it self it's messed up after trying to install xposed.... just when its about to start, it reboots...
So.......
Still 3 ways that i can resolv this:
1 - the dload method (already tried, it updates until 5%, then error:" Install update failed" (Use the update.app file from the OTA, FullOTA, just the app file, all files in the update.zip... ) Not sure if i'm missing the right app file or if the eRecovery (maybe the NoCkeck version used to update initially) is screwed-up...
2 - Unlocking the FRP (Factory Reset Protection) this means that the "Allow OEM unlocking" is Off
Hopping to find a way to unlock it via fastboot
3 - The *Download latest version and recovery method allows to connect to wifi and download the firmware...
Not much sucess, but i know that i'm missing something (just dont know what it is...)
It seems that the router requires a certain configuration which i have no idea....
Suggestions are always welcome!
Thanks
RSGI said:
Please can you explain that in detail?
Cause that might be the only way to save this (#"))&%&(/)&....
So, here is my situation:
- No TWRP access (recovery_ramdisk might be empty or damage... hopefully just empty)
- Bootloader Unlocked but FRP Locked
- eRecovery only presents 3 choices: Shutdown, Reboot and "Download latest version and recovery"*
- The System it self it's messed up after trying to install xposed.... just when its about to start, it reboots...
So.......
Still 3 ways that i can resolv this:
1 - the dload method (already tried, it updates until 5%, then error:" Install update failed" (Use the update.app file from the OTA, FullOTA, just the app file, all files in the update.zip... ) Not sure if i'm missing the right app file or if the eRecovery (maybe the NoCkeck version used to update initially) is screwed-up...
2 - Unlocking the FRP (Factory Reset Protection) this means that the "Allow OEM unlocking" is Off
Hopping to find a way to unlock it via fastboot
3 - The *Download latest version and recovery method allows to connect to wifi and download the firmware...
Not much sucess, but i know that i'm missing something (just dont know what it is...)
It seems that the router requires a certain configuration which i have no idea....
Suggestions are always welcome!
Thanks
Click to expand...
Click to collapse
What I'm trying to understand , is how were you trying to install exposed.
I assume it was with twrp, no.
mrmazak said:
What I'm trying to understand , is how were you trying to install exposed.
I assume it was with twrp, no.
Click to expand...
Click to collapse
theres not much to understand there....
i flashed it with twrp and the phone never booted again...
yes, had access to the twrp for a while, but then, trying to run again the update process to flash the wrong recovery to recovery_ramdisk partition.... (another shot in the foot)
now i dont have twrp anymore and i'm unable to flash it cause th frp lock keeps telling thats not allowed...
the most clean way to solve this is to erase/unlock the FRP without accessing the ROM...
I'm already thinking about buy some credits with one of those online services that might unlock it...
Can you suggest to me some serious and honest services?
I'm desperate....
RSGI said:
theres not much to understand there....
i flashed it with twrp and the phone never booted again...
yes, had access to the twrp for a while, but then, trying to run again the update process to flash the wrong recovery to recovery_ramdisk partition.... (another shot in the foot)
now i dont have twrp anymore and i'm unable to flash it cause th frp lock keeps telling thats not allowed...
the most clean way to solve this is to erase/unlock the FRP without accessing the ROM...
I'm already thinking about buy some credits with one of those online services that might unlock it...
Can you suggest to me some serious and honest services?
I'm desperate....
Click to expand...
Click to collapse
Ok, I see
Didn't know you where 2 or 3 miss- steps past a failed exposed install.
I have no idea which service to recommend.
Hi,
Hope OP got his solution.
@matt4321
Honorable mod, I guess this thread belongs to Honor 7X Q&A forum. Please relocate.
Cheers
you cant downgrade from emui 8 you need to extract update.app of emui 8 an flash the ramdisk boot img so it will boot for that you need to download indian firmware mannual update given in other forum and extract the zip file update22 and data file extract both zip files and download the multi tool version 8 install all drivers boot your phone into bootloader now go to multi tool and click on unbreak and open huawie update extractor and extract update.app of data or update 22 make sure to check the mark on top emui 8 and when you click on update make sure to uncheck the verify the headder for that you go to settings in extracting update and follow the procedure of flashing for that you can google how to use multi tool i cant explain more i am not a developer but i phase the same problem and i got fixed hope i helped you
RSGI said:
Hi
After updating to EMUI 8.0 from this tutorial everything went well. Got Oreo working fine, so started to root with magisk = Ok; Xposed=Nok... Bootloop.
First - clean Data and Cache+Dalvik, still Bootloop
Entered to fastboot and tried to flash this file to rollback to 8.0, but...
I nottest that it said on the screen:
Bootloader UNLOCKED (in RED) and FRP Locked (In Green)
Confusing colors, cause it seems that i can't flash anything with unlocking the FRP... but i don´t have access the the system....
Also cant format System partition cause its read only, unable to flash other recovery files thought fastboot....
It s a f*cking MESS....
Can anyone please advice on this?
What can i do to recover this piece of sh*t??
Please........
Thank you, people
Click to expand...
Click to collapse
can't you install image from fastboot, if so try to flash rr or aosp system.img or extract from update.app
11122314 said:
download multi tool in pc and flash oreo beta via bootloader
i phase the same problem and it fixed my problem
Click to expand...
Click to collapse
Tried that but the only response that fastboot gives me is "Command not allowed" .
I just can´t flash anything in fastboot. I think i can thought adb shell dd (at least that how i manage to screw twrp partition), but i just can´t get ADB connection.
Just got fastboot connection with HiSuite drivers...
How can i get ADB access? It just installs an USB Storage Device...
Also i can try update via fastboot but it saying that it misses android-info.txt file.... whatever that means...
If i could boot once into the ROM, i would enable "Allow OEM Unlocking" and do exactly that.... btut i junt can´t... not yet...
11122314 said:
you cant downgrade from emui 8 you need to extract update.app of emui 8 an flash the ramdisk boot img so it will boot for that you need to download indian firmware mannual update given in other forum and extract the zip file update22 and data file extract both zip files and download the multi tool version 8 install all drivers boot your phone into bootloader now go to multi tool and click on unbreak and open huawie update extractor and extract update.app of data or update 22 make sure to check the mark on top emui 8 and when you click on update make sure to uncheck the verify the headder for that you go to settings in extracting update and follow the procedure of flashing for that you can google how to use multi tool i cant explain more i am not a developer but i phase the same problem and i got fixed hope i helped you
Click to expand...
Click to collapse
That was my plan... but even that is screwed-up.....
Here is my Recovery Status, without the possibility to flash any img via fastboot:
recovery_ramdisk (empty or in-error)
erecovery_ramdisk ( BND-RECOVERY-NoCheck.img flashed to update into EMUI 8.0)
With the software now, whats failling me is the ****ing recovery, that flash only 5% before it shows this error : "Install update failed!"
Dont have ADB support, maybe because i dont have the "USB Debbuging" option enable...
It seems that i will spend 15 euros to unlock this &%/())(/&%$######()/=?(/%&$#
Just thought I'd post here in case you are still in need. I believe that there are two different recovery modes - one that is triggered by holding power, up vol, and down vol, and another that is triggered by holding just power and up vol. Are you sure twrp is gone? I thought I had lost twrp when in fact it was in the other recovery.
RSGI said:
Please can you explain that in detail?
Cause that might be the only way to save this (#"))&%&(/)&....
So, here is my situation:
- No TWRP access (recovery_ramdisk might be empty or damage... hopefully just empty)
- Bootloader Unlocked but FRP Locked
- eRecovery only presents 3 choices: Shutdown, Reboot and "Download latest version and recovery"*
- The System it self it's messed up after trying to install xposed.... just when its about to start, it reboots...
So.......
Still 3 ways that i can resolv this:
1 - the dload method (already tried, it updates until 5%, then error:" Install update failed" (Use the update.app file from the OTA, FullOTA, just the app file, all files in the update.zip... ) Not sure if i'm missing the right app file or if the eRecovery (maybe the NoCkeck version used to update initially) is screwed-up...
2 - Unlocking the FRP (Factory Reset Protection) this means that the "Allow OEM unlocking" is Off
Hopping to find a way to unlock it via fastboot
3 - The *Download latest version and recovery method allows to connect to wifi and download the firmware...
Not much sucess, but i know that i'm missing something (just dont know what it is...)
It seems that the router requires a certain configuration which i have no idea....
Suggestions are always welcome!
Thanks
Click to expand...
Click to collapse
[BND-L22 / BND-AL10C675] Back to Stock / Unbrick your Honor 7X Indian Variants
Sudeep Duhoon said:
[BND-L22 / BND-AL10C675] Back to Stock / Unbrick your Honor 7X Indian Variants
Click to expand...
Click to collapse
Not even that i can do....
Let's update:
State
OS: Bootloop
System: No "recovery_ramdisk" partition (no stock / no twrp)
Bootloader: Unlocked
*FRP: Locked
So can't flash in fastboot, *Already got the unlock code for the FRP but without the "recovery_ramdisk" recovery the system wont reset....
(Weird!) No adb access in recovery mode (which would help A LOT....)
The dload method, whatever the update.app only updates until 5% , then error updating...
The eRecovery Wireless method might work, but i just dont know how to do it.
Tried with a usb pen inserted on the router with all the ROMs all together, in separated folders, whatever, no rom detected... there must be a way to do it right... i just dont know how...
Just need one of two things to happend:
Flash the stock recovery - still dont know how to do it...
Fix the bootloop and access the SO Rom - also, without adb access just dont know how...
Out of the box thinking required...
About UPDATE.APP
Can't we make a update.app much like o do it for zip files?
Would it be possible to make um UPDATE.APP just to flash/restore recovery partition?
The updates with zip files must also be inside a dload folder?
About Bootloop and SD Card
Is there a way, using the sd card, to stop the reboot, maybe enable the Safe Mode...
Something that would allowed me to access the Settings...
Any apk, any script that could be loaded from the SD card....
Not an easy plan... i know...
Maybe something very basic and easy is escaping me....
RSGI said:
Not even that i can do....
Let's update:
State
OS: Bootloop
System: No "recovery_ramdisk" partition (no stock / no twrp)
Bootloader: Unlocked
*FRP: Locked
So can't flash in fastboot, *Already got the unlock code for the FRP but without the "recovery_ramdisk" recovery the system wont reset....
(Weird!) No adb access in recovery mode (which would help A LOT....)
The dload method, whatever the update.app only updates until 5% , then error updating...
The eRecovery Wireless method might work, but i just dont know how to do it.
Tried with a usb pen inserted on the router with all the ROMs all together, in separated folders, whatever, no rom detected... there must be a way to do it right... i just dont know how...
Just need one of two things to happend:
Flash the stock recovery - still dont know how to do it...
Fix the bootloop and access the SO Rom - also, without adb access just dont know how...
Out of the box thinking required...
About UPDATE.APP
Can't we make a update.app much like o do it for zip files?
Would it be possible to make um UPDATE.APP just to flash/restore recovery partition?
The updates with zip files must also be inside a dload folder?
About Bootloop and SD Card
Is there a way, using the sd card, to stop the reboot, maybe enable the Safe Mode...
Something that would allowed me to access the Settings...
Any apk, any script that could be loaded from the SD card....
Not an easy plan... i know...
Maybe something very basic and easy is escaping me....
Click to expand...
Click to collapse
I just read through the fastboot partition from my backup using "strings" to find the available "oem" commands.
I think i found possible solution for you.
careful useing these commands as I do not know for sure if they work and what they do.
Code:
fastboot oem frp-unlock
also not sure about the dashes or underscores.
mrmazak said:
I just read through the fastboot partition from my backup using "strings" to find the available "oem" commands.
I think i found possible solution for you.
careful useing these commands as I do not know for sure if they work and what they do.
Code:
fastboot oem frp-unlock
also not sure about the dashes or underscores.
Click to expand...
Click to collapse
Hi
Thank you for replying.
Already tried that.... Actually the command should be:
Code:
fastboot oem frp-unlock (unlock frp key)
Bought the unlock code from an online unlock store.
Spent 10 euros. The code is correct cause i got the message that the device will reboot and do a factory reset.
Than it reboots into an error screen, cause i screwed up the "recovery_ramdisk" partition earlier and its not working now. So, no factory reset, no changing the Frp status... Still locked.
Still no flashing img files from recovery... Still got the reply oficial Command Not Allowed...
But:
I'm trying to gain adb access while on eRecovery.
Than i could try to flash the stock recovery with the code dd command. From there i would unlock the Frp with the code and the Factory Reset might be enought to fix the bootloop.
Also the bootloop it self...
I wonder if there's a way to force the boot even with FC errors....
Access to the ROM software would allow me to flash the stock recovery and then make a factory reset, by changing the OEM Unlocking status
Thanks for your reply, maybe you can give me some tips on this 2 ways that i'm exploring right now.
Or some other ways that i haven't consider yet... please....
:cyclops::cyclops:
I've unlocked my bootloader, and tried to install TWRP (the BND-L21 version, it seemed to work fine for other US users) so I could flash a generic boot image like LineageOS 15. It flashed without problems, but when trying to boot to it, I get the following error:
Attention!
Please update system again
[picture of open Android logo]
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
However, I can boot into the system without problems. I've tried to use erecovery to download the firmware and install the update, but that failed.
Is there a way I can either:
A. Install TWRP so I have a recovery? or
B. Install the default firmware so I can have the stock recovery?
P.S. Here's the command I used:
HTML:
fastboot flash recovery_ramdisk (name of recovery file here)
ZentixZaneic said:
I've unlocked my bootloader, and tried to install TWRP (the BND-L21 version, it seemed to work fine for other US users) so I could flash a generic boot image like LineageOS 15. It flashed without problems, but when trying to boot to it, I get the following error:
Attention!
Please update system again
[picture of open Android logo]
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
However, I can boot into the system without problems. I've tried to use erecovery to download the firmware and install the update, but that failed.
Is there a way I can either:
A. Install TWRP so I have a recovery? or
B. Install the default firmware so I can have the stock recovery?
P.S. Here's the command I used:
fastboot flash recovery_ramdisk (name of recovery file here)
Click to expand...
Click to collapse
Happened the same thing with me and i easily had the work around..
But this thread doesnt belong here..
And are you able to access the rom which you installed? Or it straight away goes to erecovery or the error page?
sid21 said:
Happened the same thing with me and i easily had the work around..
But this thread doesnt belong here..
And are you able to access the rom which you installed? Or it straight away goes to erecovery or the error page?
Click to expand...
Click to collapse
The ROM I have installed is the stock EMUI 8.0 ROM. I can boot into it without problems. It only shows the error page if I try to boot into the recovery.
ZentixZaneic said:
The ROM I have installed is the stock EMUI 8.0 ROM. I can boot into it without problems. It only shows the error page if I try to boot into the recovery.
Click to expand...
Click to collapse
Just go through this threads last few pages.. U would probably have to fastboot flash the kernel and/or recovery..
The guy who owns the thread will help you.. He helped me recover too..
The commands are written in last few pages..
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649/page6
same here help me!! i got the same error while booting ?? please give me the solution
ZentixZaneic said:
I've unlocked my bootloader, and tried to install TWRP
Attention!
Please update system again
[picture of open Android logo]
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
However, I can boot into the system without problems. I've tried to use erecovery to download the firmware and install the update, but that failed.
Is there a way I can either:
A. Install TWRP so I have a recovery? or
B. Install the default firmware so I can have the stock recovery?
P.S. Here's the command I used:
HTML:
fastboot flash recovery_ramdisk (name of recovery file here)
Click to expand...
Click to collapse
please help i got the same error ??