Related
Ok... I'm desperate. I don't care if I won't recover any data, I just want it back working.
My d850 G3 was rooted and TWRP was installed but while trying to open the TWRP interface to copy the latest CyanogenMod, when I rebooted the phone with QuickBoot, it got stuck in developer mode. Now nothing else works besides rebooting and the only way my laptop recognizes the phone is when I select "Apply Update from ADB" but it goes into sideload mode and I cannot sideload anything with MinimalADB & Fastboot or with the SDK Platform Tools.
I tried adb push & adb sideload -> LG_G3_Flash2FixStuckRecovery (the zip from the other thread) , from the sdcard & laptop, it doesn't work.
-> last CMmod, cm-12.1-20151209-NIGHTLY-d850 ... doesn't work...
Any ideas on how to save my phone? I don't care what ROM, even if I can get the custom ROM back, it's still helpful.
Forgot to say I was using Android Kitkat... and here's an image with the screen:
RaulFetish said:
Ok... I'm desperate. I don't care if I won't recover any data, I just want it back working.
My d850 G3 was rooted and TWRP was installed but while trying to open the TWRP interface to copy the latest CyanogenMod, when I rebooted the phone with QuickBoot, it got stuck in developer mode. Now nothing else works besides rebooting and the only way my laptop recognizes the phone is when I select "Apply Update from ADB" but it goes into sideload mode and I cannot sideload anything with MinimalADB & Fastboot or with the SDK Platform Tools.
I tried adb push & adb sideload -> LG_G3_Flash2FixStuckRecovery (the zip from the other thread) , from the sdcard & laptop, it doesn't work.
-> last CMmod, cm-12.1-20151209-NIGHTLY-d850 ... doesn't work...
Any ideas on how to save my phone? I don't care what ROM, even if I can get the custom ROM back, it's still helpful.
Click to expand...
Click to collapse
I hate to tell you budy, But that isnt TWRP or developer mode, what you have here is, default Stock android Recovery that comes with the phone.. So whoever told you that you have TWRP or whatever you
think was TWRP isnt twrp.. so best bet, Flash KDZ.. go into download mode if you can... One more thing.. Read up on this stuff cause you really dont know what your doing........
http://forum.xda-developers.com/showthread.php?t=2772199 you will need to download the kdz for your variant. So omit the file from the post and use the one for for the d850. Follow the instructions.
After more research (about 20 tabs opened in chrome with other forum links and tutorials) I found what I was looking for and fixed my phone. I cannot thank you enough guys I didn't know where to search, for what exactly.
I'm still considering installing a custom ROM, though... any complete tutorial (for newbies) for CMmod or something better?
Best of luck! Cheers
You need to make sure you are rooted and have twrp. The recovery you show in that photo stock. And make sure its bumped.
So I made a post in the general help thread and nobody has replied (although I've only waited a few days so I could probably wait a bit longer) but still I feel like my phone's issues are "unique" compared to other bootloops, I can't find anyone else having the same symptoms on their phone. I'll repost what I said in the general help thread and then give a brief overview of everything because I simply cannot comprehend why I'm unable to get out of bootloop with this damn phone.
So I just recently picked up an old Zenfone 2 (ZE500CL) off of my father who didn't really need it anymore and it was an upgrade from my old ****ty phone, so of course I wanted to root it and after using it for a few hours I wanted to install a custom rom by unlocking the bootloader. Well, I tried that, and something must have gone wrong because I got a bootloop and was only really able to boot into recovery mode.
Now, I didn't backup because I'm dumb for one and two I generally have a good idea of where to start if something does go wrong. The thing is, the methods I've looked up and tried have all failed. First, reflashing the stock rom of my ZE500CL (I've tried four different firmwares from the official website, and I know it's ZE500CL because that's what recovery mode is telling me) does not work. Adb hits 47% in the command prompt, the phone stays at 25% until then, and it goes:
E: failed to verify whole-file signature
E: signature verification failed
Installation aborted
Not sure why it doesn't work, I looked it up and tried various things and it just isn't resolving itself.
So I tried simply running commands like the following:
fastboot flash recovery recovery.img
Using files from the stock firmwares themselves, and that gives me a flash_cmds error. I've tried deleting all of the userdata, the system, the cache, and a factory reset through recovery mode but none of that works. I'd really appreciate any help anyone could offer, this is a pickle and I'd really like to get this phone back up so that I can just run it as a rooted phone.
Click to expand...
Click to collapse
Now, I'll go over the issues quickly:
I'm stuck in bootloop but I can get into recovery mode
Trying to flash any rom, including multiple stock roms from the asus website, results in an installation aborted message at 47% in either ADB or microSD attempt at flashing the rom.
Attempting to run commands like fastboot flash recovery recovery.img ends up giving me a flash_cmds error which I cannot find anywhere else for the Zenfone 2e
Deleting the cache, userdata, system, or factory resetting the phone does not remove the bootloop
Unlocking and relocking the bootloader does nothing
I would really appreciate any help, feels like my phone is a lost cause even when it's not hard bricked.
Try ASUS Flashtool with a .RAW Firmware...
Find on This Thread...
ponnuvelpandian said:
Try ASUS Flashtool with a .RAW Firmware...
Find on This Thread...
Click to expand...
Click to collapse
Thanks, I haven't seen this. I've got the Intel and xFSTK drivers all up and running but my phone isn't being recognized constantly by my computer under Intel Soc in my Driver Manager, and it's not being recognized as MOOREFIELD but rather as CLOVERVIEW PLUS, and only for a second in-between boots on my phone. Can't get the files to be downloaded through xFSTK, so I've hit a snag here unless someone knows the solution to this.
I'll try just running the flash tool and using a raw firmware, then, since I can't do any of the other stuff.
EDIT: Looks like the issue I was having before is stopping me from running the tool, seems that the computer needs to recognize my phone through the Intel drivers at all time (which it doesn't) in order to run the tool. Also I can't get the tool to view the raw file, it only seems to read zip files (so I put the raw into an empty zip, thinking that could maybe work but I don't know for sure). Damnit, I don't know why this is so difficult.
EDIT 2: All right! Looks like I got it working. The process was relatively simple, actually. It involved booting into TWRP but I wasn't able to most of the time for some reason, it would just never do it. But, I was able to using the CWM Zenfone 2 bat file located here: http://forum.xda-developers.com/zenfone2/help/ze500cl-rooting-related-stuff-t3163528/
Then, I needed the stock rom for my ZE550CL placed onto an external sd card which can be found here: http://forum.xda-developers.com/zenfone2/help/ze550cl-factory-reset-return-to-stock-t3141513
So I would download the CWM Zenfone 2, replace the recovery file as the post states, then run the file. After that, I would run T4 since T1 and T2 didn't work (never tried T3), only T4 would seem to boot me into TWRP. From there, I went to Install, left Zip Verification unchecked, and let the damn thing run. It was the only thing that would run for me, even when doing it with ADB it wouldn't work with the stock rom. Then, I just rebooted and now I'm back on my phone. Hopefully this helps anyone else having this troubling issue, it was terrible!
First I apologize for my English, I do not speak English, and I used google translate to translate my text.
I need your help. Please, anyone who understands TWRP and Recovery on Xiaomi phones, help me.
I'll leave it to you to make it easier for you to understand, because the text is long.
TL; DR my cell phone is neither with TWRP nor with Recovery of xiaomi (I think it is not, because I can not get into any of the 2 at all). Everything I did I left step by step in the text.
I wanted to install the ROM pixel, do root and install GCam on my Xiaomi Redmi Note 5 Pro.
The first step was to unlock the bootloader, and yes, I was able to unlock everything quietly, (I waited 180 hours and then I was saying that I did not have my cell phone long enough to unlock, so I downloaded another version of miunlock and managed to unlock).
The second step was to install TWRP, which started to complicate.
Through a video on youtube of a channel that always posts videos to this phone, I followed the instructions for installing TWRP, I did everything according to the video (in this video he did not ask to install anything in Windows, just use cmd) and the commands he typed were as follows:
fastboot flash antirbpass dummy.img,
fastboot flash recovery twrp-3.2.3-1-whyred.img
From there he had to close the cmd and turn off the cell phone (remembering that the cell phone was already in fastboot mode) and then turn on the cell holding power + volume UP to enter the TWRP, however, did not enter the TWRP, entered the recovery mode standard of xiaomi.
So I left for another video. This time, the video was gringo, in this video, the guy asked to install an Adb on the PC, installed correctly and entered the CMD as the video. The commands that the guy from the video passed were this:
fastboot devices
fastboot boot twrp (twrp from another version)
This time the device entered TWRP, but to my surprise, TWRP was asking for a password (which I had no idea what it was) so I went after another version of twrp.
The alternative version for not asking for a password in TWRP that I used is 3.2.3.0, I used it according to the tips of the second video (the same one that I got to TWRP for the first time), and finally I joined the TWRP and did not asked for no password, end of the second part.
The third step was to install the ROM pixel and the magisk, and that's where it started to disgrace everything, I followed the steps according to another video for ROM installation.
In the video, the guy had to enter WIPE, advanced and check some options that did not include internal memory, I did everything right as in the video. Then he had to go to install and select the ROM, when the installation of my ROM started, it already presented an error, the despair hit and I did not know what to do (since I had no more operating system because I had reset the cell phone ) and by impulse, I decided to download the last version of MIUI 10 Stable (I was using the Beta version of MIUI 10), but I did not look right because I was VERY DESPERATE and I ended up downloading ROM Recovery, not ROM fastboot (I think influence on something, I am layman in that, I do not know), I was able to install the MIUI 10 Stable ROM, and soon after I installed Magisk to do the root, in that he had to restart the device.
After rebooting, I made the initial settings, and according to the video, I would need to turn off the phone to enter the TWRP mode to install the GCAM, but my cell phone HAS NO MORE TWRP, and worse, it does not come in the standard Recovery mode of the xiaomi, it's just written MI (that normal boot screen when you connect the Xiaomi device) and I have to restart it by holding down the power button.
I'm using it normally, it's root. But I can not get into the TWRP nor the normal Recovery of the ceular, that is, I can not even install GCam.
That's where my doubt comes in. Can I install TWRP yet? Remembering that the steps I did for the installation is on the topic so I do not know if I can do it again.
And since I'm without TWRP and without Recovery, I will not be able to update my phone anymore? I'm getting into fastboot and system mode at least.
spoktasy said:
First I apologize for my English, I do not speak English, and I used google translate to translate my text.
I need your help. Please, anyone who understands TWRP and Recovery on Xiaomi phones, help me.
I'll leave it to you to make it easier for you to understand, because the text is long.
TL; DR my cell phone is neither with TWRP nor with Recovery of xiaomi (I think it is not, because I can not get into any of the 2 at all). Everything I did I left step by step in the text.
I wanted to install the ROM pixel, do root and install GCam on my Xiaomi Redmi Note 5 Pro.
The first step was to unlock the bootloader, and yes, I was able to unlock everything quietly, (I waited 180 hours and then I was saying that I did not have my cell phone long enough to unlock, so I downloaded another version of miunlock and managed to unlock).
The second step was to install TWRP, which started to complicate.
Through a video on youtube of a channel that always posts videos to this phone, I followed the instructions for installing TWRP, I did everything according to the video (in this video he did not ask to install anything in Windows, just use cmd) and the commands he typed were as follows:
fastboot flash antirbpass dummy.img,
fastboot flash recovery twrp-3.2.3-1-whyred.img
From there he had to close the cmd and turn off the cell phone (remembering that the cell phone was already in fastboot mode) and then turn on the cell holding power + volume UP to enter the TWRP, however, did not enter the TWRP, entered the recovery mode standard of xiaomi.
So I left for another video. This time, the video was gringo, in this video, the guy asked to install an Adb on the PC, installed correctly and entered the CMD as the video. The commands that the guy from the video passed were this:
fastboot devices
fastboot boot twrp (twrp from another version)
This time the device entered TWRP, but to my surprise, TWRP was asking for a password (which I had no idea what it was) so I went after another version of twrp.
The alternative version for not asking for a password in TWRP that I used is 3.2.3.0, I used it according to the tips of the second video (the same one that I got to TWRP for the first time), and finally I joined the TWRP and did not asked for no password, end of the second part.
The third step was to install the ROM pixel and the magisk, and that's where it started to disgrace everything, I followed the steps according to another video for ROM installation.
In the video, the guy had to enter WIPE, advanced and check some options that did not include internal memory, I did everything right as in the video. Then he had to go to install and select the ROM, when the installation of my ROM started, it already presented an error, the despair hit and I did not know what to do (since I had no more operating system because I had reset the cell phone ) and by impulse, I decided to download the last version of MIUI 10 Stable (I was using the Beta version of MIUI 10), but I did not look right because I was VERY DESPERATE and I ended up downloading ROM Recovery, not ROM fastboot (I think influence on something, I am layman in that, I do not know), I was able to install the MIUI 10 Stable ROM, and soon after I installed Magisk to do the root, in that he had to restart the device.
After rebooting, I made the initial settings, and according to the video, I would need to turn off the phone to enter the TWRP mode to install the GCAM, but my cell phone HAS NO MORE TWRP, and worse, it does not come in the standard Recovery mode of the xiaomi, it's just written MI (that normal boot screen when you connect the Xiaomi device) and I have to restart it by holding down the power button.
I'm using it normally, it's root. But I can not get into the TWRP nor the normal Recovery of the ceular, that is, I can not even install GCam.
That's where my doubt comes in. Can I install TWRP yet? Remembering that the steps I did for the installation is on the topic so I do not know if I can do it again.
And since I'm without TWRP and without Recovery, I will not be able to update my phone anymore? I'm getting into fastboot and system mode at least.
Click to expand...
Click to collapse
id say start from scratch.. upto you to reset to official miui with fastboot rom and mi flash (note if you do check clean all only or ill relock bootloader if clean and lock is selected.. no need to wait again but you must unlock it again)
follow this guide.
https://forum.xda-developers.com/re...ne-xiaomi-redmi-note-5-whyred-unlock-t3778049
just skip steps you already did like adb if already installed.... also install drivers.
for twrp use this 1 click also has miflash
https://drive.google.com/open?id=1XLncxs4UDcSxiefQomwT4yZpWthwfAES
i recommend to use orangefox recovery. when you boot into twrp flash orangefox zip thats it.
thanks for answering. I was able to solve the TWRP part using another version of it. Now I'd like to know if it's possible for me to access TWRP directly from my cell phone, without the need for the computer.
spoktasy said:
thanks for answering. I was able to solve the TWRP part using another version of it. Now I'd like to know if it's possible for me to access TWRP directly from my cell phone, without the need for the computer.
Click to expand...
Click to collapse
use quick reboot app from playstore. it boots into recovery or fastboot .
spoktasy said:
thanks for answering. I was able to solve the TWRP part using another version of it. Now I'd like to know if it's possible for me to access TWRP directly from my cell phone, without the need for the computer.
Click to expand...
Click to collapse
settings > developer options > enable extended power menu
this should work
Good morning guys.
I'm not really new to this forum, I've known you for years and I've always followed you for small "mods" or particular problems that I had over time with my devices.
I apologize, but I would like to ask you for help because I have big problems with an ASUS Nexus WiFi 32GB Tablet
Unfortunately, I can in no way connect it to the PC in order to install any rom (I wanted to install the rom stock). I tried everything, I even formatted an old PC and installed windows XP hoping for more compatibility (nostalgic).
The first time, I managed to install a ROM from TWRP recovery 2.8, enabling the USB-OTG and buying the appropriate cable, but then unfortunately, I wanted to try to change ROM and already I was there I wanted to update the recovery to 3.3 .1.0, but I must have been wrong to click somewhere in the recovery. I was convinced that the USB-OTG could always be enabled, so I had the security that I would always be able to install a S.O.
Now the S.O is no longer present in the device and from recovery I can no longer enable USB-OTG, and obviously in the device, no image is present that can help me, probably because I have eliminated everything with different wipes.
The PC in no way manages to see the device, whatever driver I try to install, it tells me that they have no information regarding the connected device, so I can't even use adb.
Please, help me, if needed, format a PC and install Linux or anything else I can use to resurrect this damn device.
Thank you so much for existing ...
Hello, did you try to reboot your tab in bootloader mode, and then install stock factory image from Asus? Maybe After that you will be able to reinstall twrp and custom rom you want... Your tab is unlocked? Did you try the wugfresh tool? Good luck
Thanks for the reply ichi-nii, I tried to reboot the device in bootloader mode (The menu with the open heart robot, Fastboot Mode, right?), Even if it doesn't give me many options, I can only choose whether to Turn off the device, Start it in Recovery (TWRP) or restart the Bootloader, nothing more, and from here I can't install anything anyway.
I believe the device is unlocked, or at least it was, and Fastboot tells me that it is unlocked, so ...
To use the Wugfresh tool, if I didn't err I have to be able to connect this Nexus to the PC and make it see it, but as I said ... No driver allows me to recognize this device from the PC ...
I don't know what to do ...
Isn't there a TWRP terminal way to do something? Some commands that can re-enable the USB-OTG ...
I think I inadvertently (because I didn't know what I was going towards) SELinux enabled, it was after this that the USB-OTG didn't work anymore (I think) ...
Sorry for you bro, so you tell me even in bootloader mode , the tab is not recognized ? Maybe try to connect it when you are in twrp, And another one thing, maybe try another usb port or cable... About otg I can't help you , maybe your connector is broken? Did you try with windows 7 or linux( just to send files to sdcard)
edit: I just try to connect my tab (twrp mode on the screen) to my computer with kali Linux and I Can access to sdcard on the tab
ichi-nii said:
Sorry for you bro, so you tell me even in bootloader mode , the tab is not recognized ? Maybe try to connect it when you are in twrp, And another one thing, maybe try another usb port or cable... About otg I can't help you , maybe your connector is broken? Did you try with windows 7 or linux( just to send files to sdcard)
edit: I just try to connect my tab (twrp mode on the screen) to my computer with kali Linux and I Can access to sdcard on the tab
Click to expand...
Click to collapse
Thank you so much for your help!
I tried to connect the device, both from TWRP and from Fastoboot mode but it is not recognized by Windows ... (Both Windows XP, Windows 7 and Windows 10) I tried to change USB ports and I also tried to change the cable, but nothing ...
The OTG cable is new, I used it on this device and it worked perfectly, I tried it on another device and it works, so the cable is ok, I must have done some **** myself.
Sending any file to the device is just what I'm desperately trying to do, I don't care how, I'm interested in doing it and fixing the damn thing.
If you tell me that your computer with Kali Linux sees it and you can access the memory, I try immediately.
Thank you so much !!
I'm not at all an expert on Linux, how does it work in this case? From Linux terminal? do I have to send commands? Or is it seen as a folder? ....
Forgive my humble ignorance ...
? I'm not an expert too? just install any linux with graphic interface then open the file manager , I did this with kali just because I have it on an old computer.
Good luck
ichi-nii said:
I'm not an expert too just install any linux with graphic interface then open the file manager , I did this with kali just because I have it on an old computer.
Good luck
Click to expand...
Click to collapse
I have to thank you for the help, from Linux I can easily see the device, I managed to insert in the internal memory the rom that I had previously installed ... so I took a big step forward! Unfortunately the misfortune haunts me and the recovery doesn't want to know to install that damn rom. I had to fall back on a Slimroms that I found here on the forum, but I'm not exactly where I want to be. I would like to be able to install my ROM or at most something more complete and updated. Now I try to install the GApps so that I can install some apps that allow me to permanently disable SELinux, then try again to Flash my rom ...
I do not know how to thank you! You have been very helpful.
IgNuReNt said:
I have to thank you for the help, from Linux I can easily see the device, I managed to insert in the internal memory the rom that I had previously installed ... so I took a big step forward! Unfortunately the misfortune haunts me and the recovery doesn't want to know to install that damn rom. I had to fall back on a Slimroms that I found here on the forum, but I'm not exactly where I want to be. I would like to be able to install my ROM or at most something more complete and updated. Now I try to install the GApps so that I can install some apps that allow me to permanently disable SELinux, then try again to Flash my rom ...
I do not know how to thank you! You have been very helpful.
Click to expand...
Click to collapse
Congratulations, like you said it's a big step. Do you use the last twrp? Maybe the problem comes from that...
ichi-nii said:
Congratulations, like you said it's a big step. Do you use the last twrp? Maybe the problem comes from that...
Click to expand...
Click to collapse
I updated the TWRP to 3.3.1.0, I think it is quite up to date, but it is strange that this is so, because from OTG I installed it quietly without problems ... I am convinced that SELinux blocks something ...
I also tried to check the zip file before installation and it gives me an error, it can't install ...
I'm going crazy ... but at least now I have the chance to do tests!
IgNuReNt said:
I updated the TWRP to 3.3.1.0, I think it is quite up to date, but it is strange that this is so, because from OTG I installed it quietly without problems ... I am convinced that SELinux blocks something ...
I also tried to check the zip file before installation and it gives me an error, it can't install ...
I'm going crazy ... but at least now I have the chance to do tests!
Click to expand...
Click to collapse
And now Can you connect the tab to your computer (with windows this Time) If yes you can try install the rom you want from the wugfresh tool?
ichi-nii said:
And now Can you connect the tab to your computer (with windows this Time) If yes you can try install the rom you want from the wugfresh tool?
Click to expand...
Click to collapse
My dear friend! You are an ace, a beast! It was only thanks to you that I was able to solve my problem. Thank you very much, now there is a little 7-year-old who can come back and have fun with this Nexus 7, and of course he also thanks you very much.
I'll tell you briefly how I had to move and the problems I encountered and how I solved it step by step, so that if it happens to someone else, it may have a path to follow eventually.
I was screwed, after I managed to copy the stock image from flash to Kali-Linux inside the Nexus 7, because that damned TWRP crashed during installation without giving me a reason, I had to restart the tablet and that's it; from linux, same speech with ADB Sideload, did not complete the installation.
So I tried to Flashare a custom image, Slimrom that gave me only problems right away, I couldn't touch anything that gave error (but it was installed .. so I was still hoping).
So I tried to flash my damned stock rom directly from Fastboot, but it gave me a thousand mistakes of every kind, from there I suspected that there was something wrong with the file system or the partitions ... something must have messed up something , it was not possible that I could not install any roms anymore, not even the wipe worked, there was something strange, I thought of starting from the base.
So from recovery I found the function that allows you to change File System in the various partitions, so one by one I restored F2FS, the Wipe worked magically, the road was the right one.
I start with the installation of the Stock Rom ... but nothing, errors concerning the lack of files or information (now unfortunately I don't remember in detail)
Reading on the forum, I realized that it could be a common problem and that you could flash the individual files contained in the "stock.img" file that I had downloaded, even individually. So I extracted the archive of the downloaded stockrom, extracted the same .img file inside it, I found myself with all those files.img (boot.img / recovery.img / userdata.img etc etc) at that point I have them flash them one by one with the special fastboot commands.
eeeeeeeeeeeeeeeeeeeee
Taaaaaaaaaaakkkkk
Now it finally starts, it works !!!!!
All this, thanks to you, with that idea of connecting it to linux you gave me hope and it worked !!
I am Italian, from Rimini, if you ever happen in Italy you have a paid fish dinner !!!!!
Thanks again!!!!
IgNuReNt said:
My dear friend! You are an ace, a beast! It was only thanks to you that I was able to solve my problem. Thank you very much, now there is a little 7-year-old who can come back and have fun with this Nexus 7, and of course he also thanks you very much.
I'll tell you briefly how I had to move and the problems I encountered and how I solved it step by step, so that if it happens to someone else, it may have a path to follow eventually.
I was screwed, after I managed to copy the stock image from flash to Kali-Linux inside the Nexus 7, because that damned TWRP crashed during installation without giving me a reason, I had to restart the tablet and that's it; from linux, same speech with ADB Sideload, did not complete the installation.
So I tried to Flashare a custom image, Slimrom that gave me only problems right away, I couldn't touch anything that gave error (but it was installed .. so I was still hoping).
So I tried to flash my damned stock rom directly from Fastboot, but it gave me a thousand mistakes of every kind, from there I suspected that there was something wrong with the file system or the partitions ... something must have messed up something , it was not possible that I could not install any roms anymore, not even the wipe worked, there was something strange, I thought of starting from the base.
So from recovery I found the function that allows you to change File System in the various partitions, so one by one I restored F2FS, the Wipe worked magically, the road was the right one.
I start with the installation of the Stock Rom ... but nothing, errors concerning the lack of files or information (now unfortunately I don't remember in detail)
Reading on the forum, I realized that it could be a common problem and that you could flash the individual files contained in the "stock.img" file that I had downloaded, even individually. So I extracted the archive of the downloaded stockrom, extracted the same .img file inside it, I found myself with all those files.img (boot.img / recovery.img / userdata.img etc etc) at that point I have them flash them one by one with the special fastboot commands.
eeeeeeeeeeeeeeeeeeeee
Taaaaaaaaaaakkkkk
Now it finally starts, it works !!!!!
All this, thanks to you, with that idea of connecting it to linux you gave me hope and it worked !!
I am Italian, from Rimini, if you ever happen in Italy you have a paid fish dinner !!!!!
Thanks again!!!!
Click to expand...
Click to collapse
Yessssss! Congratulations bro ! That's a very good news ?
IgNuReNt said:
My dear friend! You are an ace, a beast! It was only thanks to you that I was able to solve my problem. Thank you very much, now there is a little 7-year-old who can come back and have fun with this Nexus 7, and of course he also thanks you very much.
I'll tell you briefly how I had to move and the problems I encountered and how I solved it step by step, so that if it happens to someone else, it may have a path to follow eventually.
I was screwed, after I managed to copy the stock image from flash to Kali-Linux inside the Nexus 7, because that damned TWRP crashed during installation without giving me a reason, I had to restart the tablet and that's it; from linux, same speech with ADB Sideload, did not complete the installation.
So I tried to Flashare a custom image, Slimrom that gave me only problems right away, I couldn't touch anything that gave error (but it was installed .. so I was still hoping).
So I tried to flash my damned stock rom directly from Fastboot, but it gave me a thousand mistakes of every kind, from there I suspected that there was something wrong with the file system or the partitions ... something must have messed up something , it was not possible that I could not install any roms anymore, not even the wipe worked, there was something strange, I thought of starting from the base.
So from recovery I found the function that allows you to change File System in the various partitions, so one by one I restored F2FS, the Wipe worked magically, the road was the right one.
I start with the installation of the Stock Rom ... but nothing, errors concerning the lack of files or information (now unfortunately I don't remember in detail)
Reading on the forum, I realized that it could be a common problem and that you could flash the individual files contained in the "stock.img" file that I had downloaded, even individually. So I extracted the archive of the downloaded stockrom, extracted the same .img file inside it, I found myself with all those files.img (boot.img / recovery.img / userdata.img etc etc) at that point I have them flash them one by one with the special fastboot commands.
eeeeeeeeeeeeeeeeeeeee
Taaaaaaaaaaakkkkk
Now it finally starts, it works !!!!!
All this, thanks to you, with that idea of connecting it to linux you gave me hope and it worked !!
I am Italian, from Rimini, if you ever happen in Italy you have a paid fish dinner !!!!!
Thanks again!!!!
Click to expand...
Click to collapse
ichi-nii said:
Yessssss! Congratulations bro ! That's a very good news
Click to expand...
Click to collapse
Thanks guys, I stumbled across this thread and changed the file system of System & Data partitions to F2FS (from ext4) and everything seemed to work normally after that. Thank you!
[email protected] said:
Thanks guys, I stumbled across this thread and changed the file system of System & Data partitions to F2FS (from ext4) and everything seemed to work normally after that. Thank you!
Click to expand...
Click to collapse
Congrats
Hello, sorry for the generic title, but i'm quite the noob about android modding and stuff.
Anyway I wanted to root my phone, just to stream some music to my stereo system. How naive I was...
So I unlocked the bootloader, installed twrp with adb and SuperSU with twrp. Everything was fine and phone was rooted but my past naive me thought "well let's try a custom rom, why not". So I went forth and downloaded some stuff from getdroidtips and what I understood is that all I needed to do was to do a wipe, then install the zip file via twrp. I did that and didn't work. After that I realized I made a crucial mistake: I didn't backup my phone from twrp, so I was there with no OS, quite panicked and frustrated. So I tried some other roms, finally I got one that worked, this: https://forum.xda-developers.com/honor-7x/development/openkirin-aosp-8-0-honor-7x-t3746257
It works but it's barebones and on boot it shows a message: "There's an internal problem with your device. Contact your manifacturer for details.". So, I tried recovering from HiSuite, recovery mode etc but nothing worked, I reinstalled SuperSU in the new OS via twrp to see if that would help somehow, but no. in the end I had the even more naive thought that maybe unrooting would allow me to repair via hi suite or something, so I mindlessly selected "complete unroot" on the SuperSU app, and this was the second big mistake, the process somehow ****ed up the twrp install and it no longer works. Instead, if I try to enter twrp with power button + volume up button, it shows the regular "your phone has been unlocked" screen and then comes up for a split second a black screen with, on the bottom half of the screen the "no command" logo, under it some lines of code that I can't read. It suddenly disappears and sometimes enters in a bootloop showing this screen and powering off every time.
If I keep power button pressed bootloop ends and the phone boots "regularly" in the openkirin OS.
I tried reinstalling twrp the same way I did the first time. No error on adb but same no command behaviour
So what I got now is:
kind of bootlooping no command window
openkirin OS with internal problem message
fastboot and rescue mode
it seems to work on adb (everything is fine if I type adb devices)
not working HiSuite recovery
not working Huawei eRecovery
not working download mode (I guess? the power+volume up+volume down combination)
Maybe I should mention I also did a data wipe (?? the option on the right next to "advanced wipe" in the Wipe screen, if I remember correctly) in twrp before installing openkirin, it was suggested on a yt video about how to install openkirin. And that, at a stage I tried using MultiTool but it gives me an error: "exception during a web client request. Error#9", while at the bottom left it says "downloading AdbWinUsbApi.dll..."
Sorry for the general noobishness and the bad english that might be there.
So, any tips for bringing back the phone to normal? Or at least repair twrp??
Please help, I hate needing to throw this phone away just because I wanted to stream some music and because of a couple of stupid errors
Sorry for not answering earlier. It seems, between TWRP and stock recovery, you have messed up I think. When there is no proper recovery it become difficult to bring back the phone. You should try to put it in fastboot mode first, by powering off, pressing the volume lower button and connecting it to computer. Try installing TWRP and flash a custom rom other than openkirin from there if possible. Fastboot is the choice to go if recovery is messed up.
sdivk said:
Sorry for not answering earlier. It seems, between TWRP and stock recovery, you have messed up I think. When there is no proper recovery it become difficult to bring back the phone. You should try to put it in fastboot mode first, by powering off, pressing the volume lower button and connecting it to computer. Try installing TWRP and flash a custom rom other than openkirin from there if possible. Fastboot is the choice to go if recovery is messed up.
Click to expand...
Click to collapse
No worries, I managed to fix it anyway. Some things might be obvious but I'll share what I did nevertheless, in case some other newbie finds himself in a similar situation.
So there was seemingly no way of reinstalling twrp nor the stock recovery. But luck came my way and by almost random clicking I found out that, even if multitool closed as soon as I clicked the ok button in the error message, if I simply ignored the error, the program worked just fine (as I write this I installed another version and it gave no error message). So I played with it a bit and found out that it can flash twrp and it does not need a file from you, it already has a twrp version ready to install. I did that and it worked. It looks like the first twrp file I used didn't work anymore or was someway corrupted by the countless things I tried. So, with twrp working again I was able to backup the sloppy openkiring OS and try the unbrick tool. So I browsed the internet for a guide. Guides always mention as the first step for unbricking using the VENDOR.img file located inside a full stock rom. Problem is, 99% of the times they provide a rom without the needed file. So after some tries I found a good complete stock rom with the VENDOR.img here: drive.google.com/file/d/1tjHefytEWbpuV1f4YjX8AaSMzT6jr8TQ/view but I can't remember which forum/site I found it in.
I followed the guide which involves:
-extracting the UPDATE.APP file contained in the provided zip with huawei extractor tool into an X folder on your pc
-copying the VENDOR.img file contained in the X folder, on the root folder of the sd card
-backing up OS (if there's any) via twrp (I had something like 50 partitions, I guess that was messing things up a bit, but for safety I backed them all up)
-doing an advanced wipe from twrp selecting ALL checkboxes BESIDES the SDcard of course
-flashing the vendor.img file via twrp selecting the "Vendor" partition when prompted
-downloading the update_full_[your model]_hw_[your region].zip file, in my case update_full_BND-L21C_hw_eu.zip
-extracting the UPDATE.APP file contained in update_full_BND-L21C_hw_eu.zip with Huawei extractor tool in some other folder Y
-looking for a file named cust.img/CUST.img/version.img/other_name.img (I don't know which other names it can have, I was lucky and had a VERSION.img file in it)
-rename the cust.img/CUST.img/version.img/other_name.img to CUST.img and copy it from the Y folder to the X folder
-boot your phone into fastboot mode
-connect phone to multitool via usb and select the "unbrick" tab
-there, Multitool asks for a folder, give it the X folder. There are some checkmarks on the Multitool "unbrick" page. 4/5 of them should become checked after the folder input. In my case the first 4
-then, simply press the unbrick button
-wait and pray (it can look like it freezes while it's copying the system.img file but wait, it'll be fine)
So I did that and it worked flawlessly, the phone booted slowly but surely into EMUI 5.1 with Android 7.0 I think and everything was fine.
At that point I had a working OS and a working twrp but wanted to go back to the OS I was used to, Android 8.something so, I tried connecting the thing to HiSuite and it automatically asked if I wanted to update, not to 8.something but to 9.1. I thought "SURE I DO!" and updated flawlessly (I thought 9.1 hadn't even been released here in Italy).
When it booted I found out the new OS was working like an antivirusless xp pc: it didn't recognise the SIM, it would crash every 20 seconds, app downloads got stuck at 99%, if it felt like it, it rebooted, pc connection was not stable. Besides, the update being "official" and installed from "trusted" sources (HiSuite), it completely wiped twrp.
And that was the "OH ****, here we go again" moment: no twrp and worse-than-ever-working OS.
So because of the new EMUI version, I guess, Multitool kept recognizing the phone but stopped offering its own recovery, eRecovery, twrp files available for flashing. I was completely frustrated with all of this and decided to give up, but I made the last effort: I tried the relock function in multitool. So I provided the key, pressed relock, waited, prayed, and finally cheered. It worked like a charm. Phone runs now on EMUI 9.1 with locked bootloader without problems. Finally
So I guess in the end I payed 4 euros for a nice update, a painful and frustrating trip into android modding and a lesson : never do android modding!
no, just kidding, don't do it just if you are a newbie AND you don't want to risk to throw the phone in the grabage.
In all other cases consider it carefully
Oh, and also, God bless the MT Team and Russia altogether!! thanks
Quite an experience. All the best. ?
Lol sounds fun. I've bricked my Huawei Mate SE/Honor 7x more times than I can count. I'm just awaiting my 9.1. I want my GPU Turbo! Is it as good as it's supposed to be?