Related
Please help, my nexus was unlocked rooted with trinity kernel. When i pushed update, my tablet restarted with clockwokmod and failed to update
to 4.2. i believed it was because of custom kernel so i then flashed to stock factory, and re locked using nexus toolkit.
When i go to setting for update, it's showing me that my system is up to date 4.1.2. I don't understand. I thought flashing it back to stock factory will solve the problem.
Thanks a lot in advance for you hep
diamondx911 said:
Please help, my nexus was unlocked rooted with trinity kernel. When i pushed update, my tablet restarted with clockwokmod and failed to update
to 4.2. i believed it was because of custom kernel so i then flashed to stock factory, and re locked using nexus toolkit.
When i go to setting for update, it's showing me that my system is up to date 4.1.2. I don't understand. I thought flashing it back to stock factory will solve the problem.
Thanks a lot in advance for you hep
Click to expand...
Click to collapse
1) If you are using a custom kernel and/or custom recovery and/or removed/froze required system apks and/or modified build.prop and/or have a dozen other "custom" things, then the OTA update will NOT work. Period. You need to revert ALL of that. Stock kernel, recovery, system apks, build.prop, etc. Because if any of those aren't stock, the install will abort.
2) Having root is irrelevant. The update will remove suid access on the binary, so you will need to "re-root", but the binaries presence is irrelevant.
3) If it failed the OTA update, it won't download it again right away. Your best bet is to download the file and try to flash manually in a custom recovery (which will work as long as everything else is stock).
4) Did you say you relocked the tablet? If so, why? That was NOT required, and you just f*cked yourself, because you won't be able to flash a custom recovery back without unlocking the bootloader again, which will wipe your sdcard. There is NO reason to relock unless you are returning the device.
5) Again, this is why I hate toolkits. Learn to do things manually and you will be much better off.
At this point, assuming you relocked the bootloader, you will probably need to do a full factory reset and unlock it again. Then flash custom recovery and then flash the update. Or, since it would have been reset at that point, just download the full image from Google and flash that, then flash custom recovery.
phonic said:
1) If you are using a custom kernel and/or custom recovery and/or removed/froze required system apks and/or modified build.prop and/or have a dozen other "custom" things, then the OTA update will NOT work. Period. You need to revert ALL of that. Stock kernel, recovery, system apks, build.prop, etc. Because if any of those aren't stock, the install will abort.
2) Having root is irrelevant. The update will remove suid access on the binary, so you will need to "re-root", but the binaries presence is irrelevant.
3) If it failed the OTA update, it won't download it again right away. Your best bet is to download the file and try to flash manually in a custom recovery (which will work as long as everything else is stock).
4) Did you say you relocked the tablet? If so, why? That was NOT required, and you just f*cked yourself, because you won't be able to flash a custom recovery back without unlocking the bootloader again, which will wipe your sdcard. There is NO reason to relock unless you are returning the device.
5) Again, this is why I hate toolkits. Learn to do things manually and you will be much better off.
At this point, assuming you relocked the bootloader, you will probably need to do a full factory reset and unlock it again. Then flash custom recovery and then flash the update. Or, since it would have been reset at that point, just download the full image from Google and flash that, then flash custom recovery.
Click to expand...
Click to collapse
Haha, thanks for answering... the update came back by itself.
I was not aware of anything when i unlocked and rooted my nexus. please bare with me. I'm new to the android scene. but i'm very familiar with the hacking tool, i hacked and unlocked everything i own in my house, from 3 iphones, to my psp , xbox, ps3 and psp. when i first got my hand on the nexus i saw some dead black line of pixel that was appearing for half a second, after i read that a custom kernel can fix it,
I just did it fast and was not in a mood to start learning that sh*t from scratch. so now i'm on 4.2 , i know i lost everything. i will just have to unlock again and and root it....
diamondx911 said:
Haha, thanks for answering... the update came back by itself.
I was not aware of anything when i unlocked and rooted my nexus. please bare with me. I'm new to the android scene. but i'm very familiar with the hacking tool, i hacked and unlocked everything i own in my house, from 3 iphones, to my psp , xbox, ps3 and psp. when i first got my hand on the nexus i saw some dead black line of pixel that was appearing for half a second, after i read that a custom kernel can fix it,
I just did it fast and was not in a mood to start learning that sh*t from scratch. so now i'm on 4.2 , i know i lost everything. i will just have to unlock again and and root it....
Click to expand...
Click to collapse
Understood, and "hacking" android, especially Google devices, is pretty easy once you know what you are doing. The reason I dislike toolkits is that it prevents people from understanding the process, which really is fairly easy to understand, and can complicate troubleshooting steps.
The bootloader can easily be unlocked and locked. It takes one command and it's done. In order to flash anything with fastboot, you need it to be unlocked. The problem is, when you do this, it factory resets the device. So if you inadvertantly relock it, your going to need to reset it to unlock it again.
Even without the toolkit, going from unopened stock Nexus7 to fully rooted, updated and custom firmware Nexus7 only takes maybe 10 minutes, and 9 minutes of that is waiting for it to finish doing the various steps (flashing, rebooting, etc.). The most time consuming part is, unless you have good backups, restoring all your apps and settings. Titanium Backup is the best tool (IMHO) for that.
But yeah, in this case, you're going to need to unlock/wipe again. However, you CAN backup your "sdcard" to your computer and push the files back to it after the wipe. That can be very time consuming depending on how much you have.
So I have a VZN Moto X DE and have tried a few times to take the 4.4.4 OTA. It errors out during the system update. To do this, I flashed back the stock recovery and disabled Xposed. My phone is encrypted as it is required for work. I have thought about trying to simply flash the FXZ file in fastboot (I have read of a few people that have had success with this). My question is if my encryption could be causing the error and if it will cause issues trying to flash from fastboot. My understanding is that the encryption should be the /data partition only which I don't think should be touched. Any words of knowledge in this area or wisdom as to why the OTA is failing?
Thanks
I am not sure about the encryption. But are you starting from full stock? Stock recovery and no system apps frozen? Also are you using mfastboot when flashing your system.img?
Trying to flash stock on my brand new (used) N5 awhile back....I bricked it and was VERY lucky to bring it back to life, cause some in my situation didn't. Why? It was encrypted and I didn't know it. Nor did I know the signs that it was, cause I've never used encryption.
So if you ask me....un-encrypt it first!!
My problem was like yours...I couldn't touch the data partition without errors....can't remember if I got as far as system....but somehow I kinda forced it...and boom. Bricked.
Luckily I found a debrick bat file that got it back.
Someone may know how to work around it, but I'd not try to flash it encrypted. I guarantee there's no such bat file to bring the X back to life.
Travisdroidx2 said:
I am not sure about the encryption. But are you starting from full stock? Stock recovery and no system apps frozen? Also are you using mfastboot when flashing your system.img?
Click to expand...
Click to collapse
Thanks Travisdroidx2 - I believe I should be stock. I bought it used with a custom ROM on it. I SBF'ed (or whatever it is called now) it back to stock and installed xposed. I haven't frozen any apps and have the stock recovery. I wasn't using mfastboot, I was trying to use the OTA. I am curious if I can use mfastboot and a system.img with an encrypted phone. Really don't feel like bricking it.
PhilD41 said:
Thanks Travisdroidx2 - I believe I should be stock. I bought it used with a custom ROM on it. I SBF'ed (or whatever it is called now) it back to stock and installed xposed. I haven't frozen any apps and have the stock recovery. I wasn't using mfastboot, I was trying to use the OTA. I am curious if I can use mfastboot and a system.img with an encrypted phone. Really don't feel like bricking it.
Click to expand...
Click to collapse
I have zero experience with encrypted. So I would see if someone can answer that part for you.
I should clarify. I am using fastboot (linux) not mfastboot. I believe that is a windows tool. Thanks Travisdroidx2. This is the first phone i have ever used encryption on as well so it is all new.
PhilD41 said:
I should clarify. I am using fastboot (linux) not mfastboot. I believe that is a windows tool. Thanks Travisdroidx2. This is the first phone i have ever used encryption on as well so it is all new.
Click to expand...
Click to collapse
First, @PhilD41, yes mfastboot is for windows. The Linux variant of fastboot does not have the issues of not being able to flash system.img that Windows users have with the standard fastboot (they HAVE to use mfastboot).
2nd.... Do / Can you use TiBu? If so, why not backup any APPS you must have (and can't re-download from the play store), copy everything from your internal storage to your PC (including the backups you just made in TiBu), then flash the FULL FXZ with the following commands:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem config carrier vzw
fastboot oem fb_mode_clear
This will return you to 100% bone stock. At this point, you can RE-ENCRYPT, re-flash TWRP (which will root for you), and then put everything back the way you want it....
Apologizes if there is some reason I'm missing why you can't / wouldn't do this....
Thanks samwathegreat, I could do that... and I might end up there. The reason I went with stock and xpose'd (besides the fact that it does most everything I need) was to get away with wiping and spending time setting up my phone again. I did that for years on my GNex and still keep a current TiBu / SMS / MMS backup. I was really hoping for a quick flash back to stock recovery and the OTA. Well that didn't work. I figure the next best thing is a fastboot system update without having to mess with my user data. If the answer is to wipe and start over I can.... just won't be for a few weeks with my current schedule.
PhilD41 said:
Thanks samwathegreat, I could do that... and I might end up there. The reason I went with stock and xpose'd (besides the fact that it does most everything I need) was to get away with wiping and spending time setting up my phone again. I did that for years on my GNex and still keep a current TiBu / SMS / MMS backup. I was really hoping for a quick flash back to stock recovery and the OTA. Well that didn't work. I figure the next best thing is a fastboot system update without having to mess with my user data. If the answer is to wipe and start over I can.... just won't be for a few weeks with my current schedule.
Click to expand...
Click to collapse
I understand. I just don't have ANY information that suggests you will be able to manually flash (and preserve userdata) without TOTALLY messing your phone up to all hell, because of the encryption. (wouldn't that suck....)
This is the safe route. The update isn't that big of a deal anyways...
Please update us as to success when you do have the opportunity to get around to this.
I'd probably decrypt first.
Are you properly disabling Xposed? There should be an xposed-recovery-disabler.zip file in the following directory that you should flash.
Sdcard/android/data/de.robv.android.closed.installer/files
You an also just flash the system.img of the OS version you are currently running. It won't mess up your data and all you need to do is install xposed again after you root and everything is back to normal.
Sent from my Dev Edition Moto X
Rooting and unlocking a phone that is used for work purposes, especially when they require device encryption, is asking for trouble.
Schaweet said:
I'd probably decrypt first.
Are you properly disabling Xposed? There should be an xposed-recovery-disabler.zip file in the following directory that you should flash.
Sdcard/android/data/de.robv.android.closed.installer/files
You an also just flash the system.img of the OS version you are currently running. It won't mess up your data and all you need to do is install xposed again after you root and everything is back to normal.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
Please tell how you would decrypt? AFAIK (I could certainly be mistaken...) you CAN'T decrypt...you can only "factory reset" to remove encryption...
I'm interested....especially since I would imagine that would have been the first thing the OP would have done....simply "decrypt", then accept the OTA, then re-encrypt...
imnuts said:
Rooting and unlocking a phone that is used for work purposes, especially when they require device encryption, is asking for trouble.
Click to expand...
Click to collapse
Agreed. He appears to be using some Xposed module to "hide root" from the root-detection used by the corporate apps (Exchange, etc. ?)
As far as a nexus goes...you can decrypt by doing a factory reset....only with stock recovery tho.
Or you can format /data.
Either way....all the important stuff you wanted to encrypt is gone.
---------- Post added at 08:17 PM ---------- Previous post was at 08:16 PM ----------
So yes, you can't actually decrypt.....only wipe it out. Lol
That's why hardly anyone uses encryption. That, and it slows the phone down. So I've read....never actually did it.
Actually it isn't that complicated. It is my personal phone. My work went Google for email, calendar, and apps. So with encryption I can sign into my work google account. Not "hide root" required. As for decrypt, that was my understanding as well. It is a one way street that ends in a wipe if you undo it. As for uninstalling xposed, that is possible. I am just using the uninstall button in xposed. If that doesn't do it then I am doing it wrong. I appreciate the conversation and ideas. I may try flashing over the system.img file currently on first and see if that lets me take the OTA. Still need to wait till I have a few hours to dedicate in case something bad happens.
PhilD41 said:
Actually it isn't that complicated. It is my personal phone. My work went Google for email, calendar, and apps. So with encryption I can sign into my work google account. Not "hide root" required. As for decrypt, that was my understanding as well. It is a one way street that ends in a wipe if you undo it. As for uninstalling xposed, that is possible. I am just using the uninstall button in xposed. If that doesn't do it then I am doing it wrong. I appreciate the conversation and ideas. I may try flashing over the system.img file currently on first and see if that lets me take the OTA. Still need to wait till I have a few hours to dedicate in case something bad happens.
Click to expand...
Click to collapse
If you are manually installing the OTA.zip (i.e. you have it on the /SDCard, boot to recovery and try to install), it should tell you WHY it failed. You can then just work the issues out. Not sure if it will work since /sdcard would be encrypted, so I'm not sure if recovery will be able to access it properly or not.
I would back up all your important data from the phone... i.e. stuff you can't "live without" if you lose.
When all else fails... use RSDlite to flash the FXZ, and make sure you erase userdata and cache. You'll be stock, 4.4.4 but have to set everything back up again, install all your apps, etc.
PhilD41 said:
Actually it isn't that complicated. It is my personal phone. My work went Google for email, calendar, and apps. So with encryption I can sign into my work google account. Not "hide root" required. As for decrypt, that was my understanding as well. It is a one way street that ends in a wipe if you undo it. As for uninstalling xposed, that is possible. I am just using the uninstall button in xposed. If that doesn't do it then I am doing it wrong. I appreciate the conversation and ideas. I may try flashing over the system.img file currently on first and see if that lets me take the OTA. Still need to wait till I have a few hours to dedicate in case something bad happens.
Click to expand...
Click to collapse
You'll want to flash this file in recovery to disable xposed (for me uninstall in in the app worked, some say you have to flash the zip)
https://drive.google.com/folder/d/0B89vrGhlDBcENTZvOHhSMlEzU2c/edit
Guys...why are we posting info that's already on page 1 of this thread? The EXACT same info...
samwathegreat said:
Guys...why are we posting info that's already on page 1 of this thread? The EXACT same info...
Click to expand...
Click to collapse
I have mine set to 20 posts per page, so this is still page 1
I must have missed someone else saying that flashing the OTA manually from stock recovery tells you why it failed... (and the OP asked for insights on why it failed, last sentence of the post)
And I'll blame my sinus infection... I'm not thinking clearly
KidJoe said:
I have mine set to 20 posts per page, so this is still page 1
I must have missed someone else saying that flashing the OTA manually from stock recovery tells you why it failed... (and the OP asked for insights on why it failed, last sentence of the post)
And I'll blame my sinus infection... I'm not thinking clearly
Click to expand...
Click to collapse
Correct you are...that detail was never mentioned. ( I miss things too at times -- as you can see )
Anyways glad you can't 'catch' that through the computer LOL - those are just awful!! Hope you're loading up on sudafed, or the like...
Since the OP has limited time and can't risk any possibility of data loss, or the any number of bad things that *could* happen (boot loops?), I really hope he goes with the backup / wipe data / full FXZ method....when he can get around to it. These are the reasons I avoid encryption (though he doesn't appear to have a choice in the matter).
Thanks guys!! I may try to find some time this weekend to play. I don't have data I "can't" loose, just a pain to set up again. I use to wipe, flash, re-install once or twice a week on the GNex. Got it down to a pretty good science. Looks like my OTA was stored in /cache which I might be able to access in recovery. Otherwise, I might just clear it off and run the full stock, again. Right now it is working well enough that I am not looking forward to breaking it. Then again, if it isn't broken you aren't trying hard enough.
So this is a bit of a comedy of errors on my part...
I took the OTA update to lollipop and (foolishly) followed the same method as on KK to get root, putting myself in a bootloop. I got myself out of it by clearing the userdata and the cache.
I went about sorting everything and achieved root using the chainfire method, that was fine and I then went about reinstalling the xposed modules I had before. Foolishly, I didn't double check the status of xposed on Lollipop and consequently put myself back in a bootloop (idiot). I redid what had worked earlier, clearing the userdata and the cache to no avail.
Obviously, the problem was not the same as before and I needed to disable xposed, but in clearing the userdata I not only removed the xposed_disable.zip file to do this and also turned off adb so I can't push it.
The bootloader is fine and I can use fastboot, but can't push anything across. I hadn't replaced the recovery but can boot into twrp. However, I cannot flash it because I cannot push it over using adb.
I can't work out exactly how far I need to go back/what exactly I need to flash in order to put this all back together again.
I would be very grateful for any help that people can give on this.
Seems you need a .19 stock system partition image to get rid of the bootloop. Hope somebody can backup his system after OTA and share his image,otherwise you have to wait for official release or take risk to downgrade.
----------------------------
If you can boot from TWRP, you can try put the Xposed-Disabler-Recovery.zip in an USB SD card(maybe need formatted to particular filesystem like ext4) linked your phone with otg cable,then mount the sdcard and flash the zip file via TWRP.
If you're not worried about going back with a full wipe to KK, you can follow this link here Seeing that you can get your phone into fastboot, it'll work fine.
HAXTREME said:
If you're not worried about going back with a full wipe to KK, you can follow this link here Seeing that you can get your phone into fastboot, it'll work fine.
Click to expand...
Click to collapse
Thank you! This seems to have solved the problem (whatever exactly it was) and the mobile data is fine which was what I was most unsure about.
I'm curious, my device was a XT1092GB (or at least, I believe it was a GB) and now shows as a 'reteu' where I believe it used to show as 'retgb'. This isn't a problem as it all seems to work, but should I be expecting the Lollipop OTA update to come through? I deliberately didn't follow through on the last part of that thread and install 5.0 that way, I didn't want to tempt fate! However, I would like the update if possible and am unsure which way to go about doing it.
Again, many thanks for all the suggestions everyone. This is why android is awesome
Its a stock EU 4.4.4 so the OTA should come through. Even if it doesn't, I'm sure there's a 5.0 retgb firmware doing the rounds on this forum.
HAXTREME said:
Its a stock EU 4.4.4 so the OTA should come through. Even if it doesn't, I'm sure there's a 5.0 retgb firmware doing the rounds on this forum.
Click to expand...
Click to collapse
I guess even if the 5.0 OTA doesn't come through (for the reasons as given here, any following OTA updates should be fine, right?
If not, do you reckon then 5.0 rom given in the link you sent would be appropriate or would this be a better route?
Thanks for the help!
Hi!
I was searching for this but cant get clear info about it.
I m totally noob in android flashing, etc... I never touch my phone but now the warranty is expired... so i want to root and other stuff, but that's not the reason I'm here....
I have a Moto X 2013 XT 1058
Personal Argentina Kitkat 4.4.4 (212.44.26.ghost_row.Personal.en.AR - KXA21.12-L1.26)
Unrooted - bootloader locked (stock)
I recieved yesterday the OTA to update to Lollipop 5.1. I downloaded and saved for later, but i dont dare to install it, becouse with KK all things going great!.. i use Nova Launcher, Tasker, autovoice, and lots of custom stuff... I dont know what's gonna happend with all that if I update..
But the thing is that i read there's no way to downgrade once you updated to 5.1 (by OTA)
My question is...
What should i do to mantain the possibility of downgrade?
My guess is ..
1. Unlock the bootloader
2. flash 5.1 firmware (can i do this without update the bootloader?? and without wipe user data?, how?)
3. Use the phone, and if i dont like it.. (if the bootloader was not updated) downgrade to KK 4.4.4 again
4. flash 4.4.4.
Is would be a problem if runs 5.1 rom and KK bootloader?...
is possible any of this... without unlock bootloader? (guess not.. but still ask)
any other special procedure or "notes" that i should take care of?
If I root my current rom, can i make an image of the system, and then restore after taking the above mentioned steps?..
(what should i use to do that?)
Thank you very much for helping!! because, I m not going to install OTA update without knowing this things...
P.s. Sorry for my bad english.. , and really sorry if i m posting in wrong way
I would suggest you fully read -> http://forum.xda-developers.com/moto-x/general/info-warning-risks-downgrading-impacts-t3058202
What I did so I could go back to kit kat was wait for a developer to make a version that doesn't update the bootloader. There is a rom now that I'm running for the xt1053 model on 5,1, that doesn't update the bootloader. I'm in the same boat as you, using xt1058, but mines Rogers. The only thing that doesn't work is speaker phone. There should be a version available soon for our model, so you can wait. Lollipop has its issues, high cell stanby, which can be fixed by turning off carrier internet. If you want to do what I did, so you can go back if wanted is unlock the bootloader, root, flash custom recovery, then flash the xt1053 rom that doesn't update the bootloader. I will post link to rom
---------- Post added at 11:01 AM ---------- Previous post was at 10:59 AM ----------
http://forum.xda-developers.com/showthread.php?t=3155843
---------- Post added at 11:03 AM ---------- Previous post was at 11:01 AM ----------
May I also suggest flashing xposed module, it is amazing. Then download gravitybox. It makes it so you have most of the features of a custom rom on stock
According to KidJoe's thread he is referencing, even you unlock the bootloader and successfully turn on your phone after flash the 4.4 SBF. You may experience bugs here and there. In a word, don't do it.
Sorry for no feedback... i didt have time for my beloved phone...
i read the threads, but there are many unrelated things that i lost the trail!
I downloaded a file... :
Code:
XT1058_GHOST_RETBR_5.1_LPA23.12-15_cid12_CFC.xml.zip
This is a RSDlite file... isnt it? but... it contains:
Code:
boot.img
factory_version_info_cfc.txt
flashfile.xml
fsg.mbn
gpt.bin
logo.bin
motoboot.img
NON-HLOS.bin
recovery.img
servicefile.xml
system.img
if i unlock my bootloader and flash SOME of this files (boot.img, system.img, and logo.bin)... with mfastboot.. what happend?
boot.img, system.img... and what else do i need?.. (I know that i dont have to flash motoboot.img and gpt.bin in order to leave my bootloader alone)
I m going to get 5.1 with KK bootloader doing this or i will brick my phone?.. (dont?. Why??)
Should i flash the other files?
fsg.mbn (dont know what this is)
NON-HLOS.bin (modem?... should i flash it?... should i erase modemst1 and st2 partition if i flash this?)
recovery.img (what if i want to put TWRP recovery? .. can i flash TWRP.img instead of recovery.img???)
is erasing data necessary?..
flashfile.xml file for RSDlite is:
Code:
<?xml version="1.0" ?>
<flashing>
<header>
<phone_model model="ghost_retbr"/>
<software_version version="ghost_retbr-user 5.1 LPA23.12-15 20 release-keysMSM8960PRO_BP_23255.138.89.00R"/>
<interfaces>
<interface name="AP"/>
</interfaces>
</header>
<steps interface="AP">
<step operation="getvar" var="max-download-size"/>
<step operation="oem" var="fb_mode_set"/>
<step MD5="3e8836a120a564338f472f0895c947c8" filename="gpt.bin" operation="flash" partition="partition"/>
<step MD5="d089f063b897f108729d6ffcf63679e2" filename="motoboot.img" operation="flash" partition="motoboot"/>
<step MD5="4bfe6f5412c1c419150bf25f953b61d4" filename="logo.bin" operation="flash" partition="logo"/>
<step MD5="d2d88677984930fc2a0e8e167bbccad0" filename="boot.img" operation="flash" partition="boot"/>
<step MD5="e55b202a063a58cc1d7b47dcb65658cf" filename="recovery.img" operation="flash" partition="recovery"/>
<step MD5="35a58369963b281e963920bd4d9e1b77" filename="system.img" operation="flash" partition="system"/>
<step MD5="3a094721acc8fcd15ae114c0854f3395" filename="NON-HLOS.bin" operation="flash" partition="modem"/>
<step operation="erase" partition="modemst1"/>
<step operation="erase" partition="modemst2"/>
<step MD5="76b8c66ef4480e84a8f1b69800541115" filename="fsg.mbn" operation="flash" partition="fsg"/>
<step operation="erase" partition="cache"/>
<step operation="erase" partition="userdata"/>
<step operation="erase" partition="customize"/>
<step operation="erase" partition="clogo"/>
<step operation="oem" var="fb_mode_clear"/>
</steps>
</flashing>
if i go with RSDLite... this modifications will work for what i want??
Code:
<?xml version="1.0" ?>
<flashing>
<header>
<phone_model model="ghost_retbr"/>
<software_version version="ghost_retbr-user 5.1 LPA23.12-15 20 release-keysMSM8960PRO_BP_23255.138.89.00R"/>
<interfaces>
<interface name="AP"/>
</interfaces>
</header>
<steps interface="AP">
---------DELETE <step operation="getvar" var="max-download-size"/>
<step operation="oem" var="fb_mode_set"/>
---------DELETE <step MD5="3e8836a120a564338f472f0895c947c8" filename="gpt.bin" operation="flash" partition="partition"/>
---------DELETE <step MD5="d089f063b897f108729d6ffcf63679e2" filename="motoboot.img" operation="flash" partition="motoboot"/>
<step MD5="4bfe6f5412c1c419150bf25f953b61d4" filename="logo.bin" operation="flash" partition="logo"/>
<step MD5="d2d88677984930fc2a0e8e167bbccad0" filename="boot.img" operation="flash" partition="boot"/>
---------DELETE <step MD5="e55b202a063a58cc1d7b47dcb65658cf" filename="recovery.img" operation="flash" partition="recovery"/>
<step MD5="35a58369963b281e963920bd4d9e1b77" filename="system.img" operation="flash" partition="system"/>
<step MD5="3a094721acc8fcd15ae114c0854f3395" filename="NON-HLOS.bin" operation="flash" partition="modem"/>
<step operation="erase" partition="modemst1"/>
<step operation="erase" partition="modemst2"/>
<step MD5="76b8c66ef4480e84a8f1b69800541115" filename="fsg.mbn" operation="flash" partition="fsg"/>
<step operation="erase" partition="cache"/>
---------DELETE <step operation="erase" partition="userdata"/>
---------DELETE <step operation="erase" partition="customize"/>
<step operation="erase" partition="clogo"/>
<step operation="oem" var="fb_mode_clear"/>
</steps>
</flashing>
Should i delete any other line??.. (or undelete?)
And most important..
Can i flash stock rom if something goes wrong?.. (loading logo hangs... dont like LP.. etc?) or a rom backup (if i find the way to make a backup of my actual rom.. =)... can it be done with TWRP?)
Thanks!... and sorry if i'm asking something basic... but .. the more i read, more confused i am!
KidJoe said:
I would suggest you fully read -> http://forum.xda-developers.com/moto-x/general/info-warning-risks-downgrading-impacts-t3058202
Click to expand...
Click to collapse
Buddy, your info is not very accurate, don't care to blame you, but you can't flash gpt or motoboot if you have newer version, the bl just won't let you.
Also I've downgraded 4 Moto X 2013 from 5.1 to 4.4.4 without any issue.
Unless you can somehow prove your info there, better correct it.
Ppl just tend to do stupid things like going 4.4.2 or earlier and update via OTA, which causes the broken bl.Also some get soft bricked coz of not wiping user data....
liveroy said:
Buddy, your info is not very accurate, don't care to blame you, but you can't flash gpt or motoboot if you have newer version, the bl just won't let you.
Click to expand...
Click to collapse
"Buddy"?? I don't know you, so as written, it comes across with a negative connotation. I'm not really sure how you meant it, or what your feelings are there...
But I suggest you step back and read that post (and the thread) a little closer, because the entire point of that is you can't flash an older GPT.BIN or Motoboot.img (or the parts included in motoboot.img), or downgrade them. Read FAQ #1 in that post, that calls out GPT/Motoboot while suggesting not downgrading... as do others, like #16. So maybe I generalized more than you like with the term "downgrade" but most will attempt using RSDlite and NOT edit the XML. Plus skipping parts (using fastboot or editing the XML with RSDLite) while trying to downgrade can cause other issues, so again, downgrading is generally not advised.
liveroy said:
Also I've downgraded 4 Moto X 2013 from 5.1 to 4.4.4 without any issue.
Click to expand...
Click to collapse
As I said in that thread (just maybe not the first post), some have claimed success... and 5.1 to 4.4.4 does appear to be less risky... We're seeing more try 5.1 -> 4.4.4 and posting "it worked," where as with 4.4.4 -> 4.4.2 and 4.4.2 -> lower nearly everyone who attempted had bricked and needed help recovering their phone. And because of the amount of bricks from attempts at downgrading in the past, the MODS would close and delete any posts suggesting downgrading was anything but risky.
In any case, you now have GPT and parts contained in Motoboot (specifically Bootloader, potentially TZ, and other parts) from 5.1 with the rest of 4.4.4 parts. And we've seen some features not working this way (speaker phone, Settings -> Security kicks you out, etc.)
Also in its current state, if your phone prompts you about the 5.1 OTA, and you click the wrong thing and accept it, then as even you mention, taking an OTA could cause you issues. (I also mentioned in that post/thread.)... So you'd also need to take steps to prevent being prompted for the OTA if your downgrade attempt is successful.
liveroy said:
Unless you can somehow prove your info there, better correct it.
Click to expand...
Click to collapse
Well, I do have a few threads linked in the OP of that thread from people who did try to downgrade and bricked, including some who skipped GPT/MOTOBOOT. So I would hope that counts as proof, or at least sufficient supporting evidence for providing warnings and caution messages if/when suggesting someone else downgrades their phone. And if you search, I'm sure you could find the many 4.4.4 -> 4.4.2 downgrade attempts that resulted in bricks.
Are all the bricks Hard/Solid? No. And I say that in the post and later in that thread.. there are varying degrees, some could be recovered and some couldn't. s5610 has done a lot with helping many who bricked downgrading from 5.1 to 4.4.4 recover.
liveroy said:
Ppl just tend to do stupid things like going 4.4.2 or earlier and update via OTA, which causes the broken bl.Also some get soft bricked coz of not wiping user data....
Click to expand...
Click to collapse
Funny, I mention to not downgrade then take an OTA as that causes a problem. (faq #1)
So it pretty much looks like you are agreeing with my warnings in that post/thread, so I'm not sure what your problem is? Just that I didn't word it clearly enough? or???
If you have specific points/numbers that you disagree with, please post in that thread, quoting what you think is wrong, what evidence you have that its wrong (other than it works on your phone, please provide me with posts supporting your stance), and I'll be happy to discuss and/or make corrections if I agree with you.
KidJoe said:
"Buddy"?? I don't know you, so as written, it comes across with a negative connotation. I'm not really sure how you meant it, or what your feelings are there...
But I suggest you step back and read that post (and the thread) a little closer, because the entire point of that is you can't flash an older GPT.BIN or Motoboot.img (or the parts included in motoboot.img), or downgrade them. Read FAQ #1 in that post, that calls out GPT/Motoboot while suggesting not downgrading... as do others, like #16. So maybe I generalized more than you like with the term "downgrade" but most will attempt using RSDlite and NOT edit the XML. Plus skipping parts (using fastboot or editing the XML with RSDLite) while trying to downgrade can cause other issues, so again, downgrading is generally not advised.
As I said in that thread (just maybe not the first post), some have claimed success... and 5.1 to 4.4.4 does appear to be less risky... We're seeing more try 5.1 -> 4.4.4 and posting "it worked," where as with 4.4.4 -> 4.4.2 and 4.4.2 -> lower nearly everyone who attempted had bricked and needed help recovering their phone. And because of the amount of bricks from attempts at downgrading in the past, the MODS would close and delete any posts suggesting downgrading was anything but risky.
In any case, you now have GPT and parts contained in Motoboot (specifically Bootloader, potentially TZ, and other parts) from 5.1 with the rest of 4.4.4 parts. And we've seen some features not working this way (speaker phone, Settings -> Security kicks you out, etc.)
Also in its current state, if your phone prompts you about the 5.1 OTA, and you click the wrong thing and accept it, then as even you mention, taking an OTA could cause you issues. (I also mentioned in that post/thread.)... So you'd also need to take steps to prevent being prompted for the OTA if your downgrade attempt is successful.
Well, I do have a few threads linked in the OP of that thread from people who did try to downgrade and bricked, including some who skipped GPT/MOTOBOOT. So I would hope that counts as proof, or at least sufficient supporting evidence for providing warnings and caution messages if/when suggesting someone else downgrades their phone. And if you search, I'm sure you could find the many 4.4.4 -> 4.4.2 downgrade attempts that resulted in bricks.
Are all the bricks Hard/Solid? No. And I say that in the post and later in that thread.. there are varying degrees, some could be recovered and some couldn't. s5610 has done a lot with helping many who bricked downgrading from 5.1 to 4.4.4 recover.
Funny, I mention to not downgrade then take an OTA as that causes a problem. (faq #1)
So it pretty much looks like you are agreeing with my warnings in that post/thread, so I'm not sure what your problem is? Just that I didn't word it clearly enough? or???
If you have specific points/numbers that you disagree with, please post in that thread, quoting what you think is wrong, what evidence you have that its wrong (other than it works on your phone, please provide me with posts supporting your stance), and I'll be happy to discuss and/or make corrections if I agree with you.
Click to expand...
Click to collapse
I won't multi-quote, to reduce size.
You seem very offended, even though I meant exactly the opposite, this was more like creative criticism. That's why I've used "buddy" instead of smth offensive, just fyi.I also said I won't bother to actually blame you for posting info that is not entirely true and many ppl want to downgrade, because the LP build is buggy, the Moto X just doesn't feel right on it.
Actually for the sake of the argument I can do a live session on downgrade from 5.1 to 4.4.4 on Twitch ot Youtube, but if that's the case you'll owe me an apology, which is not my sole intent.
I agree that you have mentioned about gpt and motoboot, but you still strongly advice against downgrade, when that actually is NOT so dangerous if done right and basically it's not very hard to do either.
Also to be honest, use of RDS from users that for no idea what they are doing is probably the biggest problem. While using fastboot is way safer and the way to go.
Anyway, tone down a bit and let's have a healthy conversation, so the users can actually get a grip on the stuff and what is actually possible , while keeping the risk at minimum.
liveroy said:
...Actually for the sake of the argument I can do a live session on downgrade from 5.1 to 4.4.4 on Twitch ot Youtube, but if that's the case you'll owe me an apology, which is not my sole intent.
I agree that you have mentioned about gpt and motoboot, but you still strongly advice against downgrade, when that actually is NOT so dangerous if done right and basically it's not very hard to do either.
Click to expand...
Click to collapse
I apologize if you didn't mean offence by it. You've been on line long enough to know that type written communications on these boards can be misunderstood. i.e. you can't hear the inflection in a person's voice, see their body language, so its hard to read some meanings. So I hope you can understand how, not seeing, hearing or knowing you, that calling me "buddy" could be taken in a way you might not have meant. And yeah, some of my frustration may have shown through the words and phrasing I chose when typing because that bothered me.
That being said...
I know why people would want to downgrade (see FAQ #4 in that post)
As for a live session, I'm not sure what that will do... I've already said people can downgrade by skipping parts (i.e. GPT/Motoboot) BUT that it does cause its own issues. We've seen reports of more bugs, and or things not working properly, some can live with those bugs and others can't. And of course people who accidentally took the OTA later usually, but not always, run into problems.
So if that is how you are downgrading, then there is nothing new to show me.
Your post said that you have "downgraded 4 Moto X 2013 from 5.1 to 4.4.4 without any issue." but you haven't said how. Did you skip flashing gpt/motoboot? In my reply to you, I state that you have mixed gpt/motoboot parts on the phone now. In your response, you did not comment. I've addressed your points, albeit with a slightly aggravated tone for which I apologize, so I was hoping that you could respond to them.
As you say... "if you do it right".... Ok, but no one has provided a "right way" that is 100% fool proof and has been 100% safe.
I've said in the past, I don't know everything. I don't claim to be the "end all/be all" source. In a discussion with someone claiming to be from Moto a while back who started a thread saying it was safe to downgrade and it does work (which was later deleted by the MODs because of all the people that jumped into that thread having bricked attempting it).. I said, I don't know how moto expects it should work, I just know based on hanging in this and other forums, of what actually happens. And that is still my position today.
So I don't mind if someone can show me I'm wrong. I welcome it, and appreciate the corrections as I don't want to spread WRONG/BAD info!
If you want to have a discussion, by all means, lets, but please provide a little more explanation around your difference in opinion.
KidJoe said:
I apologize if you didn't mean offence by it. You've been on line long enough to know that type written communications on these boards can be misunderstood. i.e. you can't hear the inflection in a person's voice, see their body language, so its hard to read some meanings. So I hope you can understand how, not seeing, hearing or knowing you, that calling me "buddy" could be taken in a way you might not have meant. And yeah, some of my frustration may have shown through the words and phrasing I chose when typing because that bothered me.
That being said...
I know why people would want to downgrade (see FAQ #4 in that post)
As for a live session, I'm not sure what that will do... I've already said people can downgrade by skipping parts (i.e. GPT/Motoboot) BUT that it does cause its own issues. We've seen reports of more bugs, and or things not working properly, some can live with those bugs and others can't. And of course people who accidentally took the OTA later usually, but not always, run into problems.
So if that is how you are downgrading, then there is nothing new to show me.
Your post said that you have "downgraded 4 Moto X 2013 from 5.1 to 4.4.4 without any issue." but you haven't said how. Did you skip flashing gpt/motoboot? In my reply to you, I state that you have mixed gpt/motoboot parts on the phone now. In your response, you did not comment. I've addressed your points, albeit with a slightly aggravated tone for which I apologize, so I was hoping that you could respond to them.
As you say... "if you do it right".... Ok, but no one has provided a "right way" that is 100% fool proof and has been 100% safe.
I've said in the past, I don't know everything. I don't claim to be the "end all/be all" source. In a discussion with someone claiming to be from Moto a while back who started a thread saying it was safe to downgrade and it does work (which was later deleted by the MODs because of all the people that jumped into that thread having bricked attempting it).. I said, I don't know how moto expects it should work, I just know based on hanging in this and other forums, of what actually happens. And that is still my position today.
So I don't mind if someone can show me I'm wrong. I welcome it, and appreciate the corrections as I don't want to spread WRONG/BAD info!
If you want to have a discussion, by all means, lets, but please provide a little more explanation around your difference in opinion.
Click to expand...
Click to collapse
I might end up writing a how-to sometime this weekend.
I started getting pms on how I did it, so that guide might help.
Also on a side note, I kinda sorry that you felt like you felt about my post, if something is still concerning you, feel free to contact me and we can discuss the matter.
With that said, I'm gonna work on the guide and post it and maybe get your input on it later on.
Hi, so I agreed to help a friend root his device. He's got a crappy Wiko Lenny 4 Plus. Ew. However, I cannot unlock the bootloader as he wishes to keep his saved wifi passwords. So my potentially very stupid question is: Could I extract the boot.img from the update zip, patch it, rename it back to boot.img and inject it back into the update zip? Or would that return a signature error or whatever?
We already tried root apps like framaroot, etc to bypass having to unlock the bootloader but they all didn't work and I really hate using those tools, most of them are pretty shady or very old or both.
What we also tried is to pull the wifi passwords via adb and then paste them back in the system once we're done, but that also didn't succeed.
(I tried the search function and I didn't find anything, if however I missed a thread that discusses just this, could u please point me towards it?)
Give it a try ... to be sure. I can't know for you (as I haven't any friend's phone to play with)
Does the phone support Google Play Services? Because it backs up and restores saved WiFi connections already. But if it doesn't for some reason, this guide at capturing and restoring them manually wasn't hard to find - https://www.reddit.com/r/Android/co...ifi_passwords_from_old_device?sort=confidence