Had a problem with audio playback (volume always high no matter what). Decide to flash. PAC for my Sprint LS980. I see this:
Seems to be a lot of confusion so I'll clear things up..
ZV7->ZV8->ZVA is how the ota history goes, with ZVB on the way.
If you're on stock ZVA, your aboot (bootloader) may not be downgraded, in that case, use FreeGee from Play Store to install a recovery, it will automatically downgrade your aboot.
if you have the ZVA Radio, just flash furnace or dr87's kernel after you flash an AOSP ROM, all done.
Click to expand...
Click to collapse
Sorce: http://forum.xda-developers.com/showthread.php?t=2669074
Seeing the last sentance, I think that if I flash ZVA Radio, SlimKat ROM (the one that causes me problems) and then dr87's kernel I could try a ZVA experience. I flashed SlimKat again becuase I was going to change anyway, I wanted to try it with ZVA.
Tell myself why not, I do it.
Fails but I didnt pay much attention. I reboot.
Stuck in fastboot mode and cant escape. Recovery is a no-go.
Tried flashing both ZV7aboot.img and twrp2.6.3.0.img into their appropriate partitions (boot and recovery).
Still having problems, but now I cant do any button combination (except DownloadMode. Cant turn off) after ZV7aboot.img flash.
I dont want to erase my memory (~26GB of valuable data). Is there a way to flash a ZV8Radio.zip from fastboot? I think thats my problem, but Im not too sure. Just access to recovery would allow my to fix my problems.
Thanks anyone for any help! I think I really screwed myself over this time. Thanks everyone!
Edit: Anyone know where to get a boot.img and system.img for the Sprint LS980?
zv7_aboot.img isn't a boot.img, it's the bootloader. Use FreeGee to install twrp, it will handle the aboot for you. Then you can take advantage of the last sentence.
Savoca said:
zv7_aboot.img isn't a boot.img, it's the bootloader. Use FreeGee to install twrp, it will handle the aboot for you. Then you can take advantage of the last sentence.
Click to expand...
Click to collapse
I am stuck in fastboot. No recovery. Download mode is also accessable.
Which of the following would help:
* System.img and Boot.img (where to find em?)
* A kernel .img (Do they exist?)
* Flashing the ZV7 or 8 aboot.img oncemore with twrp.img again?
Thanks for coming to help! It means a lot.
RevolcFael4 said:
I am stuck in fastboot. No recovery. Download mode is also accessable.
Which of the following would help:
* System.img and Boot.img (where to find em?)
* A kernel .img (Do they exist?)
* Flashing the ZV7 or 8 aboot.img oncemore with twrp.img again?
Thanks for coming to help! It means a lot.
Click to expand...
Click to collapse
If you can boot into a rom, use FreeGee to install twrp. If you can't boot into rom and recovery, you need to flashtool.
Savoca said:
If you can boot into a rom, use FreeGee to install twrp. If you can't boot into rom and recovery, you need to flashtool.
Click to expand...
Click to collapse
Flashtools is asking for login and password. ?
Does this mean I have to wipe all user data in order to use it?
Edit: Do you know where System.img and Boot.img could be downloaded? I think its my only hope.
RevolcFael4 said:
Flashtools is asking for login and password. ?
Does this mean I have to wipe all user data in order to use it?
Edit: Do you know where System.img and Boot.img could be downloaded? I think its my only hope.
Click to expand...
Click to collapse
You didn't read the tutorial.
http://downloads.codefi.re/autoprime/LG/LG_G2
Savoca said:
You didn't read the tutorial.
http://downloads.codefi.re/autoprime/LG/LG_G2
Click to expand...
Click to collapse
Thanks for the link! That was extremely helpful.
What I did to gain access to twrp again was:
Download boot.img from the link.
Download aboot.img from link.
Download twrp.img (but this isnt necessary, file is already available on phone. No need.)
* Enter command 'fastboot flash boot boot.img'
* (If you hold power it starts showing LG Logo.)
* Go back to Fastboot. Enter command 'fastboot flash aboot aboot.img'
* Now TWRP access is regained! Phone doesnt boot normally, must flash ROM and stuff again.
Thanks a lot! This was an okay first fastboot experience.
Soft Bricked Sprint LS980?
Hello, I'm having a similar problem. I haven't had a phone for a couple years since tinkering with my Evo and thought I still knew what I was doing with my new G2. That proved to be incorrect.
I had it semi rooted. (I followed the instructions using Ioroot and Kingo) I wasn't able to change APN and use GSM for Metro PCS
After reading up about the spark patch I followed a tutorial (not very well obviously) and managed to get the phone will it will no longer boot.
I can get it into bootloader, and a frozen in download mode. otherwise it just hangs at the LG logo.
Is there a way to recover from bootloader?
I copied twrp-2.6.3.2-g2spr.img and zv7-aboot.img to the phone and did the following.
Here are the commands I used with the guide. I looks like I was using 2 different guides at once..... :/
Originally Posted by darkpoe View Post
This phone does not use Mass storage mode, it uses MTP, you will see it as a phone inside windows explorer and when you click into it you will see "internal storage" this internal storage is what I am referring to as the root of the sdcard (as they are as well)
Also, dont blame me if your phone dies, all this stuff will void your warranty of your phone and your toaster!
Hit the build number under about phone --> software until developer mode is enabled
goto developer mode turn on mtp mode
go download twrp from there site http://www.teamw.in/project/twrp2/197
I used kingo but cant link on xda ,, google it .. its on cnet as well
get http://koush.com/post/universal-adb-driver install (works on all windows)
get http://www.xda-developers.com/androi...oot-installer/has good quick adb install it
copy the downloaded openrecovery for sprint onto the phone directly into the "root" folder (root folder being like when you look at yoru C: drive in windows explorer that is the root folder under linux), when you plug into the pc, make sure in mtp mode
with phone still plugged in run kingo and root it
it will reboot
with phone plugged in run "adb usb" from command prompt on pc (from the link for adb that it installed, it will open a command prompt for you in the proper folder when you click it)
approve adb connection on phone
then run "adb shell" from command prompt on pc
type su, approve it on phone
paste this next line exactly at the prompt
********** this is the line I used from a different guide ***** dd if=/sdcard/zv7-aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
dd if=/sdcard/openrecovery-twrp-2.6.3.2-g2spr.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
let it flash
it will say bytes copied and you will be good
type reboot inside the shell
the phone will reboot
I use goo manager from play store to boot into recovery, I dont even know the key combo for it yet.
Any help would be appreciated, thank you.
---------- Post added at 02:59 AM ---------- Previous post was at 02:06 AM ----------
x_lord said:
Hello, I'm having a similar problem. I haven't had a phone for a couple years since tinkering with my Evo and thought I still knew what I was doing with my new G2. That proved to be incorrect.
I had it semi rooted. (I followed the instructions using Ioroot and Kingo) I wasn't able to change APN and use GSM for Metro PCS
After reading up about the spark patch I followed a tutorial (not very well obviously) and managed to get the phone will it will no longer boot.
I can get it into bootloader, and a frozen in download mode. otherwise it just hangs at the LG logo.
Is there a way to recover from bootloader?
I copied twrp-2.6.3.2-g2spr.img and zv7-aboot.img to the phone and did the following.
Here are the commands I used with the guide. I looks like I was using 2 different guides at once..... :/
Originally Posted by darkpoe View Post
This phone does not use Mass storage mode, it uses MTP, you will see it as a phone inside windows explorer and when you click into it you will see "internal storage" this internal storage is what I am referring to as the root of the sdcard (as they are as well)
Also, dont blame me if your phone dies, all this stuff will void your warranty of your phone and your toaster!
Hit the build number under about phone --> software until developer mode is enabled
goto developer mode turn on mtp mode
go download twrp from there site http://www.teamw.in/project/twrp2/197
I used kingo but cant link on xda ,, google it .. its on cnet as well
get http://koush.com/post/universal-adb-driver install (works on all windows)
get http://www.xda-developers.com/androi...oot-installer/has good quick adb install it
copy the downloaded openrecovery for sprint onto the phone directly into the "root" folder (root folder being like when you look at yoru C: drive in windows explorer that is the root folder under linux), when you plug into the pc, make sure in mtp mode
with phone still plugged in run kingo and root it
it will reboot
with phone plugged in run "adb usb" from command prompt on pc (from the link for adb that it installed, it will open a command prompt for you in the proper folder when you click it)
approve adb connection on phone
then run "adb shell" from command prompt on pc
type su, approve it on phone
paste this next line exactly at the prompt
********** this is the line I used from a different guide ***** dd if=/sdcard/zv7-aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
dd if=/sdcard/openrecovery-twrp-2.6.3.2-g2spr.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
let it flash
it will say bytes copied and you will be good
type reboot inside the shell
the phone will reboot
I use goo manager from play store to boot into recovery, I dont even know the key combo for it yet.
Any help would be appreciated, thank you.
Click to expand...
Click to collapse
Found this: Worked like a charm.
–]rdsqc22 2 points 23 days ago
Alright, sorry to comment on something 3 months old, but I just had this problem and managed to solve it.
When in the mode described above, you are still able to use Fastboot. Get a linux computer and install fastboot.
Then, go here: http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware/zvc_partitions
Download the images for laf, aboot, boot, and recovery.
type the following commands in fastboot:
fastboot erase boot
fastboot erase aboot
fastboot erase recovery
fastboot erase laf
fastboot flash boot 6-boot.img
fastboot flash aboot 4-aboot.img
fastboot flash recovery 10-recovery.img
fastboot flash laf 11-laf.img
fastboot reboot
This fixed the problem for me. Good luck!
x_lord said:
Found this: Worked like a charm.
–]rdsqc22 2 points 23 days ago
Alright, sorry to comment on something 3 months old, but I just had this problem and managed to solve it.
When in the mode described above, you are still able to use Fastboot. Get a linux computer and install fastboot.
Then, go here: http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware/zvc_partitions
Download the images for laf, aboot, boot, and recovery.
type the following commands in fastboot:
fastboot erase boot
fastboot erase aboot
fastboot erase recovery
fastboot erase laf
fastboot flash boot 6-boot.img
fastboot flash aboot 4-aboot.img
fastboot flash recovery 10-recovery.img
fastboot flash laf 11-laf.img
fastboot reboot
This fixed the problem for me. Good luck!
Click to expand...
Click to collapse
Sorry for not replying, but I see you managed to fix your problem. All you needed to do was download .img files, then enter commands through fastboot. Although it is slightly more complicated than that, its the rough outline of what needs to be done to fix it. Nice work fixing your problem. I came back to this thread to remind myself of the commands that need to be entered (My comments help myself).
I think I am just going to copy-paste the quoted box above if anyone needs instructions how to do this. Thanks for the quick guide I can use to help others!
bricked , simple fix?
x_lord said:
Hello, I'm having a similar problem. I haven't had a phone for a couple years since tinkering with my Evo and thought I still knew what I was doing with my new G2. That proved to be incorrect.
I had it semi rooted. (I followed the instructions using Ioroot and Kingo) I wasn't able to change APN and use GSM for Metro PCS
After reading up about the spark patch I followed a tutorial (not very well obviously) and managed to get the phone will it will no longer boot.
I can get it into bootloader, and a frozen in download mode. otherwise it just hangs at the LG logo.
Is there a way to recover from bootloader?
I copied twrp-2.6.3.2-g2spr.img and zv7-aboot.img to the phone and did the following.
Here are the commands I used with the guide. I looks like I was using 2 different guides at once..... :/
Originally Posted by darkpoe View Post
This phone does not use Mass storage mode, it uses MTP, you will see it as a phone inside windows explorer and when you click into it you will see "internal storage" this internal storage is what I am referring to as the root of the sdcard (as they are as well)
Also, dont blame me if your phone dies, all this stuff will void your warranty of your phone and your toaster!
Hit the build number under about phone --> software until developer mode is enabled
goto developer mode turn on mtp mode
go download twrp from there site http://www.teamw.in/project/twrp2/197
I used kingo but cant link on xda ,, google it .. its on cnet as well
get http://koush.com/post/universal-adb-driver install (works on all windows)
get http://www.xda-developers.com/androi...oot-installer/has good quick adb install it
copy the downloaded openrecovery for sprint onto the phone directly into the "root" folder (root folder being like when you look at yoru C: drive in windows explorer that is the root folder under linux), when you plug into the pc, make sure in mtp mode
with phone still plugged in run kingo and root it
it will reboot
with phone plugged in run "adb usb" from command prompt on pc (from the link for adb that it installed, it will open a command prompt for you in the proper folder when you click it)
approve adb connection on phone
then run "adb shell" from command prompt on pc
type su, approve it on phone
paste this next line exactly at the prompt
********** this is the line I used from a different guide ***** dd if=/sdcard/zv7-aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
dd if=/sdcard/openrecovery-twrp-2.6.3.2-g2spr.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
let it flash
it will say bytes copied and you will be good
type reboot inside the shell
the phone will reboot
I use goo manager from play store to boot into recovery, I dont even know the key combo for it yet.
Any help would be appreciated, thank you.
---------- Post added at 02:59 AM ---------- Previous post was at 02:06 AM ----------
Found this: Worked like a charm.
–]rdsqc22 2 points 23 days ago
Alright, sorry to comment on something 3 months old, but I just had this problem and managed to solve it.
When in the mode described above, you are still able to use Fastboot. Get a linux computer and install fastboot.
Then, go here: http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware/zvc_partitions
Download the images for laf, aboot, boot, and recovery.
type the following commands in fastboot:
fastboot erase boot
fastboot erase aboot
fastboot erase recovery
fastboot erase laf
fastboot flash boot 6-boot.img
fastboot flash aboot 4-aboot.img
fastboot flash recovery 10-recovery.img
fastboot flash laf 11-laf.img
fastboot reboot
This fixed the problem for me. Good luck!
Click to expand...
Click to collapse
this process (which i got from a different thread originally)
bricked my phone Lg G2 (Ls 980 sprint 32 gb)
i was on remote connection with my friend attempting all kinds of flashes (mostly custom roms and recoveries)
what he did
he FIRST flashboot erase aboot
and then erased all the other files
foolishly he then used fastboot reboot BEFORE reflashing the necessary images
this leaves me with a device that is practically 100% empty all hardware no software
i have no response no life not even a backlight EXCEPT
i can plug into windows and see Qdloader9008 is connected comport 3
and i can communicate with the device on ubuntu terminal although im not too farmiliar with terminal syntax so im not having much luck
im convinced it is as simple as reflashing at least a working recovery or download mode from which i can install everything else i nee
between QPST, Terminal, and or some other method
sorry for Noob ish ness
any help would be appreciated even if just help with a better understanding of what to do next
payment is possible
True2This said:
this process (which i got from a different thread originally)
bricked my phone Lg G2 (Ls 980 sprint 32 gb)
i was on remote connection with my friend attempting all kinds of flashes (mostly custom roms and recoveries)
what he did
he FIRST flashboot erase aboot
and then erased all the other files
foolishly he then used fastboot reboot BEFORE reflashing the necessary images
this leaves me with a device that is practically 100% empty all hardware no software
i have no response no life not even a backlight EXCEPT
i can plug into windows and see Qdloader9008 is connected comport 3
and i can communicate with the device on ubuntu terminal although im not too farmiliar with terminal syntax so im not having much luck
im convinced it is as simple as reflashing at least a working recovery or download mode from which i can install everything else i nee
between QPST, Terminal, and or some other method
sorry for Noob ish ness
any help would be appreciated even if just help with a better understanding of what to do next
payment is possible
Click to expand...
Click to collapse
Sorry, I barely understood what to do originally. What you have to do next is to reflash the aboot/boot/ whatever partitions but getting to that position might be difficult. Maybe some sort of command would allow you to connect to it oncemore?
Sorry, try to look into it more and see if a dev could help. Try posting something in /r/lgg2 but then again I cant be certain anything would happen. Good luck!
Easy guide
Since the problem keeps happening to people heres a quick tutorial I made.
Download and install this (PC only?)
Now go here. (D802) (D800) (LS980) (VS980) (D803) (Device tree/others)Download the images for laf, aboot, boot, and recovery.
Place the 4 .img files in the same folder. Control right click in that folded and open terminal. If this isn't how you open terminal in a folder search"how to open terminal in a folder".
(NOTE: Commands below will differ from the file names. Change the values in the parenthesis to match the files, HOWEVER, do not type the parenthesis into the terminal prompt! It will not work if you do.)
type the following commands in fastboot:
fastboot erase boot
fastboot erase aboot
fastboot erase recovery
fastboot erase laf
fastboot flash boot (6-boot.img)
fastboot flash aboot (4-aboot.img)
fastboot flash recovery (10-recovery.img)
fastboot flash laf (11-laf.img)
fastboot reboot
You should be fine now!
Unbrick Ls980 formatting partitions
Do this: (only for LS980)
1. Download the adb.zip file
2. Unzip in you computer the adb.zip file
3. Connect your phone LS980 to your computer
4. Run "particiones lg g2.bat"
5. Enter in download mode and flash the phone
6. enjoy your phone
Link of download
https://drive.google.com/file/d/0B6VmAym2TGdIRGJmSXFqdm84NU0/view?usp=sharing
RevolcFael4 said:
Since the problem keeps happening to people heres a quick tutorial I made.
Download and install this (PC only?)
Now go here. (D802) (D800) (LS980) (VS980) (D803) (Device tree/others)Download the images for laf, aboot, boot, and recovery.
Place the 4 .img files in the same folder. Control right click in that folded and open terminal. If this isn't how you open terminal in a folder search"how to open terminal in a folder".
(NOTE: Commands below will differ from the file names. Change the values in the parenthesis to match the files, HOWEVER, do not type the parenthesis into the terminal prompt! It will not work if you do.)
type the following commands in fastboot:
fastboot erase boot
fastboot erase aboot
fastboot erase recovery
fastboot erase laf
fastboot flash boot (6-boot.img)
fastboot flash aboot (4-aboot.img)
fastboot flash recovery (10-recovery.img)
fastboot flash laf (11-laf.img)
fastboot reboot
You should be fine now!
Click to expand...
Click to collapse
i tried this with almost all model files but still on fastboot any other option?>
I want to say thank you so much for this thread. Just got a new (refurb) G2 switching carriers to T-Mo and my idiot self used the wrong root program and soft bricked to fastboot. 4 .img files later and a few commands and I don't think I've ever been so happy to see a download screen on a phone...
juancho8207 said:
Do this: (only for LS980)
1. Download the adb.zip file
2. Unzip in you computer the adb.zip file
3. Connect your phone LS980 to your computer
4. Run "particiones lg g2.bat"
5. Enter in download mode and flash the phone
6. enjoy your phone
Link of download
https://drive.google.com/file/d/0B6VmAym2TGdIRGJmSXFqdm84NU0/view?usp=sharing
Click to expand...
Click to collapse
GREAT, You are a life saver :laugh:
juancho8207 said:
Do this: (only for LS980)
1. Download the adb.zip file
2. Unzip in you computer the adb.zip file
3. Connect your phone LS980 to your computer
4. Run "particiones lg g2.bat"
5. Enter in download mode and flash the phone
6. enjoy your phone
Link of download
https://drive.google.com/file/d/0B6VmAym2TGdIRGJmSXFqdm84NU0/view?usp=sharing
Click to expand...
Click to collapse
wow.. worked flawlessly... thank you very much :good::good::laugh::laugh:
Related
I'm trying to install baconbits on my G2 and I have a mac. I cannot seem to get the recovery image to work through fastboot. Help?
I can access the phone through the terminal but once I command it to reboot to the bootloader I can't get it to find the img file
There's a fastboot binary available for download from this page: http://developer.htc.com/adp.html
I have the binary in my sdk's tools folder but I still can't figure it out. Where/how do input the command to boot the img file?
pak256 said:
I have the binary in my sdk's tools folder but I still can't figure it out. Where/how do input the command to boot the img file?
Click to expand...
Click to collapse
You can flash files from recovery if they are on the SD card. You can either adb push while in recovery, or mount USB storage and tranfer the file. Or just transfer it via USB while the phone is on (big, green android screen)
I'm not sure how to install baconbits, but I think you need fastboot to flash the .img file. Recovery flashes .zip files and fastboot flashes .img files. You can put fastboot-mac in the same folder as adb... then fastboot flash recovery your_recovery.img. You really don't need adb (for this) since you can boot into fastboot on the phone by restarting while holding down the trackpad button.
These might be the droids you are looking for...
Code:
adb (read the instructions)
adb devices (you'll see your phone if it's plugged in, turned on, and in the proper mode)
adb reboot bootloader (white screen with androids on skateboards)
fastboot-mac (more reading...)
fastboot-mac devices (your phone again)
fastboot flash recovery your_recovery.img
fastboot reboot-bootloader
For some reason, I had a little trouble flashing my recovery- sometimes it would hang and wouldn't flash, sometimes it would only fastboot boot. So if you run into trouble, there might be other problems.
While you are at it, you might as well save yourself the trouble and either add the adb and flashboot folders into your path, or put the binaries somewhere in your path. I also renamed fastboot-mac to fastboot for simplicity.
Going to try that when I get out of class but I think you helped me realize what I was doing wrong. Thanks and will let you know if it works
Sent from my T-Mobile G2 using XDA App
Okay I could get the fastboot prompts to work but when I try to flash the recovery it tells me "g2recovery.img" could not be loaded
okay, used clockwork and got it to work. yay!
I've done my homework but haven't found how others fix this issue.
Sucessfully rooted the Videotron LG G2 D801
.
The mistake: Autorec my LG G2 D801 with autorec D801 version unaware that Canadian D801 must be autorec'd by autorec D803 version.
Status of phone: Boots shows LG logo and goes immediately to black screen 'Fastboot mode started'.
Tried: Download mode attempts bring up the download mode logo for a sec and immediately the phone goes back to Fastboot mode started screen.
User rickthewood2 reported he had the same issue and was provided a fix. http://forum.xda-developers.com/showthread.php?t=2723687.
I tracked him on a french forum where he reported that XDA guy compiled a file for him that unbricked this issue as he was having a hard time with entering commands. He also specified that the trick was to repair his download mode with a laf.img file ... once download mode was repaired he went back to stock rom. This is the link of his post made in french http://www.phonandroid.com/forum/ecran-noir-apres-autorec-t90109.html
Please assist.
Kybby said:
I've done my homework but haven't found how others fix this issue.
Sucessfully rooted the Videotron LG G2 D801
.
The mistake: Autorec my LG G2 D801 with autorec D801 version unaware that Canadian D801 must be autorec'd by autorec D803 version.
Status of phone: Boots shows LG logo and goes immediately to black screen 'Fastboot mode started'.
Tried: Download mode attempts bring up the download mode logo for a sec and immediately the phone goes back to Fastboot mode started screen.
User rickthewood2 reported he had the same issue and was provided a fix. http://forum.xda-developers.com/showthread.php?t=2723687.
I tracked him on a french forum where he reported that XDA guy compiled a file for him that unbricked this issue as he was having a hard time with entering commands. He also specified that the trick was to repair his download mode with a laf.img file ... once download mode was repaired he went back to stock rom. This is the link of his post made in french http://www.phonandroid.com/forum/ecran-noir-apres-autorec-t90109.html
Please assist.
Click to expand...
Click to collapse
that is because the download mode partition is broken because it is the wrong model; if you download the correct model of autorec you can use WinRAR/7zip to get the laf.img from the assets folder and then flash it using adb; I know the process to flash the images through fastboot as long as your device is recognized by your pc I can help
a new hope
XxZombiePikachu said:
that is because the download mode partition is broken because it is the wrong model; if you download the correct model of autorec you can use WinRAR/7zip to get the laf.img from the assets folder and then flash it using adb; I know the process to flash the images through fastboot as long as your device is recognized by your pc I can help
Click to expand...
Click to collapse
Very good files Extracted I see the laf I need to use. So are you saying if pc sees the device I can flash using fastboot but if it doesn't I will have to flash via ADB... right? I'm such a newbie.
Kybby said:
Very good files Extracted I see the laf I need to use. So are you saying if pc sees the device I can flash using fastboot but if it doesn't I will have to flash via ADB... right? I'm such a newbie.
Click to expand...
Click to collapse
it's all done using adb; fastboot is the mood you are in and with adb is how we look for device and send the commands
after going into your adb folder(android sdk>platform-tools or ioroot folder) you make sure to copy the laf image into it and then after opening cmd window and cd into the adb folder you use the adb devices command if after starting daemon it show your device in fastboot mode then you do the following:
fastboot erase laf
fastboot flash laf laf.img
actually you can flash all the partitions using fastboot(the images inside assets folder) and then doing a simple reboot should boot your device but if it doesn't then you just have to boot into download mode:
fastboot erase aboot
fastboot flash aboot aboot.img
fastboot erase boot
fastboot flash boot boot.img
fastboot erase laf
fastboot flash laf laf.img
fastboot erase recovery
fastboot flash recovery recovery.img
with either method when done flashing correct files use:
fastboot reboot
and your device will reboot; make sure that you flash all correct files before rebooting and then if device boots normally you will have custom recovery and be back on the stock rom if by any chance it doesn't boot then you can just boot into download mode(hold volume up while plugging in usb cable to phone/pc) and then just kdz/tot back to stock
Best of Luck :fingers-crossed:
Awesome Just Awesome!!
XxZombiePikachu said:
it's all done using adb; fastboot is the mood you are in and with adb is how we look for device and send the commands
after going into your adb folder(android sdk>platform-tools or ioroot folder) you make sure to copy the laf image into it and then after opening cmd window and cd into the adb folder you use the adb devices command if after starting daemon it show your device in fastboot mode then you do the following:
fastboot erase laf
fastboot flash laf.img
actually you can flash all the partitions using fastboot(the images inside assets folder) and then doing a simple reboot should boot your device but if it doesn't then you just have to boot into download mode:
fastboot erase aboot
fastboot flash aboot.img
fastboot erase boot
fastboot flash boot.img
fastboot erase laf
fastboot flash laf.img
fastboot erase recovery
fastboot flash recovery.img
with either method when done flashing correct files use:
fastboot reboot
and your device will reboot; make sure that you flash all correct files before rebooting and then if device boots normally you will have custom recovery and be back on the stock rom if by any chance it doesn't boot then you can just boot into download mode(hold volume up while plugging in usb cable to phone/pc) and then just kdz/tot back to stock
Best of Luck :fingers-crossed:
Click to expand...
Click to collapse
Dude, I read those instructions from all over the net but I guess I needed this divine intervention. You have no idea how greatful I am for your assistance. Current situation: Download mode is back and LGmobile support tool is doing its download thing for stock rom.
I have to add that I was receiving an error message from CMD prompt for command:
fastboot flash laf.img
I replaced that by:
fastboot flash laf laf.img
and was abble to finish the rest.
Good safe rooting to all the rooters!
Kybby
PS: too bad I can only thank you once on this one...
Kybby said:
Dude, I read those instructions from all over the net but I guess I needed this divine intervention. You have no idea how greatful I am for your assistance. Current situation: Download mode is back and LGmobile support tool is doing its download thing for stock rom.
I have to add that I was receiving an error message from CMD prompt for command:
fastboot flash laf.img
I replaced that by:
fastboot flash laf laf.img
and was abble to finish the rest.
Good safe rooting to all the rooters!
Kybby
PS: too bad I can only thank you once on this one...
Click to expand...
Click to collapse
Glad it all worked out and thanks for pointing that out for some reason I always forget that fastboot needs the partition name before the image name (trust me it isn't first time I make the mistake but we ain't perfect)
If you decide to go at it again make sure to use correct version of autorec and enjoy your device :high-five:
Sent from my Pikachu powered LG D800
Are you kidding me?!?!
XxZombiePikachu said:
Glad it all worked out and thanks for pointing that out for some reason I always forget that fastboot needs the partition name before the image name (trust me it isn't first time I make the mistake but we ain't perfect)
If you decide to go at it again make sure to use correct version of autorec and enjoy your device :high-five:
Sent from my Pikachu powered LG D800
Click to expand...
Click to collapse
You're not serious right? Tell me you're joking!
With ppl like you around I'm no longer worried. This was a learning experience.
Guess what.... G2 now rooted with correct autorec version... TWRP is enabled and BusyBox is in da house too. Next step... create a backup after deleting all these spying resources hungry LG default apps and then... ENABLE 4K video capture!
Amigo, I told you You just made this dude's week.
By the way if you think I forgot something importand pls advise. I read somewhere it was a good thing to save efs or something.
Kybby said:
You're not serious right? Tell me you're joking!
With ppl like you around I'm no longer worried. This was a learning experience.
Guess what.... G2 now rooted with correct autorec version... TWRP is enabled and BusyBox is in da house too. Next step... create a backup after deleting all these spying resources hungry LG default apps and then... ENABLE 4K video capture!
Amigo, I told you You just made this dude's week.
By the way if you think I forgot something importand pls advise. I read somewhere it was a good thing to save efs or something.
Click to expand...
Click to collapse
Yea backing up efs is important since that is where your imei is and if something happens to it you can restore it using efs backup, am not near pc right now to link the guide will update when home
update:
efs backup with ioroot
efs backup guide
Sent from my Pikachu powered LG D800
OK buddy. Was I supposed to do this before Root or its OK to do now?
Kybby said:
OK buddy. Was I supposed to do this before Root or its OK to do now?
Click to expand...
Click to collapse
It is okay to do it now; if I remember correctly it is something that can only be done while rooted
Sent from my Pikachu powered LG D800
Awesone... Friday evenings! I'll definitely do it later tonight and will update you on it. Thanks a bunch for all the kind help
Hi I've been studying this thread because I have the same problem--used the wrong version of autorec and now my Verizon LG G2 is stuck in fastboot. I've downloaded the correct version of autorec but I do not understand how to open the apk to access the assets file. I right click but get no option to open or extract. Can anyone help me, or direct me to a link where the laf.img files are stored? Thanks!
davidargent0628 said:
Hi I've been studying this thread because I have the same problem--used the wrong version of autorec and now my Verizon LG G2 is stuck in fastboot. I've downloaded the correct version of autorec but I do not understand how to open the apk to access the assets file. I right click but get no option to open or extract. Can anyone help me, or direct me to a link where the laf.img files are stored? Thanks!
Click to expand...
Click to collapse
Hello David, sorry to hear you're in the same mess. Sorry I just got to read your message. Please tell me if you still need assistance. I will do my best to get you out of it...
Kybby said:
Hello David, sorry to hear you're in the same mess. Sorry I just got to read your message. Please tell me if you still need assistance. I will do my best to get you out of it...
Click to expand...
Click to collapse
Thanks, but I took it to a shop that borked it completely. Just sold it on the Bay. Picked up a Moto X off Craig's...lol...oh well, the Moto is pretty cool and since it's running 4.4.4 I can't do anything to it until someone figures out how to unlock the bootloader...probably for the best...
Kybby said:
I've done my homework but haven't found how others fix this issue.
Sucessfully rooted the Videotron LG G2 D801
.
The mistake: Autorec my LG G2 D801 with autorec D801 version unaware that Canadian D801 must be autorec'd by autorec D803 version.
Status of phone: Boots shows LG logo and goes immediately to black screen 'Fastboot mode started'.
Tried: Download mode attempts bring up the download mode logo for a sec and immediately the phone goes back to Fastboot mode started screen.
User rickthewood2 reported he had the same issue and was provided a fix. http://forum.xda-developers.com/showthread.php?t=2723687.
I tracked him on a french forum where he reported that XDA guy compiled a file for him that unbricked this issue as he was having a hard time with entering commands. He also specified that the trick was to repair his download mode with a laf.img file ... once download mode was repaired he went back to stock rom. This is the link of his post made in french http://www.phonandroid.com/forum/ecran-noir-apres-autorec-t90109.html
Please assist.
Click to expand...
Click to collapse
Hi,
do you have an idea wich autorec is nessesary for a G2 shipped from HongKong. Ic guess I have the same issue like you. But on the case I have a D802 lable. So I thought it must be the one for a D802. May I'm wrong?
Now I tried a D800 one and it worked as I could start my phones download mode. After starting it I installed different roms but all had strange behavior like wrong touch an just flipping arround after touching. There is also no chance to connect to the network. Later I saw that my G2 32GB only shows 10GB of internal storage when its connected to pc. Any idea what I did wrong?
I would be very thankfull for help!!!!
Thanks
XxZombiePikachu said:
it's all done using adb; fastboot is the mood you are in and with adb is how we look for device and send the commands
after going into your adb folder(android sdk>platform-tools or ioroot folder) you make sure to copy the laf image into it and then after opening cmd window and cd into the adb folder you use the adb devices command if after starting daemon it show your device in fastboot mode then you do the following:
fastboot erase laf
fastboot flash laf laf.img
actually you can flash all the partitions using fastboot(the images inside assets folder) and then doing a simple reboot should boot your device but if it doesn't then you just have to boot into download mode:
fastboot erase aboot
fastboot flash aboot aboot.img
fastboot erase boot
fastboot flash boot boot.img
fastboot erase laf
fastboot flash laf laf.img
fastboot erase recovery
fastboot flash recovery recovery.img
with either method when done flashing correct files use:
fastboot reboot
and your device will reboot; make sure that you flash all correct files before rebooting and then if device boots normally you will have custom recovery and be back on the stock rom if by any chance it doesn't boot then you can just boot into download mode(hold volume up while plugging in usb cable to phone/pc) and then just kdz/tot back to stock
Best of Luck :fingers-crossed:
Click to expand...
Click to collapse
thought it was working cause it was most progress ive seen in months but now im totally stuck in bootloop mode at the LG screen, i can get to download mode but that just sticks on the firmware update page with 0% progress and i can't get adb to recognize my phone now. arrrrrrrg this is my main phone what can i do now to fix this?
need help asap
please and thank you
paul
XxZombiePikachu said:
it's all done using adb; fastboot is the mood you are in and with adb is how we look for device and send the commands
after going into your adb folder(android sdk>platform-tools or ioroot folder) you make sure to copy the laf image into it and then after opening cmd window and cd into the adb folder you use the adb devices command if after starting daemon it show your device in fastboot mode then you do the following:
fastboot erase laf
fastboot flash laf laf.img
actually you can flash all the partitions using fastboot(the images inside assets folder) and then doing a simple reboot should boot your device but if it doesn't then you just have to boot into download mode:
fastboot erase aboot
fastboot flash aboot aboot.img
fastboot erase boot
fastboot flash boot boot.img
fastboot erase laf
fastboot flash laf laf.img
fastboot erase recovery
fastboot flash recovery recovery.img
with either method when done flashing correct files use:
fastboot reboot
and your device will reboot; make sure that you flash all correct files before rebooting and then if device boots normally you will have custom recovery and be back on the stock rom if by any chance it doesn't boot then you can just boot into download mode(hold volume up while plugging in usb cable to phone/pc) and then just kdz/tot back to stock
Best of Luck :fingers-crossed:
Click to expand...
Click to collapse
Thanks alot it worked for me but my phone is stuck in download mode whilst installing firmware at %60 every time saying the phone is disconnected from pc ... any idea please
Thanks in adv
Hi all im new to this forum. I am having a problem with my N7 im trying to unbrick it with nexus tool kit but at the flashing stage its says FAILED write failed unknown error for all partitions and when I try to flash a rom in twrp it hangs on patching system unconditionally. Has any one come across this problem before.
Update I have no software on my device without a way to flash it all tools including fastboot via comand prompt can't see it in bootloader mode please I really need help
gavster26 said:
Update I have no software on my device without a way to flash it all tools including fastboot via comand prompt can't see it in bootloader mode please I really need help
Click to expand...
Click to collapse
so you can boot to recovery or bootloader?
try nexus root toolkit - there is an option to unbrick. Wipe everything and try to unbrick.
how windows detects your N7? maybe try different usb cable - if not genuine, then cut a lil bit of plastic, so it goes all the way to the usb port
give some photos of what errors do you have in recovery
yaro666 said:
so you can boot to recovery or bootloader?
try nexus root toolkit - there is an option to unbrick. Wipe everything and try to unbrick.
how windows detects your N7? maybe try different usb cable - if not genuine, then cut a lil bit of plastic, so it goes all the way to the usb port
give some photos of what errors do you have in recovery
Click to expand...
Click to collapse
I can boot to bootloader and thats it that tool can't write to any partitions thats what I tried in the first place it erased the partitions but then could not write to them so im left with no system no kernel or recovery
Download drivers from here
Open cmd as admin and type fastboot devices, it should detect your n7 with some numbers and letters.
If you have grouper (wifi) n7 then download recovery here
Go to bootloader, connect n7 with pc and type:
fastboot flash recovery twrp.img
Where twrp.img is the name of recovery file you downloaded.
Then type: fastboot reboot
In cmd you probably have to go to proper folder just use cd.. to go up a folder and cd name of the folder to go to proper folder. I use C:\adb as drivers install right there
yaro666 said:
Download drivers from here
Open cmd as admin and type fastboot devices, it should detect your n7 with some numbers and letters.
If you have grouper (wifi) n7 then download recovery here
Go to bootloader, connect n7 with pc and type:
fastboot flash recovery twrp.img
Where twrp.img is the name of recovery file you downloaded.
Then type: fastboot reboot
In cmd you probably have to go to proper folder just use cd.. to go up a folder and cd name of the folder to go to proper folder. I use C:\adb as drivers install right there
Click to expand...
Click to collapse
Ok thanks I've got twrp to boot and I fastbooted aosp mm system and kernel but it won't boot up and twrp cant mount storage data or cache where to go from here it wont fastboot any stock img
I'm 63 years old & could do with some help - trying to flash my Moto G4 but no luck
Hello folks.
I apologise in advance. I thought something was a good idea, and I said to myself I would give it a try and I won't give up, but I have been at this for about 5 hours now and no progress.
I have a Moto G4 which my wife gave about a year ago. I don't like stock Android and want to install Lineage OS onto it. I understand that first I need to:
1. Unlock my bootloader (done)
2. Install ADB Driver Installer onto my Dell (done)
3. Install Minimal ADB and Fastboot onto my Dell (done)
4. Plug my G4 into my Dell using the correct cable. It seems to work as the ADP Driver Installer / APK Installer recognises it as per the image below
https://drive.google.com/open?id=1QZAu9ZrCsKBhUcCofo2bde5aB89v76TB
5. Open up the command promt in the Minimal ADB and Fastboot folder, type adb devices - the device is recognised
6. Here is where the problems start!
(a) At this stage, as soon as I type adb reboot bootloader, the G4 reboots but as it does, it disappears from the ADB Diver Installer / APK Installer!
(b) Soon after when I type fastboot flash recovery twrp.img then nothing is found, no files or directory or anything.
I don't understand what I am doing wrong and am very stuck sadly.
https://drive.google.com/file/d/1zR361DukYrsc923zD2q6Aml3Xr0DVqlj/view?usp=sharing
Would really appreciate some help from you young clever guys!
Thank you.
George.
George425 said:
Hello folks.
I apologise in advance. I thought something was a good idea, and I said to myself I would give it a try and I won't give up, but I have been at this for about 5 hours now and no progress.
I have a Moto G4 which my wife gave about a year ago. I don't like stock Android and want to install Lineage OS onto it. I understand that first I need to:
1. Unlock my bootloader (done)
2. Install ADB Driver Installer onto my Dell (done)
3. Install Minimal ADB and Fastboot onto my Dell (done)
4. Plug my G4 into my Dell using the correct cable. It seems to work as the ADP Driver Installer / APK Installer recognises it as per the image below
https://drive.google.com/open?id=1QZAu9ZrCsKBhUcCofo2bde5aB89v76TB
5. Open up the command promt in the Minimal ADB and Fastboot folder, type adb devices - the device is recognised
6. Here is where the problems start!
(a) At this stage, as soon as I type adb reboot bootloader, the G4 reboots but as it does, it disappears from the ADB Diver Installer / APK Installer!
(b) Soon after when I type fastboot flash recovery twrp.img then nothing is found, no files or directory or anything.
I don't understand what I am doing wrong and am very stuck sadly.
https://drive.google.com/file/d/1zR361DukYrsc923zD2q6Aml3Xr0DVqlj/view?usp=sharing
Would really appreciate some help from you young clever guys!
Thank you.
George.
Click to expand...
Click to collapse
It says no twrp.img in that folder.
Because You renamed it's name to twrp.img.img ?
Try flash with "fastboot flash recovery twrp.img.img"
common file extensions are not shown in name, or while rename, but you added ".img" at last, so it is doubled..
Hello sir,
Copy the twrp file to the folder where ADB is installed. The folder is located in C drive.
Next you can Shift+right click, open powershell/cmd, whichever is there.
Now type in command
" fastboot flash recovery tw" and click tab button. After tab button, click enter.
This should be done when phone is in bootloader mode and connected to laptop/PC.
after the command execution is over, you can reboot to recovery.
First flash Ex kernel and then flash magisk, in THIS ORDER ONLY, OR YOUR PHONE WILL BRICK!
And voila, you have root! Flash anything!
____Mdd said:
It says no twrp.img in that folder.
Because You renamed it's name to twrp.img.img ?
Try flash with "fastboot flash recovery twrp.img.img"
common file extensions are not shown in name, or while rename, but you added ".img" at last, so it is doubled.
Click to expand...
Click to collapse
Thank you for your suggestion. I did exactly as you said, in fact I tried different variations - I changed twrp.img to just twrp, then tried the command fastboot flash recovery twrp.img, nothing and then I changed it back to how it was, twrp.img and tried the command again, this time ending with twrp.img.img and nothing. Result is as shown below (bootloader not found / not signed or corrupted).
https://drive.google.com/open?id=1qMgUDp767Q32c0MmH2Ey17cpEGI75cJS
What shall I try now?
George425 said:
Thank you for your suggestion. I did exactly as you said, in fact I tried different variations - I changed twrp.img to just twrp, then tried the command fastboot flash recovery twrp.img, nothing and then I changed it back to how it was, twrp.img and tried the command again, this time ending with twrp.img.img and nothing. Result is as shown below (bootloader not found / not signed or corrupted).
https://drive.google.com/open?id=1qMgUDp767Q32c0MmH2Ey17cpEGI75cJS
What shall I try now?
Click to expand...
Click to collapse
You flashed it. Reboot into recovery now.
George425 said:
Thank you for your suggestion. I did exactly as you said, in fact I tried different variations - I changed twrp.img to just twrp, then tried the command fastboot flash recovery twrp.img, nothing and then I changed it back to how it was, twrp.img and tried the command again, this time ending with twrp.img.img and nothing. Result is as shown below (bootloader not found / not signed or corrupted).
https://drive.google.com/open?id=1qMgUDp767Q32c0MmH2Ey17cpEGI75cJS
What shall I try now?
Click to expand...
Click to collapse
You've done it! Reboot to recovery!
Lyuu said:
You flashed it. Reboot into recovery now.
Click to expand...
Click to collapse
DhirajKale789 said:
You've done it! Reboot to recovery!
Click to expand...
Click to collapse
Yes you are both absolutely correct thank you for your help! I didn't think it was working!
Note: I am no expert at this. I used this to get TWRP and root, but it there is no guarentee it won't brick your phone. Only do this if you know what your doing. Before you start you must have an unlocked bootloader, which will delete all your data. Here's the instructions (If you need help, feel free to post a comment):
Download Magisk's installer zip on your phone from https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 (Google Pay only works with Magisk v19.0+)
Download arter97's kernel .img to your PC. This kernel currently is the only reliable way to get TWRP. https://forum.xda-developers.com/razer-phone-2/development/arter97-kernel-razer-phone-2-t3914996
Reboot your phone into bootloader mode (Turn off then back on while holding vol down).
Make sure your phone is recognized by Windows before proceeding. Follow this guide to setup the proper drivers and fastboot.
Flash arter97's kernel by running
Code:
fastboot flash boot arter97-kernel-*.img
If you run into any issues, then you will probably need to specify the slot to flash. Reboot back into your system.
Turn on Android Debugging and run
Code:
adb shell getprop ro.boot.slot_suffix
and make note if the output is _a or _b
Reboot back into bootloader
If _a use
Code:
fastboot flash boot_a arter97-kernel-*.img
if _b use
Code:
fastboot flash boot_b arter97-kernel-*.img
Reboot to recovery (either through bootloader mode or hold vol up while rebooting).
Install the Magisk .zip from TWRP.
Be amazed by the possibilities.
Old instructions (Should always work to get root):
Download the factory image from here: https://developer.razer.com/razer-phone-dev-tools/
Extract and copy the boot.img file to your device
Download and install Magisk Manager. If you have an SD card make sure it's installed on your internal storage, not the SD card.
Tap install, select Patch Boot Image File, and select the boot.img (If using the default file manager click the overflow menu and show internal storage)
Copy the patched_boot.img back over to your PC
Flash the patched_boot.img to your device via fastboot (Turn off then back on while holding vol down) and run
Code:
fastboot flash boot patched_boot.img
.
If you run into any issues, then you will need to specify the slot to flash.
Turn on Android Debugging and run
Code:
adb shell getprop ro.boot.slot_suffix
and make note if the output is _a or _b
Reboot back into bootloader
If _a use
Code:
fastboot flash boot_a patched_boot.img
if _b use
Code:
fastboot flash boot_b patched_boot.img
Reboot, and open up magisk manager to confirm everything is working. After an OTA update you may have to re-apply due to it using a different slot.
Note: the phone wasn't properly recognized by my computer when in bootloader mode so I had to install the Google adb drivers and manually set the driver used to Google Bootloader Interface (or something like that)
I found you needed to specify boot_a or boot_b specifically as the bootloader tended to mess up the suffix(it tried "bootb_b"????). So I had to first run "fastboot getvar all" to check the current slot.
I also found the commands are executed much more reliably if you enter the command first and press enter so fastboot goes into the "waiting for device" state and then boot into the bootloader and afterwards plug in the cable so fastboot executes the command as soon as it connects.
figured itd be as easy as that. this will be my first up to date device in years, att sending it to me in the mail. should get it by the 6th . but glad to see theres root! hopefully lineage to follow <3
Twiggy000b said:
figured itd be as easy as that. this will be my first up to date device in years, att sending it to me in the mail. should get it by the 6th . but glad to see theres root! hopefully lineage to follow <3
Click to expand...
Click to collapse
I know the feeling, my last device was the Nexus 5
my last "decent" device was the essential phone. then i went to the xperia xa2 ultra, then the iphone 6 then.... zte quest. -.-
CurtisMJ said:
I found you needed to specify boot_a or boot_b specifically as the bootloader tended to mess up the suffix(it tried "bootb_b"????). So I had to first run "fastboot getvar all" to check the current slot.
I also found the commands are executed much more reliably if you enter the command first and press enter so fastboot goes into the "waiting for device" state and then boot into the bootloader and afterwards plug in the cable so fastboot executes the command as soon as it connects.
Click to expand...
Click to collapse
Lol, bootb_b:laugh:. For me at least it worked fine without specifying the slot, though I may change the instructions to specify the slot
CalebQ42 said:
With the release of the factory images we can achieve root via Magisk boot image patching. Note: I am no expert at this. I used this to achieve root, but it there is no guarentee it won't brick your phone. Only do this if you know what your doing. Before you start you must have an unlocked bootloader. Here's the instructions (If you need help, feel free to post a comment):
Download the factory image from here: https://developer.razer.com/razer-phone-dev-tools/
Extract and copy the boot.img file to your device
Download and install Magisk Manager. If you have an SD card make sure it's installed on your internal storage, not the SD card.
Tap install, select Patch Boot Image File, and select the boot.img (If using the default file manager click the overflow menu and show internal storage)
Copy the patched_boot.img back over to your PC
Flash the patched_boot.img to your device via fastboot (Turn off then back on while holding vol down and run `fastboot flash boot patched_boot.img`.
Reboot, and open up magisk manager to confirm everything is working.
Note: the phone wasn't properly recognized by my computer so I had to install the Google adb drivers and manually set the driver to Google Bootloader interface (or something like that)
I also tried to install some Android Pie GSIs, but none of them worked.
Click to expand...
Click to collapse
Does this destroy all data? Do I need to unlock bootloader? Does it matter where I place the boot.img on my device?
CalebQ42 said:
Lol, bootb_b:laugh:. For me at least it worked fine without specifying the slot, though I may change the instructions to specify the slot
Click to expand...
Click to collapse
Interesting. The bootloader isn't exactly what I'd call a masterpiece of coding (weird cause I still maintain the ROM is excellent) so it might have just been a momentary glitch.
---------- Post added at 10:54 PM ---------- Previous post was at 10:53 PM ----------
ctakah27 said:
Does this destroy all data? Do I need to unlock bootloader? Does it matter where I place the boot.img on my device?
Click to expand...
Click to collapse
Yes, yes and not really (you get a file chooser so you just need to locate it)
I updated the post a bit with instructions on how to flash to a specific slot.
Tonight I'm going to try compiling TWRP for the first time ever (unless someone beats me to in). Wish me luck!
CalebQ42 said:
I updated the post a bit with instructions on how to flash to a specific slot.
Tonight I'm going to try compiling TWRP for the first time ever (unless someone beats me to in). Wish me luck!
Click to expand...
Click to collapse
Good luck it's a easier process compare to years ago. I would do it but I have no need for root or custom recovery. If you fail on the TWRP I will do it in time for people.
Is this working on the AT&T version of this phone? Or would you need to flash the global firmware in order for this to work? Looking to upgrade to this phone and I want to be sure I can get root. The rest looks to be coming fairly quickly.
CalebQ42 said:
I updated the post a bit with instructions on how to flash to a specific slot.
Tonight I'm going to try compiling TWRP for the first time ever (unless someone beats me to in). Wish me luck!
Click to expand...
Click to collapse
jonchance_84 said:
Is this working on the AT&T version of this phone? Or would you need to flash the global firmware in order for this to work? Looking to upgrade to this phone and I want to be sure I can get root. The rest looks to be coming fairly quickly.
Click to expand...
Click to collapse
They have the image for AT&T
EAIaIQobChMIwYzbk7j_3gIVRZRpCh0RMwdoEAEYASAAEgLPifD_BwE
Warrior1988 said:
They have the image for AT&T
EAIaIQobChMIwYzbk7j_3gIVRZRpCh0RMwdoEAEYASAAEgLPifD_BwE
Click to expand...
Click to collapse
I see the separate firmware. I'm only asking because of past shadyness from AT&T trying to tell manufacturers what to do. Years ago on my Xperia x10, if on AT&T firmware, you needed to flash the global generic firmware to get around their crap.
CalebQ42 said:
With the release of the factory images we can achieve root via Magisk boot image patching. Note: I am no expert at this. I used this to achieve root, but it there is no guarentee it won't brick your phone. Only do this if you know what your doing. Before you start you must have an unlocked bootloader, which will delete all your data. Here's the instructions (If you need help, feel free to post a comment):
Download the factory image from here: https://developer.razer.com/razer-phone-dev-tools/
Extract and copy the boot.img file to your device
Download and install Magisk Manager. If you have an SD card make sure it's installed on your internal storage, not the SD card.
Tap install, select Patch Boot Image File, and select the boot.img (If using the default file manager click the overflow menu and show internal storage)
Copy the patched_boot.img back over to your PC
Flash the patched_boot.img to your device via fastboot (Turn off then back on while holding vol down) and run
Code:
fastboot flash boot patched_boot.img
.
If you run into any issues, then you will need to specify the slot to flash.
Turn on Android Debugging and run
Code:
adb shell getprop ro.boot.slot_suffix
and make note if the output is _a or _b
Reboot back into bootloader
If _a use
Code:
fastboot flash boot_a patched_boot.img
if _b use
Code:
fastboot flash boot_b patched_boot.img
Reboot, and open up magisk manager to confirm everything is working. After an OTA update you may have to re-apply due to it using a different slot.
Note: the phone wasn't properly recognized by my computer so I had to install the Google adb drivers and manually set the driver to Google Bootloader interface (or something like that)
I also tried to install some Android Pie GSIs, but none of them worked.
Click to expand...
Click to collapse
Would this procedure be the same as far as mac/win?
I understand all of that, I am simply asking if someone has tried this with the AT&T variant yet. I want to know before I go order this phone.
I love a rooted phone, but as far as I know, if you unlock the bootloader, Netflix will no longer work in HD mode. To me, this is a deal-breaker. If anyone knows about a work-around, I'd love to know.
Razer phone 2 root
so im kinda new to rooting this type of phone and to the android boot scheme in general. i have a razer phone 2 and have attempted (febaly) to root it using this meathod. after installing the google adb drivers i was unable to see the device from my pc when it was in fastboot and unable to send commands, after installing the drivers again with windows update it ran even though no device was detected with this message
">fastboot flash boot patched_boot.img
Sending 'boot_b' (19268 KB) OKAY [ 0.523s]
Writing 'boot_b' OKAY [ 0.179s]
Finished. Total time: 0.718s"
it then blackscreened, i then tried a factory reset from recovery, and it is now in a bootloop... any advice?
update: no longer in boot loop but now is full blackscreen after a glitchy install screen
andy1011 said:
so im kinda new to rooting this type of phone and to the android boot scheme in general. i have a razer phone 2 and have attempted (febaly) to root it using this meathod. after installing the google adb drivers i was unable to see the device from my pc when it was in fastboot and unable to send commands, after installing the drivers again with windows update it ran even though no device was detected with this message
">fastboot flash boot patched_boot.img
Sending 'boot_b' (19268 KB) OKAY [ 0.523s]
Writing 'boot_b' OKAY [ 0.179s]
Finished. Total time: 0.718s"
it then blackscreened, i then tried a factory reset from recovery, and it is now in a bootloop... any advice?
update: no longer in boot loop but now is full blackscreen after a glitchy install screen
Click to expand...
Click to collapse
Since it's already wiped the easiest way to fix it is to probably flash the full factory image. Did you happen to update to the MR2 update prior to following this guide? Doing this on MR2 will soft brick. Not entirely sure in what way, but I assume it would be similar to what you experienced. If you were still on MR0 you can actually just fastboot flash the original kernel image to fix it. I just finished rooting MR2 so I'll post that next
CurtisMJ said:
Since it's already wiped the easiest way to fix it is to probably flash the full factory image. Did you happen to update to the MR2 update prior to following this guide? Doing this on MR2 will soft brick. Not entirely sure in what way, but I assume it would be similar to what you experienced. If you were still on MR0 you can actually just fastboot flash the original kernel image to fix it. I just finished rooting MR2 so I'll post that next
Click to expand...
Click to collapse
this is what im trying to do. however i have no way of flashing to the device as adb is unable to see the device.
andy1011 said:
this is what im trying to do. however i have no way of flashing to the device as adb is unable to see the device.
Click to expand...
Click to collapse
Adb and fastboot are separate things. You should only need download mode and fastboot. What are you trying to use ADB for? If in doubt, the guide on Razer's website should be quite sufficient
EDIT: You can get to download mode by holding Vol Down and Power Button while the device is off. You can force reboot by holding down power for approx 15s as well