I'm doing a device swap. I'm running CM6.1 RC1 on my AMOLED N1, and I know it's also compatible with SLCD. Currently the AMOLED phone still has the old HBOOT (0.33.0012 I think). I'm assuming the replacement device could end up being SLCD (which is fine by me).
Now that ClockwordMod 2.5.11 is compatible with SLCD, I was thinking I'd do a full nandroid backup from the AMOLED phone and restore it to the SLCD phone.
However I noticed that Clockwork takes a backup of boot.img as part of the process. If I restore this nandroid to the SLCD phone, will it downgrade the HBOOT to 0.33.0012? And more importantly, is this going to mess up the phone? I seem to remember reading something along the lines that if you downgrade HBOOT on an SLCD N1, not only will the screen fail to work in the bootloader, but it may fail to work in the recovery and OS as well.
Would I be safer to do an "advanced restore", and restore every partition *except* boot?
boot.img isn't HBOOT, it's part of the system. HBOOT is a whole different thing, and you can't back it up, only take one from stock distribution ZIP.
Jack_R1 said:
boot.img isn't HBOOT, it's part of the system. HBOOT is a whole different thing, and you can't back it up, only take one from stock distribution ZIP.
Click to expand...
Click to collapse
Right okay, my mistake. The "revert HBOOT" instructions seem to indicate that the only way to revert it is by PASSIMG, and I presume the use of flash_image to misc is just so that it doesn't fail the version check.
Thanks =)
Pardon my ignorance, but I'm about to do the device swap as well.
So is this to say that a backup from an AMOLED device will, indeed, work on the SLCD variant?
Depends on the ROM you're using. Once you root, and flash Clockwork 2.5.11, take a nandroid backup of the original configuration - that's your way out if you flash an incompatible ROM.
Sent from my Nexus One using XDA App
Well, in the end my swap device was AMOLED, so moot point. It was running FRF91, I rooted it with VISIONary, and my nandroid backup restored just fine. The only unhappy apps are Swype (will reinstall) and Shazam (have to email them to transfer unlimited tagging).
Sent from my Nexus One using XDA App
Related
Hello, I have an original ADP1, updated to the latest official HTC images
I have:
radio: ota-radio-2_22_19_26I.zip*
recovery: signed-dream_devphone_userdebug-ota-148830.zip*
I want to be able to install other ROMs, like the ones offered in "Android Development".
There are a lot of guides out there on how to do that, my problem is that I want to do a nandroid backup first, before doing any flashing.
For doing a nandroid backup, I understand that I either
1) need to flash a special recovery image so I don't need a PC to restore the backup,
OR
2) Have busybox installed, and run nandroid.sh from recovery mode.
Correct so far?
I wanted to go with option 2), since I can perform a backup before flashing anything on my device. The only problem is that I don't have busybox installed.
I have seen a busybox build (over here http://benno.id.au/blog/2007/11/14/android-busybox ) which is 1.8MB because it is presumably compiled against libC, and have read here that jesusFreke was building one with bionic.
Is the bionic version anywhere to download? I suspect its in newer roms, but I *do not* want to flash a rom just to have busybox, since i only want busybox so I can perform nandroid updates before doing any flashing.
I understand that after having busybox, I just push it into /usr/xbin, --install, and nandroid will just work?
Anyone got a download to the latest, most stable and complete busybox? I would prefer one compiled for android (linked against bionic, etc..)
(what busybox version do you guys use?)
Thanks for your help and sorry for the LONG POST!
Superken7 said:
Correct so far?
I wanted to go with option 2), since I can perform a backup before flashing anything on my device. The only problem is that I don't have busybox installed.
Click to expand...
Click to collapse
I can't address most of your post, but there's a flaw in your reasoning that might make it a moot point.
Nandroid won't backup the recovery image - only the primary OS and data. So making a backup using Nandroid on your stock device won't be any different than installing a modified recovery, then backing up your device.
Really, installing the recovery is a trivial activity with little* risk of damaging your phone.
*No guarantees in life, but I wouldn't worry one bit about it.
Thanks for the quick answer!
I guess i'll look for a recovery image that fits my needs then
Let me suggest Cyanogen's Recovery 1.3.1 - As far as I know, the only one with both Nandroid backup and restore. Also has USB mount, really handy for loading updates if your device is fubared and you don't have a card reader.
http://forum.xda-developers.com/showthread.php?t=523558
Grr, double post.
Yay thanks!
I guess there are no compatibility problems between recoverys? I mean, just like you need a certain radio version in order to update the SPL, are there any compatibility requirements for that recovery? I don't see any of that in that post, but just in case.. =D
thanks again!! =D
DOUBLE KILL! erm... double post!
I'm not the only one cursed with the double posting, huh?
No, no issues with using any combination of recovery with certain ROMs, SPL, radio, etc.
You're welcome, and good luck.
X10 ?Mini Pro
Works like a charm
when you install titanium backup from the market it will download an actual busybox after first start. maybe you can try this one?
you can use Titanium Backup to update it
i'm about to root yet another device, yay!
this idea may have already been discussed, but... if i'm able to get to the jf/cyanogen recovery console, can i restore a nandroid backup without fully letting the new install process complete?
what...?
you mean you want to bork an update and then restore your nandroid?
i wouldnt recommend it but it should work fine
I have heard in many occassions for those that had bricked their phones were able to do a nandroid restore on their freshly rooted devices. I haven't tried it before but obviously you want to make sure you have the radio updated first followed by whatever spl you were using. Flash the Cyanogen or Amon_Ra recovery file and you should be good to go. If you play your cards right, you might even be able to use switchrom to backup/restore the apps too.
Hey all so I currently have an unlocked bootloader, rooted Nexus One still running the Stock Froyo 2.2.2. and I decided to finally upgrade to the OTA Gingerbread update but have a problem.
The OTA update restarts my phone with a triangle with an "!" inside it and an Android next to it, so I decided to try a manual update as described here.
Everything went well until the installation itself, during the install I kept getting some sort of error stating Twitter.apk in the system directory could not be authenticated.
So here's the problem, with Titanium Backup I made the stupid mistake of uninstalling it and not backing it up when I first rooted a while ago. I thought I could just reinstall it from the market but I get the same error. The only solution I can think of is if someone running a Nexus One Stock Froyo could possibly send me the Titanium Backup files of Twitter, hopefully this would make it work, otherwise I don't think I could ever update.
Since your bootloader is unlocked, you can use fastboot to install a custom recovery and then flash whatever you want (including a stock image)...
Sent from my Nexus One using XDA Premium App
danger-rat said:
Since your bootloader is unlocked, you can use fastboot to install a custom recovery and then flash whatever you want (including a stock image)...
Sent from my Nexus One using XDA Premium App
Click to expand...
Click to collapse
Thanks for the response, but I'm having trouble figuring some of this stuff, after spending some time with the search option here in XDA:
1. I don't the difference between custom recovery and flashing an image.
2. I can't find a simple stock Gingerbread image (thought its called ROM?) Details in posts tend to be vague for people that are learning this stuff, like me.
3. Many people have written to use Amron_ra 2.2.1 but I don't know the specifics of each ROM are (ex. if its Froyo based, Gingerbread based, etc.)
4. Would using ROM Manager be a good method to use any ROM or is it limited?
I'm essentially looking for an effective method to upgrading to a clean Gingerbread, since doing it the normal way won't work on my phone (as stated in my first post).
1 - Recovery, bootloader, and 'ROM' are two different partitions on you phone. Once you break security on one, you can use it to break the security on the other. In your case, the security on your bootloader is broken (unlocked), so you can use it to install new software on the other partitions.
2 - See bullet 4 on the first post of this thread:
http://forum.xda-developers.com/showthread.php?t=1005591
3 - For recovery you have 2 choices, Amon Ra or Clockwork, If you go with Clockwork, I recommend you stay away from 3.x versions. Unless the ROM you want to install says otherwise, either of these recoveries will work.
4 - ROM Manger will work. It's an easy way to achieve results, but unless you know what you are doing, it's also an easy way to screw things up.
I suggest you take it a step at at a time, and really understand what you are doing. Reading the wiki is always a good start, then ask specific questions...
http://forum.xda-developers.com/wiki/index.php?title=File:Nexus_One.png
Thanks Danger, I made the jump to Cyanogen 7, RC-4 via ROM Manager and couldn't be happier! Only problem is the known audio bug for Nexus One (person on other end of a call hears a lot of static sometimes, and have to recall them). The forced apps2sd is by far my most favourite feature, especially since the N1 internal space is pretty horrible, I've moved most of my apps2sd and haven't had any problems thus far.
Thanks for recommending CM7, I just wish their website listed the full features for newbies like me.
Thanks danger-rat http://www.nexusoneforum.net/forum/...lick-doesnt-work-gingerbread-2.html#post93952
I downgraded my gingerbread to froyo
Was pulling my hair out with a lame guide in the general section
Congrats!!
Sent from my Nexus One using XDA Premium App
I wanted to flash cm5 for a variety of reasons (moving from cm4, so I have some experience on the matter)
The thing is< I don't want to flash a custom spl, don't want to brick my phone, it's my only one, but have found the firerat partition method and was wondering how to proceed with the matter.
I know how to recover from a soft brick, and have nandroid backups made with cm recovery 1.4.
Anyone have any expertise on the subject?
Make a nandroid, wipe clean, flash new ROM and gapps
What's your current radio/bootloader?
Sent from my Nexus 4 using Tapatalk 2
demkantor said:
Make a nandroid, wipe clean, flash new ROM and gapps
What's your current radio/bootloader?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I have no idea what my radio version is, but I have a stock bootloader, and I'm currently unwilling to flash that because the risks are so high, but I've tried just flashing the update, and it soft bricked my phone; the really bad thing it did was partition /system in a way that nandriod didn't work, and I had to flash rc29 and repeat the procedure to even get cm4 working. My signature probably has most of the info that you'll need to see what hardware/software configuration I have. Thanks for being an such an active help demkantor!
edit: no signature with that info anymore, and it had already changed, so to rephrase: I just had stock.
Can't see SIG on app, but the risks are minimal on flashing firmware so long as you know what you're doing
I used to buy and sell g1s and have fully upgraded close to 100 of them, never damaged one
Just use fastboot when possible, check md5sums, always flash radio then bootloader, just be sure you follow proper steps and all is safe
If you want any newer ROMs you will be forced to update and it literally takes less then ten minuets to go from pure stock to fully updated phone running gingerbread or whatever. And most of the froyo and gingerbread ROMs run better than older ones especially with the ram hack
Sent from my Nexus 4 using Tapatalk 2
demkantor said:
Can't see SIG on app, but the risks are minimal on flashing firmware so long as you know what you're doing
I used to buy and sell g1s and have fully upgraded close to 100 of them, never damaged one
Just use fastboot when possible, check md5sums, always flash radio then bootloader, just be sure you follow proper steps and all is safe
If you want any newer ROMs you will be forced to update and it literally takes less then ten minuets to go from pure stock to fully updated phone running gingerbread or whatever. And most of the froyo and gingerbread ROMs run better than older ones especially with the ram hack
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I have heard a lot about fastboot, what is it and how do I enter it?
Its mode within bootloader that allows for communication between phone and PC, kinda like adb
Some of the bootloaders for the dream have limited fastboot commands available so you'll have to read dream specific threads to see which have what
Here is some help to set up and use it though
http://forum.xda-developers.com/showthread.php?t=2277112
Sent from my Nexus 4 using XDA Premium 4 mobile app
I know that many people have flashed it with a great deal of ease, however, I have no replacement, no local jtag as a possibility, and no interest in buying a new one. If you could give me detailed instructions along with working, easy to use, links to anything required, then that would be really great. If you have a way that I could preserve the data for my apps, then that would be even better!:fingers-crossed::victory:
What would you like help with, flashing cm5 or changing radio/SPL
Also write down all info on bootloader screen and let me know current recovery and ROM youre on
Sent from my Nexus 4 using XDA Premium 4 mobile app
I want reliable help with both.
The information that I could gather from the bootloader is:
DREA100 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-2.22.19.26I (P.S. the last character is an "eye", not a one or an L)
SEP 2 2008
_____________________
I flashed update-cm-4.2.15.1-signed.zip to get my current ROM, even though I have some custom mods, so it can't technically be considered more than based off of cyanogenmod.
I am running the cyanogen+JF recovery as my current recovery. I have heard of a partition re-sizer made by firerat, but have no indication of its reliability. if you have a fail-safe way of flashing cm5, of even cm6, then that would be great!:fingers-crossed::victory:
ok so here are your steps
boot to recovery and make a backup
now flash Danger SPL from recovery
now boot back to bootloader and see that you have .26i radio and .2005 SPL (not needed step but good to see this)
The preferred thing to do is flash the .13d spl with a compatible radio but we can save this until later
For now we will go through these next steps:
boot to recovery and flash THIS SUPER WIPE SCRIPT (always a good idea between flashes)
and I'm OCD when it comes to wiping clean so also wipe all in recovery
Now flash CM5 ROM
and the flash GAPPS in recovery
when all is done reboot ---- profit
also consider using THIS RECOVERY just my preferred one for the dream
Let me know if you need further help
The links to cm5 and gapps seem to be dead, but I'll find them elsewhere. And, are you sure that there is no possibility of a hard brick while doing this? If I killed this phone, then I would be out of luck for at least 6 months.
does superwipe wipe recovery and hboot as well?
These forums are almost as good as live support!
Superwipe wipes and formats system/data/cache/boot not recovery or hboot
If you can't find cm5 or gapps let me know and I'll upload them
Flashing bootloaders through recovery is dangerous so always check md5sum and once you have the .2005 hboot you will be able to use fastboot for all your firmware flashing needs
Having said that I have flashed that .zip literally over 100 times with never a brick (used to sell rooted phones on eBay) but choice is yours
Sent from my Nexus 4 using XDA Premium 4 mobile app
So you're saying both that it is dangerous and that you recommend doing it? P.S. Please excuse the immaturity of this, it's just that this is really exciting, as my first android is about to get a really major update.
Will the superwipe wipe the ex2 partition on my sd? Or will I have to make a copy?
DREAMWAVE_devteam said:
Will the superwipe wipe the ex2 partition on my sd? Or will I have to make a copy?
Click to expand...
Click to collapse
I would do the upgrade, it is safe so long as you follow proper instructions
download all files
check md5sums
make sure you meet all requirements (ie radio matches new spl - you're good here)
place all needed files on root of sd
yes it wipes ext partition, you can always extract contents of any mod/rom/whatever
if you're not sure - look through an updater-script if its flashable (this is) and see what it does
you will see it runs SuperWipe.sh - in here you see it wipes boot/cache/data/system/sd-ext (not fat32 partition) and .adroid_secure
I use this same superwipe each time i flash a new rom to my g1, its good (always make nandroid in recovery first)
and yeah, first time you do anything new like this it's scary/exciting but knowing that thousands upon thousands have successfully done this
you'll be just fine
best of luck!
Is it possible to do it without erasing the ext partition? Maybe just wiping with the recovery wipe data? It will mean that I will have to find my sd adapter if I have to copy the ext partition.
Maybe you misunderstand, it won't remove the partition altogether it will just remove contents which is a good idea when moving to a new ROM, the backup you made will backup contents of ext partition and can be restored at a later point if needed
Sent from my Nexus 4 using Tapatalk 2
I've seen a lot of tutorials on how to do this say that I need to flash hardspl. is this correct?
Bad boyz current rom
Updated firmware
Super CID
Rooted (obviously)
S-off
adb reboot-works
adb reboot recovery-works
adb reboot bootloader-works
Fastboot reboot- works
fastboot oem rebootRUU- works
RUU-no worky, says usb device not attached even with current htc drivers
Google unable to connect to server after wipe cuz i turned blinkfeed back on and had to push OK a gizzilian times due top FC and did factory reset.
I can go to dropbox thru browser and install app backup/restore and than restore all apps, but it still fails to connect to google servers as i input info from new device (custom rom) and want to start fresh. I dont care if it wipes internal storage (learned long ago how to keep nothing on device that can't be restored off device)
Yes i wiped everything twice (except system and storage, been there done that nightmare)
So.... Bone stock (any version) rom that can be flashed in recovery......
Barebones back to stock is going to require an RUU. Did you make a nandroid of stock before you rooted the phone or is that how you got it?
If you're looking for rooted stock for most recent 5.03.651.3 rom, go here: http://forum.xda-developers.com/showthread.php?t=2766604
MFOsaka said:
Barebones back to stock is going to require an RUU. Did you make a nandroid of stock before you rooted the phone or is that how you got it?
If you're looking for rooted stock for most recent 5.03.651.3 rom, go here: http://forum.xda-developers.com/showthread.php?t=2766604
Click to expand...
Click to collapse
Nope, i'm looking for 100 persent stock RUU bone stock RUU flasable in recovery.
I'm going to go back to roots (and i don't mean ROOTED)
Let's say htc evo. You could take the RUU and extract it in rar, now adays it would be 7zip, take the rom and name it to pmg.3400(example) and put it on sd card, then flash it in bootloader. That no longer exists. I have the vary first bone stock htc one sprint rom, and have extracted rom.zip from it, and it wont flash from recovery. I need to.
Looking for old timers who know what to do with this. I don't want rooted version that will flash in recovery, i have that already and fighting to pull stock OTA update out of it to flash in recovery. There has to be someone here that has had the 1st edition sprint android (hero, or evo 1st edition) that knows what i'm talking about.
Yeah, that's the unfortunate side effect of these phones and no longer have an SD slot. And believe me, I remember the Supersonic days. OG EVO was my first HTC device. EVO LTE after the fact and now this phone. Tinkered with other HTC models for other folks as well.
There is an offchance that having SuperCID not matching for Sprint could be a culprit too. I was checking out a few threads about that after I read your reply. As far as some help from someone that is savvy with the M7... BD619 knows his stuff. PM him.