I recently got another MT4G and went through the whole downgrading to froyo and rooting process. Its now has CM7 and the latest Clockwork recovery on it. While I was on froyo I forgot to Sim unlock the phone. What will I have to do to Sim unlock now that im back on 2.3.7? Do I have to downgrade again for the gfree unlock method to work?
Easy option: Call TMo and get unlock code by giving your IEMI. They will email it to you within a week.
Hard option: You guessed it, you have to downgrade.
Errr if you posted this 2days ago I would have gave you all you needed. Since I cleaned my MediaFire account and deleted master S2.2.1FY backup. Which included all you needed to root.
Best advice I can give you now is do a full nandroid backup of 2.3.7GB and do total system wipe. Then download stock nandroid backup if any is still valid in Dec sec due to file sharing sites restricting public download. Then just gfree unlock it and once verified then do wipe again and restore 2.3.7GB nandroid. If you had my backup it would take 2min max to finish it :O now it might take you 10min or so max.
I need the unlock soon so my better option would be to do it myself with a downgrade. Does it just have to be a froyo rom or does it have to be a stock restore that will change my recovery and everything back to stock?
Most of the eMMc write protection exploits for our device works on 2.2.1FY. You can keep your current CWMR as that will save your life after unlock is done with simple nandroid 2.3.7GB restore. But answer is no to reverting stock recovery.img as it plays no roll.
1) Find and download stock SFY2.2.1-nandroid, gfree, VISIONary+.
2) Nandroid backup current GB2.3.7GB, do system wipe + format /system. Then restore stock Sense2.2.1FY nandroid.
3) Load into 2.2.1 and just do simunlock flag and verify it worked on bootloader.
4) Once again do total system wipe + format /system. Then restore GB2.3.7-nandroid.
NOTE: You might also want to download basic file manager + terminal. As on stock you won't have it installed. So adb install it and make sure from settings untrusted source is enabled.
Thank you sir!
I downloaded the PD15IMG from this link here...
http://forum.xda-developers.com/showthread.php?t=1178912
It loaded me up to the stock room and kept my S-Off but I lost root.
I then used visionary to root the rom again with no problems and then I was able to proceed with unlocking through g-free.
Related
If you haven't already done so, install Rom Manager and flash Clockworkmod Recovery. It doesn't replace the actual recovery partition or the files that restore it so it won't affect flashing the update.
If you received an OTA notice don't flash it. You can go into /system/cache and copy it, or download it from the links in other threads. Place the update zip (no need to rename it) on the root of your sd card.
To install the update you must be fully stock (root is okay). That means any changed or deleted system files (including bootanimation.zip) will prevent the update from flashing. You will get a status 7 error. If you used Bloat Freezer you must defrost all before flashing the zip or it will error.
Also, have available whatever zip you used to root your Nexus one (i.e., su.zip or superboot, etc.) and put on the root of your sd card.
Once your system is back to stock reboot into CWM recovery and select flash zip from sd card. Then flash the 2.3.6 update file. Then DO NOT reboot yet. Now flash your root zip. After you have flashed both the udpate and the root zip you can reboot your phone. No need to wipe anything.
When your phone reboots you will have 2.3.6 and it will still be rooted. No bootloader gymnastics necessary.
I am using stock (almost) version of GRJ22 , but unfortunatelly I got the status 7 error when I tried to apply the update via clockworkmod recovery. I guess that's because I have already integrated some system apps into ROM using Titanium Backup.
So, if I flash stock vanilla GRJ22, then SU, then GRK39F (the incremental update) and finally SU again, won't that do the job??
Thanks..
Nikos_s3 said:
I am using stock (almost) version of GRJ22 , but unfortunatelly I got the status 7 error when I tried to apply the update via clockworkmod recovery. I guess that's because I have already integrated some system apps into ROM using Titanium Backup.
So, if I flash stock vanilla GRJ22, then SU, then GRK39F (the incremental update) and finally SU again, won't that do the job??
Thanks..
Click to expand...
Click to collapse
Yes, that will do nicely. Just need to get back to GRJ22 stock before you can flash the udpate. The updater-script does an assert and checks the md5 checksum of every system file before it allows the update to flash. If it doesn't find all stock files or checksums don't match what it is looking for, you get a status 7 error and the line above will show which file it stopped on. So you can look at those messages and keep restoring files it wants (if only a few) without having to flash completely back to stock.
I guess that would take much time, as almost all of my google apps are integrated into ROM...so I will try to follow the procedure I wrote earlier and if that won't work, I will try a ready stock,rooted ROM (Fireb33 has done it already)..
thanks mate..
Why so complicated?
You can update to 2.3.6 AND keep root even much more simple:
1.) Update from OTA to 2.3.6 (and loose root).
2.) Flash Superboot from Madaco and get back root.
Done in 3 minutes.. No need to flash, recover, overwrite and/or whatever, no need for ADB, no messing:
Code:
https://bexton.net/2011/09/24/root-access-for-nexus-one-on-android-2-3-6-grk39f-superboot/
Bexton said:
You can update to 2.3.6 AND keep root even much more simple:
1.) Update from OTA to 2.3.6 (and loose root).
2.) Flash Superboot from Madaco and get back root.
Done in 3 minutes.. No need to flash, recover, overwrite and/or whatever, no need for ADB, no messing:
Code:
https://bexton.net/2011/09/24/root-access-for-nexus-one-on-android-2-3-6-grk39f-superboot/
Click to expand...
Click to collapse
That's only for those who have the bootloader unlocked?
_raz_ said:
That's only for those who have the bootloader unlocked?
Click to expand...
Click to collapse
Well, yep. That method indicates your (phones) bootloader is unlocked. But as it's the N1, unlocking the bootloader is just 19 (up to 25) characters away -> "fastboot(-linux) oem unlock".
Edit: By the way, i looked up that post from an android platform engineer:
Code:
groups.google.com/group/android-platform/msg/b7d83992dd92accb?dmode=source
The N1 is just made for that.
tried superboot but wifi down
I flashed the update for 2.3.6 and then superboot but my wifi gives an error when I try to turn it on.
New Superboot file for GRK39F?
Is there a new Superboot file for the new OTA update?
jboxer said:
If you haven't already done so, install Rom Manager and flash Clockworkmod Recovery. It doesn't replace the actual recovery partition or the files that restore it so it won't affect flashing the update.
If you received an OTA notice don't flash it. You can go into /system/cache and copy it, or download it from the links in other threads. Place the update zip (no need to rename it) on the root of your sd card.
To install the update you must be fully stock (root is okay). That means any changed or deleted system files (including bootanimation.zip) will prevent the update from flashing. You will get a status 7 error. If you used Bloat Freezer you must defrost all before flashing the zip or it will error.
Also, have available whatever zip you used to root your Nexus one (i.e., su.zip or superboot, etc.) and put on the root of your sd card.
Once your system is back to stock reboot into CWM recovery and select flash zip from sd card. Then flash the 2.3.6 update file. Then DO NOT reboot yet. Now flash your root zip. After you have flashed both the udpate and the root zip you can reboot your phone. No need to wipe anything.
When your phone reboots you will have 2.3.6 and it will still be rooted. No bootloader gymnastics necessary.
Click to expand...
Click to collapse
I want to update to gingerbread and looking for the proper guidance going forward. I've done some looking around the forums but i'm still unclear if i need to unroot or install a stock build, etc. What i know is the phone is rooted and sim unlocked. How can i check to see if the bootloader is open/locked?
Current specs:
android version 2.2.1
Baseband 32.41.00.32U_5.08.00.04
Kernal Version 2.6.35.9-cyanogenmod
Mod Version: Cyanogenmod-6.1.1-N1
Build: FRG83D
edit:
Please treat me like an idiot and walk me through this process. It's be utterly frustrating and I'm a stone's throw away from busting out my Nokia 3390 (equipped with led disco keypad).
If your bootloader is unlocked you will see an unlocked padlock on the boot up screen...
This guide is strictly for people who have a Verizon R800x and wants to update to Gingerbread 2.3.4 with root and ClockworkMod recovery, without having to unlock the bootloader nor have a Verizon data plan. Without a data plan you can not update the Verizon Play from 2.3.3 to 2.3.4 because they don't allow updating through WiFi. Also if you flash the 2.3.4 ftf image directly, you will not be able to root it, therefor will not be able to install CWM unless you unlock the bootloader. This guide show you to will get around that.
Note: With this method, although you have CWM, you still will not be able to install custom roms and kernels until you unlock the bootloader. This guide was written before Sony allow the Verizon Play bootloader to be unlocked from their site. Go here to unlock your bootloader, which will allow you to flash custom roms and kernels to your Play: http://unlockbootloader.sonymobile.com. If you choose to do this, you can skip this entire guide.
Instructions:
1. You must be running Gingerbread 2.3.3 on your R800x. If you aren't, download the stock Gingerbread 2.3.3 firmware and use Flashtool to flash it. Drag the ftf firmware file onto the Flashtool screen and follow the onscreen instruction to install. This step will wipe all your phone data except the SDcard.
(You might need to install drivers for your device first, you can find "Flashtool-drivers.exe" in the "drivers" folder in your Flashtool folder.)
2. Enable "USB debugging mode" on your device (Settings -> Applications -> Development).
3. Use SuperOneClick created by CLShortFuse to root your R800x. Then reboot the phone.
(This program might trigger a false positive on your antivirus software, so disable your antivirus while using it. This rooting method only work with Gingerbread 2.3.3 for the Play.)
4. Use specifically the "CWM installer v5" created by pvyParts to install ClockworkMod. That's version 5 btw.
Note: At this point, if you are content with using GB 2.3.3 with root and CWM, stop here. Proceed if you want to update to 2.3.4 with root.
5. Download either the "nandroid backup of stock Gingerbread 2.3.4 w/ root" created by netizenment or this NXT Lite CDMA rom which is already debloated and optimized.
(Put the nandroid backup into the correct directory in your microSD card so ClockworkMod will recognize it, it should be extracted into a folder named "backup" within a folder named "clockworkmod".)
6. Boot the phone into ClockworkMod recovery by: Turning it on, when the Sony logo appear, keep pressing the Volume Down button until you see the blue ClockworkMod menu appear.
7. Restore the stock GB 2.3.4 nandroid backup you just downloaded. Then turn off the phone.
(This will only install the system files, it will not install the 2.3.4 kernel.)
8. Installing the stock 2.3.4 kernel:
a. Download the stock Gingerbread 2.3.4 firmware (this is for Verizon only).
b. Drag and drop the ftf onto the Flashtool window. When you see the "Firmware selection" window appears, look to the right column, under "Exclude" and check to exclude all the items in the list, except the kernel. Then flash it.
(This will install just the 2.3.4 kernel while leaving the rest of your rooted Gingerbread 2.3.4 alone. You need to do this for the Camera and WiFi to work.)
9. In the process of restoring the nandroid backup above, the ClockworkMod recovery might become lost. However, you still have root, so you can install ClockworkMod recovery again using the CWM installer.
Other tips: LBE Security Master have can help lighten the bloatware from your rom. Among its many features, can remove system apps and prevent apps from autostarting, which will leave more free rams.
The end.
does this fix the "gtalk" issue, I went back to 2.3.3 from 2.3.4 cause of that issue.
CamachoDjr said:
does this fix the "gtalk" issue, I went back to 2.3.3 from 2.3.4 cause of that issue.
Click to expand...
Click to collapse
It doesn't fix it. Verizon does this sort of thing on purpose. Pushes out a broken update and then goes, "We are working on a fix."
I am sorry if this is a dupe of other threads but I couldn't find a complete answer to my problem anywhere else.
I have a nexus 7 (2012), on stock 4.4.2, unlocked bootloader (i think, unlocked padlock on startup).
I want to root. I gather this will not wipe? (or will it?) and what tool should i use? I already have N7 toolkit and android sdk, so i can use that most easily, otherwise any other program needed is fine. I want to use stock bootloader and stock rom and ensure ota updates will occur. (i understand i may lose root through ota updates, but i assume i can just reroot as i have unlocked the bootloader?)
Thanks
Since your tab has already gone through the bootloader unlocking process, there is neither a need nor a requirement to wipe the device.
And since you want to stay as close to Stock as possible, you can even "root" without ever flashing a recovery: you just soft-boot a recovery image rather than flashing one. That is - "fastboot boot (...etc)" instead of "fastboot flash (...etc)". That allows you to use a custom recovery every once in a while while leaving a stock recovery on the tablet. That preserves maximum compatibility with future OTAs.*
And with that soft-booted recovery, immediately take a Nandroid backup including the Stock recovery (which is still on the tablet because you soft-booted the recovery you are using). In the same session, use "adb pull" to get a copy of your 100% pure-stock Nandroid backup off the tablet. (Make sure you name it clearly so you will know exactly what it is 12 or 24 months later)
Finally, use a flashable .zip installer package for SuperSU to "flash root".
After an OTA, you can just reinstall root by soft-booting a custom recovery and using the same (or updated) flashable .zip installer method for reinstalling SuperSU. And just like above, capture a new 100% pure-stock Nandroid backup (including the new stock recovery) *before* re-rooting.
This strategy allows you to roll back to any version of stock you please at any time in the future.
good luck
* flashaholics prefer to have a recovery hard-flashed on their device so they can flash things on a whim, wherever they are. The approach here is a bit more restrictive as you have to have a PC handy in order to soft-boot a recovery in order to do any flashing. I would say that the biggest limitation of this approach is that it tends to reduce the number of Nandroid backups of your ROM personalization.
Backup are a good thing. You can always throw them away later, but you can't create a missing one that is urgently needed.
Hello,
I installed KANGAPOP v2.5★|►LOLLIPOP GPE (5.0) while on GOLDFINGER v9 (4.4.2). Then everything was just fine before I had my corporate account linked to it which required device to be encrypted. I did that and since then the phone is stuck in boot loader loop (four balls are playing around!). Waited for 5-6 hours before rebooting the device. Had the Nandroid backup for old ROM but when I entered TWRP it was not able to mount /data (may be due to encryption). I am not sure which bootloader I am in but some help is suggesting to install I337UCUAMDL_I337ATTAMDL_ATT via Odin by following guide here,
http://forum.xda-developers.com/showpost.php?p=56453100
But this guide reads,
Who SHOULD NOT use this guide?
-- SGH-I337 users with a MDB or MDL bootloader. (Don’t use this guide or you’ll be locked down for good.)
Not use MDL! I am confused and asked to post here. Few questions I've.
1. Since I only have access to TWRP (without /data and may be some other partitioin), Is there a way to see which bootloader my phone is on right now?
2. Rather than going through ODIN is there a way to decrypt the partition and restored the phone via TWRP?
3. If I had to go through ODIN then what stock version should I use and where can I get one?
I know I made a really bad mess out of it but need solution to get the phone back working. I am seating on the 4th day to dead phone, and it needs life.
raone26 said:
Hello,
I installed KANGAPOP v2.5★|►LOLLIPOP GPE (5.0) while on GOLDFINGER v9 (4.4.2). Then everything was just fine before I had my corporate account linked to it which required device to be encrypted. I did that and since then the phone is stuck in boot loader loop (four balls are playing around!). Waited for 5-6 hours before rebooting the device. Had the Nandroid backup for old ROM but when I entered TWRP it was not able to mount /data (may be due to encryption). I am not sure which bootloader I am in but some help is suggesting to install I337UCUAMDL_I337ATTAMDL_ATT via Odin by following guide here,
http://forum.xda-developers.com/showpost.php?p=56453100
But this guide reads,
Who SHOULD NOT use this guide?
-- SGH-I337 users with a MDB or MDL bootloader. (Don’t use this guide or you’ll be locked down for good.)
Not use MDL! I am confused and asked to post here. Few questions I've.
1. Since I only have access to TWRP (without /data and may be some other partitioin), Is there a way to see which bootloader my phone is on right now?
2. Rather than going through ODIN is there a way to decrypt the partition and restored the phone via TWRP?
3. If I had to go through ODIN then what stock version should I use and where can I get one?
I know I made a really bad mess out of it but need solution to get the phone back working. I am seating on the 4th day to dead phone, and it needs life.
Click to expand...
Click to collapse
If you don't get any help soon you could just flash the stock firmware and that usually takes care of soft bricked phones.
Sorry if this didn't help!
I found only one way to root the galaxy s7 edge but it includes erasing everything and thats just too much trouble for me since i don't trust backup apps with my apps data and all
my model is sm-935FD
this the method i found :
https://youtu.be/nlj76YvxGYo
thank u
You don't need to erase everything, that is complete horses**t.
First off you need to confirm you have the Exynos international version. If you're on the Snapdragon version, you're s**t out of luck as the bootloader is locked and root isn't possible at this time, nor will it likely ever be.
You then have two option, install CF Autoroot from ODIN and leave your recovery as stock. Or install TWRP over your recovery via ODIN and install SuperSU from a zip file from within TWRP. Either way you won't lose data. See the following threads.
CF Autoroot -- http://forum.xda-developers.com/s7-edge/development/sm-g935-exynos-cf-auto-root-t3337354
TWRP - http://forum.xda-developers.com/s7-edge/development/recovery-official-twrp-hero2lte-3-0-0-0-t3334084
You only need to erase everything if you want to flash custom roms in twrp. Otherwise you can just root with cf autoroot and you're all set
As the others said, flashing cf autoroot in odin won't erase anything, will leave your phone as is and will add supersu.
You should be aware that by rooting you will trip the knox flag, which permanently breaks samsung pay, and will break the following stuff on the stock rom: private mode, secret mode in the browser with fingerprint authentication (which can later be fixed by flashing a custom Rom).
If you want a properly working twrp recovery, you will have to erase everything, including the internal storage of the phone, there is no way around it.
If you absolutely must have root and you're into custom roms then I say do it now, if you're OK with the stock firmware I would advise not to root. This phone doesn't have too much development and you should not expect too many custom ROMs. I personally regret rooting.
I'm erase mi data because I want to do twrp backups, if you don't want to use a custom recovery for flash Roms and use a nandroid only flash supersu.
Beefheart said:
You don't need to erase everything, that is complete horses**t.
First off you need to confirm you have the Exynos international version. If you're on the Snapdragon version, you're s**t out of luck as the bootloader is locked and root isn't possible at this time, nor will it likely ever be.
You then have two option, install CF Autoroot from ODIN and leave your recovery as stock. Or install TWRP over your recovery via ODIN and install SuperSU from a zip file from within TWRP. Either way you won't lose data. See the following threads.
CF Autoroot -- http://forum.xda-developers.com/s7-edge/development/sm-g935-exynos-cf-auto-root-t3337354
TWRP - http://forum.xda-developers.com/s7-edge/development/recovery-official-twrp-hero2lte-3-0-0-0-t3334084
Click to expand...
Click to collapse
Glad I came across this thread, as I was having the same thoughts. How easy is it to just flash recovery back to stock? or do you need to flash the complete firmware package?
TwinCalibre said:
Glad I came across this thread, as I was having the same thoughts. How easy is it to just flash recovery back to stock? or do you need to flash the complete firmware package?
Click to expand...
Click to collapse
Flashing the whole fw of course 1 of the way. Maybe if we can extract stock recovery from the fw then just odin it?.
Sent from my SM-N920C
if your on nougat and try to flash TWRP, your device wont boot....they dont have a decrypt solution to 7.0 right now.
Beefheart said:
You don't need to erase everything, that is complete horses**t.
First off you need to confirm you have the Exynos international version. If you're on the Snapdragon version, you're s**t out of luck as the bootloader is locked and root isn't possible at this time, nor will it likely ever be.
You then have two option, install CF Autoroot from ODIN and leave your recovery as stock. Or install TWRP over your recovery via ODIN and install SuperSU from a zip file from within TWRP. Either way you won't lose data. See the following threads.
CF Autoroot -- http://forum.xda-developers.com/s7-edge/development/sm-g935-exynos-cf-auto-root-t3337354
TWRP - http://forum.xda-developers.com/s7-edge/development/recovery-official-twrp-hero2lte-3-0-0-0-t3334084
Click to expand...
Click to collapse
Have anyone tried and successfully done it?
there are many ways to root
I recommend use TWRP to root with SU apk file
Beefheart said:
You don't need to erase everything, that is complete horses**t.
First off you need to confirm you have the Exynos international version. If you're on the Snapdragon version, you're s**t out of luck as the bootloader is locked and root isn't possible at this time, nor will it likely ever be.
You then have two option, install CF Autoroot from ODIN and leave your recovery as stock. Or install TWRP over your recovery via ODIN and install SuperSU from a zip file from within TWRP. Either way you won't lose data. See the following threads.
CF Autoroot -- http://forum.xda-developers.com/s7-edge/development/sm-g935-exynos-cf-auto-root-t3337354
TWRP - http://forum.xda-developers.com/s7-edge/development/recovery-official-twrp-hero2lte-3-0-0-0-t3334084
Click to expand...
Click to collapse
In nougat it will disable access to data folder and force you to format, but if you flash stock firmware nougat the same it was in and reboot it everything was like before.
Basically backup everything using non root apps and adb then format then restore.
Today I accidentally did oem unlock to OFF then rebooted and then it said custom binary blocked by frp. I then flashed many nougat versions but they all caused force close of 2 things ims service and srbg? I ended up flashing nougat from January 2017 dqlc. I got everything back and working. Next I did twrp and supersu etc but data encryption failed. Then I flashed stock dqlc and got everything back. Use home csc or otherwise it will erase everything. Now I have to backup everything.
Beefheart said:
You don't need to erase everything, that is complete horses**t.
Click to expand...
Click to collapse
That's not horse**** at all. If your storage is encrypted (most of them are by default) then it will force you to format once you flash TWRP. I took ages of trial and error of flashing stock firmwares and bootloaders etc via Odin to get it all back as I couldn't afford wiping (even if I had backed up).
Anyone reading this thread and wanting to try it should be careful.
I also found no way to backup ALL apps and ALL their data & settings reliably without root (Helium gets only part of the job done) so I could not risk wiping and restoring. I have too many apps configured and fined tuned that I use regularly.
Sorry for necro, but I found out the hard way after being badly advised ...
mastabog said:
That's not horse**** at all. If your storage is encrypted (most of them are by default) then it will force you to format once you flash TWRP. I took ages of trial and error of flashing stock firmwares and bootloaders etc via Odin to get it all back as I couldn't afford wiping (even if I had backed up).
Anyone reading this thread and wanting to try it should be careful.
I also found no way to backup ALL apps and ALL their data & settings reliably without root (Helium gets only part of the job done) so I could not risk wiping and restoring. I have too many apps configured and fined tuned that I use regularly.
Sorry for necro, but I found out the hard way after being badly advised ...
Click to expand...
Click to collapse
And finaly do you find a way to restore your data after installing TWRP ?
By now I would hope your important data is 100% redundantly backed up.
Of all the things that can and do go wrong with rooting, data lose shouldn't even enter into the equation unless you really goofed up bad.
Only two types of data users, those who have lost data and those that will...
I consider any data on internal memory 100% expendable. A complete reload/restore takes me about 2 hours and that's without the luxury of rooting.
At any moment I'm (and you should be too) ready to do a factory reset regardless of the cause without critical data lose.
After two forced back to back forced reloads on my 10+ I learned my lesson.
Thanks Blackhawk for your explication
I am on the second part of user which have lost his data but only the configuration not the contact, photo, etc...
But without root they are plenty of data (configuration, autorisation, widget) which take very long time to "reinstall" and those data are not saved if you are not root. And sometime with root also. They are not important but the time to restore them is very long and use a phone without his custumization is very anoying.
That's why I'm loocking for a way to save it without root or root without loosing those data.
jameslevalaisan said:
Thanks Blackhawk for your explication
I am on the second part of user which have lost his data but only the configuration not the contact, photo, etc...
But without root they are plenty of data (configuration, autorisation, widget) which take very long time to "reinstall" and those data are not saved if you are not root. And sometime with root also. They are not important but the time to restore them is very long and use a phone without his custumization is very anoying.
That's why I'm loocking for a way to save it without root or root without loosing those data.
Click to expand...
Click to collapse
A clean wipe of all settings data means no misconfigurations or malware will survive.
Nuke em.
I'll see how well SmartSwitch does saving the home page next reload. If it screws up it will cost another reload... of course.
Only shortcuts/folders, Good Lock, One Handed Operation plus etc kill me with setup time but it's no big deal. I've gotten pretty adapt at it
Poweramp is completely, redundantly, backed up as that would take weeks to sort of recreate, a true nightmare... as it is now, it only takes a few minutes to do.
My music database has existed for over 15 years. I've lost count of the number of backup copies I have for it... plus the source CD/HDCDs.
Currently have 3 up to date copies to be expanded soon to 4.
Overkill for data backup is a good thing.