To Flash****UPDATED******
- Boot into safestrap
-Select safe system
-toggle safe system on
(It seems we have an issue wiping the safe strap /data and /cache so these additional steps are needed for now)
-quick toggle safe system off *****MUST BE A QUICK TOGGLE*****
-wipe data/factory reset
(To be safe wipe the following)
-Wipe Cache partition
-format /system
-wipe dalvik cache (Found a bug in safestrap that prevents us from wiping dalvik cache see thread)
-quick toggle safe system on *****MUST BE A QUICK TOGGLE*****
Now, flash the rom. (Selecting external Sdcard)
Safestrap works alot like a dual boot, so you can always return to your stock system by simply disabling safestrap in the safe boot menu.
http://forum.xda-developers.com/showthread.php?t=1425026
This is ics for the droid 3 by hashcode, same guy that gave us permission to unofficially port and support safestrap. It does boot and work on our phones.
This is what i know for sure right now
-Wifi works
-Most tasks and apps work
-market is broken
-calling/texting is broken, looks like its stuck on cdma?
-accelerometer is broken
What I'd like to see from here is some one willing to take over my project on this rom. I have a few of my own flash able zips complied with various tweaks to hopefully be able to make and receive calls, no success yet. I will keep trying but this is a project better suited for some one who is not so new to the linux environment. (I just got my first linux box 2 weeks ago)
Please enjoy and the thanks button is below the download link
http://forum.xda-developers.com/showthread.php?t=1425026
Proof It works! http://youtu.be/B_J3fs80dV0
**************-Edit*************************************************************************
I have decided to take on this project. I will post a more "ported" version as I progress on it, These things take time so please be patient. The information contained above should only be used as a "prof of concept" sort of thing. Anyone willing to help may do so here: http://forum.xda-developers.com/showthread.php?t=1428117
Great work !!! Thank you very much!!! Waiting the update!!
Don't we need the source code for the Atrix 2 to make this work?
I've followed all the steps in safestrap, got it working, except mounting SD (is that expected?), but after I flash the CM9 zip while in safe mode, I reboot and get stuck with a black screen. Anyone else get this working? It seems to flash rather fast which seems abnormal to me.
I agree that this Alpha 4 is stuck on CDMA. If anyone has gotten 3g to work, please let me know how you did it. I tried entering their little trick *#*#4636#*#*, rebooted, wiped cache and dalvik like they said and still nothing.
lfaber06 said:
Flash this using safestrap only.
To Flash
Boot into safestrap
Select safe system
toggle safe system on
wipe data/factory reset
(To be safe wipe the following)
Wipe Cache partition
format /system
wipe dalvik cache
Now, flash the rom. (Selecting external Sdcard)
Safestrap works alot like a dual boot, so you can always return to your stock system by simply disabling safestrap in the safe boot menu.
http://forum.xda-developers.com/showthread.php?t=1425026
This is ics for the droid 3 by hashcode, same guy that gave us permission to unofficially port and support safestrap. It does boot and work on our phones.
This is what i know for sure right now
-Wifi works
-Most areas of the phone work
-phone is broken, looks like its stuck on cdma?
What I'd like to see from here is some one willing to take over my project on this rom. I have a few of my own flash able zips complied with various tweaks to hopefully be able to make and receive calls, no success yet. I will keep trying but this is a project better suited for some one who is not so new to the linux environment. (I just got my first linux box 2 weeks ago)
Please enjoy and the thanks button is below the download link
http://forum.xda-developers.com/showthread.php?t=1425026
Click to expand...
Click to collapse
Have you tried replacing /system/lib/hw, /system/etc/bluetooth, /system/etc/firmware, and /system/etc/ppp, and /system/etc/wifi, with the directories from our ROM, also try replacing /system/app/TelephonyProviders.apk, with the one from our ROM?
That might actually work. That is what I have done for the one I am working on, we shall see how far that gets me..... I had read someplace, that those are very important, right after the radio image, for proper hardware operation on a phone with another ROM.
Jim
Why can't I get this to boot? I go into safestrap, put it on safemode, wipe all the necessary things, flash the zip, reboot, and I get a black screen. If I take it off safe mode it goes back to my stock ROM successfully.
Calundle said:
Why can't I get this to boot? I go into safestrap, put it on safemode, wipe all the necessary things, flash the zip, reboot, and I get a black screen. If I take it off safe mode it goes back to my stock ROM successfully.
Click to expand...
Click to collapse
Try this. Using safestrap, make a Full backup Including webtop to be safe. then disable safe mode and factory reset, then wipe dalvik cache, then format /system, then wipe /data, enable safe mode, flash it, and let me know.
lfaber06 said:
Try this. Using safestrap, make a Full backup Including webtop to be safe. then disable safe mode and factory reset, then wipe dalvik cache, then format /system, then wipe /data, enable safe mode, flash it, and let me know.
Click to expand...
Click to collapse
Alright I'm trying it as we speak. So is the SD card currently unmountable in safestrap? If I do a backup while in safemode, won't that backup the safemode ROM, which is the CM9 one I can't get to work? I don't really understand how the safemode/no safemode works. I was under the impression that my stock ROM is under no safemode so anything I do with safemode off will effect that (meaning when I do the format and wipes you're talking about it would do that to my stock ROM), then when I turn safemode on everything I do effects the other ROM. Can you clarify for me?
Calundle said:
Alright I'm trying it as we speak. So is the SD card currently unmountable in safestrap? If I do a backup while in safemode, won't that backup the safemode ROM, which is the CM9 one I can't get to work? I don't really understand how the safemode/no safemode works. I was under the impression that my stock ROM is under no safemode so anything I do with safemode off will effect that (meaning when I do the format and wipes you're talking about it would do that to my stock ROM), then when I turn safemode on everything I do effects the other ROM. Can you clarify for me?
Click to expand...
Click to collapse
Not exactly..... safestrap knows which ROM is your stock system, and which one is the "safestrap". It calls your stock rom /systemorig or something similar, and then when in safe mode, it will mount the stock system to /systemorig and back that up as well as /system, which will be the CM9 rom, that is why you had to partition your card a certain way, to make this work right.
jimbridgman said:
Not exactly..... safestrap knows which ROM is your stock system, and which one is the "safestrap". It calls your stock rom /systemorig or something similar, and then when in safe mode, it will mount the stock system to /systemorig and back that up as well as /system, which will be the CM9 rom, that is why you had to partition your card a certain way, to make this work right.
Click to expand...
Click to collapse
Ah thanks for the explanation. So, when you backup it does a backup of both system and systemorig, both roms, how do you go about wiping one rom and not the other? Am I correct in saying if you have safemode off and do wipes/restores it will do that to your stock rom, but if it's on it will do it to the systemorig one, then backing up with it off does a backup of stock rom, and when it's on it backs up both?
Calundle said:
Ah thanks for the explanation. So, when you backup it does a backup of both system and systemorig, both roms, how do you go about wiping one rom and not the other?
Click to expand...
Click to collapse
Safestrap will only allow you to wipe your non safe data. it will not let you wipe your safe system aka "stock rom".
lfaber06 said:
Safestrap will only allow you to wipe your non safe data. it will not let you wipe your safe system aka "stock rom".
Click to expand...
Click to collapse
Awesome. Sorry for all of the questions, I'm familiar with CWM, but this is new territory for me. I really appreciate it. I'm doing the steps you provided. Am I basically doing a complete backup, complete wipe of both ROMs, then trying to install CM9 on the safe partition?
EDIT: I don't want to clutter this thread with questions about safestrap so I'll take any further questions to it's thread. Thanks again.
Calundle said:
Awesome. Sorry for all of the questions, I'm familiar with CWM, but this is new territory for me. I really appreciate it. I'm doing the steps you provided. Am I basically doing a complete backup, complete wipe of both ROMs, then trying to install CM9 on the safe partition?
Click to expand...
Click to collapse
No, you will only be making changes to the safestrap ROM, not the system ROM.... The backup will currently only be the stock ROM. now if when you enable safestrap do a backup, then disable safestrap, while in safestrap and taking a backup, you can backup the "safetrap" ROM, not the system ROM....
Now if you follow the directions in the original post, you will end up with two bootable ROMs on your phone. you really are only interested in the safestrap one right now, so doing the backup before flashing will ONLY backup the stock ROM. and you will not wipe the stock ROM either so to speak, because you can "dual" boot both ROMs by enabling and disabling the safestrap.
jimbridgman said:
No, you will only be making changes to the safestrap ROM, not the system ROM.... The backup will currently only be the stock ROM. now if when you enable safestrap do a backup, then disable safestrap, while in safestrap and taking a backup, you can backup the "safetrap" ROM, not the system ROM....
Now if you follow the directions in the original post, you will end up with two bootable ROMs on your phone. you really are only interested in the safestrap one right now, so doing the backup before flashing will ONLY backup the stock ROM. and you will not wipe the stock ROM either so to speak, because you can "dual" boot both ROMs by enabling and disabling the safestrap.
Click to expand...
Click to collapse
Ah okay okay, I think I understand how it works now. I've tried the steps in the OP and the ones faber mentioned and I'm still getting a blank black screen after reboot. How long should it take to flash the CM9 zip? It takes like 6-10 seconds for me and from my experience that's rather short for a ROM. Could the zip have gotten corrupted?
jimbridgman said:
Have you tried replacing /system/lib/hw, /system/etc/bluetooth, /system/etc/firmware, and /system/etc/ppp, and /system/etc/wifi, with the directories from our ROM, also try replacing /system/app/TelephonyProviders.apk, with the one from our ROM?
That might actually work. That is what I have done for the one I am working on, we shall see how far that gets me..... I had read someplace, that those are very important, right after the radio image, for proper hardware operation on a phone with another ROM.
Jim
Click to expand...
Click to collapse
Yup just tried it, I get "Unfortunately, phone has stopped" over and over so i guess its force closing.
So, without phone or 3g capabilities, this port is basically just pretty window dressing for our Atrix 2 right?
jimbridgman said:
Have you tried replacing /system/lib/hw, /system/etc/bluetooth, /system/etc/firmware, and /system/etc/ppp, and /system/etc/wifi, with the directories from our ROM, also try replacing /system/app/TelephonyProviders.apk, with the one from our ROM?
That might actually work. That is what I have done for the one I am working on, we shall see how far that gets me..... I had read someplace, that those are very important, right after the radio image, for proper hardware operation on a phone with another ROM.
Jim
Click to expand...
Click to collapse
Has anyone tried this yet? If not I will mess with it and let you know what happens.
lfaber06 said:
Yup just tried it, I get "Unfortunately, phone has stopped" over and over so i guess its force closing.
Click to expand...
Click to collapse
duke8804 said:
Has anyone tried this yet? If not I will mess with it and let you know what happens.
Click to expand...
Click to collapse
Yep lfaber06 tried it, and if you read his reply noted in the top quote here in my reply it keeps force closing..... To bad, I am guessing because it is ICS and not GB, like out phone is currently.
jimbridgman said:
Yep lfaber06 tried it, and if you read his reply noted in the top quote here in my reply it keeps force closing..... To bad, I am guessing because it is ICS and not GB, like out phone is currently.
Click to expand...
Click to collapse
Sorry about that, I guess i overlooked that one.
Related
I've been playing around with a Nexus S 4G that I have lying around and never used, and I've ran into a few problems, but you've all been helpful. I rooted all my old EVO 4G's without any problem, but the other day I rooted my NS4G using a one click/simple root and downloaded ClockWorkMod etc. But now for some reason It seems like I've almost lost my root? Is that possible? I still have the little unlocked symbol when booting up.
I've searched this forum and Google and haven't found anything, which could possibly be because I don't know what to look for. I've never had this happen :/
Currently running the stock 2.3.7
Nobody? I just need a little help.
Did you flash a superuser.zip after you installed clockworkmod?
SeeNah said:
Did you flash a superuser.zip after you installed clockworkmod?
Click to expand...
Click to collapse
I thought I had... But no lol
Thank you. Sorry for pretty much making a useless thread :/
Its the Q&A forum ask away! Lol
Did flashing it work for you though?
SeeNah said:
Its the Q&A forum ask away! Lol
Did flashing it work for you though?
Click to expand...
Click to collapse
Yes, it did. Thank you!
Now I just need to re figure out how to backup my stock rom on rom manager. I need to do that if I'm going to flash a custom rom onto my NS4G correct? I've never actually gone that far with my phones lol.
Slap-Yourself :) said:
Yes, it did. Thank you!
Now I just need to re figure out how to backup my stock rom on rom manager. I need to do that if I'm going to flash a custom rom onto my NS4G correct? I've never actually gone that far with my phones lol.
Click to expand...
Click to collapse
Okay lol hold on so just go make sure you
1. Unlocked the bootloader right?
2. Flashed a custom recovery (clockworkmod)?
3. Flashed superuser for root access?
4. Now you have a stock rooted ROM?
If you have/did all that then yeah you could backup your stock rooted ROM, you don't need to back it up but its helpful just incase you mess something you could always restore it to start all over
And you could backup any ROM you install incase you didn't know, just remember when you install different ROMS make sure to do a proper full wipe which includes data/factory reset/wiping DALVIK cache, and formatting system and boot in the "mount" option in CWM. And now I think your good lol
SeeNah said:
Okay lol hold on so just go make sure you
1. Unlocked the bootloader right?
2. Flashed a custom recovery (clockworkmod)?
3. Flashed superuser for root access?
4. Now you have a stock rooted ROM?
If you have/did all that then yeah you could backup your stock rooted ROM, you don't need to back it up but its helpful just incase you mess something you could always restore it to start all over
And you could backup any ROM you install incase you didn't know, just remember when you install different ROMS make sure to do a proper full wipe which includes data/factory reset/wiping DALVIK cache, and formatting system and boot in the "mount" option in CWM. And now I think your good lol
Click to expand...
Click to collapse
Unlocked Bootloader? If I boot in fastboot it says Unlocked. Is this what you mean?
I have ClockWorkMod, but I haven't done anything with it.
I have superuser from the root
and I was working with a stock ROM the whole time....
I think I'm ok lol
So I'll back up my ROM, and flash a Nightly CM9? And back that up as well? Just perform a factory data reset before doing so, right?
Slap-Yourself :) said:
Unlocked Bootloader? If I boot in fastboot it says Unlocked. Is this what you mean?
I have ClockWorkMod, but I haven't done anything with it.
I have superuser from the root
and I was working with a stock ROM the whole time....
I think I'm ok lol
So I'll back up my ROM, and flash a Nightly CM9? And back that up as well? Just perform a factory data reset before doing so, right?
Click to expand...
Click to collapse
Yeah if it says unlocked your good to go. The super user.zip you first flashed won't be needed once you flash different ROMS, it was only needed for stock because you didn't install a ROM you just unlocked the boot loader and super user just gave you root access that didn't come with stock.
Yeah backup your stock ROM JUST in case you encounter a boot loop so you can just restore and start over, you don't need to back up CM9 that's completely your choice if you want . Its convenient though if you like CM9 but still like to flash other ROMS that way you can just go back if you miss CM9 without doing the whole setup process.
And a full wipe is
Data/factory reset
Then wipe dalvik under "advanced"
Then wipe system and boot under the "mount" option in CWM
stellar said:
Yeah if it says unlocked your good to go. The super user.zip you first flashed won't be needed once you flash different ROMS, it was only needed for stock because you didn't install a ROM you just unlocked the boot loader and super user just gave you root access that didn't come with stock.
Yeah backup your stock ROM JUST in case you encounter a boot loop so you can just restore and start over, you don't need to back up CM9 that's completely your choice if you want . Its convenient though if you like CM9 but still like to flash other ROMS that way you can just go back if you miss CM9 without doing the whole setup process.
And a full wipe is
Data/factory reset
Then wipe dalvik under "advanced"
Then wipe system and boot under the "mount" option in CWM
Click to expand...
Click to collapse
I'm not sure if I'm supposed to post links to videos or not. But I'm in love with some of the features this guy has on his NS4G
https://www.youtube.com/watch?v=IKdyAm3CgHc
He said it was a nightly etc.
The hidden status bar and bottom menu hidden is amazing. I also like the inverted G-Mail and Facebook. Is this all separate from the Nightly ROM?
Hi,
I tried to modify the build.prop file of my LG Optimus 2X to simply disable the animation during the boot. It didn't really worked well because my cellphone is now looping during the boot. I think I saved the build.prop on my sdcard but now I don't know what to do...! I tried to hard reset and wipe date, but it's still no booting. I have clockwork mod instal.
Thank you!
EjasRus said:
Hi,
I tried to modify the build.prop file of my LG Optimus 2X to simply disable the animation during the boot. It didn't really worked well because my cellphone is now looping during the boot. I think I saved the build.prop on my sdcard but now I don't know what to do...! I tried to hard reset and wipe date, but it's still no booting. I have clockwork mod instal.
Thank you!
Click to expand...
Click to collapse
Well, first, I'd like to ask if you have a CWM backup of your system before you edited your build.prop? I assume that since you can wipe the data, you can reach CWM. If you can and have a backup, try recovering that backup and see if that works. If you do not, then you can always try to find an RUU (ROM update utility) that should return your phone to an unrooted, stock ROM. I don't know of any other options, all I can say now is become best friends with that search bar up there.
Hope you manage to get your phone back. :fingers-crossed:
revert to stock, oh just reflash whatever custom ROM you have been using (if you have any), you should be able to mount SD card from CWM and copy your ROM in there and flash away. I am under the assumption that since you were doing your DIY mods there, you should have knowledge of flashing back to stock or Custom Roms of choice. Good luck.
TekGadgt said:
Well, first, I'd like to ask if you have a CWM backup of your system before you edited your build.prop? I assume that since you can wipe the data, you can reach CWM. If you can and have a backup, try recovering that backup and see if that works. If you do not, then you can always try to find an RUU (ROM update utility) that should return your phone to an unrooted, stock ROM. I don't know of any other options, all I can say now is become best friends with that search bar up there.
Hope you manage to get your phone back. :fingers-crossed:
Click to expand...
Click to collapse
No I don't have a CWM backup :S Do you know where I could get a RUU for my phone?
EjasRus said:
No I don't have a CWM backup :S Do you know where I could get a RUU for my phone?
Click to expand...
Click to collapse
Here's a start. http://forum.xda-developers.com/showthread.php?t=1035041
The search bar on top is very useful if that doesn't help...
Foreverme89 said:
The search bar on top is very useful if that doesn't help...
Click to expand...
Click to collapse
That it is. Half of the time when helping people out, that is my starting point I'm really new to this, but know my way around a search engine and how to read
Boot into recovery, wipe cache and dalvik cache, and flash the same ROM you were already using
Sent from my MB508 using xda premium
do a full wipe or flash with the original rom
Hi Folks.
Ok here is my situation, I have a rooted and unlocked TF700.
I flashed Zeus 4 and all worked well, then flashed (after full wipe) PARANOIDANDROID 2.15 and again everything was great,
Yesterday I flashed Baked Bean 4 (again after a full wipe) and apart from some SD issues all seemed ok,
I then decided to restore my TWRP backup of Zeus as I needed to use my 64gig msd card.
After a full wipe and restore Zeus started up but the dpi was messed up (160) I think (way small)
I was seeing loads of FC's and file manager showed my internal SD as being empty. Rebooted to recovery and tried the "Format Data" option
It failed right away with this message "E: Unable to format data."
I have tried flashing the stock .26 rom via TWRP and I have the same issue, dpi set to 160 and internal sd not mounted.
It seems my Internal sd is corrupt
What is the procedure to reformat it via ADB or fastboot? (I have searched but the results I found relate to other devices and I dont want to simply follow instructions that might cause further harm to my TF700)
I have followed the NVflash brick proof procedure and have all relevant files backed up (I did this before flashing the last 2 roms)
Please can some one point me in the right direction
Thanks a lot
Jules
I always wipe cache, system, internal, davic and then do a factory reset.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
When you said that you tried to flash the stock .26 you meant installing not restoring a backup, right? What rom you have on your device right now?
Pretoriano80 said:
When you said that you tried to flash the stock .26 you meant installing not restoring a backup, right. What rom you have on your device right now?
Click to expand...
Click to collapse
Yip extracted the zip from the zip file and copied it to my ext sd and flashed it via TWRP
I have an unusable Zeus4,
Im about to try a full wipe again and then flash .26 again
EDIT
After flashing .26 and selecting reboot I get the "No OS installed! Are you sure you wish to reboot?" message
Looks like the system partition is corrupted, but i'm not sure. I think you should come here on IRC and maybe someone with more experience will help you - - http://webchat.freenode.net/?channels=asus-transformer
Thanks so much Pretoriano80!
With his help on IRC I was able to solve the problem,
In the end I had to return to complete stock, It seems CM10 caused some problems,
You are a a legend dude Thanks!!
:good:
ZaJules said:
Thanks so much Pretoriano80!
With his help on IRC I was able to solve the problem,
In the end I had to return to complete stock, It seems CM10 caused some problems,
You are a a legend dude Thanks!!
:good:
Click to expand...
Click to collapse
This same thing happened to me with my Prime when I was getting ready to send it off for RMA because of a broken HDMI port. Since I was unlocked I was advised to restore to stock before sending it in. However, before I got the chance to do that I started getting the "E: Unable to format data." error that you were. I ended up erasing all partitions from fastboot and putting a note in the box that it wouldn't boot after an OTA. I managed to get away with it and wasn't charged for fixing it
For future reference it would be really helpful to know how you fixed this. Did you do something like what is in this thread: http://forum.xda-developers.com/showthread.php?t=1803343.
Did you ever figure out how CM10 messed up your Infinity? I was running CM9 on my Prime when I got this error. Thanks!
It's hard to say if it was CM10 (or any other custom rom) or TWRP to mess the things up but we managed to get back to stock by replacing the twrp with CWM recovery and installing a modified .30 update package. Was a tricky one but we didn't had to mess with the partitions and that's good.
Pretoriano80 said:
It's hard to say if it was CM10 (or any other custom rom) or TWRP to mess the things up but we managed to get back to stock by replacing the twrp with CWM recovery and installing a modified .30 update package. Was a tricky one but we didn't had to mess with the partitions and that's good.
Click to expand...
Click to collapse
Why did you switch to CWM? Do you have any thoughts on the advantages and disadvantages of TWRP vs CWM?
paddycr said:
Why did you switch to CWM? Do you have any thoughts on the advantages and disadvantages of TWRP vs CWM?
Click to expand...
Click to collapse
Switched to CWM just to make sure it wasn't twrp recovery that somehow was failing to flash the partitions correctly. Tbh so far both do their job and both share the same limitation so far, meaning both fail to restore the boot partition (kernel) so in order to restore successfully (from a nandroid backup) you need to flash the right kernel after restoring is done. Otherwise i like TWRP better and never had issues with it, but i miss the advanced option from CWM, the one that let you format each partition individually.
Pretoriano80 said:
Switched to CWM just to make sure it wasn't twrp recovery that somehow was failing to flash the partitions correctly. Tbh so far both do their job and both share the same limitation so far, meaning both fail to restore the boot partition (kernel) so in order to restore successfully (from a nandroid backup) you need to flash the right kernel after restoring is done. Otherwise i like TWRP better and never had issues with it, but i miss the advanced option from CWM, the one that let you format each partition individually.
Click to expand...
Click to collapse
I'm not certain what you're referring to here. I've restored many times from different TWRP backups (for each custom rom that successfully boots and is half-decent, I make and keep a backup in case I want to jump around and try new things) and I've never had any issues. I am still on the .26 firmware update because I plan to do the nvflash thing. Are you saying that between Zeus v4 (ICS) and various Jelly Bean roms I've been on the same kernel? I gues I just haven't checked.
Anyway, I really love the TWRP recovery and use it with Xoom and Nexus 7 as well. It's so easy to use and always has been reliable.
okantomi said:
I'm not certain what you're referring to here. I've restored many times from different TWRP backups (for each custom rom that successfully boots and is half-decent, I make and keep a backup in case I want to jump around and try new things) and I've never had any issues. I am still on the .26 firmware update because I plan to do the nvflash thing. Are you saying that between Zeus v4 (ICS) and various Jelly Bean roms I've been on the same kernel? I gues I just haven't checked.
Anyway, I really love the TWRP recovery and use it with Xoom and Nexus 7 as well. It's so easy to use and always has been reliable.
Click to expand...
Click to collapse
For me moving between various roms by just restoring a backup never worked like it should. Let's say i'm on CM10 and i want to restore from a stock rom backup, the restore process is done, after reboot the device gets stuck to the first Asus screen and will stay there. Now if i get back to recovery and flash an update. zip containing the stock kernel the device will boot just fine, so definitely the boot image doesn't get restored in my case (with . 26 bootloader ).
Edit: @okantomi: You are using the internal storage or a MicroSD for backup / restoring? I'm really curious how this could work for some and not work for others, i mean same device, same recovery, same bootloader version...
Pretoriano80 said:
For me moving between various roms by just restoring a backup never worked like it should. Let's say i'm on CM10 and i want to restore from a stock rom backup, the restore process is done, after reboot the device gets stuck to the first Asus screen and will stay there. Now if i get back to recovery and flash an update. zip containing the stock kernel the device will boot just fine, so definitely the boot image doesn't get restored in my case (with . 26 bootloader ).
Edit: @okantomi: You are using the internal storage or a MicroSD for backup / restoring? I'm really curious how this could work for some and not work for others, i mean same device, same recovery, same bootloader version...
Click to expand...
Click to collapse
Ok, I only flash a new zip from the internal storage...made myself a "Flashworthy" folder which I keep stocked with newest versions of roms/gapps. I save my TWRP backups to my external microsdcard, as well as my TiBu backups. I have never had a problem restoring from TWRP this way, honestly.
okantomi said:
Ok, I only flash a new zip from the internal storage...made myself a "Flashworthy" folder which I keep stocked with newest versions of roms/gapps. I save my TWRP backups to my external microsdcard, as well as my TiBu backups. I have never had a problem restoring from TWRP this way, honestly.
Click to expand...
Click to collapse
Well, in this case i really have no clue why restoring works for some users but not for all.Dees_Troy, the dev behind Twrp recovery told me that .26 bootloader is to blame for the recovery failing to restore the boot partition, but looks like you have that bootloader version and restoring works good for you... interesting.
Pretoriano80 said:
Well, in this case i really have no clue why restoring works for some users but not for all.Dees_Troy, the dev behind Twrp recovery told me that .26 bootloader is to blame for the recovery failing to restore the boot partition, but looks like you have that bootloader version and restoring works good for you... interesting.
Click to expand...
Click to collapse
It is a mystery. Is there any other info that might be relevant to see why the difference in results? I ask because I would like to understand this device better, as well as potentially help others.
okantomi said:
It is a mystery. Is there any other info that might be relevant to see why the difference in results? I ask because I would like to understand this device better, as well as potentially help others.
Click to expand...
Click to collapse
I don't know, maybe the twrp version and the backup options, like if you are using compression or not, which partitions do you backup (boot, system, data, recovery, cache)...
Pretoriano80 said:
I don't know, maybe the twrp version and the backup options, like if you are using compression or not, which partitions do you backup (boot, system, data, recovery, cache)...
Click to expand...
Click to collapse
I'm using TWRP 2.2.2.1, I back up boot, system and data only, and I don't use compression.
Flashed several ROMS in my life and have not always wiped all data. Mainly i do dalvik and cache. My phones have always work. Now i have a Razr HD with an unlocked BL with TWRP loaded. I cant seem to get past the initial bootup screen no matter what ROM i flash. What am i missing here guys? Do i need to check the "factory reset" in TWRP along with Dalvik, system and cache?
famac! said:
Flashed several ROMS in my life and have not always wiped all data. Mainly i do dalvik and cache. My phones have always work. Now i have a Razr HD with an unlocked BL with TWRP loaded. I cant seem to get past the initial bootup screen no matter what ROM i flash. What am i missing here guys? Do i need to check the "factory reset" in TWRP along with Dalvik, system and cache?
Click to expand...
Click to collapse
answered here http://forum.xda-developers.com/showthread.php?t=2465695
bweN diorD said:
answered here http://forum.xda-developers.com/showthread.php?t=2465695
Click to expand...
Click to collapse
Not really. The majority of ROMS in question have been 4.2.2 based....
famac! said:
Not really. The majority of ROMS in question have been 4.2.2 based....
Click to expand...
Click to collapse
quote from post 11
"By golly that worked! It booted up fast as well. It must lie with the formatting your internal storage before flashing the 4.3 rom. I tried something similiar to this but I was already on a 4.3 rom that wouldn't boot and I formatted the sd card then tried flashing it again and it booted again for the first time but wouldn't the second. So if your having trouble do this:
Restored stock 4.1.2 using Matt's utility
Rooted with Matt's utility
Put 4.3 rom and GAPPS on external SD
Fastboot flash CWM 6.0.3.5 (or install via Matt's utility if you like)
Wipe data/factory reset
Wipe Cache/Dalvik
Go to mounts/storage and format /data and /data/media (/sdcard) **Back up anything in your internal SD you want to keep before doing this!**
Flash 4.3 rom
Wipe Cache/dalvik
Flash GAPPS
Wipe Cache/dalvik
Boot up and setup rom
Reboot"
bweN diorD said:
quote from post 11
"By golly that worked! It booted up fast as well. It must lie with the formatting your internal storage before flashing the 4.3 rom. I tried something similiar to this but I was already on a 4.3 rom that wouldn't boot and I formatted the sd card then tried flashing it again and it booted again for the first time but wouldn't the second. So if your having trouble do this:
Restored stock 4.1.2 using Matt's utility
Rooted with Matt's utility
Put 4.3 rom and GAPPS on external SD
Fastboot flash CWM 6.0.3.5 (or install via Matt's utility if you like)
Wipe data/factory reset
Wipe Cache/Dalvik
Go to mounts/storage and format /data and /data/media (/sdcard) **Back up anything in your internal SD you want to keep before doing this!**
Flash 4.3 rom
Wipe Cache/dalvik
Flash GAPPS
Wipe Cache/dalvik
Boot up and setup rom
Reboot"
Click to expand...
Click to collapse
Please explain this further to me. My problem is with 4.2.2 ROMS. The fix above is for folks having issues with 4.3 ROMS. Are you suggesting that doing this will also fix my 4.2.2 problems? This is also CWM while i run TWRP. I did a quick look and the two are setup a little difference. I played around with those highlighted instructions and almost accidentally wiped my only backup of my previous state. I actually thought i was toast but somehow i reloaded and went back to my old backup state.
famac! said:
Please explain this further to me. My problem is with 4.2.2 ROMS. The fix above is for folks having issues with 4.3 ROMS. Are you suggesting that doing this will also fix my 4.2.2 problems? This is also CWM while i run TWRP. I did a quick look and the two are setup a little difference. I played around with those highlighted instructions and almost accidentally wiped my only backup of my previous state. I actually thought i was toast but somehow i reloaded and went back to my old backup state.
Click to expand...
Click to collapse
i could be wrong, but in my opinion having the exact same issue even though its a different version, one of the 2 fixes in that thread should work.
the first fix likely doesn't directly apply although i suggest you ensure you have the latest version of your recovery of choice found here http://www.mediafire.com/download/tt7cwwua49n24uv/Razr_HD_Recovery_Flasher_V7.rar
second fix (backup ALL data you don't want to loose first as noted above), then do a full wipe as listed above, not just a fdr that doesn't wipe everything on the internal card.
the problem at this point is, you are assuming it wont work because of version differences, i am assuming it will. until you try it, i don't see any point in exploring other options, if there are any.
Dirty flashing when you go to different ROMs is generally not a good idea. Even on 4.2.2, it leaves residual data behind. There's a reason that the devs talk about doing complete wipes in their ROM threads, and there's a reason that they tell you not to talk about bugs unless you use their install directions.
RikRong said:
Dirty flashing when you go to different ROMs is generally not a good idea. Even on 4.2.2, it leaves residual data behind. There's a reason that the devs talk about doing complete wipes in their ROM threads, and there's a reason that they tell you not to talk about bugs unless you use their install directions.
Click to expand...
Click to collapse
Yeah, i am straight now. Did a full wipe and sailed right past the startup animation. Thanks all.
famac! said:
Yeah, i am straight now. Did a full wipe and sailed right past the startup animation. Thanks all.
Click to expand...
Click to collapse
Nice! Glad to see you got it working.
Hey guys, I am having trouble flashing some roms on my Sprint Galaxy SIII. Some of the unflashable roms include: Carbon 1.6, Pac-Man, and a few other's I can't remember the name of at the moment. Successful flashes so far are Slim, Cyanogenmod 10, and Carbon 1.5 (but with some minor issues). I googled this and the only things that came up where possible bad downloads but I have downloaded these bad ones over and over and have no different outcome. Okay so what happens when I try to flash these is it will say successful in clockwork recovery, then when I reboot the device it get's frozen in boot. On Carbon it just was black but the power button wouldn't respond until I pulled the battery out and put it back in so I assume it was in boot. Pac-Man shows the blue android Galaxy SIII screen and just stays there. I read somewhere to leave the phone for 15 minutes after a flash so I have tried that with both of these and nothing changes. The successful flashes don't take more that a minute or two. So I have no idea what is going on and now I am begging to think it might have something to do with my rooting method choice. Any suggestions or words of wisdom for me? Thank you!!!
Also so rule out some questions ahead of time: Yes I wipe system/factory reset, yes I wiped cache, yes I wiped Dalvik cache, I flashed them from my external sd card (sdcard1), I used the motochopper method of rooting from here: http://forum.xda-developers.com/showthread.php?t=2286241 , I had no problems with the motochopper root process according to the instructions. Okay I think that is all the standard questions, please ask if I missed one. Thank you again!
JacobGates said:
Hey guys, I am having trouble flashing some roms on my Sprint Galaxy SIII. Some of the unflashable roms include: Carbon 1.6, Pac-Man, and a few other's I can't remember the name of at the moment. Successful flashes so far are Slim, Cyanogenmod 10, and Carbon 1.5 (but with some minor issues). I googled this and the only things that came up where possible bad downloads but I have downloaded these bad ones over and over and have no different outcome. Okay so what happens when I try to flash these is it will say successful in clockwork recovery, then when I reboot the device it get's frozen in boot. On Carbon it just was black but the power button wouldn't respond until I pulled the battery out and put it back in so I assume it was in boot. Pac-Man shows the blue android Galaxy SIII screen and just stays there. I read somewhere to leave the phone for 15 minutes after a flash so I have tried that with both of these and nothing changes. The successful flashes don't take more that a minute or two. So I have no idea what is going on and now I am begging to think it might have something to do with my rooting method choice. Any suggestions or words of wisdom for me? Thank you!!!
Also so rule out some questions ahead of time: Yes I wipe system/factory reset, yes I wiped cache, yes I wiped Dalvik cache, I flashed them from my external sd card (sdcard1), I used the motochopper method of rooting from here: http://forum.xda-developers.com/showthread.php?t=2286241 , I had no problems with the motochopper root process according to the instructions. Okay I think that is all the standard questions, please ask if I missed one. Thank you again!
Click to expand...
Click to collapse
It's a good practice to wipe cache and dalvik AFTER flashing the ROM. Also, sometimes I'll have better luck flashing a particular ROM with TWRP if it doesn't flash well with CWM, and vice versa.
mcgrabowski said:
It's a good practice to wipe cache and dalvik AFTER flashing the ROM. Also, sometimes I'll have better luck flashing a particular ROM with TWRP if it doesn't flash well with CWM, and vice versa.
Click to expand...
Click to collapse
Oh, I haven't heard about wiping cache and dalvik after before, I will try that with one of them and see what happens. I did try TWRP once but it wouldn't do much of anything; I couldn't get it to mount the sd card, nandroid back up, and a few other things that I don't remember at the moment but maybe I had a bad download or install with that. Any suggestions on where to get it? I did it through goomanager last time.
JacobGates said:
Oh, I haven't heard about wiping cache and dalvik after before, I will try that with one of them and see what happens. I did try TWRP once but it wouldn't do much of anything; I couldn't get it to mount the sd card, nandroid back up, and a few other things that I don't remember at the moment but maybe I had a bad download or install with that. Any suggestions on where to get it? I did it through goomanager last time.
Click to expand...
Click to collapse
Nandroid backups are NOT compatible between TWRP and CWM, so that can always be tricky trying to switch between the two and still being able to restore if needed. As long as you don't delete the folder where your backup is stored on the SDCard, you should be able to flash back to your other recovery and restore if it doesn't work out.
I've flashed recoveries through GooManager, Rom Toolbox Pro and Rom Manager as well as downloading the recoveries directly from their website and flashed them manually. (CWM or TWRP)