Following situation: I have bought a Nexus S from someone. The previous owner installed Superuser at some point and later on updated to ICS 4.0.3 (and unrooted the phone as well before the update, apparently). For warranty reasons, I want to remove the Superuser application completely, but naturally I can only do that by rooting the phone again (otherwise I will not be able to delete /system/app/Superuser.apk).
I searched around here and other sites around the web and found a few guides, but haven't found anything specifically for the i9023 with ICS 4.0.3, especially for unrooting.
Could someone may be point me in the right direction? Or is there simply no way of doing that currently on an i9023 with ICS 4.0.3?
The best thing to do would be to root, flash a stock image (incl bootloader and recovery). Then relock the bootloader, and you're all done
Also, recently some sort of flash counter resetter has come to light for ICS devices, look it up and check it out before you unroot, it might be worth the probable risk, if you're willing to go the distance to ensure a warranty. I have no clue on how or if it works though, be careful.
One question though, do you actually have any warranty seeing as you bought the device used? If not, why not just reroot it and enjoy that?
Erythnul said:
The best thing to do would be to root, flash a stock image (incl bootloader and recovery). Then relock the bootloader, and you're all done
Also, recently some sort of flash counter resetter has come to light for ICS devices, look it up and check it out before you unroot, it might be worth the probable risk, if you're willing to go the distance to ensure a warranty. I have no clue on how or if it works though, be careful.
One question though, do you actually have any warranty seeing as you bought the device used? If not, why not just reroot it and enjoy that?
Click to expand...
Click to collapse
Nexus S doesn't have a flash counter
Sent from my ice cream powered Nexus S
Erythnul said:
The best thing to do would be to root, flash a stock image (incl bootloader and recovery). Then relock the bootloader, and you're all done
Click to expand...
Click to collapse
I already went ahead and tried that, but I ran into a problem unfortuantely: http://forum.xda-developers.com/showthread.php?p=22599816#post22599816
Other users on a german Android forum reported the same problem, when using this method (the Nandroid backup image and restoring it via CWM). They then tried a different method using Odin.
(Funnily enough, when I reverted to my original ICS 4.0.3 backup image via CWM, my USB Transfer Speed problem got fixed. I only had 1 MiB/sec before, and now after this whole ordeal I have ~20 MiB/sec (or more).)
Erythnul said:
One question though, do you actually have any warranty seeing as you bought the device used? If not, why not just reroot it and enjoy that?
Click to expand...
Click to collapse
I do still have warranty on it. The device was bought on 14th of December 2011 and I have the receipt. According to the seller, he got a Galaxy Nexus on Christmas 2 weeks later, so he simply sold his brand new Nexus S.
I may want to send the phone in, because the phone speaker is a bit bad. It's not completely broken, I can still understand everything, but the quality is rather bad, some frequencies get really distorted etc. I don't know if the Samsung support partner where I'll go to will grant me the warranty here, but I want to try nonetheless. Paid too much money for it to have a bad speaker .
In my opinion, you should never use other people's CWM backups on your own phone. It can mess things up BAD. Especially when they don't say what model they have.
Grab a full ROM from here: http://forum.xda-developers.com/showthread.php?t=1445635 and you'll be good to go. Don't forget to wipe /system, /data, /cache, /boot, dalvik cache and do a factory reset before flashing, assuming you're using CWM.
Good to hear about the warranty, good luck with that!
Erythnul said:
In my opinion, you should never use other people's CWM backups on your own phone. It can mess things up BAD. Especially when they don't say what model they have.
Click to expand...
Click to collapse
Yeah, well, I am thinking the same now . I simply trusted the stickied FAQ . Maybe this should get removed.
Erythnul said:
Don't forget to wipe /system, /data, /cache, /boot, dalvik cache
Click to expand...
Click to collapse
Phew, but for that, I'd need to root it again, right? I am still not sure if any of the rooting guides I found so far also apply to my case, since I have ICS 4.0.3 on it. (As I said superuser is already installed, but the device is not rooted and it seems to be a leftover from before the ICS 4.0.3 update.)
Well, I wouldn't know Try booting into recovery, if it's CWM recovery it's really very easy, and that's all you'll need anyway. doing the full wipe and reflash guarantees that there'll be no traces of the rooting process remaining at all.
If you don't have CWM, but the phone boots up with an unlocked symbol at the Google logo (first indicator of an unlocked bootloader), you can easily flash CWM again and then flash to all-stock. Then relock. Most rooting guides still hold, just make sure you flash the latest CWM (5.0.2.0 (non-touch) or 5.8.0.x (touch)), especially as for what you want to do you don't need SU, just CWM.
Step-by-step quick guide written by me
Install Android SDK if necessary (for adb and fastboot) (plenty of guides for that around)
download recovery file from CWM and rename to recovery.img
Connect phone to computer and reboot into bootloader
fastboot oem unlock
fastboot flash recovery recovery.img
use CWM to wipe everything and reflash
fastboot oem lock
???
Profit!
Alternately, use a one-click root method to flash CWM and then work from there
Good luck
EDIT: The FAQ you mentioned is probably old news by now, but I wouldn't know how to get that updated I'll see if I can get something done about that. I feel linking to a backup, especially with a dedicated full ROM thread (also stickied btw ) around, isn't a good idea at all
Thx for that.
I did look into CWM before you posted it and noticed these wiping options. However, I am unsure what exactly I should use. There is
- wipe data/factory reset
- wipe cache partition
in the main menu of CWM and
- Wipe Dalvik Cache
under advanced. But there is no specific mention of /system and /boot .
Also is this
download recovery file from CWM and rename to recovery.img
Click to expand...
Click to collapse
actually necessary? I searched around a bit and I thought that I simply have to grab one of the full ROMs (e.g. Android 2.3.6/GRK39F/XXKF1 Radio/KA3 Bootloader) and then use
- install zip from sdcard
in CWM.
Ah, I wasn't sure whether you had CWM on there, that makes all this way easier
The format options are under mounts and storage. Be careful not to wipe the SD, and make backups of stuff you want to keep (like SMS messages or apps etc). What I always do is wipe everything (except the sd-card!) under mounts and storage and then do a factory reset, that should also take care of the dalvik cache if I remember correctly. So just skip everything I said before wipe and reflash
Sounds like you have a good handle on the situation now, good luck on the warranty thing!
Erythnul said:
Ah, I wasn't sure whether you had CWM on there, that makes all this way easier
Click to expand...
Click to collapse
Yes, although I have to flash it every time I want to use it (I guess because the stock Android ICS ROM is removing it on every boot?).
Erythnul said:
The format options are under mounts and storage. Be careful not to wipe the SD, and make backups of stuff you want to keep (like SMS messages or apps etc). What I always do is wipe everything under mounts and storage and then do a factory reset, that should also take care of the dalvik cache if I remember correctly. So just skip everything I said before wipe and reflash
Click to expand...
Click to collapse
Aaah ok, so under
- mounts and storage
I do
- format /system
- format /cache
- format /data
- format /boot
and maybe
- format /sdcard
as well, if I don't need anything on it anymore, and then
- wipe data/factory reset
in the main menu of CWM, correct? And after that
- install zip from sdcard
with the aforementioned ROM.
Exactly, but don't wipe the sdcard, as the ROM you're going to flash is on there
and after that, don't forget to relock your bootloader, if it's still unlocked they'll know it used to be rooted
Erythnul said:
Exactly, but don't wipe the sdcard, as the ROM you're going to flash is on there
Click to expand...
Click to collapse
lol, damn, yeah, that would have been stupid
Related
Hey!
First let me say that I know all about flashing SGS and SGS2. Im a proud owner of SGS1 from day 1.
Last week I decided to finally flash my brothers i9023 so I flashed stock 4.0.3 with stock recovery. Then we wanted to flash some XDA stuff and I don't understand these guides...
I found one guide where you get superuser access with one click and usb cable, I did that, then I flashed CWM through Rom manager and flashed 4.0.4 from evilisto (v1.1) and it worked. Now I'm trying to flash some others, like nuhetri reloaded or pixel rom and I'm always getting stuck at boot animation. It just keeps "working" and nothing happens for 5+ minutes.
What am I doing wrong? Please help!
Best Regards
Luka
(in general)in recovery wipe data factory reset, format cache, davlik cache, system, boot. then flash new rom.
with nuhetri i think there is a bug where your not supposed to wipe data coming from another rom only davlik cache and cache then flash nuhetri
sean1984 said:
(in general)in recovery wipe data factory reset, format cache, davlik cache, system, boot. then flash new rom.
with nuhetri i think there is a bug where your not supposed to wipe data coming from another rom only davlik cache and cache then flash nuhetri
Click to expand...
Click to collapse
Hey and thanks for such quick reply!
I did all these now, rebooted to recovery (from CWM) and flashed this Fully Touched:
http://forum.xda-developers.com/showthread.php?t=1411734
Its stuck at boot image for 5 minutes now.
What now?
your using updated version of cwm? http://forum.xda-developers.com/showpost.php?p=22044793&postcount=82
steps
put rom on sd card
reboot into cwm recovery
wipe data, cache, davlik cahe, and format system and boot
install zip from sd card
choose rom you put on sd card
should say install from sd complete or something like that
reboot system now
let it boot into new rom (should not take more than 3-5 min)
edit: just seen this post in the rom thread your trying to flash http://forum.xda-developers.com/showpost.php?p=23255456&postcount=389 try redownloading again
sean1984 said:
your using updated version of cwm? http://forum.xda-developers.com/showpost.php?p=22044793&postcount=82
steps
put rom on sd card
reboot into cwm recovery
wipe data, cache, davlik cahe, and format system and boot
install zip from sd card
choose rom you put on sd card
should say install from sd complete or something like that
reboot system now
let it boot into new rom (should not take more than 3-5 min)
edit: just seen this post in the rom thread your trying to flash http://forum.xda-developers.com/showpost.php?p=23255456&postcount=389 try redownloading again
Click to expand...
Click to collapse
I did all that before... Im going to redownload, maybe its corrupted but I doubt it. Is it maybe because I have locked bootloader or something? Beacause I didnt use that long guide with "android SDK" in General, but some other very quick guide. Just plug USB, enable debugging and run some script and thats it.
devianceluka said:
I did all that before... Im going to redownload, maybe its corrupted but I doubt it. Is it maybe because I have locked bootloader or something? Beacause I didnt use that long guide with "android SDK" in General, but some other very quick guide. Just plug USB, enable debugging and run some script and thats it.
Click to expand...
Click to collapse
do yourself a favor, do it the right way the first time and save yourself headaches in the future. its not hard. fastboot oem unlock(bootloader), flash a custom recovery, flash a custom rom(and gapps) via the recovery, then boot up. thats it.
If you are more of a visual type of guy I suggest going on YouTube and search "zedomax". He has some really simple videos on how to root your nexus s, he has a couple videos on how to root but make sure its for a GSM nexus.
Simms got all in a simply way.
Unlock boot loader
Install or flash cwm
install the new stuff from SD card
reboot
Can anyone tell me or please provide a link to what unlocking bootloader does please.
Best Regards
Excuse my ignorance, I'm pretty new to this and I might not be of any help at all... but is it even possible to flash a custom recovery without unlocking the bootloader on the Nexus S?
I followed the instructions found on the NexusShacks.com website (How to root Nexus S or Nexus S 4G on ICS or Gingerbread) without any issues at all (sorry, can't post links due to low postcount :/)
No problems for me, I had zero experience with this sort of stuff but I have flashed a new ROM a every few days now without any issues whatsoever.
devianceluka said:
Can anyone tell me or please provide a link to what unlocking bootloader does please.
Best Regards
Click to expand...
Click to collapse
use this link: http://nexusshacks.com/
its complete with the files, pictures, video and some ics roms that you can try. let me know if you have any other question
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 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.
Hello XDA community,
I've rooted my HTC One X+ like 2 months ago.
I still got the latest stock ROM but I want to put a custom ROM on it.
Which is this one:
http://forum.xda-developers.com/showthread.php?t=1987885
I still got some questions about it since it will be the first time flashing a ROM, because the thread isn't really clear to me so I hope someone can help me out with a little bit more detailed guide than mentioned in the ROM thread.
1. Do I have to wipe all my data?
2. Is a dalvik wipe really needed?
I contacted the developer of the ROM he said I didn't have to but when I asked more things about it he didn't reply.
3. How to flash a boot.img?
I can't find a really good tutorial on that.
4. What's the really right order to perform this flash mentioned in above linked thread?
I hope anyone of you can help me out since most of the threads I've seen around people are *****ing about: you shouldn't do it if you don't know what you are doing blablabla.
Since I really want to learn something about it too.
Sent from my HOX+
NiZii. said:
Hello XDA community,
I've rooted my HTC One X+ like 2 months ago.
I still got the latest stock ROM but I want to put a custom ROM on it.
Which is this one:
http://forum.xda-developers.com/showthread.php?t=1987885
I still got some questions about it since it will be the first time flashing a ROM, because the thread isn't really clear to me so I hope someone can help me out with a little bit more detailed guide than mentioned in the ROM thread.
1. Do I have to wipe all my data?
2. Is a dalvik wipe really needed?
I contacted the developer of the ROM he said I didn't have to but when I asked more things about it he didn't reply.
3. How to flash a boot.img?
I can't find a really good tutorial on that.
4. What's the really right order to perform this flash mentioned in above linked thread?
I hope anyone of you can help me out since most of the threads I've seen around people are *****ing about: you shouldn't do it if you don't know what you are doing blablabla.
Since I really want to learn something about it too.
Sent from my HOX+
Click to expand...
Click to collapse
FULL WIPE is clearly recommended when you want to flash another rom. That means (/boot) /system /data /cache /dalvik. You can try it without a FULL WIPE but that will causes errors in most cases.
You need a working HTC USB cable
You need working adb/fastboot, download it from here
You need latest HTC drivers, download it from here
You need a GOOD custom recovery, download it from here
Additionally you need a flashable rom + boot.img
When you got all these we can proceed with flashing a rom
LS.xD said:
FULL WIPE is clearly recommended when you want to flash another rom. That means (/boot) /system /data /cache /dalvik. You can try it without a FULL WIPE but that will causes errors in most cases.
You need a working HTC USB cable
You need working adb/fastboot, download it from here
You need latest HTC drivers, download it from here
You need a GOOD custom recovery, download it from here
Additionally you need a flashable rom + boot.img
When you got all these we can proceed with flashing a rom
Click to expand...
Click to collapse
Hello LS.xD,
Thanks for your reply.
I am not at home at the moment.
I will be in about 4.5 or 5 hours, so I will download everything then.
I got the recovery flashed already, so I can probably skip that.
My HTC drivers are probably outdated.
Since my HTC desktop programm had to update the last time I opened it.
And I downloaded the files of the ROM too.
Sent from my HOX+
By the way LS.xD,
I got 'CWM-based Recovery v6.0.3.2'. (That's what it says in the top when I am in recovery mode)
I got three wipe options:
- wipe data/factory reset
- wipe cache partition
- wipe dalvik cache
These are all the wipes I got to perform AFTER installing the zip right? Because if you do it before you will wipe the zip file, is that right?
Sent from my HOX+
NiZii. said:
By the way LS.xD,
I got 'CWM-based Recovery v6.0.3.2'. (That's what it says in the top when I am in recovery mode)
I got three wipe options:
- wipe data/factory reset
- wipe cache partition
- wipe dalvik cache
These are all the wipes I got to perform AFTER installing the zip right? Because if you do it before you will wipe the zip file, is that right?
Sent from my HOX+
Click to expand...
Click to collapse
Its for a reason i recommended the recovery in my post. Pls install and THEN we can go on
and NO you first perform the wipe and then install a rom.
and pls uninstall HTC sync before using fastboot to flash boot.img as it will cause errors if you have htc sync installed.
LS.xD said:
Its for a reason i recommended the recovery in my post. Pls install and THEN we can go on
and NO you first perform the wipe and then install a rom.
and pls uninstall HTC sync before using fastboot to flash boot.img as it will cause errors if you have htc sync installed.
Click to expand...
Click to collapse
Okay I will do that when I am home. Thanks for the patience with me and all the help, nobody was replying in other threads so I really appreciate all your help.
Sent from my HOX+
One more question, what is a safe spot to put the ROM zip file on? So it doesn't get wiped? (HOX+ doesn't have a SD slot, just 64GB internal)
Sent from my HOX+
NiZii. said:
One more question, what is a safe spot to put the ROM zip file on? So it doesn't get wiped? (HOX+ doesn't have a SD slot, just 64GB internal)
Sent from my HOX+
Click to expand...
Click to collapse
Thats totally safe as long as you dont WIPE or FORMAT /sdcard LOL
Probably a dumb question, but if you do a factory reset your music and pictures will be deleted, why doesn't the zip file be deleted? I will test it at home though. Factory reset, put the zip file on it, then factory reset again in recovery and look if the zip file still exists on my phone.
Sent from my HOX+
NiZii. said:
Probably a dumb question, but if you do a factory reset your music and pictures will be deleted, why doesn't the zip file be deleted? I will test it at home though. Factory reset, put the zip file on it, then factory reset again in recovery and look if the zip file still exists on my phone.
Sent from my HOX+
Click to expand...
Click to collapse
MAN be patient pls. Install the recovery i suggested. Then everything will be clear and safe once you opened it. DONT perform factory reset / clear storage in bootloader mode!!!
LS.xD said:
MAN be patient pls. Install the recovery i suggested. Then everything will be clear and safe once you opened it. DONT perform factory reset / clear storage in bootloader mode!!!
Click to expand...
Click to collapse
I am sorry, I will tell you when I did..
Sent from my HOX+