Related
I had a new phone on 2.3.4. The first thing I tried to do was to unlock it by RSD flashing the unlock sbf from the main pudding thread (http://forum.xda-developers.com/showthread.php?t=1136261).
The initial process seemed to go okay, but I think when the phone was supposed to reboot, it ended up giving me a boot failure message (0x1000, if I remember correctly).
So, I tried the "fastboot oem unlock" command anyway, and it worked.
I tried to RSD flash the full 2.3.4 sbf from brandon15811's thread, but RSD gave an error, something about not being able to find the handle or something.
So, the next thing I did was to see if I could flash RomRacer's CWM via fastboot, and that seemed to work, too.
After that, if I tried to reboot, I would get the motorola startup screen and the word "unlocked", but it just seems to stay there.
I'm about to see if I can use the recovery to flash the full 2.3.4 sbf from here (http://forum.xda-developers.com/showthread.php?t=1138204).
Is that the right way to try to fix this, or is there something else I should try?
Haphim said:
I had a new phone on 2.3.4. The first thing I tried to do was to unlock it by RSD flashing the unlock sbf from the main pudding thread (http://forum.xda-developers.com/showthread.php?t=1136261).
The initial process seemed to go okay, but I think when the phone was supposed to reboot, it ended up giving me a boot failure message (0x1000, if I remember correctly).
So, I tried the "fastboot oem unlock" command anyway, and it worked.
I tried to RSD flash the full 2.3.4 sbf from brandon15811's thread, but RSD gave an error, something about not being able to find the handle or something.
So, the next thing I did was to see if I could flash RomRacer's CWM via fastboot, and that seemed to work, too.
After that, if I tried to reboot, I would get the motorola startup screen and the word "unlocked", but it just seems to stay there.
I'm about to see if I can use the recovery to flash the full 2.3.4 sbf from here (http://forum.xda-developers.com/showthread.php?t=1138204).
Is that the right way to try to fix this, or is there something else I should try?
Click to expand...
Click to collapse
If you have cwm just use samcripp's fruitcakes and see if that works.
Sent from my MB860 using XDA Premium App
msd24200 said:
If you have cwm just use samcripp's fruitcakes and see if that works.
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
I haven't confirmed it works yet, but if it does, why those builds instead of brandon15811's?
Haphim said:
I haven't confirmed it works yet, but if it does, why those builds instead of brandon15811's?
Click to expand...
Click to collapse
Sbf flashing is dangerous and not recommended
Sent from my MB860 using XDA Premium App
Unlocking an atrix already on 2.3.4 will give you a soft brick, its been confirmed many times. No way around it. Find the fruit cakes thread as msd24200 stated. Any recovery will work. If you do the full 2.3.4 sbf you can't rds back to an older build our even if you try the 2.3.4, that would give you a hard brick. If your unlocked just go for one of the great roms available.
Sent from my MB860 using XDA App
Dirtburgler said:
Unlocking an atrix already on 2.3.4 will give you a soft brick, its been confirmed many times. No way around it. Find the fruit cakes thread as msd24200 stated. Any recovery will work. If you do the full 2.3.4 sbf you can't rds back to an older build our even if you try the 2.3.4, that would give you a hard brick. If your unlocked just go for one of the great roms available.
Click to expand...
Click to collapse
I did a lot of reading before doing this, and somehow, I never came across that particular fact. Ai! Well, thank you for pointing that out!
So, here's a question then... I have another phone that has 1.83 on it. What's the best way to upgrade that to 2.3.4, unlocked and rooted? Should I follow the same path I did here, do the OTA update, unlock and brick via the unlock sbf, flash a recovery, then apply a fruitcake?
Or is there a better way? I've heard that the 2.3.4 update resizes the partitions, and that seems like a good thing, so I'm not sure I want a path that avoids that.
What do you think?
Haphim said:
I did a lot of reading before doing this, and somehow, I never came across that particular fact. Ai! Well, thank you for pointing that out!
So, here's a question then... I have another phone that has 1.83 on it. What's the best way to upgrade that to 2.3.4, unlocked and rooted? Should I follow the same path I did here, do the OTA update, unlock and brick via the unlock sbf, flash a recovery, then apply a fruitcake?
Or is there a better way? I've heard that the 2.3.4 update resizes the partitions, and that seems like a good thing, so I'm not sure I want a path that avoids that.
What do you think?
Click to expand...
Click to collapse
why bother to update if you're going to downgrade it again?
the unlocker SBF if 1.8.3, and the phone is on 1.8.3, so flash that. then install 2.3.4 via CWM with a fruitcake. done.
dLo GSR said:
why bother to update if you're going to downgrade it again?
the unlocker SBF if 1.8.3, and the phone is on 1.8.3, so flash that. then install 2.3.4 via CWM with a fruitcake. done.
Click to expand...
Click to collapse
Unce I've unlocked the phone on 1.8.3, would it be better to do the OTA update for 2.3.4, and then root? Is this even possible?
One important question, if I apply the CWM fruitcake over 1.83. will it resize the partitions the way the OTA update would?
Haphim said:
Unce I've unlocked the phone on 1.8.3, would it be better to do the OTA update for 2.3.4, and then root? Is this even possible?
One important question, if I apply the CWM fruitcake over 1.83. will it resize the partitions the way the OTA update would?
Click to expand...
Click to collapse
I don't believe so, someone correct me if I'm wrong, but in all honesty there is no reason to use fruitcakes if you don't plan on going back to an older build. Even if you mess something up flashing roms you can go into recovery and restore a backup and your good to go. The only way I've seen a hardbrick is from going back with rsd.
I would unlock then ota to 2.3.4 then install romracers cwm and then your free to flash pre rooted stock roms or cherry (3.14) or alien rom.
Sent from my MB860 using XDA App
Nevermind 10char
I could see flashing back to an older build beneficial to a developer but not your everyday user and rom flasher. Both methods will get you to the same place, fruitcake or ota. I know there are benefita doing the ota like partition size and some other tweaks but I'm not 100% what those benefits are.
I jumped in early and got the leaked ota before we knew of the hard brick issue and like I said I'm still rocking the same atrix I bought back in march.
Sent from my MB860 using XDA App
Dirtburgler said:
I don't believe so, someone correct me if I'm wrong, but in all honesty there is no reason to use fruitcakes if you don't plan on going back to an older build. Even if you mess something up flashing roms you can go into recovery and restore a backup and your good to go. The only way I've seen a hardbrick is from going back with rsd.
I would unlock then ota to 2.3.4 then install romracers cwm and then your free to flash pre rooted stock roms or cherry (3.14) or alien rom.
Click to expand...
Click to collapse
Thanks! If that's an okay route to take, then that's what I'll do.
Hi, just bought myself a new Motorola Atrix phone and i'd like to know what are my backup options?
Tried stock recovery but it shows only wipe+reboot options. There are no backup/restore features i'd expect from recovery system.
If i flash CWM, how can i uninstall it and get back to stock one if i happen to have return it to service shop someday (god forbid)?
Thanks
purpler said:
Hi, just bought myself a new Motorola Atrix phone and i'd like to know what are my backup options?
Tried stock recovery but it shows only wipe+reboot options. There are no backup/restore features i'd expect from recovery system.
If i flash CWM, how can i uninstall it and get back to stock one if i happen to have return it to service shop someday (god forbid)?
Thanks
Click to expand...
Click to collapse
please read the noob thread at the top of the forum, it will explain everything you need to know about unlocking your bootloader, installing a custom recovery, and then flashing new ROMs.
im very familiar with unlocking bootloader, rooting, flashing recovery and such. That topic doesn't say anything about going back to stock recovery if i remember correctly. Correct me if im wrong.
purpler said:
im very familiar with unlocking bootloader, rooting, flashing recovery and such. That topic doesn't say anything about going back to stock recovery if i remember correctly. Correct me if im wrong.
Click to expand...
Click to collapse
if you've already done all your research, then you would know that you can reflash a stock 2.3.4 sbf file with RSDlite to turn your phone back into completely stock.
that is, if you've already done all your research.. i mean, it's not like you can google these questions or anything
heh, so flashing SBF will erase CWM recovery right?
purpler said:
heh, so flashing SBF will erase CWM recovery right?
Click to expand...
Click to collapse
There is no stock recovery.... CWM does not come with your phone, you installed it. And who cares if you have a recovery on the phone and have to take it back?? You think the jack holes at AT&T even know what recovery is, let alone how to enter recovery mode... they all have iPhones.
Just flash a fruitcake if you have to take it back, and be done with it.
OBTW, since you unlocked your bootloader, you're unlocked forever... how you going to hide that?
Sent from my MB860 using xda premium
purpler said:
heh, so flashing SBF will erase CWM recovery right?
Click to expand...
Click to collapse
it will turn your phone completely stock again. it will even 'relock' your bootloader for you. just be careful, and only use it as a last resort since RSDlite always has a chance to brick your device permanently.
Alcapone263 said:
it will turn your phone completely stock again. it will even 'relock' your bootloader for you. just be careful, and only use it as a last resort since RSDlite always has a chance to brick your device permanently.
Click to expand...
Click to collapse
Can not re-lock bootloader... only can make the Unlocked word dissappear from boot screen.
Sent from my MB860 using xda premium
It doesnt show "Unlocked" message at least so im pretty much safe. Where i bought it they barelly knew specs of my phone god forbid to find out if its unlocked.
Lemme rephrase my question: If i flash CWM, can i erase it with flashing stock SBF?
purpler said:
It doesnt show "Unlocked" message at least so im pretty much safe. Where i bought it they barelly knew specs of my phone god forbid to find out if its unlocked.
Lemme rephrase my question: If i flash CWM, can i erase it with flashing stock SBF?
Click to expand...
Click to collapse
Yes... maybe... I don't know...
If they didn't know anything about your phone, why are you even worried.
You're safe??? safe from what? The unlocked bootloader police??
Sent from my MB860 using xda premium
Swiftks said:
Can not re-lock bootloader... only can make the Unlocked word dissappear from boot screen.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
which is why relock was surrounded by apostrophes. although, technically if you reflash the stock .sbf it takes away the pudding files in the bootloader, which is what allows us to flash custom recovery and stuff. have you ever reflashed a stock 2.3.4 sbf and then tried to install CWM through fastboot? it just doesn't work. the fuse in your device may be blown, but without those pudding files injected into the bootloader, you might as well have a locked device.
@Swiftks
you totally trolled my topic dude. and you aren't helping at all :\
purpler said:
you totally trolled my topic dude. and you aren't helping at all :\
Click to expand...
Click to collapse
your questions aren't making any sense. you can't install CWM without unlocking the bootl.oader, so if there's no unlocked text when you start the phone up, you're not gonna be able to do anything with CWM.
and it's already been established that if you flash a .sbf file, it will give you a stock recovery again.
Alcapone263 said:
which is why relock was surrounded by apostrophes. although, technically if you reflash the stock .sbf it takes away the pudding files in the bootloader, which is what allows us to flash custom recovery and stuff. have you ever reflashed a stock 2.3.4 sbf and then tried to install CWM through fastboot? it just doesn't work. the fuse in your device may be blown, but without those pudding files injected into the bootloader, you might as well have a locked device.
Click to expand...
Click to collapse
Ill agree with this.... so we agree, it's netural... an unlocked device that you can't do any of the cool unlocked features with.
Sent from my MB860 using xda premium
purpler said:
@Swiftks
you totally trolled my topic dude. and you aren't helping at all :\
Click to expand...
Click to collapse
Dude... are you done crying. Man up, grab your sack and stop worrying about what may happen if you have to return your phone.
Why do you want to install CWM Recovery... I'm assuming to flash a ROM... well guess what genius, you have to unlock your bootloader first... which means if these super scientists who work only at your local phone store, want to know if you've tampered with your phone, they're gonna know.
Sent from my MB860 using xda premium
i just wanted to know if flashing SBF erases already installed CWM. If i have CWM, its quite obvious bootloader's unlocked, at least to me it would.
My question was inspired by situation where i might need to return phone under warranty to service shop and hide that it has been unlocked and screwed with custom ROM's as much as i can.
There are some strange reboots/shutdowns which wasnt paid so phone is going back with hidden traces of being total geek.
Clearer?
purpler said:
i just wanted to know if flashing SBF erases already installed CWM. If i have CWM, its quite obvious bootloader's unlocked, at least to me it would.
My question was inspired by situation where i might need to return phone under warranty to service shop and hide that it has been unlocked and screwed with custom ROM's as much as i can.
There are some strange reboots/shutdowns which wasnt paid so phone is going back with hidden traces of being total geek.
Clearer?
Click to expand...
Click to collapse
Let me more precise with you.... Since you have unlocked your bootloader, you have burnt a fuse that can not replaced, short of cracking open the phone, finding the fuse, and fixing it (if that's even possible). So, if they are paying that close of antention to notice that you have CWM Recovery installed, they most likely would also notice that the bootloader fuse is gone, therefore who have tampered with your phone.... whether you flash a sbf file it not.
Sent from my MB860 using xda premium
</epic misunderstanding>
Wow. This thread is epic. Btw, chuck Norris can relock his bootloader.
Sent from my MB860 using Tapatalk
Phalanx7621 said:
Wow. This thread is epic. Btw, chuck Norris can relock his bootloader.
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
Damn right he can!
Let me get this straight if i were to make a factory cable then could I load right up to a recovery and flash a rom without doing anting on the computer right? If not please explain what it can do for an unbricked user.
Thank in advance!
no.
u need a computer. the cable just puts it in *fastboot* mode to be able to run fastboot commands from your computer.
Sent from my HTC Glacier using xda premium
Oh i was under the impreson that you could put a recovery in a folder the when you hooked up the factroy cable it would load the recovery oh by the way whats the eashest way to put the energy rom on my kindle and I dont whant to root unless neccesary.
can I even use a factory cable without rooting and can I put the recovery on there without rooting?
So you are gonna flash a rom but you don't want to root? Lol
Sent from my Kindle Fire using XDA
YESSS! please help.
U can use a factory cable, to replace your recovery and remain on stock OS unrooted if you choose. U can change the bootloader or not as well(without it u need the factory cable to get into recovery). U can make backups, whatever.
As soon as u flash a different rom, u will have root. It wont hurt you, but it'll be there lol
Sent from my HTC Glacier using XDA
Basicly I just whant to got rid of the stock and flash twrp so I can flash a Rom and what do you mean Id have to root aferter I pot a Rom on it. Spell fails!
Can someone do a video on the kfs factory cable that would be great
noahawesome said:
Basicly I just whant to got rid of the stock and flash twrp so I can flash a Rom and what do you mean Id have to root aferter I pot a Rom on it. Spell fails!
Click to expand...
Click to collapse
ALL 100% of custom ROM's are pre-rooted, there is NO reason to not be rooted. You have to root in order to enjoy the better apps available. I've been here 5 years now and never heard of someone who wants a custom ROM installed without Root. It makes no sense at all...
Sent from my SGH-T959 using XDA
No no no I mean I whatnt to get to a rooted Rom on my stock 6.3 kf! Any help please
noahawesome said:
No no no I mean I whatnt to get to a rooted Rom on my stock 6.3 kf! Any help please
Click to expand...
Click to collapse
There are countless threads on how to do this. Just search, the info is there.
If you want to "remove" root for security reasons or for whatever reason, uninstall superuser.
Sent from my Amazon Kindle Fire using Tapatalk 2
SkOrPn said:
ALL 100% of custom ROM's are pre-rooted, there is NO reason to not be rooted. You have to root in order to enjoy the better apps available. I've been here 5 years now and never heard of someone who wants a custom ROM installed without Root. It makes no sense at all...
Sent from my SGH-T959 using XDA
Click to expand...
Click to collapse
miui is a custom rom without root(until its enabled manually).
but yup, without it, I don't know what I would use my device for. I need root
Sent from my HTC Glacier using xda premium
Thank you everyone who helped! I did what Imntone told me to and it sort of worked! after i got into fastboot, your last two commands didnt work... i used kfu to try to install twrp after getting into fastboot & it worked! THX THX THX for all ur help!!!!!!!!!!!!!!!!!!!!!!! :angel::victory::laugh::silly::good::highfive:
I think there is some confusion here as to what "rooting" means.
The term "rooting" is generally used in the community for the process of flashing a custom bootloader and recovery in order to gain root access to the device. This isn't really accurate as flashing a custom bootloader and recovery are 2 completely separate processes that just happen to generally be prerequisites to gaining root on many devices. It is completely possible on some devices to root the device without a custom recovery or custom bootloader and it is completely possible on most devices to flash a custom bootloader and recovery without gaining root access.
What becomes confusing to some is the widely known fact that rooting your device voids the warranty. In reality rooting is generally easy to reverse, removing a custom recovery and bootloader is not usually easy to do. Flashing a custom recovery and bootloader is really the reason that your warranty is voided, neglecting to install the superuser.apk to gain root is doing nothing to preserve your warranty. For this reason there really is nothing to gain from flashing a custom recovery and bootloader to install a custom rom without root access over installing a rom with root access. With root access you gain the ability to use many more advanced apps which allow you to take full advantage of the device it also allows you to have the option to modify system files which are normally protected which can allow you to manually fix some problems which may arise.
I hope this helps clear things up for some.
Sent from my ICS Dinc2
[Solved] Need some help..
I want to get my ATT galaxy s4 back to stock. I searched for a lot online. Basically it needs Odin and a downloaded stock firmware.
My question is does it work even for my phone currently is CWRP recovery and custom rom flashed? Does the Odin flash the stock recovery to the phone?
Thank you so much!
LingBo said:
Need some help..
I want to get my ATT galaxy s4 back to stock. I searched for a lot online. Basically it needs Odin and a downloaded stock firmware.
My question is does it work even for my phone currently is CWRP recovery and custom rom flashed? Does the Odin flash the stock recovery to the phone?
Thank you so much!
Click to expand...
Click to collapse
CWRP recovery? is that new? You have the 2 recoveries mixed, hehe good one though. I like that name. Anywaz...use ODIN, get the stock image and flash.
TheAxman said:
CWRP recovery? is that new? You have the 2 recoveries mixed, hehe good one though. I like that name. Anywaz...use ODIN, get the stock image and flash.
Click to expand...
Click to collapse
TWRP..typo..:laugh:
So it can remove the TWRP and flash stock recovery automatically by ODIN, right?
LingBo said:
TWRP..typo..:laugh:
So it can remove the TWRP and flash stock recovery automatically by ODIN, right?
Click to expand...
Click to collapse
heh we cool, um, it does not remove the recovery, but a hint here, odin back to stock, go into recovery after and factory reset. If you are wanting to remove everything including recovery, there is a thread or 2 with info on that.
Good luck.
TheAxman said:
heh we cool, um, it does not remove the recovery, but a hint here, odin back to stock, go into recovery after and factory reset. If you are wanting to remove everything including recovery, there is a thread or 2 with info on that.
Good luck.
Click to expand...
Click to collapse
Thank you very much! Still have a question..After I go to recovery and factory reset, can I get OTA update?
since the OTA update would check for system integrity like recovery.
LingBo said:
Thank you very much! Still have a question..After I go to recovery and factory reset, can I get OTA update?
since the OTA update would check for system integrity like recovery.
Click to expand...
Click to collapse
I have heard different stories on that, the one that I think is if you are rooted and recovery installed, your status would show custom, so no updates.
Anyone have any input on this?
TheAxman said:
I have heard different stories on that, the one that I think is if you are rooted and recovery installed, your status would show custom, so no updates.
Anyone have any input on this?
Click to expand...
Click to collapse
Asked someone if OTA is available after, he just said "should be" which is risky for me...
The goal is to get everything back to stock and question is can "Odin+stock firmware" achieve... I am so confused..
LingBo said:
Asked someone if OTA is available after, he just said "should be" which is risky for me...
The goal is to get everything back to stock and question is can "Odin+stock firmware" achieve... I am so confused..
Click to expand...
Click to collapse
Yes, ODIN BACK TO STOCK.
TheAxman said:
Yes, ODIN BACK TO STOCK.
Click to expand...
Click to collapse
Hello,Sir~ Thanks for advice!
Do you have any idea about the boot unlock image with word "custom"? I found something online saying that even if you flashed a stock firmware
by Odin and reset factory in recovery, it could be still there and probably related to some files be signed or not by samsung.. Any suggestion?
LingBo said:
Hello,Sir~ Thanks for advice!
Do you have any idea about the boot unlock image with word "custom"? I found something online saying that even if you flashed a stock firmware
by Odin and reset factory in recovery, it could be still there and probably related to some files be signed or not by samsung.. Any suggestion?
Click to expand...
Click to collapse
There is a way to get that to read normal, but you must first get back to stock. Start there, and we will get the other taken care of.
good luck.
LingBo said:
Hello,Sir~ Thanks for advice!
Do you have any idea about the boot unlock image with word "custom"? I found something online saying that even if you flashed a stock firmware
by Odin and reset factory in recovery, it could be still there and probably related to some files be signed or not by samsung.. Any suggestion?
Click to expand...
Click to collapse
You can find more about the process by reading this thread:
http://forum.xda-developers.com/showthread.php?t=2261573
If you want to be 100% stock like you were out of the box, you can do a factory reset/wipe in TWRP and then ODIN back to stock.
Factory reset will wipe all of your data - some of which is causing the custom icon at boot. You can wipe the cache and davlik cache as well to be sure.
Next, ODIN will remove root and custom recovery afterwards, leaving you completely stock.
My understand is that if you don't want to wipe all your apps and data, you can ODIN back to stock and then manually remove the files that are causing the custom icon, but I have not tried that.
jeffreii said:
You can find more about the process by reading this thread:
http://forum.xda-developers.com/showthread.php?t=2261573
If you want to be 100% stock like you were out of the box, you can do a factory reset/wipe in TWRP and then ODIN back to stock.
Factory reset will wipe all of your data - some of which is causing the custom icon at boot. You can wipe the cache and davlik cache as well to be sure.
Next, ODIN will remove root and custom recovery afterwards, leaving you completely stock.
My understand is that if you don't want to wipe all your apps and data, you can ODIN back to stock and then manually remove the files that are causing the custom icon, but I have not tried that.
Click to expand...
Click to collapse
I am not the one seeking this info.
It is for the OP. Good info though.
TheAxman said:
I am not the one seeking this info.
It is for the OP. Good info though.
Click to expand...
Click to collapse
My bad - clicked on the wrong reply button!
TheAxman said:
I am not the one seeking this info.
It is for the OP. Good info though.
Click to expand...
Click to collapse
Yeah! I got everything back to stock 4.2.2 UCUAMDL. The lock custom logo is gone. I checked for OTA update, but it said the software was up to date. Obviously it is not the latest. What can I do to get the latest update?
Thank you!
Man, I got everything back to stock and installed the latest OTA manually. Thank you so much!
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Problem solved ! Thank you!
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
LingBo said:
Problem solved ! Thank you!
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Glad to hear.
Edit your header to say problem solved, so others will see that if they need this info, there is a fix.
LingBo said:
Man, I got everything back to stock and installed the latest OTA manually. Thank you so much!
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Did you use Odin to do the OTA update manually? I was rooted and had custom recovery and used Kies to get back to "stock" but only to MDL. Phone checks for updates and it says im on the latest as well.. I want to update the phone to MF3 but I cant find it anywhere... Can you me out?
tiptoekirk said:
Did you use Odin to do the OTA update manually? I was rooted and had custom recovery and used Kies to get back to "stock" but only to MDL. Phone checks for updates and it says im on the latest as well.. I want to update the phone to MF3 but I cant find it anywhere... Can you me out?
Click to expand...
Click to collapse
I would use this one, if you are rooted...
http://forum.xda-developers.com/showthread.php?t=2364635
Follow the instructions there...
Thanks you
Good luck.
TheAxman said:
I would use this one, if you are rooted...
http://forum.xda-developers.com/showthread.php?t=2364635
Follow the instructions there...
Thanks you
Good luck.
Click to expand...
Click to collapse
I want it stock as stock gets if possible.. I don't want to deal with recovery's and such.. I have to warranty the phone once I come up with the $$ for the deductible because the screen is cracked and I don't want them saying my warranty its void...
Will getting to MF3 this way cause me to have the custom unlocked symbol on the startup screen again??
Hello, I have rooted and installed TWRP in my nexus 6p and now I have received the OTA update but I can't install it. How can I install it without losing my data?
Thanks
Sent from my Nexus 6P using XDA Free mobile app
airmark said:
Hello, I have rooted and installed TWRP in my nexus 6p and now I have received the OTA update but I can't install it. How can I install it without losing my data?
Thanks
Sent from my Nexus 6P using XDA Free mobile app
Click to expand...
Click to collapse
Unfortunately you cant :/
Download TiBu that is the closest you can get...
If you download a custom rom that keeps it up to date, they will probably include the update and you can just flash over it. but stock rom there isnt much u can do.
airmark said:
Hello, I have rooted and installed TWRP in my nexus 6p and now I have received the OTA update but I can't install it. How can I install it without losing my data?
Thanks
Sent from my Nexus 6P using XDA Free mobile app
Click to expand...
Click to collapse
Download the Google factory image for the 6p. Use fastboot to manually flash the system.img, boot.IMG, and recovery.IMG. take the ota then reroot.
Sent from my Nexus 6P using Tapatalk
airmark said:
Hello, I have rooted and installed TWRP in my nexus 6p and now I have received the OTA update but I can't install it. How can I install it without losing my data?
Thanks
Sent from my Nexus 6P using XDA Free mobile app
Click to expand...
Click to collapse
Go to guide, instructions there:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
raul4916 said:
Unfortunately you cant :/
Download TiBu that is the closest you can get...
If you download a custom rom that keeps it up to date, they will probably include the update and you can just flash over it. but stock rom there isnt much u can do.
Click to expand...
Click to collapse
Yes you can.
I did that and after rebooting I got a message saying:
Encryption unsuccessful
and prompting me to do a factory reset!
please don't tell me i have to wipe data!? quick googling doesn't seem promising...
airmark said:
I did that and after rebooting I got a message saying:
Encryption unsuccessful
and prompting me to do a factory reset!
Click to expand...
Click to collapse
airmark said:
please don't tell me i have to wipe data!? quick googling doesn't seem promising...
Click to expand...
Click to collapse
What did you do?
airmark said:
please don't tell me i have to wipe data!? quick googling doesn't seem promising...
Click to expand...
Click to collapse
Trying to undo the last steps by flashing back the modified boot.img and TWRP.
Booting into TWRP and it asks for a password to decrypt storage!!!
Is wiping the only option??
I followed the guide religiously. What went wrong?
Heisenberg said:
What did you do?
Click to expand...
Click to collapse
I followed the guide (part 10. How To Take An OTA Update If You Have Root).
Then after rebooting (before installing the OTA that is) I got a message saying encryption unsuccessful and I needed to wipe my phone. I turned it off instead and tried to restore it as it was before. Screw the OTA, I just need my phone back. I flashed back boot and recovery, is system.img or vendor.img the culprit?
Any ideas? Do I need to wipe data?
airmark said:
Trying to undo the last steps by flashing back the modified boot.img and TWRP.
Booting into TWRP and it asks for a password to decrypt storage!!!
Is wiping the only option??
I followed the guide religiously. What went wrong?
Click to expand...
Click to collapse
airmark said:
I followed the guide (part 10. How To Take An OTA Update If You Have Root).
Then after rebooting (before installing the OTA that is) I got a message saying encryption unsuccessful and I needed to wipe my phone. I turned it off instead and tried to restore it as it was before. Screw the OTA, I just need my phone back. I flashed back boot and recovery, is system.img or vendor.img the culprit?
Click to expand...
Click to collapse
I really don't know what went wrong here, other people have done this with no issues. In TWRP it should be able to decrypt as long as you enter the password/pin.
Heisenberg said:
I really don't know what went wrong here, other people have done this with no issues. In TWRP it should be able to decrypt as long as you enter the password/pin.
Click to expand...
Click to collapse
I had a screen lock pattern, I entered the numbers that correspond to it (from what I read somewhere else, like a num keypad), no joy.
But then again, shouldn't actual booting into the system work as well? Why give this error msg?
I'm going to format then...
unless your super comfortable with ADB and fastboot, flashing things through them is never a good idea, you will screw up allot of the time. its always easier for the average user to wait for a ota zip and flash that. Or never root and accept otas.
Im not saying never use adb, just dont use it when its super important to keep your data
TheAtheistOtaku said:
unless your super comfortable with ADB and fastboot, flashing things through them is never a good idea, you will screw up allot of the time. its always easier for the average user to wait for a ota zip and flash that. Or never root and accept otas.
Im not saying never use adb, just dont use it when its super important to keep your data
Click to expand...
Click to collapse
The only problem with that is even when an OTA zip is available you'd need to use fastboot to flash system etc to remove root anyway.
So I formatted, then set it up, then tried restoring my latest nandroid backup and now it doesn't recognise the pattern lock!
Heisenberg said:
The only problem with that is even when an OTA zip is available you'd need to use fastboot to flash system etc to remove root anyway.
Click to expand...
Click to collapse
i meant a TWRP zip. unless im misunderstanding something, you can just flash those over your current rooted stock and be on your way
---------- Post added at 07:50 PM ---------- Previous post was at 07:47 PM ----------
airmark said:
So I formatted, then set it up, then tried restoring my latest nandroid backup and now it doesn't recognise the pattern lock!
Click to expand...
Click to collapse
known problem, read this
Thanks for that, although at first after reading the first few posts I thought there was no solution, luckily I kept reading until here: http://forum.xda-developers.com/showpost.php?p=63797741&postcount=34
I did that and it worked! so at least I got back my working phone. Back to square one (almost, I lost all my local copies of photos, with only cloud backup for the last 2 weeks or so) with no OTA installed. I may try it again at some other point or wait for a more safe method.
airmark said:
Thanks for that, although at first after reading the first few posts I thought there was no solution, luckily I kept reading until here: http://forum.xda-developers.com/showpost.php?p=63797741&postcount=34
I did that and it worked! so at least I got back my working phone. Back to square one (almost, I lost all my local copies of photos, with only cloud backup for the last 2 weeks or so) with no OTA installed. I may try it again at some other point or wait for a more safe method.
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-6p/development/rom-nexus6p-stock-roms-t3234067
TheAtheistOtaku said:
http://forum.xda-developers.com/nexus-6p/development/rom-nexus6p-stock-roms-t3234067
Click to expand...
Click to collapse
Thanks, I've just overcome the trauma and gathered the courage needed to give it another go today
So, do I have this right? If I download and flash build MDA89D ROM will it upgrade in place over my currently installed build MDB08K without losing my data? (I asked in that thread as well)
Sent from my Nexus 6P using XDA Free mobile app