Full Factory Reset - Asus Transformer TF700

What happened to me? I testig new settings Buildprop file and I was stuck.
TF 700 not boot
______________________________________
Wipping/factor reset
POWER off
VOL down
VOL up to recovery
Wipe/Factor reset
Boot
but
Not boot I cry almost :crying:
______________________________________
I wonder.....
Download ASUS.com your Factor version Asus update
Open zip file Unzip first Zip file (WW_epad-user-9.4.5.22.zip)
Re name (WW_epad-user-9.4.5.22.zip) EP201_768_SDUPDATE.zip
And put zip file External Sdcard root
POWER off
VOL down
VOL up to recovery
Now auto starting full factory reset/update and TF700 :fingers-crossed: boot normal.
if anyone benefited from that I'm happy
Zeus :good:

I had the same problem and used (+described here) the same solution a few days ago, but thanks for this. Glad it worked for you too ]:>
http://forum.xda-developers.com/showpost.php?p=28597763&postcount=17

To clear up possible ambivalence on file location: the firmware file should be placed in the root directory of the microSD card. When you get an error message saying that some directory couldn't be mounted or some file couldn't be found, check if it hasn't been put on the SD card's root accidentally. :highfive:

To answer what actually happened, a factory reset only touches the data partition. Since the build.prop is on the system partition, its not wiped and so whatever prevented it form booting before is still there. Until we get an unlocked bootloader AND a custom recovery, I'd stay away from build.prop changes and any other mod that could potentially prevent booting unless you know completely what you are doing.

Jotokun said:
To answer what actually happened, a factory reset only touches the data partition. Since the build.prop is on the system partition, its not wiped and so whatever prevented it form booting before is still there. Until we get an unlocked bootloader AND a custom recovery, I'd stay away from build.prop changes and any other mod that could potentially prevent booting unless you know completely what you are doing.
Click to expand...
Click to collapse
Factor reset only return data partion default
if using sd card option Recovery return system partition. (But not touch data partition settings etc..)
I've restored the system partition twice.

