Hey guys, so first of all, consider me a noob with everything related to samsung devices, i used to root xperia devices, but now wanna try rooting my sm-g900h but i have a few questions about the process and a few possibilites from you savvy lot.
Pre-requisites :
- device has usb debugging mode on
- has unlocked bootloader
- computer has device drivers
//Do i need anything else ?
Questions :
1. I would like to install a custom recovery too (idk how that works using the odin program), so after having installed said recovery would i be able to root my device using it ? (flashing the needed rom and the CF rooting module ?)
2. When i try flashing android 4.4 on my device, odin seems to get stuck at the "initialisation" step every time. (as i've said, i'm new to odin and such) After reading around, a few tips were said about removing the battery before going into flashmode then putting it in once odin detects it but still to no avail. What am i doing wrong while flashing the custom rom ?
Any help would be greatly appreciated,
Thanks.
Go to the below link for rooting
http://forum.xda-developers.com/showthread.php?t=2696537
Got to the below link to download custom recovery (TWRP)
https://dl.twrp.me/klte/
Instructions to flash recovery
Download the tar file
Put phone in download mode
open odin select AP or PDA depending on the odin version
Select the Tar file
Click start
Satsana said:
Hey guys, so first of all, consider me a noob with everything related to samsung devices, i used to root xperia devices, but now wanna try rooting my sm-g900h but i have a few questions about the process and a few possibilites from you savvy lot.
Pre-requisites :
- device has usb debugging mode on
- has unlocked bootloader
- computer has device drivers
//Do i need anything else ?
Questions :
1. I would like to install a custom recovery too (idk how that works using the odin program), so after having installed said recovery would i be able to root my device using it ? (flashing the needed rom and the CF rooting module ?)
2. When i try flashing android 4.4 on my device, odin seems to get stuck at the "initialisation" step every time. (as i've said, i'm new to odin and such) After reading around, a few tips were said about removing the battery before going into flashmode then putting it in once odin detects it but still to no avail. What am i doing wrong while flashing the custom rom ?
Any help would be greatly appreciated,
Thanks.
Click to expand...
Click to collapse
androidtweaker1 said:
Go to the below link for rooting
http://forum.xda-developers.com/showthread.php?t=2696537
Got to the below link to download custom recovery (TWRP)
https://dl.twrp.me/klte/
Click to expand...
Click to collapse
Ok so first things first, i finally managed to root my phone, (my knox counter tripped, =1 now) but i think it soft-bricked my phone since i found myself in a bootloop.
After trying to access the recovery (volume up + home + power buttons) nothing happened, so tried flashing a new recovery, following the link u provided, but i still cannot seem to be able to get into the recovery.
Am i doing something wrong ?
Thx a lot for your help
Try this
1) Flash stock firmware using odin
2) Flash recovery from the my previous post
3) Root using odin using file from this link. It your model specific file. I had given root file for KLTE model previously may be that's causing the bootloop.
Satsana said:
Ok so first things first, i finally managed to root my phone, (my knox counter tripped, =1 now) but i think it soft-bricked my phone since i found myself in a bootloop.
After trying to access the recovery (volume up + home + power buttons) nothing happened, so tried flashing a new recovery, following the link u provided, but i still cannot seem to be able to get into the recovery.
Am i doing something wrong ?
Thx a lot for your help
Click to expand...
Click to collapse
androidtweaker1 said:
Try this
1) Flash stock firmware using odin
2) Flash recovery from the my previous post
3) Root using odin using file from this link. It your model specific file. I had given root file for KLTE model previously may be that's causing the bootloop.
Click to expand...
Click to collapse
Well finally managed to familiarize myself with odin (from a noobs perspective of course hehe) But yeah that's what i've done, then flashed cwm recovery, cause that's actually the only one that didn't cause a bootloop in my case.. and rooted it again via the chain fire's method all over again =3.
Thank you guys very very much for your help and for your precious time,
Helped me quite the bit ;3
Great! :highfive:
Satsana said:
Well finally managed to familiarize myself with odin (from a noobs perspective of course hehe) But yeah that's what i've done, then flashed cwm recovery, cause that's actually the only one that didn't cause a bootloop in my case.. and rooted it again via the chain fire's method all over again =3.
Thank you guys very very much for your help and for your precious time,
Helped me quite the bit ;3
Click to expand...
Click to collapse
androidtweaker1 said:
Great! :highfive:
Click to expand...
Click to collapse
If i may ask one last question that isn't related to this thread, it would be how would i be able to access the phone via adb (i already have everything installed for it of course ) without the phone being turned on
On my old sony phone we had this fastboot mode for example so we could use the fastboot command interface =o.
In the case of samsung devices there seems to be only the odin mode/recovery options and i can't detect the phone from odin mode and via the recovery it's detected [using the "update from adb" option] but using this, the options are quite limited (i can only use the command : adb sideload <module_to_flash> =/)
[in my case i would like to do a nandroid backup through adb but i need to be able to first detect my phone (and without having the phone booted on the system)]
Thanks a bunch though, for everything
You can do a nandroid backup using CWM
Satsana said:
If i may ask one last question that isn't related to this thread, it would be how would i be able to access the phone via adb (i already have everything installed for it of course ) without the phone being turned on
On my old sony phone we had this fastboot mode for example so we could use the fastboot command interface =o.
In the case of samsung devices there seems to be only the odin mode/recovery options and i can't detect the phone from odin mode and via the recovery it's detected [using the "update from adb" option] but using this, the options are quite limited (i can only use the command : adb sideload <module_to_flash> =/)
[in my case i would like to do a nandroid backup through adb but i need to be able to first detect my phone (and without having the phone booted on the system)]
Thanks a bunch though, for everything
Click to expand...
Click to collapse
androidtweaker1 said:
You can do a nandroid backup using CWM
Click to expand...
Click to collapse
Tried doing one using cwm right now, 5GB and still not enough space =O have to do it all over again =.='
But isn't there any way to access phone via adb without it being turned on ? =o
If you want ADB access do the below.
Ensure you have the USB drivers installed
Go to settings>about phone>build number>tap build number 7 times
Go back to settings>developer options>select usb debugging
Now connect phone to PC> there will be a prompt displayed on your phone select okay
ADB drivers will be installed. Thats it
Now you have ADB access
You can take a backup even when the phone is turned on via ADB
Satsana said:
Tried doing one using cwm right now, 5GB and still not enough space =O have to do it all over again =.='
But isn't there any way to access phone via adb without it being turned on ? =o
Click to expand...
Click to collapse
androidtweaker1 said:
If you want ADB access do the below.
Ensure you have the USB drivers installed
Go to settings>about phone>build number>tap build number 7 times
Go back to settings>developer options>select usb debugging
Now connect phone to PC> there will be a prompt displayed on your phone select okay
ADB drivers will be installed. Thats it
Now you have ADB access
You can take a backup even when the phone is turned on via ADB
Click to expand...
Click to collapse
So if somehow i softbrick my phone there won't be any possible way to use adb ? =o
You can have ADB access if you put your phone in recovery mode (power+volume up+home button) even if the phone is soft bricked. But USB debugging should be enabled.
Satsana said:
So if somehow i softbrick my phone there won't be any possible way to use adb ? =o
Click to expand...
Click to collapse
androidtweaker1 said:
You can have ADB access if you put your phone in recovery mode (power+volume up+home button) even if the phone is soft bricked. But USB debugging should be enabled.
Click to expand...
Click to collapse
Thx a bunch ;3 again
Related
Hi,
Have the LG G2 D802 and previously had rooted and installed CWM 6.0.4.4. I left it with stock rom afterwards. I made the mistake of clicking for the OTA update and now I continually boot into CWM recovery.
I tried wiping cache, dalvik cache, factory wipe, etc to no avail. I cannot access phone through ADB while I'm in CWM (even after going into sideloader) and cannot get into download mode (if I push volume up and plug in usb cord it gets stuck on LG loading screen. If I hold power down it resets back into CWM). USB mount doesn't work.
I searched through the forums (and saw others who have similar issue) but haven't seen a solution. I know this was solved for TWRP in the below:
http://forum.xda-developers.com/showthread.php?t=2451696
but I'm guessing I'm probably SOL but just wanted to have a last check if anyone had come up with a solution.
The only thing that I'm potentially trying is that when I plug in to the computer while in CWM it does detect the device but can't install the drivers. Previously I was able to connect to it via ADB going through the normal route when phone was working properly on my computer so I know the drivers should be good so I'm guessing just through CWM it doesn't work properly. I've tried installing all the latest drivers but no luck also. Has anyone gotten ADB to work when in CWM recovery mode on the D802? Thanks in advance.
Yingy said:
The only thing that I'm potentially trying is that when I plug in to the computer while in CWM it does detect the device but can't install the drivers. Previously I was able to connect to it via ADB going through the normal route when phone was working properly on my computer so I know the drivers should be good so I'm guessing just through CWM it doesn't work properly. I've tried installing all the latest drivers but no luck also. Has anyone gotten ADB to work when in CWM recovery mode on the D802? Thanks in advance.
Click to expand...
Click to collapse
Try installing the PdaNet drivers and see if you have any luck. Otherwise maybe try another computer. Good luck!
Fixed!
jz3 said:
Try installing the PdaNet drivers and see if you have any luck. Otherwise maybe try another computer. Good luck!
Click to expand...
Click to collapse
Great suggestion with PdaNet drivers! You are a lifesaver. Though the normal drivers through LG website didn't work, the PdaNet drivers allowed me to install the drivers when in CWM recovery mode and it allowed me to connect via ADB and fix the issue!! Thanks so much!!!!
For those who have similar issues, I did the below steps:
1. While connected to computer in CWM recovery, install the drivers via PdaNet (these replace any original LG drivers)
http://forum.xda-developers.com/showthread.php?t=1983470
2. Connect to phone via ADB while still connected in CWM recovery (see below ADB download if you didn't already have it or forgot where it was)
http://forum.xda-developers.com/showthread.php?t=2317790
3. While connected via ADB you can use the same method as in the below thread (use the first one).
http://forum.xda-developers.com/showthread.php?t=2451696&nocache=1
All thanks to respective thread owners!
Yingy said:
Great suggestion with PdaNet drivers! You are a lifesaver. Though the normal drivers through LG website didn't work, the PdaNet drivers allowed me to install the drivers when in CWM recovery mode and it allowed me to connect via ADB and fix the issue!! Thanks so much!!!!
For those who have similar issues, I did the below steps:
1. While connected to computer in CWM recovery, install the drivers via PdaNet (these replace any original LG drivers)
http://forum.xda-developers.com/showthread.php?t=1983470
2. Connect to phone via ADB while still connected in CWM recovery (see below ADB download if you didn't already have it or forgot where it was)
http://forum.xda-developers.com/showthread.php?t=2317790
3. While connected via ADB you can use the same method as in the below thread (use the first one).
http://forum.xda-developers.com/showthread.php?t=2451696&nocache=1
All thanks to respective thread owners!
Click to expand...
Click to collapse
Hello, I had the same problem too with the OTA and i have TWRP. Followed your instructions because my computer can't recognize the phone. Everything worked well, i am out of recovery boot loop but now i am stuck in LG Logo. Please help.
I had to try it a few times but thank you for this i finally got it and back up and running perfectly!
alvingaoat said:
Hello, I had the same problem too with the OTA and i have TWRP. Followed your instructions because my computer can't recognize the phone. Everything worked well, i am out of recovery boot loop but now i am stuck in LG Logo. Please help.
Click to expand...
Click to collapse
If you can get into download mode follow the directions here: http://optimusforums.com/threads/guide-complete-guide-to-unbrick-your-soft-bricked-g2-f320.9232
You will need the TOT file and corresponding DLL for your specific phone.
Yingy said:
Great suggestion with PdaNet drivers! You are a lifesaver. Though the normal drivers through LG website didn't work, the PdaNet drivers allowed me to install the drivers when in CWM recovery mode and it allowed me to connect via ADB and fix the issue!! Thanks so much!!!!
For those who have similar issues, I did the below steps:
1. While connected to computer in CWM recovery, install the drivers via PdaNet (these replace any original LG drivers)
http://forum.xda-developers.com/showthread.php?t=1983470
2. Connect to phone via ADB while still connected in CWM recovery (see below ADB download if you didn't already have it or forgot where it was)
http://forum.xda-developers.com/showthread.php?t=2317790
3. While connected via ADB you can use the same method as in the below thread (use the first one).
http://forum.xda-developers.com/showthread.php?t=2451696&nocache=1
All thanks to respective thread owners!
Click to expand...
Click to collapse
Help!
Same problem here, but until step 3 I cannot do that, possibly because I am using CWM recovery not TWRP?
ANy suggestion? Many thanks!!
samuel_wong_1 said:
Help!
Same problem here, but until step 3 I cannot do that, possibly because I am using CWM recovery not TWRP?
ANy suggestion? Many thanks!!
Click to expand...
Click to collapse
You have to do the commands that are in the first box of that post in ADB on your computer.
Just tried this and worked beautifully. Thanks OP.
Had a similar issue last night then thankfully a fellow nerd mentioned if you hold power and vol down then hold where the home screen would be on your blank device screen it will pull up factory reset which if you accept will put you into your recovery. Saved my ass last night thought I was dunzo.
If u don't have any roms to flash this will do u no good and you'll have to go the download mode route
Sent from my VS980 4G using Tapatalk
---------- Post added at 02:28 AM ---------- Previous post was at 02:23 AM ----------
chakra said:
OK
1. Turn device off by holding power key down until bootloop stops.
2. Hold power, down volume and where the home key would be.
3. choose yes factory reset, should take you back to recovery....
Click to expand...
Click to collapse
Here is original instructions that got me back into recovery
Sent from my VS980 4G using Tapatalk
i have the same problem. G2 D802 (asia), CWM, bootloop after update, tried the PdaNet but it couldnt connect to my phone. said that usb debugging is not on, how do i turn it on with my phone stuck on boot loop? need help please
seaniglesia said:
i have the same problem. G2 D802 (asia), CWM, bootloop after update, tried the PdaNet but it couldnt connect to my phone. said that usb debugging is not on, how do i turn it on with my phone stuck on boot loop? need help please
Click to expand...
Click to collapse
Not sure if it'll help but you can also try the koush driver referenced here: http://forum.xda-developers.com/showthread.php?t=2564012&highlight=koush+com&page=2
You could also try going into sideload mode in CWM (not sure if it does anything though, I didn't need to do that, google sideload to see if you aren't familiar with it). Good luck.
Thanks dude, now my phone back to normal! Thanks for the guide
Yingy said:
Not sure if it'll help but you can also try the koush driver referenced here: http://forum.xda-developers.com/showthread.php?t=2564012&highlight=koush+com&page=2
You could also try going into sideload mode in CWM (not sure if it does anything though, I didn't need to do that, google sideload to see if you aren't familiar with it). Good luck.
Click to expand...
Click to collapse
Great! i thought I had a very expensive brick in my hand! LG rigntone was music to my ears when it turned on!
Saved my G2
Yingy said:
Great suggestion with PdaNet drivers! You are a lifesaver. Though the normal drivers through LG website didn't work, the PdaNet drivers allowed me to install the drivers when in CWM recovery mode and it allowed me to connect via ADB and fix the issue!! Thanks so much!!!!
For those who have similar issues, I did the below steps:
1. While connected to computer in CWM recovery, install the drivers via PdaNet (these replace any original LG drivers)
http://forum.xda-developers.com/showthread.php?t=1983470
2. Connect to phone via ADB while still connected in CWM recovery (see below ADB download if you didn't already have it or forgot where it was)
http://forum.xda-developers.com/showthread.php?t=2317790
3. While connected via ADB you can use the same method as in the below thread (use the first one).
http://forum.xda-developers.com/showthread.php?t=2451696&nocache=1
All thanks to respective thread owners!
Click to expand...
Click to collapse
Woke up this morning to forced update that I had ignored for a couple days. Caused recovery loop in CM. Followed to a T and now I'm back
Thanks to all !
Thanks All
I have fixed my phone by the help of you. I have also sent the below post to the QA section:
http://forum.xda-developers.com/showthread.php?p=49591370
Regards and thanks again.
Selim
jz3 said:
Try installing the PdaNet drivers and see if you have any luck. Otherwise maybe try another computer. Good luck!
Click to expand...
Click to collapse
Yingy said:
Great suggestion with PdaNet drivers! You are a lifesaver. Though the normal drivers through LG website didn't work, the PdaNet drivers allowed me to install the drivers when in CWM recovery mode and it allowed me to connect via ADB and fix the issue!! Thanks so much!!!!
For those who have similar issues, I did the below steps:
1. While connected to computer in CWM recovery, install the drivers via PdaNet (these replace any original LG drivers)
http://forum.xda-developers.com/showthread.php?t=1983470
2. Connect to phone via ADB while still connected in CWM recovery (see below ADB download if you didn't already have it or forgot where it was)
http://forum.xda-developers.com/showthread.php?t=2317790
3. While connected via ADB you can use the same method as in the below thread (use the first one).
http://forum.xda-developers.com/showthread.php?t=2451696&nocache=1
All thanks to respective thread owners!
Click to expand...
Click to collapse
Many thanks! Fixed my bootlooping issue
i have the almost same problem. the difference is my phone doesnt turn on no matter what i do. no recovery, no fatboot, also my pc doesnt detect my phone so i cant use adb. i am hopeless. what can i do.
thanks!!!
Joppykid said:
Had a similar issue last night then thankfully a fellow nerd mentioned if you hold power and vol down then hold where the home screen would be on your blank device screen it will pull up factory reset which if you accept will put you into your recovery. Saved my ass last night thought I was dunzo.
If u don't have any roms to flash this will do u no good and you'll have to go the download mode route
Sent from my VS980 4G using Tapatalk
---------- Post added at 02:28 AM ---------- Previous post was at 02:23 AM ----------
Here is original instructions that got me back into recovery
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
this saved my g2!!! thanks a lot
Thanks
Yingy said:
Great suggestion with PdaNet drivers! You are a lifesaver. Though the normal drivers through LG website didn't work, the PdaNet drivers allowed me to install the drivers when in CWM recovery mode and it allowed me to connect via ADB and fix the issue!! Thanks so much!!!!
For those who have similar issues, I did the below steps:
1. While connected to computer in CWM recovery, install the drivers via PdaNet (these replace any original LG drivers)
http://forum.xda-developers.com/showthread.php?t=1983470
2. Connect to phone via ADB while still connected in CWM recovery (see below ADB download if you didn't already have it or forgot where it was)
http://forum.xda-developers.com/showthread.php?t=2317790
3. While connected via ADB you can use the same method as in the below thread (use the first one).
http://forum.xda-developers.com/showthread.php?t=2451696&nocache=1
All thanks to respective thread owners!
Click to expand...
Click to collapse
Many Many many thanks
Today when I saw software update available in the notification panel, I just hit update. Aftter my phone went into recovery loop, and never rebooted. I thought I lost my phone, I searched the internet for solutions, and I found your thread, it worked magic, now I recovered my phone
Thank you once more
Dr.saidalavi
Yingy said:
Great suggestion with PdaNet drivers! You are a lifesaver. Though the normal drivers through LG website didn't work, the PdaNet drivers allowed me to install the drivers when in CWM recovery mode and it allowed me to connect via ADB and fix the issue!! Thanks so much!!!!
For those who have similar issues, I did the below steps:
1. While connected to computer in CWM recovery, install the drivers via PdaNet (these replace any original LG drivers)
http://forum.xda-developers.com/showthread.php?t=1983470
2. Connect to phone via ADB while still connected in CWM recovery (see below ADB download if you didn't already have it or forgot where it was)
http://forum.xda-developers.com/showthread.php?t=2317790
3. While connected via ADB you can use the same method as in the below thread (use the first one).
http://forum.xda-developers.com/showthread.php?t=2451696&nocache=1
All thanks to respective thread owners!
Click to expand...
Click to collapse
OK now im stuck with the same issue, adb only see's my device as offline so i cant execute shell. How to I put it into online mode?
I ****ed up my phone today I did full wipe (formatted internal storage too, so i can't flash any rom in recovery because there is nothing) and now i've been searching hours someone who can help me? In TWRP i can't mount anything to my pc (i do not know why?) AND adb says me "devices not found" or something like that so can't push any zip-file to my phone via adb sideload. Is there any way to reapir my phone? can someone help me? Thanks alot!
There was a bug in a bunch of recent twrp releases that causes adb to not work in recovery. Patched versions have been made, try finding one for your device.
Added:
If you can't find a patched version, flash cwm or philz recovery with fastboot, adb is working on both of those. You just need a rrcovery image and do
"fastboot flash recovery <recovery-file>.img"
In fastboot mode.
let's try it out!
nvan7891 said:
There was a bug in a bunch of recent twrp releases that causes adb to not work in recovery. Patched versions have been made, try finding one for your device.
Click to expand...
Click to collapse
So u mean i need to flash new recovery version? how i can do it when my adb isn't workin? thanks!
alkkade said:
I ****ed up my phone today I did full wipe (formatted internal storage too, so i can't flash any rom in recovery because there is nothing) and now i've been searching hours someone who can help me? In TWRP i can't mount anything to my pc (i do not know why?) AND adb says me "devices not found" or something like that so can't push any zip-file to my phone via adb sideload. Is there any way to reapir my phone? can someone help me? Thanks alot!
Click to expand...
Click to collapse
i dont know how to fix your problem but i know how u can change the devices not found
install on your computer pdanet driver.
p.s.
i ****ed up my phone as well today i publish a post i will be thankfull if look on my problem.thanks.
alkkade said:
So u mean i need to flash new recovery version? how i can do it when my adb isn't workin? thanks!
Click to expand...
Click to collapse
See the edit to my first response. Fastboot is done in fastboot mode, not recovery, so you should be good. You just need the basic .img file of cwm or philz recovery.
If you are on win 7 try this:
http://adbdriver.com/downloads/
(Adb driver installer)
Run it when you turn adb sideload on in G2 and connect it to PC.
If it fails you still can go buy somewhere USB OTG cable (few bucks) and flash ROM from usb stick like me.
It appears that accessing fastboot pn the lg g2 is not so simple. Sorta like samsung phone deal, where a manufacturer download is used instead. From what I gather, recovery might need to be wiped to access fastboot, which you could do from terminal in twrp, but thats risky. Apparently, a lot of people have gotten stuck in fastboot mode. Best bet would be to reflash stock firmware through lg download mode. Also see this thread for a method to return to stock firmware:
http://forum.xda-developers.com/showthread.php?t=2432476
Once you are back to stock, just reroot and flash revovery, etc.
downloadmode should still work. go back to any kdz for your version
also source and versions post next time
Could someone please help.
I've just updated from KK 4.4.4. to Lp 5.0.1 via OTA updates.
Then I tried to install TWRP 2.8.6.0 using Odin 3.10.6 (and 3.09), but I can't boot into TWRP, it just goes into Android System Recovery (or whatever it's called).
Before I updated, I could successfully use TWRP, root and create/restore backups etc. But, since the OS update I can't (plus I will have lost root, as I downloaded/installed the KK ROM as a "clean install".
From looking around various sites and watching videos. I think I need to side load TWRP using ADB.
But, I've visited the Dev. site, downloaded the SDK zip files. Extracted them, but the folder that should contain the files (platforms) is empty.
So, I downloaded the exe file. It wouldn't allow me to install it as I don't have Java installed.
I downloaded and tried to install Java, but it fails to install. Just F typical.
Could someone offer an easy to follow step by step advice and maybe post the files I need to use (if I do need to use ADB).
I'm using 910F and USB debugging is allowed.
Thank you.
************ EDIT ************
Never mind. I had to flash the Lp 5.0.1 stock ROM to fix the problem and now TWRP works.
******************************
Is reactivation lock enabled? If yes, disable and try again
abdyasar said:
Is reactivation lock enabled? If yes, disable and try again
Click to expand...
Click to collapse
abdyasar said:
Is reactivation lock enabled? If yes, disable and try again
Click to expand...
Click to collapse
Thank you for your help.
The reactivation lock is disabled.
To update my OP, other things I've tried:
I've downloaded and installed the basic files for ADB as well as the full SDK.
Some site say to update the ADB files to the Google USB Drivers (found in the SDK). It just says I'm up to date when I try to find newer drivers via Device Manager.
Tried flashing CWM instead of TWRP using Odin.
Tried installing TWRP (zip) when in the Android System Recovery mode via SD card.
When using ADB. My device is listed when I type "adb devices".
But when I type "fastboot flash recovery <the name of the TWRP file .IMG> I just get "waiting for device".
I get this message if I'm in Bootloader mode or using the phone "normally".
Hopefully it works out
Firstly download TWRP from the website : https://dl.twrp.me/trltexx/twrp-2.8.6.0-trltexx.img.tar.html
Then turn your device off and remove the battery for around 10 seconds (make sure the device isn't connected to any charger or anything via the USB cable).
Then after the 10 seconds put the battery back into the device and hold the home, volume down and power button.
Once you are in download mode and it says 'Downloading', plug your device into computer using the USB cable.
Open up Odin as admin and make sure no security software is interfering; once your device shows up in Odin select 'PDA' and then browse to the directory of the recovery file.
Then press start, however while it's flashing press the volume up and home button and this should boot the device directly into recovery. This is important as sometimes stock firmware might revert to stock recovery if you don't boot into recovery at least once.
I hope this helps you out.
UPDATE:
Crap, I didn't read that it worked out XD Ignore me ;P
Battlehero said:
Firstly download TWRP from the website : https://dl.twrp.me/trltexx/twrp-2.8.6.0-trltexx.img.tar.html
Then turn your device off and remove the battery for around 10 seconds (make sure the device isn't connected to any charger or anything via the USB cable).
Then after the 10 seconds put the battery back into the device and hold the home, volume down and power button.
Once you are in download mode and it says 'Downloading', plug your device into computer using the USB cable.
Open up Odin as admin and make sure no security software is interfering; once your device shows up in Odin select 'PDA' and then browse to the directory of the recovery file.
Then press start, however while it's flashing press the volume up and home button and this should boot the device directly into recovery. This is important as sometimes stock firmware might revert to stock recovery if you don't boot into recovery at least once.
I hope this helps you out.
UPDATE:
Crap, I didn't read that it worked out XD Ignore me ;P
Click to expand...
Click to collapse
Thanks for the reply.
Yes, I did fix it by re-flashing.
But, the info will be useful if I get into a similar situation again. Or will help anyone else who's stuck.
Hi,
I rooted my ZTE Axon 7 UK version, A2017G and i accidentally formatted the system, currently i have the US version of the software running but i dont have any WIFI
thanks for the help in advance
Can't help you with the European system
But have you tried flashing B20 boot.img from tenfar tool ? Might solve your wifi issue...
If that works, it's awesome !
shia786 said:
Hi,
I rooted my ZTE Axon 7 UK version, A2017G and i accidentally formatted the system, currently i have the US version of the software running but i dont have any WIFI
thanks for the help in advance
Click to expand...
Click to collapse
djona12 said:
Can't help you with the European system
But have you tried flashing B20 boot.img from tenfar tool ? Might solve your wifi issue...
If that works, it's awesome !
Click to expand...
Click to collapse
the A2017G have a FULL FACTORY UPDATE IMAGE (B02) you guys are actually lucky in that department, us A2017U we wish had one.
here : http://forum.xda-developers.com/axon-7/how-to/a2017g-b02-update-released-europe-t3440619
i cannot seem to find tenfar tool anywhere
DrakenFX said:
the A2017G have a FULL FACTORY UPDATE IMAGE (B02) you guys are actually lucky in that department, us A2017U we wish had one.
here : http://forum.xda-developers.com/axon-7/how-to/a2017g-b02-update-released-europe-t3440619
Click to expand...
Click to collapse
i have found the tool but i think i flashed the US version of the boot image now my phone does not boot up at all,
it goes to stock recovery
if i turn the phone on then it goes to ZTE LOGO for about half a second then the screen goes blank
i can access fastboot but only through stock recovery which when i go to bootloader i cannot run any fastboot commands, even if i run fastboot reboot it does not reboot the phone at all
shia786 said:
i cannot seem to find tenfar tool anywhere
Click to expand...
Click to collapse
Got the same problem, i've formatted the system and now i can only go to the stock recovery, i can't reboot to edl mode by pressing both volume buttons doing this a Handset Diagnostic Interface (DFU) appears in my Device Manager instead of Qualcomm USB device, so i can't install a TWRP.
shia786 said:
i cannot seem to find tenfar tool anywhere
Click to expand...
Click to collapse
Cricius said:
Got the same problem, i've formatted the system and now i can only go to the stock recovery, i can't reboot to edl mode by pressing both volume buttons doing this a Handset Diagnostic Interface (DFU) appears in my Device Manager instead of Qualcomm USB device, so i can't install a TWRP.
Click to expand...
Click to collapse
As I said before, YOU GUYS have full update file posted the link (thread) about... You DON'T need @tenfar tools to use the FULL A2017G update (B02) , download the file (like 2.2gb I guess) and flashed using stock recovery.
DrakenFX said:
As I said before, YOU GUYS have full update file posted the link (thread) about... You DON'T need @tenfar tools to use the FULL A2017G update (B02) , download the file (like 2.2gb I guess) and flashed using stock recovery.
Click to expand...
Click to collapse
When I press update from SD card it comes up with cannot update from SD card, when I try to do ADB side load and says cannot read file
shia786 said:
When I press update from SD card it comes up with cannot update from SD card, when I try to do ADB side load and says cannot read file
Click to expand...
Click to collapse
Try enable " OEM Unlocking " under developers option and try again
DrakenFX said:
Try enable " OEM Unlocking " under developers option and try again
Click to expand...
Click to collapse
I cannot access the software at all, all I got is stock recovery
shia786 said:
I cannot access the software at all, all I got is stock recovery
Click to expand...
Click to collapse
Try using that same full update with twrp,
As title said you can boot only to TWRP? From there you may be able to flash the zip.
DrakenFX said:
Try using that same full update with twrp,
As title said you can boot only to TWRP? From there you may be able to flash the zip.
Click to expand...
Click to collapse
I no longer have access to TWRP recovery as I flashed stock recovery to install the firmware file using stock recovery but somehow the os got screwed up and now the only thing I have access to is stock recovery
shia786 said:
I no longer have access to TWRP recovery as I flashed stock recovery to install the firmware file using stock recovery but somehow the os got screwed up and now the only thing I have access to is stock recovery
Click to expand...
Click to collapse
You can just boot into TWRP using tenfar tools and Flash the zip.
DrakenFX said:
You can just boot into TWRP using tenfar tools and Flash the zip.
Click to expand...
Click to collapse
For me to use the tool I need to access the phone in edl mode which I cannot do because I do not have access to ADB
shia786 said:
For me to use the tool I need to access the phone in edl mode which I cannot do because I do not have access to ADB
Click to expand...
Click to collapse
and not having access to adb, you meant don't have a PC/Laptop?
Cuz there is an alternative way how to boot to " edl "
- turn your phone completely off
- press and hold Volume DOWN & UP
- plug your device to your PC/Laptop
DrakenFX said:
and not having access to adb, you meant don't have a PC/Laptop?
Cuz there is an alternative way how to boot to " edl "
- turn your phone completely off
- press and hold Volume DOWN & UP
- plug your device to your PC/Laptop
Click to expand...
Click to collapse
so what i mean by i cannot access ADB is that the phone has stock recovery in which there is no ADB functionality, i cannot access the OS so i cannot use ADB that way either,
i tried the method above to go into edl mode but it just goes onto a black screen where the led light flashed red and green and the computer does not recognise anything being plugged in, not even the system sound,
I have the correct drivers installed as i used his before when the OS was working
shia786 said:
so what i mean by i cannot access ADB is that the phone has stock recovery in which there is no ADB functionality, i cannot access the OS so i cannot use ADB that way either,
i tried the method above to go into edl mode but it just goes onto a black screen where the led light flashed red and green and the computer does not recognise anything being plugged in, not even the system sound,
I have the correct drivers installed as i used his before when the OS was working
Click to expand...
Click to collapse
Hi,
I have the exact same issue
Did you find a way to get your phone booting again ?
DrakenFX said:
and not having access to adb, you meant don't have a PC/Laptop?
Cuz there is an alternative way how to boot to " edl "
- turn your phone completely off
- press and hold Volume DOWN & UP
- plug your device to your PC/Laptop
Click to expand...
Click to collapse
That doesn't work on the A2017G, you have to use "adb reboot edl", so you see the problem. Also, the A2017G doesn't actually have an EDL mode but something very similar that's ZTE call Handset diagnostic Interface - quite why, who knows, this is ZTE after all...
I have a old phone that had been stuck at this state for a while,
`orange state, your device has been unlocked and can't be trusted. Your device will boot in 5 seconds`
Should I follow this guide to un-brick it?
https://forum.xda-developers.com/le-2/how-to/repair-hard-bricked-phone-x52x-sd-t3648348
I have tried to follow the guide but after pressing volume up and down button the phone does not boot. Only shows it is in orange state.
Also if I hold the volume down button and the power button, it shows booting in fastboot.
But the FlashOne app cannot detect any phone.
What should I do ??:crying::crying::crying::crying:
mrchow19910319 said:
I have tried to follow the guide but after pressing volume up and down button the phone does not boot. Only shows it is in orange state.
Also if I hold the volume down button and the power button, it shows booting in fastboot.
But the FlashOne app cannot detect any phone.
What should I do ??:crying::crying::crying::crying:
Click to expand...
Click to collapse
What should I do? You need to read, the answers to your questions are here a million times over. Always do your homework first. Also thank someone who helps you. Otherwise they will not continue helping you.
FlashOne: Why are you using FlashOne? You are not bricked. Also FYI, if using FlashOne , you have to be in EDL mode. not fastboot.
Now here is probably good news, since you can enter fastboot then you are very likely just fine,and you are definitely not bricked. However, you will probably end up losing any files that you had on the phone, because the user data( storage ) will most likely need to be formatted, (type yes reboot to recovery)
So my instructions are to help get your phone working again, not to recover data. Unfortunately, you didn't provide much information so I have to assume some things.
Is the bootloader unlocked?
Have you flashed custom roms before?
Which phone do you have? A Leeco X5?? A Leeco X6??
Let guess and say that maybe bootloader is unlocked, you are asking a question on XDA so maybe that is a safe guess?
What you need to do is use ADB or the the Tool all in One and flash Recovery and root. Here comes the reading part again, I can't explain everything or I will be here all day. I assume that you know how what Recovery and root is?
Download the correct TWRP Recovery for your device, if you don't know your way around ADB too well.
You can use Mauronofrio's "TOOL ALL IN ONE" for removing encryption, installing TWRP, Root, your ROM, Gapps, and even to restore to stock Recovery, or to flash a stock Rom
Read that thread for instructions or for any questions.
If your device not recognized it is a usb driver issue, ensure that device drivers are installed and You will need to reinstall the Google USB driver, and while you are at it check to make sure adb is up to date. The All in One tool can do all of this for you, its with the advanced menu section. ** You will need to temporarily disable Windows defender for installation. **
Use the All in One tool to flash Recovery, then boot to recovery.
Ensure that you have TWRP installed permanently by rebooting to Recovery and then rooting the phone.
Always reboot to Recovery and check the boxes to install TWRP when rebooting to recovery
To remove encryption you will always need to format the storage
Not wipe >> Choose Format > type yes> Reboot to Recovery)**
(If you see a message that says there is no OS installed are you sure> Click Yes, then reboot to Recovery, ignore message about no OS)
When you reboot to recovery swipe to be able to read and write to the device.
Use an OTG Usb adapter to connect a USB to your phone and flash your prefered rom, Gapps, and root. Reboot to recovery, thenn reboot to system. If you were successful, the error message will be gone and you will be able to set up the phone.
As mentioned the tool will help you with installing your rom, Gapps, and root.
The All in One Tool can completely restore your phone to stock if absolutely needed. It actually links to Mauronofrio's server and it has all of the significant EUI Stock Roms, in case you want to restore the stock rom.
Hopefully this helps you, Good luck.
tsongming said:
.
Click to expand...
Click to collapse
thank you so much for the in depth explanation.
sorry for the super delayed reply.
I will try to follow the instruction and will update here soon.
again thank you.
I have the same problem with umidigi bison, I tried to root with the mtkroot tool v2.5.8, the process ended correctly but when I turned on it showed orange, the problem is that I cannot enter with any combination of keys, it does not recognize adb, please help