Related
Hello, I've got a problem and I'd be very happy for any advice.
I am on rom JellyBean AOSP. I was using my Transformer and sound stopped working. So I decided to turn it off and on again and when I tried to turn it on and I wasn't able to start tablet anymore. I'm stuck on the first screen you see when you turn on the tablet. So I wanted to do factory reset in the recovery. In recovery everything works allright. When I click on the factory reset it says error when deleting something in /data/ and I also can't do "Format /data/" because of the same error.
Here is the log from recovery - https://dl.dropbox.com/u/3045404/recovery.log
How can I completely delete /data/ can I do it somehow from PC for example? I don't care about my data I can lose everything. I just want to get it work. I also tried to flash AOSP JellyBean ROM again, but with the same effect. I think that tablet just can't do the factory reset but I don't know why. Thanks for any advice.
Hi there !
I think you should try to start your tablet into ADB mode, connect it to your computer and use the "adb shell" command. If your tablet was rooted, then you might be able to use the "su" command, but that depends also on your settings (I mean your Android settings... those you can't change anymore ).
Another way to get your TF101 working again is to use the NVflash "unbrick pack". OK, you'll be running the stock non-rooted ROM, but you'll be able to root it again and install a new fresh copy of your Android AOSP. I'm going to search for a link to this nvflash and I'll post it asap.
By the way, were you using the AOSP "alpha" from RaymanFX ?
EDIT : NVflash unbrick pack is here, and you also might want to try with EasyFlasher !
Thanks, I'll try it. Yes, I've been using alpha from RaymanFX. I haven't done anything that could "brick" my device while using the tablet before I turned it off.
This is what tablet shows after I attempt to do a factory reset. https://dl.dropbox.com/u/3045404/DSC05813.JPG
GameEs said:
This is what tablet shows after I attempt to do a factory reset.
Click to expand...
Click to collapse
That's weird. And you're using an old CWM Recovery
I think in most CWM versions there's a "fix permissions" item, you could try this one first. Im' not sure of what it exactly does, but it might do the trick: a permission-related problem seems (to me) a good reason for displaying this kind of errors...
yeah I also tried fix permissions but didn't help. I also remembered that it sometimes freezes even in the recovery. Is it safe to flash a new recovery NOW when I'm not able to startup the tablet? Please could you link me to the best recovery that I should flash? thanks a lot. I'm careful about it and I don't want to do something that would brick my device.
I dunno if it is the best recovery, but I prefer to use the CWM Recovery.
You'll find the 6.x series here.
I actually use the 6.x on my Sony Xperia Ray.
On my TF101, I use this touch Rogue recovery, not as recent as the first one. In fact I never did the update 'cause I'm waiting for the next release of RaymanFX's CM10 release to flash everything
EDIT: And I think you can flash a new recovery safely, because it's not on the same partition as the Android system. And in the case it fails, you should be able to boot in ADB mode and use the NVflash unbrick pack to get your device up and running !
oh god thank you so much. New recovery helped a lot it did factory reset and everything works allright. I would like to ask you one more question. what's in your opinion best rom for Transformer? I just want it to be stable. Because I don't like freezing every day and slow motion through tablet. I tried many roms but it was always unreliable. Thank you )
Great !
About the ROM s, one told me that Revolver is a great one, but I never used it.
I never had problems with CyanogenMod 9. I would recommend that one !
For now I'm running RaymanFX's CM10 build, which is great too !
Sent from my Transformer using xda premium
I've just done the JB update on my TF700, and it's now dead... :crying:
Update downloaded OK, went into the update process. Seemed to go fine. Did the "Optimising applications" bit, rebooted, and stuck on the boot screen with the spinnywheel.
I let that run for half-an-hour (tablet was getting very warm) then did a paper-clip reset (no response to buttons). Same thing, won't boot.
It's an unmodded device apart from being rooted. I've encrypted the storage; I've set the default browser to Dolphin. I have Titanium installed, but not frozen any apps.
Suggestions for how to recver from this gratefully received ....
Thanks
Alan
[UPDATE: Oh, and I did not have the tablet in the dock when I updated. Significant??]
Same problem here. Please help!!
Did the update and it went all ok.. untill first reboot (stuck on boot screen with the spinnywheel).
Unmodded rooted device. Tried cold boot, but nothing changes.
Tried to download some files for recovery and didn´t work:
TF700T WW_10.4.4.16-20120927 OTA.zip
WW_epad-user-9.4.5.30.zip
any ideas?
Piruelo said:
Same problem here. Please help!!
Did the update and it went all ok.. untill first reboot (stuck on boot screen with the spinnywheel).
Unmodded rooted device. Tried cold boot, but nothing changes.
Tried to download some files for recovery and didn´t work:
TF700T WW_10.4.4.16-20120927 OTA.zip
WW_epad-user-9.4.5.30.zip
any ideas?
Click to expand...
Click to collapse
try booting into bootloader and selecting the "wipe data" option. This will delete all your files on the devices but will also mean you can use it again
Piruelo said:
Same problem here. Please help!!
Did the update and it went all ok.. untill first reboot (stuck on boot screen with the spinnywheel).
Unmodded rooted device. Tried cold boot, but nothing changes.
Tried to download some files for recovery and didn´t work:
TF700T WW_10.4.4.16-20120927 OTA.zip
WW_epad-user-9.4.5.30.zip
any ideas?
Click to expand...
Click to collapse
To recover from that just wait until Asus post the full JB update on their site and use that to do a Factory Restore with stock recovery (follow the how-to guide in my signature for more details).
Thanks!!
Will the 'Factory Restore with stock recovery' erase my internal storage?
Piruelo said:
Thanks!!
Will the 'Factory Restore with stock recovery' erase my internal storage?
Click to expand...
Click to collapse
It shouldn't wipe the sdcard, only the Wipe Data option from the stock recovery should do that.
Pretoriano80 said:
To recover from that just wait until Asus post the full JB update on their site and use that to do a Factory Restore with stock recovery (follow the how-to guide in my signature for more details).
Click to expand...
Click to collapse
Thanks for that.
A newbie question, though (I'm a Windows dev, and Android is quite new to me) - what would happen if did this with the .30 ICS firmware with the device in this state?
SpooRancher said:
Thanks for that.
A newbie question, though (I'm a Windows dev, and Android is quite new to me) - what would happen if did this with the .30 ICS firmware with the device in this state?
Click to expand...
Click to collapse
You can try to do that,but i guess it will just fail to install...You could also try the "Wipe Data" thing from the recovery ,but i don't think it will work.
Pretoriano80 said:
You can try to do that,but i guess it will just fail to install...You could also try the "Wipe Data" thing from the recovery ,but i don't think it will work.
Click to expand...
Click to collapse
OK, many thanks. I'll give it a go - otherwise it's just wait for Asus to post the files
SpooRancher said:
I've just done the JB update on my TF700, and it's now dead... :crying:
Update downloaded OK, went into the update process. Seemed to go fine. Did the "Optimising applications" bit, rebooted, and stuck on the boot screen with the spinnywheel.
I let that run for half-an-hour (tablet was getting very warm) then did a paper-clip reset (no response to buttons). Same thing, won't boot.
...
Click to expand...
Click to collapse
I have the same exact problem.
Most probably, it's because of the encryption.
Perhaps ASUS thought that nobody would use Android encryption ...
i have exactly the same problem, was stock and only rooted. i did a backup with titanium backup and one of my internal sdcard via the dock sdcard and adb now but i'm still trying to find a way to boot without wiping because i fear that i will lose root and so goes my titanium backup..
anyways, it seems i've got adb access (no root because su crashes) during this neverending spinning wheel. i've dumped logcat during the boot process. maybe someone has a suggestion what's wrong here? i have a good understanding of linux but not the logcat output or android boot phase. it seems many services can't find files and many things fail (wifi, gps, tethering, ...), no idea if that's also the case for a valid boot, and then after some time nearly all services die.
logcat part1: http://pastebin.com/HTSULj59
logcat part2: http://pastebin.com/ncgjzwsY
logcat part3: http://pastebin.com/071hWwRm
i also tried to wipe cache via fastboot, but it didn't help.
i also think it has to do with encryption because it says something like:
"E/VoldConnector( 401): NDC Command {6 cryptfs checkpw $pwd} took too long (10418ms)" and then services get restarted or die
Oops
0x000 said:
i also think it has to do with encryption because it says something like:
"E/VoldConnector( 401): NDC Command {6 cryptfs checkpw $pwd} took too long (10418ms)" and then services get restarted or die
Click to expand...
Click to collapse
Does this imply that it's not possible to recover from this without completely resetting the SD card? Does a Wipe Data do that?
Two extra things I've thought of here: I changed the encryption password from screen lock PIN to something else with EncPasswdChange; however, the "enter encryption password" screen accepted the correct password and rejected anything else. I also have BusyBox installed.
Personally I'm not bothered about having to reset everything - I'm sure JB will be rootable soon, and I have no data I care about. Very annoying for those that do have valuable stuff, though.
ASUS have the JB files on their website now (US and WW SKUs) [Sorry, system won't let me post a link...]
Downloaded from asus, renamed to 'EP201_768_SDUPDATE.zip' in microsd card,and succesfully unbriked, without loosing any data :victory:
Updated fine. Rebooted fine.
Stock, locked and rooted. Supersu+voodoo, unencrypted.
After update I had extreme laggyness only after a sleep. Cold boot seems to have fixed that.
I would like to encrypt. Has anyone successfully encrypted AFTER updating?
I've managed to unbrick mine too
However I had to do a Wipe Data - trying without gave me the dead android with the red triangle as soon as the upgrade started.
Never mind, it's back and running JB. There wasn't any data on it I cared about, so apart from losing root I'm happy.
Thanks for all the advice, everyone. Very much appreciated.
i've also tried to fix the problem in recovery by using the zip file posted on the asus servers. it did something, had some blue progress bar, then it rebooted, had to enter my encryption password and.. it did not work :crying: still spinning wheel and it hangs. i can still use adb, my old su binary is gone, but i'm stuck as i don't want to wipe my data. i need root for using titanium backup again. and yeah, i don't want to unlock for now too :/
did it work for anyone who has their tablet encrypted?
[edit]
i've tried to downgrade to ICS .30 firmware via recovery method and it worked (although i'm not unlocked). it did wipe my whole data though and the tablet is not encrypted anymore. at least i can root again now, upgrade to JB and then encrypt (i hope..)
[/edit]
Piruelo said:
Downloaded from asus, renamed to 'EP201_768_SDUPDATE.zip' in microsd card,and succesfully unbriked, without loosing any data :victory:
Click to expand...
Click to collapse
was your internal storage encrypted?
---------- Post added at 09:20 PM ---------- Previous post was at 09:16 PM ----------
0x000 said:
...
i've tried to downgrade to ICS .30 firmware via recovery method and it worked (although i'm not unlocked). it did wipe my whole data though and the tablet is not encrypted anymore. at least i can root again now, upgrade to JB and then encrypt (i hope..)
Click to expand...
Click to collapse
How did u downgrade to ICS?
did u placed the .zip from asus again in sd card and powered on with pressing volume donw?
How did u downgrade to ICS?
did u placed the .zip from asus again in sd card and powered on with pressing volume donw?
Click to expand...
Click to collapse
yes, i placed the (extracted & renamed) zip from asus to my external microsd card and used stock recovery (volume down).
i've already installed JB now with root and i'm currently restoring my apps with titanium backup
I started with a factory wiped system when I bought it.
I unlocked and rooted
I installed CROMI-X 4.68 and patched to 4.69 with _that v3+ (I think that is one of the stock options for CROMI)
I then installed the MAX kernel RC1 and everything was running pretty well. Still a little laggy here and there but not bad
I had been making Nandroid backups along the way so I felt pretty confident
Then I heard that doing a clean install might be even better and I wasn't exactly sure what options I had selected when installing CROMI the first time so I decided to try a clean install
I got a microsd card and put all of my ROMs and kernels on it
I rebooted into TWRP an went to Wipe-->Advanced Wipe and selected everything but the microSD and wiped it
I then formatted the data partition (I don't think that I had to do this but it felt like it was even more clean somehow)
I then installed CROMI 4.6.8 (this time I selected to disable fsync where I am pretty sure that i didn't last time because I didnot know what it did)
It rebooted fine
Installed 4.6.9 patch
It rebooted fine
Installed MAX RC1 (just like I had before)
Started booting, updated 37 apps and the hung on the starting apps dialog.
Waited a while and rebooted manually and it would hang on the boot animation toward the end
I got a little worried so I tried restoring my last Nandroid backup
Seemed to restore fine but again hung on the boot animation
Started to get more worried now because I thought that this was always my safety net and it didn't seem to be working
Wiped everything again (same as above)
restored the stock JB backup that I had and it booted fine. whew...
Tried a factory reset through stock JB ( I thouugh tthat this would put me back in a situation like I was in during the first install so I could reinstall CROMI and the MAX kernel and be on my way
Again, I then installed CROMI 4.6.8 (disabled fsync again)
It rebooted fine
Installed 4.6.9 patch
It rebooted fine
Installed MAX RC1 (just like I had before)
Started booting, updated 37 apps and the hung on the starting apps dialog.
Waited a while and rebooted manually and it would hang on the boot animation toward the end
This was all done around midnight ladst night and I need to get some sleep so I could come to work today (and write this post )
I am not sure what to do at this point. I really just want a nice clean install of CROMI 4.6.9 with the MAX kernel that I can start using like I want to. I would also like to try disabling fsync to see if it is any less laggy but at this point I may try all of the above steps but leave it enabled to see if that is the variable that is causing my problem. I will try fooling with it again tonight to see if I can get it working. I even re-downloaded all of the zip files in case one of them got corrupt somehow (just trying to cover my bases.
Any thoughts on what I am doing wrong would be greatly appreciated.
sorry for the long post
Jeff
gixxer340 said:
I started with a factory wiped system when I bought it.
I unlocked and rooted
I installed CROMI-X 4.68 and patched to 4.69 with _that v3+ (I think that is one of the stock options for CROMI)
I then installed the MAX kernel RC1 and everything was running pretty well. Still a little laggy here and there but not bad
I had been making Nandroid backups along the way so I felt pretty confident
Then I heard that doing a clean install might be even better and I wasn't exactly sure what options I had selected when installing CROMI the first time so I decided to try a clean install
I got a microsd card and put all of my ROMs and kernels on it
I rebooted into TWRP an went to Wipe-->Advanced Wipe and selected everything but the microSD and wiped it
I then formatted the data partition (I don't think that I had to do this but it felt like it was even more clean somehow)
I then installed CROMI 4.6.8 (this time I selected to disable fsync where I am pretty sure that i didn't last time because I didnot know what it did)
It rebooted fine
Installed 4.6.9 patch
It rebooted fine
Installed MAX RC1 (just like I had before)
Started booting, updated 37 apps and the hung on the starting apps dialog.
Waited a while and rebooted manually and it would hang on the boot animation toward the end
I got a little worried so I tried restoring my last Nandroid backup
Seemed to restore fine but again hung on the boot animation
Started to get more worried now because I thought that this was always my safety net and it didn't seem to be working
Wiped everything again (same as above)
restored the stock JB backup that I had and it booted fine. whew...
Tried a factory reset through stock JB ( I thouugh tthat this would put me back in a situation like I was in during the first install so I could reinstall CROMI and the MAX kernel and be on my way
Again, I then installed CROMI 4.6.8 (disabled fsync again)
It rebooted fine
Installed 4.6.9 patch
It rebooted fine
Installed MAX RC1 (just like I had before)
Started booting, updated 37 apps and the hung on the starting apps dialog.
Waited a while and rebooted manually and it would hang on the boot animation toward the end
This was all done around midnight ladst night and I need to get some sleep so I could come to work today (and write this post )
I am not sure what to do at this point. I really just want a nice clean install of CROMI 4.6.9 with the MAX kernel that I can start using like I want to. I would also like to try disabling fsync to see if it is any less laggy but at this point I may try all of the above steps but leave it enabled to see if that is the variable that is causing my problem. I will try fooling with it again tonight to see if I can get it working. I even re-downloaded all of the zip files in case one of them got corrupt somehow (just trying to cover my bases.
Any thoughts on what I am doing wrong would be greatly appreciated.
sorry for the long post
Jeff
Click to expand...
Click to collapse
I hoped that you had a latest bootloader and TWRP. You can try to follow the procedures below. It works fine for me every time.
1. Boot into TWRP and select "Wipe"
2. Use "Format" instead of Wipe Caches and Data. They are probably the same but I prefer Format method.
3. Install Cromi X V4.6.8. When it is finished, install Patch V4.6.9 on top of V4.6.8 in the Same Session.
4. When you see install the Successful message, now you can reboot and let it update.
5. When you see the Setup Screen, leave it there for about 1 minute and boot it back into TWRP and install the Kernel that you prefer
6. After the Kernel is completed, you can reboot your device and start using it. Good luck and please report back, thanks.
BTW, you don't have to disable FSync during install process. You can manually toggle it on/off after you are happy with your installation and with all the update. If you have some kind of root file manager, you can navigate to this folder: system/ect/init.d and add this line at the end of the 50CleanTWEAKS file: echo 0 > /sys/devices/virtual/misc/fsynccontrol/fsync_enabled. 0 is disable and 1 is enable.
I have TWRP 2.5, not sure about the version of the bootloader.
I will try your suggestions but i do have one question though.
You say "5. When you see the Setup Screen, leave it there for about 1 minute and boot it back into TWRP and install the Kernel that you prefer"
Do you mean when I see the white setup screens just wait for 1 minute and then power off back to recovery? Don't finish the setup?
Thanks again
Jeff
gixxer340 said:
I have TWRP 2.5, not sure about the version of the bootloader.
Jeff
Click to expand...
Click to collapse
This may be the clue!
Boot the tablet with Volume Down and Power buttons and read the tiny script. You should be on the 10.6.1.14.4 or 10.6.1.14.8 bootloader.
If you are not, grab the bootloader/TWRP package from the CROMi-X OP, flash it in TWRP and reboot.
gixxer340 said:
I have TWRP 2.5, not sure about the version of the bootloader.
I will try your suggestions but i do have one question though.
You say "5. When you see the Setup Screen, leave it there for about 1 minute and boot it back into TWRP and install the Kernel that you prefer"
Do you mean when I see the white setup screens just wait for 1 minute and then power off back to recovery? Don't finish the setup?
Thanks again
Jeff
Click to expand...
Click to collapse
Yes, you are correct.
---------- Post added at 01:49 PM ---------- Previous post was at 01:46 PM ----------
berndblb said:
This may be the clue!
Boot the tablet with Volume Down and Power buttons and read the tiny script. You should be on the 10.6.1.14.4 or 10.6.1.14.8 bootloader.
If you are not, grab the bootloader/TWRP package from the CROMi-X OP, flash it in TWRP and reboot.
Click to expand...
Click to collapse
Bootloader Version: 1.00e and Released by Firmware Version: 10.6.1.14.8 :good:
My bootloader is 10.6.1.14.4. is that new enough?
Jeff
gixxer340 said:
My bootloader is 10.6.1.14.4. is that new enough?
Jeff
Click to expand...
Click to collapse
I believed that the bootloader version is the same on both 10.6.14.4 and 10.6.14.8 firmwares. Maybe, someone with a better knowledge can confirm it.
LetMeKnow said:
I hoped that you had a latest bootloader and TWRP. You can try to follow the procedures below. It works fine for me every time.
1. Boot into TWRP and select "Wipe"
2. Use "Format" instead of Wipe Caches and Data. They are probably the same but I prefer Format method.
3. Install Cromi X V4.6.8. When it is finished, install Patch V4.6.9 on top of V4.6.8 in the Same Session.
4. When you see install the Successful message, now you can reboot and let it update.
5. When you see the Setup Screen, leave it there for about 1 minute and boot it back into TWRP and install the Kernel that you prefer
6. After the Kernel is completed, you can reboot your device and start using it. Good luck and please report back, thanks.
BTW, you don't have to disable FSync during install process. You can manually toggle it on/off after you are happy with your installation and with all the update. If you have some kind of root file manager, you can navigate to this folder: system/ect/init.d and add this line at the end of the 50CleanTWEAKS file: echo 0 > /sys/devices/virtual/misc/fsynccontrol/fsync_enabled. 0 is disable and 1 is enable.
Click to expand...
Click to collapse
I followed your recipe exactly and it seems to have worked like a charm. I did leave fsync enabled this time as well. I am now setting everything back up. Thanks a lot for the help.
Jeff
gixxer340 said:
I followed your recipe exactly and it seems to have worked like a charm. I did leave fsync enabled this time as well. I am now setting everything back up. Thanks a lot for the help.
Jeff
Click to expand...
Click to collapse
It is great that you got your tablet going. About the FSync, you don't have to hurry to disable it. You can manually toggle it off later when everything is running good. It improves your I/O speed quite bit. Just to remember to enable it when you do a major update or app installations. Good luck.
gixxer340 said:
My bootloader is 10.6.1.14.4. is that new enough?
Click to expand...
Click to collapse
LetMeKnow said:
I believed that the bootloader version is the same on both 10.6.14.4 and 10.6.14.8 firmwares. Maybe, someone with a better knowledge can confirm it.
Click to expand...
Click to collapse
The 10.6.1.14.4 and 10.6.1.14.8 bootloaders are identical (except for version number and build date).
_that said:
The 10.6.1.14.4 and 10.6.1.14.8 bootloaders are identical (except for version number and build date).
Click to expand...
Click to collapse
Thanks _that for the confirmation. :good:
gixxer340 said:
I followed your recipe exactly and it seems to have worked like a charm. I did leave fsync enabled this time as well. I am now setting everything back up. Thanks a lot for the help.
Jeff
Click to expand...
Click to collapse
For completeness sake I would like to add a couple other things that I did differently from my previous attempts. I don't know if they made a difference or not.
1. Reformatted the microSD card to FAT32 instead of exFAT
2. Redownloaded all images and verified their MD5 sum after copying them to the SD card/
Again, not sure if it made a difference but I am up and running now.
Thanks again
Jeff
Hello First post here so hopefully in the right place! I've got a nexus 5, UK model purchased around January time. I had rooted, running stock with SuperSU installed and a few apps installed with xposed mod.
It was running perfectly fine, until a few days back where I was required to reboot, it then got stuck at the Google screen and wouldn't go past that, I turned the phone off for a while and eventually could get into it.. Great, until it happened again.. I spoke to a friend who said perhaps it was the xposed which was causing it, so I flashed back to factory, ran it for a while and it was fine, so went back to root and tested it, was stable so I reinstalled xposed.. It then got stuck in the bootloop again, so flashed to factory certain that it was xposed causing issues. I'm now running factory, however the phone will still get stuck in bootloop but will also randomly reboot itself now.. Has anyone experienced this? After scanning the forums I can't find anything so hopefully someone can help!! My boot loader is still unlocked.
Thank you, Jordan.
arsenaljordan said:
Hello First post here so hopefully in the right place! I've got a nexus 5, UK model purchased around January time. I had rooted, running stock with SuperSU installed and a few apps installed with xposed mod.
It was running perfectly fine, until a few days back where I was required to reboot, it then got stuck at the Google screen and wouldn't go past that, I turned the phone off for a while and eventually could get into it.. Great, until it happened again.. I spoke to a friend who said perhaps it was the xposed which was causing it, so I flashed back to factory, ran it for a while and it was fine, so went back to root and tested it, was stable so I reinstalled xposed.. It then got stuck in the bootloop again, so flashed to factory certain that it was xposed causing issues. I'm now running factory, however the phone will still get stuck in bootloop but will also randomly reboot itself now.. Has anyone experienced this? After scanning the forums I can't find anything so hopefully someone can help!! My boot loader is still unlocked.
Thank you, Jordan.
Click to expand...
Click to collapse
Are you able to flash a custom recovery? like TWRP, PHILZ, CWM? try it.
if successful, flash a custom Rom. just to discard the possibility of emmc failure.
GUGUITOMTG4 said:
Are you able to flash a custom recovery? like TWRP, PHILZ, CWM? try it.
if successful, flash a custom Rom. just to discard the possibility of emmc failure.
Click to expand...
Click to collapse
I am able to flash a custom recovery and so forth, so wouldn't think it to be emmc failure.
arsenaljordan said:
I am able to flash a custom recovery and so forth, so wouldn't think it to be emmc failure.
Click to expand...
Click to collapse
It doesn't really exonerates emmc from being bad yet. now, wipe and flash a Rom, a stock/aosp based one
GUGUITOMTG4 said:
It doesn't really exonerates emmc from being bad yet. now, wipe and flash a Rom, a stock/aosp based one
Click to expand...
Click to collapse
I have already flashed the stock recovery and ROM back to the device
Hello.
I've been experimenting with my TF700t now.
Tried to install CM11, and it got random reboots all the time. I needed Clockwork so i recovery (had twrp before). I finally managed to get past the setup (basically skip and next on all settings) but it was "ready" it still freezes and random reboots.
I'm not really sure what boot loader i have.
Maybe the one i have is to old?
I had CleanRom before i started playing around with it.
If i cant fix it the trash bin is very close, but if i can get it to work again it would be nice.
It haven't been much used since i got my Note3 phone.
Any suggestion for what i should try? Im open for everything.
rvenes said:
I'm not really sure what boot loader i have.
Maybe the one i have is to old?
Click to expand...
Click to collapse
Yes, that can be the reason.
_that said:
Yes, that can be the reason.
Click to expand...
Click to collapse
LOL
Yes, that and wrong recovery, no or insufficient wipes before flashing the new rom - lots of possibilities.
Before you fire into the trash send it to me! I could use a tablet to recklessly experiment on
rvenes said:
Hello.
I've been experimenting with my TF700t now.
Tried to install CM11, and it got random reboots all the time. I needed Clockwork so i recovery (had twrp before). I finally managed to get past the setup (basically skip and next on all settings) but it was "ready" it still freezes and random reboots.
I'm not really sure what boot loader i have.
Maybe the one i have is to old?
I had CleanRom before i started playing around with it.
If i cant fix it the trash bin is very close, but if i can get it to work again it would be nice.
It haven't been much used since i got my Note3 phone.
Any suggestion for what i should try? Im open for everything.
Click to expand...
Click to collapse
No trash! The TF700 is an awesome tablet.
I would start over. Go to the Zombi-X thread and install that rom, *after* making sure you've got the boot loader mentioned in the first posting in that thread. Then, install TWRP (the latest version rather than the 2.6 one mentoined in the thread -- I think it is up to 2.8.01 or so). Then install Zombi-X. If you have an external micro-sd card, go for the ROM2SD install as well. If not, no worries. You'll be so glad you did. But again, the Zombi-X thread will step you through the entire process. They've done a fantastic job. And your tablet will impress.
I haven't had time to look at it yet! So many other gadgets to use.
Will find time sometime this xmas.
If you were on CleanROM, you're bootloader is probably way too old.
Also you HAVE to do a clean install = wipe of cache, Dalvik and data before installing a new rom.