Related
Hi
I made a very stupid mistake
I used the tool to root my xoom wifi model
I used the tool in this thread
http://forum.xda-developers.com/showthread.php?t=1011196
I tried to post this issue in the thread but I did not have the permissions.
by mistake I used the root of the 3G model
I followed the steps and everything was ok
I tried the unroot and here is the deadly (hopefully not) mistake
the xoom stops and first screen and refuses to boot
Did I brick my device??
Is there a way to resolve this problem??
Thanks
Yes, you have bricked it. Fastboot won't work at this point, so your only option is probably to return it.
-Jim (who's on his 2nd xoom)
Sent from my Xoom using Tapatalk
nawialkair said:
Hi
I made a very stupid mistake
I used the tool to root my xoom wifi model
I used the tool in this thread
http://forum.xda-developers.com/showthread.php?t=1011196
I tried to post this issue in the thread but I did not have the permissions.
by mistake I used the root of the 3G model
I followed the steps and everything was ok
I tried the unroot and here is the deadly (hopefully not) mistake
the xoom stops and first screen and refuses to boot
Did I brick my device??
Is there a way to resolve this problem??
Thanks
Click to expand...
Click to collapse
what does the first screen say? failed boot image?
BeagleBoy said:
Yes, you have bricked it. Fastboot won't work at this point, so your only option is probably to return it.
-Jim (who's on his 2nd xoom)
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
That's the thing I did not want to hear but expected it.
============================================
znfrazier said:
what does the first screen say? failed boot image?
Click to expand...
Click to collapse
No
I am stuck at the motorola logo and the word dual core technology
When I press Volume up or down (fanrkly I could not get into that menu again) I get a list
it includes the following:
Fast Boot
If I choose it I get
Starting Fastboot protocol support
nawialkair said:
That's the thing I did not want to hear but expected it.
============================================
No
I am stuck at the motorola logo and the word dual core technology
When I press Volume up or down (fanrkly I could not get into that menu again) I get a list
it includes the following:
Fast Boot
If I choose it I get
Starting Fastboot protocol support
Click to expand...
Click to collapse
Can you see the xoom in /fastboot devices? See if you can access you xoom from the computer. I actually did the same thing and got mine in working order.
nawialkair said:
That's the thing I did not want to hear but expected it.
============================================
No
I am stuck at the motorola logo and the word dual core technology
When I press Volume up or down (fanrkly I could not get into that menu again) I get a list
it includes the following:
Fast Boot
If I choose it I get
Starting Fastboot protocol support
Click to expand...
Click to collapse
Try doing this real quick, the best that can happen is that you can turn this around. You may NOT in fact be bricked. I made the mistake of doing this also, but I figured it is just like when I was using the Danger SPL on the G1 and I had to at least find a way.
So, do this real quick if you know how.
1. Power on and press Vol - at the same time
2. Open a command prompt to your ADB file and type in fastboot oem unlock
3. If this lets you in (it may not) go through the regular procedure of pressing Vol -+-+
4. It will format and you should know if it is in fact bricked or not because it won't boot up.
5. ******
6. Profit???
Let us know how it goes.
znfrazier said:
Can you see the xoom in /fastboot devices? See if you can access you xoom from the computer. I actually did the same thing and got mine in working order.
Click to expand...
Click to collapse
Yes I can see it
Thank you
stevenege said:
Try doing this real quick, the best that can happen is that you can turn this around. You may NOT in fact be bricked. I made the mistake of doing this also, but I figured it is just like when I was using the Danger SPL on the G1 and I had to at least find a way.
So, do this real quick if you know how.
1. Power on and press Vol - at the same time
2. Open a command prompt to your ADB file and type in fastboot oem unlock
3. If this lets you in (it may not) go through the regular procedure of pressing Vol -+-+
4. It will format and you should know if it is in fact bricked or not because it won't boot up.
5. ******
6. Profit???
Let us know how it goes.
Click to expand...
Click to collapse
I did that
and it started the format
After the boot, it stopped at the same place
Motorola's Logo and Dual Core
What's next??
thanks
root using the instructions in this thread it should fix your problem
http://forum.xda-developers.com/showthread.php?t=1010568
nawialkair said:
Yes I can see it
Thank you
I did that
and it started the format
After the boot, it stopped at the same place
Motorola's Logo and Dual Core
What's next??
thanks
Click to expand...
Click to collapse
you should try flashing the boot.img used to root i believe its tiamat 1.1.6 and the system.img for wifi. i have the stock system.img if you need it. hopefully that would git ya to boot atleast. MAKE SURE THAT IT IS WIFI ONLY.
Go here and follow the second post I posted. This will help you do this without downloading the files because they are already there.
Give it a shot at least
stevenege said:
Go here and follow the second post I posted. This will help you do this without downloading the files because they are already there.
Give it a shot at least
Click to expand...
Click to collapse
did they fix the boot prob with the one click? i haven't tried it.
znfrazier said:
did they fix the boot prob with the one click? i haven't tried it.
Click to expand...
Click to collapse
Yes, it has all been fixed. There still seems to be an issue with SU rights until you download BusyBox and no clue why.
I have been testing the WiFi one constantly and have not had any major hickups.
stevenege said:
Yes, it has all been fixed. There still seems to be an issue with SU rights until you download BusyBox and no clue why.
I have been testing the WiFi one constantly and have not had any major hickups.
Click to expand...
Click to collapse
good good. ill have to check it out. i still need to try out the pimp my xoom. ill post over there haha. gotta stay on topic.
Thanks ALL
I flashed Tiamat 1.1.6 boot.img
the problem is that when using this command:
adb remount
I get
error: device not found
The xoom is defined in the device manager as
Android adb Interface
nawialkair said:
Thanks ALL
I flashed Tiamat 1.1.6 boot.img
the problem is that when using this command:
adb remount
I get
error: device not found
The xoom is defined in the device manager as
Android adb Interface
Click to expand...
Click to collapse
Sounds like you are probably bricked :-/
Can I get the stock boot image
I just want to try that last option
I flashed the stock img and system img
It works fine
Yaaaaa
Thanks very much
Thanks very much
nawialkair said:
I flashed the stock img and system img
It works fine
Yaaaaa
Thanks very much
Thanks very much
Click to expand...
Click to collapse
Told ya haha, save those files on your computer for next time. I keep them in close reach just incase something happens. if you have any other problems give me a holla. glad everything is working again.
I think I'm more screwed than OP because I was already unlocked and rooted. Then locked my wifi xoom with the 3g one click tool. Yes I know that was very stupid but I was wondering what are my options?
Take it back to Amazon?
Use the following method in this thread?
Wait for SBF?
Thank you your time and sorry if I hijacked this thread.
jarretf said:
I think I'm more screwed than OP because I was already unlocked and rooted. Then locked my wifi xoom with the 3g one click tool. Yes I know that was very stupid but I was wondering what are my options?
Take it back to Amazon?
Use the following method in this thread?
Wait for SBF?
Thank you your time and sorry if I hijacked this thread.
Click to expand...
Click to collapse
It relocked? Yikes... I don't trust those 1-click things. I need to know what's going on step by step. My first Xoom got bricked when I thought I had untainted OEM image files and relocked it. There's really no reason to relock a Wifi Xoom right now.
Anyway, if it relocked, you might have been in the same boat I was where the computer wouldn't recognize the Xoom in Fastboot mode or RSD mode. And I went and got it exchanged at that point.
Oh, if RSD Lite can't see your Xoom in RSD mode, you might be out of luck. SBF won't help if RSD Lite can't see your Xoom. BUT, if it does see it, it sounds like you can flash the 3G/4G SBF from Motorola/Verizon and to get sorta running, then use Fastboot to overwrite the boot and system partitions.
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 ).
Everything is screwed for me. I can't even RSD back to stock. I can access TWRP, but can't wipe System or Data. Fastboot is just there and won't actually push anything. I already have a Moto X now, and I was talking about this issue about a week ago on the Android Development subcat, but I thought I would give it one last go on here to see if I can at least make it a backup.
kungpowchicken said:
Everything is screwed for me. I can't even RSD back to stock. I can access TWRP, but can't wipe System or Data. Fastboot is just there and won't actually push anything. I already have a Moto X now, and I was talking about this issue about a week ago on the Android Development subcat, but I thought I would give it one last go on here to see if I can at least make it a backup.
Click to expand...
Click to collapse
Maybe if you could give some more detail about what exactly you can and can't get the phone to do, what screens can be accessed, and what you did that lead to this condition, we could offer some advice.
Also, no offence to the devs, but twrp is the devil lol. Most issues I have had in the past have led back to it in one way or another, so I never use it. (Just my opinion)
Tappin G2 Style
I can get to the Fastboot screen, I can access TWRP, and I can get the phone to bootloop at the boot animation screen.
I can't push anything through ADB or Fastboot, I cannot mount data or system in TWRP or otherwise. RSD comes back failed every time with every single stock build I use.
Literally two weeks ago, I was in bed, watching TV, with the phone charging. I unlock it to see if I had any notifications, and it kept saying that Nova launcher FC'd. So logically, I rebooted my phone and that's when it started boot looping.
I did nothing to the phone for a couple of hours, it was on the official CM 10.2 11/9 build. I had that ROM running fine for at least 24 hours before it went FUBAR.
kungpowchicken said:
Everything is screwed for me. I can't even RSD back to stock. I can access TWRP, but can't wipe System or Data. Fastboot is just there and won't actually push anything. I already have a Moto X now, and I was talking about this issue about a week ago on the Android Development subcat, but I thought I would give it one last go on here to see if I can at least make it a backup.
Click to expand...
Click to collapse
Is it this problem?: http://forum.xda-developers.com/showpost.php?p=47558893&postcount=47
If so use this solution: http://forum.xda-developers.com/showpost.php?p=47716278&postcount=57
scoobaspeaz said:
Is it this problem?: http://forum.xda-developers.com/showpost.php?p=47558893&postcount=47
If so use this solution: http://forum.xda-developers.com/showpost.php?p=47716278&postcount=57
Click to expand...
Click to collapse
Nope, my status us unlocked: 3. But when I get home, I'll try the mfastboot instead if fastboot.
kungpowchicken said:
I can get to the Fastboot screen, I can access TWRP, and I can get the phone to bootloop at the boot animation screen.
I can't push anything through ADB or Fastboot, I cannot mount data or system in TWRP or otherwise. RSD comes back failed every time with every single stock build I use.
Literally two weeks ago, I was in bed, watching TV, with the phone charging. I unlock it to see if I had any notifications, and it kept saying that Nova launcher FC'd. So logically, I rebooted my phone and that's when it started boot looping.
I did nothing to the phone for a couple of hours, it was on the official CM 10.2 11/9 build. I had that ROM running fine for at least 24 hours before it went FUBAR.
Click to expand...
Click to collapse
i made a modified utility to fix the partition error but need someone to test it please. it should do the process previously suggested automatically through the script.
http://www.mediafire.com/download/987490ykl14j4t8/DROID_RAZR_HD_Utility_1.3.gpt_fix.rar
thanks
bweN diorD said:
i made a modified utility to fix the partition error but need someone to test it please. it should do the process previously suggested automatically through the script.
http://www.mediafire.com/download/987490ykl14j4t8/DROID_RAZR_HD_Utility_1.3.gpt_fix.rar
thanks
Click to expand...
Click to collapse
Testing now.
UPDATE: Still no go.
kungpowchicken said:
Testing now.
UPDATE: Still no go.
Click to expand...
Click to collapse
Well that sux.
Your problem is different than what I made this for but I was hoping it would work for you.
What did it do, fail all the way through?
When I tested it on my phone it reported flashing the partitions ok. There was actually extra text displayed while it was doing it that I didn't put into the script, that's how I knew it was working.
Tappin G2 Style
Failed all the way.
kungpowchicken said:
Failed all the way.
Click to expand...
Click to collapse
im running out of suggestions
if you havent tried to put stock recovery back on yet, how about we try that and see what happens.
if you dont know how to do it through adb, just grab the 1.34 utility from the dev forum, it will push it through fastboot.
something is obviously wrong with twrp, maybe we can fix that first.
I tried flashing even the stock Recovery manually and through the 1.34 utility. Always comes up failed. :sad:
Did you try the manual steps that I posted in my links?
i hope that works, but im doubtful.
the utility essentially flashes exactly as you would manually.
he doesnt have a partition issue, im guessing something is wack with the permissions.
if twrp somehow screwed up the permissions to read only, i believe even the partition file cant overwrite it. i could be wrong.
So I think it has something to do with the Permissions of one or more of the partitions. I just noticed it keeps saying Permissions Denied when I try to fastboot or mfastboot.
kungpowchicken said:
So I think it has something to do with the Permissions of one or more of the partitions. I just noticed it keeps saying Permissions Denied when I try to fastboot or mfastboot.
Click to expand...
Click to collapse
Are you sure you have the snapdragon fastboot? Can't hurt to reinstall it.
Sent from my MB886 using Tapatalk
Also have you tried flashing it manually? (fastboot flash system system.img, etc.)
penser said:
Are you sure you have the snapdragon fastboot? Can't hurt to reinstall it.
Sent from my MB886 using Tapatalk
Also have you tried flashing it manually? (fastboot flash system system.img, etc.)
Click to expand...
Click to collapse
he defiantly has the right fastboot, its in the utility that has been downloaded thousands of times.
if its write protected some how, its not going to flash no matter how you try it.
what i was wondering is if recovery can fix permissions that deep, not sure he said he tried that.
What do you mean with recovery?
kungpowchicken said:
What do you mean with recovery?
Click to expand...
Click to collapse
go into twrp, advanced (i think thats the right section) and look for a line that says "fix permissions" and do it.
Keeps saying it can't mount anything.
kungpowchicken said:
Keeps saying it can't mount anything.
Click to expand...
Click to collapse
thats what i figured would happen
I'm new to Motorola in the smartphone world, but just upgraded to a Droid Maxx Developer Edition. The bootloader is unlocked and it has root, but with the stock ROM. Well since yesterday it has been VERY annoyingly insisting on installing an OTA device update every few hours. After postponing it and postponing it I accidentally selected install. Now it's constantly rebooting into recovery (I assume) to install the update, but TWRP loads instead of the stock recovery so nothing happens. Then when I reboot into Android (4.2 19.5.3), within 2 minutes it reboots again to attempt installing the update.
Now, I'm ready to get away from stock (played with it stock for about a month, ready to move on), so I downloaded CM for it. But it won't stay booted into Android long enough for me to copy the .zip over to the phone to flash in TWRP. Also, I've never done anything in adb or fastboot. However, I did install adb (Windows 7 64-bit) and have been playing with that. When my phone is in android, I can usually see it listed as "TA4310BUAV unauthorized" when I run adb devices. After googling, this is because I've not authorized my computer on my phone. However, even after selecting 'revoke all authorizations' or whatever in developer settings, I still get no notification to authorize. And then when I'm booted into TWRP I can't see the phone at all.
Basically, I'm stuck in a bootloop and just want to copy the CM zip file to the phone so I can flash it in TWRP, but I'm at a loss as to how to do this. Can anyone provide me with some advice on how to proceed? It would be greatly appreciated!!
carmike692000 said:
I'm new to Motorola in the smartphone world, but just upgraded to a Droid Maxx Developer Edition. The bootloader is unlocked and it has root, but with the stock ROM. Well since yesterday it has been VERY annoyingly insisting on installing an OTA device update every few hours. After postponing it and postponing it I accidentally selected install. Now it's constantly rebooting into recovery (I assume) to install the update, but TWRP loads instead of the stock recovery so nothing happens. Then when I reboot into Android (4.2 19.5.3), within 2 minutes it reboots again to attempt installing the update.
Now, I'm ready to get away from stock (played with it stock for about a month, ready to move on), so I downloaded CM for it. But it won't stay booted into Android long enough for me to copy the .zip over to the phone to flash in TWRP. Also, I've never done anything in adb or fastboot. However, I did install adb (Windows 7 64-bit) and have been playing with that. When my phone is in android, I can usually see it listed as "TA4310BUAV unauthorized" when I run adb devices. After googling, this is because I've not authorized my computer on my phone. However, even after selecting 'revoke all authorizations' or whatever in developer settings, I still get no notification to authorize. And then when I'm booted into TWRP I can't see the phone at all.
Basically, I'm stuck in a bootloop and just want to copy the CM zip file to the phone so I can flash it in TWRP, but I'm at a loss as to how to do this. Can anyone provide me with some advice on how to proceed? It would be greatly appreciated!!
Click to expand...
Click to collapse
In TWRP try wiping your cache. That should delete the OTA. Then when you boot back into the OS use titanium backup to freeze the app "MotorolaOTA." That should do it.
Sent From Droid Ultra
Caseyk621 said:
In TWRP try wiping your cache. That should delete the OTA. Then when you boot back into the OS use titanium backup to freeze the app "MotorolaOTA." That should do it.
Sent From Droid Ultra
Click to expand...
Click to collapse
Thank you so much! I will try this immediately. I just figured out how to get into fastbook, and my computer recognizes the phone in that mode. Is that a good method for pushing the CM.zip to the phone (just for future reference if the above doesn't work)?
carmike692000 said:
Thank you so much! I will try this immediately. I just figured out how to get into fastbook, and my computer recognizes the phone in that mode. Is that a good method for pushing the CM.zip to the phone (just for future reference if the above doesn't work)?
Click to expand...
Click to collapse
May be wrong but I don't think you can push files in that way via fastboot. If my first method didn't work let me know. There are a few other things to try.
Sent From Droid Ultra
Caseyk621 said:
May be wrong but I don't think you can push files in that way via fastboot. If my first method didn't work let me know. There are a few other things to try.
Sent From Droid Ultra
Click to expand...
Click to collapse
I erased the cache like you said (though I did it through fastboot since I already had it up and it's 'new and exciting' and all), and rebooted. Seems to have worked so far. I could go ahead and d/l TiB and freeze that service like you said, but since I'm going to flash CM anyways, I don't see as that's necessary at the moment. However, I can't get W7 to see the phone to be able to transfer the .zip to the phone, whether by Windows Explorer or adb, because I still don't have the option on the phone to authorize my laptop.
EDIT - I'm sure one problem with the computer not listing the phone as a device is it cannot find the device driver to install for it, and I've not been successful googling for it. So in the Windows Device Manager list, my XT1080 has a yellow exclamation mark by it. Also, just installed TiB and froze "Motorola OTA" since I had to wait five minutes to post this edit anyways.
carmike692000 said:
I erased the cache like you said (though I did it through fastboot since I already had it up and it's 'new and exciting' and all), and rebooted. Seems to have worked so far. I could go ahead and d/l TiB and freeze that service like you said, but since I'm going to flash CM anyways, I don't see as that's necessary at the moment. However, I can't get W7 to see the phone to be able to transfer the .zip to the phone, whether by Windows Explorer or adb, because I still don't have the option on the phone to authorize my laptop.
Click to expand...
Click to collapse
Ok i just like to disable the OTA app to avoid accidentally upgrading and bootlooping. Plus I'm assuming that you'll be making a back up of your stock system to go back to should you not care for CM. Do you have USB debugging enabled on your phone?
Sent From Droid Ultra
Caseyk621 said:
Ok i just like to disable the OTA app to avoid accidentally upgrading and bootlooping. Plus I'm assuming that you'll be making a back up of your stock system to go back to should you not care for CM. Do you have USB debugging enabled on your phone?
Sent From Droid Ultra
Click to expand...
Click to collapse
As per my edit above, I have now frozen "Motorola OTA". That is a great point regarding the backup.
Yes, I do have USB debugging enabled on my phone. Also, per my edit above, not having the proper driver installed for my phone may be the limiting factor here. Though having never used adb before, maybe it's a slew of other things, I'm not sure.
carmike692000 said:
As per my edit above, I have now frozen "Motorola OTA". That is a great point regarding the backup.
Yes, I do have USB debugging enabled on my phone. Also, per my edit above, not having the proper driver installed for my phone may be the limiting factor here. Though having never used adb before, maybe it's a slew of other things, I'm not sure.
Click to expand...
Click to collapse
Maybe here
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Sent From Droid Ultra
Caseyk621 said:
Maybe here
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Sent From Droid Ultra
Click to expand...
Click to collapse
Finally we're getting somewhere. I had installed that earlier, but never had any success with it. However, after just aimlessly disabling and reenabling things (USB debugging, PTP media sharing, revoking authorizations), and unplugging/replugging, it finally installed the driver. And now adb recognizes it, I was able to authorize my laptop, and I just copy and pasted the cm .zip to my phone.
It seems everything is going to work out just fine! I'm going to back up a few things with TiB and then flash CM.
Thank you so much for your input! I'd still be dead in the water if it weren't for your help!
carmike692000 said:
Finally we're getting somewhere. I had installed that earlier, but never had any success with it. However, after just aimlessly disabling and reenabling things (USB debugging, PTP media sharing, revoking authorizations), and unplugging/replugging, it finally installed the driver. And now adb recognizes it, I was able to authorize my laptop, and I just copy and pasted the cm .zip to my phone.
It seems everything is going to work out just fine! I'm going to back up a few things with TiB and then flash CM.
Thank you so much for your input! I'd still be dead in the water if it weren't for your help!
Click to expand...
Click to collapse
Glad I could help! Don't forget to make a backup in TWRP! You may find yourself wanting to go back to stock sooner than you think! I keep trying ROMs but always end up missing active notifications and touch less as well as some others!
Sent From Droid Ultra
I am wanting to take and install the latest Ota update. I'm rooted and unlocked (via Chinese method). My question is how do I actually install the downloaded update considering that I have twrp for a recovery?.... Thank you in advance
nubia11 said:
I am wanting to take and install the latest Ota update. I'm rooted and unlocked (via Chinese method). My question is how do I actually install the downloaded update considering that I have twrp for a recovery?.... Thank you in advance
Click to expand...
Click to collapse
Flash the stock recovery with fastboot. I forget if you need to also unroot or not. Also make sure you have any apps that were disabled or frozen enabled/defrosted
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.