I rooted my phone only end of last week and am pleased with it, as working fine.
I used SPLHard and engineer recovery testkeys, and because I used jf1.5 i also updated the radio for 1.5 so this is now 2.22.19.26i.
I'm now trying to backup the phone, but can't find the options Alt+B when go into recovery mode to do this
So have I installed the correct stuff or should I be using the engineering SPL and not the Hard SPL, and if so would it have issues seeing I'm running the latest radio stuff
camera+power shows
DREA110 PVT 32B
HSPL10.95.3000
CPLD-4
RADIO-2.22.19.26I
Oct 20 2008
using home+power shows
Android system recovery utility
Using test keys
E:Can't open /cache/recovery/command
Home+Back = reboot
Alt+L = log text
Alt+S = install update
Alt-W = wipe
Now from what others have said there should be Alt+B to perform a Nandroid backup, but I can't find this option anywhere.
The only other thing I've done since rooting the phone is to change bootloader and install Buuf theme.
I also tried settin up the sdcard for Ext2 but again can't find apps2sd, so in the process of putting card back to normal
You need to boot off the modified recovery image. And then, alt-b are buttons on the keyboard, so there is nothing to "find".
lbcoder said:
You need to boot off the modified recovery image. And then, alt-b are buttons on the keyboard, so there is nothing to "find".
Click to expand...
Click to collapse
i've tried doing it both camera+power and home+power
then press alt+b and nothing
so how do i know if the nandroid backup is on the build i have?
walkerx said:
i've tried doing it both camera+power and home+power
then press alt+b and nothing
so how do i know if the nandroid backup is on the build i have?
Click to expand...
Click to collapse
Nandroid is part of the modified recovery image, not an SPL. JesusFreke did not package the modified recovery image with the 1.5 and 1.51 firmwares. Get it here and you'll get your nandroid backup.
mikedmeyer said:
Nandroid is part of the modified recovery image, not an SPL. JesusFreke did not package the modified recovery image with the 1.5 and 1.51 firmwares. Get it here and you'll get your nandroid backup.
Click to expand...
Click to collapse
thanks
downloaded and transfered to phone and installed, rebooted back into recovery, a load of info came up then got the recovery menu with Alt+B and Alt+X, performed backup which said completed
So thanks again
You're welcome. Nandroid puts *.img files in the "Nandroid" subdirectory of your SDCard. You might want to copy them somewhere safe (onto your PC). The important ones are: system.img, data.img, and boot.img. If you ever need to restore them you'll need them on your PC anyway, and you'll need to get fastboot running on that PC.
Once you get fastboot running you can recover from *almost* any firmware flashing disaster. As long as you can boot the phone into fastboot by powering up with the camera button held down, you can restore these backups and bring your phone back to the state it was in when you backed up. Just connect to PC USB and type
fastboot flash system system.img
fastboot flash userdata data.img
fastboot flash boot boot.img
in the PC command prompt. (Obviously you need to be in the same directory as fastboot.exe and the img files, or they need to be in your path)
Where to get fastboot?
http://forum.xda-developers.com/showpost.php?p=3083753&postcount=1
There was no need to write the recovery image. You can put your phone into fastboot and boot off *any* recovery image using "fastboot boot recovery.img" from your regular computer.
lbcoder said:
There was no need to write the recovery image. You can put your phone into fastboot and boot off *any* recovery image using "fastboot boot recovery.img" from your regular computer.
Click to expand...
Click to collapse
There was no need to write it to restore, however to simplify making a nandroid backup there is a need.
Related
So I just got into this stuff last week and have learned quite a bit. I tried various types of images. Accidentally I happened to load the Android 1.6 dev image to my regular G1. Now it wont let me flash anything! It wont let me flash images or even the spl! Please help me!!! How do I get back to cupcake now?
You mean the stock ADP1v1.6 image from developer.htc.com?
First off, you do NOT want to be flashing the SPL. The first thing you should have done is to write the ENGINEERING SPL (ADP1 stock SPL), and then NEVER touch the SPL again.
Now since you managed to write the stock ADP1v1.6 image, I suspect that you already have this (or the uselessly different hack of it called HARDSPL), which means that you have a mode called FASTBOOT (which can be used to write ANY image (in image format, not in update format) to the device. I suggest flashing the RECOVERY partition with cyanogen's recovery image. You can use fastboot to do this. The fastboot binary and instructions on getting into fastboot mode is available at developer.htc.com/adp.html -- the command to use would be "fastboot flash recovery recovery.img".
Note: With a stock ADP1v1.1 or newer, root access is available (yes, stock root), but only via ADB -- this is a SECURITY precaution to prevent malicious apps from hijacking root. If you want to su to root, just need to go in via ADB. So in other words, if somehow you have a stock tmobile SPL that lacks fastboot, then you DO have root access, so you can go in and flash the recovery partition over ADB. What you would do here is copy the recovery.img onto the root of your sdcard and use the flash_image command... i.e. "flash_image recovery /sdcard/recovery.img".
Hi everybody, I unlocked a N1 using fastboot and clockwork recovery. At the time to install the CM6 I encountered and error related to the version of de HBOOT.
I found a guide by Amritttt for reverting HBOOT to 0.33.0012, when I flashed PASSIMG following reboot the screen has become dead.
I tried to re-flash the phone with Amon_Ra recovery (1.8.1 and 2.0) but I can't enter in any mode. The only way I found is entering in the Bootloader and pushing files using fastboot... so I tried to restore the original system using the following:
PASSIMG_Passion_Google_WWE_1.01.1700.1_ERD79_release_signed
Passion-VF-FRF91
with this method: uncompress, flash userdata, system and recovery.
But it did't work, in the last flash the phone hasn't the SIM inside and I realized that the trackball blincked in red two or three minutes after rebooting. So I am wondering if I have a SLCD N1 what can I do to solve this disaster??
thanks!
Look at my signature, go there, see "Unroot/restore your Nexus", reflash EVERYTHING - either with fastboot (and you need to reflash HBOOT too), or do the PASSIMG method - with FRG33, and then upgrade to FRG83.
actually ignore me, that wont work for s-on, yeah, u gunna have to go through the pass-img method, completely reverting back to stock and start from scratch
Thanks, I'll try. I can't use PASSIMG method because my screen ism't working, or there's other way to do?
When you say all, you refer to use "fastboot flash all FRG33" Doing that I reflash alse the HBOOT or I need to do something more?
Thanks
ptrigomou said:
Thanks, I'll try. I can't use PASSIMG method because my screen ism't working, or there's other way to do?
When you say all, you refer to use "fastboot flash all FRG33" Doing that I reflash alse the HBOOT or I need to do something more?
Thanks
Click to expand...
Click to collapse
Can you not get your working hboot.img
boot to fastboot by Powering off
Power on by holding power & Trackball (will take you directly to fastboot)
then do "fastboot flash hboot hboot.img"
bagofcrap24 said:
Can you not get your working hboot.img
boot to fastboot by Powering off
Power on by holding power & Trackball (will take you directly to fastboot)
then do "fastboot flash hboot hboot.img"
Click to expand...
Click to collapse
The hboot files i have are hbootxxxxxxxxx.nb0, it's ok?
bagofcrap24 said:
actually ignore me, that wont work for s-on, yeah, u gunna have to go through the pass-img method, completely reverting back to stock and start from scratch
Click to expand...
Click to collapse
Yeah, but my screen is not working, and ADB is not reconizing the phone. I only can send files using fastboot and the screen is not working
There is a method for doing the pass-img method using fastboot?
or maybe the only problem is the HBOOT?
OK, here we go
Download Latest Amon-Ra
http://forum.xda-developers.com/showthread.php?t=611829
copy it to your android-sdk/tools/ folder and rename recovery.img
boot to fastboot, (Power & Trackball)
open up a shell (cmd prompt) and
cd (path to sdk/tools)
fastboot devices (make sure your device is there)
fastboot boot recovery.img
your phone should boot into recovery image
use your method for flashing through adb now if you can
if you can't then try flashing the korean wwe update
hit enable usb-ms
download this, its a korean FRF91 build. it is known to have the updated 0.35.0017 Hoot in it which i believe has support for slcd displays, http://forum.xda-developers.com/showthread.php?t=722281
copy to your SD
hit trackball to disable usb-ms, go to wipe, wipe all data
then goto flash image from zip,
choose the korean frf91 that you just downloaded hopefully when you reboot you will have updated your hboot again
i tried the baove method but i cannot get the recovery .......i have the same problem my display is dead !! i have gone into recovery but i cant see it and hence cant do a wipe and flash the zip can nyone please help me!!!!
Jack gave you the response you need.
Follow the unroot/restore guide from the wiki, using the PASSIMG method:
http://forum.xda-developers.com/wik...des_&_Tutorials#Unroot_.2F_Restore_your_Nexus
The long to the files is on the word "here" on step 2. Use FRG33.
This is done from the bootloader - you don't need to use recovery...
Sent from my Nexus One using XDA App
actualy i cant see anything cant see fastboot menu nor the bootloader! so i will not be able to do from step 2...please can nyone tell me wad to do?? is my fone bricked?? do i have to giv it to htc??
Its HBOOT, not recovery.
Rusty! said:
Its HBOOT, not recovery.
Click to expand...
Click to collapse
What's HBOOT, not recovery?
Sent from my Nexus One using XDA App
I'm not too experienced in flashing roms so please have some patience with me.
I recently installed the ota update from htc and then unlocked the bootloader through the official htcdev site. I then flashed clockworkmod recovery through fastboot and flashed cm7 through CWM. I'm still running cm7 at the moment.
However, I am now not able to restore my phone back to the stock rom. I tried to restore the stock rom through a backup I did on nandroid in CWM. It went through all the steps and told me that the backup has been successfully restored. But after choosing the reboot phone option, the screen shows the white HTC screen, followed by a black screen for a couple of seconds, then the white HTC screen again, and then it finally brings me to CWM.
I'm not sure what I can do to restore my phone to stock rom. I went back to cm7 and tried to restore using ROM manager but it didn't work out too.
Help please!
Hboot 2.00
Radio 3822.10.08.28_M
(I'm not sure what other info might be needed so just let me know and i'll post it on here)
I have the same issue, I have a feeling about the cause but it is just a brainstrom. I could be wrong.
It might have something to do with ext4 vs ext3 file system. Custom roms usually format your phone in ext4 format while the stock rom only supports ext3
I would try and search a a format script that formats in ext3. (zip file format so you can flash it through clockwork or something)
fallenwout said:
I have the same issue, I have a feeling about the cause but it is just a brainstrom. I could be wrong.
It might have something to do with ext4 vs ext3 file system. Custom roms usually format your phone in ext4 format while the stock rom only supports ext3
I would try and search a a format script that formats in ext3. (zip file format so you can flash it through clockwork or something)
Click to expand...
Click to collapse
Awesome if you do manage to find it please post it
crunchyHTC said:
I'm not too experienced in flashing roms so please have some patience with me.
I recently installed the ota update from htc and then unlocked the bootloader through the official htcdev site. I then flashed clockworkmod recovery through fastboot and flashed cm7 through CWM. I'm still running cm7 at the moment.
However, I am now not able to restore my phone back to the stock rom. I tried to restore the stock rom through a backup I did on nandroid in CWM. It went through all the steps and told me that the backup has been successfully restored. But after choosing the reboot phone option, the screen shows the white HTC screen, followed by a black screen for a couple of seconds, then the white HTC screen again, and then it finally brings me to CWM.
I'm not sure what I can do to restore my phone to stock rom. I went back to cm7 and tried to restore using ROM manager but it didn't work out too.
Help please!
Hboot 2.00
Radio 3822.10.08.28_M
(I'm not sure what other info might be needed so just let me know and i'll post it on here)
Click to expand...
Click to collapse
fallenwout said:
I have the same issue, I have a feeling about the cause but it is just a brainstrom. I could be wrong.
It might have something to do with ext4 vs ext3 file system. Custom roms usually format your phone in ext4 format while the stock rom only supports ext3
I would try and search a a format script that formats in ext3. (zip file format so you can flash it through clockwork or something)
Click to expand...
Click to collapse
With the unlocked bootloader, when the device is in recovery mode, it cannot overwrite the boot.img partition. So when you flash a custom ROM in CWM, you must manually extract the boot.img file from the zip file and flash it manually in Fastboot mode using the command:
fastboot flash boot boot.img
In the case when you are attempting to restore a previous backup, the same is true, except in this case you would manually flash the boot.img from the CWM backup folder in Fastboot mode.
This should solve both of the situations you have encountered.
Okay that method worked a charm. Just flashed back the stock rom.
Thanks for much for that!
crunchyHTC said:
Okay that method worked a charm. Just flashed back the stock rom.
Thanks for much for that!
Click to expand...
Click to collapse
Weird, didnt work for me. Dit you manually flashed the boot.img extracted from the nandroid backup?
Yup. So i took the backup from my sd card and put the backup onto my computer. Then I used clockworkmod recovery to restore the backup, and then used fastboot on the computer to manually flash boot.img through usb.
Hope that helps
Cannot restore with the procedure.
I have been trying to restore stock rom but I'm unable to do it.
I flashed boot.img using command prompt.
Restored it via Clockworkmod recovery but after restoring when i reboot the phone, it again takes me to recovery mode.
What should I do?
Maybe it is because you have changed the backup name.. I heard that if you change the stock from backup name you will wreck the md5sum ...
___________________________
Device: HTC Incredible S
Bootloader: S-OFF - ENG
Rom: ARHD 2.2.0
Android for life!
NicOsol said:
Maybe it is because you have changed the backup name.. I heard that if you change the stock from backup name you will wreck the md5sum ...
___________________________
Device: HTC Incredible S
Bootloader: S-OFF - ENG
Rom: ARHD 2.2.0
Android for life!
Click to expand...
Click to collapse
No..I have not changed anything.
I even tried formatting it in ext3 using Touch recovery and then tried to back up..but it didn't work.
It just keeps on taking me to recovery mode when I reboot.
Why don't you guys get s-off? I'll post a link when I'm on my PC on how to do it. That way, you won't have to flash the boot.img each Time you install a new rom...
Sent from my HTC Incredible S using XDA
tpbklake said:
With the unlocked bootloader, when the device is in recovery mode, it cannot overwrite the boot.img partition. So when you flash a custom ROM in CWM, you must manually extract the boot.img file from the zip file and flash it manually in Fastboot mode using the command:
fastboot flash boot boot.img
In the case when you are attempting to restore a previous backup, the same is true, except in this case you would manually flash the boot.img from the CWM backup folder in Fastboot mode.
This should solve both of the situations you have encountered.
Click to expand...
Click to collapse
Hello, I tried with "fastboot flash boot boot.img" took the boot.img from the backup and then I did a restore but it always goes into recovery mode, what else can I do?
I apparently flashed a bad .zip file that won't load, and now all I can do is sit at the Motorola logo. I've tried the hard reboot with power+vol up and down but, for whatever reason, that won't reboot to the bootloader like it used to. So, I can't get back into recovery at the moment. I can ocassionally get it to reboot to the fastboot menu, but I don't know what commands or anything to use to get me back to recovery. If I could just get back to the recovery I would be fine because I have a few older ROM zips I could flash.
Can anyone give me some advice on what to do here? My computer has ubuntu, so I'm not sure if Myth tools or anything would work?
Parham112 said:
I apparently flashed a bad .zip file that won't load, and now all I can do is sit at the Motorola logo. I've tried the hard reboot with power+vol up and down but, for whatever reason, that won't reboot to the bootloader like it used to. So, I can't get back into recovery at the moment. I can ocassionally get it to reboot to the fastboot menu, but I don't know what commands or anything to use to get me back to recovery. If I could just get back to the recovery I would be fine because I have a few older ROM zips I could flash.
Can anyone give me some advice on what to do here? My computer has ubuntu, so I'm not sure if Myth tools or anything would work?
Click to expand...
Click to collapse
You can do the following while on bootloader (Volume DOWN + Power button):
fastboot flash recovery recovery.img
Where recovery.img is your custom recovery image. Just make sure is in the same folder that your fastboot archive. After this, you should be able to access to recovery and flash another ROM.
OR... You can flash to stock with RSD Lite and then do everything again.
Use Myth Tools to flash stock ROM or recovery.
My phone is almost bricked
I was trying to install sevenrov v3.2 while i was on v3.1 and i ****ed up everything while doing a fullwipe
Right now there is only fastboot&rescuemode available
twrp is not working, because it does no read the digitizer(i cannot press anything)
i can install cwm but should i ?
I believe that is best to flash images through fastboot.
But what images should i flash?
Where to find them?
How should i flash them?
revery0 said:
My phone is almost bricked
I was trying to install sevenrov v3.2 while i was on v3.1 and i ****ed up everything while doing a fullwipe
Right now there is only fastboot&rescuemode available
twrp is not working, because it does no read the digitizer(i cannot press anything)
i can install cwm but should i ?
I believe that is best to flash images through fastboot.
But what images should i flash?
Where to find them?
How should i flash them?
Click to expand...
Click to collapse
Oh dear! You are in a mess. All I can suggest is that you flash the stock recovery and then install a stock ROM for your phone using the force update (dload) method that has been described in other threads. Then you can return to a custom ROM of your choice. As far as I know CWM for this phone is only in Chinese so it may be of little value unless you understand the language.
arthios said:
Oh dear! You are in a mess. All I can suggest is that you flash the stock recovery and then install a stock ROM for your phone using the force update (dload) method that has been described in other threads. Then you can return to a custom ROM of your choice. As far as I know CWM for this phone is only in Chinese so it may be of little value unless you understand the language.
Click to expand...
Click to collapse
cwm has english also but it has no use for me
Only fastboot works
dload method does not complete, the blue progress bar goes up to to 85% and stays there forever...
I am looking for a mathod to create a flashable zip for fastboot
to use fastboot flash filename.zip command
or flash each partition seperatly , i tried the method with huawei extractor
extracted the images system,root,boot,cache,cust,userdata
flashed each one on their partitions
but without success
revery0 said:
cwm has english also but it has no use for me
Only fastboot works
dload method does not complete, the blue progress bar goes up to to 85% and stays there forever...
I am looking for a mathod to create a flashable zip for fastboot
to use fastboot flash filename.zip command
or flash each partition seperatly , i tried the method with huawei extractor
extracted the images system,root,boot,cache,cust,userdata
flashed each one on their partitions
but without success
Click to expand...
Click to collapse
Why you do not flash twrp recovery in fastboot mode and then install a flashable ZIP?
Edit:
In this thread, are the same probs:
http://forum.xda-developers.com/showthread.php?p=56634210
Short: install recovery and try to flash a rom again.
I See your post in this thraed that this not work for you but i think you have to try it again. In fastboot mode you can flash recovery and cust. Its that working?
Can you explain step by step what are you doing?
87insane said:
Why you do not flash twrp recovery in fastboot mode and then install a flashable ZIP?
Edit:
In this thread, are the same probs:
http://forum.xda-developers.com/showthread.php?p=56634210
Short: install recovery and try to flash a rom again.
I See your post in this thraed that this not work for you but i think you have to try it again. In fastboot mode you can flash recovery and cust. Its that working?
Can you explain step by step what are you doing?
Click to expand...
Click to collapse
First of all thank you,
Right now my phone is in a bootloop(not more than 6 sec duration, with short vibration)
3 buttons , power button tricks and combos don't seem to work
The only way to exit the bootloop is by sending the fastbbot reboot recovery command and wait for some loops while you are doing the vol+vol-power combo
Then the phone enters fastboot rescue mode
I get reply when sending the fastboot devices command,
And the phone has unlocked bootloader (OEM command)
I can flash images extracted from the official 135 ROM
I tried cust boot user data system cache recovey , and the are all flashed correctly
But I can't get into recovery mode aftethe reboot (yes I am doing the 3 buttons trick)
I tried different SD cards with different update.app each time, from b135 official and sevenrom3 (yes I put them in /dload folder)
I even tried flashing cwm and twrv recovery images in the recovery partition, but I got in a bootloop after the reboot again
So I am asking if there is anyway to flash the partitions correctly from fastboot or maybe send a kernel image with some offset and run it with the fastboot command
Of course adb does not work, not responding
Maybe reparation the storage?
I don't know
And I am desperare...
revery0 said:
First of all thank you,
Right now my phone is in a bootloop(not more than 6 sec duration, with short vibration)
3 buttons , power button tricks and combos don't seem to work
The only way to exit the bootloop is by sending the fastbbot reboot recovery command and wait for some loops while you are doing the vol+vol-power combo
Then the phone enters fastboot rescue mode
I get reply when sending the fastboot devices command,
And the phone has unlocked bootloader (OEM command)
I can flash images extracted from the official 135 ROM
I tried cust boot user data system cache recovey , and the are all flashed correctly
But I can't get into recovery mode aftethe reboot (yes I am doing the 3 buttons trick)
I tried different SD cards with different update.app each time, from b135 official and sevenrom3 (yes I put them in /dload folder)
I even tried flashing cwm and twrv recovery images in the recovery partition, but I got in a bootloop after the reboot again
So I am asking if there is anyway to flash the partitions correctly from fastboot or maybe send a kernel image with some offset and run it with the fastboot command
Of course adb does not work, not responding
Maybe reparation the storage?
I don't know
And I am desperare...
Click to expand...
Click to collapse
Okay...
your system is so messy. we must bring fully to factory condition first time.
Plesse try to flash stock recovery img. (In your post you write only that you have tryed twrp/cwm).
And then try update in recovery.
I not think your phone is broken. You can try my tool (http://forum.xda-developers.com/asc...eandadjust-t2941186/post56774286#post56774286). There is a stock recovery img in it. In your case you have to flash cust img to.
87insane said:
Okay...
your system is so messy. we must bring fully to factory condition first time.
Plesse try to flash stock recovery img. (In your post you write only that you have tryed twrp/cwm).
And then try update in recovery.
I not think your phone is broken. You can try my tool (http://forum.xda-developers.com/asc...eandadjust-t2941186/post56774286#post56774286). There is a stock recovery img in it. In your case you have to flash cust img to.
Click to expand...
Click to collapse
Thank you but I already did flash the official recovery image, both extracted from a factory update.app and your recovery.IMG also... None of them worked.... Iam still in the same bootloop.
I am starting to believe that the partitions have been ****ed up.
Any way to repartition?
Also is there a procedure to create a flashable zip with huawei software extractor? I edited the accompaning XML to add the p7 device on the list (copy data from p6 and changed the name) created the zip but fastboot doesn't flash the zip because its missing 2 XML files which I can't remember their name.
And at this point I would like to give my 2 cents of advice to everyone who might listen,
Before you flash anything from a microsd, first verify the card with h2testw, and always use high quality microsd and never ever stop a flashing procedure by any means. . i would like to make it more extreme and advise to use a software with copy verification (like richcopy) when you copy files that are going to be flashed.
I tend to believe that a faulty microsd is the cause of my problems... Even though I checked the microsd afterwards and didn't got any errors.
I would advise the ROM creators to append this on their posts!