Now that the new ZVB security update is out for Sprint LG G Flex 2, is there anyway we can root when we have ZVB installed? Like a rootedZVBsystem.img?
If you can provide the system.img, I can root it.
Run below dd command, then upload the resulting system.img.
dd if=/dev/block/mmcblk0 bs=8192 skip=58368 count=522240 of=/data/media/0/system.img
Click to expand...
Click to collapse
Sent from my LGLS996 using Tapatalk
ls996zvb
The system image is uploaded here:
https://mega.nz/#!fkxjxSpL!WckL2OX7WENO1sGBxSluqK-ggqPkhCnAMUDrdZfcDx8
etirkca said:
Run below dd command, then upload the resulting system.img.
Sent from my LGLS996 using Tapatalk
Click to expand...
Click to collapse
---------- Post added at 10:14 PM ---------- Previous post was at 10:13 PM ----------
kevin3688 said:
If you can provide the system.img, I can root it.
Click to expand...
Click to collapse
nitroshot said:
The system image is uploaded here:
https://mega.nz/#!fkxjxSpL!WckL2OX7WENO1sGBxSluqK-ggqPkhCnAMUDrdZfcDx8
---------- Post added at 10:14 PM ---------- Previous post was at 10:13 PM ----------
Click to expand...
Click to collapse
Thanks for this! Hopefully now @kevin3688 with grace us with a rooted image. I would have gladly uploaded a ZVB image myself, but I have not yet updated to ZVB from ZV9 as I am rooted. And to be honest, root is so great that I was hoping to get my hands on a rooted ZVB before I update myself
Uploaded
https://drive.google.com/file/d/0B0UblGbOPFYBcUNmQlVPazdGWE0/view?usp=sharing
I can't make it work. following the steps of the thread: ROOT LG G FLEX 2 (LS996-ZV6-ZV7-Sprint/H955-V15a-INT/H950-V11x-ATT) 5.1.1 but using the img you guys uploaded and the dd command on this thread. I have an LG G FLEX 2 LS996 running on 5.1.1 VZB. I can make it through the process but after I finish... no root.
Using the img file posted by kevin3688 in post #6 above this is what I did earlier today with my LS996:
- use LG Flash Tool to flash the ZV8 TOT file to the LS996 (instructions are elsewhere if needed - you might (I'm saying you might here) have to do a Board DL mode flash first then reflash using the Upgrade DL mode immediately afterward - if you get stuck in MiniOS wait for it to load, tap the screen one time as requested, wait for the menu to appear then hold Power and tap "Normal" to reboot normally - this happens after the Board DL flash process, if you get stuck with the blue screen and the big red 2 hold Volume Down+Power for 20+ seconds to totally power the device off - 20+ full seconds or it'll just keep looping, after which you do the same thing again: Board DL mode flash again, then immediately flash using Upgrade DL mode)
- after that's done, set up the phone as usual but stop before adding a Google account, etc (skip all that, just get to the home screen)
- copy the rootedsystem.img for ZVB to the internal storage of the device
- power down, reconnect device in bootloader mode (hold Volume Up while plugging in the USB cable)
- open a Command Prompt where you have the LG_Root files
- verify the diagnostic COM port using ports.bat
- use the Send_Command.exe \\.\COM(port number) command to start the mode necessary - it works if you see the # prompt
- while you don't have to do it, type id (and press Enter) and you should see a string of device ID information - if the command doesn't work and you see nothing at all I'd start over again (you can disconnect the LS996, power it down, then put it back in bootloader mode and try again - the only reason the command might not work is a mismatch in COM ports but again you don't have to use the id command at all, it's completely optional)
- use the command which is for the LG G Flex 2 LS996 Sprint model ONLY:
Code:
dd if=/data/media/0/rootedsystem.img bs=8192 seek=58368 count=522240 of=/dev/block/mmcblk0
to flash the rootedsystem.img (assuming that's the filename, you may have renamed it differently, I don't know) from the internal storage file you copied over to the system partition. Each of the Flex 2 models has a slightly different dd command so MAKE ABSOLUTELY SURE you're using the one I just posted for the LS996 Sprint Flex 2 - if you use one of the other model's dd lines you could do damage to the partition structure so, again, the command I just posted above is for the LS996 only.
When you execute the command you will see nothing but the flashing cursor in the Command Prompt which is normal, no other activity will be noted, nothing on the LS996 either. After maybe 1-2 minutes or so (sometimes less, sometimes a bit more, depending) the flashing cursor will jump down a line, you'll see the # prompt again, and that's the signal the process has completed - it won't tell you anything else, just the # prompt and the flashing cursor.
Type LEAVE (all caps) and press Enter and you're done, the LS996 will then reboot and you should be good to go after the reboot is complete. It will do the full "Android is upgrading..." thing as all the files are inspected/modded/compiled (because it's ART now) as required during the boot process.
After that's done and the phone is properly booted, you'll probably get the notification from SuperSU within a few minutes that it needs to be upgraded, or you can run SuperSU manually and it'll tell you - do the Normal upgrade method, then reboot when required (immediate reboot, don't do anything else with the device after you've done the SuperSU upgrade). After that reboot, get your Google account set up and hit the Play Market to get the latest version of SuperSU (yes another upgrade) and then you should be complete and ready to go with the rest of the device setup as you see fit.
That's the process I've done 15x or more so far with my Flex 2, it's never had issues, never had problems, never failed, so I can't imagine there will be any issues for anyone else as long as they're following the steps accurately. If you do this right and there's still a problem then it typically means something is probably wrong with the device itself for whatever reason and that's the kind of troubleshooting that can't be done in a forum post, unfortunately.
Good luck...
Rooted! Now havin troubles to unlock the LS996 to GSM
Managed to root the phone with the extra instructions provided by br0adband (Thank you very much), now having issues unlocking the phone for a GSM use. Any ideas? I already follow 2 different guides for 2 other forums.
br0adband said:
Using the img file posted by kevin3688 in post #6 above this is what I did earlier today with my LS996:
- use LG Flash Tool to flash the ZV8 TOT
(snip)
- copy the rootedsystem.img for ZVB to the internal storage of the device
Click to expand...
Click to collapse
This is fine, but will only update system to ZVB. radio and possibly other components (bootloader, boot, recovery?) if changed since ZV8 won't be updated.
OTA to ZVB before writing rootedsystem.img to be complete.
etirkca said:
This is fine, but will only update system to ZVB. radio and possibly other components (bootloader, boot, recovery?) if changed since ZV8 won't be updated.
OTA to ZVB before writing rootedsystem.img to be complete.
Click to expand...
Click to collapse
So, I've got a question. I am on rooted ZV9 right now. I was just now planning on using the dd command to flash my backed up UNrooted ZV9 system. From there I was going to update "normally" (I believe this is "OTA" method that you refer to) to ZVB. Then I was going to use dd to install rootedZVB.
Would this be the "complete" method?
jplum22 said:
So, I've got a question. I am on rooted ZV9 right now. I was just now planning on using the dd command to flash my backed up UNrooted ZV9 system. From there I was going to update "normally" (I believe this is "OTA" method that you refer to) to ZVB. Then I was going to use dd to install rootedZVB.
Would this be the "complete" method?
Click to expand...
Click to collapse
That works well. Happy upgrading.
Sent from my LGLS996 using Tapatalk
jplum22 said:
So, I've got a question. I am on rooted ZV9 right now. I was just now planning on using the dd command to flash my backed up UNrooted ZV9 system. From there I was going to update "normally" (I believe this is "OTA" method that you refer to) to ZVB. Then I was going to use dd to install rootedZVB.
Would this be the "complete" method?
Click to expand...
Click to collapse
As I noted in the steps I did above, I went from ZV8 to ZVB directly (rooted, of course). I installed the ZV8 TOT file, then flashed the rooted ZVB image directly without having ZV9 on the device at all and it works just fine.
I did have to flash the updated radio.img file as noted also but that was done manually using FlashFire, but from what I can tell there's no issues aside from me not being able to get this phone of mine working with T-Mobile - that has nothing to do with the methodology I described however which works.
etirkca said:
That works well. Happy upgrading.
Sent from my LGLS996 using Tapatalk
Click to expand...
Click to collapse
Thanks! Worked great, now running rooted ZVB.
jplum22 said:
Thanks! Worked great, now running rooted ZVB.
Click to expand...
Click to collapse
Did you have any apps frozen before updating? Wondering if it matters. I have lots of stuff frozen...
hallucinate said:
Did you have any apps frozen before updating? Wondering if it matters. I have lots of stuff frozen...
Click to expand...
Click to collapse
I didn't have any of my apps frozen. I would have (because I hate bloat) but instead I just live dangerously and flat-out remove all the bloat apps I can.
Another successful update and root here. Thanks guys!
jplum22 said:
I didn't have any of my apps frozen. I would have (because I hate bloat) but instead I just live dangerously and flat-out remove all the bloat apps I can.
Click to expand...
Click to collapse
my phone is freezing like hell , everytime in 20-30 seconds , reflashed zv8 tot many times , wiped data/cache , flashed rootedsystem , system images , still the freezing is present !! before following @br0adband method i.e f=before updating , there were no freeze.
Also camera and phone are not working !!!(currently on zvb).
br0adband said:
Using the img file posted by kevin3688 in post #6 above this is what I did earlier today with my LS996:
- copy the rootedsystem.img for ZVB to the internal storage of the device
- power down, reconnect device in bootloader mode (hold Volume Up while plugging in the USB cable)
- open a Command Prompt where you have the LG_Root files
- verify the diagnostic COM port using ports.bat
- use the Send_Command.exe \\.\COM(port number) command to start the mode necessary - it works if you see the # prompt
- while you don't have to do it, type id (and press Enter) and you should see a string of device ID information - if the command doesn't work and you see nothing at all I'd start over again (you can disconnect the LS996, power it down, then put it back in bootloader mode and try again - the only reason the command might not work is a mismatch in COM ports but again you don't have to use the id command at all, it's completely optional)
- use the command which is for the LG G Flex 2 LS996 Sprint model ONLY:
Code:
dd if=/data/media/0/rootedsystem.img bs=8192 seek=58368 count=522240 of=/dev/block/mmcblk0
to flash the rootedsystem.img (assuming that's the filename, you may have renamed it differently, I don't know) from the internal storage file you copied over to the system partition. Each of the Flex 2 models has a slightly different dd command so MAKE ABSOLUTELY SURE you're using the one I just posted for the LS996 Sprint Flex 2 - if you use one of the other model's dd lines you could do damage to the partition structure so, again, the command I just posted above is for the LS996 only.
When you execute the command you will see nothing but the flashing cursor in the Command Prompt which is normal, no other activity will be noted, nothing on the LS996 either. After maybe 1-2 minutes or so (sometimes less, sometimes a bit more, depending) the flashing cursor will jump down a line, you'll see the # prompt again, and that's the signal the process has completed - it won't tell you anything else, just the # prompt and the flashing cursor.
Type LEAVE (all caps) and press Enter and you're done, the LS996 will then reboot and you should be good to go after the reboot is complete. It will do the full "Android is upgrading..." thing as all the files are inspected/modded/compiled (because it's ART now) as required during the boot process.
After that's done and the phone is properly booted, you'll probably get the notification from SuperSU within a few minutes that it needs to be upgraded, or you can run SuperSU manually and it'll tell you - do the Normal upgrade method, then reboot when required (immediate reboot, don't do anything else with the device after you've done the SuperSU upgrade). After that reboot, get your Google account set up and hit the Play Market to get the latest version of SuperSU (yes another upgrade) and then you should be complete and ready to go with the rest of the device setup as you see fit.
That's the process I've done 15x or more so far with my Flex 2, it's never had issues, never had problems, never failed, so I can't imagine there will be any issues for anyone else as long as they're following the steps accurately. If you do this right and there's still a problem then it typically means something is probably wrong with the device itself for whatever reason and that's the kind of troubleshooting that can't be done in a forum post, unfortunately.
Good luck...
Click to expand...
Click to collapse
Followed the instructions above without the flash tool or tot and rooted perfect. Rooted with zvb update.
Dirty 'dd' flashed rooted zvB image directly on top of rooted zv9. Only had to update the 'Super SU' afterwards.
No need to go back to unrooted zv9 or unrooted zvB. Just go directly.
All the settings and apps are intact and working fine. No problems. This is for a T-Mobile set up LS996.
If you want to do it even quicker, install and use 'Terminal Emulator' app to issue the 'dd' command directly from your phone. Type 'su' for a # prompt in the terminal then type in the exact 'dd' command. No need to use a PC to run the 'dd' command.
Related
I haven't flashed either of these so I don't promise that they work. They ought to though.
I suggest you follow the instructions in the original root post under Commands to dump system.img and dump an image from your working phone. Name it something you'll remember and keep it on your internal storage. If something goes wrong from flashing the rooted image you can hopefully recover by changing the filename in the flash command to your original image. Don't run a factory reset or the original image will be deleted.
You'll want to rename the image file you extract from the RAR file. I named them with detail so I wouldn't get them confused.
Good luck!
A user reported that the H81010b image bootlooped their phone. Use at your own risk. You can flash the H810PR KDZ to recover but there's no going back to AT&T stock then. Keep a good copy of your original system.img on internal memory to recover and don't factory reset!
ATT_H81010b_Rooted.system.rar
ATT_H81010e_Rooted.system.rar
Why'd I use RAR? Why not? I'm one of those weirdos that paid for it. A site license even!
Here's my H810 repository on Androidfilehost if you're looking for other H810 files.
It says the img is not mountable, is it safe?
Edit: For 10e, yes it works.
thanks
and winrar 5 is awesome, love it. I've always been a fan of winrar
yoavst said:
It says the img is not mountable, is it safe?
Edit: For 10e, yes it works.
Click to expand...
Click to collapse
Here's a way to open the img file in Windows, but it's much easier to make an Ubuntu boot flash drive and mount it in Linux.
@phineous, it seems the 10e file works so I will give it a try tomorrow morning.
For my personal knowledge of the whole process, how did you determine the dd command parameters (block size, count, skip, etc) for the system.img dump command as well as the flashing command that fit the 10e software version? Are all 810 software versions (10e, 10b, 10g, etc) all the same command parameters of is there a way to determine the correct parameters to enter. Regardless of if all 810 versions are the same parameters, I'm sure there is a process to figure out the right things to enter into the dd command?
Thanks!
Sent from my LG-H810 using Tapatalk
Norcalz71 said:
@phineous, it seems the 10e file works so I will give it a try tomorrow morning.
For my personal knowledge of the whole process, how did you determine the dd command parameters (block size, count, skip, etc) for the system.img dump command as well as the flashing command that fit the 10e software version? Are all 810 software versions (10e, 10b, 10g, etc) all the same command parameters of is there a way to determine the correct parameters to enter. Regardless of if all 810 versions are the same parameters, I'm sure there is a process to figure out the right things to enter into the dd command?
Thanks!
Sent from my LG-H810 using Tapatalk
Click to expand...
Click to collapse
Yes I did with the original params for the G version (I had e).
Norcalz71 said:
@phineous, it seems the 10e file works so I will give it a try tomorrow morning.
For my personal knowledge of the whole process, how did you determine the dd command parameters (block size, count, skip, etc) for the system.img dump command as well as the flashing command that fit the 10e software version? Are all 810 software versions (10e, 10b, 10g, etc) all the same command parameters of is there a way to determine the correct parameters to enter. Regardless of if all 810 versions are the same parameters, I'm sure there is a process to figure out the right things to enter into the dd command?
Thanks!
Sent from my LG-H810 using Tapatalk
Click to expand...
Click to collapse
@autoprime posted the commands to flash the different versions in the original root thread. All the AT&T H810 versions use the same command to flash.
The variables for the flash command are determined based on the location of the partition you want to overwrite in the partition table on the phone. There's a little discussion about it in the original root thread, but I'm sure it's discussed more in depth in rooting threads for earlier phones and threads about Android rooting in general.
phineous said:
@autoprime posted the commands to flash the different versions in the original root thread. All the AT&T H810 versions use the same command to flash.
The variables for the flash command are determined based on the location of the partition you want to overwrite in the partition table on the phone. There's a little discussion about it in the original root thread, but I'm sure it's discussed more in depth in rooting threads for earlier phones and threads about Android rooting in general.
Click to expand...
Click to collapse
Got it, thanks @phineous. I can follow directions like these pretty easily (it is all indeed low effort) but I like to try and understand the process behind the commands. So the seek/count/block size parameters, whether dumping a system.img or flashing a stock or rooted system.img are all the same for each command and for each software version across the H810? In this case they are:
bs=8192
seek=65536
count=579584
I'll have to dig a little more to learn how they figured out the proper parameters for each model.
Thanks again
Norcalz71 said:
Got it, thanks @phineous. I can follow directions like these pretty easily (it is all indeed low effort) but I like to try and understand the process behind the commands. So the seek/count/block size parameters, whether dumping a system.img or flashing a stock or rooted system.img are all the same for each command and for each software version across the H810? In this case they are:
bs=8192
seek=65536
count=579584
I'll have to dig a little more to learn how they figured out the proper parameters for each model.
Thanks again
Click to expand...
Click to collapse
It's the same for the AT&T H810s. The Claro H810pr that some us used after we killed our AT&T phones is different.
Look for posts about android partitions. @rightonred has a couple of posts where they show the partition table from our phones.
Here's the man(ual) page for dd where the commands (BS,SEEK,COUNT) are documented.
phineous said:
It's the same for the AT&T H810s. The Claro H810pr that some us used after we killed our AT&T phones is different.
Look for posts about android partitions. @rightonred has a couple of posts where they show the partition table from our phones.
Here's the man(ual) page for dd where the commands (BS,SEEK,COUNT) are documented.
Click to expand...
Click to collapse
Have a question for OP, this is just came into my head but flashing this img into 810pr fw will break the system itself as the seek and count partition are totally different..or what if we used code seek and count from PR??
faizalotai said:
Have a question for OP, this is just came into my head but flashing this img into 810pr fw will break the system itself as the seek and count partition are totally different..or what if we used code seek and count from PR??
Click to expand...
Click to collapse
That could work, but I don't know much about how the system checks itself and the bootloader. I think it would probably end up with the security error boot screen.
phineous said:
That could work, but I don't know much about how the system checks itself and the bootloader. I think it would probably end up with the security error boot screen.
Click to expand...
Click to collapse
autoprime said:
I just looked into the H810PR 10A files and it seems it's about equal to the AT&T H810 10G (newest ATT OTA). The H810PR 10A and the H810 10G (and I think 10E as well) have updated bootloaders with the "1" version... which was updated from the initial version out of box.. i think it was 10A (or 10b/10c/d.. not e/f).
So... obviously for people who were "bricked" (stuck in download mode) you should use this KDZ as that's about you're only hope at this point. KDZ will upgrade bootloader and you will be set at "1".. never to be at "0" again. 0 vs 1 doesnt mean anything yet... so it may not matter. But any possible bootloader exploit that may happen in the future that somehow only works on v0 bootloaders... you'll be out of luck. But lets hope that isn't the case. And who knows if there will even be an unofficial unlock.
For those who ARENT stuck in download mode but don't care about being on an updated "1" bootloader.. feel free to flash H810PR KDZ all you want.
For those who are on the original AT&T sw (10a/b/c/d) with a "0" bootloader who want root and wanna stay at "0"... someone with your 10a/b/c/d sw will need to dump and upload that system.img and then someone will have to root it.. then upload that img... then H810 10a/b/c/d users will have a safe root method that won't cause a security error and also won't update the bootloader. And maybe it'd be safe for now to keep the pre-rooted system.img (the one that doesnt yet exist as of the moment i am typing this) on your internal storage so if anything were to happen you could reflash system.. never needing an H810 KDZ/TOT (as long as you don't mess with other partitions).
Click to expand...
Click to collapse
@autoprime
I forgot about that post. It wouldn't work then. There was a version # in the build.prop that made me think H810PR had an older bootloader.
How do we determine/confirm if a software version bootloader count is at 0 or 1? I thought 10e was at 0 still but maybe not? Hopefully it is...
Sent from my LG-H810 using Tapatalk
Have we confirmed this works with 1010e? I just got the phone and that is the version installed and I want me some root
Edit, nvm it worked perfectly, thanks!
Rooted my at&t 10e with your image. Work great. Thanks.
Sent from my LG-H810 using Tapatalk
Obsolete
GvIn2it said:
Has anyone rooted their H81010b with this file?
---------- Post added at 09:01 AM ---------- Previous post was at 08:48 AM ----------
How can this work with the original root post, that file is 4GB. This one is only 1.6GB. Just interested to know. It's a little scary when someone posts:
"I haven't flashed either of these so I don't promise that they work. They ought to though." Where did they come from? Did you make them, or someone else who tested them? I would really like to try the H81010b but need a little verification.
Click to expand...
Click to collapse
You must extracted zip/rar to image..than copy to internal memory.
have you tried the H810 10b yet. I tried it on my phone and i keep getting a bootloop......
I really want my 4g back
scabbie1980 said:
have you tried the H810 10b yet. I tried it on my phone and i keep getting a bootloop......
I really want my 4g back
Click to expand...
Click to collapse
I don't think anyone has tested it yet.
Are you flashing it on an AT&T H810 with 10b or on the H810PR? It won't work on the H810PR.
If my 10b image really is broken I'll take it down.
Since none of the updates have prevented root, I doubt LG has made security changes to the bootloader. It's probably safe to upgrade to a new version. They're having a hard enough time making the phone work. I hope they're not wasting time patching, especially when we haven't even found a bootloader unlock. I could be wrong though.
I have seen root is now available for that H810. My software version is H81010g. Is root possible with my phone yet?
Yea check the root thread in the general lg g4 thread.
Sent from my LG-H810 using XDA Free mobile app
I need help! LGG4
I have Software Version. H81010I
I was unaware if a root exploit to unlock bootloader and also to root my phone
was available for my phone yet. I also would prefer a different flashing utility than TWRP.
I dont like it when I used it with my Optimus G.
Thanks in advance.
BH1984 said:
I have Software Version. H81010I
I was unaware if a root exploit to unlock bootloader and also to root my phone
was available for my phone yet. I also would prefer a different flashing utility than TWRP.
I dont like it when I used it with my Optimus G.
Thanks in advance.
Click to expand...
Click to collapse
Right now there is no TWRP for the AT&T variant. Also can you pull your system.img of your stock 10I software? To do that do this:
1. Download these drivers
2. Download the root tools (make sure you mouse over the download button and the bottom of your browser says LG_Root.zip)
3. On this page follow steps 1,2,3,6,7,8,and 9 ONLY also make sure you run the ports.bat and are using the port that says DIAG
4. Then run this command
Code:
dd if=/dev/block/mmcblk0 bs=8192 skip=65536 count=579584 of=/data/media/0/system.img
5. When the command prompt returns to # type LEAVE to reboot your phone. Has to be in all caps.
6. On you computer navigate to your phones internal storage and you will see a file called system.img. Upload this to google drive.
Status: Root unsuccessful
I ran the script through cmd. I watched everything happening and I was unable to gain img or root. What do I do next?
BH1984 said:
I ran the script through cmd. I watched everything happening and I was unable to gain img or root. What do I do next?
Click to expand...
Click to collapse
If you followed my steps exactly as above then you shouldn't have root. there should be a file in your phones internal memory called system.img
If you don't have this try it again. when you issue the command
Code:
dd if=/dev/block/mmcblk0 bs=8192 skip=65536 count=579584 of=/data/media/0/system.img
it should take 2-3 minutes to come back to the # sign. if it is instant then it didn't work. keep retrying until you get the system.img file.
When you get that and upload it I can root it for you then you can flash it to your phone.
Thanks.
It was able to create a system img for me. I can root it if you just let me know the steps. Should I not just follow all of the steps 1-10?
BH1984 said:
It was able to create a system img for me. I can root it if you just let me know the steps. Should I not just follow all of the steps 1-10?
Click to expand...
Click to collapse
No, that is not how you root it. It needs to be rooted in a linux environment. that's why I asked you to upload, because it isn't a simple process to root.
GMAIL
What is your GMAIL. I will share it through drive?
BH1984 said:
It was able to create a system img for me. I can root it if you just let me know the steps. Should I not just follow all of the steps 1-10?
Click to expand...
Click to collapse
BH1984 said:
What is your GMAIL. I will share it through drive?
Click to expand...
Click to collapse
just post the link here and make it so only people who have the link can see it. once i download it I will post here so you can remove the link if you want. It is safe to share through drive on XDA, I do it all the time.
Here is the IMG
[It won't let me share outside link. PM me your gmail
[
QUOTE=uly609;62657493]just post the link here and make it so only people who have the link can see it. once i download it I will post here so you can remove the link if you want. It is safe to share through drive on XDA, I do it all the time.[/QUOTE]
hey guys, I'm running h*1010g rooted software and I just got a message on my phone saying an update is available anyone have an idea what the update is and if there is a rooted image of it? and if I take the update I would asume I will lose root but is the update itself worth it? the texting bugs and lad on the 1010g are worse than the 1010e. thanks for the response.
---------- Post added 10th September 2015 at 12:30 AM ---------- Previous post was 9th September 2015 at 11:57 PM ----------
hey, just a note to let everyone Know, got home from work plugged my phone is and let it charge to 70% then i was about to run a debloater from my pc but as soon as I plugged in the usb cable the phone said shutting down to install updates! I thought oh hell I'm bricked but the screen came on and said my phone is rooted and unable to install the update. no clue what it was or if it would have been worth it. just thought Id let everyone know.
Hi,
I'm using an unlocked 810 on TMobile, so I can't get any OTA past 10g. Please guide me on how to get 10l and root. Thanks!
mankand007 said:
Hi,
I'm using an unlocked 810 on TMobile, so I can't get any OTA past 10g. Please guide me on how to get 10l and root. Thanks!
Click to expand...
Click to collapse
I don't think you can without ATT sim
Yeah I went to an AT&T store and updated to 10l from there.
mankand007 said:
Yeah I went to an AT&T store and updated to 10l from there.
Click to expand...
Click to collapse
How did you do that? Did it download automatically over their wireless? I wonder if it works work over any att WiFi access point.
Hello everyone!
A little bit of a back story here - I was on NATF's rom when I proceeded to take the flashable 10Q/10R updates posted by @dimm0k. These newer updates, starting with 10P, are Anti-Rollback. I spent some time poking around trying to find answers on how to return to stock and how I could do this in a way that seemed comfortable to me.
I have found that ARB 0 is interchangeable with anything ARB 0. Anything that is ARB1, is interchangeable with ARB1, and so forth if LG decides to up the values to '2' or maybe even '3'.
If you are ever curious and want to know on later firmwares if you have ARB and what version it is, use this dialer code:
*#*#244773825625#*#*
###
I AM IN NO WAY RESPONSIBLE FOR YOUR DEVICE. THIS IS A AT YOUR OWN RISK TUTORIAL.
###
Moving forward here - I was able to flash 10P KDZ to remove TWRP and revoke root.
Requirements:
H918 TMO V20
10P/10Q/10R partial update software by dimm0k
1. Download LGUP_Store_Frame_Ver_1_14_3.msi and search for LGUP_common.dll ( I actually used the G5 dll)
1a. Download 10P KDZ from here: https://forum.xda-developers.com/v20/how-to/t-mobile-v20-h918-10p-kdz-file-t3653797 and set this off to the side.
2a. Install both LGUP and common.dll
3. Search, download and install LGMobileDriver.
4. Completely Power off the v20 (or to remove and put the battery back)
5. Plug the USB end of sync cable to your PC
6. Press and hold "Volume Up"
7. Plug the USB in to the v20. The phone will enter download mode (or Firmware Update). Now you can release the "Volume Up".
8. Run LGUP. The program will recognize the v20.
9. At the file path, click "..." and choose the .kdz file 10P
10.Choose "UPGRADE"
11.Click "Start" and wait until the process is complete.
The phone will go thru its phases.
After about 10-15 minutes, the phone will reboot. You will land at your lockscreen. This does not wipe your data. Once you are at the lockscreen, run a factory reset within the settings app.
Let the phone cycle thru the reset and bam! You are back to stock!
To confirm my work, I adb reboot recovery to verify twrp is no longer there. Settings shows 10P software.
This guide is to return a user back to stock. I am getting ready to sell my device - this was the steps I took to return the software to stock. Don't forget to lock bootloader after.
Saving this one just in case - If you need clarification on something, please ask.I did my best to explain my process.
HiddenKnight said:
Hello everyone!
A little bit of a back story here - I was on NATF's rom when I proceeded to take the flashable 10Q/10R updates posted by @dimm0k. These newer updates, starting with 10P, are Anti-Rollback. I spent some time poking around trying to find answers on how to return to stock and how I could do this in a way that seemed comfortable to me.
I have found that ARB 0 is interchangeable with anything ARB 0. Anything that is ARB1, is interchangeable with ARB1, and so forth if LG decides to up the values to '2' or maybe even '3'.
If you are ever curious and want to know on later firmwares if you have ARB and what version it is, use this dialer code:
*#*#244773825625#*#*
###
I AM IN NO WAY RESPONSIBLE FOR YOUR DEVICE. THIS IS A AT YOUR OWN RISK TUTORIAL.
###
Moving forward here - I was able to flash 10P KDZ to remove TWRP and revoke root.
Requirements:
H918 TMO V20
10P/10Q/10R partial update software by dimm0k
1. Download LGUP_Store_Frame_Ver_1_14_3.msi and search for LGUP_common.dll ( I actually used the G5 dll)
1a. Download 10P KDZ from here: https://forum.xda-developers.com/v20/how-to/t-mobile-v20-h918-10p-kdz-file-t3653797 and set this off to the side.
2a. Install both LGUP and common.dll
3. Search, download and install LGMobileDriver.
4. Completely Power off the v20 (or to remove and put the battery back)
5. Plug the USB end of sync cable to your PC
6. Press and hold "Volume Up"
7. Plug the USB in to the v20. The phone will enter download mode (or Firmware Update). Now you can release the "Volume Up".
8. Run LGUP. The program will recognize the v20.
9. At the file path, click "..." and choose the .kdz file 10P
10.Choose "UPGRADE"
11.Click "Start" and wait until the process is complete.
The phone will go thru its phases.
After about 10-15 minutes, the phone will reboot. You will land at your lockscreen. This does not wipe your data. Once you are at the lockscreen, run a factory reset within the settings app.
Let the phone cycle thru the reset and bam! You are back to stock!
To confirm my work, I adb reboot recovery to verify twrp is no longer there. Settings shows 10P software.
This guide is to return a user back to stock. I am getting ready to sell my device - this was the steps I took to return the software to stock. Don't forget to lock bootloader after.
Click to expand...
Click to collapse
if I'm not mistaken, simply re-locking your bootloader would wipe your device and on the first boot after would restore your recovery from backup, wrong out TWRP. that said, sorry to see a fellow LGV20 user go...
dimm0k said:
if I'm not mistaken, simply re-locking your bootloader would wipe your device and on the first boot after would restore your recovery from backup, wrong out TWRP. that said, sorry to see a fellow LGV20 user go...
Click to expand...
Click to collapse
I didn't want to leave anything behind. I guess this method above is the long way and did work.
Sorry to leave. But good luck guys!
Wish I seen this before I did the OTA update for 10q ?
Couldn't you try to sell your phone with the bootloader already unlocked?
I would have paid more for one pre-unlocked.
How do you lock the bootlooder. I gotta get a replacement because my phone started to overheat regularly up to 180 degrees Fahrenheit so much so that I get severe seven retention and my DAC stopped functioning.
mookiexl said:
How do you lock the bootlooder. I gotta get a replacement because my phone started to overheat regularly up to 180 degrees Fahrenheit so much so that I get severe seven retention and my DAC stopped functioning.
Click to expand...
Click to collapse
Go to settings developer options lock bootloader done
---------- Post added at 01:01 AM ---------- Previous post was at 12:58 AM ----------
stillblaze01 said:
Go to settings developer options lock bootloader done
Click to expand...
Click to collapse
That is how to lock the bootloader but will that return to stock?????
Actually that isn't the way to lock the bootloader. You fastboot the command bootloader lock and then find KDZ stock firmware and flash.
mookiexl said:
Actually that isn't the way to lock the bootloader. You fastboot the command bootloader lock and then find KDZ stock firmware and flash.
Click to expand...
Click to collapse
You are correct. But I flashed kdz and then. Locked bootloader using dab. I did it back wards but it worked
I cant enter download mode because i changed LAF (Download Mode) for TWRP to root the device, i cant use your method and dont know how you did it if your version is the same as mine V10P
ernestico911 said:
I cant enter download mode because i changed LAF (Download Mode) for TWRP to root the device, i cant use your method and dont know how you did it if your version is the same as mine V10P
Click to expand...
Click to collapse
did u find any solution for it
Flash the zip at the end of the first post in the lafsploit thread....
-- Brian
Miggs22 said:
did u find any solution for it
Click to expand...
Click to collapse
yes just flashed the same version via TWRP
Hello, I just want to clarify since there are no other places to ask, is firmwares 10p 10q 10r 10s 10t and 10u are ARB1? or is it just 10p that's ARB0?
10a to 10o == ARB 0
10p to 10u == ARB 1
-- Brian
20G KDZ if anyone needs to return to complete stock Oreo
https://megaupload.nz/o6sfkalbb2/H91820g_00_1010_kdz
https://megaupload.nz/K0Q9j6labe/LGUP_c_dll
Hello everyone!
Since I've unlocked and rooted my Pixel 2 it keeps failing the OTA update. I get the notification and the update is downloaded but when it's being installed, there is an undefined error. For all updates I had to sideload the OTA file via ADB. Honestly, I don't really know what could have caused this issue, as the first OTA update when I got the phone with all stock settings and roms it worked fine. Currently I can only instal the OTA.zip updates via ADB.
Things I did so far which could have caused the issue:
flash boot.img via fastboot (Magisk Root)
unlock bootloader via fastboot
Things I tried to resolve the issue:
Lock the bootloader again
Flash full stock rom with fastboot and official google script (failed "couldn't write bootloader.img" altough I had it unlocked)
Factory reset
Also, everytime I reboot my phone i get the message that something is wrong with my phone and I should check it with my vedor. But everything is working perfectly - except for the updates.
Does anyone else have similar experiences?
ekalz said:
Things I did so far which could have caused the issue:[/B]
flash boot.img via fastboot (Magisk Root)
unlock bootloader via fastboot
Click to expand...
Click to collapse
My understanding is that anytime you modify the file system, etc (rooting patches some files) then it will fail the integrity check and not OTA.
ekalz said:
Also, everytime I reboot my phone i get the message that something is wrong with my phone and I should check it with my vedor. But everything is working perfectly - except for the updates.
?
Click to expand...
Click to collapse
Yes! I have that exact same message when I reboot. I flashed TWRP, rooted with Magisk Manager. I can't tell any negative concequences either.
SweetSofie said:
My understanding is that anytime you modify the file system, etc (rooting patches some files) then it will fail the integrity check and not OTA.
Yes! I have that exact same message when I reboot. I flashed TWRP, rooted with Magisk Manager. I can't tell any negative concequences either.
Click to expand...
Click to collapse
The error you see about system integrity (or whatever it is ) when you boot the phone is due to Magisk patching the dtbo partition. It's a bug and will most likely get fixed eventually. It's nothing to be concerned about though. You can safely ignore it.
Can you root without patching or unlocking the bootloader so you don't fail the integrity check?
robocuff said:
The error you see about system integrity (or whatever it is ) when you boot the phone is due to Magisk patching the dtbo partition. It's a bug and will most likely get fixed eventually. It's nothing to be concerned about though. You can safely ignore it.
Click to expand...
Click to collapse
Thanks for the clarification! I would love to learn more about that stuff, I'm just not sure where to start learning.
I have the same problem with my pixel 2. I have tried full factory reset by flashing stock image. I have tried the recovery script some user posted in the p2 forum.
I contacted Google support about it and now i am waiting for 2nd line to contact me.
I will post here if/when i get a solution.
With an unlocked bootloader, you will not be able to update via Android; you must sideload. However, sideload will fail if you do not have the factory boot and dtbo.
So, assuming you are rooted:
0. You must start with factory boot and dtbo images; if you are running custom, download the factory image that corresponds to your build, unpack and flash boot and dtbo
1. Download the latest ota.zip from the Google Developers website
2. Connect phone to computer, use ADB to reboot into bootloader
3. Once in bootloader, hit Power + Vol Up to bring up menu, use volume buttons to scroll to Apply update via ADB
4. Use ADB to sideload:
Code:
adb sideload update.zip
5. Select Reboot System in recovery when complete
socal87 said:
With an unlocked bootloader, you will not be able to update via Android; you must sideload. However, sideload will fail if you do not have the factory boot and dtbo.
So, assuming you are rooted:
0. You must start with factory boot and dtbo images; if you are running custom, download the factory image that corresponds to your build, unpack and flash boot and dtbo
1. Download the latest ota.zip from the Google Developers website
2. Connect phone to computer, use ADB to reboot into bootloader
3. Once in bootloader, hit Power + Vol Up to bring up menu, use volume buttons to scroll to Apply update via ADB
4. Use ADB to sideload:
Code:
adb sideload update.zip
5. Select Reboot System in recovery when complete
Click to expand...
Click to collapse
That would explain a lot but are you sure its the unlocked bl that causes this problem? Google support told me it should not matter. Would it work with ota if i lock the bl again?
smorgar said:
That would explain a lot but are you sure its the unlocked bl that causes this problem? Google support told me it should not matter. Would it work with ota if i lock the bl again?
Click to expand...
Click to collapse
I am not certain, but with unlocked bootloader and stock kernel, the OTA still failed to install within system. I was able to sideload it, but the kernel had to be stock.
I just posted a guide how to get around this by using the factory image, as it does not appear to perform signature checks.
Thread
socal87 said:
I am not certain, but with unlocked bootloader and stock kernel, the OTA still failed to install within system. I was able to sideload it, but the kernel had to be stock.
I just posted a guide how to get around this by using the factory image, as it does not appear to perform signature checks.
Thread
Click to expand...
Click to collapse
I tried relocking BL and proceeded to install OTA but same error presists. (OTA: Feb patch -> Mar patch)
smorgar said:
I tried relocking BL and proceeded to install OTA but same error presists. (OTA: Feb patch -> Mar patch)
Click to expand...
Click to collapse
Did you try to sideload via ADB?
socal87 said:
Did you try to sideload via ADB?
Click to expand...
Click to collapse
No I am waiting to get it resolved by Google so that I can install OTA in the future.
smorgar said:
No I am waiting to get it resolved by Google so that I can install OTA in the future.
Click to expand...
Click to collapse
Why don't you try sideloading the OTA? It worked for me. As for the future, you might not able to take OTAs without a completely stock image, but if you're just trying to get the March security update, either sideload the OTA, or flash the stock system image from the most recent factory ROM as described in my thread.
socal87 said:
Why don't you try sideloading the OTA? It worked for me. As for the future, you might not able to take OTAs without a completely stock image, but if you're just trying to get the March security update, either sideload the OTA, or flash the stock system image from the most recent factory ROM as described in my thread.
Click to expand...
Click to collapse
I was trying to fix the problem permanently so that i dont have to sideload if i dont want to.
**** went to ****... I did factory reset as the Google support person told me. Tried installing OTA again but it did not work. So they left me waiting for second line support to contact me but its now been the whole weekend and no support.
After support told me to do reset the last time the phone began to freeze and crash apps randomly. So i tried to install full factory image via fastboot but that was the last time the phone booted up. Now its completely dead.
When i try to boot the phone nothing happens. If i hold power button for 20-30 sec i sometimes get a short vibration and a line of pixels flashing by on the screen then nothing more happens. Now im waiting for Google support for real. Pray for my dead pixel2
If anyone have some tips for me im willing to try. The phone does not seem to boot and the PC does not recognize it at all.
You'll need to go into fastboot mode. Download the latest factory image and unzip. You'll find a flash all batch file to run in Windows. It will then do its magic. Remove the "-w" parameter at the end of it so that it doesn't wipe your system. You can always manually factory reset. That parameter has been known to have issues.
davidisflash said:
You'll need to go into fastboot mode. Download the latest factory image and unzip. You'll find a flash all batch file to run in Windows. It will then do its magic. Remove the "-w" parameter at the end of it so that it doesn't wipe your system. You can always manually factory reset. That parameter has been known to have issues.
Click to expand...
Click to collapse
How do i enter fastboot mode when the phone wont turn on and the PC cant recognize it?
Some update regarding google support:
I was told to wait for 24-72h for second line support to contact me. They contacted me this saturday, about a week later and they are absolutely useless. They dont read what you type fully and they seem to not really know what they are talking about. I honestly feel like they have outsourced their support to Bagdad or something. My own enligsh skillz is not so good, but theirs is as basic as it gets. Feels kinda like chatting with a bot.
Some tips when contacting google support via chat: Dont use any advanced words. Dont type more than 5-10 words per sentence or they will not read it fully. Have patience, they take forever to respond, even a short sentence like: "What can i do for you?"
/rant
smorgar said:
How do i enter fastboot mode when the phone wont turn on and the PC cant recognize it?
Some update regarding google support:
I was told to wait for 24-72h for second line support to contact me. They contacted me this saturday, about a week later and they are absolutely useless. They dont read what you type fully and they seem to not really know what they are talking about. I honestly feel like they have outsourced their support to Bagdad or something. My own enligsh skillz is not so good, but theirs is as basic as it gets. Feels kinda like chatting with a bot.
Some tips when contacting google support via chat: Dont use any advanced words. Dont type more than 5-10 words per sentence or they will not read it fully. Have patience, they take forever to respond, even a short sentence like: "What can i do for you?"
/rant
Click to expand...
Click to collapse
And so how did everything work out for you? Were they able to get you resolved, or are they just RMA'ing your phone?
No resolution. I sent it back to uk for replacement via seller.
smorgar said:
How do i enter fastboot mode when the phone wont turn on and the PC cant recognize it?
Some update regarding google support:
I was told to wait for 24-72h for second line support to contact me. They contacted me this saturday, about a week later and they are absolutely useless. They dont read what you type fully and they seem to not really know what they are talking about. I honestly feel like they have outsourced their support to Bagdad or something. My own enligsh skillz is not so good, but theirs is as basic as it gets. Feels kinda like chatting with a bot.
Some tips when contacting google support via chat: Dont use any advanced words. Dont type more than 5-10 words per sentence or they will not read it fully. Have patience, they take forever to respond, even a short sentence like: "What can i do for you?"
/rant
Click to expand...
Click to collapse
How are you trying to turn on the phone? What about it just holding the power button for like 30 seconds, releasing, then again but this time holding power button AND volume down? Is the battery charged?
There are two separate drivers for Windows. When the phone is in fastboot mode, you'll need to use the separate adb / fastboot drivers. In fact in device manager, this will appear as a separate device (that's because the device will register under a different device ID).
The main Windows driver is here:
https://developer.android.com/studio/run/win-usb.html
The adb driver is here:
Good page I used to debug it not being recognized:
https://forum.xda-developers.com/pixel-2-xl/help/device-recognized-adb-fastboot-t3698716
davidisflash said:
How are you trying to turn on the phone? What about it just holding the power button for like 30 seconds, releasing, then again but this time holding power button AND volume down? Is the battery charged?
There are two separate drivers for Windows. When the phone is in fastboot mode, you'll need to use the separate adb / fastboot drivers. In fact in device manager, this will appear as a separate device (that's because the device will register under a different device ID).
The main Windows driver is here:
https://developer.android.com/studio/run/win-usb.html
The adb driver is here:
Good page I used to debug it not being recognized:
https://forum.xda-developers.com/pixel-2-xl/help/device-recognized-adb-fastboot-t3698716
Click to expand...
Click to collapse
I have done all the basic and advanced stuff. I had it dead for about a week to play around with. Used to work in a mobile repair shop so this isnt something new for me.
For those of you that are rooted and would like to return back to stock with a relocked bootloader follow the steps.
This could also be useful for those of you stuck with a non bootable device. It will make your device eligible for warranty replacement again.
1. Flash stock boot.img (link) with the following command:
Code:
Fastboot Flash boot Stock_Boot.img
2.Re-lock bootloader with
Code:
Fastboot flashing lock
3. Enter recovery with Vol+ and USB plugged in. Then go down to wipe and Factory restore. Reboot and DONE
Hope this tip is useful to some.
See yah
Stock Boot.img Link
https://drive.google.com/open?id=1SqjkwVzNC3nAqDkNDMdEpqQH7viXDmb4
Is this the stock boot image for the regular non-carrier Razer Phone?
Kalveitt said:
Is this the stock boot image for the regular non-carrier Razer Phone?
Click to expand...
Click to collapse
This is for Non-Carrier.
Confirmed , you just made my day sir . i resurrect my device i flashed how you said with that command but i need to add -i 0x1532 , i got a message that is gonna flash it on b partition ,he said is done , after i restart it i got a message on phone (erasing) after i done the steps to factory reset it , i managed to get in the stock recovery, after 10 minutes i booted in the software all fine but not the wifi and flashlight ,
thank you once again for your hard work.
we keep in touch maybe i can do the wifi and flashlight
my device
Razer three uk
Anyone flash back to stock and have issues installing the latest update? Downloads but won't install?
So I relocked the bootloader before this file was released, by mistake my phone has twrp on both partitions, so when ever I boot it just says device corrupt and reboot I can however access qualcom diagnostics by pressing volume up + volume down at the same time, just wondering if phone can be restored through that interface
Btw as I'm finding out.. This doesn't reset to stock! It does relock your phone and you loose root, but any changes made to the system files while you were rooted sticks.. Ie hosts file changes. I'm back to "stock" and the adaway hosts file changes are still present.. I expect other changes are still there too and that's why I can't flash the update. guess I'm waiting for factory images for a full stock as well)
mikeandjaimie said:
Btw as I'm finding out.. This doesn't reset to stock! It does relock your phone and you loose root, but any changes made to the system files while you were rooted sticks.. Ie hosts file changes. I'm back to "stock" and the adaway hosts file changes are still present.. I expect other changes are still there too and that's why I can't flash the update. guess I'm waiting for factory images for a full stock as well)
Click to expand...
Click to collapse
Hopefully they get released at all at this point...sure looking less and less likely at this juncture with incremental push updates coming from Razer.
mikeandjaimie said:
Btw as I'm finding out.. This doesn't reset to stock! It does relock your phone and you loose root, but any changes made to the system files while you were rooted sticks.. Ie hosts file changes. I'm back to "stock" and the adaway hosts file changes are still present.. I expect other changes are still there too and that's why I can't flash the update. guess I'm waiting for factory images for a full stock as well)
Click to expand...
Click to collapse
Or if someone with a US/NA Razer Phone was nice enough to upload and post there TWRP backups before the the partitions were modified. We have a backup for the 3UK people, but one from US/NA Razer Phone, and one from the EU/Non Carrier Razer would help alot of people. I know people have them, just no one willing to share I guess Will probably be months if Razer ever actually posts the Factory Images.
There have been files for both uploaded and it was determined you couldn't use them for 3 phones already.. That's how alot of people got non working phones that just say corrupted now..
Gotta wait till factory images are released if you are on 3.
mikeandjaimie said:
Btw as I'm finding out.. This doesn't reset to stock! It does relock your phone and you loose root, but any changes made to the system files while you were rooted sticks.. Ie hosts file changes. I'm back to "stock" and the adaway hosts file changes are still present.. I expect other changes are still there too and that's why I can't flash the update. guess I'm waiting for factory images for a full stock as well)
Click to expand...
Click to collapse
I manage to find the location of the ota Update.zip and tried flashing it in the stock recovery but it also fails on stage 2.
As you pointed it out. The update is failing because it's still recognizing the system as modified.
I'll leave my link up to help those who are stuck on a boot loop with an unlocked bootloader this will at least make them eligible for warranty replacement so it's something... Follow the steps and then send it off to Razer for warranty replacement. It's a shame really to send out a phone that could easily be fixed with system images. Razer has really dropped the ball. Not having system images from day one really hurt the enthusiast development for this device. If your not able to send it out for warranty replacement then all you can really do is wait for Razer to release the images and I think they may not release them until they release Oreo.
I followed the step-by-step for putting twrp on mine. All seems to go well but it just keeps booting back into bootloader. If I turn it off and hold the vol+ while plugging in the USB I just get the Razer logo and nothing. When I finally gave up I flashed the stock boot in the OP. I'm up and running now but no BT and the latest update just fails. Relocked the BL and no system changes were made since TWRP never seems to have installed, if though I got a successful when complete. I hate to send this back, anyone know if they can reflash it remotely? I'll pay the fee, just need the phone working on WiFi again.
Does this method also work if am rooted, running a stock 8.1 rom and kernal?
Solved Flash Razer Phone To Stock and gain OTA capable!!
This is for the Razer Phone!!!! Fixed Warranty and OTA Update!! As if freshly purchased!!!!
I figured out that unless you use the Razer provided images from their support site your phone will not function properly as any other procedure will be extremely time consuming on a command prompt!!! Imagine individually flashing all components in their respective orders and flashing to both partitions is a requirement so use the provide images and the flashall.sh command included in the downloaded file.
The instructions for gaining the ability to flash the update via windows cmd.
follow the original instructions from the razer support site and the do this for the connection or what it's actually called (Environment variables) you will need to navigate on your pc to the system properties window the click on environment variables, two panes in the window at the lower pane look for the PATH line which is the pathe for the variable to point cmd to file system where your stock razer update is located. If you followed all steps : usb drivers, androis sdk 28.xx or higher extracted to C:/adb folder, navigated to system window then update driver connect phone in bootloader mode then open update driver browse computer let me pick from a list of drivers on my computer and install the android bootloader interface continue even though it says not recomended it works.
now open your razer downloaded factory file and double click flashall.sh and wait till finished then stop the reboot and boot to booloader and open windows cmd and type fastboot devices then type fastboot flashing lock and lock it up, Done sorry for the unorganized text but I'm sure nobody cares as long as it works right? !#fi enjoy!!!
Solved!!!!!!!!!!!!!
---------- Post added at 06:41 AM ---------- Previous post was at 06:20 AM ----------
Mike02z said:
I followed the step-by-step for putting twrp on mine. All seems to go well but it just keeps booting back into bootloader. If I turn it off and hold the vol+ while plugging in the USB I just get the Razer logo and nothing. When I finally gave up I flashed the stock boot in the OP. I'm up and running now but no BT and the latest update just fails. Relocked the BL and no system changes were made since TWRP never seems to have installed, if though I got a successful when complete. I hate to send this back, anyone know if they can reflash it remotely? I'll pay the fee, just need the phone working on WiFi again.
Click to expand...
Click to collapse
I solved this and if you need detailed instructions or help anyone can ask and I will help and yes it does return it to brand new fresh ota and warranty is returned, everything works as it should no bugs wifi works and data on sim.
As for twrp you should flash it to one slot not both as you may know system is on both slots you could have two slots with twrp and no system lol I did that before!
Your phone can be stock but not ota with twrp fyi.
mikedeboefis said:
Solved!!!!!!!!!!!!!
---------- Post added at 06:41 AM ---------- Previous post was at 06:20 AM ----------
I solved this and if you need detailed instructions or help anyone can ask and I will help and yes it does return it to brand new fresh ota and warranty is returned, everything works as it should no bugs wifi works and data on sim.
As for twrp you should flash it to one slot not both as you may know system is on both slots you could have two slots with twrp and no system lol I did that before!
Your phone can be stock but not ota with twrp fyi.
Click to expand...
Click to collapse
Thanks, but I returned my Razer within the first 30 days. Just not for me.
mikedeboefis said:
This is for the Razer Phone!!!! Fixed Warranty and OTA Update!! As if freshly purchased!!!!
I figured out that unless you use the Razer provided images from their support site your phone will not function properly as any other procedure will be extremely time consuming on a command prompt!!! Imagine individually flashing all components in their respective orders and flashing to both partitions is a requirement so use the provide images and the flashall.sh command included in the downloaded file.
The instructions for gaining the ability to flash the update via windows cmd.
follow the original instructions from the razer support site and the do this for the connection or what it's actually called (Environment variables) you will need to navigate on your pc to the system properties window the click on environment variables, two panes in the window at the lower pane look for the PATH line which is the pathe for the variable to point cmd to file system where your stock razer update is located. If you followed all steps : usb drivers, androis sdk 28.xx or higher extracted to C:/adb folder, navigated to system window then update driver connect phone in bootloader mode then open update driver browse computer let me pick from a list of drivers on my computer and install the android bootloader interface continue even though it says not recomended it works.
now open your razer downloaded factory file and double click flashall.sh and wait till finished then stop the reboot and boot to booloader and open windows cmd and type fastboot devices then type fastboot flashing lock and lock it up, Done sorry for the unorganized text but I'm sure nobody cares as long as it works right? !#fi enjoy!!!
Click to expand...
Click to collapse
Yeah.. I need help on this one. I tried it and fastboot doesn't allow me to flash_all script.
How do you even double click flashall.sh?
I know this is kind of old but I'm currently having the same problem as a person above. I've tried using the flash_all command but it will only stay at "waiting for device" and doing flash_all.sh doesn't work.