Database Info

Bricked MAXX, Need Help

Hello,
I have been crack flashing for a long time, but when I got the Droid Maxx from verizon I was disappointed at the lack of an unlocked bootloader. I had been running safestrap and was getting the phone ready to return for a refund so I can get the developer edition.
So, it looks like using safestrap I completely wiped the system partition. I can get the phone to boot to flashboot mode or to the safestrap flash screen but that is all.
Using RSDlite I attempted to flash 12.9.0, but get the return message "Failed flashing process. 2/17 flash partition "gpt.bin" -> Phone returned FAIL. On the phone it said:
"downgraded security version
update gpt_main version failed
preflash validation failed for GPT."
So it looks like the issue might be because I am flashing the FXZ file for 12.15.15, but I cannot find the FXZ file for it.
I also tried using House of Moto. Attached is a screen shot of what I get.
So basically it looks like I have no ROM whatsoever. Is there a way out of this so I can return the phone for a refund?
Thanks in advance!

I realized that I had not set things up correctly for House of Moto, I ran it, and boot.img, system.img, and motoboot.img are not loading because they are from the previous image and it will not allow a downgrade.
So, I guess I need to get the factory image of the latest update, or perhaps get those *.img files from someone with a working phone and drop them in to folder before flashing.
Anyone have the factory image after the OTA? Or perhaps the missing files I need (if dropping them will actually work, of course)?

kclantz said:
I realized that I had not set things up correctly for House of Moto, I ran it, and boot.img, system.img, and motoboot.img are not loading because they are from the previous image and it will not allow a downgrade.
So, I guess I need to get the factory image of the latest update, or perhaps get those *.img files from someone with a working phone and drop them in to folder before flashing.
Anyone have the factory image after the OTA? Or perhaps the missing files I need (if dropping them will actually work, of course)?
Click to expand...
Click to collapse
,
I am having the same problem only I am on the Droid Ultra and not the Maxx, I too need the files for the latest OTA because the two older files are supposedly out dated for me, i get a bunch of failures. What sucks is some files were clearly restored because it erased Safestrap and now i have stock recovery but it didn't restore the OS or anything so i cannot boot up into anything but fastboot....hopefully someone uploads the latest ota to the site or even the forums....good luck to you. i need it as well.

ahjee said:
,
I am having the same problem only I am on the Droid Ultra and not the Maxx, I too need the files for the latest OTA because the two older files are supposedly out dated for me, i get a bunch of failures. What sucks is some files were clearly restored because it erased Safestrap and now i have stock recovery but it didn't restore the OS or anything so i cannot boot up into anything but fastboot....hopefully someone uploads the latest ota to the site or even the forums....good luck to you. i need it as well.
Click to expand...
Click to collapse
I'm in the same boat, but not quite as bad. I've got the mini, and it boots into the normal mode, but not all things work - touchless controls crash every time I try to open it, and my calendars won't sync. My recovery is gone, when I try to boot into it, I get an android logo with it's chest open with a red triangle.
I tried using RSD Lite and fastboot with the original stock image files, but the result are the same. I'm going to hold out for someone to post an image with the OTA included or another workaround. Amazing how we got the same problems at roughly the same time after the OTA.

rds217 said:
I'm in the same boat, but not quite as bad. I've got the mini, and it boots into the normal mode, but not all things work - touchless controls crash every time I try to open it, and my calendars won't sync. My recovery is gone, when I try to boot into it, I get an android logo with it's chest open with a red triangle.
I tried using RSD Lite and fastboot with the original stock image files, but the result are the same. I'm going to hold out for someone to post an image with the OTA included or another workaround. Amazing how we got the same problems at roughly the same time after the OTA.
Click to expand...
Click to collapse
if yours boots into the OS maybe you can still root it, after you root it you can then modify system apps, getting rid of touchless control and then reinstall it, may fix the force close. also if you manage to gain root you could install safestrap. the android with the triangle is the stock recovery, i forget what buttons or button combination you have to hit to make the menu appear but that is the stock recovery by what you're describing

So I just got back from the Verizon store, I went in to see if they could flash the files I need. They told me they couldn't but gave me a number at motorola to see if they would e-mail the files to me.
Unfortunately that didn't work. Motorola said I could send the phone in for a repair, and that was my only option.
I think I'll take the second option and wait until someone posts the files and flash them with RSD Lite.
I just hope that happens soon, as I am wanting to return the phone and get the developer edition. I have until Saturday to return it and I doubt they will give me a refund with it in this state.

