Hey everyone, so I woke up Saturday morning to a wonderful surprise, and am just getting around to letting everyone know and maybe throw their suggestions my way!
Device: Tmo LG V10, H901
Recovery: [TWRP] Recovery: V10_H901_pplus [V3.0.2-0] [08/16/2016]
ROM: [ROM] [STOCK] [H901] V10_H901_V20J_Stock_Custom_2e [08/15/2016]; V10_H901_V20J_Stock_Custom_2e-signed
Root: Systemless Instructions - How to - 08/08/2016
Xposed: Systemless Xposed, see root guide above
Friday night, I was using my T-Mobile V10 like normal. No recent modifications, no new apps, adjustments, etc... Plug it into the charger and go to bed for the night. No issues right?
I wake up Saturday and the screen is blank. The phone isn't responding to the power button, so I hold the Vol-Down+Vol-Up+Power down to reboot it.
The phone won't reboot. So I pull the battery, and throw it back in.
Phone hits the LG logo, yey!
But it never moves from the LG logo
So at this point, I try booting into Recovery (TWRP) and the phone seems to not be responding to my button commands. It hits the boot logo and never does anything else.
I tried to boot into Download mode, nothing, just sitting on the logo.
After messing with the phone, with and without a USB cable attached to my laptop, I finally get the device into Fastboot.
In fastboot, I can run commands, but since I am on V20J, I am unable to flash or boot TWRP
I was also able to get into download mode when plugged into my PC only.
So down below, I will go over all the stuff I have tried.
Modes I can enter-
Fastboot
Download Mode (USB)
Stuff I tried-
LG Bridge Update
Update says it succeeds
Still does not boot
When I reconnect LG Bridge again, it says an error occurred and wants to update again
Direct .img flash via Fastboot
Using the steps from this post
Unable to flash, FAILED (remote:unknown command) due to V20J I believe
Flash V20J .tot via LGUP
It seems to flash successfully, but the phone still doesn't boot
So I left for the T-Mobile store Saturday, phone not booting, just stuck on the logo.
They are Warrantying the phone, so I am just waiting on a back-ordered replacement now.
EDIT: The Plot Thickens....
So I thought I would fire up the phone this morning, maybe try some other updates/flashes again, maybe something will happen.
Now I cant even get into Download Mode (USB) anymore.
It shows Download Mode on the screen, then the phone just reboots.
Additionally, on first boot I received some sort of error on the screen, but it went away so fast I couldn't read it.
Now I can't get that error to come back for the life of me...
I am just so confused now. The phone has a mind of its own.
My brother had 2 V10's that did that. Replaced under warranty.
Exact thing happened to me back on pre mm.. I got into twrp after many many many tries.. Flashed an old back up and phone booted. I was able to get into the phone long enough to relock bootloader before it started the same crap... Warrantied it out and that was that..
Yikes. Making me scared once this warranty is up.... Would hate to just lose a phone randomly for no reason!
Swizzle82 said:
Exact thing happened to me back on pre mm.. I got into twrp after many many many tries.. Flashed an old back up and phone booted. I was able to get into the phone long enough to relock bootloader before it started the same crap... Warrantied it out and that was that..
Click to expand...
Click to collapse
Can you plz guide how you relocked bootloader? I am rooted and using custom rom. Should I first install stock kdz and then give command via fastboot or it must be done with root? Thanks
Waxim1 said:
Can you plz guide how you relocked bootloader? I am rooted and using custom rom. Should I first install stock kdz and then give command via fastboot or it must be done with root? Thanks
Click to expand...
Click to collapse
You can relock via fastboot using the command
Code:
fastboot oem lock
Use the below command to check your current status
Code:
fastboot getvar unlocked
I believe it even says these commands on the screen when in fastboot.
Fenopy said:
You can relock via fastboot using the command
Code:
fastboot oem lock
Use the below command to check your current status
Code:
fastboot getvar unlocked
I believe it even says these commands on the screen when in fastboot.
Click to expand...
Click to collapse
Thnks I jav read these but need to know if i should b on stock rom before locking or what? And any known issue while trying relocking it?
Related
OK, I will start off by saying I have (nearly) completely screwed myself.
I have a P769 (TMO; does this mean BK?).
I followed this (http://forum.xda-developers.com/showthread.php?p=38677123http://forum.xda-developers.com/showthread.php?p=38677123) to root the device and successfully made it through (using V20D KDZ).
Then then tried to flash this ROM (http://forum.xda-developers.com/showthread.php?t=2335984). Unforunately, I did not have an unlocked bootloader and now I am receiving a Security Error at boot. Even more unfortunate is that I did NOT do a backup so I am truly in a bad place now.
I tried to run through the first step of rooting but the software will not detect the phone as being connected and tells me to connect the USB cable. I have installed the drivers that are in that post but admittedly I may have updated them after rooting.
At this point I only have access to fastboot so I am trying that method but I cannot find any system.img files to be able to flash the system partition.
What do I do now? Can anyone help me? I have exhausted every Google search and XDA search. I may be missing something but I feel I am in a very bad place now and need to get this phone back up and running.
thchipmunk said:
OK, I will start off by saying I have (nearly) completely screwed myself.
I have a P769 (TMO; does this mean BK?).
I followed this (http://forum.xda-developers.com/showthread.php?p=38677123http://forum.xda-developers.com/showthread.php?p=38677123) to root the device and successfully made it through (using V20D KDZ).
Then then tried to flash this ROM (http://forum.xda-developers.com/showthread.php?t=2335984). Unforunately, I did not have an unlocked bootloader and now I am receiving a Security Error at boot. Even more unfortunate is that I did NOT do a backup so I am truly in a bad place now.
I tried to run through the first step of rooting but the software will not detect the phone as being connected and tells me to connect the USB cable. I have installed the drivers that are in that post but admittedly I may have updated them after rooting.
At this point I only have access to fastboot so I am trying that method but I cannot find any system.img files to be able to flash the system partition.
What do I do now? Can anyone help me? I have exhausted every Google search and XDA search. I may be missing something but I feel I am in a very bad place now and need to get this phone back up and running.
Click to expand...
Click to collapse
A system.img is to big to flash in fastboot. Follow Lelus directions http://forum.xda-developers.com/showpost.php?p=43021469&postcount=5
Sent from my LGMS769 using xda app-developers app
kuma82 said:
A system.img is to big to flash in fastboot. Follow Lelus directions http://forum.xda-developers.com/showpost.php?p=43021469&postcount=5
Sent from my LGMS769 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the suggestion. I just tried it and I get an error"
Updating is not possible any longer due to a fatal error while the LG Mobile Phone Software Update.
Click to expand...
Click to collapse
I am still getting the security error even though other threads said I should be able to get rid of it.
Is it possible to create a custom update.zip to flash with?
When I do the recovery it returns my phone as a P769BKGO if that helps with anything.
thchipmunk said:
Thanks for the suggestion. I just tried it and I get an error"
I am still getting the security error even though other threads said I should be able to get rid of it.
Is it possible to create a custom update.zip to flash with?
Click to expand...
Click to collapse
What os are you running also what kdz are you trying to flash ?
Lelus said:
What os are you running also what kdz are you trying to flash ?
Click to expand...
Click to collapse
I am running 32-bit Windows 7 Professional Service Pack 1. I tried flashing V20D_00.kdz (using the offline flash) as well as the V10G_00.kdz and V10E_00.kdz.
Using the offline flash method I constantly get the error of cannot connect to phone no matter how many times I restart the PC or phone and unplug USB.
thchipmunk said:
I am running 32-bit Windows 7 Professional Service Pack 1. I tried flashing V20D_00.kdz (using the offline flash) as well as the V10G_00.kdz and V10E_00.kdz.
Using the offline flash method I constantly get the error of cannot connect to phone no matter how many times I restart the PC or phone and unplug USB.
Click to expand...
Click to collapse
you already flashed ics xloader and uboot with fastboot and kdz files names are all CAPS right ?
Lelus said:
you already flashed ics xloader and uboot with fastboot and kdz files names are all CAPS right ?
Click to expand...
Click to collapse
All caps, correct.
Should I do fastboot and then run the offline method?
I did do the fastboot then tried the recovery phone option from the support tool.
I did find a recovery I made that included (for some reason) only the recovery and boot.
thchipmunk said:
All caps, correct.
Should I do fastboot and then run the offline method?
I did do the fastboot then tried the recovery phone option from the support tool.
I did find a recovery I made that included (for some reason) only the recovery and boot.
Click to expand...
Click to collapse
Don't worry about stock recovery it's useless, just flash ics xloader and uboot http://forum.xda-developers.com/showthread.php?t=2292828 option #5
, put your phone into s/w upgrade mode and try offline method
Lelus said:
Don't worry about stock recovery it's useless, just flash ics xloader and uboot http://forum.xda-developers.com/showthread.php?t=2292828 option #5
, put your phone into s/w upgrade mode and try offline method
Click to expand...
Click to collapse
I'll reboot and then try that again. I'll check back afterwards.
Should I do anything extra like start the offline flash from scratch as far as drivers? I'm not even sure where to begin in regards to what drivers/files to remove.
Thank you! Thank you! Thank you!
Now I just need to figure out the screen calibration.
Also, what can I do with this now? Do I need to unlock the bootloader to load custom ROMs without getting a security error?
Sorry for my lack of knowledge. My last phone was a Bionic and that was the easiest phone to root and add a ROM to.
unfortunately i find myself in this situation
gettin security error after what i assume was me trying to flash on a locked bootloader
anyway, i can't figure this out, the whole flashing fastboot and what not
i read through the readme and installed the drivers for the "other/unknown" device that pops up
this is what i try to do next
open up start.bat
enter 5 and hit enter
remove battery from phone (as instructed) and hit any key
boot phone into sw upgrade (holding vol up and plugging in usb cable)
device seems to be picked up and i see the "wait 5 seconds" (german?) and the image is revered horizontally on my phone
now after 4/5 seconds it says "waiting for device", which then i put the battery in
but NOTHING happens after this, it hangs at "waiting for device"
can someone please tell me what i'm doing wrong?
otherwise i think i'm left with a totally effed lg optimus l9
rotatorkuf said:
unfortunately i find myself in this situation
gettin security error after what i assume was me trying to flash on a locked bootloader
anyway, i can't figure this out, the whole flashing fastboot and what not
i read through the readme and installed the drivers for the "other/unknown" device that pops up
this is what i try to do next
open up start.bat
enter 5 and hit enter
remove battery from phone (as instructed) and hit any key
boot phone into sw upgrade (holding vol up and plugging in usb cable)
device seems to be picked up and i see the "wait 5 seconds" (german?) and the image is revered horizontally on my phone
now after 4/5 seconds it says "waiting for device", which then i put the battery in
but NOTHING happens after this, it hangs at "waiting for device"
can someone please tell me what i'm doing wrong?
otherwise i think i'm left with a totally effed lg optimus l9
Click to expand...
Click to collapse
Odds are, you are doing nothing wrong. Check your android version, if you are on 4.2+ (JellyBean) you can't unlock your bootloader quite yet. Here is the thread you should keep track of at the moment http://forum.xda-developers.com/showthread.php?t=2277639&page=152
Insert battery more quickly
rotatorkuf said:
unfortunately i find myself in this situation
gettin security error after what i assume was me trying to flash on a locked bootloader
anyway, i can't figure this out, the whole flashing fastboot and what not
i read through the readme and installed the drivers for the "other/unknown" device that pops up
this is what i try to do next
open up start.bat
enter 5 and hit enter
remove battery from phone (as instructed) and hit any key
boot phone into sw upgrade (holding vol up and plugging in usb cable)
device seems to be picked up and i see the "wait 5 seconds" (german?) and the image is revered horizontally on my phone
now after 4/5 seconds it says "waiting for device", which then i put the battery in
but NOTHING happens after this, it hangs at "waiting for device"
can someone please tell me what i'm doing wrong?
otherwise i think i'm left with a totally effed lg optimus l9
Click to expand...
Click to collapse
I've found that the process completes if you put the battery back in , right after you reconnect the USB.
mven45 said:
I've found that the process completes if you put the battery back in , right after you reconnect the USB.
Click to expand...
Click to collapse
hi iam in the same boat have you figured any thing out please help i also may have found away if you by chance had your lg pc suit installed and setup prior to this mishap
maso321 said:
hi iam in the same boat have you figured any thing out please help i also may have found away if you by chance had your lg pc suit installed and setup prior to this mishap
Click to expand...
Click to collapse
If you're running a Windows 8 OS, that's the reason it's not working.
Sent from my LGMS769 using XDA Premium 4 mobile app
rotatorkuf said:
unfortunately i find myself in this situation
gettin security error after what i assume was me trying to flash on a locked bootloader
anyway, i can't figure this out, the whole flashing fastboot and what not
i read through the readme and installed the drivers for the "other/unknown" device that pops up
this is what i try to do next
open up start.bat
enter 5 and hit enter
remove battery from phone (as instructed) and hit any key
boot phone into sw upgrade (holding vol up and plugging in usb cable)
device seems to be picked up and i see the "wait 5 seconds" (german?) and the image is revered horizontally on my phone
now after 4/5 seconds it says "waiting for device", which then i put the battery in
but NOTHING happens after this, it hangs at "waiting for device"
can someone please tell me what i'm doing wrong?
otherwise i think i'm left with a totally effed lg optimus l9
Click to expand...
Click to collapse
Take out battery and USB cable from phone
Enter #5
Plug in USB when it tells you
Wait 5 seconds or less then place battery in
once in fastboot mode remove battery for a couple of seconds then replace
take out the usb press the vol + then reconnect
S/W upgrade mode achieved.
Flash accordingly. . .
Nathan.7118391 said:
Take out battery and USB cable from phone
Enter #5
Plug in USB when it tells you
Wait 5 seconds or less then place battery in
once in fastboot mode remove battery for a couple of seconds then replace
take out the usb press the vol + then reconnect
S/W upgrade mode achieved.
Flash accordingly. . .
Click to expand...
Click to collapse
Hey Nathan did you ever get your device operating again?
Sent from my LGMS769 using XDA Premium 4 mobile app
kuma82 said:
Hey Nathan did you ever get your device operating again?
Sent from my LGMS769 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Nope! I had to do a warranty exchange. I was copying the system image then I thought it finished so I unplugged the phone. May I tried my best to get the phone back but I could only get into fastboot mode, but hey lesson learned. Though I did see this tool that someone here was trying to use to flash bin and fls files in 3 minutes! But it only works for p790 Optimus black. Which sucks because I could get my phone into an inverted S/W upgrade mode (yeah I know it's on the real one) but it only lasted for about 3 minutes then shut down so doing the offline fix just took too long. I would get to about 23% install and the phone would just turn off. . so close! LOL
EDIT: YEAH got the phone to finally work! No exchange now, take that LG! Just kept trying there offline fix
Nathan.7118391 said:
Nope! I had to do a warranty exchange. I was copying the system image then I thought it finished so I unplugged the phone. May I tried my best to get the phone back but I could only get into fastboot mode, but hey lesson learned. Though I did see this tool that someone here was trying to use to flash bin and fls files in 3 minutes! But it only works for p790 Optimus black. Which sucks because I could get my phone into an inverted S/W upgrade mode (yeah I know it's on the real one) but it only lasted for about 3 minutes then shut down so doing the offline fix just took too long. I would get to about 23% install and the phone would just turn off. . so close! LOL
EDIT: YEAH got the phone to finally work! No exchange now, take that LG! Just kept trying there offline fix
Click to expand...
Click to collapse
I'm trying to restore my P769 to stock (Stuck LG logo), and getting nowhere.
How did you get the flash to work? What error did you get when the phone would turn off? How did you get the inverted S/W mode?
My phone only got to 17-20% before getting an connection error using the offline booth method, this was with both JB and ICS u-boot/boot/recovery .imgs from the P769 ROMs--should I try the steps in unlocking the bootloader to at least get to a bootable state?
Nathan.7118391 said:
Nope! I had to do a warranty exchange. I was copying the system image then I thought it finished so I unplugged the phone. May I tried my best to get the phone back but I could only get into fastboot mode, but hey lesson learned. Though I did see this tool that someone here was trying to use to flash bin and fls files in 3 minutes! But it only works for p790 Optimus black. Which sucks because I could get my phone into an inverted S/W upgrade mode (yeah I know it's on the real one) but it only lasted for about 3 minutes then shut down so doing the offline fix just took too long. I would get to about 23% install and the phone would just turn off. . so close! LOL
EDIT: YEAH got the phone to finally work! No exchange now, take that LG! Just kept trying there offline fix
Click to expand...
Click to collapse
How did you solve this? I am at the same steps, I get into mirrored software mode and then I attempt the offline fix. I have even started the offline fix early to save time. And yet it will only stay on for 2 and a half minutes or so and then shuts off. The farthest i have been able to get it to go is 41%. I have tried fastboot mode to try and send boot.img and it just says that it cannot find the boot partition. So it looks like my only option is the offline fix but it doesn't have enough time to complete. I have tried about 20 or so times how many tries did it take for you? Did you do anything special to get it to finish? any advice on how to get it to finish? Spent about 6 hrs last night trying to get this phone back up and running and this is where i am stuck. Its lame cuz i woke up to the phone like this it was fine when i went to bed. And was for months.
I pretty much screwed my phone so bad, and I can't seem to the find any solution anywhere...
Here's what I did in order:
-tried rooting it with this guy's guide [link taken down since im a new member, but it's on htconeroot dot com//htc-one-root/how-to-root-htc-one-windowsmaclinux/]
[keep in mind it's S-On with HBoot 1.55]
-found out TWRP wasn't updated so I replaced it with a newer one (2.6.3)
-now rooted device
-wanted to restore to normal stock settings so I downloaded the Guru Reset M7 1.26.502.15 and put it in my root folder
-went to recovery to install the guru reset ZIP
-things install, but touch screen doesn't work
problems now:
-can't turn off phone on main screen (tried holding down power, but doesn't restart phone past the 3 second mark)
-can't boot into bootloader from restart
-ruu doesn't work
can anyone provide me with help? please and thank you
EDIT: few things to keep in mind
-everytime i use RUU 3.17.502.3, it loads up black screen with HTC logo int he middle, then I can turn off the phone.
-when loading up, i can load into bootloader
-when choosing recovery/factory reset, it brings up the software update screen, but then goes to red triangle
-at red triangle screen, i can reboot system through android recovery system.
-back at square 1, touch screen doesn't work, etc.
All I can say is that I am in the same waters, phone stuck in bootloop, or goes to triangle of death, and PC WILL NOT recognize phone at all so without driver support, I am screwed too.
Added: All I did was unlock through HTCDev, and all hell broke loose, loaded up AIO, and phone freaked upon flashing TWRP. 1.55 HBoot, 4.3 ATT update.
hack14u said:
All I can say is that I am in the same waters, phone stuck in bootloop, or goes to triangle of death, and PC WILL NOT recognize phone at all so without driver support, I am screwed too.
Added: All I did was unlock through HTCDev, and all hell broke loose, loaded up AIO, and phone freaked upon flashing TWRP. 1.55 HBoot, 4.3 ATT update.
Click to expand...
Click to collapse
Here's a solution:
-get into bootloader mode
-fastboot
-plug usb in
-open cmd, then get to where your HTC One rooting stuff is (for example, everything was in a folder on my desktop)
-type "fastboot oem lock"
-your phone should say "relocked"
-open the latest RUU you have
-run things normally
that's how i fixed mine, lemme know if you have any more questions.
i also don't know why your phone has to be "relocked" in order to update it's software.
pztrixwsup said:
Here's a solution:
-get into bootloader mode
-fastboot
-plug usb in
-open cmd, then get to where your HTC One rooting stuff is (for example, everything was in a folder on my desktop)
-type "fastboot oem lock"
-your phone should say "relocked"
-open the latest RUU you have
-run things normally
that's how i fixed mine, lemme know if you have any more questions.
i also don't know why your phone has to be "relocked" in order to update it's software.
Click to expand...
Click to collapse
A thousand thanks, you are my new hero! And if you run the RUU, then go back and re-unlock the bootloader, it only says "unlocked" not tampered.
That's why we need to wait for the issue with Rumrunner S-off for our phones to get squared away. So we can flash other carrier or older software.
---------- Post added at 06:51 PM ---------- Previous post was at 06:40 PM ----------
Has anybody had success with Rumrunner for 3.17.502.3 yet? I have been hitting a wall and am not the only one. The phone is freezing on adb at test 2.1. We have tried flashing the RUU and doing it again, but it fails every time in the same way.
Here's what I get:
Code:
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
[PN0712000-1.55.0000]
Test 2 (ALT): Booting device
Rebooting from fastboot
Waiting for ADB (22/120)
Test 2.1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
Waiting for ADB (120/120)
ADB connection failed!!
FIX IT, yes, YOU fix it no!!!FIX IT NOW!!!!!
Reboot command failed!!
Bootloader unlock failed?
Press ENTER to exit
Specifically looking for somebody with 3.17.502.3 to chime in if they've tried it, or one of the most awesome devs that work tirelessly so we common folk may find new ways to nearly-brick our phones :silly:
hack14u said:
A thousand thanks, you are my new hero! And if you run the RUU, then go back and re-unlock the bootloader, it only says "unlocked" not tampered.
Click to expand...
Click to collapse
Yea no problem bro, i was in your position for the whole day and i stumbled upon a billion sites and eventually trial and error'd the whole way through
Check the discussion in other thread about 4.3 and s-off. We have tried quite a few different things with no luck so far. I even posted in HTC one forums in the support thread. Hoping they will release something soon for our hboot 155.
Sent from my HTC One using xda app-developers app
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
I don't know if anyone else has posted anything similar, if they have, please point me in the direction of their thread and I will piggyback off of it. I have a LG G Vista VS880 that I rooted with Kingroot. My next step was to nuke the LAF, go into fast boot and use fastboot oem unllock to unlock the bootloader so I could install custom recovery. I got as far as nuking the LAF when I had to stop and fix dinner for the kids. When I got back to the computer I forgot that I hadn't unlocked the bootloader yet and flashed the custom recovery and a magisk patched boot.img using flashify. Now it will not boot into system or recovery. I can get it to boot into fastboot mode by holding the volume up button while plugging it in but all my fastboot commands are locked. I have searched the forums and have found nothing except some info on getting into QHUSB mode by shorting out the test point but that post was for the G3 and when I took off the back plate the configuration was different and I didnt want to mees my phone up any worse than I already had. I just want to get back to stock and start over. Can someone please help or at least point me in the right direction?!?!?!? I would welcome any assistance!
Still very new to the community, so please bear with me if I miss something or make any mistakes.
Trying to flash havocOS
I flashed an unofficial version of twrp (for X657, made sure to disable verity on both vbmeta and vbmeta_system), then attempted to boot into twrp, with no luck (it just ended up booting into fastboot for some reason).
I then tried to boot into fastbootd, completely forgetting i had twrp still installed, to flash havoc from there (this is where i think i messed up, i remember reading somewhere that twrp prevents this)
Now my phone is stuck looping on the infinix logo
Tried the SP Flash Tool, but kept getting this error. Which I'm guessing is because the phone keeps restarting (mainly because "Disconnected!" shows up in the console between two instances of the same error).
Any advice?
UnequalB said:
Still very new to the community, so please bear with me if I miss something or make any mistakes.
Trying to flash havocOS
I flashed an unofficial version of twrp (for X657, made sure to disable verity on both vbmeta and vbmeta_system), then attempted to boot into twrp, with no luck (it just ended up booting into fastboot for some reason).
Click to expand...
Click to collapse
Probably you haven´t to flash vbmeta to boot to TWRP but just when you are ready to boot to system.
UnequalB said:
I then tried to boot into fastbootd, completely forgetting i had twrp still installed, to flash havoc from there (this is where i think i messed up, i remember reading somewhere that twrp prevents this)
Click to expand...
Click to collapse
You can flash the TWRP image through fastboot and then boot to it through commands.
UnequalB said:
Now my phone is stuck looping on the infinix logo
Tried the SP Flash Tool, but kept getting this error. Which I'm guessing is because the phone keeps restarting (mainly because "Disconnected!" shows up in the console between two instances of the same error).
Any advice?
Click to expand...
Click to collapse
This is the list of errors from SP Flash tool https://forum.hovatek.com/thread-439.html
Anyway, you have a tool specific for your device https://forum.hovatek.com/thread-9224.html
I guess this thread must be moved to Android General Questions.
SubwayChamp said:
Probably you haven´t to flash vbmeta to boot to TWRP but just when you are ready to boot to system.
You can flash the TWRP image through fastboot and then boot to it through commands.
Click to expand...
Click to collapse
I meant twrp prevents booting to fastbootd, it was after trying to boot into fastbootd using "fastboot reboot fastboot" that the bootloop started, right now I can't seem to get past the boot logo.
SubwayChamp said:
This is the list of errors from SP Flash tool https://forum.hovatek.com/thread-439.html
Click to expand...
Click to collapse
Weirdly enough the error i got was not listed here..
SubwayChamp said:
Anyway, you have a tool specific for your device https://forum.hovatek.com/thread-9224.html
I guess this thread must be moved to Android General Questions.
Click to expand...
Click to collapse
This method doesn't work either since the phone won't stay off for more than 7 seconds.
I'm not stuck in a bootloop as in the phone powers on, then gets stuck, or powers off again
The phone continuously powers on and off and nothing I do (apart from disconnecting the battery) stops it, even then, once the battery is back in it begins looping again...
UnequalB said:
I meant twrp prevents booting to fastbootd, it was after trying to boot into fastbootd using "fastboot reboot fastboot" that the bootloop started, right now I can't seem to get past the boot logo.
Click to expand...
Click to collapse
You don't need to reboot to fastbootd, and you can't apply ADB commands either, because your device doesn't allow it due to random reboots and due to USB debugging is disabled right now.
UnequalB said:
Weirdly enough the error i got was not listed here..
This method doesn't work either since the phone won't stay off for more than 7 seconds.
Click to expand...
Click to collapse
Not true, this is the whole idea of this kind of tools either through SP Flash tool or Infinix tool you just have to GET device can be detected, this tiny portion of time will be enough for the tools can start its job, once the tool started the device get attached without a way to get out of it. To achieve this, prepare ALL that you need for tool to work even press flash/download, connect device with PC and apply the right combination key,
Prepare device manager on Windows and check which status of connection it is passing through to better understand which mode is lacking of.
UnequalB said:
I'm not stuck in a bootloop as in the phone powers on, then gets stuck, or powers off again
The phone continuously powers on and off and nothing I do (apart from disconnecting the battery) stops it, even then, once the battery is back in it begins looping again...
Click to expand...
Click to collapse
You are not saying till now which model your device is, assuming that the bootloader is unlocked.
SubwayChamp said:
You don't need to reboot to fastbootd, and you can't apply ADB commands either, because your device doesn't allow it due to random reboots and due to USB debugging is disabled right now.
Not true, this is the whole idea of this kind of tools either through SP Flash tool or Infinix tool you just have to GET device can be detected, this tiny portion of time will be enough for the tools can start its job, once the tool started the device get attached without a way to get out of it. To achieve this, prepare ALL that you need for tool to work even press flash/download, connect device with PC and apply the right combination key,
Prepare device manager on Windows and check which status of connection it is passing through to better understand which mode is lacking of.
You are not saying till now which model your device is, assuming that the bootloader is unlocked.
Click to expand...
Click to collapse
I tried again and that error seems to just be an issue with the linux version, it detected the phone fine and started writing to "super" on windows, but my laptop died, and now the phone isn't showing up on SP Flash, neither would it turn on at all.. but the charging indicator light comes on when I plug it in.
UnequalB said:
I tried again and that error seems to just be an issue with the linux version, it detected the phone fine and started writing to "super" on windows, but my laptop died, and now the phone isn't showing up on SP Flash, neither would it turn on at all.. but the charging indicator light comes on when I plug it in.
Click to expand...
Click to collapse
Well, if you interrupted the process, that's not good at all. The only you can do is keeping trying it, if your motherboard was not damaged.
hi guys i am DELTIERO from the Philippines did you allready solve the problem?
If not yet done message me on my facebook page https://www.facebook.com/del.villalobos.1/
and i will help you im here veltech san carlos negross occidental phil
Help please! I flashed a gapps zip file using flashify on my infinix smart 5 x657 (Running on lineageos gsi android 12) then the phone just went off. and it not turning on. but it shows the charging indicator light when i connect it to power.
I've tried disconnecting the battery still nothing
what possible solution is there for this?