Will this get rid of root? I am going to exchange my tf700 because the volume rocker is mushy and seems defective (I went to the store to check out the tf201's/etc asus tabs to compare) and I am sending back to amazon to exchange - so want it factory fresh.

It won't, apart from wiping data you need to remove su from /system/bin/ or xbin, wherever it is, and uninstall busybox (if installed)
You may reflash firmware as well, should do the trick.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app

d14b0ll0s said:
It won't, apart from wiping data you need to remove su from /system/bin/ or xbin, wherever it is, and uninstall busybox (if installed)
You may reflash firmware as well, should do the trick.
Click to expand...
Click to collapse
Thanks - found it there in xbin

Related

cwm cant mount /system and /data

Hey guys I need your help
I've been using cm7 for a couple of weeks now. I havnt had problems until today.
I flashed build 32 over and for some reason it wasn't booting up. It was on the splash screen for a while (it usually does that and when I take battery out and restart it boots) so then I took the battery out. Next thing I know is that my phone is stuck on the mytouch screen... I went to recovery and when it booted into cwm 3. I got a error saying it couldn't open system/recovery/log or something like that... it still went to cwm and I checked the mounts and it said /system and /data wasn't mounted. I clicked it to mount and it gave me an error saying it couldn't ... therefore it wouldn't let me install cm7 or do a wipe... is there anything I can do to fix this? It seems to be that the nand. Is corrupted or something...
I think, based on your description, that pulling the battery at the particular instant caused the secondary problem.
A "factory reset" reformats /data and /cache. But not /system. You can do that manually from the mounts and storage menu, then either restore a nandroid backup or install cm7 and gapps.
HTC Glacier running CM7 #33
Hmm I font think its just two directories... I think my whole internal storage is messed up. I tried using the reformat option from cwm but no luck
Time to discover what you might be able to accomplish with Fastboot and a USB cable.
HTC Glacier running CM7 #33
I think a lot of people are having problems with clockwork 3 in the nexus forums, and more specifically with it screwing up partitions. I was luck just to lose my ext position on my sd...
Reformat and reflash seems to be the easiest fix...
Sent from my Nexus One using XDA App
i dont know how to repartition the phone storage :/
i tried doing it off cwm and it wouldn't let me... is there anyway to do this through adb? i think adb is working...
Reformat the whole card, and then try to repartition. This will write your data, so back up first...
Sent from my Nexus One using XDA App
how do i do that? o_o through cwm? i tried formating everything including system data cache... and i dont know how to repartition through cwm. cwm is the only thing i can get to right now :/
Sorry, looks like the only option in clockwork is to partition. Can you not do it from your pc?
Sent from my Nexus One using XDA App
yeah it gives me error when i try to do :
fastboot erase system -w :/ is there anything else?
guys... ((((( am i totally effed up? i couldn't find anything i could do.. no matter what i did, the /system and /data would NOT mount... so i cant format it
I have never tried this, but you might consider it.
In this thread is a method to return your phone to stock -- it uses the bootloader's ability to repartition and reformat everything somewhat automatically, using a file called PD15IMG.ZIP from the SD card's root folder.
http://forum.xda-developers.com/showthread.php?p=11011692&highlight=pd15img.zip#post11011692
There's a link in the thread to the .zip file -- look to post signatures. Put the file on an SD card (with another phone, or camera, or Micro-SD to SD adapter, etc.) and boot into the bootloader with that file on the SD card.
I do not know if you can rename the .zip it to update.zip and force it to flash with Fastboot's update command, because the PD15IMG.ZIP is a specific thing this phone's bootloader looks for. As stated, I have never tried this, and do not recommend this. It might work, or, it might cause more damage. Putting the file on an SD card without Fastboot will be safer.
You could try to boot your phone into fastboot,
and then type
fastboot erase -w system
Your phone wont boot after that, but you should be able to flash a new rom from clockwork.
ive tried both the pd15img.zip method. it says "partition update fail"
and i also tried the "fastboot erase system -w" and it did not work.. it says that it can't be done. i also tried to format /system through adb and cwm, and both says it can't because it must be mounted before
From your description, it seems to me that the internal flash memory has a damaged partition table -- easy enough to repair if this were a hard drive you could remove and take to a linux system somewhere. But it's a phone, and a bit of flash memory that can't be removed.
Flashboot has an "erase <partition>" command. I don't know what it does, since it's not well documented. Does it reformat an existing partition? Or does it remove the partition from the partition table? There is no commensurate "create <partition>" command, so perhaps it recreates an empty partition. But I tend to doubt it.
I would think such work might be done from an engineering bootloader or engineering recovery system -- one available to HTC service technicians, for example.
Since you're not getting a great deal of help in the MT4G subforum, you might post your question in the top level Questions and Answers forum.
Sorry I'm not much help with this.
One last thought. The bootloader itself has a Factory Reset. That might do it. Might not. But like chicken soup, it probably couldn't hurt. Boot into the bootloader (volume down while powering up), select BOOTLOADER with the volume control and then the power button, then select FACTORY RESET. Perhaps it will do something positive.
eh.. i couldnt do anything. i tried all options. its like impossible to reformat or repartition the drive..
i actually called up insurance and they'll be sending me a new mytouch 4g..
we have just told them that it doesnt go past the mytouch screen.. would they figure out that it is rooted? i mean.. choosing recovery from the bootloader menu takes it right into cwm lol
Just flash the stock recovery back via fastboot...
Sent from my Nexus One using XDA App
ive tried
dumbkkid said:
ive tried
Click to expand...
Click to collapse
you are sending the fastboot commands while in the bootloader right? I would imagine you are but I just want to make sure.

sdcard wont format

i have a odd issue.
Last night the MIUI 1.10.7 ROM froze up with trinity kernal. After the reboot trinity kernal on boot screen kept freezing.
I did a full whipe re-installed MIUI 1.10.7 flashed nertchy and i was good to go.. once booted up as apps where getting restored from the market random crashed started and now everything force closes.
that is not the issue.. the issue is that i want to do a full whipe again.. how ever i can not do anything with sdcard. i have tried every possible format method and coping files to sdcard...
all it ends up is restoring the files and the file that i have copied to sdcard is gone wth :S
i can boot the system back to what it was even when i re-flash it over again still same system there trying to download files and crashing..
i have reached the end i dont know what it possible could have changed :S
help?
You could try and lock the bootloader and unlock it again. That might reset everything and get it working for you again. I had a problem with the SD card and I wasn't able to mount it in CWM to access any files so I locked and then unlocked the bootloader and everything has been working great again
no go.
earlier i tried pushing some files to sdcard using adb successfully. this only lasted until the phone was rebooted out of recovery and files where back to w/e they where before.
i pushed an filed called update.zip tried flashing.. as if i never tried.
what it seems to me like is that the whole system is preventing updates/changes to the system :S :S
no matter what i try to do to reinstall or format it goes back into its old form with exact same files and exact same problems..
basically unable to flash and delete :S:S
have you went to storage in setting menu and hit erase then erase everything?
yes,
i have tried all of the following:
- factory reset from settings
- unmounted sdcard and formatting from settings
- delete files using file explorer (deleted them but comes back on reboot)
- uninstalling application (error occurs)
- moving application to sdcard from internal storage (not enough space error occurs)
- doing factory reset using cwm
- doing individual deletes using cwm
- creating backup using cwm (error occurs, cant get chm5)
- locking/unlocking bootloader
- mounting sdcard to pc and deleting files (same thing files delete until reboot then restore)
- adb remount (remounts nothing happens)
- adb push file, i can push a file and its only there until phone reboots
- installing pushed file update.zip (miui 2.1.x) installs but still goes back to corrupted miui 1.10.7..
i don't remember what else i have tried. every time file deletes it comes back after reboot. as well as the system.
i can flash a new recovery mod and it will stick but nothing in terms of deleting files or installing new system files.
new development.. i have tried installing update.zip from fastboot menu
and this is what happens:
sending 'system' ... Okay
writing 'system' ....failed (remote: write fail)
it almost seems as if i lost all write access.. is there a way to fix this?
(fix permissions does not fix this problem)
cheers,
as the Nexus s has no actual physical SD card but it purely refers to the storage partition, I am guessing you have some how corrupted the partitions settings and possibly damaged the memory as well, i have also seen from other threads where this issue is nearly identical that the PCB board being changed fixed the problem.
sorry to say either way your Nexus S may need to go under the knife,
hmm, this was the last day i played with it...
i'll have a look tomorrow for a bussins that will take it and try to fix it
cheers, for all those who tried to help.

[Q] HELP... hosed up the SR

Damn... got a bit too adventurous with the SR. Used the UOT Kitchen to make a simple battery/icon mod. Created the zip successfully.. but don't have CWM installed (running stock 3e Recovery). I was rooted running OTA 2.3.6. On my PC, I extracted the framework-res.apk from the zip and moved it to the SR. Moved it to /system first to fix permission (rw.r.r), then was going to move it to /system/framework folder. But being a complete azzclown, I thought I'd be cautious and rename my stock framework-res.apk to framework-res.apk.OEM. Didn't even have a chance to move the cooked up framework-res.apk to /system/framework folder cause as soon as I renamed the good framework-res.apk, I was in FC hell. F. Anyway, now I'm stuck at the "SAMSUNG" boot screen. What's the best course of action at this point?
I can get into stock 3e Recovery Mode... but hoping there's a way I can just somehow rename my good framework-res.apk.OEM back to framework-res.apk. (Reality tells me I can't). Anyway, I do have a Titanium Backup on my external SD. Just not sure what the best steps are from 3e Recovery: In 3e Recovery, do I "wipe data/factory reset" ? Do I need to "wipe cache partition", or will I just F it up more.
I m pretty sure this will help!
it's Sean's work!
When in 3 e recovery do a factory data reset (home button is enter)
7. now close and reopen odin
8.pull the battery on your phone and put it back into download mode
9.in the pda slot this time select clockwork recovery.tar
10.make sure your phone is in the com slot and hit flash
11. now reboot into clockwork also doing a factory data reset
12.clearing cache partition
13.go to advanced and clear dalvik cache
14. lastly go under mounts and storage and format system
15. now install any rom of choice .. your phone should be clean
DoctorQMM said:
Damn... got a bit too adventurous with the SR. Used the UOT Kitchen to make a simple battery/icon mod. Created the zip successfully.. but don't have CWM installed (running stock 3e Recovery). I was rooted running OTA 2.3.6. On my PC, I extracted the framework-res.apk from the zip and moved it to the SR. Moved it to /system first to fix permission (rw.r.r), then was going to move it to /system/framework folder. But being a complete azzclown, I thought I'd be cautious and rename my stock framework-res.apk to framework-res.apk.OEM. Didn't even have a chance to move the cooked up framework-res.apk to /system/framework folder cause as soon as I renamed the good framework-res.apk, I was in FC hell. F. Anyway, now I'm stuck at the "SAMSUNG" boot screen. What's the best course of action at this point?
I can get into stock 3e Recovery Mode... but hoping there's a way I can just somehow rename my good framework-res.apk.OEM back to framework-res.apk. (Reality tells me I can't). Anyway, I do have a Titanium Backup on my external SD. Just not sure what the best steps are from 3e Recovery: In 3e Recovery, do I "wipe data/factory reset" ? Do I need to "wipe cache partition", or will I just F it up more.
Click to expand...
Click to collapse
Appdroid... thanks for the quick reply... appreciate the help. I was avoiding putting CWM on until official ICS OTA rolled out... was going to keep the OTA 2.3.6 and 3e Recovery until then. If I wipe data/factory reset from 3e Recovery, will this put framework-res.apk back in /system/framework? Or is my only option now is going to download mode and Odin flash (and trip the counter)...
It may work, try it ans see, i wont hurt anything, have you ever had cwm on your device at all?
Sent from my Transformer TF101 using xda premium
cdshepherd said:
It may work, try it ans see, i wont hurt anything, have you ever had cwm on your device at all?
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
I've never installed CWM... I rooted the stock 2.3.5 with SuperOneClick back in November, then took the OTA 2.3.6 update... and maintained my root. I just did the wipe data/factory reset.. that looks like it only wiped my user data and reformatted the /data partition. Now when I try to get back into Recovery Mode, I get a white triangle with a yellow exclamation in the middle.. and a green droid under that.. WTF?
OK... I can get back into 3e Recovery... but can confirm, the "wipe data/factory reset" only erases user data... it formats the /data and /cache partitions. When I reboot from Recovery, it still gets stuck at the 2nd SAMSUNG during boot. Do I need to Odin flash CWM, or can I somehow Odin flash the stock 2.3.5 with 3e Recovery, then re-root... or will flashing the stock ROM also trip the counter?
I believe kernal only trips counter, but who cares about the counter. Do what you gotta do to save her. You could prob just odin cwm, wipe and flash a rom
Sent from my Transformer TF101 using xda premium
UPDATE: saved the Rocket!
Appdroid, cdshepherd: Thanks (and XDA Thanks buttons pressed as well!). Brought the SR back from the brink of brickmania. Nearly 5 hours of hell from one idiotic move (which was renaming "framework-res.apk" instead of simply overwriting it with the UOT Kitchen cooked-up mod). Anyway, used Sean's method to wipe phone and Odin flash CWM. Then the fun really started when it was time to flash a ROM via CWM.. and I had no ROMs on my sdcard! So pulled my external sd out of SR, put it in a MicroSD adapter... then discovered my desktop computer couldn't read my MicroSD! So, shoved the MicroSD adapter in my work laptop, it auto-added drivers so SD was recognized in the laptop. Then, back to the desktop and copied my ROM of choice (went with silver03wrx's Stock 2.3.6) onto a USB flash drive. Ported the USB flash drive over to the laptop and copied the Stock 2.3.6 ROM to the MicroSD. Finally, popped the external SD out of the adapter and back in the SR... booted into CWM recovery, and flashed the ROM from the external SD. Things began to become much more clear after my 3rd beer and the clock striking 1am!
Re-downloaded Visual VoiceMail, Superuser, and all my purchased apps. After reinstalling Root Explorer, I actually braved the UOT Kitchen fiasco again and flashed my Kitchen mods... all working to perfection. Titanium restored all my user apps+data (and yes, did NOT restore ANY system stuff). 2am now and all that remains is to reinstall the volume button camera mod and translucent 3.4.4 Market app (both of which are pretty cool), and get my home-screen widgets re-setup. Oh, and by the way, my custom binary counter is still "NO", and says "SAMSUNG OFFICIAL". After all of this, I'm not sure why I even cared about the counter.... but in any event, it's still "0". Thanks XDA for all the stellar helpful posts and development materials.
Glad she's back up and running. A good thing to remember is, when your In CWM. You can plug your USB into phone/computer. Go to mounts and storage option in cwm and click mount USB storage. Then you can copy files between your SD and computer without having to do the SD card swap fiasco. Always remember to unmount SD from computer first. Hope this helps and good luck buddy!
EDIT: don't forget to make a nandroid backup. It can easily save ya
Sent from my SAMSUNG-SGH-I727 using xda premium
You're not alone. I did the exact same thing! Wish I would have never tried to make my own battery mod...But I'll probably try it all over again!
cdshepherd said:
Glad she's back up and running. A good thing to remember is, when your In CWM. You can plug your USB into phone/computer. Go to mounts and storage option in cwm and click mount USB storage. Then you can copy files between your SD and computer without having to do the SD card swap fiasco. Always remember to unmount SD from computer first. Hope this helps and good luck buddy!
EDIT: don't forget to make a nandroid backup. It can easily save ya
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Good to know! That MicroSD card swap and USB Flashdrive nonsense was insane. Thanks.
vonerk said:
You're not alone. I did the exact same thing! Wish I would have never tried to make my own battery mod...But I'll probably try it all over again!
Click to expand...
Click to collapse
I was pissed at myself for such a bonehead move (renaming an active framework file). After going through the whole process to bring the SR back from the dead, I was determined to get that freaking battery icon mod installed and risk it all again! Fortunately, it worked this time and all is good. With CWM now installed, I could have just flashed the UOT Kitchen zip... but was sure my Root Explorer process would work so did it again, but this time I "replaced" the active file instead of renaming the active apk.
DoctorQMM said:
I was pissed at myself for such a bonehead move (renaming an active framework file). After going through the whole process to bring the SR back from the dead, I was determined to get that freaking battery icon mod installed and risk it all again! Fortunately, it worked this time and all is good. With CWM now installed, I could have just flashed the UOT Kitchen zip... but was sure my Root Explorer process would work so did it again, but this time I "replaced" the active file instead of renaming the active apk.
Click to expand...
Click to collapse
Hey glad you got it back!! I tell you, I'm thinking about buying a used phone just to practice & experiment on.
Sent from my SGH-I727R using xda premium

[Q] Ooops - Tab's funked. Help!

P6800 running Zeta
I was browsing facebook the other night when... shaboom - everything froze. No biggie I thought, I'll just do a little reset (I was getting a few FCs here and there anyway lately) and I'll be good to go...
NOPE. It started bootlooping at the initial Samsung Galaxy Tab 7.7 screen. I'm able to enter CWM recovery and even wipe the cache and flash ZIP files, but when I try to wipe data/factory reset, wipe the Dalvik cache or restore a Nandroid backupI get a System Error. It doesn't look good.
Is there a way to fix my seemingly funked /system without losing all my internal SD card data (where my Titanium backups reside) or to recover it before a full Odin flash?
Just tried again - it reboots and goes into a loop when I try to wipe data and dalvik, and when I try to restore a previous backup it gives me "Error while restoring /system!"
Any help greatly appreciated before it becomes a $600 door stop
Do you dare to wipe the system folder and follow by flashing another ROM?
Sent from my GT-P6800 using xda app-developers app
iena said:
Just tried again - it reboots and goes into a loop when I try to wipe data and dalvik, and when I try to restore a previous backup it gives me "Error while restoring /system!"
Any help greatly appreciated before it becomes a $600 door stop
Click to expand...
Click to collapse
ok... try go long way... download old HC stock rom and install that... then try go to stock recovery in hc and wipe your data
Thread moved to Q & A section, post in the relevant section next time.
edan1979 said:
ok... try go long way... download old HC stock rom and install that... then try go to stock recovery in hc and wipe your data
Click to expand...
Click to collapse
Do you mean via Odin? Will I lose the data on my internal SD card by doing that? Is there any way of mounting the device in its current state as external storage on my PC to copy all data before a wipe?
ZhenMing: I'm not sure what you mean, but as I wrote above I am not able to wipe the system folder.
yes you will loose your data... i can give you another advice... but do this one carefully... the reason why your device cant wipe any /system or /data is because the corrupted partition... you need to check it... follow the guide in this thread...
USE ONLY PART 3... follow the guide start from this para to check your device...
Code:
Now we are going to use e2fsck to check our new partitions for errors, but not only, it also fixes some erros and it will even for example create lost & found in /data
So let's go, we'll begin with /system. If you're still in the (parted) shell, use ctrl+c and type "adb shell", then issue the following :
http://forum.xda-developers.com/showthread.php?t=1862294
iena said:
Do you mean via Odin? Will I lose the data on my internal SD card by doing that? Is there any way of mounting the device in its current state as external storage on my PC to copy all data before a wipe?
ZhenMing: I'm not sure what you mean, but as I wrote above I am not able to wipe the system folder.
Click to expand...
Click to collapse
Since you can go into cwm, you can mount your storage and then connect to PC to copy all you want.
edan1979 said:
yes you will loose your data... i can give you another advice... but do this one carefully... the reason why your device cant wipe any /system or /data is because the corrupted partition... you need to check it... follow the guide in this thread...
USE ONLY PART 3... follow the guide start from this para to check your device...
Code:
Now we are going to use e2fsck to check our new partitions for errors, but not only, it also fixes some erros and it will even for example create lost & found in /data
So let's go, we'll begin with /system. If you're still in the (parted) shell, use ctrl+c and type "adb shell", then issue the following :
http://forum.xda-developers.com/showthread.php?t=1862294
Click to expand...
Click to collapse
But won't it downsize the int sd size, if OP tab still under warranty, better to get it fix by samsung for free and not lost any space.
Just reading the 1st post of the ZETA rom thread.
He says he is using stock Kernel.
He says every 5 lines, that you should full wipe...
without giving any sort of warning that it will eventually brick your device.
friedje said:
Since you can go into cwm, you can mount your storage and then connect to PC to copy all you want.
Click to expand...
Click to collapse
Tried that one, but it won't mount unfortunately. The external will no problem, but when I try with the internal it just... well it does nothing. It's a bummer cause all my most recent backups are on the internal. Any other way of retrieving my data short of extracting the chip?
Giving it back to Samsung sounds like the best option, but I'm worried cause it has a custom ROM and it's rooted. Anyone has experience doing that?
Also I thought full wipes were good, but you're saying they eventually brick the device? How come? I thought having a custom recovery meant it would be virtually impossible to brick my device... and the weird thing is that it happened during normal usage, not while flashing.
Anyway, my priority is obviously to get my tab working again, but retrieving my internal data is second highest. Isn't there a flashable ZIP that would copy the contents of the internal SD into an external SD card? Surely this has happened to someone before me?
Thanks for all the answers, really appreciated!
bruce16878 said:
But won't it downsize the int sd size, if OP tab still under warranty, better to get it fix by samsung for free and not lost any space.
Click to expand...
Click to collapse
nope it wont... the 3rd stage on that thread command for just check and fix the corrupted partition... its like when we force boot windows... it will run on a little diagnostic software to check the drive... same concept.
Oh I see, Thanks for the explanation. Learn something new today.
Sent from my LT18i using xda app-developers app
friedje said:
Since you can go into cwm, you can mount your storage and then connect to PC to copy all you want.
Click to expand...
Click to collapse
edan1979 said:
nope it wont... the 3rd stage on that thread command for just check and fix the corrupted partition... its like when we force boot windows... it will run on a little diagnostic software to check the drive... same concept.
Click to expand...
Click to collapse
Gotcha! Will try that one and post result - thanks!
how did your partition check go?
i'm annoyed that some partitions can be corrupted randomly even doing some mundane stuffs
even on stock ICS fw, i encountered DATA corruption by just deleting a contact
i guess you have softbrick..
here is what i did:
-flash stock Honeycomb firmware using Odin
-forced tablet into stock recovery mode
-wipe Cache/Data/Factory Reset
- reboot
when your tab is working again you could backup files from your internal EMMC and you could flash ROMS from there
JAYZE said:
how did your partition check go?
i'm annoyed that some partitions can be corrupted randomly even doing some mundane stuffs
even on stock ICS fw, i encountered DATA corruption by just deleting a contact
i guess you have softbrick..
here is what i did:
-flash stock Honeycomb firmware using Odin
-forced tablet into stock recovery mode
-wipe Cache/Data/Factory Reset
- reboot
when your tab is working again you could backup files from your internal EMMC and you could flash ROMS from there
Click to expand...
Click to collapse
Thanks for that. I haven't tried anything yet as I'm away till Weds, but I will then and let you know. So you're saying by flashing stock HC via Odin and wiping/resetting everything through stock recovery I won't lose my internal storage data?
that's what i experienced..but i could not guarantee that it will be the same for your device
i noticed that because old folder are not deleted when i rebooted, but i haven't checked if the system folders are cleared
to have a clean reflash i also format/sdcard on recovery..but don't do this on stocl ICS recovery since you might risk increasing the damage
try to format via odin the Honeycomb fw first [don't put PIT file neither enable Repartion, just normal flash]
then force it to enter recovery mode when it bootloops after reset
you might fix your device this way if it has softbrick
just resort to using PIT/repartition as your last option
Again I would not recommend repartition when tab still under warranty. Repartition the last resort only if the tab is without warranty after failing all other alternatives.
JAYZE said:
how did your partition check go?
i'm annoyed that some partitions can be corrupted randomly even doing some mundane stuffs
even on stock ICS fw, i encountered DATA corruption by just deleting a contact
i guess you have softbrick..
here is what i did:
-flash stock Honeycomb firmware using Odin
-forced tablet into stock recovery mode
-wipe Cache/Data/Factory Reset
- reboot
when your tab is working again you could backup files from your internal EMMC and you could flash ROMS from there
Click to expand...
Click to collapse
+1
After a full hangup, your stock hc is your first step out of the dark!
Best of luck
al128 said:
+1
After a full hangup, your stock hc is your first step out of the dark!
Best of luck
Click to expand...
Click to collapse
Ok I'm gonna do it. There are dozens of versions of HC for the 6800 though, can I just pick any or do I need to find out what it was running out of the box? Mine came from Singapore.

[Q] How do properly install KatKiss ROM?

Hi
My problem with battery drain, somehow, was kind of solved. If I "full wipe battery stats" at 100% and never EVER let it run out of juice, it would last as longer as I would want.
And
I couldn't manage, by any means, to push the ROM into the tablet, adb push didn't work. So as my problem was solved I gave up.
http://forum.xda-developers.com/showthread.php?t=2367518
But now I got two bigger problems, the battery of my tablet never goes to 100%, it finishes recharging at 93% and my dock station does not recharge, doesn't matter how long I let it on the power supply. Plus the light indicator is always blinking on red.
Every key works perfectly, the pointer track too and all the USB ports aswell. I can even recharge the tablet with the dock connected, so energy seems to be flowing fine.
I was told that installing a brand new system can solve this, so I want to give it a shoot.
I was told too that this KatKiss ROM is very good, so why not?
http://forum.xda-developers.com/showthread.php?t=2392087
To do that I must upgrade my recovery to this version:
http://forum.xda-developers.com/showthread.php?t=2434422
So to avoid any mistakes like this one:
http://forum.xda-developers.com/showthread.php?t=2144143
I want to ask:
How do properly install KatKiss ROM?
Off-Topic Question:
Should I wait for android 4.4 KitKat
Here is some useful information:
Thank you very much!
For your dock battery, there is a chance that the switch in the doc for the battery charge circuit changed state. If you are good with delicate work, might be worth a shot to open up the dock and give that a look. 2 screws under the rear rubber feet then it prys a part. I start from one of the back corners and work around when I have opened mine.
So, I would HIGHLY recommend upgrading to TWRP. There are a few ways to do it. If you can boot your ROM, put the TWRP.zip file from this thread: http://forum.xda-developers.com/showthread.php?t=2434422 on the /sdcard/ and flash it from recovery. REBOOT NORMALLY. If you try to reboot directly to recovery it won't work.
If you cannot boot to your ROM, you will have to use ADB to push the file to the internal directory.
If that does not work, try EasyFlasher. I have a tutorial here as well as newer versions of TWRP bundled with EasyFlasher: http://www.transformerforums.com/fo...nt/31927-frederucos-guide-root-rom-tf101.html
Once you get TWRP installed, make a nandroid of what you currently have just in case.
Then wipe the following: Cache, Davlik, System, Data (note wipe data will not completley wipe the /sdcard/ partition, only the FORMAT DATA or WIPE INTERNAL will wipe the /sdcard/).
Install the KatKiss ROM and the applicable GAPPS 2nd.
Wipe caches
Reboot.
I have a thread for KatKiss for n00bs here:http://www.transformerforums.com/fo...f101-roms/38407-rom-jb-4-3-katkiss-tf101.html
frederuco said:
For your dock battery, there is a chance that the switch in the doc for the battery charge circuit changed state. If you are good with delicate work, might be worth a shot to open up the dock and give that a look. 2 screws under the rear rubber feet then it prys a part. I start from one of the back corners and work around when I have opened mine.
So, I would HIGHLY recommend upgrading to TWRP. There are a few ways to do it. If you can boot your ROM, put the TWRP.zip file from this thread: http://forum.xda-developers.com/showthread.php?t=2434422 on the /sdcard/ and flash it from recovery. REBOOT NORMALLY. If you try to reboot directly to recovery it won't work.
If you cannot boot to your ROM, you will have to use ADB to push the file to the internal directory.
If that does not work, try EasyFlasher. I have a tutorial here as well as newer versions of TWRP bundled with EasyFlasher: http://www.transformerforums.com/fo...nt/31927-frederucos-guide-root-rom-tf101.html
Once you get TWRP installed, make a nandroid of what you currently have just in case.
Then wipe the following: Cache, Davlik, System, Data (note wipe data will not completley wipe the /sdcard/ partition, only the FORMAT DATA or WIPE INTERNAL will wipe the /sdcard/).
Install the KatKiss ROM and the applicable GAPPS 2nd.
Wipe caches
Reboot.
I have a thread for KatKiss for n00bs here:http://www.transformerforums.com/fo...f101-roms/38407-rom-jb-4-3-katkiss-tf101.html
Click to expand...
Click to collapse
Hi Freduco!
I will leave any hardware approach after dealing with the software.
Here is the TWRP updated (Glad it worked)
Going to try now the system
Edit. 1
FINALLY the EasyFlasher worked!!!
I guess it was a problem with my old Recovery
Before doing that I wiped: CACHE, DAVLIK CACHE, FACTORY RESET, SYSTEM and INTERNAL.
I have flashed both:
KatKiss-4.3.1_027.zip
gapps-KatKiss-4.3_20130914.zip
But when I go to install on the TWRP there is no .zip to install.
There are several android system folders like the system is already installed, but I don't know.
Do I need to "Bootloader" or something?
Please help me,
I think it is the last thing I need to do
Filipebergami said:
Please help me,
I think it is the last thing I need to do
Click to expand...
Click to collapse
How is your microSD formatted?
You are using TWRP 2.2.1.4 which only supports FAT32. You will need to boot to recovery AFTER inserting the microSD. It is not hot swappable.
Also, I would recommend TWRP 2.3.2.3 or later as 2.2.1.4 does not properly support the new directory structure when flashing updates to 4.2.X and later ROMs. It is fine for initial install though.
frederuco said:
How is your microSD formatted?
You are using TWRP 2.2.1.4 which only supports FAT32. You will need to boot to recovery AFTER inserting the microSD. It is not hot swappable.
Also, I would recommend TWRP 2.3.2.3 or later as 2.2.1.4 does not properly support the new directory structure when flashing updates to 4.2.X and later ROMs. It is fine for initial install though.
Click to expand...
Click to collapse
I am not using a microSD card,
I am flashing the KatKiss-4.3.1_027.zip and the gapps-KatKiss-4.3_20130914.zip with Easy-Flash (Its meant to be used instead of the /adb push stuff, right?)
But easy-flash isn't copying the .zip it seems it is extracting everything alread, so I don't know how to install it.
Now that everything is wiped, to install a new Recovery system, I need to do the /adb push stuff again?
Filipebergami said:
I am not using a microSD card,
I am flashing the KatKiss-4.3.1_027.zip and the gapps-KatKiss-4.3_20130914.zip with Easy-Flash (Its meant to be used instead of the /adb push stuff, right?)
But easy-flash isn't copying the .zip it seems it is extracting everything alread, so I don't know how to install it.
Now that everything is wiped, to install a new Recovery system, I need to do the /adb push stuff again?
Click to expand...
Click to collapse
Ok, you cannot use EasyFlasher to flash KatKiss because the files are not in SOS format.
EasyFlasher can flash Stock firmware (as downloaded from Asus, not unzipped) and also .sos files for recoveies.
Once you get TWRP installed, use that to install your ROM.
If you do not have a microSD, it is much easier if you get one, even a small 1-4 GB one.
Otherwise, you need to use ADB to push the ROM and GAPPS to the /sdcard/ when the tablet is in recovery (and if you are on TWRP 2.6 or newer you need to enable ADB sideload in the recovery).
Alternatively, you could flash back to stock with EasyFlasher. Then download the files into the /sdcard/. After that, flash TWRP with EasyFlasher and then boot to TWRP and install the files from the internal memory.
frederuco said:
Ok, you cannot use EasyFlasher to flash KatKiss because the files are not in SOS format.
EasyFlasher can flash Stock firmware (as downloaded from Asus, not unzipped) and also .sos files for recoveies.
Once you get TWRP installed, use that to install your ROM.
If you do not have a microSD, it is much easier if you get one, even a small 1-4 GB one.
Otherwise, you need to use ADB to push the ROM and GAPPS to the /sdcard/ when the tablet is in recovery (and if you are on TWRP 2.6 or newer you need to enable ADB sideload in the recovery).
Alternatively, you could flash back to stock with EasyFlasher. Then download the files into the /sdcard/. After that, flash TWRP with EasyFlasher and then boot to TWRP and install the files from the internal memory.
Click to expand...
Click to collapse
Alright! Stock worked!
Can I install the Katkiss and gapps with the TWRP without wipe Internal now its stock? Otherwise I will lose it again
Filipebergami said:
Alright! Stock worked!
Can I install the Katkiss and gapps with the TWRP without wipe Internal now its stock? Otherwise I will lose it again
Click to expand...
Click to collapse
Any time you flash from any ROM to another, unless it is a newer version (say KatKiss 026 to KatKiss 027) you should ALWAYS wipe the data (factory reset).
Not doing this can cause some fragments of system data to cause instabilities (Random Reboots and Sleep Of Death).
To go from Stock to KatKiss, I would not try it without wiping Data, System, Cache and Davlik in TWRP.
Wiping the Data partition in TWRP will not actually wipe the files on the /sdcard/, it only wipes those in the /data/ partition without touching /data/media/.
However - if you choose the (depends on version of TWRP) FORMAT DATA or FORMAT INTERNAL it will wipe out the /sdcard/
Before doing anything further, I recharged the both tablet and dock.
The 93% battery bug is solved, now its 100%, although the dock still not recharging.
So since I am selling the tablet I will leave it stock, the buyer may complain about battery drain, freezes or random reboots, things I had with Android Revolution HD.
The dock... I will try to contact Asus about my problem and ask a blueprint where should I find this circuit you told me about.
If you can lead me with good video tutorials or forum threads about how to open and find that circuit I would be really grateful.
Thank you for all your help and kindness Freduco !
Have a look at this thread: http://forum.xda-developers.com/showthread.php?t=2381186
The dock is pretty easy to open. Remove the rear rubber feet, 2 screws, and then start from a back corner and pop it open.
That board is on the left.
frederuco said:
Have a look at this thread: http://forum.xda-developers.com/showthread.php?t=2381186
The dock is pretty easy to open. Remove the rear rubber feet, 2 screws, and then start from a back corner and pop it open.
That board is on the left.
Click to expand...
Click to collapse
I opened the dock and the switch was already on, I changed to "off" and "on" again, but it still not recharging.
More than 2 hours on the power supply and red light still blinking,
What else can be done?

Categories

Resources