ahjee said:
if yours boots into the OS maybe you can still root it, after you root it you can then modify system apps, getting rid of touchless control and then reinstall it, may fix the force close. also if you manage to gain root you could install safestrap. the android with the triangle is the stock recovery, i forget what buttons or button combination you have to hit to make the menu appear but that is the stock recovery by what you're describing
Click to expand...
Click to collapse
Here's the issue, I can't boot into write-protected off mode. When I tried running HouseOfMoto, I flashed stock recovery for pre-OTA; since I received the OTA, I can't install PwnMyMoto, which is what gave me the write-protection off mode in the first place. Now when I go from the bootloader into recovery, I get the dead android + red triangle, what you call stock recovery.
I have root level access, but it's all but useless since the system is write protected. In other words, no Safestrap. I'll have to live with what I've got until someone finds time and reason to upload the post-OTA image or something newer.
Edit: Fixed it, maybe it will work for you guys. Check the PwnMyMoto thread for the source, I can't post it due to being new.
jcase said:
If you used 1.1 and have a problem with recovery coming back, run the following command:
adb shell su -c "dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/dev/block/platform/msm_sdcc.1/by-name/recovery"
Click to expand...
Click to collapse

rds217 said:
Here's the issue, I can't boot into write-protected off mode. When I tried running HouseOfMoto, I flashed stock recovery for pre-OTA; since I received the OTA, I can't install PwnMyMoto, which is what gave me the write-protection off mode in the first place. Now when I go from the bootloader into recovery, I get the dead android + red triangle, what you call stock recovery.
I have root level access, but it's all but useless since the system is write protected. In other words, no Safestrap. I'll have to live with what I've got until someone finds time and reason to upload the post-OTA image or something newer.
Edit: Fixed it, maybe it will work for you guys. Check the PwnMyMoto thread for the source, I can't post it due to being new.
Click to expand...
Click to collapse
With my issue I cannot even get to the point where I can use ADB. I am pretty much stuck with fastboot commands. I can get the bootloader and stock recovery, but nothing more.
Is there something that I can edit in the update file that would allow the version downgrade test to pass? I've played around with the XML file, but I am not having much luck.

kclantz said:
With my issue I cannot even get to the point where I can use ADB. I am pretty much stuck with fastboot commands. I can get the bootloader and stock recovery, but nothing more.
Is there something that I can edit in the update file that would allow the version downgrade test to pass? I've played around with the XML file, but I am not having much luck.
Click to expand...
Click to collapse
Your only current options are to wait for a newer FXZ or have Motorola perform a repair on it.
Sent from my SCH-I605 using Tapatalk

erishasnobattery said:
Your only current options are to wait for a newer FXZ or have Motorola perform a repair on it.
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
Thanks, that was what I was afraid of. I guess now I will check obsessively for the new FXZ files. Got have some way to spend my day (you know, as opposed to doing my job ).

[Q] How to take OTA update after Sunshine

