I've searched around but haven't found anything on this. I want to root my phone to get more out of it and all, but It's not going so well.
My phone is a Huawei Honor 7 running Android 6.0, I'm using stock since I bricked my phone (I backed up anything important which were some apps and my contacts and such), so I have that which I can import.
I've followed different tutorials with no success in getting TWRP onto my phone, I got it unlocked but I can't get any further.
This is what I've tried for it:
Boot phone into Fastboot and have it connected wia USB to computer.
Checked if it shows up in "fastboot devices", which it does.
Did "fastboot flash recovery TWRP.img", which it says went OKAY, but then when after rebooting it, and getting it into recovery mode, it just boots into the default Huawei eRecovery, and not TWRP.
I've tried different TWRP images, some who said it were for the Honor7 as well, but with no luck, it just won't boot into it.
I hope that's all the needed information, if need anything else just ask.
mikkel1156 said:
I've searched around but haven't found anything on this. I want to root my phone to get more out of it and all, but It's not going so well.
My phone is a Huawei Honor 7 running Android 6.0, I'm using stock since I bricked my phone (I backed up anything important which were some apps and my contacts and such), so I have that which I can import.
I've followed different tutorials with no success in getting TWRP onto my phone, I got it unlocked but I can't get any further.
This is what I've tried for it:
Boot phone into Fastboot and have it connected wia USB to computer.
Checked if it shows up in "fastboot devices", which it does.
Did "fastboot flash recovery TWRP.img", which it says went OKAY, but then when after rebooting it, and getting it into recovery mode, it just boots into the default Huawei eRecovery, and not TWRP.
I've tried different TWRP images, some who said it were for the Honor7 as well, but with no luck, it just won't boot into it.
I hope that's all the needed information, if need anything else just ask.
Click to expand...
Click to collapse
If you want to get into recovery you have to unplug your phone from PC. You can use "ADB reboot recovery" command if you're connected and running system.
Sent from PLK-TL01H
mikkel1156 said:
I've searched around but haven't found anything on this. I want to root my phone to get more out of it and all, but It's not going so well.
My phone is a Huawei Honor 7 running Android 6.0, I'm using stock since I bricked my phone (I backed up anything important which were some apps and my contacts and such), so I have that which I can import.
I've followed different tutorials with no success in getting TWRP onto my phone, I got it unlocked but I can't get any further.
This is what I've tried for it:
Boot phone into Fastboot and have it connected wia USB to computer.
Checked if it shows up in "fastboot devices", which it does.
Did "fastboot flash recovery TWRP.img", which it says went OKAY, but then when after rebooting it, and getting it into recovery mode, it just boots into the default Huawei eRecovery, and not TWRP.
I've tried different TWRP images, some who said it were for the Honor7 as well, but with no luck, it just won't boot into it.
I hope that's all the needed information, if need anything else just ask.
Click to expand...
Click to collapse
+1 the phone must not be connected to the pc when you try to reboot in recovery mode
Also you can use the MultiTool to install Twrp and reboiot to recovery from this tool
Thanks a lot guys! I'm able to boot into TWRP now.
Now I only got to fix my SuperSU problem, it makes me stuck where it says honor, which is loading screen really.
Tried different versions of the BETA-SuperSU (using the betas because got one from tutorai ladn read that they support Android 6.0), but as said simply stuck and don't know if it actually rooted my phone.
Related
"""I recently updated my TF300T to JellyBean 4.2.1. That worked fine. I then wanted to see if I could root this version. I tried 4-5 different custom recoveries, including multiple TWRP and CWM versions. Although they were able to boot to the custom recovery, they could never mount any of the data on the tablet, so I wasn't able to flash any custom roms or root my device. Anyway, I finally installed the latest CWM for the TF300 on JellyBean (6.0.3.1 or something). I still could not mound any tablet data from the recovery. Although installing any of this on a brand new 4.2.1 was incredibly stupid, it gets worse...
I thought that maybe if I did a "wipe data" on the device I would be able to mount it. I then got stuck in a situation in which the tablet would only boot to CWM recovery. I didn't even press the volume key- it would simply go directly to the recovery. This was useless, to say the least, as I could not flash anything or do anything from this.
I then found a way to actually boot into my transformer- I used my PC and typed "adb reboot-bootloader". This gave me the option to cold boot and get into the tablet like normal. However, any subsequent reboots or power-offs would require PC intervention and a cold boot in order to boot into the tablet. This wasn't convenient, although I admin it is much better than where I am now.
I tried multiple times to flash a new recovery, and the same CWM stays on the system. I cannot for the life of me get this stinkin CWM recovery off my device! I ended up trying to wipe my system again, and now I'm absolutely stuck. I can only boot into recovery if I don't do anything on the PC. I can get into fastboot by using a PC, but that's about it. I can't boot into the system after fastboot, and recovery has no rights to change any files.
I can run commands to write new recovery, system, etc using adb, and it sends the file, "writes" it unrealistically fast, and then just says OK as if it was complete. The screen on the tablet doesn't change at all during this, other than the fact that the blinking box for the Fastboot options becomes solid. I have let it sit there for 10-15 minutes and it simply does nothing. (The last attempt was "fastboot -i 0x0B05 flash system blob" where the blob file was the one from the most recent stock firmware download from ASUS.com.) I then have to manually reboot the tablet using the power button, and the whole cycle starts over again.""" I didn't feel like writing all this out so I'm plagiarizing; kill me if you like. I did exactly what he did and got things working the way he did.
Recently though I wiped my hard drive to start a clean windows 7 from scratch and I can't figure out how to get the drivers installed on my computer. As Asus hasn't published them from what I can find and I haven't gotten the android sdk manager to do anything past flashing cmd prompt for a millionth of a second. I basically just need help with the drivers, so any help would be very appreciated. I haven't found anything so far looking through the forums that has helped by the way. I haven't been able to find any threads with solutions yet...
I used the asus pc sync package for the tf300t from asus's website since the tf300tg did not want to download, in any case that with the new google sdk works for me.
Also I noticed issues using anything but twrp openrecovery-twrp-2.5.0.0-tf300t-4.2.blob when it comes to mounting and backups this is the only one that i tried that worked so far.
Device: Nexus 9 (Wi-Fi), Bootloader Unlocked
Computer: Windows 10 (Bootcamp on a Retina MacBook Pro)
After and unsuccessful attempt to install CM 12.1 on my Nexus 9 (Wi-Fi) using TWRP, I tried using this method to return to stock:
http://forum.xda-developers.com/nexus-9/general/guide-nexus-9-to-stock-guide-unbrick-t2975668/
I thought it had worked perfectly, but the tablet still would not boot. I went back and looked at the command prompt log and realized I had made a grave error: I had flashed everything except for the system image. I re-entered fastboot in an attempt to fix it by flashing the system, but now the tablet will not connect to my computer at all. I have tried to remove and reinstall the ADB drivers, but it doesn't show up at all in Device Manager. I tried booting into recovery via fastboot, but got an image of the android mascot knocked-out with an exclamation point, presumably since I over-wrote it with the method above.
Any ideas on how to restore the fastboot/adb connection with my computer? If I can accomplish that I can presumably just flash the system image and that would restore the stock ROM.
Any insight at all would be much appreciated.
dgindra said:
Device: Nexus 9 (Wi-Fi), Bootloader Unlocked
Computer: Windows 10 (Bootcamp on a Retina MacBook Pro)
After and unsuccessful attempt to install CM 12.1 on my Nexus 9 (Wi-Fi) using TWRP, I tried using this method to return to stock:
http://forum.xda-developers.com/nexus-9/general/guide-nexus-9-to-stock-guide-unbrick-t2975668/
I thought it had worked perfectly, but the tablet still would not boot. I went back and looked at the command prompt log and realized I had made a grave error: I had flashed everything except for the system image. I re-entered fastboot in an attempt to fix it by flashing the system, but now the tablet will not connect to my computer at all. I have tried to remove and reinstall the ADB drivers, but it doesn't show up at all in Device Manager. I tried booting into recovery via fastboot, but got an image of the android mascot knocked-out with an exclamation point, presumably since I over-wrote it with the method above.
Any ideas on how to restore the fastboot/adb connection with my computer? If I can accomplish that I can presumably just flash the system image and that would restore the stock ROM.
Any insight at all would be much appreciated.
Click to expand...
Click to collapse
Hello,
I have reported this thread to be moved to right Q&A section in order to get expertise help.
-Vatsal
Have you ever tried to connect your tablet to another computer?
Turns out I forgot to actually press the button in fastboot that enables the USB connection (I feel even more stupid now). Was able to return to stock, albeit with the "This device is corrupt" message during boot.
dgindra said:
Turns out I forgot to actually press the button in fastboot that enables the USB connection (I feel even more stupid now). Was able to return to stock, albeit with the "This device is corrupt" message during boot.
Click to expand...
Click to collapse
I got the same message yesterday after I returned to stock kernel from a custom one. What I did to get rid of that warning message was to flash all img file(boot, cache, recovery, system, vendor) in MMB29K factory image. (Bootloader is optional) [After that I also performed a factory reset but this step might be unnecessary, do it if the message still exist after flashing stock images] If you don't like that warning you can try these procedures.
I was running CM12 and everything was fine. I received a notification to update to CM 13 and I selected yes. It installed OK, but no GAPPS. I tried everything I could think of to install GAPPS, and kept getting errors. IN my frustrated efforts, something happened to my TWRP and now I only have CM Recovery. I'm trying to reinstall TWRP but my phone is being recognized as a "Marshall London Bootloader Interface" ONLY when in the Fastboot and Recovery mode. I have Huawei Hisuite installed and it recognizes the phone fine when powered on, but as soon as I boot into Fastboot and Rescue mode, it reverts to the MLB interface. I am at my wits end as to how to get my PC to recognize my phone properly when in Fastboot and recovery. I did try removing and reinstalling drivers when in Fastboot, but the Marshall Interface keeps on getting inserted. Any suggestions?????? (I also seem to have erased the SD card that has my original system backup files on it. I tried to flash several downloaded stock ROMs using CM recovery, but they all error out. )
I was finally able to re load TWRP using the Huawei Hi Suite. I flashed Carbon ROM and GAPPS and everything seems to be OK but I still cannot use ADB because the phone is recognized by Windows as a Marshall device ONLY when in bootloader mode and ADB does not find the device. When I connect normally it is recognized as a Mate 2 and it connects normally to Hi Suite. I have no idea what could be wrong, but I have read of other people who have this mysterious "Marshall" device show only up when in bootloader mode. Anyone have any ideas????? Can I go back to stock from here if I don't have a saved recovery image to see if I can fix this???
I have no idea what Marshall device means. Is it possible to place the stock 5.1 ROM on a blank micro SD card and follow the flashing instructions? (boot to download mode or whatever it's called)
ScoobSTi said:
I have no idea what Marshall device means. Is it possible to place the stock 5.1 ROM on a blank micro SD card and follow the flashing instructions? (boot to download mode or whatever it's called)
Click to expand...
Click to collapse
I explained what "Marshall Device" is in the first post. I ended up going back to stock (322) and loosing root. I then updated to 5.1 using the SD card. Everything seems to be working OK. Maybe I'll root again and start over when I have more time.
Hi,
I'm new here, so please excuse me if I am posting in the wrong category.
So I tried to root my Doogee F7 (not the pro version) using fastboot and TWRP, and it resulted in a sort of bootloop where it says:
Code:
Orange State
Your device has been unlocked and can't be trusted
Your device will boot in 5 seconds
And then it restarts and gives the same message again. This loop has been going on for some time and I can't stop it because the phone has a non-removable battery and I have tried every possible combination of buttons (i.e. Power + Volume Down + Volume Up).
The process I used in my attempt to root was as following:
1. I used
Code:
adb reboot bootloader
to go into fastboot. (I already set up everything like USB debugging and OEM unlocking in the developer options)
2. I then used
Code:
fastboot oem unlock
and pressed Volume Up to unlock the bootloader. All was successful.
3. I then tried to flash TWRP to recovery and I believe this is where everything went wrong. I flashed it using
Code:
fastboot flash recovery recovery.img
and it was successful, according to the command prompt:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery "C:\Users\momen\Downloads\recovery (1).img"
target reported max download size of 134217728 bytes
sending 'recovery' (12832 KB)...
OKAY [ 0.562s]
writing 'recovery'...
OKAY [ 0.213s]
finished. total time: 0.779s
4. After it finished I used
Code:
fastboot reboot
to reboot the phone and that's when it got stuck.
At the moment I am just letting my battery run out, as I have no other way of turning off the phone, and neither adb nor fastboot is working.
I don't really know if my device was even supported, but I followed the instructions on various websites stating that I should first unlock my bootloader, then flash TWRP, then flash superSU onto it, and my phone would be rooted. I used the latest TWRP image, and I think that was where I went wrong. Is there anything I can do to get my phone to work again?
Hey! i´m sorry for your phone, can you tell me any updates, is it fixed now? what happened? i am about to do the same process to root my Doogee F7 and i´m very worried that my phone gets bricked, so please, i need your recommendations.
I hope everything is alright with your phone.
solartediego said:
Hey! i´m sorry for your phone, can you tell me any updates, is it fixed now? what happened? i am about to do the same process to root my Doogee F7 and i´m very worried that my phone gets bricked, so please, i need your recommendations.
I hope everything is alright with your phone.
Click to expand...
Click to collapse
Ah yes, sorry for not updating. I managed to connect my phone to my PC again using the flash tool and then I could flash the original ROM back onto it. I found the ROM by Googling for a bit tho I dont have a link. Be aware that if you do this, it basically factory resets your phone, locking your bootloader again and all. If you do manage to root your phone please contact me as I still have not managed to do so.
Edit: This process of flashing back your ROM always works as long as your phone powers on, so don't worry too much about bricking your phone. I think I've bricked my phone over 20 times trying to root it, and it worked every single time.
Hello there. I suggest that you use "fastboot boot recovery.img" than using "fastboot flash" if you are not sure if the custom recovery works (or if you just want to test/try it). In this way, you'll just boot the custom recovery temporarily (and your stock recovery is still in tacked).
For rooting your device, first you'll need a working custom recovery for your device (you used TWRP, very first if it works or compatible with your device).
Insyder28 said:
Ah yes, sorry for not updating. I managed to connect my phone to my PC again using the flash tool and then I could flash the original ROM back onto it. I found the ROM by Googling for a bit tho I dont have a link. Be aware that if you do this, it basically factory resets your phone, locking your bootloader again and all. If you do manage to root your phone please contact me as I still have not managed to do so.
Edit: This process of flashing back your ROM always works as long as your phone powers on, so don't worry too much about bricking your phone. I think I've bricked my phone over 20 times trying to root it, and it worked every single time.
Click to expand...
Click to collapse
Hi.How you actually managed to connect your phone to PC using flash tool if you were in a bootloop and had no access to fastboot mode or recovery?
ciubsy2004 said:
Hi.How you actually managed to connect your phone to PC using flash tool if you were in a bootloop and had no access to fastboot mode or recovery?
Click to expand...
Click to collapse
Im interested too in your process to flash TWRP again, as i am in the same boot loop than you with a Doogee S60. I´ve waited till the battery ended, but now flash tool doesn´t recognize my phone. If i charge the battery, i get a boot loop again..
TheBidan said:
Im interested too in your process to flash TWRP again, as i am in the same boot loop than you with a Doogee S60. I´ve waited till the battery ended, but now flash tool doesn´t recognize my phone. If i charge the battery, i get a boot loop again..
Click to expand...
Click to collapse
I have managed to get the flash tool recognizing my phone.Had to keep pressed volume up,if i recall properly(or try volume down) before connecting usb cable to phone with flash tool opened and . It was a while ago though and i can't remember exactly which key was for sure. Hope this helps
Hi People,
I hope I am putting this question in the proper location.
I have had several attempts ate flashing a new ROM to my device as it was the Chinese version & kinda useless to me not having Play store or several other APPs I want. I also wanted to try ROOT a phone for the first time.
I managed to get as far as getting ADB & fastboot working & TWRP installed on the device. The first ROM I had put in my file storage was corrupt so I tried the Lineage 17 version which "seemed"to install with a success message, but the phone would only boot into TWRP. so I tried the Havoc ROM from the thread in this site area. Same thing, would only boot into TWRP. Then I thought I would start over & install the factory ROM from: https://xiaomifirmwareupdater.com/miui/olivelite/stable/V12.0.2.0.QCPMIXM/ with ADB & fastboot. I got a success message from the MiFlash tool but the device is now saying the "MIUI verson cannot be installed on this device" in one screen from the Redmi-Recovery 3.0 menu that's now on it.
From here I can Reboot, wipe data or connect with MiAssistant. When I try MiAssistant (PC Suite) the phone does not connect to my PC but I can see the ADB device from device manager and ./adb fastboot devices shows a serial number -but connected as sideload if that makes a difference?
I hope I explained well enough to be understood. Is there anything I can do from here to get it working or is it fully stuffed?
Ur device's bootloader still unlocked?
T0B3R said:
Hi People,
I hope I am putting this question in the proper location.
I have had several attempts ate flashing a new ROM to my device as it was the Chinese version & kinda useless to me not having Play store or several other APPs I want. I also wanted to try ROOT a phone for the first time.
I managed to get as far as getting ADB & fastboot working & TWRP installed on the device. The first ROM I had put in my file storage was corrupt so I tried the Lineage 17 version which "seemed"to install with a success message, but the phone would only boot into TWRP. so I tried the Havoc ROM from the thread in this site area. Same thing, would only boot into TWRP. Then I thought I would start over & install the factory ROM from: https://xiaomifirmwareupdater.com/miui/olivelite/stable/V12.0.2.0.QCPMIXM/ with ADB & fastboot. I got a success message from the MiFlash tool but the device is now saying the "MIUI verson cannot be installed on this device" in one screen from the Redmi-Recovery 3.0 menu that's now on it.
From here I can Reboot, wipe data or connect with MiAssistant. When I try MiAssistant (PC Suite) the phone does not connect to my PC but I can see the ADB device from device manager and ./adb fastboot devices shows a serial number -but connected as sideload if that makes a difference?
I hope I explained well enough to be understood. Is there anything I can do from here to get it working or is it fully stuffed?
Click to expand...
Click to collapse
You should flash China factory rom, if you can.
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com