Database Info

RUU Stuck. Help?

A few days ago I was in the process of changing roms. I was using clean rom 4.5 beta. During the process I accidentally hit Factory Reset on the bootloader menu. I then proceeded to change roms but all of my sdcard data was erased and I cannot mount the sdcard at this time to put a new rom on there. I tried RUU (currently running 1.85, tried updating to 2.20) to no avail because I always get stuck at the sending screen for hours. I've emailed a few devs already who could'nt help, I also busted my ass searching forums and googling crap :crying: Any ideas ?

Do you have a recovery installed? Clockworkmod has been known to have some issues with the onex. I would recommend flashing TWRP in bootloader.
It may say in TWRP that you cannot select the sd for mounting. However if you check your PC, should still show up and may also ask for you to fomat the drive. Its ok to format fat32 since you've allready wiped. If your running linux or Mac. I'm affraid I'm no help at all.

subarudroid said:
Do you have a recovery installed? Clockworkmod has been known to have some issues with the onex. I would recommend flashing TWRP in bootloader.
It may say in TWRP that you cannot select the sd for mounting. However if you check your PC, should still show up and may also ask for you to fomat the drive. Its ok to format fat32 since you've allready wiped. If your running linux or Mac. I'm affraid I'm no help at all.
Click to expand...
Click to collapse
Im using TWRP 2.20 I was wondering about that as well, so I should format the drive? I will be formatting the system right? I am using Windows.

slayher186 said:
Im using TWRP 2.20 I was wondering about that as well, so I should format the drive? I will be formatting the system right? I am using Windows.
Click to expand...
Click to collapse
You will in affect be formatting the sd card. At first its a little scary cause your affraid that you'll loose your recovery. I went through a similar issue.
format the SD then copy and paste your ROM or custom ROM to SD. Then flash away to your hearts desire. :highfive:
HIt the Thanks button if I helped.
Running with HOX CM10.

subarudroid said:
You will in affect be formatting the sd card. At first its a little scary cause your affraid that you'll loose your recovery. I went through a similar issue.
format the SD then copy and paste your ROM or custom ROM to SD. Then flash away to your hearts desire. :highfive:
HIt the Thanks button if I helped.
Running with HOX CM10.
Click to expand...
Click to collapse
Once I can get the format option to pop up again I'll format, thanks!

slayher186 said:
Once I can get the format option to pop up again I'll format, thanks!
Click to expand...
Click to collapse
I was able to format and put a rom on the sdcard :highfive: but its failing to install because I cannot mount the cache.

Sorry Just got home from work noticed your update. looks like your back east? Maybe too late for you. Any who, once you put your rom on the SD card then go to install, Under the TWRP file you should find the ROM.

subarudroid said:
Sorry Just got home from work noticed your update. looks like your back east? Maybe too late for you. Any who, once you put your rom on the SD card then go to install, Under the TWRP file you should find the ROM.
Click to expand...
Click to collapse
I'm all set now. Your a life saver, almost cried thinking I would have to shelf my HOX. I definitely appreciate all of the help. :good: :victory:

Corrupt internal SD Card

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.

[Q] rebooting from recovery

my one s recently developed a strange issue, where if i try to run a nandroid backup, it will mostly finish, then reboot itself without fully completing the process, leaving me with a bunk backup and stuck on one rom for now. also, and the more important of my 2 concerns, is that i don't know if it will do this during a rom flash, nor do i want to find out, seeing as i have no current working backup. doe's anyone have any ideas as to how i could fix this?

mercenaryhmster said:
my one s recently developed a strange issue, where if i try to run a nandroid backup, it will mostly finish, then reboot itself without fully completing the process, leaving me with a bunk backup and stuck on one rom for now. also, and the more important of my 2 concerns, is that i don't know if it will do this during a rom flash, nor do i want to find out, seeing as i have no current working backup. doe's anyone have any ideas as to how i could fix this?
Click to expand...
Click to collapse
At a guess you got a high Hboot so that means when you restore its not restoring the boot.img. You need to flash that in fastboot.

