Hey guys,
before I want to root or flash my GFs p7000 I'd like to know if there is a possibility to unroot or fully return to stock for example to RMA.
Hope you can shed some light in this
Thanks
I have just got this phone today and would also like to know this if anybody has the answer.
Just go to superSU -> Settings -> Full Unroot
and re-flash with this: (select everything)
image: i.imgur.com/dIo6xOc.png
link: mega.co.nz/#!F0JxxYKY!wCvtgpvdPx3RTp7FMc-w_oVxVPyy3FlHf-IHMNi8n-k
Related
Hi,
I am new to this forum and android stuff.
Please forgive me if I asked noob question.
I tried to search but got no complete answer.
My condition:
Nexus 7
build number JRO03S
used Nexus root toolkit 1.5.3
to unlock and root
used TWRP to install poitee kernel for usb dac.
Then:
The 4.1.2 updates notification show up
I pressed yes ... accidentally.
Now:
The build number becomes JRO03S
but the Android version is still 4.1.1
Question:
a. How to update to 4.1.2?
b. How to update without wiping any data and apps?
c. Do I have to reinstall the pointee kernel?
d. Will flashing rom ( updating to newer version ) wipe all things?
Sorry for so many questions,
For my situation it is a mixed up that I can't find similar condition on the internet yet.
Please kindly help and advise.
Much Thanks!
Btw,
I done below, no success:
1. quickboot
2. TWRP recovery
3. install nakasi-JZO54K-from-JRO03S.zip (from /sdcard)
4. error --> "Status 7" shown.
Cannot update.
Please Please help....
Use the wugs toolkit and go back to fully stock ROM, re lock the bootloader.
Only then will you be able to apply the OTA update.
backup your app data using titanium backup.
There is a modified version of the update that someone made. It doesn't perform the system checks that cause so many peoples devices to fail. If you can't run the update because you changed or deleted a system apk, read this post: http://forum.xda-developers.com/showpost.php?p=32752631&postcount=20
Don't run this if you're just not sure of why your update is failing.
vinny86 said:
Use the wugs toolkit and go back to fully stock ROM, re lock the bootloader.
Only then will you be able to apply the OTA update.
backup your app data using titanium backup.
Click to expand...
Click to collapse
Understood and Thanks a lot!!!:good:
that means all in all,
I still have to go through
the route of "Backup all --> Flash Stock & unroot --> Root --> Restore all".
However, considering the latest update seems don't have anything important or useful to me
So I just wait for the next more important update.
and save the drudgery next time.
vinny86 said:
Use the wugs toolkit and go back to fully stock ROM, re lock the bootloader.
Only then will you be able to apply the OTA update.
backup your app data using titanium backup.
Click to expand...
Click to collapse
He doesn't need to lock his bootloader, and he'll still not be able to run the update the natural way as long as he's got twrp or cwm installed. He can flash the factory rom and push the update through using custom recovery though.
Visa Declined said:
There is a modified version of the update that someone made. It doesn't perform the system checks that cause so many peoples devices to fail. If you can't run the update because you changed or deleted a system apk, read this post: http://forum.xda-developers.com/showpost.php?p=32752631&postcount=20
Don't run this if you're just not sure of why your update is failing.
Click to expand...
Click to collapse
Thanks for you advise,:highfive:
it is very kind of you to help.
I think may be the Status 7 error could be caused by the Custom Kernel Installed (poitee)
I better ask him in detail later on.
But mine is JRO03S,
May be it is safer to Return to Stock Rom completely and go for OTA later.
Sadly, This 4.1.2. seems got no very useful component to me,
I solely use it as a second PDA and Music Player with USB DAC.
I will have to wait for better solution then.....
pleaseabcd said:
However, considering the latest update seems don't have anything important or useful to me
Click to expand...
Click to collapse
The latest update allows you to boot into recovery mode without being plugged into usb. Now, if I get stuck in a bootloop, I don't have to look for something to plug my device into to restore. This feature alone is worth whatever hassle one may have to do to update.
Visa Declined said:
The latest update allows you to boot into recovery mode without being plugged into usb. Now, if I get stuck in a bootloop, I don't have to look for something to plug my device into to restore. This feature alone is worth whatever hassle one may have to do to update.
Click to expand...
Click to collapse
O'really.....em...then it is a different story..(Safer for the future...)
Perhaps, I just:
1. use Titanium Backup to back up everything --> copy the "Back up" to PC (just in case)
2. use Wugfresh Nexus Root Toolkit 1.5.4 to Flash Stock n Root
3. if can Flash to 4.1.2 stock rom directly, OK
4. if can't --> flash back to 4.1.1 stock rom (JRO03S) and then OTA
5. Finally, use Titanium backup to restore Everything.
Have to Thank You you guys again!
I know I am a newbie... but I am learning......
Hate to be limited to what I was given......while I can experiment and make mistake to grow up !:laugh:
Hey everyone,
I put a stock image of 4.3 on my phone - T Mobile to remove root, update to 4.4.2; then realized that it's really not worth the issues I'm dealing with in customizing the phone. I really regret doing this!!! I have no idea how to roll it back because when I do so in odin 3.07 or 3.09 with UVUEMK2 I have to reflash the "stock boot img" in order to get my S4 back alive as trying to roll it back that way "FAILS" in odin and breaks the stock boot and the phone asks me to plug it in and use kies to troubleshoot; when I just flash the bootloader and it's fine again.
ULTIMATELY:
1- Can ANYONE tell me how I can roll it back to 4.3 until I JUMP to my S5 in April?
2- If not how does one go about removing - ROOT - by Chainfire or CF-AutoRoot?
=> so I can at least trade in my phone for the 5 and be done with this mess in a month.
Reason I want 4.3 is because I had much more control over the system and was able to perform tethering tasks and APN tricks that have been blocked by the Kitkat update.
Thank you to whomever has the capacity to help me I've spent all day trying to figure it out and I have a 4 page grad paper I'm postponing because I gotta figure this out first, for some apparent reason. So any help APPRECIATED!!
I may be giving you bad news but last time I checked the ota notice said you cannot roll back ... I have yet yo see anyone roll back from KitKat official on the 9500
The new boot loader is pretty persistent at rollback prevention.
Sent from my Nexus 4 using Tapatalk
How about in terms of Unrooting? CF-Autoroot has the option in SuperUser app to unroot. I'm guessing this will do the trick for when I hand the phone back over to T-Mo? Or have they added things to circumvent removing SU?
I basically don't want to do it now (Figure out how to unroot) if I don't have to quite yet.
Gillion said:
I may be giving you bad news but last time I checked the ota notice said you cannot roll back ... I have yet yo see anyone roll back from KitKat official on the 9500
The new boot loader is pretty persistent at rollback prevention.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
zz1049 said:
Hey everyone,
1- Can ANYONE tell me how I can roll it back to 4.3 until I JUMP to my S5 in April?
2- If not how does one go about removing - ROOT - by Chainfire or CF-AutoRoot?
=> so I can at least trade in my phone for the 5 and be done with this mess in a month.
Reason I want 4.3 is because I had much more control over the system and was able to perform tethering tasks and APN tricks that have been blocked by the Kitkat update.
Click to expand...
Click to collapse
Once you have installed 4.4.2 with the matching boot loader, you cannot install 4.3 with Odin. However you can restore an Nandroid backup of your old 4.3 setup from recovery, so the phone will be back to how it was before the upgrade.
If you want to unroot, you can fire up SuperSU and select the "Full Unroot" option from the settings tab.
In order to restore APN settings on 4.4.2, I have always taken a backup of them on earlier versions using this great app:
https://play.google.com/store/apps/details?id=com.riteshsahu.APNBackupRestore
In order to make it work on 4.4.2, you move the APK from /Data/App to /System/priv-app using Root Explorer or similar, then reboot. Disable the ICS check in the settings section of APNBackupRestore, and you're good to go!
For tethering by USB, this works very well for me:
https://play.google.com/store/apps/details?id=com.koushikdutta.tether
Good Luck!
Nandroid recovery
Hi VogonP0et,
I have a Sprint S4. I also upgraded OTA to 4.4.2 and am regretting it. I was not rooted when upgrading. Haven't been rooted for a few months. I do not like 4.4.2 restrictive sd card. Screwed up my Doc's to Go and Sygic nav.
I do have a nandroid recovery back up from last summer. MDL i believe.
Do I understand you correctly, I can root 4.4.2 reinstall TWRP. Then do a recovery back to my earlier version. Is this correct?
Thanks in advance.
Jim
Clean install rooted 4.4.2
BrickBait said:
Hi VogonP0et,
I have a Sprint S4. I also upgraded OTA to 4.4.2 and am regretting it. I was not rooted when upgrading. Haven't been rooted for a few months. I do not like 4.4.2 restrictive sd card. Screwed up my Doc's to Go and Sygic nav.
I do have a nandroid recovery back up from last summer. MDL i believe.
Do I understand you correctly, I can root 4.4.2 reinstall TWRP. Then do a recovery back to my earlier version. Is this correct?
Thanks in advance.
Jim
Click to expand...
Click to collapse
Hi Jim
You can only restore a 4.3 or 4.4.2 backup, not an earlier version.
I have an International i9505 jfltexx, although I believe the process would be the same for you. Here's what I did:
- Nandroid backup to the external SD card first job! Copy to the PC for safety.
- Power off the phone, and manually re-start in Download mode.
- Flash original factory KitKat 4.4.2 firmware of choice using Odin (I used V3.09), which will include the matching boot loader.
- Allow the phone to start up, which will take some time.
- Power off the phone, and manually re-start in Download mode.
- Use Chainfire's CF-Auto-Root to root it, using the Odin that comes in the package. Find it here (3rd post):
http://forum.xda-developers.com/showthread.php?t=2219803
- phone will re-start when the process is complete
- I did a full wipe at this point, and although it's a bit of a pain to restore all your data with Titanium backup it gives a problem-free start.
- Full wipe made my Sygic work properly again!
- Before you drop in a custom recovery, it is a good idea to use Chainfire's Triangle Away to reset the flash counter. It seems that the Flash Counter needs to be zero for successful operation of Mobile Odin in future.
https://play.google.com/store/apps/details?id=eu.chainfire.triangleaway
- once you have set up your Google Play account, download SGS4Flasher here:
https://play.google.com/store/apps/details?id=nl.bvgemert.flasher
- SGS4Flasher will drop in the recovery of your choice. I use and recommend TWRP personally.
- You're good to go, and Flash Counter is still zero!
- Now you can restore an earlier Nandroid backup of a 4.3 ROM, or install a new custom 4.3 or 4.4.2 ROM
After this I installed the custom ROM of my choice, which is Echoe V16 based on 4.4.2. Echoe makes all the limitations and restrictions of 4.4.2 go away, but there must be a custom ROM suitable for you. I don't think you can use Echoe on your phone, but you may have a favourite. I have to say that doing the full wipe was an important step to make it all work well, so worth the hassle.
The only concern I have is that your backup at version at MDL may actually be Android 4.2, which I don't think you can use directly. However Titanium Backup can extract the data from a Nandroid backup to restore. I have spent quite a bit of time understanding the 4.4.2 limitations and restrictions, and found ways to make it do what I want now. Overall I'm happy, but it has taken some time to get there.
Good Luck!
I'm getting my P8 tomorrow and have some concerns:
I definitely gonna root it, i know how to do (write E-Mail to Huawei), but is it possible to unroot and go back to 100% stock? With stock Recovery and such?
Maybe there's something like an "Stock Firmware" Image i could use in order to get back to stock?
Thanks.
Hi guys
Firstly thanks to everyone who contributes on here you have been great!
I have been trawling the web and cannot find a definitive answer to wanted to see if anyone can help
I rooted my moto x style and have twrp. I want to set it back to stock as ibhave someone who wants to buy it.
Is it possible to reset fully to stock including a full wipe ( flashing doesn't seem to clean everything)
How do I relock the bootloader...and get rid of that God awful annoying message?
bdt1978 said:
Hi guys
Firstly thanks to everyone who contributes on here you have been great!
I have been trawling the web and cannot find a definitive answer to wanted to see if anyone can help
I rooted my moto x style and have twrp. I want to set it back to stock as ibhave someone who wants to buy it.
Is it possible to reset fully to stock including a full wipe ( flashing doesn't seem to clean everything)
How do I relock the bootloader...and get rid of that God awful annoying message?
Click to expand...
Click to collapse
You can search this thread to relock the boot loader. However it will not relock the bootloader completely it will set the Phone status to 2.
http://forum.xda-developers.com/moto-x-style/help/how-relock-bootloader-t3207771
To remove the annoying message while you but up you can try
http://forum.xda-developers.com/mot...o-remove-unlocked-bootloader-warning-t3201141
Received this yesterday evening and am wondering if anyone has a good idea of what this update entails. It states is security patch and stability fix, if I'm not mistaken. Probably just a regular non-major update, then?
I am in the middle of returning my tab back to stock to then update to this update... Will report back in a while. @all
If you have unlocked your bootloader to use a custom recovery DO NOT UPDATE. It will soft brick!!! I tried in vain and am having to resort to 'back to stock' as, like a pleb, I don't backup before I tinkered
Sent from my SM-G901F using Tapatalk
I happens to the best of us, man. Sorry to hear. I'm currently not rooted, but at some point will, so that possibility of messing up will ALWAYS be there.
i have just updated my yoga 830LC. But i forgot my bootloader is unlocked. It's soft brick. Can you help me how to back to stock Lollipop ROM. please help me! thanks
Do you have a backup? When I first tried to update I think it did update part of the rom. I reflashed the patched esp (which you should still have if you have unlocked you boot-loader)
It then let me in to recovery and to restore.
Try that and report back
Sent from my SM-G901F using Tapatalk
Hi. I have this update from lenovo too, my 1050F is rooted, how I do a backup ? and you flash which stock rom, before upgrading ?
If possible, I want to keep my data.
Thank you.
I think the only way to keep you data is with something like Titanium backup saved to an external source and then whenever the update is finished re-root and restore selected backed up data
If you have unlocked you boot-loader you must have flashed a customers recovery. I did a twrp back up and selected what I want to restore.
Edit - get the files you need from this post
corasman said:
Hi Rob
These files I copied from various threads on here.
They are on my g/drive,if they are any good to you or anyone else.
http://tinyurl.com/zdr92pf
http://tinyurl.com/zmmaww5
http://tinyurl.com/zgt7sjo
http://tinyurl.com/hjy4kks
http://tinyurl.com/jhrjscj
Click to expand...
Click to collapse
Sent from my SM-G901F using Tapatalk
I have the 8 inch version of this tablet (830F) and received a similar update notification.
I just used the temp recovery trick to root and disable some bloat but left it otherwise stock. The tablet is currently in the process of backing up with temp TWRP and I was thinking of unrooting and giving this update a shot.
But it's not worth losing root over it...
Did anyone apply the patch in the meantime? Were you able to root again?
Thanks.
Yeah I have rooted, unlocked the boot-loader and flash twrp... All is good.
Have you flashed the patched boot-loader? If so you will need to flash the stock 830F ROM
Soft Brick
I'm just leaving my experience in case anyone does the same mistake as I.
I tried to use de "Hide root" option of SuperSu before upgrading, I have a locked bootloader, so I thought that it would be enough but I well... it didn't even boot after de lenovo screen
So I had to returno to stock, after reading what other peole did I manage to finally flash it back to stock lollipop.
I download this stock rom from lenovo-forums.ru
1050f_s100196_151123_row_lос-50
Click to expand...
Click to collapse
[As rookie, cannot post links :silly:]
Before flashing, the flash.xml has to be edited. Find
<string>fastboot flash system $system_file</string>
Click to expand...
Click to collapse
and add -s 1G to the command
<string>fastboot -S 1G flash system $system_file</string>
Click to expand...
Click to collapse
Then, enter on bootloader mode. I did it from de Recovery Mode (PWR on, and after de "lenovo" press both volume keys)
And just flash it with Phone Flash Tool
Everything it's probably pretty obvious for many of you but I leave this here for noobies like me! :victory:
Thank you 69PerTTu69.
Did you have keep your data partition?
I have understood you have only install system partition. Right ?
If so, I Will try to use your method.
Sounds good. No I only have the temp twrp bootloader pushed from the pc. Untethered it is stock but it's rooted. I'll revert that tomorrow and give this a shot. Cheers.
-beluga- said:
Sounds good. No I only have the temp twrp bootloader pushed from the pc. Untethered it is stock but it's rooted. I'll revert that tomorrow and give this a shot. Cheers.
Click to expand...
Click to collapse
I have a new 1050F which has finished churning through all the updates to get it from KitKat.
It is now at the level of this update (..S100256_160119..)
I was about to root following the "[HOW TO] Root Yoga Tablet 2 [STEP-BY-STEP] [NOOB FRIENDLY]" 1st post instructions by AndroMAN (which uses a temporary pushed recovery) but I'm now a little concerned since that will put me in exactly the position of you -beluga-.
I'd be grateful if you could let me know how you get on (or if anyone else can comment on whether attempting to root this way is now a bad idea)
-beluga- said:
Sounds good. No I only have the temp twrp bootloader pushed from the pc. Untethered it is stock but it's rooted. I'll revert that tomorrow and give this a shot. Cheers.
Click to expand...
Click to collapse
Ok, this was a success -
1. Unroot through the SU app (just to be safe)
2. Restart
3. Apply the update through the regular system/settings UI and wait for it to finish
4. Re-root as before (using IntelAndroid-FBRL-07-24-2015 and BETA-SuperSU-v2.67-20160121175247)
Keep in mind that I was on stock bootloader and didn't alter much besides disabling crapware. Deeper modifications may cramp your style.
Cheers
---------- Post added at 12:18 PM ---------- Previous post was at 12:17 PM ----------
dingers01 said:
I have a new 1050F which has finished churning through all the updates to get it from KitKat.
It is now at the level of this update (..S100256_160119..)
I was about to root following the "[HOW TO] Root Yoga Tablet 2 [STEP-BY-STEP] [NOOB FRIENDLY]" 1st post instructions by AndroMAN (which uses a temporary pushed recovery) but I'm now a little concerned since that will put me in exactly the position of you -beluga-.
I'd be grateful if you could let me know how you get on (or if anyone else can comment on whether attempting to root this way is now a bad idea)
Click to expand...
Click to collapse
Yes, this worked fine. See my other follow up post. Good luck.
saupiquet said:
Thank you 69PerTTu69.
Did you have keep your data partition?
I have understood you have only install system partition. Right ?
If so, I Will try to use your method.
Click to expand...
Click to collapse
Sorry for the delay, but no. Everything within the internal storage will be lost.