Hi! I'm kind of new to this so please forgive me (done once before with a few problems).
Basically, I was looking to root my new HomTom HT16 with SuperSU by downloading a custom recovery (TWRP). I rebooted into bootloader with USB Debugging enabled and OEM Unlocking enabled too.
I selected Fastboot mode from the menu in the bootloader and plugged my phone into my computer. I had no problems recognising the device. I followed the bootloader unlocking steps with:
{fastboot oem unlock}
The instructions that I was originally followed told me that I had to use the Fastboot command (with the recovery.img being TWRP):
{fastboot flash recovery recovery.img}
I was told nowhere that I had to clear any cache partitions (still not sure if I had too). Everything I did seemed successful until I was told to take the battery out, put it back in and turn the device on. It brought up the "HOMTOM" text for the boot screen but instead of booting, it repeatedly turned off and on. Because none of this actually worked, it didn't actually flash the recovery, and so I couldn't boot to it. It just got stuck in a boot loop.
I searched up how to fix a bootloop and I could find anywhere a solid solution unless I just wasn't looking properly. I have all the factory ROM files, I just don't know how to use them to replace anything that could be corrupted. I flashed back the original recovery.img but it still will not turn on, it just says on the "HOMTOM" text screen for a very long time. The recovery also doesn't work, it's just an image of broken android with its internals showing.
Does anyone know what to do now?
adamshaw said:
Hi! I'm kind of new to this so please forgive me (done once before with a few problems).
Basically, I was looking to root my new HomTom HT16 with SuperSU by downloading a custom recovery (TWRP). I rebooted into bootloader with USB Debugging enabled and OEM Unlocking enabled too.
I selected Fastboot mode from the menu in the bootloader and plugged my phone into my computer. I had no problems recognising the device. I followed the bootloader unlocking steps with:
{fastboot oem unlock}
The instructions that I was originally followed told me that I had to use the Fastboot command (with the recovery.img being TWRP):
{fastboot flash recovery recovery.img}
I was told nowhere that I had to clear any cache partitions (still not sure if I had too). Everything I did seemed successful until I was told to take the battery out, put it back in and turn the device on. It brought up the "HOMTOM" text for the boot screen but instead of booting, it repeatedly turned off and on. Because none of this actually worked, it didn't actually flash the recovery, and so I couldn't boot to it. It just got stuck in a boot loop.
I searched up how to fix a bootloop and I could find anywhere a solid solution unless I just wasn't looking properly. I have all the factory ROM files, I just don't know how to use them to replace anything that could be corrupted. I flashed back the original recovery.img but it still will not turn on, it just says on the "HOMTOM" text screen for a very long time. The recovery also doesn't work, it's just an image of broken android with its internals showing.
Does anyone know what to do now?
Click to expand...
Click to collapse
Do you say you have the original files if yes, then if your device is a Mediatek device use SP Flash Tool to flash the rom. If you still need help contact me here or on [email protected]
Related
Purchased an Lg Gpad 7 Wifi tablet (v400) 2 weeks ago. Came with preinstalled Lollipop android so i couldnt install a recovery rom to flash any other custom roms. Downgraded to Kitkat version following the instructions on Xda forums and succesfully installed Twrp. When i installed Cyanogenmod 12.1 through Twrp i got stuck in fastboot screen.
Any suggestions and / or solutions would be greatly appreciated.
I had a similar problem.. Only mine was stuck at the bootloader. Go in TWRP and repair /data and other partitions. My data partition gave me an error since F2FS is a little flaky and some ROMs corrupted it (claimed they supported it). I would recommend erasing the system, cache and data partition if you can't get into TWRP.
The problem is i cant get out of fastboot whatever i try. It says start on bootloader but the tablet just restarts on an empty screen doing nothing.
Hakalai said:
The problem is i cant get out of fastboot whatever i try. It says start on bootloader but the tablet just restarts on an empty screen doing nothing.
Click to expand...
Click to collapse
if you have an sd card, try removing that, then reboot.
if that doesnt work, try entering fastboot command, fastboot continue
Tried without sdcard and i get the same fastboot screen.
How can i give any commands? The only options i have are Restart Bootloader / Restart / Power off. Tried restarting bootloader but i get nothing in return tablet just stays on with nothing on screen.
Hakalai said:
Tried without sdcard and i get the same fastboot screen.
How can i give any commands? The only options i have are Restart Bootloader / Restart / Power off. Tried restarting bootloader but i get nothing in return tablet just stays on with nothing on screen.
Click to expand...
Click to collapse
you said it was stuck on fastboot, if thats the case, install any needed drivers on your pc, connect device to it, open a terminal in the fastboot dir (after you go get fastboot), then try those commands i gave. you could also try, fastboot reboot dont think i mentioned that before.
bweN diorD said:
you said it was stuck on fastboot, if thats the case, install any needed drivers on your pc, connect device to it, open a terminal in the fastboot dir (after you go get fastboot), then try those commands i gave. you could also try, fastboot reboot dont think i mentioned that before.
Click to expand...
Click to collapse
Did as you said but every command i gave gives me an error message in adb terminal. There are new lines in fastboot menu in tablet now. Bottom two are SECURE BOOT - enabled & LOCK STATE - locked.
Hakalai said:
Did as you said but every command i gave gives me an error message in adb terminal. There are new lines in fastboot menu in tablet now. Bottom two are SECURE BOOT - enabled & LOCK STATE - locked.
Click to expand...
Click to collapse
hmm, ok, im guessing it would have said that normally, when not broken. all the command does is try to release it past where its stuck. it doesnt actually flash, lock, unlock, or change anything.
imo, this seems good, because now we know fastboot is working.
i own lg devices, but not your specific device. i would hate to give you some bad advice and make your tablet broken more, but if it were me in this situation, i would try to flash the factory KK firmware you used to downgrade with odin or however you did it. hopefully, that will clean everything up and let it boot properly.
if for whatever reason you cant do that, we could try extracting the factory file, and just flashing recovery and system, those should be the only things that got changed putting on twrp and cm normally.
Sorry, I have the serious proplem wtih my LG pad V400, I rooted it and using <LG Flash Tool 2014> with <V40010c_00.kdz> to downgrate the firmware but their is error then my LG pad stuck in fastboot menu as with just turn off, restart and restart bootloader. if i seclect one one them the tablet just logged again the fastboot menu
it stuck on the fastboot menu and i cannot do nay think with it. I can restart with factory restore mode but when select yes to restore, it will restart and log in fastboot menu again.
I downloaded adb and fastboot program and put in one folder <Minimal ADB and Fastboot> in C:\Program Files (x86)\Minimal ADB and Fastboot
I dont have recovery image so i download file <cm-13.0-20160421-NIGHTLY-v400-recovery.img> form your link to download TWRP file
move it to folder of fastboot programe and changed its name to <recovery.img>
I turn on the tablet and it waited at fastboot menu
when i run the command <fasboot flash recovery recovery.img> and they said some thing wrong like in picture
please help me
I was messing around with my settings last night and quickly enabled the pattern lock without paying much attention to the lock I entered (careless, I know) and now I'm locked out of my OPO on CM13 6.0.1 Marshmallow. I'm not sure if it's just Marshmallow or not but I can't even boot into TWRP.. when I hold the custom recovery buttons with phone both on and off it wont boot into recovery. When this happened, I didn't have USB debugging enabled so I can't use ADB. The only screens that I can look at are the locked lockscreen (spent all night and day guessing patterns) and I AM able to boot into Fastboot mode via powering off the phone and holding the power + up volume button which gives me a SLIVER of hope that I may not have to lose everything due to such a stupid and careless mistake.
Making matters worse, my phone is my only internet source so I'm at the library posting this hoping I'll get the response I need (or any response) sooner rather than later. I'll do ANYTHING I possibly can to not lose my files.. please help! (I even went and bought a brand new laptop with Windows 10 on it since my XP home computer doesn't like my OPO.)
If you can get to fastboot, then you could try flashing the system.img only and see if it boots. If not, the you may have to flash the entire package, excluding userdata and recovery.
Fastboot flashing guide:
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
Fastboot image:
http://builds.cyngn.com/factory/bacon/cm-13.0-ZNH0EAS2JK-bacon-signed-fastboot-2d1a3b8dca.zip
If you are able to boot into fastboot mode,then first flash a custom recovery(eg.twrp) using the command
Code:
fastboot flash recovery recovery.img
Then boot into recovery from fastboot mode using this command
Code:
fastboot boot recovery.img
If you did everything right you might boot into your recovery. And from there I'm sure you can resolve your issue.
If you want any further help please contact me at [email protected]
Hit Thanks If You Find My Solution Valid
Hello,
as the title says... I bricked my phone. In the past, I successfully installed LineageOS on my old Galaxy S3. I got a used Huawei P9 Lite recently and wanted to install a custom ROM. Here's what happened:
1. Unlocked the phone
2. Accessed Fastboot mode
3. Installed TWRP* via fastboot flash recovery file.img
4. This didn't work and I read on the web, I could try to flash revocery2 with fastboot flash recovery2 file.img
5. This didn't help either, so I decided to cancel my plan and use the manufactorer's system since the system still booted (of course, I didn't install any custom OS).
6. The phone told me on each startup it's unlocked. I didn't need the unlock anymore, so I accessed the Fastboot mode again.
7. I re-locked the system by using fastboot oem relock password.
8. The phone asked me to do confirm this action and do a factory reset
9. After this, I'm stuck at the Huawei logo and can't access Fastboot mode anymore!
When I shut down the phone, it immediately restarts itself. No chance to get into Fastboot mode again, which I did through pressing Vol- and plugging in an USB cable.
*I tried several versions, 3.0.1 and 3.2.1 since no version worked
This may be a beginner's fault, my last phone was already unlocked and I had not a single problem back then. But this time... I hope you can help me.
What would happen if I let drain the battery down to 0% - the phone wouldn't restart of course. If I press Vol- and plug it in, would I come back to Fastboot mode or would it stay in this loop?
Any help is appreciated!
Hi everyone,
I'm quite new to unlocking and rooted phone, but I've read many many post on this forum but nothing worked....
Here what's happening;
Few days ago I wanted to Recover from TWRP a backup that I've made. I launch the recovery from TWRP (important details, it was a backup that I made from slot B in twrp....) in slot A.
So yes I indeed restore a slot B recovery into the slot A in TWRP.....
And I tried to reboot after that..... and the problems begins !!
I just have a blackscreen with a blue light, nothing happened..... Same thing If i try to boot into recovery mode.....
Since I tried many many things but nothing worked...... I can't boot into TWRP from fastboot.
When I'm trying that:
Code:
fastboot boot twrp-3.2.2-0-enchilada.img
The phone just reboot and got stucked on the screen with one plus logo and the text "fastboot mode" below the logo.....
I read all these post below and everything I tried (erase all data, change the active slot on fastboot mode......)didn't work:
https://forum.xda-developers.com/oneplus-6/help/oneplus-6-os-twrp-stuck-fastboot-screen-t3870989
https://forum.xda-developers.com/oneplus-6/help/stuck-fastboot-rooted-help-please-t3851802
This one I didn't really understand exactly what needed to be done but I guess I need to boot into a custom recovery as well:
https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051
Even tried that but it didn't unbrick the phone:
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
I tried to boot into another recovery, but same thing not working/booting;
Code:
fastboot boot blu_spark_r65-oos-pie_op6_9a5f932e4.zip
So I'm desesperate and really really need help !!:crying::crying:
Does anyone can help me step by step or has a solution please?
I can access to fastboot mode that is the only think I can do and the bootloader is unlocked.
Go and see there :
https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3903272
You'll get your phone like it comes out of the box.
yep, do this:
https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3903272
I had the same problem with my OP3. i cant get past the fastboot screen. after i tried the tool everything was back to normal. but i had to oem lock after it to boot up.
Also use the official twrp for a fully functional backup and restore
Thank you all for your reply !
I've tried to follow the process from the link but the MSMTool is not finding my OP6 and I've uninstall in the Device Manager as indicated:
HTML:
plug in the phone to the computer, go in device manager and under port (COM) disinstall qualcomm one (oneplus 6) and then unplug
But When I go into safe mode and re-plug, I can't do this part because I don't have this information....
HTML:
Now you have to see US8_BULK as new device connected and you can also see in device manager; if you can't notice it, repeat the process until you see it (power on, power off, hold...) there is a full youtube guide for op5 and it's the same process
I tried on 2 different PC (Windows 10 and 7) but nothing worked so I can't used the MSMTool
You have to use it in safe mode to install the unsigned drivers. It only works when you see the device as something like 9800 in your device manager.
Dont worry if it fails a few times. I had to do this 8 times on my OP3 till it was successful.
You can also use this guide:
https://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
The steps are the same
Had a bad idea this morning and decided to try to root the phone, leagoo t5. The last time Im going to go messing with a phone that wasnt broken! after spending 10hrs trying to sort it! I downloaded adb tools and and twrp. I unlocked the bootloader with fastboot and installed twrp. However when I rebooted the phone it just booted straight into twrp. I cant get it to boot normally. I reinstalled the firmware but it will still not boot. I can get into recovery and factory modes but thats it. what can I do? Thanks
pcfreeze said:
Had a bad idea this morning and decided to try to root the phone, leagoo t5. The last time Im going to go messing with a phone that wasnt broken! after spending 10hrs trying to sort it! I downloaded adb tools and and twrp. I unlocked the bootloader with fastboot and installed twrp. However when I rebooted the phone it just booted straight into twrp. I cant get it to boot normally. I reinstalled the firmware but it will still not boot. I can get into recovery and factory modes but thats it. what can I do? Thanks
Click to expand...
Click to collapse
Have you tried factory resetting in recovery?
ktmom said:
Have you tried factory resetting in recovery?
Click to expand...
Click to collapse
Yes I did. No Joy. When I power on I just get the leagoo logo coming on and off repeatedly. Pressing the power button then will not turn the phone off again. I can switch it off by pressing vol- and pwr together though.
Is the problem caused by unlocking the bootloader with fastboot or that the firmware I installed is not suiting? Rebooting the phone after unlocking the bootloader before reflashing the firmware caused the leagoo logo to come on and off repeatedly accompanied by this message in very small text "Orange State - Your device has been unlocked and can't be trusted, Your device will boot in 5 seconds". After flashing the firmware with Sp Flash Tool this message is not being shown. Does reflashing firmware undo the action of unlocking the bootloader?
What your are describing is a bootloop. It sounds like the device can not find the system kernel to boot to. Did you boot the device after unlocking but before doing anything else?
Where did you get the TWRP recovery from?
Isn't this a mediatek chipset? If so, I think you need to use SP Flash Tool*to install.
I would look for a stock ROM for this device to revert to.
I'm not experienced on mediatek devices, but maybe @SubwayChamp could help.
pcfreeze said:
Yes I did. No Joy. When I power on I just get the leagoo logo coming on and off repeatedly. Pressing the power button then will not turn the phone off again. I can switch it off by pressing vol- and pwr together though.
Is the problem caused by unlocking the bootloader with fastboot or that the firmware I installed is not suiting? Rebooting the phone after unlocking the bootloader before reflashing the firmware caused the leagoo logo to come on and off repeatedly accompanied by this message in very small text "Orange State - Your device has been unlocked and can't be trusted, Your device will boot in 5 seconds". After flashing the firmware with Sp Flash Tool this message is not being shown. Does reflashing firmware undo the action of unlocking the bootloader?
Click to expand...
Click to collapse
Then to unlock bootloader is not normal that Android refuses to boot normally but when you flash a custom recovery or modify other partition this usually could happen so either or both you have to do a factory resetting/format data as @ktmom said or/and flash a kind of DM-verity for your device, this last avoids that bootloader checks the integrity of the partitions and can boot normally to system.
The warning message is normal then to unlock bootloader and reflashing the stock rom doesn´t relock it, you have to relock it at similar way that you unlocked it via fastboot command, most commom is "fastboot oem relock" but there are other variants and keep in mind that you have to return completely to stock before to apply it.
SubwayChamp said:
Then to unlock bootloader is not normal that Android refuses to boot normally but when you flash a custom recovery or modify other partition this usually could happen so either or both you have to do a factory resetting/format data as @ktmom said or/and flash a kind of DM-verity for your device, this last avoids that bootloader checks the integrity of the partitions and can boot normally to system.
The warning message is normal then to unlock bootloader and reflashing the stock rom doesn´t relock it, you have to relock it at similar way that you unlocked it via fastboot command, most commom is "fastboot oem relock" but there are other variants and keep in mind that you have to return completely to stock before to apply it.
Click to expand...
Click to collapse
I relocked the boot loader with the command "fastboot flashing lock". small white text dialogue on phone screen stated bootloader was locked successfully. rebooted phone then and it was still stuck in the boot loop. For a few seconds in between the leagoo logo a strange circular graphic was displayed on the phone with word "erasing" under it. What does this mean?
Can you tell me more about how to flash DM-verity?
pcfreeze said:
I relocked the boot loader with the command "fastboot flashing lock". small white text dialogue on phone screen stated bootloader was locked successfully. rebooted phone then and it was still stuck in the boot loop. For a few seconds in between the leagoo logo a strange circular graphic was displayed on the phone with word "erasing" under it. What does this mean?
Can you tell me more about how to flash DM-verity?
Click to expand...
Click to collapse
Ok, then to relock bootloader I guess that you did successfully boot to system again, right?
When you unlocked bootloader first then device is formatted to avoid a new user can access to the user´s data and when you relock it again the same happens.
As for DM-verity, newer devices strictly since nougat can´t boot to system after any partition was modified like happened when you flashed a custom recovery on it, here is when DM-verity can be useful, is used to avoid bootloader checks the integrity and allow a modified device can perform a reboot and more custom actions not officially permitted. You had to flash it through a custom recovery, sometimes flashing only Magisk is enough but not always.
You *might* be able to use this universal dm-verify script. It can be flashed only in a custom recovery and I'm not certain that is available to you.
ktmom said:
You *might* be able to use this universal dm-verify script. It can be flashed only in a custom recovery and I'm not certain that is available to you.
Click to expand...
Click to collapse
Good news and bad news! I got the phone to boot! I reinstalled twrp and the "magisk","no verity opt encrypt" and "disable dm verity" zips from the ext sdcard with fastboot. Twrp stated the zips installed ok but there were also some red line failure lines in the dialogue as they were being installed. I rebooted the phone via fastboot but this just resulted in it booting direct to twrp as before. I tried normal boot from twrp but it still booted straight back to twrp. I then tried selecting normal boot from the fastboot, normal, recovery option menu accessed on the Leagoo T5 by powering off the phone and then pressing the pwr and vol+ buttons together but this still resulted in it booting straight to twrp. I then decided to uninstall twrp by flashing the stock firmware recovery image to try to boot from stock recovery. I did same and rebooted from fastboot and it booted to system.
The bad news is there is an imei failure message and the sim is not connecting to the network.I googled imei failure and saw that its can happen when firmware is changed. I installed the "mobileuncle" app but according to a youtube video I watched, when I tap "Engineer Mode" there should be 2 further options available, one being MTK Mode. I am only getting one option "Engineering Mode (Android) which when I select just results in being returned to the previous menu. please say this is not a major problem!
@pcfreeze you quoted me, but as I said earlier, I'm not experienced with mediatek devices. You'd be better off quoting @SubwayChamp
pcfreeze said:
Good news and bad news! I got the phone to boot! I reinstalled twrp and the "magisk","no verity opt encrypt" and "disable dm verity" zips from the ext sdcard with fastboot. Twrp stated the zips installed ok but there were also some red line failure lines in the dialogue as they were being installed. I rebooted the phone via fastboot but this just resulted in it booting direct to twrp as before. I tried normal boot from twrp but it still booted straight back to twrp. I then tried selecting normal boot from the fastboot, normal, recovery option menu accessed on the Leagoo T5 by powering off the phone and then pressing the pwr and vol+ buttons together but this still resulted in it booting straight to twrp. I then decided to uninstall twrp by flashing the stock firmware recovery image to try to boot from stock recovery. I did same and rebooted from fastboot and it booted to system.
The bad news is there is an imei failure message and the sim is not connecting to the network.I googled imei failure and saw that its can happen when firmware is changed. I installed the "mobileuncle" app but according to a youtube video I watched, when I tap "Engineer Mode" there should be 2 further options available, one being MTK Mode. I am only getting one option "Engineering Mode (Android) which when I select just results in being returned to the previous menu. please say this is not a major problem!
Click to expand...
Click to collapse
It could be many reasons why device didn´t boot to system. Then to flash it you had to format data + flash DM-verity. Also is possible that this TWRP version is not completely suitable for your device or is unable to mount/unmount partitions correctly, you have to check from where you downloaded it and if some users are experiencing similar issues with it.
As per you IMEI lost, better is ever take a backup of the NVRAM through TWRP before to go further then it´ll be easy to recover it. In almost all firmwares for mediatek devices you´ll fnd inside the zips SPFT and SN Writer that is to recover your IMEI. Your IMEI is not really lost only got actually covered by blank codes due to a bad/incorrect flashing/wrong sequence firmware, so be careful what you do with Mobile Uncle tool if you´re not experimented with otherwise you´ll lost permanently.
SubwayChamp said:
It could be many reasons why device didn´t boot to system. Then to flash it you had to format data + flash DM-verity. Also is possible that this TWRP version is not completely suitable for your device or is unable to mount/unmount partitions correctly, you have to check from where you downloaded it and if some users are experiencing similar issues with it.
As per you IMEI lost, better is ever take a backup of the NVRAM through TWRP before to go further then it´ll be easy to recover it. In almost all firmwares for mediatek devices you´ll fnd inside the zips SPFT and SN Writer that is to recover your IMEI. Your IMEI is not really lost only got actually covered by blank codes due to a bad/incorrect flashing/wrong sequence firmware, so be careful what you do with Mobile Uncle tool if you´re not experimented with otherwise you´ll lost permanently.
Click to expand...
Click to collapse
I got into engineering mode via dialer code. CDS option was missing from connectivity. I installed https://m.apkpure.com/cds-mobile/com.doubleapaper.cds.cds_mobile but CDS is still missing from engineering mode
pcfreeze said:
I got into engineering mode via dialer code. CDS option was missing from connectivity. I installed https://m.apkpure.com/cds-mobile/com.doubleapaper.cds.cds_mobile but CDS is still missing from engineering mode
Click to expand...
Click to collapse
Sorry, just realised that this is the wrong app! nothing to do with cds in engineering mode! I triedhttps://apkcombo.com/common-data-service/com.mediatek.connectivity/
but got message that the file was corrupted and it would not install