Darknites said:
At a guess you got a high Hboot so that means when you restore its not restoring the boot.img. You need to flash that in fastboot.
Click to expand...
Click to collapse
nope, i have hboot 1.06, and either way that wouldn't, and shouldn't, cause a nandroid to fail during backup, nor for the phone to reboot by itself.

mercenaryhmster said:
nope, i have hboot 1.06, and either way that wouldn't, and shouldn't, cause a nandroid to fail during backup, nor for the phone to reboot by itself.
Click to expand...
Click to collapse
Oh if you mean you cant make a backup try a newer recovery or if its already up to date try an old one.
Edit, just to add I use TWRP 2.2.2.0 and it works fine.

Darknites said:
Oh if you mean you cant make a backup try a newer recovery or if its already up to date try an old one.
Edit, just to add I use TWRP 2.2.2.0 and it works fine.
Click to expand...
Click to collapse
tried using twrp 2.3, 2.2, cwm touch, regular cwm, does it on all of them.

mercenaryhmster said:
tried using twrp 2.3, 2.2, cwm touch, regular cwm, does it on all of them.
Click to expand...
Click to collapse
Not sure then sorry.

Do you have enough free space on your sdcard partition?
You can also try (un?)mounting /data and /system before you start the backup.

Just as an update, I solved my problem. It seems that there were some corrupted files on my data partition, and they were causing nandroid to fail and reboot randomly. So, since I was planning on wiping anyway, I wiped and set up viper again, and successfully made a nandroid after.

[Q] ViperS 3.1.2 + Sensation XE

Hi.
I want to switch to ViperS 3.1.2 but have few questions before I do so. I've never done it before so I'm new to this.
Does it come rooted (or do all ROMs come rooted)?
Is there any instruction on how to do it or just flash it from .zip via the recovery mode (I have CWM 5.x.x installed already)?
And are there any bugs with it such as Wi-Fi problems/tethering, or calls (speaker)?
Also, what if something goes wrong? I've got a backup of my current ROM (stock), so do I just flash that one back or try ViperS' in case it was a mistake on my side?
Lastly, I've heard some people mentioning OTA updates. I'm assuming it's done in the same way as stock ROMs, so you just need Wi-Fi/working internet and the new update will install on its own, or do I have to download the update from here and then do it myself?
Thanks!

MrCatalyst said:
Hi.
I want to switch to ViperS 3.1.2 but have few questions before I do so. I've never done it before so I'm new to this.
Does it come rooted (or do all ROMs come rooted)?
Is there any instruction on how to do it or just flash it from .zip via the recovery mode (I have CWM 5.x.x installed already)?
And are there any bugs with it such as Wi-Fi problems/tethering, or calls (speaker)?
Also, what if something goes wrong? I've got a backup of my current ROM (stock), so do I just flash that one back or try ViperS' in case it was a mistake on my side?
Lastly, I've heard some people mentioning OTA updates. I'm assuming it's done in the same way as stock ROMs, so you just need Wi-Fi/working internet and the new update will install on its own, or do I have to download the update from here and then do it myself?
Thanks!
Click to expand...
Click to collapse
Are you S-Off or S-On? If S-Off then you can flash the zip directly from recovery and if you're S-On then you gotta flash 4EXT recovery first and enable smart flash feature and then flash the zip file.
There are no major bugs in the Rom except the ones listed on the OP of the official thread. Enjoy flashing.
Sent from my HTC Sensation Z710e using xda app-developers app

I'm S-Off. I've had root earlier but I've installed SuperSU and accidentally pressed Clean SU which has pretty much wiped it. :|

Post your bootloader details to make things more clearer. Flashing a custom Rom doesn't need root access. You can flash it as you're s-off.
What Rom you're using currently? What firmware?
Sent from my HTC Sensation Z710e using xda app-developers app