Please forgive me for having to ask what I'm sure sounds like a stupid question, but I have no idea how to accept the OTA update Verizon is attempting to send me to version 4.4.4 on my HTC One M8 now that I have used Sunshine to attain S-Off and have TWRP and SuperSU installed.
I have used ADB, but am not very familiar with it at all.
I saw threads talking about flashing ROMS, but for the most part it really seems like Greek to me.
I had only gone down the Sunshine road because I wanted root access mainly for one app--Lightflow. In retrospect I'm feeling like I opened a can of worms. But the can is open, and the worms are out there, so now I need to learn how to handle them.
I know I am supposed to keep S-off, no matter what I do. I think perhaps I'm supposed to revert back somehow to a "stock" bootloader (instead of TWRP--is that right?) but I don't have any idea how to do that (though I expect ADB is involved), and I also don't know what effect that would have on SuperSu, as I vaguely recall TWRP may have been required for SuperSU to work.
I'm really lost.
Any help, in very easy to understand terms (pretend you're trying to explain this to your grandmother) would be appreciated.
Thanks!

Andyw2100 said:
Please forgive me for having to ask what I'm sure sounds like a stupid question, but I have no idea how to accept the OTA update Verizon is attempting to send me to version 4.4.4 on my HTC One M8 now that I have used Sunshine to attain S-Off and have TWRP and SuperSU installed.
I have used ADB, but am not very familiar with it at all.
I saw threads talking about flashing ROMS, but for the most part it really seems like Greek to me.
I had only gone down the Sunshine road because I wanted root access mainly for one app--Lightflow. In retrospect I'm feeling like I opened a can of worms. But the can is open, and the worms are out there, so now I need to learn how to handle them.
I know I am supposed to keep S-off, no matter what I do. I think perhaps I'm supposed to revert back somehow to a "stock" bootloader (instead of TWRP--is that right?) but I don't have any idea how to do that (though I expect ADB is involved), and I also don't know what effect that would have on SuperSu, as I vaguely recall TWRP may have been required for SuperSU to work.
I'm really lost.
Any help, in very easy to understand terms (pretend you're trying to explain this to your grandmother) would be appreciated.
Thanks!
Click to expand...
Click to collapse
Taking the OTA is simple, you'll need your stock 4.4.3 recovery installed not TWRP. If you try to take it as you are right now it will fail everytime because of TWRP. I'm going to assume you haven't modified your stock ROM in anyway so accept the OTA and let it install. You will not lose S-OFF so rooting is simple. Reinstall TWRP and flash the latest SuperSU zip file.

The Stig 04 said:
Taking the OTA is simple, you'll need your stock 4.4.3 recovery installed not TWRP. If you try to take it as you are right now it will fail everytime because of TWRP. I'm going to assume you haven't modified your stock ROM in anyway so accept the OTA and let it install. You will not lose S-OFF so rooting is simple. Reinstall TWRP and flash the latest SuperSU zip file.
Click to expand...
Click to collapse
Thanks for the response.
So the question is how do I go back to my stock recovery instead of TWRP?
And then after taking the update, what do I need to do to reinstall TWRP and then flash the latest SuperSU.zip file?
I realize I should know this stuff, but I had help from the Sunshine folks last time, so I really don't remember everything that went on, or exactly what I did vs. what they did, etc.
Thanks again!

Andyw2100 said:
Thanks for the response.
So the question is how do I go back to my stock recovery instead of TWRP?
And then after taking the update, what do I need to do to reinstall TWRP and then flash the latest SuperSU.zip file?
I realize I should know this stuff, but I had help from the Sunshine folks last time, so I really don't remember everything that went on, or exactly what I did vs. what they did, etc.
Thanks again!
Click to expand...
Click to collapse
You don't need to do any of that.
Download the exe from this thread: http://forum.xda-developers.com/showthread.php?p=56211035
run it and you will be on stock 4.4.4.
To get TWRP back you have to flash it fastboot (lots of tutorials all over the forum for that) and with the recovery installed you can just flash SuperSU in recovery to gain root again.

The Stig 04 said:
Taking the OTA is simple, you'll need your stock 4.4.3 recovery installed not TWRP. If you try to take it as you are right now it will fail everytime because of TWRP. I'm going to assume you haven't modified your stock ROM in anyway so accept the OTA and let it install. You will not lose S-OFF so rooting is simple. Reinstall TWRP and flash the latest SuperSU zip file.
Click to expand...
Click to collapse
berndblb said:
You don't need to do any of that.
Download the exe from this thread: http://forum.xda-developers.com/showthread.php?p=56211035
run it and you will be on stock 4.4.4.
To get TWRP back you have to flash it fastboot (lots of tutorials all over the forum for that) and with the recovery installed you can just flash SuperSU in recovery to gain root again.
Click to expand...
Click to collapse
Thanks. That thread says that using that .exe is going to wipe my phone, which would then mean I need to restore it from a backup. I think I'd really just rather take the OTA update to 4.4.4, since in the future I'm going to want to take other OTA updates as well. So if I can learn how to return to my stock recovery now, and the rest of it for this OTA update, I should be good to go for future OTA updates.
Thanks, though.
So my questions above remain about how to revert to the stock recovery, and then how to reinstall TWRP and SuperSU.
Thanks!

Andyw2100 said:
Thanks. That thread says that using that .exe is going to wipe my phone, which would then mean I need to restore it from a backup. I think I'd really just rather take the OTA update to 4.4.4, since in the future I'm going to want to take other OTA updates as well. So if I can learn how to return to my stock recovery now, and the rest of it for this OTA update, I should be good to go for future OTA updates.
Thanks, though.
So my questions above remain about how to revert to the stock recovery, and then how to reinstall TWRP and SuperSU.
Thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2723159
Download the file "Stock Recovery 4.4.3" from the thread above. Flash that using ADB, once you take the OTA and are on 4.4.4 Flash TWRP using ADB again.
http://forum.xda-developers.com/showthread.php?t=1538053
Download SuperSu from the thread above and place that in your SD Card. Boot into recovery and install it. Though you should already have this on your computer or SD Card.
Edit: I believe there is an even easier way, just have never done it/tried it so I don't wanna lie and act like I know what to do.

The Stig 04 said:
http://forum.xda-developers.com/showthread.php?t=2723159
Download the file "Stock Recovery 4.4.3" from the thread above. Flash that using ADB, once you take the OTA and are on 4.4.4 Flash TWRP using ADB again.
http://forum.xda-developers.com/showthread.php?t=1538053
Download SuperSu from the thread above and place that in your SD Card. Boot into recovery and install it.
Click to expand...
Click to collapse
You have to flash the stock recovery in fastboot - not ADB. And you gotta make sure all the bloatware that comes with the original stock rom is in place or the OTA will fail (it does a "system integrity check" prior to applying the OTA). That can be a headache if you do not have a backup of apps you may have removed...
Each future update will be available within days of release here on XDA, either as a standalone firmware update or stock rooted rom or both. I would not take OTAs - ever.
Develop a solid backup routine and restoring your device is a 20 minute exercise...

Thanks to both of you.
I don't believe I removed any bloatware, so I think the OTA update should work.
How do I flash the stock recovery in fastboot?
Again, many thanks!

I just checked my ADB folder, and see a fastboot.exe there, so I imagine it's just a command like ADB. I'll give this a shot later. Again, many thanks to both of you for the assistance. I will post again with, hopefully, my good results, or with additional questions.
Thanks!

berndblb said:
You have to flash the stock recovery in fastboot - not ADB. And you gotta make sure all the bloatware that comes with the original stock rom is in place or the OTA will fail (it does a "system integrity check" prior to applying the OTA). That can be a headache if you do not have a backup of apps you may have removed...
Each future update will be available within days of release here on XDA, either as a standalone firmware update or stock rooted rom or both. I would not take OTAs - ever.
Develop a solid backup routine and restoring your device is a 20 minute exercise...
Click to expand...
Click to collapse
Sorry I thought fastboot and ADB was kinda that same thing seeing as it was refereed to as "fastboot/adb directory"? If not my bad! Also this is the method I always use to take OTA's and have never ever had a problem.

Andyw2100 said:
I just checked my ADB folder, and see a fastboot.exe there, so I imagine it's just a command like ADB. I'll give this a shot later. Again, many thanks to both of you for the assistance. I will post again with, hopefully, my good results, or with additional questions.
Thanks!
Click to expand...
Click to collapse
Put the recovery image into the same folder with your fastboot.exe
Open a command prompt from that folder (shift + right click > open cmd window here)
check connection with
Code:
fastboot devices
if successful
Code:
fastboot flash recovery <name of recovery>.img

Would you need to remove root before taking the OTA? Just curious.
Sent from my GT-N5110 using xda app-developers app

mumbles202 said:
Would you need to remove root before taking the OTA? Just curious.
Sent from my GT-N5110 using xda app-developers app
Click to expand...
Click to collapse
No. You will lose root after the ota so it doesn't matter but you can always get it back as long as you are S-OFF by flashing a custom recovery like TWRP and then flashing SuperSu.

Well, I have run into a snag right off the bat.
While the command "ADB Devices" sees the phone, "Fastboot Devices" does not.
Any ideas as to how to rectify this?
Thanks!

I did some googling, and this problem I solved on my own.
I had to use adb to get into fastboot USB mode or something with adb reboot bootloader, and then fastboot devices worked.
I'm now continuing on.

Well, so much for this being easy.
I believe I successfully flashed my stock recovery.
But apparently I no longer have the OTA update ready to install, as at some point I tried to run it again just to get TWRP up, and now it's not showing as available. And when I try to check for updates in Settings/Software update/Check new I get an error message that says Download Unsuccessful. We were not able to download this update.
For now I guess I'll wait and see if Verizon tries to send me the update again, or if it works if I check for it myself some other time. (Or if anyone here has any suggestions.)
Also, I still seem to have root access. I thought that I wouldn't, since I believe I have replaced TWRP with the stock recovery.

I'm also now getting a constant error message about Google Play Services having stopped. And my wi-fi doesn't seem to be connecting properly.
I'm really wondering just what the heck I've done.

Well, for anyone still following my saga...
Things are somewhat better, but not totally resolved.
I kept checking, and eventually I was able to download the OTA update to 4.4.4. I did, I updated, and all went smoothly. I then was able to flash TWRP and then install Super SU and I have root access again. So on that front, all is well.
The problems that remain, though, are that I still am having issues with Google Play Services quitting and my Wi Fi not connecting. Could these things be related somehow? I've tried clearing the cache and then actually all data from Google Play services, but that has not helped. I have deleted my networks, and then tried reconnecting to them, but that also has not helped. It shows my networks in range as "saved" or "disabled" but won't connect to any of them.
Any ideas for me?
Thanks.
And thanks for the help in getting the 4.4.4 OTA update. At least that worked!

I realize I am basically having a conversation with myself at this point, but just to wrap things up, in case anyone does come along and read any of this...
I have solved all my issues.
The Google Play Services issue must have been related to the Wi-Fi not connecting, and the Wi-Fi not connecting was due to my main network actually having an issue and the fact that I had never authorized the phone on the other networks. I guess this is what happens after being up almost 24 hours. At least I think everything is OK now.
Again, thanks to those that helped!

Andyw2100 said:
I realize I am basically having a conversation with myself at this point, but just to wrap things up, in case anyone does come along and read any of this...
I have solved all my issues.
The Google Play Services issue must have been related to the Wi-Fi not connecting, and the Wi-Fi not connecting was due to my main network actually having an issue and the fact that I had never authorized the phone on the other networks. I guess this is what happens after being up almost 24 hours. At least I think everything is OK now.
Again, thanks to those that helped!
Click to expand...
Click to collapse
Not sure why I stopped receiving notifications from your thread. But at least you got your phone in working order! lol

[Q] How to root this device without deleting any data?

Is it possible to root one plus one, without deleting any data and apps from it? I just want root access but don't want any custom rom.

yes, of course..
root doesn't delete any of your data

senaferdy79 said:
yes, of course..
root doesn't delete any of your data
Click to expand...
Click to collapse
Thanks for that. How can I do that?
#newtorooting

senaferdy79 said:
yes, of course..
root doesn't delete any of your data
Click to expand...
Click to collapse
That isn't technically true. In order to get root you must have a custom recovery installed. In order to install a custom recovery you must unlock the bootloader. Unlocking the bootloader wipes the device.
---------- Post added at 08:13 PM ---------- Previous post was at 08:10 PM ----------
sourabhkejriwal said:
Thanks for that. How can I do that?
#newtorooting
Click to expand...
Click to collapse
Sorry you got your hopes up, but the other poster isn't right. As per my reply to him you need to unlock your bootloader first, which is going to wipe your device. I'd suggest backing up any files that you have that are important to you. As for your apps and settings, you'll have to set them up again afterwards. Go to my guide thread here:
http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
You need to follow (in order) sections 1, 2, 3, and 4. This will give you root access on your stock ROM. You should also follow section 10, it's very important that you make a backup of your EFS partition.

timmaaa said:
That isn't technically true. In order to get root you must have a custom recovery installed. In order to install a custom recovery you must unlock the bootloader. Unlocking the bootloader wipes the device.[
Click to expand...
Click to collapse
So are you saying all the many how to's that tell you that you can skip installing recover are wrong? Apparently, I don't have enough posts yet to create a link but I've seen posts here on XDA that say other wise and the one I have in front of me at the moment is from ibtimes . com titled "how-root-oneplus-one-install-twrp-recovery-1450708"
Their "Step-7" reads
Step-7: If you want to root the phone without installing TWRP recovery, type the following command
fastboot boot twrp.img
Click to expand...
Click to collapse
I guess the real question being, why would you need a custom recovery?

pdhx said:
So are you saying all the many how to's that tell you that you can skip installing recover are wrong? Apparently, I don't have enough posts yet to create a link but I've seen posts here on XDA that say other wise and the one I have in front of me at the moment is from ibtimes . com titled "how-root-oneplus-one-install-twrp-recovery-1450708"
Their "Step-7" reads
I guess the real question being, why would you need a custom recovery?
Click to expand...
Click to collapse
You're looking at outdated information. They used to be correct, but now they are wrong. This is because you can no longer use the fastboot boot recovery.img command with a locked bootloader. In fact, that functionality was removed quite some time ago.
You need a custom recovery because that's how you flash SuperSU to get root. There's no way around it.
Transmitted via Bacon

The default recovery will only flash cm signed zip, which is another reason for needing a custom recovery. That method you mention at ibtimes meant that it would allow you to, for one boot cycle, do a "live boot" of twrp
Sent From Lollipopified Bacon Goodness!

But how is anything going to be written to the system partition if it is locked ?

timmaaa said:
You're looking at outdated information. They used to be correct, but now they are wrong. This is because you can no longer use the fastboot boot recovery.img command with a locked bootloader. In fact, that functionality was removed quite some time ago.
You need a custom recovery because that's how you flash SuperSU to get root. There's no way around it.
Click to expand...
Click to collapse
Ugh, was afraid of that, you might want to add a comment to that effect to your guide....
Would have been nice to just add a setting to the default recovery to allow you to toggle whether you need a signed zip or not. Sucks that I could root my SGS III (which is far less hacker friendly than the One) without wiping it but I can't do that for the One, all i want is root for the moment. However, after playing around some more I'm getting stick before I even get that far; I can get ADB to find the device but when I adb reboot bootloader I cannot get fastboot to find the device. I've tried multiple drivers, different USB ports. When my One goes into fastboot the screen seems awfully dim, almost like it hasn't completely initialized, is that normal? And if so, any suggestions on why I can get adb to work but not fastboot?

pdhx said:
Ugh, was afraid of that, you might want to add a comment to that effect to your guide....
Would have been nice to just add a setting to the default recovery to allow you to toggle whether you need a signed zip or not. Sucks that I could root my SGS III (which is far less hacker friendly than the One) without wiping it but I can't do that for the One, all i want is root for the moment. However, after playing around some more I'm getting stick before I even get that far; I can get ADB to find the device but when I adb reboot bootloader I cannot get fastboot to find the device. I've tried multiple drivers, different USB ports. When my One goes into fastboot the screen seems awfully dim, almost like it hasn't completely initialized, is that normal? And if so, any suggestions on why I can get adb to work but not fastboot?
Click to expand...
Click to collapse
The one's bootloader is not like a nexus one where you can at least reboot recovery etc, once it boots thats it
what do get when you type fastboot devices ?

bombadier said:
The one's bootloader is not like a nexus one where you can at least reboot recovery etc, once it boots thats it
Click to expand...
Click to collapse
Which seems to be somewhat limiting for such an otherwise developer friendly device?
bombadier said:
what do get when you type fastboot devices ?
Click to expand...
Click to collapse
Nada, nothing, nil. however, "adb devices" works fine... WTF?

pdhx said:
Which seems to be somewhat limiting for such an otherwise developer friendly device?
Nada, nothing, nil. however, "adb devices" works fine... WTF?
Click to expand...
Click to collapse
Point one was just to say there is not anything really you can do in the bootloader, being able to reboot to recovery etc is actually a handy feature
Try a different fastboot.exe ? if you say that adb works perfectly then there has to be something wrong with your fastboot binary
I have attached my one,download and change the name back to .exe and see what happens
Going to need more info in order to help

bombadier said:
Point one was just to say there is not anything really you can do in the bootloader, being able to reboot to recovery etc is actually a handy feature
Try a different fastboot.exe ? if you say that adb works perfectly then there has to be something wrong with your fastboot binary
I have attached my one,download and change the name back to .exe and see what happens
Going to need more info in order to help
Click to expand...
Click to collapse
Fair point about bootloader, what I don't get is why they forced you to have to do the unlock to root? All I started out wanting to do was install Titanium and run a Nandroid or two. Guess if I'm going to have to wipe I guess I may end up installing a Lollipop ROM. However, I still can't get there. The fast boot you supplied gives the same problem. I was running the latest fastboot from the Android SDK and your's appears to be the same (though I haven't done a binary compare). As far as I can tell that leaves the device drivers, the laptop, or the phone itself. I'm running Win 7 SP 1 64 bit and I've tried various drivers including the Samsung the Google generic and they make no difference. Not sure how they would since adb works but I've seen some suggestions that drivers can be finicky in this regard.
What else can I tell you that might help?
Seems since I can get into the recovery that comes with the phone I could maybe get a works around somehow?

pdhx said:
Fair point about bootloader, what I don't get is why they forced you to have to do the unlock to root? All I started out wanting to do was install Titanium and run a Nandroid or two. Guess if I'm going to have to wipe I guess I may end up installing a Lollipop ROM. However, I still can't get there. The fast boot you supplied gives the same problem. I was running the latest fastboot from the Android SDK and your's appears to be the same (though I haven't done a binary compare). As far as I can tell that leaves the device drivers, the laptop, or the phone itself. I'm running Win 7 SP 1 64 bit and I've tried various drivers including the Samsung the Google generic and they make no difference. Not sure how they would since adb works but I've seen some suggestions that drivers can be finicky in this regard.
What else can I tell you that might help?
Seems since I can get into the recovery that comes with the phone I could maybe get a works around somehow?
Click to expand...
Click to collapse
They're "forcing" you to unlock the bootloader in order to root the device because that's the universally accepted standard (unlock bootloader, install custom recovery, flash root). Some devices have super secure bootloaders and that's why you end up needing to use hacks to get those devices rooted, but that isn't the normal way to go about it. Anyway, there's no advantage to leaving the bootloader at all. There's also no disadvantage to unlocking the bootloader at all. You might say that the fact that the device is wiped during the unlocking process is a disadvantage, but that fact is very well documented both here, on the OnePlus forums, and pretty much any other reputable tech site that mentions unlocking the bootloader on this phone. The point to that last sentence? It pays to research a device thoroughly before buying it, or before using it, the wiping of the device is no issue at all if you do it when you receive the phone (prior to using it), like many people have. But in your situation you're just going to have to backup any important media from the phone prior to unlocking.
Anyway, on to your fastboot issue. Exactly which drivers do you have installed on your PC? Do you have any other phone drivers or software installed on the PC? And do you have access to another PC in case the one you're using is the source of the issue?

Got it, 27th try (give or take) is the charm.... Had to use USBdeview and uninstall the Google and the Qualcomm drivers. Reinstalled the Google drivers (after a reboot) and got it to work. Guess I could have figured that out from dev manager by watching what drivers got activated while fastboot was active but nothing ever jumped out at me as an obvious culprit.
Interesting to note that TWRP now automatically prompts you to install SuperSU if you reboot after installing it. Maybe it found the zip but either way, nice touch!
Now to go and decide what ROM to install....
Thanks for your help!

I would suggest temasek unofficial cm12 ROM. Been using it pretty much as a daily driver since version 1.something of the ROM and no problems. At this point it's been almost a month of not having to boot into my cm11s ROM lol. I use it with AK kernel, seems like a good match cuz both devs are working together looks like. Flash AK ukm special edition after flashing his kernel and install synapse from play store if you want to play around with settings of the kernel
Sent From Lollipopified Bacon Goodness!

zenix23456 said:
I have been using AnyRooter for months and it is quite good to root OnePlus phones.
Click to expand...
Click to collapse
Except the Oneplus One.

Relock Bootloader and return stock

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.

Pixel bricked after trying to install the newest Android Q Beta

Hey everyone,
I have the following issue with my recently purchased Google Pixel smartphone. The other day I was trying to update to the Android Q Beta, but in the middle of the process the phone turned off.
All I have now is a phone with a locked bootloader. I cannot neither unlock the bootloader nor sideload any OTA (when I try doing so I get a "no devices/emulators found" message). I tried unlock the bootloader with the Unified Anroid Toolkit, but no go because of the same message.
Any thoughts how to revive it?

To get more, better answers. Full battery?, what was working system, unlocked?, update Q well exactly how, ota? Verify cables, different pc, verify drivers? When described as brick= what, how, display?. No matter what you will need bootloader to get working. Then factory images flash.

kkjb said:
To get more, better answers. Full battery?, what was working system, unlocked?, update Q well exactly how, ota? Verify cables, different pc, verify drivers? When described as brick= what, how, display?. No matter what you will need bootloader to get working. Then factory images flash.
Click to expand...
Click to collapse
It bricked while installing the beta and simultaneously charging approximately at 60% battery. Prior to trying to install the latest beta 3 I had the beta 2. Updated the system officially via Settings. Unsure if it was unlocked and I'd just bought the Pixel and randomly decided to update it.
The usb-c cable is fine and is working with other devices. It's also the same with other PCs.
All I have is a bootloader with some options - Start/ Restart Bootloader/Recovery mode (it won't load)/Barcodes.

So when using adb "fastboot devices" command do you get your device number returned? If so, was the data important to keep not wiped? Because a factory images flash is next. Or can look search on manually flashing bootloader or recovery or twrp recovery too. Data most likely gone with Q beta 2 but you may get it back. I would factory flash since you have fastboot available... Best so all of memory is correctly wiped, flashed.

kkjb said:
So when using adb "fastboot devices" command do you get your device number returned? If so, was the data important to keep not wiped? Because a factory images flash is next. Or can look search on manually flashing bootloader or recovery or twrp recovery too. Data most likely gone with Q beta 2 but you may get it back. I would factory flash since you have fastboot available... Best so all of memory is correctly wiped, flashed.
Click to expand...
Click to collapse
Yes, I get a device number with this command. I usually back up all the necessary data, so I don't really need what's on the phone and I can wipe it.
How can I do a factory image flash?

Best case then is to flash factory image, download either Q beta 3 or May stock image. Completely wipes and starts from scratch. Look at the many instructions, if need more guidance under flashing factory images. Q beta 3 is good, but if you flash Q through this process can't OTA to next version. So if that's a issue do May image then go back to ota through as before.

kkjb said:
Best case then is to flash factory image, download either Q beta 3 or May stock image. Completely wipes and starts from scratch. Look at the many instructions, if need more guidance under flashing factory images. Q beta 3 is good, but if you flash Q through this process can't OTA to next version. So if that's a issue do May image then go back to ota through as before.
Click to expand...
Click to collapse
But as far as I understand, I can't flash a factory image with a locked bootloader, can I? Also I don't have OEM unlocked

Correct. When you got the device number back from fastboot I guessed it was authorized. Which means OEM unlock. So I am at a loss at how much more to "help". Is your pixel unlockable in the first place? Verizon or carrier locked?

kkjb said:
Correct. When you got the device number back from fastboot I guessed it was authorized. Which means OEM unlock. So I am at a loss at how much more to "help". Is your pixel unlockable in the first place? Verizon or carrier locked?
Click to expand...
Click to collapse
Well, I have no idea if it's unlockable. I'm from Russia, so it's not Verizon or any other.

Pixels have unlockable or not bootloaders. Carrier sim lock (Verizon us carrier) have a exploit to unlock. In your case, if I have it right- accepted ota
Update to Q beta. As first post. So when failed, and would not boot to G screen. Power off then on if you hold down power + volume get bootloader. Now options are limited to restart bootloader, off, start, recovery. Tried and nothing, then went to recovery....got android icon laying down with red warning. So when you have that screen a different set of button pushes will give more options. So search how to factory erase through recovery. Hopefully will wipe bad q and return to before system...the one that was running correctly before last accept ota q.

kkjb said:
Pixels have unlockable or not bootloaders. Carrier sim lock (Verizon us carrier) have a exploit to unlock. In your case, if I have it right- accepted ota
Update to Q beta. As first post. So when failed, and would not boot to G screen. Power off then on if you hold down power + volume get bootloader. Now options are limited to restart bootloader, off, start, recovery. Tried and nothing, then went to recovery....got android icon laying down with red warning. So when you have that screen a different set of button pushes will give more options. So search how to factory erase through recovery. Hopefully will wipe bad q and return to before system...the one that was running correctly before last accept ota q.
Click to expand...
Click to collapse
Recovery mode is not working for me either. Any chance to factory erase it any other way?

https://www.androidexplained.com/pixel-factory-reset/ explains hard factory reset with bootloader. If still can't reset through that method, then I believe no options. I would search pixel threads with "hard brick" or "soft brick" and see if any other way.

im in the same boat. bootloader locked, can not access recovery. OEM-Unlock from system unchecked. fastboot commands needs unlocked bootloader. no idea what to do.

kkjb said:
https://www.androidexplained.com/pixel-factory-reset/ explains hard factory reset with bootloader. If still can't reset through that method, then I believe no options. I would search pixel threads with "hard brick" or "soft brick" and see if any other way.
Click to expand...
Click to collapse
Unfortunately, it explains the reset only in case a pixel can be turned on or factory mode is available.

wahur1 said:
im in the same boat. bootloader locked, can not access recovery. OEM-Unlock from system unchecked. fastboot commands needs unlocked bootloader. no idea what to do.
Click to expand...
Click to collapse
Just checked your thread and all I have to say I'm in a completely similar situation.

Might be a longshot but I remember a few people saying about using the fastboot continue command to get a soft bricked pixel booted. Not sure on their mileage using it but worth a punt.

junglism93 said:
Might be a longshot but I remember a few people saying about using the fastboot continue command to get a soft bricked pixel booted. Not sure on their mileage using it but worth a punt.
Click to expand...
Click to collapse
Yeah, I tried this one, but still no go. Thanks.

mighty_ok said:
Just checked your thread and all I have to say I'm in a completely similar situation.
Click to expand...
Click to collapse
I guess its a paperweight now.