I want to upgrade a US T-Mobile G1 to 2.1. Is the following procedure correct? (Don't need to backup.)
In bootloader flash RC29 DREAIMG.nbh. Reboot.
Type telnetd, install Android Telnet Client and root.
Install recovery-RA-dream-v1.7.0-cyan.img using Telnet Client.
In recovery flash G1-radio-2_22_23_02.zip. Reboot.
In recovery flash spl_1_33_2003.zip. Reboot.
In recovery flash FR-recovery-v1.5.3-CustomMTD_S.zip. Reboot.
In recovery flash signed-SuperE103.zip then flash gapps-mdpi-FRF91-3-signed.zip then flash FR-boot-v1.5.3-CustomMTD_S.zip. Reboot.
Your way will work but I recommend a minor change iif you are using the rc29 method of rooting:
In bootloader flash RC29 DREAIMG.nbh. Reboot.
Type telnetd, install Android Telnet Client and root.
Install recovery-RA-dream-v1.7.0-cyan.img using Telnet Client.
In recovery flash spl_1_33_2003.zip. Reboot. (Will return to recovery)
boot fastboot and flash the 2.x radio (info on my 1.33.2003 post.. and the *.img file is in the g1boot.zip)
while in fastboot wipe so custom mtd works 'fastboot erase system -w' and 'fastboot erase boot'
In recovery flash FR-recovery-v1.5.3-CustomMTD_S.zip. Reboot.
In recovery flash signed-SuperE103.zip then flash gapps-mdpi-FRF91-3-signed.zip then flash FR-boot-v1.5.3-CustomMTD_S.zip. Reboot.
I'm not 100% sure of that gapps package.. just check the super-e page if its correct
Edit: If you don't want to downgrade first look at:
http://forum.xda-developers.com/wiki/index.php?title=User:Ezterry/G1_1.6_To_Custom_Firmware
Thanks for the links. What is the advantage of installing radio via fastboot instead of recovery?
felix1234 said:
Thanks for the links. What is the advantage of installing radio via fastboot instead of recovery?
Click to expand...
Click to collapse
Rather than re-iterate see my post here: http://forum.cyanogenmod.com/topic/...e-via-fastboot/page__view__findpost__p__44790
In short it should be of similar difficulty for you the user and it has slightly less risk (not that there was much risk in flashing a 2.x over a 1.x one in recovery)..
For many scenarios that could brick however: if you flash via fastboot you will likely continue to be able to access fastboot after the flash; thus able to fix the phone.. while if you flash via recovery you get stuck in "boot mode 3" unable to boot anything without JTAG.
Thanks for explaining and writing the exploit guide. Will try!
Related
My first post but I've been lurking for years. Pretty good with search, etc.
If anyone could help I would really appreciate it. I've been working on this for 12 hours!
I updated to Cyanogen 4.1.999
I successfully installed the new radio and fastboot confirms 2.22.19.261
Here's where I made the mistake in the following directions:
I have CMRecovery Image 1.4
-Go to http://developer.htc.com/adp.html
-DL the 1.6 "recovery image" the file name is - signed-dream_devphone_userdebug-ota-14721.zip
-Then DL CyanogenMod-4.1.99
http://n0rp.chemlab.org/android/expe....99-signed.zip
-put them both on your SD card
-Boot up into CM recovery image 1.4 by rebooting and holding the home button, do a wipe.
-update using any zip to that "recovery image" (signed-dream_devphone_userdebug-ota-14721.zip)
(it should auto reboot install radio then reboot again and load back up to the CMrecovery img screen)
I mistakenly rebooted normally instead of applying the update in the next step. This is when the black screen began.
-Then update any zip usig CyanogenMod-4.1.99 (update-cm-4.1.99-signed.zip)
-Then power on the phone
I am stuck at the black screen of death.
I can fastboot and I've fastbooted the pimp recovery and still can't access recovery. Just get the triangle.
So, during update after new radio I rebooted normally instead of updating with the final build update got a black screen and have no recovery.
I've tried fastboot flash recovery and fastboot update.
fastboot flash recovery is succesful
fastboot update or fastboot flashall give me the "archive does not contain android-info.text and android-product.text" errors.
Any ideas would be greatly appreciated.
this should be posted in Q/A not development.
cingall said:
this should be posted in Q/A not development.
Click to expand...
Click to collapse
Sorry!
Mod please move. Thanks!
if you have access to fastboot, do a fastboot flash everything... from radio, system, and what not (forgetting something)
if that doesn't work... do a fastboot of the radio and boot and system, do everything.
basically do a fastboot of the normal dev 1.6 system....
its on htc's website.... gl dude
theomajigga said:
if you have access to fastboot, do a fastboot flash everything... from radio, system, and what not (forgetting something)
if that doesn't work... do a fastboot of the radio and boot and system, do everything.
basically do a fastboot of the normal dev 1.6 system....
its on htc's website.... gl dude
Click to expand...
Click to collapse
any ideas on the commands to flash them as flashall? HTC's site has them as separate files so I can only flash the "recovery" file.
I'm sorry to be somewhat of a noob with the actual codes. Could you be more specifc with which files to flash with which commands?
TIA!
Using the HTC website 1.6 "recovery" with fastboot update I get the following:
Error: update package has no android-info.txt or android-product.txt
I can't figure out how to flash the radio or system files in any other way than update in fastboot.
Did you erase the recovery? When this happened to me, just installing CM 1.4 from fastboot did not work, I had to erase the recovery then install. Hope this helps.
Also remove your SD card while booting, as prior stuff in your ext3 partition can cause black screens during boot. If that fixes it, you need to reformat your ext3.
The triangle you see is the standard recovery, to access it you need to do alt-L?or alt-x cant remember. To fix you need to flash cm-recovery to do this reboot into the boot loader (power + camera) plug in usb and hit the back button you should see "fastboot" then run
fastboot erase recovery
fastboot flash recovery cm-recovery-1.4.img
seehttp://forum.xda-developers.com/showthread.php?t=523558
then install rom as normal
okay this happened to me as well. I just made sure that I wiped, then started allover again. i had to do it a couple of times but it worked. just make sure that you still have the files on your SD card.
Good Luck!!!!
brnbock said:
Did you erase the recovery? When this happened to me, just installing CM 1.4 from fastboot did not work, I had to erase the recovery then install. Hope this helps.
Click to expand...
Click to collapse
You are a STAR!! Thank you, thank you, thank you!! I knew it was something stupid!
Back at the recovery console! woot!!!
Mods please close this thread!
Please Help "Brick" with Cyanogen's newest upate
Do you still need help bricking your phone???
took 30 min to post a re.. sorry i was late
fastboot erase recovery
fastboot flash recovery *name of recovery*
fastboot flash system system.img
fastboot flash userdata data.img
fastboot flash boot boot.img
fastboot reboot
Click to expand...
Click to collapse
That should fix it.
ugh, now I am stuck at the g1 screen after a reboot of a successful update.
reformatted sd and all probs are solved!
mghtyred said:
Please Help "Brick" with Cyanogen's newest upate
Do you still need help bricking your phone???
Click to expand...
Click to collapse
Hi mghtyred (of tmobile forums) welcome to XDA
I flashed a new ROM to the phone and rebooted. At reboot, when the first "android" screen comes up it gets stuck there.
If I reboot in to the recovery screen it will go there but I can't do ANYTHING! Can't scroll to a command, can't "Alt+" any command.
At the very bottom of the screen it says:
Build : RA-dream-v1.7.0
E:Error in CACHE:recovery/log
(No space left on device)
HELP?!? Did I finally manage to find a way to brick my phone?
I do not expect that you bricked your phone. What SPL do you have installed? If you have 1.33.2003 or 1.33.2005 installed, you have always he possiblity to go to fastboot mode and flash a new recovery.
AndDiSa said:
I do not expect that you bricked your phone. What SPL do you have installed? If you have 1.33.2003 or 1.33.2005 installed, you have always he possiblity to go to fastboot mode and flash a new recovery.
Click to expand...
Click to collapse
I AM able to get it in to fastboot. I'm still a bit of a newbie though, so I'm not sure what SPL I have...? Possibly Danger? How do I flash a new recovery?
AndDiSa said:
I do not expect that you bricked your phone. What SPL do you have installed? If you have 1.33.2003 or 1.33.2005 installed, you have always he possiblity to go to fastboot mode and flash a new recovery.
Click to expand...
Click to collapse
Oh! I see in fastboot that I do have 1.33.2005. So how do I flash a recovery? Thanks!
Nevermind, I Got it!! Thanks for the suggestion/help!
1.33.21005 is DangerSPL, so you have the possibility to use fastboot. There is a tutorial here in the forum to setup adb and fastboot. Unfortunately I do not have the link at the moment.
If you have setup your fastboot environment, you should be able to flash a new recovery with the following command:
fastboot flash recovery recovery.img
Send from my G1 with HTCClay's UNOFFICIAL Superfly 1.5 D/S ADS using XDA App
Excellent
AndDiSa said:
1.33.21005 is DangerSPL, so you have the possibility to use fastboot. There is a tutorial here in the forum to setup adb and fastboot. Unfortunately I do not have the link at the moment.
If you have setup your fastboot environment, you should be able to flash a new recovery with the following command:
fastboot flash recovery recovery.img
Send from my G1 with HTCClay's UNOFFICIAL Superfly 1.5 D/S ADS using XDA App
Click to expand...
Click to collapse
I had the exact same issue and this worked from me...using Amon_RA's method:
"via fastboot :
* Requires engineerings SPL!
Code:
Copy recovery-RA-dream-v1.7.0.img to a location where fastboot can find it.
Boot your G1 into fastboot mode (boot while holding BACK)
Connect your G1 via usb to your pc/mac/...
fastboot devices (to make sure that fastboot "sees" your device)
fastboot flash recovery recovery-RA-dream-v1.7.0.img
"
I just saved recovery-RA-dream-v1.7.0.img to the "tools" folder of the android-sdk and ran cmd from there (Hold shift + Right-click in win7).
Rebooted holding home and I was in RA-dream-v1.7.0 without the error.
Click the recovery image link in my sig for more info.
Thanks!!
To all of you that have suggested things, I figured it out thanks to your suggestions!! I appreciate all of your help on this issue!!
i have the latest radio and hboot for G1 (check sig) and in fastboot mode it says S-on.. now im having trouble flashing a custom splash screen via fastboot and i read somewhere that the S-on may be why.. do i need to downgrade to engineering spl to use fastboot flash method? I keep getting a... <bootloader> checking signature failed! in cmd... but i do have fastboot enabled and working properly..
Did you follow ezterry's on how to install the spl and radio:http://forum.xda-developers.com/showthread.php?t=831139? did u follow these steps for installing the spl?
== Installing ==
(Note: Please Do read the information on the SPL below before actually installing)
1) Take a nandroid backup of your current rom (mandatory if you are trying to move the current rom to the new radio/SPL) to simplify things put any update.zips you expect to need on the SD card now
2) enter fastboot mode
3) flash the files and other operations via fastboot
Code:
fastboot flash recovery recovery-RA-dream-v1.7.0-cyan.img
fastboot flash radio radio-2.22.27.08.img
fastboot flash hboot hboot-1.33.0013d.img
fastboot reboot-bootloader
now you will see you have an s-on boot loader with 1.33.0013d as its version
Code:
fastboot erase system -w
fastboot erase boot
please remember while fastboot erase works; fastboot flash does not so be careful *not* to remove the recovery
4) Boot into recovery
5) install a system from backup or as a fresh rom some options are:
Click to expand...
Click to collapse
ldrifta said:
i have the latest radio and hboot for G1 (check sig) and in fastboot mode it says S-on.. now im having trouble flashing a custom splash screen via fastboot and i read somewhere that the S-on may be why.. do i need to downgrade to engineering spl to use fastboot flash method? I keep getting a... <bootloader> checking signature failed! in cmd... but i do have fastboot enabled and working properly..
Click to expand...
Click to collapse
You have a perfected SPL installed on your phone (0013d), so you do not have full fastboot support and you are not able to flash a custom splash screen.
If you want to downgrade, flash the orange-xxx.nbh file from Terry's thread (can be found in my signature) and after that you will have an engineering SPL. With this you should be able to flash a custom splash screen. After that you can go back to 1.33.0013d/2.22.28.25 ... everything can be done using fastboot, so your risks to brick your phone are very(?) limited ...
yeah i figured it out thanks guys!! had to temp flash the engineering spl to do what i wanted.. than jus re flashed 0013d everything is all set thank you guys though!!!
I accidentally removed the recovery... and still having same issues with S-ON with HBOOT-1.33.0013d.... need help getting recovery back on my phone. have new radio too.
hubby0925 said:
I accidentally removed the recovery... and still having same issues with S-ON with HBOOT-1.33.0013d.... need help getting recovery back on my phone. have new radio too.
Click to expand...
Click to collapse
You (as I see was indicated in the thread before) go to the 2708+ kernel/SPL/Radio thread:
http://forum.xda-developers.com/showthread.php?t=831139
This has all the information on the use of 2708/2835 radios and the 1.33.0013d SPL including a section on what to do if you loose access to both the system and recovery in the '== Important Information about 1.33.0013d ==' section [Its important to read that section anyway if you are using 1.33.0013d]
If you still have access to boot, just use flash_image or rom manager to restore your recovery image.
I'm flashing the dev phone stock rom for the g1 on a canadian ebi1 rogers dream. I've changed my radio to g1 hence i went from ebi1 to ebi0. I have a question though.. Would these be the steps to flash it?
At http://developer.htc.com/
1) download the system image (signed-dream_devphone_userdebug-img-14721 )
2) unzip the zip file on your computer
2) make sure you have a 2.22.* radio less than 2.22.27.08 (2.22.19.26I is the one this rom shipped with)
3) run 'fastboot erase system -w'
4) using the files in that zip run 'fastboot flash boot boot.img' and 'fastboot flash system system.img'
5) boot the phone, you will be on the official google rom
EDIT: I've flashed it succesfully.. Turns out I didn't like the rom.. flashing another..
I downloaded the flashable zip from https://www.androidfilehost.com/?fid=95851846488293411
I use WugToolKit with TWRP, Unlocked and Decrypted. Stock ROM
I'm confused as to how I should flash this, I've read I should just click flash zip in the toolkit and let it finish and done. Also that I could download the file to my phone and use TWRP to flash straight to the phone. Some say backup and some say don't. Also some threads say I need to flash back to factory image, tho this flashable zip should be a factory image of 5.0.1.
Any help will be appreciated. Thank you.
Sent from my Nexus 6
SoCoCapricorn said:
I downloaded the flashable zip from https://www.androidfilehost.com/?fid=95851846488293411
I use WugToolKit with TWRP, Unlocked and Decrypted. Stock ROM
I'm confused as to how I should flash this, I've read I should just click flash zip in the toolkit and let it finish and done. Also that I could download the file to my phone and use TWRP to flash straight to the phone. Some say backup and some say don't. Also some threads say I need to flash back to factory image, tho this flashable zip should be a factory image of 5.0.1.
Any help will be appreciated. Thank you.
Sent from my Nexus 6
Click to expand...
Click to collapse
Apparently the new update OTA or zip will update blocks instead of files so from my understanding, even the slightest change from stock will cause this ZIP to fail when flashing. I'm rooted, decrypted, and changed mixer_paths.xml and as expected the flash failed in TWRP and adb sideload so I'm backing up via Titanium and flashing the 5.0.1 stock. I'll decrypt/root/restore after the flash.
Here are the steps I took to flash the factory image and not lose my settings:
Flash bootloader and radio:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
I then unzipped this file: image-shamu-lrx22c.zip
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
After the phone restarted I then used CF-Auto-Root to re-root my phone. I did not lose any of my settings or installed apps. HTH...
So if I am stock but rooted I cannot sideload the OTA?
I keep getting status 7 error when trying to sideload with ADB using the update OTA.
It actual unzips and installs about 50% and then I get the Status 7 Error
mzimand said:
So if I am stock but rooted I cannot sideload the OTA?
I keep getting status 7 error when trying to sideload with ADB using the update OTA.
It actual unzips and installs about 50% and then I get the Status 7 Error
Click to expand...
Click to collapse
Rooting causes a change to the system partition, so no, you can't sideload the OTA anymore. (not since Lollipop)
stevetrooper said:
Here are the steps I took to flash the factory image and not lose my settings:
Flash bootloader and radio:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
I then unzipped this file: image-shamu-lrx22c.zip
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
After the phone restarted I then used CF-Auto-Root to re-root my phone. I did not lose any of my settings or installed apps. HTH...
Click to expand...
Click to collapse
Worked like a CHAMP!!
:highfive:
stevetrooper said:
Here are the steps I took to flash the factory image and not lose my settings:
Flash bootloader and radio:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
I then unzipped this file: image-shamu-lrx22c.zip
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
After the phone restarted I then used CF-Auto-Root to re-root my phone. I did not lose any of my settings or installed apps. HTH...
Click to expand...
Click to collapse
Are you using nexus toolkit by wug?
Sent from my Nexus 6
SoCoCapricorn said:
Are you using nexus toolkit by wug?
Sent from my Nexus 6
Click to expand...
Click to collapse
No, just used the steps I listed.
SoCoCapricorn said:
Are you using nexus toolkit by wug?
Sent from my Nexus 6
Click to expand...
Click to collapse
No, he used fastboot. Be wary of toolkits. They can do damage that a novice wont be able to fix.
stevetrooper said:
Here are the steps I took to flash the factory image and not lose my settings:
Flash bootloader and radio:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
I then unzipped this file: image-shamu-lrx22c.zip
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
After the phone restarted I then used CF-Auto-Root to re-root my phone. I did not lose any of my settings or installed apps. HTH...
Click to expand...
Click to collapse
Jeezus! perfect!
Thats similar to what I did.
Only thing to do if you are already decrypted is to download this boot file, rename it to boot.img and flash it instead of the one included in the google zip package.
http://forum.xda-developers.com/showpost.php?p=57406510&postcount=360
I had to manually flash each file separately. For some reason when the flash.bat file was running it kept reporting that the system.img file was too big. Not had that before.
dunjamon said:
I had to manually flash each file separately. For some reason when the flash.bat file was running it kept reporting that the system.img file was too big. Not had that before.
Click to expand...
Click to collapse
yeah - since 5.0, the flash-all.bat isn't working for a lot of users.
stevetrooper said:
Here are the steps I took to flash the factory image and not lose my settings:
Flash bootloader and radio:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
I then unzipped this file: image-shamu-lrx22c.zip
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
After the phone restarted I then used CF-Auto-Root to re-root my phone. I did not lose any of my settings or installed apps. HTH...
Click to expand...
Click to collapse
What about the cache.img? do we not flash the cache?
mzimand said:
What about the cache.img? do we not flash the cache?
Click to expand...
Click to collapse
From what I understand, if you flash cache.img, you will go back to stock and lose all of your settings.
Awesome man, worked perfect, you sir rock!
Great!!!!
stevetrooper said:
Here are the steps I took to flash the factory image and not lose my settings:
Flash bootloader and radio:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
I then unzipped this file: image-shamu-lrx22c.zip
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
After the phone restarted I then used CF-Auto-Root to re-root my phone. I did not lose any of my settings or installed apps. HTH...
Click to expand...
Click to collapse
It works like a champ! THX man :good:
stevetrooper said:
Here are the steps I took to flash the factory image and not lose my settings:
Flash bootloader and radio:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
I then unzipped this file: image-shamu-lrx22c.zip
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
After the phone restarted I then used CF-Auto-Root to re-root my phone. I did not lose any of my settings or installed apps. HTH...
Click to expand...
Click to collapse
Excellent, works perfectly as described. Thanks
The only thing that I'd add, to avoid any confusion, is that the factory image can be downloaded from:
https://developers.google.com/android/nexus/images
Thanks again, stevetrooper :good:
stevetrooper said:
Here are the steps I took to flash the factory image and not lose my settings:
Flash bootloader and radio:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
I then unzipped this file: image-shamu-lrx22c.zip
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
After the phone restarted I then used CF-Auto-Root to re-root my phone. I did not lose any of my settings or installed apps. HTH...
Click to expand...
Click to collapse
Curious as to why so many steps?
All i did was flash the radio and system images. Went to 5.0.1 just fine, all settings/data retained.
Didn't flash bootloader, kept unlocked during process, only had to re-root.
Having an issue while flashing system.img file. I flashed radio, and flashed system.img then flashed cf-auto-root. On first start up I was having issues with my radio. LTE was not connecting to T Mobile. So I Nandroid back to stock. Then of course I noticed this didnt change my radio back to stock. Starting everything over, I reflashed radio, reboot bootloader, Flash system.img, reboot bootloader, then fash autoroot. Restart device. Radio was flashed and I had root, but stuck on 5.0 Tried to reflash system.img and I am getting error. "access denied" when flashing. I have read this is an issue with mounting the drive, I have even tried to do this in fast boot but I am coming up with nothing. Any help on this will be greatly appreciated.
theblizzard2010 said:
Curious as to why so many steps?
All i did was flash the radio and system images. Went to 5.0.1 just fine, all settings/data retained.
Didn't flash bootloader, kept unlocked during process, only had to re-root.
Click to expand...
Click to collapse