I apologise for not posting, although it may be a bit too late now since I'm already installing the ROM.
So, just wanna know now - do ROMs come rooted, and if I can always go back to stock ROM as long as I have the boot.img/download stock ROM from HTC site?

MrCatalyst said:
I apologise for not posting, although it may be a bit too late now since I'm already installing the ROM.
So, just wanna know now - do ROMs come rooted, and if I can always go back to stock ROM as long as I have the boot.img/download stock ROM from HTC site?
Click to expand...
Click to collapse
Yup they come pre-rooted

Thanks for the help, everyone! Managed to install the ROM, despite being stuck in bootloop for 2 hours but it works flawlessly now.

MrCatalyst said:
I apologise for not posting, although it may be a bit too late now since I'm already installing the ROM.
So, just wanna know now - do ROMs come rooted, and if I can always go back to stock ROM as long as I have the boot.img/download stock ROM from HTC site?
Click to expand...
Click to collapse
Most roms come rooted, and the rest provide root tools so you have a choice while flashing.
To return to stock look up ruu. An ruu + s on = your device as it came.

If you had flashed Firmware-3.33 before the ROM - you would have had no "bootloops" at all! The most important thing is to have Firmware-3.33

Rom is broken , EMERGENCY , plz help
Hello everybody. I'm in a real trouble with my phone. it's very emergency , so i really need your help please. My ViperS 3.1.2 is broken and doesn't boot. i reinstalled Rom without wiping and again with update only setting but still doesn't boot.I flashed boot.img again but still... i did everything i could such as wiping cache and dalvik cache but again the same problem. the phone stays on "SENSATION" boot screen with beats audio on bottom for 20 seconds and suddenly screen become dark and phone restarts . i wiped dalvik and again "android is upgrading" starts and after it finished the phone restarts again i know if i perform a full wipe during Rom installation it will be fixed but i REALLY,REALLY,REALLY need my contacts and messages.... is there anyway i could fix my phone or make a backup of contacts and messages??? PLEEAAASSSE help me . tnx

