Here are some instructions for installing JesusFreke's modified recovery image. You have to install the modified recovery image before you can install modified firmwares. These instructions are simpler than the existing ones because they don't require the use of adb or telnet.
Firstly, you need to already have firmware version RC29 or RC7. To check which version you have go to "Settings" and then "About phone". At the bottom you will see a "Build number" which will include "RC" and then a number. If you have RC30 or RC8 then you need to downgrade. THAT WILL WIPE ALL THE DATA/APPLICATIONS ON YOUR PHONE. Instructions for downgrading are here.
Now that you have RC29/RC7:
Download 'AndroidMod.zip' from one of the links in JesusFreke's post
Extract 'recovery_testkeys.img' from that zip and copy it to your SD card.
Download 'install.zip' which is attached to this post below.
Extract 'install' from that zip and copy it to your SD card.
Put the SD card in the phone or disconnect the phone if it is attached by USB.
Reboot the phone (switch it off and then on again).
When it has finished booting type the following at the home screen. It will start searching your contacts, but don't worry about that. Also, you won't see any visible sign that the first command worked. Just go ahead and type the second command straight afterwards:
cd sdcard<press enter>
sh install<press enter>
After a moment your phone should reboot itself. To check that the flashing worked, switch off the phone and then hold down the home key while you switch it on again. Keep the home key held down until you see the recovery screen (with the "!" triangle and the picture of the phone). Then press Alt+L on the keyboard and if you see "Using test keys" on the second line of text then the modified recovery image is installed and you can now install a modified firmware.
Cool! Thanks for that... much simpler... anyone else tried this yet?
I'm going to attempt all this later.
Phil
i just tried it and it works. confirmed.
great for beginners!
Hey tried it and it works!! Now how about one on restoring data after backup.
thanks for this just tryed it and worked first time.
First off thanks for all information here. Am I correct that after I downgrade to rc29 I then follow the instructions in this thread and then I can install jf 1.3 rc30. Or do I have this all wrong?
gottifour said:
First off thanks for all information here. Am I correct that after I downgrade to rc29 I then follow the instructions in this thread and then I can install jf 1.3 rc30. Or do I have this all wrong?
Click to expand...
Click to collapse
you are correct. once you have the modded recovery image, you can use jfs update zips.
korndub said:
you are correct. once you have the modded recovery image, you can use jfs update zips.
Click to expand...
Click to collapse
Sweet! Thanks for the reply. I will attempt this real soon. Do you have any suggestions before I begin? After I modify the firmware I will not get ota updates anymore right? Lets say the cupcake update, or any other for that matter, does come out. I would just have to wait untill a smarter person then me converts it to a new modified image to flash to my phone? Is that right? Thanks for any help. I'm sure this is probably the worng place to ask all of these questions. d
gottifour said:
Sweet! Thanks for the reply. I will attempt this real soon. Do you have any suggestions before I begin? After I modify the firmware I will not get ota updates anymore right? Lets say the cupcake update, or any other for that matter, does come out. I would just have to wait untill a smarter person then me converts it to a new modified image to flash to my phone? Is that right? Thanks for any help. I'm sure this is probably the worng place to ask all of these questions. d
Click to expand...
Click to collapse
in one of the zips from JF is an app that will REsign any update.zip, so when an ota comes you just have to wait for the update.zip to show up then you could REsign it with the dev keys, pretty easy, but it will probably show up pretty fast now that almost every G1 is probably running that keyset.
bhang
UPDATE..
Its working now...I wasn't doing it in the telnet client. I was just typing it in randomly and it didnt work that way for some reason.
Ok. I have downgraded to rc29 and copied the two images two my sd card. but I'm not sure if I even have root. When I try to change directory it doesnt happen. I have to have root by installing the modified rc29 right? I did type telnetd at the home screen and pushed enter. nothing happened. I know I'm missing something just not sure what yet? I did install the telnet client from the market as well. I'm not understanding something it appears. Anyone?
gottifour said:
UPDATE..
Its working now...I wasn't doing it in the telnet client. I was just typing it in randomly and it didnt work that way for some reason.
Ok. I have downgraded to rc29 and copied the two images two my sd card. but I'm not sure if I even have root. When I try to change directory it doesnt happen. I have to have root by installing the modified rc29 right? I did type telnetd at the home screen and pushed enter. nothing happened. I know I'm missing something just not sure what yet? I did install the telnet client from the market as well. I'm not understanding something it appears. Anyone?
Click to expand...
Click to collapse
use the telnet client to telnet to localhost. *then* you will have root. (note: that's only applicable for RC29. to get root on JFv1.3, just type su in terminal emulator).
To know if you have root access, check the prompt you get. if you get #, then you have root access. if you get $, you don't have root access.
JJC1138 said:
Here are some instructions for installing JesusFreke's modified recovery image.
Click to expand...
Click to collapse
well this is a big help for many people thank you for your addition
JesusFreke said:
use the telnet client to telnet to localhost. *then* you will have root. (note: that's only applicable for RC29. to get root on JFv1.3, just type su in terminal emulator).
To know if you have root access, check the prompt you get. if you get #, then you have root access. if you get $, you don't have root access.
Click to expand...
Click to collapse
I got the #
Thanks so much for everything so far..This is really awesome!!
gottifour said:
UPDATE..
Its working now...I wasn't doing it in the telnet client. I was just typing it in randomly and it didnt work that way for some reason.
Click to expand...
Click to collapse
Hi there. I just wanted to clarify that if you're following the instructions I posted then you don't need telnet.
gottifour said:
Ok. I have downgraded to rc29 and copied the two images two my sd card. but I'm not sure if I even have root. When I try to change directory it doesnt happen. I have to have root by installing the modified rc29 right?
Click to expand...
Click to collapse
No, you don't need the modified RC29 to do this. After you type the "cd sdcard<enter>" command nothing visible should happen. It works because the bug in RC29 which we are exploiting executes everything you type on a hidden root console, so the cd command works, but it just doesn't show you anything. Then you enter the second "sh install<enter>" command and that runs a script that does all the good stuff and then reboots.
JJC1138 said:
Hi there. I just wanted to clarify that if you're following the instructions I posted then you don't need telnet.
No, you don't need the modified RC29 to do this. After you type the "cd sdcard<enter>" command nothing visible should happen. It works because the bug in RC29 which we are exploiting executes everything you type on a hidden root console, so the cd command works, but it just doesn't show you anything. Then you enter the second "sh install<enter>" command and that runs a script that does all the good stuff and then reboots.
Click to expand...
Click to collapse
Thanks for the reply and for simplifying this for everyone. I was confused at first but now I understand better. I have the modified RC30 working now with the dev boot loader as well. Oh and a new theme too. Thanks again!!!
JJC1138 said:
Hi there. I just wanted to clarify that if you're following the instructions I posted then you don't need telnet.
No, you don't need the modified RC29 to do this. After you type the "cd sdcard<enter>" command nothing visible should happen. It works because the bug in RC29 which we are exploiting executes everything you type on a hidden root console, so the cd command works, but it just doesn't show you anything. Then you enter the second "sh install<enter>" command and that runs a script that does all the good stuff and then reboots.
Click to expand...
Click to collapse
Correct, this is a really good idea! Instead of typeing telnetd to start it as root, you are typing in and running the script that will root your phone-- as root! I'll update my sticky post shortly.
worked for me now do i delete the install file, DREAIMG file and Recovery test keys files or do i have to keep em?
l0uisz said:
worked for me now do i delete the install file, DREAIMG file and Recovery test keys files or do i have to keep em?
Click to expand...
Click to collapse
You can delete them off your SD card after they're installed.
Related
Hot off the presses. Get it here.
That file is the crappy "patch" version that tries to patch you from RC29 to RC30.
Here is the full update, which should be much more reliable
Obviously, don't install it unless you want to lose root access
Update for those who are interested: I went ahead and bought myself a new G1. One of the stores in the area had a couple. It still had RC28 (not RC29) on it, so I'm back in business. I'll just unlock my RC30 one and sell it on ebay.
OMG how stupid can they be... look what I see in the update script
# delete unneeded files
delete SYSTEM:system/bin/telnetd
Click to expand...
Click to collapse
Can we patch this like today cause I kinda think there is more to this than just doing that.
neoobs said:
OMG how stupid can they be... look what I see in the update script
Can we patch this like today cause I kinda think there is more to this than just doing that.
Click to expand...
Click to collapse
There is. They added a kernel option "console=null", which I suspect basically makes it so that the physical keyboard no longer sends input to the console device. Note that there is still a root shell running on the console though.. it's just that now there isn't any way to send keypresses to that root shell.
Plus there are a ton of patches to the android apps and framework jars and such. Not sure what all changed there.
I'm in the process of modifying the patch, to apply to my phone without losing root access. More to come
What does the "applypatch" piece do?
That part looks different.
Interesting that it's only a 4 meg update, and that it only contains a new recovery.img and a new boot.img - I wonder what is different in those images. I hope they are keeping the recovery stuff in the open source branch updated - because, well, that's the nice thing for them to to do
Jesus Freke - when you get your patched-up version ready, please post it somewhere for us lazy bastards who want to ride your coat-tails
I just noticed something. This update doesn't wipe the system partition. If you had created a setuid copy of the shell ("su", or whatever), I don't think it will get deleted if you applied the update as-is.
but didn't you say it removes the use of keyboard in shell? If so we would still be up the creek. you know what a notice this update came really fast i never got and OTA until this(fishy) i had to force OTA. Well hope you work your magic JesusFreke.
Arg! dangit. I accidentally applied RC30 and lost my root access. I copied the wrong update file to my sdcard... grrrr!
So I'm out of the game. Sorry.
Oh, btw - I was wrong about the update keeping the setuid shell around. It completely wipes the permissions of the system folder, so if you did have a setuid copy of the shell, it will be set back to normal non-setuid status by the update. duh.
Sh**!! You were the shining hope , one question can you still get root through the adb shell? cuz if so you can save your a**
Nope. Like I said, I'm out of the game. Unless someone wants to trade me for a RC19/RC29 phone. Or until another root exploit is found. *sigh*
DOH! That sucks! Sorry to hear that, and thanks for taking one for the team.
So if an update does try to install do we just need to turn off the phone until a solution is found? I may need to go back to my Dash for a while until this all gets figured out!
The update that you meant to put on the card- was it a test? If the worst that will happen is the update will take maybe someone that doesnt mind the update could test it for you?
JesusFreke said:
Arg! dangit. I accidentally applied RC30 and lost my root access. I copied the wrong update file to my sdcard... grrrr!
So I'm out of the game. Sorry.
Click to expand...
Click to collapse
I'm sorry about that!
Also, I'm confused. Hadn't you updated the keys in your bootloader to prevent an update? Or does that simply prevent the phone from downloading an update?
Can not we flash back that old RC29 File again ????
The update zip contains the boot.img and the recovery.img. so when the update starts it rewrites JesusFreke's mod recovery.img
spoofing
could we spoof the version # on our device? thus ending the nag and the ability to force the upgrade, for the time being?
bhang
RegGuheert said:
I'm sorry about that!
Also, I'm confused. Hadn't you updated the keys in your bootloader to prevent an update? Or does that simply prevent the phone from downloading an update?
Click to expand...
Click to collapse
Yes. But I had accidentally re-signed the full update with the new key and updated my phone with it. I was in the process of modifying the update, and had grabbed the wrong file to sign and update.
JesusFreke said:
Yes. But I had accidentally re-signed the full update with the new key and updated my phone with it. I was in the process of modifying the update, and had grabbed the wrong file to sign and update.
Click to expand...
Click to collapse
Ahh! That's a pain in the arse... the usb mass storage process is running as root, any chance of a buffer exploit there?
JesusFreke said:
Yes. But I had accidentally re-signed the full update with the new key and updated my phone with it. I was in the process of modifying the update, and had grabbed the wrong file to sign and update.
Click to expand...
Click to collapse
koush said:
mount -oremount,rw /dev/block/mtdblock3 /system
You can't remount that directory that unless you have root.
Use the dd command to copy stuff around (the cp command is not available). I should mention I'm a Windows guy, and am pretty clueless with Linux: my coworker figured the rest of this out once I got to a root prompt.
Incidentally, in the /system/bin directory there is a flash_image executable that changes the recovery.img used when you hard reset the device. I've noticed that I can run this without root access from a standard adb shell. Maybe we never needed to root the device after all... I think we can flash it without root access... I'm too scared to mess with that at all though.
Click to expand...
Click to collapse
I found this, you may want to look into it.
syrusfrost said:
I found this, you may want to look into it.
Click to expand...
Click to collapse
Thanks. But you have to have root access for the flash_image command to work. Or more precisely, you have to have write access to the /dev/mtd/mtd# device that you are trying to flash.
I am also the same unlucky guy who had Press Update Button and now we are in RC30
Now what are the chances of our device to get root access or ability to flash Test_Signed code in RC30
well i removed( # delete unneeded files delete SYSTEM:system/bin/telnetd )and replaced the boot.img and recovery.img with jesusfreke's anything else i should edit before i try to resign and update?
MODS - can you please move this thread to the sapphire development forum and stick it? thanks
_______________________________________________________________
WE HAVE A ROOT NOW
haykuro said:
GOT ROOT?
http://droiddeveloper.com/hrbuilds/boot-new.img.zip
1. download this, extract boot-new.img to your computer.
2. place your device into bootloader mode (BACK+POWER, or VOLUME DOWN+POWER)
3. fastboot boot boot-new.img
4. wait for device to boot
5. adb push boot-new.img /sdcard/boot-new.img
6. adb shell flash_image boot /sdcard/boot-new.img
that's it!
your device now has root via adb shell.
i'm making the rooted recovery.img now for magic
Click to expand...
Click to collapse
It shouldn't be too hard.
Viper only needs to update his QMAT for creaatin goldcards for the Magic.
Then you have to flash the RC29 nbh with it.
If only adb successes connecting to the magic with rc29 of g1, you can start telnetd.
Then you should be able to. Flash a custom recovery image to flash a modified cupcake.
maxisma said:
It shouldn't be too hard.
Viper only needs to update his QMAT for creaatin goldcards for the Magic.
Then you have to flash the RC29 nbh with it.
If only adb successes connecting to the magic with rc29 of g1, you can start telnetd.
Then you should be able to. Flash a custom recovery image to flash a modified cupcake.
Click to expand...
Click to collapse
Well, you see what I meant? all the expert are here!
Let's wait for Viper comment and/or ideas.
But one problem:
I don't know if the RC29 is compatible with the Magic. Maybe someone has to create a custom .nbh with customized drivers for the magic.
And please. Don't call me an expert
It's only an idea I know linux commands etc. But i know only some basics of programming (e.g. to make a DOS caluclator in C++ )
maxisma said:
But one problem:
I don't know if the RC29 is compatible with the Magic. Maybe someone has to create a custom .nbh with customized drivers for the magic.
And please. Don't call me an expert
It's only an idea I know linux commands etc. But i know only some basics of programming (e.g. to make a DOS caluclator in C++ )
Click to expand...
Click to collapse
I am far from being an expert but even if RC29 works and the DREAM test recovery works (which I doubt), it has no support for virtual keyboard, so right after he gets root he will need a hacked rooted ROM for the Magic. Isn't it safe to assume that until someone cook a special ROM for the Magic he is stuck with a rooted but unusable device?
A much bigger problem: how in the hell can you telnet in the Magic with no keyboard? Or even get past the setup wizard? In other words, even with RC29 there'll be no way to get root or even use the phone. This is gonna be a hell of a lot more difficult than it was for the G1(and it was pretty damn difficult for that)
Well, I guess HTC created this function for their reasons (tests etc.) and now it's only a matter of time until someone will find the way to do it too.
that's the reasone I posted the request, I seen things in XDA that i could never believe before, let's hope it'll happen again ...
Will this post help? http://www.codeandroid.org/forum/?wpforumaction=viewtopic&t=9.2
The guy pk detailed a 27 step, step-by-step guide to unlock those HTC Dream outside UK and US. Hope it helps.
chuazy said:
Will this post help? http://www.codeandroid.org/forum/?wpforumaction=viewtopic&t=9.2
The guy pk detailed a 27 step, step-by-step guide to unlock those HTC Dream outside UK and US. Hope it helps.
Click to expand...
Click to collapse
"2) Launch Terminal Emulator
3) Enter the following:
cd /sys/class/mmc_host/mmc1:*"
Terminal Emulator doesn't seem to work without hardware keyboard(doesn't bring up vk for me on G1 using cupcake, I'd imagine it wouldn't work on magic either). Speaking of which, you guys with Magic's wouldn't be able to use any of the recovery mode options either since those all require a hw keyboard. So even if you got a JF build you wouldn't be able to flash it.
[email protected] said:
"2) Launch Terminal Emulator
3) Enter the following:
cd /sys/class/mmc_host/mmc1:*"
Terminal Emulator doesn't seem to work without hardware keyboard(doesn't bring up vk for me on G1 using cupcake, I'd imagine it wouldn't work on magic either). Speaking of which, you guys with Magic's wouldn't be able to use any of the recovery mode options either since those all require a hw keyboard. So even if you got a JF build you wouldn't be able to flash it.
Click to expand...
Click to collapse
But you do understand this function must be exist right? even if you can't find it now, HTC created it because they do use the recovery mode options for test and stuff...
avimak said:
But you do understand this function must be exist right? even if you can't find it now, HTC created it because they do use the recovery mode options for test and stuff...
Click to expand...
Click to collapse
Unless they do so using some external hardware which is fully possible...(think external keyboard, possibly through extUSB)
EDIT: btw: not trying to be an ass or say that you guys are screwed, just pointing out problems that will need to be solved in order for this to work.
[email protected] said:
Unless they do so using some external hardware which is fully possible...(think external keyboard, possibly through extUSB)
EDIT: btw: not trying to be an ass or say that you guys are screwed, just pointing out problems that will need to be solved in order for this to work.
Click to expand...
Click to collapse
Well, if external USB keyboard is the only thing it takes to root my device - I'll buy one, and root the rest of the Magic Israeli users for free
You don't need a virtual keyboard.
If USB-Connection an ADB wworks, you can get in the hidden root shell by using adb shell with the sdk-tools.
maxisma said:
You don't need a virtual keyboard.
If USB-Connection an ADB wworks, you can get in the hidden root shell by using adb shell with the sdk-tools.
Click to expand...
Click to collapse
I got it:
$ (I can write stuff)...
what next?
@avimak:
You mean, you've connected your magic with installed rc29?
maxisma said:
@avimak:
You mean, you've connected your magic with installed rc29?
Click to expand...
Click to collapse
No, I have the Magic (vodafone version) connected to my PC (win xp) and I can run ADB shell.
avimak said:
No, I have the Magic (vodafone version) connected to my PC (win xp) and I can run ADB shell.
Click to expand...
Click to collapse
ok.
But i meant someone has to test if a magic downgraded to rc29 (via goldcard) works.
Not the orig. Firmware.
maxisma said:
You don't need a virtual keyboard.
If USB-Connection an ADB wworks, you can get in the hidden root shell by using adb shell with the sdk-tools.
Click to expand...
Click to collapse
That's true for the terminal once the operating system has started, but they'll be hosed if they ever reach a boot looping problem or need to flash any ROM.
EDIT: Well not if they boot loop on the android screen, but if it loops on the SPL, then they're hosed.
[email protected] said:
That's true for the terminal once the operating system has started, but they'll be hosed if they ever reach a boot looping problem or need to flash any ROM.
EDIT: Well not if they boot loop on the android screen, but if it loops on the SPL, then they're hosed.
Click to expand...
Click to collapse
Can you please write it again in simple words?
It's a bit "pro only" talking. I got my Android yesterday...
maxisma said:
ok.
But i meant someone has to test if a magic downgraded to rc29 (via goldcard) works.
Not the orig. Firmware.
Click to expand...
Click to collapse
There is an option to go back to the orig. version after the downgrade? can I "dump" my OS somewhere and Install it again from SPL if it failed the rc29?
I'm coming from WM - I'm speaking they lang...
Here are the directions and files used to fix this problem (do not type any of the "quotation marks"):
1. Download the .zip file from here: http://www.megaupload.com/?d=YUYEMJNM
and put it on the root of your sdcard. (Do not unzip the file). Then rename it to PD15IMG.zip .
2. Download the miscnew file to your computer (uploaded as attachment to this post). Unzip it and place the miscnew.img file that was in the zip onto the root of your sdcard. You can delete the .zip file after you do this.
3. Boot your phone up like normal and connect your phone to your computer.
4. Make sure your sdcard is NOT mounted (but make sure those 2 files were copied to your sdcard).
5. Go into adb and type "adb shell"
6. Then type, "su"
7. Then type, "dd if=/sdcard/miscnew.img of=/dev/block/mmcblk0p17"
8. Once this is done after about 5 seconds, turn your phone off and unplug from the computer.
9. Once the phone is off, hold down the volume-down key and the power button until you arrive at the bootloader. Once there, the phone should automatically start checking that .zip file you downloaded to the root of your sdcard. After its done checking, it will ask you if you want to continue, and just follow the prompt to say "yes" and YOU'RE DONE!
This guide was made by travisjames and was just put into my own words. His guide was a derivative of Apache14's OTA and Radio downgrade guide for the T-Mobile G2.
Also, thanks to Clarknick27 for tipping me off on how to get back into my phone after it was unbootable.
***Please click "thanks" if this helped you!
Ignore/Wrong thread...
two questions-
if i used gfree, do i need to undo gfree 1st? (you make no mention of rooting techniques, and if this undoes all those or not)
second, my phone, about a month ago, lost data connectivity on the usb port-- in other words, it charges fine, but i can not get any computer to pick it up any more to transfer files are use adb, which is a royal pain. -- can i use terminal emulator to accomplish your commands, or am I SOL ?
thanks
Yes, you need to undo Gfree.
Yes, you can run the commands from Terminal Emulator.
Added to Wiki.
thanks jack,
would the syntax be exactly the same as above via term em?
Yes, just skip the "adb shell" command.
Is this to undo 2.3.4 GB update and take it back to 2.2.1?
How do I undo gfree? And if I just run the pg15img will I keep root? I need a way to return to stock but rooted.
Sent from my Incredible 2 using XDA App
andrewp3481 said:
How do I undo gfree? And if I just run the pg15img will I keep root? I need a way to return to stock but rooted.
Sent from my Incredible 2 using XDA App
Click to expand...
Click to collapse
First question, Here is the thread you need to undo gfree (get s-on) http://forum.xda-developers.com/showthread.php?t=858996 (about half way down OP)
Second question, no you will not keep root
witch stock rom do you want rooted, stock 2.3.4 can not be rooted right now
So... to summarize, this would be to revert back to Android 2.3.4, sense 3.5 STOCK, without root, eng. hboot, or s=off.
In other words, if you purchased a MT4G now, or received a replacement MT4G with 2.3.4.... Following these steps will give you this new gingerbread stock state (approximately).
Please confirm. Thanks!
can i use this steps with terminal emulator on my phone instead of adb?
unciviilized said:
can i use this steps with terminal emulator on my phone instead of adb?
Click to expand...
Click to collapse
Yes...check the 3rd and 4th post of this thread....
Just curious, so if I flash this ROM in recovery, will I lose root, s-off, etc.?
What I'm trying to do is flash the phone to the MT4G stock rom (which I assume this is), use gfree to sim unlock it, then revert back to my nandroid backup, so I wanna make sure this will not interfere with my root access before I proceed to flashing it. Thanks in advance to whoever answers me~!
ronin178 said:
Yes...check the 3rd and 4th post of this thread....
Click to expand...
Click to collapse
ok so when im on emulator i do "s" and it says permission denied,
then i got to command prompt and it says adb shell is not recognized as and internal or external command. Any suggestions?
unciviilized said:
ok so when im on emulator i do "s" and it says permission denied,
then i got to command prompt and it says adb shell is not recognized as and internal or external command. Any suggestions?
Click to expand...
Click to collapse
You don't need to type adb shell because you are on terminal emulator.
Just type su to gain superuser access.
Then type dd if=/sdcard/miscnew.img of=/dev/block/mmcblk0p17
Make sure you have the file miscnew.img in the root of your sd card.
Absolutely Perfect
I have looked and looked all over both XDA and the Interent in general. I was trying to restore my Glacier (MyTouch 4g) from stock 2.3.4 to stock 2.2. NOTHING worked. It got to the point that I didn't even remember everything that I tried. I followed this guide to the T. PERFECT!!! I am now back to having my phone exactly how I left the Tmo store with it.
I CANNOT THANK YOU ENOUGH!!
Great work in helping people out that don't understand. And making it a less strenious process
Sent from my HTC Glacier using xda premium
Jack_R1 said:
Yes, you need to undo Gfree.
Yes, you can run the commands from Terminal Emulator.
Added to Wiki.
Click to expand...
Click to collapse
Sorry, a complete noob to "gfree". I'm a new convert to GSM as I was with SPrint CDMA for 10 years until a couple weeks ago. I've rooted Samsing phones but never an HTC.
Anyways, I just purchased a MyTouch that had been rooted and loaded with Virtuous ROM. It's for my wife and she wants it back to stock. I tried all your directions exactly but still will not work. I'm assuming it's this "gfree" issue. I followed the link to the other thread but it's not clear on exactly what I need to do in my situation.
When I run the bootloader, it says bad or no such image... I have confirmed I have PD15IMG.zip and miscnew.img in the sdcard root directory.
Can someone please show me in simplified terms. Thanks!
socal88 said:
Sorry, a complete noob to "gfree". I'm a new convert to GSM as I was with SPrint CDMA for 10 years until a couple weeks ago. I've rooted Samsing phones but never an HTC.
Anyways, I just purchased a MyTouch that had been rooted and loaded with Virtuous ROM. It's for my wife and she wants it back to stock. I tried all your directions exactly but still will not work. I'm assuming it's this "gfree" issue. I followed the link to the other thread but it's not clear on exactly what I need to do in my situation.
When I run the bootloader, it says bad or no such image... I have confirmed I have PD15IMG.zip and miscnew.img in the sdcard root directory.
Can someone please show me in simplified terms. Thanks!
Click to expand...
Click to collapse
If you are new to this rooting stuffs, i suggest don't go with methods, that have potential to brick your phone.
Just do this simple method, Follow the link in my signature, you will see a Rooted version of the stock 2.3.4 rom.
Just flash the Rom through your recovery.........no big deal.......easy way to get the stock feel.....
Follow the instructions carefully.........Happy Flashing........
Thanks for the great help. One more question -- How do I turn "quick boot" off?
I download the OTA and the phone resets. When I get the Android updating screen, it dies on 20%... then reboots and tells me the update failed. anyone know why it's failing to update? I did freeze some apps from titanium backup.
ImYoungxD said:
I download the OTA and the phone resets. When I get the Android updating screen, it dies on 20%... then reboots and tells me the update failed. anyone know why it's failing to update? I did freeze some apps from titanium backup.
Click to expand...
Click to collapse
That is probably why. I'd recommend doing a factory reset in recovery.
ImYoungxD said:
I download the OTA and the phone resets. When I get the Android updating screen, it dies on 20%... then reboots and tells me the update failed. anyone know why it's failing to update? I did freeze some apps from titanium backup.
Click to expand...
Click to collapse
If you're running titanium then that means you're rooted, right? If you're rooted you should NOT (ie. Never) take a factory ota update. It has the potential to brick your phone.
What ota was it?
Sent from a SYNERGIZED GalaxySIII
Thats your device telling you to stay way the hell away from OTA's and revert to the dev section for your flashing needs!
I usually update my rooted transformer infinity OTAs with no problems.
Never knew rooted S3 can't update OTAs. meh.
I don't feel like flashing the phone because backing up the IMEI looks like such a pain ... Looks like I will have to look over it again.
ImYoungxD said:
I usually update my rooted transformer infinity OTAs with no problems.
Never knew rooted S3 can't update OTAs. meh.
I don't feel like unlocking the phone because backing up the IMEI looks like such a pain ... Looks like I will have to look over it again.
Click to expand...
Click to collapse
all you do is open terminal emulator, grant super user access, and type "NV Backup". I almost busted out in sweat the task was so strenuous.
droidstyle said:
all you do is open terminal emulator, grant super user access, and type "NV Backup". I almost busted out in sweat the task was so strenuous.
Click to expand...
Click to collapse
I have to start from scratch. I don't have ABD or whatever that thing was called. I'm going to try it out again some other day.
ImYoungxD said:
I have to start from scratch. I don't have ABD or whatever that thing was called. I'm going to try it out again some other day.
Click to expand...
Click to collapse
terminal is a app you download from the playstore... all you need is root access to use it.
droidstyle said:
terminal is a app you download from the playstore... all you need is root access to use it.
Click to expand...
Click to collapse
It's that simple...? never knew i can download it from the play store...
What is this whole site for? http://www.addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android/
read this thread
http://forum.xda-developers.com/showthread.php?t=1852255
I got that link in step 1.
"1. If your phone does not have Terminal Emulator installed, you will need to use ADB. Download and install the Android SDK platform-tools for your platform. This is a bit non-trivial as it requires the installation of the Android SDK, however, you can find a guide for installing adb here. After installing, open a command prompt and navigate to the "platform-tools" folder within the SDK, where adb is stored. If you need additional help on this, simply ask in this thread."
That site with the guide to install adb has terrible instructions so I gave up.
ImYoungxD said:
I got that link in step 1.
"1. If your phone does not have Terminal Emulator installed, you will need to use ADB. Download and install the Android SDK platform-tools for your platform. This is a bit non-trivial as it requires the installation of the Android SDK, however, you can find a guide for installing adb here. After installing, open a command prompt and navigate to the "platform-tools" folder within the SDK, where adb is stored. If you need additional help on this, simply ask in this thread."
That site with the guide to install adb has terrible instructions so I gave up.
Click to expand...
Click to collapse
Dude you are making this way too difficult lol...install terminal emulator from the playstore and run the nv backup command...then never worry about losing imei again.
For Terminal Emulator: The actual "beef" of the command is the "reboot nvbackup" line. Therefore, if you have Terminal Emulator installed, you can just run the command straight off your phone. Enter these two commands from the app:
Code:
su
reboot nvbackup
I had the same problem. Ended up using odin to push the latest stock software which included the update. Now to see if I still get the no sim error. Realizing after all this time I really didn't need to root.
ImYoungxD said:
I did freeze some apps from titanium backup.
Click to expand...
Click to collapse
This is without a doubt the reason the update failed (unless there are multiple reasons). If you unfreeze the apps, it should install as expected.
apacseven said:
This is without a doubt the reason the update failed (unless there are multiple reasons). If you unfreeze the apps, it should install as expected.
Click to expand...
Click to collapse
I had zero apps frozen and was unable to install the update. Pushing it via Odin was the only thing that worked for me.
mdt73 said:
I had zero apps frozen and was unable to install the update. Pushing it via Odin was the only thing that worked for me.
Click to expand...
Click to collapse
Yes it isnt the only thing that can cause an update to fail. But since he already stated that he had frozen some apps, then it is known that the check will fail and the update wont proceed.
If you don't know why it failed. download to OTA. And when it prompts you to install, say you'll do it later. Now extract the update file from your /cache/ directory. (That's where it was on Motorola's, I think its /cache/fota/ on our S3 ). Copy/move that file to the root of your SD card. Reboot into stock recovery and flash it. Watch the update when it fails it will call out specifically what went wrong. When you let the system automatically do it you don't get that luxury. If you initiate the update on your own through stock recovery though, you are granted that key piece of Intel as to what it didn't like.
Freezing anything in titanium will fail an OTA automatically. It checks system files to make sure certain ones are there, especially bloatware. Also having custom recovery will fail you.
As was said if your rooted you should never both with OTA anymore. If you're coming from a motorola like I did it is hard to grasp that at first. We needed official OTA to update the kernel. So you almost had to do it. Now though. We have an unlocked bootloader here. You can flash any kernel you feel. So OTA are meaningless for us on the S3. The devs steal all the good code and bits and put it in their ROMs and leave out the garbage. No reason to need official OTA anymore then unless you truly want to
Sent from a GlaDos Baked Potato
droidstyle said:
Dude you are making this way too difficult lol...install terminal emulator from the playstore and run the nv backup command...then never worry about losing imei again.
For Terminal Emulator: The actual "beef" of the command is the "reboot nvbackup" line. Therefore, if you have Terminal Emulator installed, you can just run the command straight off your phone. Enter these two commands from the app:
Code:
su
reboot nvbackup
Click to expand...
Click to collapse
Seriously..... That was easy lol. What's the point of step 1
Since I never read the next lines that says " If your phone is rooted and has Terminal Emulator installed, you don't need to do any of this. Simply open up the Terminal Emulator and go to step 2.", I never completed backing up the IMEI probably because I didn't know the Terminal Emulator was an playstore app.... Now I got a backup, I'm unlocked, running a custom rom. Thanks a lot man. You helped a lot.
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thanks
FNM
ImYoungxD said:
Seriously..... That was easy lol. What's the point of step 1
Since I never read the next lines that says " If your phone is rooted and has Terminal Emulator installed, you don't need to do any of this. Simply open up the Terminal Emulator and go to step 2.", I never completed backing up the IMEI probably because I didn't know the Terminal Emulator was an playstore app.... Now I got a backup, I'm unlocked, running a custom rom. Thanks a lot man. You helped a lot.
Click to expand...
Click to collapse
No prblem sir, glad to help!
Google Store purchased, currently have root and twrp installed, bootloader unlocked.
I read briefly that to accept the new update and keep root, you have to mess with the bootloader? Is there some sort of simplified guide on this?
Thanks to chainfire, there is a guide for updating to may version and keep may bootloader.
First, you have to flash new factory image or sideload the ota
Let it reboot, now you lost recovery, custom kernel, root etc..
Reboot to bootloader and boot to twrp, flash supersu and the zip provided by chainfire for signing the bootloader
Reboot and you should have root with may update
If you want a custom kernel or twrp you should flash the zips and the verification tool, i didn't understand the right process for this, for me it looped a couple of times but after flashing those files a bunch of times in different orders it succesfully booted with no errors.
I'm currently running stock 7.1.2 may update with supersu 2.79 SR3, TWRP 3.0.1 RC1, franco kernel r15 with no errors, everything running perfectly
Where can we get the May ota download and a refresher on sideloading it? I've done that before but don't do it often enough to get through it quickly... currently running 7.1.2 / NHG47K on my Google bought Pixel which has been unlocked, and rooted. Though I've not installed TWRP, I can bootload into it fine....
My phone app has suddenly started acting all wonky, so I'd really like to update and see if that will help straighten things up.
Thanks for the assistance...
Got the May ota and will now sideload it. Where is this 'guide' that you mentioned Chainfire has setup to assist folks handling the May update?? I'd like, specifically, to get a copy of the zip file that signs the bootloader.
Thanks!!
I am wondering also. Still using NDE63P from October, wasn't aware we could take OTA's at all and keep root. Been having so many Bluetooth issues, it's worth a shot given their focus on it a month or so ago.
Well... up until this recent May ota release, it used to be pretty easy to simply download the latest Superuser zip file and re-install it on your phone, thereby re-establishing root access (assuming your phone is / was unlocked and rooted prior to taking the update). That is not the case going forward.... but I am still researching it.... follow along by looking here: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Oh wow, that's super easy. Sweet! Now I need to find out where the past OTA's are so I can flash all of those...
I'm going to give all that a try soon, if anyone following this thread needs help or has questions, feel free to reply here with them.
To dumb down that entire OP into the reason why it's needed: the OTA's being sent out up through April 2017 was just the OTA itself. In May, they started requiring them to be encrypted with a certificate, but didn't provide requirements on from whom the certificate comes from. This means that now, instead of just flashing the ZIP, you first encrypt it with your own certificate and then flash the result of that.
They mention the private keys can be discarded later, given they are generated for the sole purpose of uploading OTA's to the phone, I would think keeping them on the internal SD card of the phone itself would be suitable. Heck, zip those puppies up and email them to yourself, they're not being used for security, why not, right?
Try here: https://developers.google.com/android/ota
Just sideload the latest... you only need one
pstgh said:
... https://developers.google.com/android/ota
Just sideload the latest
Click to expand...
Click to collapse
pstgh said:
... follow along by looking here: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Click to expand...
Click to collapse
Yes, the first link is the ota repositories, download the zip of may, then put it in the adb folder, reboot to recovery, go in advanced menu and start sideload, without wipe cache or dalvik.
Then in cmd just type "adb sideload <name-of-the-ota.zip>"
Let it finish both steps and reboot, then you are ready to boot to twrp and flash supersu and the zip v3 from chainfire's thread for signin the bootloader.
That's it
Agree. Pro tip: after downloading the proper ota update, rename it to something simpler so you can more easily enter that adb sideload ota-filename.zip command!
pstgh said:
Agree. Pro tip: after downloading the proper ota update, rename it to something simpler so you can more easily enter that adb sideload ota-filename.zip command!
Click to expand...
Click to collapse
better pro tip: tab auto completes the filename.
exad said:
better pro tip: tab auto completes the filename.
Click to expand...
Click to collapse
Expert pro tip: shift+right click the file, "Copy As Path", paste into the terminal.
(I use ConEmu, so right-clicking the terminal itself pastes what's on the clipboard; some Linux distros do this also Command Prompt I think right click is done on the title bar or some obscure thing like that, can't remember).
Expert pro tip: shift+right click the file, "Copy As Path", paste into the terminal. -
I like this one but when I tried it, fyi, it pastes the path with quote marks on either end.... which is burdensome
Quotes are accepted in the adb commands. Without them, each space in the path is interpreted as an argument delimiter.
adb some-command C:\Program Files\Some-Program\Main.exe
passes "C:\Program" and "Files\Some-Program\Main.exe" as two different arguments to adb. Surrounding it with quotes instead allows adb to use the full path correctly. Common practice with command-line apps, although not universally supported.
It does work with adb/fastboot though, just did it a couple days ago to upgrade my Huawei Watch with the Wear 2.0 OTA that it kept failing to detect was available.