Does anyone have a step-by-step instruction to successfully and easily downgrade or revert from 38R to 33R? I have root, titanium backup, and everything else is stock. I'm really hoping this is an easy process without too much loading and reloading.
Follow the steps, http://forum.xda-developers.com/showthread.php?t=2826541
You'll have to start from scratch. May I ask why you're downgrading?
Sent from my A0001 using Tapatalk
zephiK said:
Follow the steps, http://forum.xda-developers.com/showthread.php?t=2826541
You'll have to start from scratch. May I ask why you're downgrading?
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Are my apps screwed? I'm assuming I cant back them up and restore them with Titanium? I'm downgrading because I cant play Puzzles and Dragons (I know it's a sad excuse but I'd rather not carry two phones, and one used for just that game).
Did you not make a nandroid backup of 33R? You can backup all of your apps with Titanium and then restore them afterwards. You don't really need to follow the guide that Zephik linked you to though, you can just flash the recovery flashable version of 33R from here:
http://forum.xda-developers.com/showthread.php?t=2857110
Transmitted via Bacon
Related
My phone has been rooted using the old-school method. I've made a nandroid backup.
Can I follow the unroot guide to get stock everything, take it to the store, then use revolutionary to root it again, then restore the nandroid which was made on my phone with normal s-off? Or do I need to do the oldschool method before restoring the nandroid?
lukesed said:
My phone has been rooted using the old-school method, but I need to unroot it to get tech support (think my LTE radio is faulty). I've made a nandroid backup.
Can I follow the unroot guide to get stock everything, take it to the store, then use revolutionary to root it again, then restore the nandroid which was made on my phone with normal s-off? Or do I need to do the oldschool method before restoring the nandroid?
Click to expand...
Click to collapse
I would use this Tbolt tool to unroot it and make sure your on the .19 radio combo. That's the latest firmware radio. And use this tool to root it again and then you should be able to flash nandroid backup again believe. Here's the link to the TBolt tool
http://forum.xda-developers.com/showthread.php?p=27238740
heath2805 said:
I would use this Tbolt tool to unroot it and make sure your on the .19 radio combo. That's the latest firmware radio. And use this tool to root it again and then you should be able to flash nandroid backup again believe. Here's the link to the TBolt tool
http://forum.xda-developers.com/showthread.php?p=27238740
Click to expand...
Click to collapse
Thanks a lot! So after putting .19 radios on, all I need to do is use this too to 1) unroot and 2) put on some old OTA rom?
lukesed said:
Thanks a lot! So after putting .19 radios on, all I need to do is use this too to 1) unroot and 2) put on some old OTA rom?
Click to expand...
Click to collapse
Yup
Sent from my ADR6400L using Tapatalk 2
lukesed said:
Thanks a lot! So after putting .19 radios on, all I need to do is use this too to 1) unroot and 2) put on some old OTA rom?
Click to expand...
Click to collapse
Yes, you should be on 2.11.605.19 firmware . That's the latest.
Sent from my ADR6400L using Tapatalk 2
I am going to Odin back to 4.0.4 stock.
Can I just wipe and flash CM10.1 right aftter or is there a need to go to 4.1 first?
dpaine88 said:
I am going to Odin back to 4.0.4 stock.
Can I just wipe and flash CM10.1 right aftter or is there a need to go to 4.1 first?
Click to expand...
Click to collapse
You can go directly to CM10.1, no need to flash anything in particular beforehand. I believe the only requirement is an unlocked bootloader.
Make sure to do a nandroid backup of your existing setup first. You should also read the thread on backing up your IMEI.
CrustyMcLovin said:
You can go directly to CM10.1, no need to flash anything in particular beforehand. I believe the only requirement is an unlocked bootloader.
Make sure to do a nandroid backup of your existing setup first. You should also read the thread on backing up your IMEI.
Click to expand...
Click to collapse
Thank you very much.
If I already did backup my IMEI months ago, would I need to do that again?
dpaine88 said:
Thank you very much.
If I already did backup my IMEI months ago, would I need to do that again?
Click to expand...
Click to collapse
No your all good it's safe to always use your oldest imei backup anyways.
Sent from my SCH-I535 using xda app-developers app
I went into recovery, wiped data/factory reset and cleaned my caches then went to restore my nandroid for mb1, but it said the md5 failed and couldn't restore it, so I rebooted the phone and now it's back to complete stock/unrooted. Is there a way to fix it and be able to restore my nandroid, or do I have to start fresh? I lost all my pics and apps, it's there a way to restore those?
Sent from my SCH-I535 using xda app-developers app
yepyep14u2know said:
I went into recovery, wiped data/factory reset and cleaned my caches then went to restore my nandroid for mb1, but it said the md5 failed and couldn't restore it, so I rebooted the phone and now it's back to complete stock/unrooted. Is there a way to fix it and be able to restore my nandroid, or do I have to start fresh? I lost all my pics and apps, it's there a way to restore those?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
What rom were you on originally before your nandroid restore failed? Can you find any of your pics using a File Explorer? Lastly, how did you verify that you have lost root: did you look in /system/xbin/su or download an app such as Root Checker to verify you have lost root?
I was only stock rooted. Was on the newest md3, and like I said I did all the wipes in CMW then went into restore backup and selected my nandroid of mb1 and pressed ok, but it said the md5 was mismatched. Couldn't figure anything out so I did a reboot and it was like a new phone.....no superuser, titanium backup wouldn't get SU permissions and it would only boot into stock recovery. Plugged the phone into laptop and saw the nandroid on the sd card but not sure how to reroot and fix the nandroid
Sent from my SCH-I535 using xda app-developers app
yepyep14u2know said:
I was only stock rooted. Was on the newest md3, and like I said I did all the wipes in CMW then went into restore backup and selected my nandroid of mb1 and pressed ok, but it said the md5 was mismatched. Couldn't figure anything out so I did a reboot and it was like a new phone.....no superuser, titanium backup wouldn't get SU permissions and it would only boot into stock recovery. Plugged the phone into laptop and saw the nandroid on the sd card but not sure how to reroot and fix the nandroid
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
The best I could suggest if you are truly unrooted is to re-root and unlock using Open1your1eyes0 thread in the dev section. I'm not well versed in the md5 mismatching for a nandroid failing unless you changed the name of the nandroid after it was completed?
SlimSnoopOS said:
The best I could suggest if you are truly unrooted is to re-root and unlock using Open1your1eyes0 thread in the dev section. I'm not well versed in the md5 mismatching for a nandroid failing unless you changed the name of the nandroid after it was completed?
Click to expand...
Click to collapse
Yes I just checked with rootchecker and it says I lost root. I did rename the CWM nandroid, but I've done that before on my wife's phone and it restored fine.. I'm downloading the files from the thread you listed above as I write. I had Tibu installed before, so that should be enough to restore my lost apps/pics/etc once I Odin back and gain root again?
yepyep14u2know said:
Yes I just checked with rootchecker and it says I lost root. I did rename the CWM nandroid, but I've done that before on my wife's phone and it restored fine.. I'm downloading the files from the thread you listed above as I write. I had Tibu installed before, so that should be enough to restore my lost apps/pics/etc once I Odin back and gain root again?
Click to expand...
Click to collapse
Yea, try not to do that with CWM. I suggest using TWRP if you want to name backups since it allows you to do so natively. TWRP and CWM nandroids are not compatible so if you do switch, I suggest (if you can) restore your VRBMB1 nandroid using CWM, make a new backup using TWRP, then delete the entire CWM folder from your phone/sdcard.
I haven't done this before but you could see if this process works for you. If not, then start fresh via Odin and use TWRP so this doesn't happen again.
If you can still see the files using a file explorer, then TB should be able to locate and restore them if you know how to make it scan the entire device.
SlimSnoopOS said:
Yea, try not to do that with CWM. I suggest using TWRP if you want to name backups since it allows you to do so natively. TWRP and CWM nandroids are not compatible so if you do switch, I suggest (if you can) restore your VRBMB1 nandroid using CWM, make a new backup using TWRP, then delete the entire CWM folder from your phone/sdcard.
I haven't done this before but you could see if this process works for you. If not, then start fresh via Odin and use TWRP so this doesn't happen again.
If you can still see the files using a file explorer, then TB should be able to locate and restore them if you know how to make it scan the entire device.
Click to expand...
Click to collapse
I realize that now! Going through the Odin process now, then custom recovery and unlocking the bootloader. By glancing at that link, it says that using different versions of CMW causes this issue. Go figure. Ugh
yepyep14u2know said:
I realize that now! Going through the Odin process now, then custom recovery and unlocking the bootloader. By glancing at that link, it says that using different versions of CMW causes this issue. Go figure. Ugh
Click to expand...
Click to collapse
haha stick to TWRP, its great. Let me know how this goes.
SlimSnoopOS said:
haha stick to TWRP, its great. Let me know how this goes.
Click to expand...
Click to collapse
Will do! Just got used to CMW back in the day of our HTC evo 4g and stuck with it due to all the problems TWRP had back then
Hey guys, I've read a lot on updating after being rooted, but just need to confirm before I do mess up anything.
All I have done is Rooted Stock (I have TWRP on the phone), and have flashed volume mod, and also battery percent mod. (Other then that I am running Nova Launcher, Titanium Backup)
Guessing I need to flash the back to stock for volume and battery percent (Correct if I am wrong).
And then how exactly do I go about updating to 4.4.2 and preferably retaining root?
Sorry I know noob question, just making sure as I've always unrooted, and never had any mods when I have done updates in the past.
1) you have to flash back to stock system image since you modded your phone
2) once you either get the OTA or sideload it, you just flash cwm/twrp in fastboot and then flash the supersu.zip
thats all
so in other words go back and unroot completely, go completely back to stock, and redo everything from the beginning?
Just flash the 4.4.2 stock rooted rom in the dev section
sent from my HAMMERHEAD neXus
Or you can flash the Updated Super SU zip right?
Sent from my Nexus 5 using Tapatalk
AndroidRaven said:
so in other words go back and unroot completely, go completely back to stock, and redo everything from the beginning?
Click to expand...
Click to collapse
You are flashing back the stock ROM. If you want to keep data intact, flash only the boot.img, system.img
niv3d said:
Or you can flash the Updated Super SU zip right?
Click to expand...
Click to collapse
that won't help you get back to stock.
I guess I need a tutorial on what you guys are talking about because I still am not understanding..
Would flashing the rooted 4.4.2 work? And if so what do I need to do before I flash this?
How exactly do I go about only flashing only the boot.img and system.img?
Will I loose anything through this process?
Sent from my Nexus 5 using XDA Premium 4 mobile app
AndroidRaven said:
I guess I need a tutorial on what you guys are talking about because I still am not understanding..
Would flashing the rooted 4.4.2 work? And if so what do I need to do before I flash this?
How exactly do I go about only flashing only the boot.img and system.img?
Will I loose anything through this process?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Follow this guide --> http://forum.xda-developers.com/showthread.php?t=2523217
Best guide out there, with big thanks to El Daddy
AndroidRaven said:
I guess I need a tutorial on what you guys are talking about because I still am not understanding..
Would flashing the rooted 4.4.2 work? And if so what do I need to do before I flash this?
How exactly do I go about only flashing only the boot.img and system.img?
Will I loose anything through this process?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
One safe way to get the OTA, taking into account that you modded your phone, is:
i) flash system.img then flash stock recovery,
ii) once the OTA update is on your phone and you have accepted it (it installed itself) you are back to stock.
iii)flash your custom recovery and re-install your SuperSu to get back your root.
Good luck
Hello
All XDA members
I have a problem that made me raise a question an that is an we know the name of a rom from a nanriod backup either on PC or on Andriod.??
Ideally PC would be good !!
Thanks
Most ( not all) recovery apps let you name the file. Are you asking how to find the file? If so, it likely is in a folder named backups. You can move the file to your pc and keep it there if you are out of storage space.
Sent from my CROM-i X powered TF700T using tapatalk
stevens243 said:
Most ( not all) recovery apps let you name the file. Are you asking how to find the file? If so, it likely is in a folder named backups. You can move the file to your pc and keep it there if you are out of storage space.
Sent from my CROM-i X powered TF700T using tapatalk
Click to expand...
Click to collapse
Sorry if I wasn't clear please consider the following situation :
I have around 12 backups of different roms and I dont want to restore each n every backup for sake of simple file or simple thing. So any tool which can read the name of Rom? Probably the buildprop or about phone info will help
Sent from my A110 using Tapatalk
Well, if you gave a single boot system, your recovery should "see" all of those files. If so, you can usb them or copy to a sd card and move them. Just move them back when you need to.
Sent from my CROM-i X powered TF700T using tapatalk
Can someone explain nandroid backup to me? Does it mean I can make a backup my current rom and save it? Sorry for the dumb question.
Yep
TPS_Reports said:
Can someone explain nandroid backup to me? Does it mean I can make a backup my current rom and save it? Sorry for the dumb question.
Click to expand...
Click to collapse
Simply,it is a backup of your OS and settings. It is extremely valuable if you flash a new ROM that doesn't/won't function. Then, you can use your recovery to, well, recover your previous WORKING OS.
When/if you begin to flash new ROMs (and other tools that may corrupt your OS) you should always.first.backup.your.files.
Can I assume I would need to wipe data/factory reset, etc. before I restore the backup?
Sent from my VS980 4G using Tapatalk
No assumptions
TPS_Reports said:
Can I assume I would need to wipe data/factory reset, etc. before I restore the backup?
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
So, that depends on what your starting config is, what you upgraded to.
For instance, if you are stock and flash a ROM using the stock recovery, then likely yes. You should and you would use the stock bootloader to wipe with.
If you have loaded a new recovery (TWRP, CWM) then read(!) the instructions on the developers page. My example is that on my tablet, once I upgraded to TWRP, I SHOULD NOT use the factory wipe option as that would wipe both TWRP and the backup files. That would cause lots of problems so, don't assume.
Typically, you do need to data/reset/wipe prior to flashing a new or recovering to an old ROM, just be careful what/how you do it.
I have a CWM recovery installed and installed custom Rome before. I have always redid everything again. So a backup would save me a lot of time.
Sent from my VS980 4G using Tapatalk
TPS_Reports said:
I have a CWM recovery installed and installed custom Rome before. I have always redid everything again. So a backup would save me a lot of time.
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
Then, unless the ROM developer states otherwise, you should make backups, wipe data, install ROMs and recover your device using the Nandroid backup.
You likely shouldn't use the "factory" wipe data as that would cause issues.
Larry