VAHIDHAVASBEIGY said:
Hello everybody. I'm in a real trouble with my phone. it's very emergency , so i really need your help please. My ViperS 3.1.2 is broken and doesn't boot. i reinstalled Rom without wiping and again with update only setting but still doesn't boot.I flashed boot.img again but still... i did everything i could such as wiping cache and dalvik cache but again the same problem. the phone stays on "SENSATION" boot screen with beats audio on bottom for 20 seconds and suddenly screen become dark and phone restarts . i wiped dalvik and again "android is upgrading" starts and after it finished the phone restarts again i know if i perform a full wipe during Rom installation it will be fixed but i REALLY,REALLY,REALLY need my contacts and messages.... is there anyway i could fix my phone or make a backup of contacts and messages??? PLEEAAASSSE help me . tnx
Click to expand...
Click to collapse
If you made a backup before flashing you should restore it, or else flash the ROM you had before flashing.
Then use "Titanium Backup" and back up your messages (your contacts are automatically synced with your google account, unless you saved them on the phone, but you can change that with the "people" app.
after you backed your phone up, make a full wipe, and flash the new ROM. Install Titanium Backup and restore your messages backup.
Good luck.

astar26 said:
If you made a backup before flashing you should restore it, or else flash the ROM you had before flashing.
Then use "Titanium Backup" and back up your messages (your contacts are automatically synced with your google account, unless you saved them on the phone, but you can change that with the "people" app.
after you backed your phone up, make a full wipe, and flash the new ROM. Install Titanium Backup and restore your messages backup.
Good luck.
Click to expand...
Click to collapse
excuse me, you said 2 options . first is to restore backup , unfortunately i don't have backup. second is flashing the rom i had before flashing ! i didn't understand what you said... what do you mean? i don't have any backup, if you can help me to boot up phone just for 2 mins to backup my contacts! they aren't synced to my google account....

pleeeeaaaaaaaaaasssseeeee helppp meee. i am becoming crazyy because of my problem.... HELP PLZZZ :crying:

VAHIDHAVASBEIGY said:
excuse me, you said 2 options . first is to restore backup , unfortunately i don't have backup. second is flashing the rom i had before flashing ! i didn't understand what you said... what do you mean? i don't have any backup, if you can help me to boot up phone just for 2 mins to backup my contacts! they aren't synced to my google account....
Click to expand...
Click to collapse
Get a download of the ROM you had before, and you can flash it normally. If you had stock, find a download of stock ROM (although Sense 3.6 custom ROMs might actually work too).

Right
i dont had a Problem :good:

astar26 said:
Get a download of the ROM you had before, and you can flash it normally. If you had stock, find a download of stock ROM (although Sense 3.6 custom ROMs might actually work too).
Click to expand...
Click to collapse
excuse me again! you mean install another ROM without Wiping on ViperS? I am using ViperS for about 1 years, Are you sure? now i should download another ROM like Android Revolution HD for sensation and install it on my phone without performing full wipe and it can fix boot problem?

VAHIDHAVASBEIGY said:
excuse me again! you mean install another ROM without Wiping on ViperS? I am using ViperS for about 1 years, Are you sure? now i should download another ROM like Android Revolution HD for sensation and install it on my phone without performing full wipe and it can fix boot problem?
Click to expand...
Click to collapse
Oh no, I thought you wanted to flash viperS. Flash the ROM you had before flashing, whichever ROM that was (but flash that specific ROM, not a different one. My advice from the previous comment was if you came from stock ROM). If you flash the same ROM you don't have to wipe, and then you can back up your phone.

astar26 said:
Oh no, I thought you wanted to flash viperS. Flash the ROM you had before flashing, whichever ROM that was (but flash that specific ROM, not a different one. My advice from the previous comment was if you came from stock ROM). If you flash the same ROM you don't have to wipe, and then you can back up your phone.
Click to expand...
Click to collapse
ohhh , in my first post i said ( i reinstalled Rom without wiping and again ...) i mean i did your advice , but it doesn't fix my problem... :crying:

VAHIDHAVASBEIGY said:
ohhh , in my first post i said ( i reinstalled Rom without wiping and again ...) i mean i did your advice , but it doesn't fix my problem... :crying:
Click to expand...
Click to collapse
I hope you can operate adb, because the solution I found requires it.
Go to recovery, and use adbto pull the contacts database with the following command:
adb pull data/data/com.android.providers.contacts/databases/contacts.db
It might give an error for a protected directory (but I don't know since it's going to be done in recovery), if that happens, use 'adb shell' and then 'su'. then exit, and you have root access to the device (do it only if required).
Once you obtained the file, it should be on your adb folder. you need to open it with a database app which supports SQLite3 (I won't reccomend anyrhing since I've never used them. but from a quick search I found a few. and searching in the context of reading android databases would give some recommendations.).
Good luck
p.s - It's hard for me to believe this is the simplest solution. It might work, but it's not easy. So others might give better solutions.

astar26 said:
I hope you can operate adb, because the solution I found requires it.
Go to recovery, and use adbto pull the contacts database with the following command:
adb pull data/data/com.android.providers.contacts/databases/contacts.db
It might give an error for a protected directory (but I don't know since it's going to be done in recovery), if that happens, use 'adb shell' and then 'su'. then exit, and you have root access to the device (do it only if required).
Once you obtained the file, it should be on your adb folder. you need to open it with a database app which supports SQLite3 (I won't reccomend anyrhing since I've never used them. but from a quick search I found a few. and searching in the context of reading android databases would give some recommendations.).
Good luck
p.s - It's hard for me to believe this is the simplest solution. It might work, but it's not easy. So others might give better solutions.
Click to expand...
Click to collapse
tnx , if i try i can do it. i can operate adb easily . but a person said me to backup /data partition with recovery and then perform a full wipe and install viperS again then restore /data . do you have any idea abou it? can it help?

[Q] Formatting just internal Storage back to stock

I am having a hard time finding anything that shows how to format just my internal storage (where downloads, etc live). I am selling this phone and wish to perform the wipe but keep root.
Can someone point me in the direction of a thread or knows how to do this?

oconnell84 said:
I am having a hard time finding anything that shows how to format just my internal storage (where downloads, etc lives). I am selling this phone and wish to perform the wipe.
Can someone point me in the direction of a thread or knows how to do this?
Click to expand...
Click to collapse
you will need to go to settings->backup and reset-> and choose reset phone.
make sure you have already backed up all your files on you computer or sd card before doing this also make sure your SD card is removed as well.

neggie said:
you will need to go to settings->backup and reset-> and choose reset phone.
make sure you have already backed up all your files on you computer or sd card before doing this also make sure your SD card is removed as well.
Click to expand...
Click to collapse
And this factory reset will not remove root or associated files that are in the Stock Rooted Rom?

oconnell84 said:
And this factory reset will not remove root or associated files that are in the Stock Rooted Rom?
Click to expand...
Click to collapse
Depends... How did you root? Weaksauce or perm root via custom recovery?
If you have TWRP or CWM installed format data from the Wipe menu in recovery. That will wipe your apps and personal data but keep your root intact.
If Weaksauce is installed to /data it would be wiped by a factory reset mentioned above, but you could easily reinstall it and gain temp root that way.

oconnell84 said:
I am having a hard time finding anything that shows how to format just my internal storage (where downloads, etc live). I am selling this phone and wish to perform the wipe but keep root.
Can someone point me in the direction of a thread or knows how to do this?
Click to expand...
Click to collapse
TWRP has an option to wipe just the internal storage.

sfobrien said:
TWRP has an option to wipe just the internal storage.
Click to expand...
Click to collapse
Yeah, but unless TWRP for the M8 works differently than TWRP for my Transformer tablets, the /data wipe doesn't wipe /data/media and he/she wants to prepare his phone for sale, as in: making sure no personal data is left. AFAIK only formatting data does that.

Originally Posted by sfobrien View Post
TWRP has an option to wipe just the internal storage.
Click to expand...
Click to collapse
berndblb said:
Yeah, but unless TWRP for the M8 works differently than TWRP for my Transformer tablets, the /data wipe doesn't wipe /data/media and he/she wants to prepare his phone for sale, as in: making sure no personal data is left. AFAIK only formatting data does that.
Click to expand...
Click to collapse
TWRP will allow you to wipe everything. If I read correctly he wants to keep the device rooted but clean. Use TWRP to wipe Internal Storage, Dalvik,Cache,System,and Data. Before rebooting device install a fresh copy of whatever ROM he wants from the External Card. This should achieve what he is looking to do. You can then remove the external card or wipe it too if it's going to remain in the device.

Use the RUU from dottats thread, does everything you want, plus prerooted stock

aer0zer0 said:
Use the RUU from dottats thread, does everything you want, plus prerooted stock
Click to expand...
Click to collapse
Sorry, where is that thread? I am looking to flash back to stock in order to get the verizon OTA when it comes out.

RedBullet said:
Sorry, where is that thread? I am looking to flash back to stock in order to get the verizon OTA when it comes out.
Click to expand...
Click to collapse
Here's the link to the ruu thread: http://forum.xda-developers.com/showthread.php?t=2727831

RedBullet said:
Sorry, where is that thread? I am looking to flash back to stock in order to get the verizon OTA when it comes out.
Click to expand...
Click to collapse
And I would suggest not going stock to take the ota. Flashables of the firmware and 4.4.3 will be put up really soon after the actual ota drops, then no risk of locking up your device

Shamestick said:
And I would suggest not going stock to take the ota. Flashables of the firmware and 4.4.3 will be put up really soon after the actual ota drops, then no risk of locking up your device
Click to expand...
Click to collapse
OK, sitting tight.