Please note: This will not recover you from a bricked device. This applies to bootloops caused by modifications you made, AFTER successfully rooting.
So you changed your build.prop or deleted a system file you shouldn't have? Your phone is now constantly rebooting? Your variant doesn't have a KDZ available? Here's an easy, albeit time consuming method to recover. (without TWRP or KDZ and no data loss)
First off, if you haven't caused a bootloop yet and you are doing a lot of modifications, do the following. Go to SuperSU and allow su requests on boot. This will allow you to fix minor problems during the bootloop, such as restoring your backed up build.prop or other modified system file. Many times, people will forget to set permissions on a file, especially build.prop. This will cause a bootloop.
If you GRANTED su requests during boot in SuperSU:
Say you set the wrong permissions on build.prop:
While your phone is bootlooping, plug it into your PC, then execute the following commands:
Code:
adb shell
$ stop
$ su
# chmod 0644 /system/build.prop
# reboot
Say you screwed the build.prop up and need to restore a backup you made to your sdcard:
Code:
adb shell
$ stop
$ su
# cp /sdcard/build.prop /system/build.prop
# chmod 0644 /system/build.prop
# reboot
If you DID NOT grant su requests during boot in SuperSU (or if you have tried and failed other methods to recover):
While your phone is bootlooping, plug it into your PC, then do the following:
1. Locate the image you used to root your phone.
2. If the image is on your phone still, just re-root. Your phone will be fixed.
3. If you deleted it from your internal SD card continue to step 4.
4. Open command prompt in folder on your PC containing image, then issue the following command:
This will take a VERY long time (20-30 minutes)
Code:
adb push system_image_name.img /sdcard/system_image_name.img
Note: If you don't have adb mapped to your environment variables, move the image into your platform-tools folder, or whichever folder contains adb. Then run the above command.
5. Re-root
Can't wait to try this when i get home. I soft bricked my LG G4 with a bad system.img so i am trying to restore. Is this actually going to allow me to push the img file back to the phone even though i cant boot?
minirx7 said:
Can't wait to try this when i get home. I soft bricked my LG G4 with a bad system.img so i am trying to restore. Is this actually going to allow me to push the img file back to the phone even though i cant boot?
Click to expand...
Click to collapse
In your case I'd say 50/50. It depends if it at least gets to the part of the boot sequence which enables adb.
I KDZ back to stock, then re-rooted to fix mine. No data loss.
Sent from my VS986 using XDA Free mobile app
Meibs81 said:
I KDZ back to stock, then re-rooted to fix mine. No data loss.
Sent from my VS986 using XDA Free mobile app
Click to expand...
Click to collapse
That is a great method to use, but several variants don't have KDZs :crying:
I'm on the Sprint variant and am getting the Security Error loop. I have no system.img yet, however I can't seem to adb push anything (or see the phone with ADB at all)... am I doing something wrong?
pcrhckyman said:
I'm on the Sprint variant and am getting the Security Error loop. I have no system.img yet, however I can't seem to adb push anything (or see the phone with ADB at all)... am I doing something wrong?
Click to expand...
Click to collapse
That would not be considered a bootloop. That's a brick. I'm sorry, but in your case unless you already had a system image on your phone to flash, you are SOL until we get a TOT file.
tabp0le said:
In your case I'd say 50/50. It depends if it at least gets to the part of the boot sequence which enables adb.
Click to expand...
Click to collapse
Well i am able to access factory reset and i am able to get into download mode and see it from the send_command tool.. HOpe that means my odds are 100% instead!
minirx7 said:
Well i am able to access factory reset and i am able to get into download mode and see it from the send_command tool.. HOpe that means my odds are 100% instead!
Click to expand...
Click to collapse
Not necessarily. Download mode and factory reset(recovery) are located on different partitions than boot and system. Do you at least get to the carrier boot animation while attempting to boot? If so, your chances are good. If not, your chances are bad. The initial commands, including adb push have to be run while the phone is attempting to boot. NOT in download mode or recovery.
tabp0le said:
In your case I'd say 50/50. It depends if it at least gets to the part of the boot sequence which enables adb.
Click to expand...
Click to collapse
tabp0le said:
Not necessarily. Download mode and factory reset(recovery) are located on different partitions than boot and system. Do you at least get to the carrier boot animation while attempting to boot? If so, your chances are good. If not, your chances are bad. The initial commands, including adb push have to be run while the phone is attempting to boot. NOT in download mode or recovery.
Click to expand...
Click to collapse
I get stuck on the LG logo where the light flashes on and off. While this happens if the phone is connected to the computer i hear the USB connection sound in windows. I will be trying it in a few hours.. hope it works!
minirx7 said:
I get stuck on the LG logo where the light flashes on and off. While this happens if the phone is connected to the computer i hear the USB connection sound in windows. I will be trying it in a few hours.. hope it works!
Click to expand...
Click to collapse
You may be able to do it then. Let us know how it goes!
Delete
Peeptastic said:
Can I use this method to solve my particular problem (bypassing setup - I cannot move forward in the setup after a hard reset). Thanks (Can give you more info if you need it)
Click to expand...
Click to collapse
You may be able to. Does your phone boot? How far does it get in the booting process? If you get to initial phone setup, and can't get to the settings app to enable developer options and debugging, then you probably can't use this.. I'm not sure it would work, but you could try-During boot, debugging might enabled by default. (I'm not sure) Right when your bootanimation comes on you might be able to run the command:
Code:
adb shell stop
Then run the rest of the commands/follow this guide. It would be worth a shot.
Delete
Peeptastic said:
I will try it. I can get into the phone to the screen right after entering wifi, then it just stalls. It doesn't freeze, but it also doesn't go anywhere. This is with wifi and data (I left the phone on for a bit and data picked up). If it's related, I turned on Voice Assistance and when the phone gets to the first set up screen she says something about Google play services not working and then "Hangouts needs Google Play services". That could be why I can't move on.....
---------- Post added at 05:10 PM ---------- Previous post was at 05:07 PM ----------
I hear windows chime when it starts up, and the computer charges the phone. Running your command tells me: error: device not found.
Click to expand...
Click to collapse
How did you get in this situation to begin with? Are you able to get into settings at all?
Delete
Peeptastic said:
Factory reset because of the Google play error. Only it looks like Factory reset didn't fix it. And nope, can't get into settings because I can't get out of the set up screen (setup like when you first turn on the phone out of the box). I can get to download mode and stock recovery. As far as I know, there is no way to skip the original LG setup (clockwise button press doesn't work).
Can I adb sideload the image and try that way
Click to expand...
Click to collapse
Unfortunately that will not work. adb sideload is only for flashing .zip files.
tabp0le said:
Unfortunately that will not work. adb sideload is only for flashing .zip files.
Click to expand...
Click to collapse
Delete
every time I run the command while in bootloop it says "Device not found"
sarwaria23 said:
every time I run the command while in bootloop it says "Device not found"
Click to expand...
Click to collapse
This is what is happening to me too. I can see that the phone during boot loop is recognized. I check the device drivers and it shows up under windows as LG.
Crap. not good.
Related
Is there anyone around with a Rogers HTC Dream?
if so, could you please do a nandroid backup of your phone and sent me the files?
I can't boot my phone after messing up reflashing it with incompatable firmware
Thanks in advance!
they are here
Yep they are there and I plan to leave them on that server permanently.
would i install these using fastboot... or what would I use?
the nandroid gives me errors
it refuses to back up my data and will not restore anything
if i use nandroid-mobile.sh backup in the console it says
error reading recovery no space left on device
PurpleFries said:
would i install these using fastboot... or what would I use?
the nandroid gives me errors
it refuses to back up my data and will not restore anything
if i use nandroid-mobile.sh backup in the console it says
error reading recovery no space left on device
Click to expand...
Click to collapse
yup fastboot.
k heres what i used
fastboot flash boot boot.img
fastboot flash system system.img
restarted and
still stuck on rogers screen
no change whatsoever
When I semi-bricked my phone these are the instructions I used.
Since you can get into fastboot you should be able to reload to factory settings no problem.
should be...
hmmmm, looks like you did the correct thing.
Just to let you know, after you reload the fresh copy of boot.img and system.img it will take much longer for your phone to turn on the first time, typically 5-10 minutes. It has to re-install the OS on the phone.
thats essentially what i did
however the link you gave me did not include a data.img
DISREGARD TEMPORARILY, waiting those 5-10 minutes
it doesnt work if i just flash the boot and system
also, would i need to reflash the recovery with the stock rom? because then i need the stock recovery rom as well
PurpleFries said:
thats essentially what i did
however the link you gave me did not include a data.img
Click to expand...
Click to collapse
The data.img would be personal. It's not needed, but if you don't have when you flash your Dream it'll be like you're starting over for the first time.
it doesnt work if i just flash the boot and system
also, would i need to reflash the recovery with the stock rom? because then i need the stock recovery rom as well
Click to expand...
Click to collapse
AFAIK, the stock from is the system.img file. How lond did you leave it on the Rogers screen before you manually restarted your phone?
as of now, it's been approx 10 minutes.
after ur post edit i wiped and re-fastboot-ed the stuff
gonna let it run for about 20 minutes before i conclude its still not workin
EDIT
18 minutes so far...
not looking favorable T.T
EDIT2
yea its been 20 minutes, no change...
any other ideas?
EDIT3
30 minutes...
def not working
PurpleFries said:
as of now, it's been approx 10 minutes.
after ur post edit i wiped and re-fastboot-ed the stuff
gonna let it run for about 20 minutes before i conclude its still not workin
Click to expand...
Click to collapse
yeah after 20 minutes it's certainly too long. I think mine only took about 5 minutes, but good luck. eeep
edit: worse comes to worse, take it back to the store and tell them your phone wont turn on.
Also you might be able to get more help tomorrow on the subject. I'm a fairly big newbie here so I don't know that much. There is a way for your computer to see at what point your phone may be frozen at but I can't remember how.
edit 2:
17. It's taking forever to boot!
The first boot will take longer than normal because dexopt needs to run. If you are nervous, connect USB and run "adb logcat" to watch the progress.
Click to expand...
Click to collapse
That is from cyanogen, but it should give you some insight as to what your phone may be doing.
doesnt help
it doesnt see my device as attached.
adb devices doesnt list a device
and adb logcat tells me its waiting for devices
I'm sure ill need some sort of explanation as to why it doesnt turn on... what could I say?
also, not sure if i thanked you before, but thanks for all of the assistance
EDIT
it sees the device if it is attached in recovery mode
I still cant logcat tho
it says: /sbin/sh: exec: line 1: logcat: not found
PurpleFries said:
doesnt help
it doesnt see my device as attached.
adb devices doesnt list a device
and adb logcat tells me its waiting for devices
I'm sure ill need some sort of explanation as to why it doesnt turn on... what could I say?
also, not sure if i thanked you before, but thanks for all of the assistance
EDIT
it sees the device if it is attached in recovery mode
I still cant logcat tho
it says: /sbin/sh: exec: line 1: logcat: not found
Click to expand...
Click to collapse
I would just tell them I turned it on this morning and this happened. Ask them if they can fix it and see what happens. Mention nothing about trying to root it.
Just to make sure you're doing the steps correctly.
You're downloading the files I provided for you and placing them in your android/sdk..../tools folder right?
Then you boot the phone into fastboot?
Then I think you press the talk button to usb connect
from there you type in the commands.
Is that what you're doing?
exactly word for word.
during entering the commands:
i flash the boot and system.img
and press the back button to reboot
then i do the adb logcat and it cannot detect the device
PurpleFries said:
exactly word for word.
during entering the commands:
i flash the boot and system.img
and press the back button to reboot
then i do the adb logcat and it cannot detect the device
Click to expand...
Click to collapse
have you applied the update.zip file? Perhaps try applying that again first and then try the recover again.
which update.zip?
you never told me to install an update.zip previously
it's done through the recovery menu correct?
PurpleFries said:
which update.zip?
you never told me to install an update.zip previously
it's done through the recovery menu correct?
Click to expand...
Click to collapse
Well from that earlier psot I showed you that linked to HOFO step #1 had this.
Assuming you installed the update.zip before or after rooting (you can do it at any point really), now you can begin the recovery. First, enter the following into the command prompt
Click to expand...
Click to collapse
So it looks like the phone has to be rooted before you can apply the backup and to root the phone correctly you need the update.zip file.
The instructions to install the update.zip file and the file itself can be found here
Perhaps try to follow all of those steps, well skip the nandroid backup and see if your phone boots after that. If it does not but you can install the update.zip file then try the recovery method you have been trying.
tried updating with the files given (update.zip, boot.img, recovery.img)
could not go into recovery mode, would not boot
tried updating with update.zip and other files from before(update.zip, boot.img, system.img)
still no booting
my phone was, however already root-ed before it stopped working
PurpleFries said:
tried updating with the files given (update.zip, boot.img, recovery.img)
could not go into recovery mode, would not boot
tried updating with update.zip and other files from before(update.zip, boot.img, system.img)
still no booting
my phone was, however already root-ed before it stopped working
Click to expand...
Click to collapse
Sorry then. I'm out of ways to help. I don't really know all that much about the process. Perhaps your phone is slightly different than the rest of our Rogers phones so my backup files wont work on yours.
how long ago did you get it?
this thursday
Was playing around at work today, getting ready to install the edited build.prop. I had renamed the old one to build.prop.bak, and somehow managed to restart the phone without putting a new one in.
The phone stays at the M screen, and I can get into the standard recovery (i thought I had the custom one installed...guess not). Is there anyway I can push a new build.prop file through standard recovery??
The only thing I have tried to do is reapply the 2.2 update.zip I was running, which didn't work due to signature verification failure.
Don't know. You may have to hard reset, or apply the sbf.
terriermike said:
Was playing around at work today, getting ready to install the edited build.prop. I had renamed the old one to build.prop.bak, and somehow managed to restart the phone without putting a new one in.
The phone stays at the M screen, and I can get into the standard recovery (i thought I had the custom one installed...guess not). Is there anyway I can push a new build.prop file through standard recovery??
The only thing I have tried to do is reapply the 2.2 update.zip I was running, which didn't work due to signature verification failure.
Click to expand...
Click to collapse
Is adb accesible with the standard recovery??
Meaning if you type in:
Code:
adb devices
Do your device show up?
If so, you can use adb to push the build.prop to /system
If not, sbf
I will try that. I've never used adb before, just terminal from the phone. I went on the google adb site and could't find a download link though...can you post it? I just see a bunch of tutorials on how to use it.
terriermike said:
I will try that. I've never used adb before, just terminal from the phone. I went on the google adb site and could't find a download link though...can you post it? I just see a bunch of tutorials on how to use it.
Click to expand...
Click to collapse
http://code.google.com/p/xdroidx/wiki/HowToSetUpADB
So for the first time in my history of Android's since the G1 I've finally bricked a phone. Apparently there was an OTA for the T-Mo devices and I managed to hamfist my notification and accept it.
Needless to say I'm now stuck permanently booting into TWRP. I've tried some various troubleshooting methods including doing what I thought was a successful sideload of the TMo-Stock-Rooted Rom. It showed a successful push and ran through the install but I got a message kicked back saying "No OS installed". Now I've seen other users receive this same message and after rebooting anyway they got their ROM to boot.
No such luck for me, after it reboots (post sideload install) it shows system as unmounted and then just boots back into recovery ad nauseum...I'm really at a loss here folks.
Have you already tried this?...
http://forum.xda-developers.com/showthread.php?t=2451696
redduc900 said:
Have you already tried this?...
http://forum.xda-developers.com/showthread.php?t=2451696
Click to expand...
Click to collapse
Hadn't tried it previously but I just attempted to run the ADB command and it still boots into TWRP. I'm not sure if those commands worked or not however. I got a big wall of text in terminal after the second command.
FWIW, on every reboot System is unmounted (Data & Cache remain mounted) but I can check it. Seems that it's irrelevant whether its checked or not.
Tried a sideload using the Stock Rooted 110G image and still nothing. Sideload appears to go, and install goes through without error but reboots only into TWRP with System unmounted.
k4ylr said:
Hadn't tried it previously but I just attempted to run the ADB command and it still boots into TWRP. I'm not sure if those commands worked or not however. I got a big wall of text in terminal after the second command.
FWIW, on every reboot System is unmounted (Data & Cache remain mounted) but I can check it. Seems that it's irrelevant whether its checked or not.
Click to expand...
Click to collapse
can you get the phone to shut off and stay off. If you can then simply put it in download mode and use LG flash tool to flash stock rom back on. Please let me know if this is an option if not I will try and figure out something else
joewaz said:
can you get the phone to shut off and stay off. If you can then simply put it in download mode and use LG flash tool to flash stock rom back on. Please let me know if this is an option if not I will try and figure out something else
Click to expand...
Click to collapse
I can get it to shut off and stay off no problem. I'm on OSX at the moment and likely won't be able to get to a PC until the 9th. I'll definitely give the LG Flash tool method a try when I can.
k4ylr said:
I can get it to shut off and stay off no problem. I'm on OSX at the moment and likely won't be able to get to a PC until the 9th. I'll definitely give the LG Flash tool method a try when I can.
Click to expand...
Click to collapse
yes I am afraid you are stuck in till you can get to a real man's computer lol. I'm just kidding though my girlfriend has a stupid Apple and I was stuck with the same problem I had to drive 50 miles to where I used to live to pick up my laptop to fix this. But the LG flash tool works like a charm and you will not have any problems. Just make sure that you read the procedure for the Verizon phone. If you are not surelookup the forum wink Link
joewaz said:
yes I am afraid you are stuck in till you can get to a real man's computer lol. I'm just kidding though my girlfriend has a stupid Apple and I was stuck with the same problem I had to drive 50 miles to where I used to live to pick up my laptop to fix this. But the LG flash tool works like a charm and you will not have any problems. Just make sure that you read the procedure for the Verizon phone. If you are not surelookup the forum wink Link
Click to expand...
Click to collapse
Haha I hear you. I moved recently and the apt I'm in doesn't have ethernet drops so I had to order up a PCI wireless nic card =\ I'll dig around for the LG flash tool guides and see what I can learn.
I was hesitant to even flash a recovery because of how ass backwards LG made it for us in the first place =\
k4ylr said:
Haha I hear you. I moved recently and the apt I'm in doesn't have ethernet drops so I had to order up a PCI wireless nic card =\ I'll dig around for the LG flash tool guides and see what I can learn.
I was hesitant to even flash a recovery because of how ass backwards LG made it for us in the first place =\
Click to expand...
Click to collapse
brother I feel your pain. But when you get everything all situated I will tell you the easiest way to install a backup recovery program. It is an app in the App Market called free GEE... One click and bam you have a backup lol.. You may want to use freegee to make sure twrp is installed right.. It will just over write all the files and correct any wrongs... Freegee.. Remember that!!
k4ylr said:
So for the first time in my history of Android's since the G1 I've finally bricked a phone. Apparently there was an OTA for the T-Mo devices and I managed to hamfist my notification and accept it.
Needless to say I'm now stuck permanently booting into TWRP. I've tried some various troubleshooting methods including doing what I thought was a successful sideload of the TMo-Stock-Rooted Rom. It showed a successful push and ran through the install but I got a message kicked back saying "No OS installed". Now I've seen other users receive this same message and after rebooting anyway they got their ROM to boot.
No such luck for me, after it reboots (post sideload install) it shows system as unmounted and then just boots back into recovery ad nauseum...I'm really at a loss here folks.
Click to expand...
Click to collapse
No worries friend! I almost went crazy last night trying to find a fix!! Here what fixed mine!
You need to be EXTREMELY CAUTIOUS when typing this in:
Go to Advanced in TWRP and run Terminal
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit go
after it pushes through again type:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
then hit enter and reboot.
coldcrush390 said:
No worries friend! I almost went crazy last night trying to find a fix!! Here what fixed mine!
You need to be EXTREMELY CAUTIOUS when typing this in:
Go to Advanced in TWRP and run Terminal
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit go
after it pushes through again type:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
then hit enter and reboot.
Click to expand...
Click to collapse
Are those commands pushable through ADB? For whatever reason when I get to the Terminal Command through TWRP it wants me to navigate to a different directory and there's no command line to type things in. I've always been a CWM flash a .zip kinda guy so digging into ADB is all new for me.
coldcrush390 said:
no worries friend! I almost went crazy last night trying to find a fix!! Here what fixed mine!
You need to be extremely cautious when typing this in:
Go to advanced in twrp and run terminal
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit go
after it pushes through again type:
Dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
then hit enter and reboot.
Click to expand...
Click to collapse
this worked perfectly!!! Thanks sooooo much!!!!!!!!!!!
k4ylr said:
Are those commands pushable through ADB? For whatever reason when I get to the Terminal Command through TWRP it wants me to navigate to a different directory and there's no command line to type things in. I've always been a CWM flash a .zip kinda guy so digging into ADB is all new for me.
Click to expand...
Click to collapse
Don't navigate anywhere, I thought the same thing just tap on select below and follow the commands. Take your time doing it and don't rush!
---------- Post added at 07:24 PM ---------- Previous post was at 07:23 PM ----------
jwagman1 said:
this worked perfectly!!! Thanks sooooo much!!!!!!!!!!!
Click to expand...
Click to collapse
Your welcome
What about if your in CWR? How can I bring my wife's phone? It tried to update itself and I'm stuck on recovery
coldcrush390 said:
Don't navigate anywhere, I thought the same thing just tap on select below and follow the commands. Take your time doing it and don't rush!
Click to expand...
Click to collapse
Ran the terminal side commands, got to LG Splash and we're sitting there now. We'll see how long it sits or if it's a boot loop.
**EDIT**
10 minutes sitting at the LG splash no go. I managed to snag an interim wifi adapter for my desktop so I'm going to try the Flash tool posted from earlier and see if it works.
Update
I was able to bring the phone back with those commands using adb thank you guys for your help.
djeddieone said:
How can I do this on add? What would be the commands on adb? I'm on CWR so I can't use twrp
Click to expand...
Click to collapse
Can't say for sure, I had seen some to run this way:
adb shell
then the 2 lines of prompt. I'm stuck on a boot loop so I'm trying to get the Flash Tool method to work. I should have not messed with G2 in retrospect lol, way too little support and far too big of a PITA to bother.
coldcrush390 said:
No worries friend! I almost went crazy last night trying to find a fix!! Here what fixed mine!
You need to be EXTREMELY CAUTIOUS when typing this in:
Go to Advanced in TWRP and run Terminal
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit go
after it pushes through again type:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
then hit enter and reboot.
Click to expand...
Click to collapse
This worked for me. I tried several other methods from other threads but could not complete them for various reasons.
This also is the simplest method as it installed the update without my having to download it again.
djeddieone said:
Update
I was able to bring the phone back with those commands using adb thank you guys for your help.
Click to expand...
Click to collapse
Did you have any driver issues? I'm stuck in the same situation booting just to ClockworkMod Recovery after an attempted OTA update. Can't connect to Win7 because driver can't configure properly even with the latest drivers installed. Connects file with my wife's working LG G2 so I know the drivers are right. Also tried to get into download mode with no luck. I'm stuck. Does anyone know how to get pass this?
Problem fixed!!!!
eat314 said:
Did you have any driver issues? I'm stuck in the same situation booting just to ClockworkMod Recovery after an attempted OTA update. Can't connect to Win7 because driver can't configure properly even with the latest drivers installed. Connects file with my wife's working LG G2 so I know the drivers are right. Also tried to get into download mode with no luck. I'm stuck. Does anyone know how to get pass this?
Click to expand...
Click to collapse
OK. Finally got it working. Wish I had figured it out before I factory reset my phone. My main issue was the driver. Even though I had the right LG drivers installed, it just would not recognize it properly. Here is what I had to do after a failed device configuration.
- Go to Computer Management and find the failed device and Update Driver.
- Choose to manually select device and then select Have Disk.
- Find and select \Program Files (x86)\LG Electronics\LG VZW United Driver\64BitADB\lgandadb.inf (Tried the other xxxadb.inf files but none worked)
- When the list of devices is presented, scroll down and select LGE Mobile Server Single ADB Interface
Your device should now be recognized by adb. Follow the steps provided by others above in this thread and you should be good to go. Worked for me. Good luck.
Thank you all for the great knowledge base. Saved me $500!!! ::good:
I was having some issue with a rom and figured it was time to reflash/flash a new one. I started the process in TWRP and Aroma froze half way through. I had to reboot. Unfortunately I had already wiped my rom. I can get to fastboot, but I cannot get anywhere else at all. Can anyone point me to a way to get back into recovery?
Should have mentioned, H918.
codman2728 said:
I was having some issue with a rom and figured it was time to reflash/flash a new one. I started the process in TWRP and Aroma froze half way through. I had to reboot. Unfortunately I had already wiped my rom. I can get to fastboot, but I cannot get anywhere else at all. Can anyone point me to a way to get back into recovery?
Should have mentioned, H918.
Click to expand...
Click to collapse
Download adb to your computer. Connect the phone to the computer. Open cmd and use cd or pushd to point cmd to the directory where adb is. Once you are in that directory (from cmd), use " adb reboot recovery "
If what jinkerz9430 suggests doesn't work,
You may have to go back to stock. Here is how to do it for 10j:
https://forum.xda-developers.com/sho...80&postcount=8
Then you reroot as before.
Fixed!
jinkerz9430 said:
Download adb to your computer. Connect the phone to the computer. Open cmd and use cd or pushd to point cmd to the directory where adb is. Once you are in that directory (from cmd), use " adb reboot recovery "
Click to expand...
Click to collapse
Thanks for the response. I ended up rooting around for a long while after this post and settled on using LGUP and found the correct files to reflash to stock. Adb would not work at all. I could get fastboot access, but that is gimped. No driver update would fix the adb problem. I've never had this issue before, with any phone. LG seems to make things more difficult than necessary. I miss Samsung.
Thanks
androiddiego said:
If what jinkerz9430 suggests doesn't work,
You may have to go back to stock. Here is how to do it for 10j:
https://forum.xda-developers.com/sho...80&postcount=8
Then you reroot as before.
Click to expand...
Click to collapse
That link seems to 404. I'd be interested in reading that though, if it isn't actually a 404. I believe what you are referring to is what I did though LOL. I found the kdz and dll, and used LGUP to get flashed back to stock. I'll never let it out of my sight again.
codman2728 said:
Thanks for the response. I ended up rooting around for a long while after this post and settled on using LGUP and found the correct files to reflash to stock. Adb would not work at all. I could get fastboot access, but that is gimped. No driver update would fix the adb problem. I've never had this issue before, with any phone. LG seems to make things more difficult than necessary. I miss Samsung.
Click to expand...
Click to collapse
If you flashed stock with lgup then everything is back to factory settings. Is this is the case, then the autorization you gave to your computer via usb debbug (where the prompt appears if the device is connected to a other device without authorization asking you whether you want to authorize it or not). Is also back to factory settings. Which means not even developer mode is on. But after you turn developer mode on and usb debbug then connect the phone to the computer and it will ask you once again for authorization
[/B]
codman2728 said:
That link seems to 404. I'd be interested in reading that though, if it isn't actually a 404. I believe what you are referring to is what I did though LOL. I found the kdz and dll, and used LGUP to get flashed back to stock. I'll never let it out of my sight again.
Click to expand...
Click to collapse
That's it!
Hi All,
In the best interest to provide clarity I'm creating this quick and easy tutorial on how to root your Razer Phone 2 after the Pie Upgrade. Please send me any feedback to improve this post, we need to build up a strong community.
*As usual, I'm not responsible of any damage or brick to your phone, do it at your own risk.
Pre-Requirements:
-Be sure to have at least 70% of charges... or plug your phone to power
-Backup anything you consider important
-Already installed Pie Upgrade via OTA or Side Loaded
-Enable Developer Options
• Open Phone "Settings" and scroll down.
• You will see an option "Build Number".
• Simply tap on it 7 times to enable it on your Android Oreo based device.
• Your device immediately display a message on screen that will say "You are now a developer".
• The Developer Option is now available in the Settings>System>Developer Options. Enjoy!
- Install Android Drivers (https://developer.android.com/studio/run/win-usb) and ADB, I personally recommend -[TOOL]Minimal ADB and Fastboot [2-9-18] - https://forum.xda-developers.com/showthread.php?t=2317790
-Unlock Bootloader
• To enable OEM unlock, go to Settings > Developer options and check Enable OEM unlock
• Using ADB commands reboot on bootloader
adb reboot bootloader
• After reboot completes follow phone menus and select "UNLOCK BOOTLOADER"; accept all warnings, after restart you have completed the unlock.
Root and Installing Magisk
Since our phone doesn't have a proven customer recovery fully working (Ex TWRP) Magisk needs to be installed by manually patching the device boot image.
Making leverage of Warrior1988 post [Root Magisk Pie Update For Unlocked Devices] all credits to him. Download the image from his post
• Boot in fastboot mode To boot into fastboot, press and hold the Power button + Volume Down Keys for few seconds; Copy the image on the same folder as your ADB and Run the following commands:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot
Install Magisk Download the apk and install it as usual on your RP2, that should be all.
DONE!!!! You now have a unleashed the beast! Please send me any recommendations to improved this guide.
chpimentelpr said:
Install Android Drivers and ADB
Click to expand...
Click to collapse
Your link has everything necessary for this step, right? Direct link to version 1.4.3 is here: https://androidfilehost.com/?fid=746010030569952951
Or are drivers and ADB two separate downloads?
chpimentelpr said:
• To enable OEM unlock, go to Settings > Developer options and check Enable OEM unlock
Click to expand...
Click to collapse
I assume this is where we plug our phone into our computer?
chpimentelpr said:
• Using ADB commands reboot on bootloader
Click to expand...
Click to collapse
For anyone dumb and new like me, I think this is with cmd.exe in Windows. Win+S -> type "cmd" (without quotation marks) and hit enter. Once open, you want to navigate to ADB, which you've already installed via the above instructions.
So your cmd will say:
C:\Users\YourName>
And you want to get to ADB, so you'll type "cd" (without quotation marks) which means you want to change directories, and then "cd adb" (if its in C:\ directory) or "cd [whatever the path is to the ADB folder]\adb"
Assuming it was directly in C:, you should see something like:
C:\adb>
Now you want to type "adb devices" to make sure it sees your phone is plugged in. You should see: "list of devices attached - [model] device" or something.
Now you're ready to go with the instructions starting at "adb reboot bootloader." If I'm wrong about this, someone less new and dumb than I am please correct me.
chpimentelpr said:
• Copy the image on the same folder as your ADB and Run the following commands:
fastboot flash*boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot
Click to expand...
Click to collapse
I'm confused on this one. The first one has "flash*boot_a," but the second one has "flash boot_b" without the * symbol. What does the * do, and what happens if we mess it up? Sorry if that's a dumb question.
AbsoluteContingency said:
Your link has everything necessary for this step, right? Direct link to version 1.4.3 is here: https://androidfilehost.com/?fid=746010030569952951
Or are drivers and ADB two separate downloads?
I assume this is where we plug our phone into our computer?
For anyone dumb and new like me, I think this is with cmd.exe in Windows. Win+S -> type "cmd" (without quotation marks) and hit enter. Once open, you want to navigate to ADB, which you've already installed via the above instructions.
So your cmd will say:
C:\Users\YourName>
And you want to get to ADB, so you'll type "cd" (without quotation marks) which means you want to change directories, and then "cd adb" (if its in C:\ directory) or "cd [whatever the path is to the ADB folder]\adb"
Assuming it was directly in C:, you should see something like:
C:\adb>
Now you want to type "adb devices" to make sure it sees your phone is plugged in. You should see: "list of devices attached - [model] device" or something.
Now you're ready to go with the instructions starting at "adb reboot bootloader." If I'm wrong about this, someone less new and dumb than I am please correct me.
I'm confused on this one. The first one has "flash*boot_a," but the second one has "flash boot_b" without the * symbol. What does the * do, and what happens if we mess it up? Sorry if that's a dumb question.
Click to expand...
Click to collapse
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot
Warrior1988 said:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot
Click to expand...
Click to collapse
No asterisk. Cool. Got it. Thank you, dude.
The drivers are the regular ones for android nothing specific, they can be downloaded from their SDK https://developer.android.com/studio/run/win-usb
App root detection?
If I root my Razer phone 2 using this guide, will certain apps like banking apps, and rideshare apps be able to detect root?
Bounty33 said:
If I root my Razer phone 2 using this guide, will certain apps like banking apps, and rideshare apps be able to detect root?
Click to expand...
Click to collapse
You can use magisk to hide the root from those apps. In general banking app are not affected by root. Google pay could be affected, but I don't use it so can't be sure. And you can always unroot.
AbsoluteContingency said:
No asterisk. Cool. Got it. Thank you, dude.
Click to expand...
Click to collapse
Did you rooted? Anything missing on the guide? I want make it as useful as possible so feedback is welcome.
chpimentelpr said:
Did you rooted? Anything missing on the guide? I want make it as useful as possible so feedback is welcome.
Click to expand...
Click to collapse
I have not, but I've been really sick and useless. I think I'll try tonight and let you know how it goes. Thanks for the guide, dude.
---------- Post added at 02:50 PM ---------- Previous post was at 02:45 PM ----------
Wait, yes, I do have a question. I download the drivers, and I download the Fastboot ADB thing. What do I do with the drivers? Do they just install in Windows like anything else, and that allows me to connect to the phone?
AbsoluteContingency said:
I have not, but I've been really sick and useless. I think I'll try tonight and let you know how it goes. Thanks for the guide, dude.
---------- Post added at 02:50 PM ---------- Previous post was at 02:45 PM ----------
Wait, yes, I do have a question. I download the drivers, and I download the Fastboot ADB thing. What do I do with the drivers? Do they just install in Windows like anything else, and that allows me to connect to the phone?
Click to expand...
Click to collapse
Yes, install them as any other driver.
After rooting can you relock the boot loader or will that brick the phone?
ndragon798 said:
After rooting can you relock the boot loader or will that brick the phone?
Click to expand...
Click to collapse
Not sure, but why you want to relock the boot.
chpimentelpr said:
Not sure, but why you want to relock the boot.
Click to expand...
Click to collapse
Mostly to get rid of the startup message
Very nice. I've rooted a ton of phones over the years, but they had more established communities and had well-explained (and tested) methods of rooting. The previous guide posted (that you referenced) was fine enough, but it was very much lacking a couple prerequisites that I was wondering/concerned about. This guide has cleared all of that up for me, and I now feel confident about rooting this phone.
Just as soon as I charge up the phone and install the OTA I've been avoiding until now... lol. Hoping somebody will make a Magisk module to move the clock back to where it belongs (if they haven't already).
EDIT: Just wanted to add my success story to this. Only thing I had to do that wasn't listed in the instructions (but makes sense) is that fastboot didn't work until I enabled USB Debugging (again, after the wipe and reboot), and I had to very manually tell the computer which driver to use (ADB) after that. Didn't have that issue for the bootloader instructions beforehand (that time, the driver worked automatically), so I figured I'd mention it.
chpimentelpr said:
Not sure, but why you want to relock the boot.
Click to expand...
Click to collapse
Also is there a way to turn back on the preboot authentication. Pretty much I just want to maintain full encryption and the built in security while having root.
ndragon798 said:
Also is there a way to turn back on the preboot authentication. Pretty much I just want to maintain full encryption and the built in security while having root.
Click to expand...
Click to collapse
I don't believe encryption is supported at the moment, and I don't encourage you to try it until TWRP is fully supported since you may end up in a boot loop. I'm eagerly waiting for the full encryption capability, so I will let you know as soon as something come up.
This has to be......one of the most usefull and noob friendly guides i have ever seen.....
You sir....are a God
Thank You.
ChronosTrigger said:
This has to be......one of the most usefull and noob friendly guides i have ever seen.....
You sir....are a God
Thank You.
Click to expand...
Click to collapse
i'm glad it helps.
Alright so after fighting with windows for a few hours, I discovered that my ADB was severely outdated.... Lesson learned there.
After getting the new boot image installed, though, I hit another problem... WiFi refuses to work. The toggle switch in the statusbar, nor the toggle in the system settings, will bring my wifi to life. Which is weird! Because I got through setup just fine, connected to wifi and signed into google... Yet now all wifi functionality has vanished. I tried a factory reset, to no avail. I'm gonna have to restore the factory boot image and start all over... But for now, figured I'd ask if anyone else has run into this weird bug?
***update***
I've now gone and flashed the global image for 8.1.0 to the phone... and it's telling me the OS is up to date???? How do I get back to pie?? It's late here and I've got wifi back now... but I'm stumped. Any help would be so greatly appreciated!
xttweaponttx said:
Alright so after fighting with windows for a few hours, I discovered that my ADB was severely outdated.... Lesson learned there.
After getting the new boot image installed, though, I hit another problem... WiFi refuses to work. The toggle switch in the statusbar, nor the toggle in the system settings, will bring my wifi to life. Which is weird! Because I got through setup just fine, connected to wifi and signed into google... Yet now all wifi functionality has vanished. I tried a factory reset, to no avail. I'm gonna have to restore the factory boot image and start all over... But for now, figured I'd ask if anyone else has run into this weird bug?
***update***
I've now gone and flashed the global image for 8.1.0 to the phone... and it's telling me the OS is up to date???? How do I get back to pie?? It's late here and I've got wifi back now... but I'm stumped. Any help would be so greatly appreciated!
Click to expand...
Click to collapse
I doubt the issue with the wifi is related with the image, since it doesn't have anything to do with it. If your phone doesn't detect the update you will need to sideload it. Then try the root guide again. Let us know how it goes, it the first time I hear something wrong with WIFI after rooting.