Related
Hello guys, I've got a weird problem. I messed around with my Transformer a bit, rooted etc on 8.4.4.11. CWM isn't working, and I can't even boot into recovery. It just sits at the "Loading recovery kernel...". Anyway, its freezing at the eeePad screen on bootup and doesn't do anything (this has stopped me from reflashing a blob, or Asus OTA updating). I've tried reflashing stock and rooted images quite a few times, but it always does the same thing. Now, I can get around the freeze by going to the hard reset screen and declining, and it boots into Android.
Whats wrong? Bootloader? Has to be something in startup, but I cant figure it out.
Re-flash using NVFlash method, in dev section (and don't forget to put the NVFlash ROM version in the folder)
bud77 said:
Re-flash using NVFlash method, in dev section (and don't forget to put the NVFlash ROM version in the folder)
Click to expand...
Click to collapse
Nope, that actually made it worse. Anyway, each root that I tried to go through did the exact same thing. Now it doesnt show anything on boot.
Is there some way to completely return it to stock? Just flash an official firmware pack with nvflash and have everything back to the day it was shipped?
EDIT: Fixed it, I had the wrong type of ROM unpacked. Thanks Bud.
padd3r said:
Nope, that actually made it worse. Anyway, each root that I tried to go through did the exact same thing. Now it doesnt show anything on boot.
Is there some way to completely return it to stock? Just flash an official firmware pack with nvflash and have everything back to the day it was shipped?
Click to expand...
Click to collapse
How could it make it worse .... ?
What's the error you're getting while NVFlashing ?
For the stock, if you can't NVFlash a rom, you won't be able to flash stock too, as the process is identical
I recently purchased a Asus Transformer, and being the android nerd I am I immediately began my rooting. After I rooted it, I began to look up roms and such. I decided to put the revolution HD Tom on it. I booted into recovery, wiped data, wiped cache, wiped dalvic, and than processed to flash the rom it flashed and said rom installed successfully. I rebooted and now nothing. I understand the wait time for boot but its been over 30 mins. I almost possitive its off and bricked. I need help as I only know how to unbrick a moto device. :/
sent from a DROIDX using S.S. 2.2... the best rom for it...
after a little searching I found a program called nvflash, I'm guessing that this is sort of like rsd lite. Ill try it later.
sent from a DROIDX using S.S. 2.2... the best rom for it...
NVFlash is only going to work if you have SBK v1.
Did you check the MD5Sum of the ROM file before flashing?
Sbk v1, what's that? And sorry I'm a noob with this transformer.
sent from a DROIDX using S.S. 2.2... the best rom for it...
It is the Secure Boot Kit of the device.
Look at your TF serial number: if you have B7O, B8O, B9O it should have the new version of SBK (v2). If it's the case, you CAN'T use NVFlash method to unbrick at the moment.
Look at this link to be able to check the SBK version of your TF:
http://forum.xda-developers.com/showthread.php?t=1290503
atothis said:
It is the Secure Boot Kit of the device.
Look at your TF serial number: if you have B7O, B8O, B9O it should have the new version of SBK (v2). If it's the case, you CAN'T use NVFlash method to unbrick at the moment.
Look at this link to be able to check the SBK version of your TF:
http://forum.xda-developers.com/showthread.php?t=1290503
Click to expand...
Click to collapse
Well if I can't turn on the device and I cant tell if its off than how can I get it into the mode asked? If that makes sence.
sent from a DROIDX using S.S. 2.2... the best rom for it...
Have you tried to force turn-off?
If not so, press and hold the power button for 10-20 seconds.
Then try to enter CWM recovery (or to boot normally).
Have you also tried to put it to charge? (Just to see if something happens).
EDIT: Did you eventually checked the serial # (On the box or on the back bottom part of the TF) ? If you have a B6O or lower, you can quite surely use NVFlash.
Tf101 is on the bottom as soon as I leave bdubs ill check to see if I can force it off and than enter recovery.
sent from a DROIDX using S.S. 2.2... the best rom for it...
atothis said:
Have you tried to force turn-off?
If not so, press and hold the power button for 10-20 seconds.
Then try to enter CWM recovery (or to boot normally).
Have you also tried to put it to charge? (Just to see if something happens).
EDIT: Did you eventually checked the serial # (On the box or on the back bottom part of the TF) ? If you have a B6O or lower, you can quite surely use NVFlash.
Click to expand...
Click to collapse
I'm guessing it will say B6O at the end of the serial. O and also what must I do in order to use nvflash, what preparation needs to be done?
sent from a DROIDX using S.S. 2.2... the best rom for it...
At the bottom of your transformer is a sticker if it says b60 you can use nvflash
If you have checked that then just look in the dev thread and you will find all you need about nvflash
Sent from my tf101 using xda premium 1.54Ghz
I tryed to hard reset it, didn't work. :/ I also checked and I have a tf101, B6O. How do I use the nvflash tool?
sent from a DROIDX using S.S. 2.2... the best rom for it...
HaXERxPaYLaY said:
I'm guessing it will say B6O at the end of the serial. O and also what must I do in order to use nvflash, what preparation needs to be done?
sent from a DROIDX using S.S. 2.2... the best rom for it...
Click to expand...
Click to collapse
Actually you need to read the FIRST three letters of the serial.
If it is a B6O, you're lucky
I have a B7O SBKv2, so I didn't used NVFlash, but you can find clear instructions here:
http://forum.xda-developers.com/showthread.php?t=1123429
Here's the general REF thread (MANY useful info, it's a sticky thread in dev section): http://forum.xda-developers.com/showthread.php?t=1044424
Ill try this all tonight and ill let you know what happens. I'm kinda nervous cause I really don't want to have high dollar brick.
sent from a DROIDX using S.S. 2.2... the best rom for it...
I got it to work im posting from it now! Thank you guys!
I have this problem and resolved with super wipe full script ( find in first post of revolution hd rom )
For use it, just download, put in sd card, run it on recovry ( install zip ... )
After wipe, I install revolver rom
Sent from my Transformer TF101
HaXERxPaYLaY said:
I got it to work im posting from it now! Thank you guys!
Click to expand...
Click to collapse
how did you get it working?
Hi everyone,
I have tried to read most of the 92 pages and still have not solved my problem.
The situation is as follows:
- I had a perfectly fine Asus Transformer B40 running Revolver 3.11 ROM with CPU OCed @ 1.6 Panda.test. While I was browsing the web the TF shut off and since then I cannot turn it on properly (boot into the OS).
- after failed attempts to reflash I wanted to get back to stock + unroot.
- I followed the steps from the first post here, I have a US version B40. I downloaded the US latest firmware from the first post and then ran the .bat file. Everything went fine and it restarted.
- then I did just this: hold vol- and power until you get the option to erase your data.... Select the option to wipe data.
Now the problem is more or less the same: I boot up the device, it shows the ASUS logo with the spinning wheel and then it turns off or reboots continuously. Sometimes it gets after the logo to the Select Language or Country screen. Touchscreen works. But then it reboots again. Every time it does that there is also a small hardware click sound.
I have also tried to manually reflash with firmware from Asus website but I still get the Android robot with an exclamation mark inside.
I just got this for Christmas, hope you can help me somehow as I don't know what to do...
Thanks a lot!
Just walked a friend through the downgrade on his B70 over the phone, he is rooted and running PRIME 2.1.1 in less than an hour.
First, get the WW_epad-user(blah blah) 8.6.6.19.zip update (downgrade/update, available in the dev section stickies), be sure it is the 8.6.6.19, not 8.6.5.19. Place the file on your SD card in the root, also make a copy and rename it
EP101_SDUPDATE.zip
(make sure your SD card is FAT32 formatted too, this has caused problems for some I have read). If these files are placed in the root of your external SD card then when booting into recovery mode it *should* find one of these two files and ask to install the 'update'. Once updated, install razorclaw and recoveryinstaller, grab the updated CWM installer with the 8.6.6.21 patch on it, available in the dev section, and then flash your new ROM over this patch (apparently you can't flash the patch over anything but a stock ROM, so if you already have a flashed ROM you need to flash back to stock ROM, search around instructions and files are available on xda).
If when you boot into recovery (vol - and pwr, vol+ on prompt) it doesn't tell you it is installing, give it some time, others have reported that the android/yellow triangle screen is actually good to see and will install updates on this screen even though it isn't notifying you (can't confirm from first hand, but what I have read on this site from other users), if it doesn't though, try rebooting normally, other users have said the update installs from notification bar in stock android OS (this confuses me too..). If recovery mode nor rebooting installs the downgrade, double check that you have the correct files, named correctly..try on another SD card, reformat to FAT32, etc. from what I understand even though it's different for some users there is some good success flashing back to the 8.6.6.19 build from the .21. Good luck, tell us if you fix it and how!
superwipe..
Before you flash revolution, you were supposed to flash superwipe then the rom, if you havent already go do so.
I've found a number of help of how to make the nvFlash files to make my Infinity unbrickable. But I cannot seem to find any concise instructions on what to do with the 8 files I end up with. I've saved them all over my system. But I do know how to use them. Could someone point me in the right direction?
I was unlocked, rooted, ICS, using TWRP 2.3.1. I can get into recovery, and I can get into Fastboot.
My tablet is stuck at the logo with the spinning icon, and shutting it down only starts up again. The tablet is also getting a little warm. The only way to fully shut it off is to use TWRP to power off.
Thanks, in advance. I'm panic-ing. :crying:
Reggie777 said:
I've found a number of help of how to make the nvFlash files to make my Infinity unbrickable. But I cannot seem to find any concise instructions on what to do with the 8 files I end up with. I've saved them all over my system. But I do know how to use them. Could someone point me in the right direction?
I was unlocked, rooted, ICS, using TWRP 2.3.1. I can get into recovery, and I can get into Fastboot.
My tablet is stuck at the logo with the spinning icon, and shutting it down only starts up again. The tablet is also getting a little warm. The only way to fully shut it off is to use TWRP to power off.
Thanks, in advance. I'm panic-ing. :crying:
Click to expand...
Click to collapse
You don't need NvFlash to recover from that, just flash an official Ics or JB rom from recovery. Also try a factory reset from recovery, but i guess it won't work, maybe you tried to install something that is messing with you sytem files or some mod (dpi change, beats audio, chainfire,,etc) ?
Pretoriano80 said:
You don't need NvFlash to recover from that, just flash an official Ics or JB rom from recovery. Also try a factory reset from recovery, but i guess it won't work, maybe you tried to install something that is messing with you sytem files or some mod (dpi change, beats audio, chainfire,,etc) ?
Click to expand...
Click to collapse
Thanks for the reply. I'm just overjoyed you didn't say it was hopeless. :highfive:
Sorry to be such a noob, but how do I flash an official ICS or JB rom from recovery? I was on ICS and wouldn't mind going up to JB. But when I went to the Asus site to download the update, I could not find my SKU [?] among them. I think mine is ILM. So where could I find an official JB rom without the SKU limitation? Also, when you say a "factory reset", I am assuming you mean a clean wipe? I hadn't tried that.
Reggie777 said:
Thanks for the reply. I'm just overjoyed you didn't say it was hopeless. :highfive:
Sorry to be such a noob, but how do I flash an official ICS or JB rom from recovery? I was on ICS and wouldn't mind going up to JB. But when I went to the Asus site to download the update, I could not find my SKU [?] among them. I think mine is ILM. So where could I find an official JB rom without the SKU limitation? Also, when you say a "factory reset", I am assuming you mean a clean wipe? I hadn't tried that.
Click to expand...
Click to collapse
All Asus software download located here:
http://forum.xda-developers.com/showthread.php?t=1734005
All instruction how to do things here:
http://forum.xda-developers.com/showthread.php?t=1834521
Is there such thing as a guide like this one but that is up to date and with working links? I want to flash a new ROM onto my phone, but the guides I've found here and elsewhere have broken links, or use language that I don't understand, or skip vital steps. I've been working on this for four hours straight and I haven't gotten a single guide to work, or get stuck, or something else that's really dumb. For someone who has worked on computers for the last 17 years this is extremely frustrating. I'm very new to the android modding scene and apparently it's not just a community, but an entirely different culture and I'm feeling a bit shocked and confused. I have like 30 tabs open with guides, info, different ROMs, different ways to do it, etc and the more I learn the less I understand how to do this :/ I just want to get my phone working with a ROM that's very similar to stock Sense but without the crappy bloatware and memory issues. Miktouch is the one I thought I wanted, but apparently hasn't been updated in almost a year, and bulletproof/doubleshot is confusing. I can't even figure out how to root and get S-Of... Gah!
Please help.
This guide is confusing and skips steps or lacks real explanations.
Thank you.
First thing you want to do is root your phone, this is done by unlocking you bootloader through the HTC dev website. There is a tutorial that is stickyed in the developer section called something like root from any bootloader. I suggest to read that a bit.
Once you followed those steps and unlocked your bootloader you can decide if you want to remove all security flags (highly recommend this, but some find it difficult) in the same guide it explains what radio s-off is and links you to the jbear site to do the wire trick (needs Linux) (or find weekendstoshort for a way to do it in windows)
Feel free to ask more questions but all answers should be found in these xda threads and jbear site, no need to Google anything for this
Sent from my Nexus 4 using xda premium
I hope so...I'll give it another go tomorrow. I'm still quite frustrated at it. I wish I knew someone who had done it and could show me in person.
GiftigDegen said:
I hope so...I'll give it another go tomorrow. I'm still quite frustrated at it. I wish I knew someone who had done it and could show me in person.
Click to expand...
Click to collapse
MikTouch is optimized stock... So updating it farther would take it a direction we wasn't going with it.
Bulletproof is even older. We don't have much here... But what's here is solid
Sent from my Nexus 4 using Tapatalk 4 Beta
First timer here as well (although long time computer user/programming familiar so I might have a better understanding of some things than you) and I was able to fully unlock, S-OFF, and load up a JB rom to my phone using the guide right on this site (http://forum.xda-developers.com/showthread.php?t=1801106) and some help from some online friends that have done this kind of thing before. I found all links to be working, and pretty much all steps to be covered. The I guess hardest part was the permanent S-OFF using the wire trick. I had to burn an Ubuntu live cd and boot a laptop with it, but I was even able to get that step done. A little frustrating with the timing, I think it took me about 8 tries until it finally unlocked. The only thing I think I initially missed was wiping all 3 caches, so I did a dirty flash that got stuck on the boot screen. After I wiped and loaded again, no problems. If you'd like any additional help, I get pretty bored at work, so find me on aim or gchat, or just shoot me a PM here, I think I should get notified
Good luck, it's not as bad as I thought it would be
Also I haven't personally tried it, but feel free to peruse this thread as well: http://forum.xda-developers.com/showthread.php?t=1696373
Note you'll need to have already achieved HTCDev unlocked and be rooted to use this (covered in that first link)
Hope that helps!
PsychoPhreak said:
First timer here as well (although long time computer user/programming familiar so I might have a better understanding of some things than you) and I was able to fully unlock, S-OFF, and load up a JB rom to my phone using the guide right on this site (http://forum.xda-developers.com/showthread.php?t=1801106) and some help from some online friends that have done this kind of thing before. I found all links to be working, and pretty much all steps to be covered. The I guess hardest part was the permanent S-OFF using the wire trick. I had to burn an Ubuntu live cd and boot a laptop with it, but I was even able to get that step done. A little frustrating with the timing, I think it took me about 8 tries until it finally unlocked. The only thing I think I initially missed was wiping all 3 caches, so I did a dirty flash that got stuck on the boot screen. After I wiped and loaded again, no problems. If you'd like any additional help, I get pretty bored at work, so find me on aim or gchat, or just shoot me a PM here, I think I should get notified
Good luck, it's not as bad as I thought it would be
Also I haven't personally tried it, but feel free to peruse this thread as well: http://forum.xda-developers.com/showthread.php?t=1696373
Note you'll need to have already achieved HTCDev unlocked and be rooted to use this (covered in that first link)
Hope that helps!
Click to expand...
Click to collapse
I'm following the first guide you linked. So far it's working I just flashed CWmod on and I loaded it according to the instructions in the guide "After fastboot finishes, disconnect your MT4GS, go into bootloader, and go to “RECOVERY.” You should now be in ClockworkMod Recovery 5.0.2.7. The first thing I would do in CWM Recovery is make a backup of your stock ROM for safe keeping. "
But I forgot to d/c my phone. It still loaded CWmod and I navigated to backup/restore and clicked it. Right now my phone has the clockwork logo in the middle but it didn't give me any prompts after selecting backup/restore. What's it doing? It's been doing this for like 5 minutes. Should I be worried that I forgot to d/c the cable and whatnot?
Thanks
GiftigDegen said:
I'm following the first guide you linked. So far it's working I just flashed CWmod on and I loaded it according to the instructions in the guide "After fastboot finishes, disconnect your MT4GS, go into bootloader, and go to “RECOVERY.” You should now be in ClockworkMod Recovery 5.0.2.7. The first thing I would do in CWM Recovery is make a backup of your stock ROM for safe keeping. "
But I forgot to d/c my phone. It still loaded CWmod and I navigated to backup/restore and clicked it. Right now my phone has the clockwork logo in the middle but it didn't give me any prompts after selecting backup/restore. What's it doing? It's been doing this for like 5 minutes. Should I be worried that I forgot to d/c the cable and whatnot?
Thanks
Click to expand...
Click to collapse
I wouldn't worry, and I'm not entirely sure what it's trying to do, perhaps the possibility of USB storage is throwing it off. At this point I'd say just try to disconnect it, pull the battery, and start back up into recovery, but without the USB attached this time. I imagine then you'll be fine and able to backup the stock image like they say for safe keeping.
One more dummy question (tech support for many years, always check the simple stuff first...) you do have SOME SD card in there right?
PsychoPhreak said:
I wouldn't worry, and I'm not entirely sure what it's trying to do, perhaps the possibility of USB storage is throwing it off. At this point I'd say just try to disconnect it, pull the battery, and start back up into recovery, but without the USB attached this time. I imagine then you'll be fine and able to backup the stock image like they say for safe keeping.
One more dummy question (tech support for many years, always check the simple stuff first...) you do have SOME SD card in there right?
Click to expand...
Click to collapse
Yeah, 32gb =)
booted into recovery, clicked on bacup/restore...still just showing the logo in the middle.
(PS any mods out there listening, I'd love to have that 5 minute restriction removed =D )
Okay, so the select button changes from power to the scroll pad once in recovery...good to know.
GiftigDegen said:
booted into recovery, clicked on bacup/restore...still just showing the logo in the middle.
(PS any mods out there listening, I'd love to have that 5 minute restriction removed =D )
Okay, so the select button changes from power to the scroll pad once in recovery...good to know.
Click to expand...
Click to collapse
NVMD....You got it now.
strapped365 said:
MikTouch is optimized stock... So updating it farther would take it a direction we wasn't going with it.
Bulletproof is even older. We don't have much here... But what's here is solid
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Using CWM to flash Miktouch now. Hopefully it works... =D
Just remember, if you are "S-On" you're going to need to fastboot flash boot boot.img after your ROM is thru flashing or you will hang up at the boot animation.
strapped365 said:
MikTouch is optimized stock... So updating it farther would take it a direction we wasn't going with it.
Bulletproof is even older. We don't have much here... But what's here is solid
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
K. First impressions:
When I restart the phone, the first thing it does is force stop Gmail and Youtube several times. Is this supposed to happen?
Also, I'm extremely impressed with the speed of the restart. It's at LEAST twice as fast as stock.
And, Genius button doesn't work even after installing the patch linked to on your website (universal.zip).
WeekendsR2Short said:
Just remember, if you are "S-On" you're going to need to fastboot flash boot boot.img after your ROM is thru flashing or you will hang up at the boot animation.
Click to expand...
Click to collapse
Thanks Weekends. I did that and it's installed, though I fastboot flash boot boot.img before I used CWM to flash the rom. Does that make a difference? Do you think doing it that way will fix the force close mentioned above?
If there's not a fix for the gmail/youtube force closes, is it possible to do bulletproof with s-on? Thoughts? I really want to stick as close to stock MT4GS but with as solid a system as possible.
Flashing boot image before ROM will overwrite kernel
Wipe all
Flash ROM
Flash boot
Reboot
Sent from my Nexus 4 using xda premium
demkantor said:
Flashing boot image before ROM will overwrite kernel
Wipe all
Flash ROM
Flash boot
Reboot
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Another noob question. How do I wipe all?
Also, when I use CWM to install Mikrom it atuo restarts and loads up. Then do I restart again and go fastboot the new kernal?
Thank you all for how much help you have given me.
At the end of the updater-script there must be a reboot command, but being this ROM is based of stock you may not need to flash the kernel anyway.
Best methods for wiping is one of bluex's superwipe scripts or with fastboot
fastboot erase system -w
But being you are s-on that command may fail.
But always do a wipe data/factory reset, wipe cache, and wipe dalvik in recovery.
It also good practice to make a nandroid of current ROM before you flash anything
Sent from my Nexus 4 using xda premium
demkantor said:
At the end of the updater-script there must be a reboot command, but being this ROM is based of stock you may not need to flash the kernel anyway.
Best methods for wiping is one of bluex's superwipe scripts or with fastboot
fastboot erase system -w
But being you are s-on that command may fail.
But always do a wipe data/factory reset, wipe cache, and wipe dalvik in recovery.
It also good practice to make a nandroid of current ROM before you flash anything
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Mmkay, working doing this now.
Quick question, hopefully someone can give me a link, but I'd love the install the depaginated app drawer, genius fix and menu wake up mods for this, but the links are broken (dev-host times out). Any help?
See weekends mirror thread
Sent from my Nexus 4 using xda premium
Last night I ran that LagFree app or whatever it's called because my tablet is slow as hell (or maybe I'm just used to my GS4 being so fast). I have it unlocked with CROMI and I think one of the OCed kernels. Anyway, I woke up this morning and the app finished trimming whatever it needed to, so I rebooted it before I left for work. When I got home, I saw that the tablet was completely dead. I plugged it in and saw that it gets stuck at the Asus spinning logo, and it must have been cranking along all day and drained the battery.
I can get to the recovery portion and tried flashing one of the other kernels but still have the same problem. What happened all of a sudden and how should I go about fixing it? And how do I shut this stupid ass thing off? Every time I hold the power button in until it shuts off it just starts back up again.
I am by no means an expert on this, but it sounds like you may have corrupted a system file. I would first try to install a rom you have downloaded in recovery (if you dont want to do a factory reset) if that doesnt work or if you are okay with wiping apps (not internal data) go to the wipe menu in twrp and do a factory reset (do not do this from the bootloader). I think there might be a shut off button in the reboot menu in twrp
berfles said:
Last night I ran that LagFree app or whatever it's called because my tablet is slow as hell (or maybe I'm just used to my GS4 being so fast). I have it unlocked with CROMI and I think one of the OCed kernels. Anyway, I woke up this morning and the app finished trimming whatever it needed to, so I rebooted it before I left for work. When I got home, I saw that the tablet was completely dead. I plugged it in and saw that it gets stuck at the Asus spinning logo, and it must have been cranking along all day and drained the battery.
I can get to the recovery portion and tried flashing one of the other kernels but still have the same problem. What happened all of a sudden and how should I go about fixing it? And how do I shut this stupid ass thing off? Every time I hold the power button in until it shuts off it just starts back up again.
Click to expand...
Click to collapse
As long as you still can get back to your custom recovery, you are ok. Let try some quick fix to see if you can get it back and run again. Do you know what custom recovery that you are using, Cromi version, kernel version? More information is a lot easier for others to help you out.
LetMeKnow said:
As long as you still can get back to your custom recovery, you are ok. Let try some quick fix to see if you can get it back and run again. Do you know what custom recovery that you are using, Cromi version, kernel version? More information is a lot easier for others to help you out.
Click to expand...
Click to collapse
Throw in the bootloader version while you're at it. If you have a nandroid backup of your system, restore it and then troubleshoot from there.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
I'm using TWRP 2.3.3.0, I'll attach the list of kernels I have tried to install (I forget which I had at the time of running, one of the hundsbuah ones though), and I'm not sure which Cromi version I have, can I tell from recovery? It's an older version, I have a 3.2.1 folder on my computer so I think that's the version I'm running.
berfles said:
I'm using TWRP 2.3.3.0, I'll attach the list of kernels I have tried to install (I forget which I had at the time of running, one of the hundsbuah ones though), and I'm not sure which Cromi version I have, can I tell from recovery? It's an older version, I have a 3.2.1 folder on my computer so I think that's the version I'm running.
Click to expand...
Click to collapse
Wow, that's really old! No wonder you have lag...
You can find the build number and the Kernel you're running under Settings > About Tablet.
My advice would be that you upgrade to CROMi-X, the JB 4.2 based successor of CROMI.
Look for the thread in the development section.
First you would have to flash the 10.6.1.14.8 bbotloader/TWRP 2.5 package from the OP of that thread, boot back into your old rom once, then boot back into TWRP, do a factory reset (highly recommended when you move from a 4.1. rom to 4.2. Back up your apps though, they will get wiped) and then flash CROMi-X.
It's currently on version 4.6.9 but sbdags will release 4.7 pretty soon. And his roms have gotten better from version to version - you won't believe the difference!
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
berndblb said:
Wow, that's really old! No wonder you have lag...
You can find the build number and the Kernel you're running under Settings > About Tablet.
My advice would be that you upgrade to CROMi-X, the JB 4.2 based successor of CROMI.
Look for the thread in the development section.
First you would have to flash the 10.6.1.14.8 bbotloader/TWRP 2.5 package from the OP of that thread, boot back into your old rom once, then boot back into TWRP, do a factory reset (highly recommended when you move from a 4.1. rom to 4.2. Back up your apps though, they will get wiped) and then flash CROMi-X.
It's currently on version 4.6.9 but sbdags will release 4.7 pretty soon. And his roms have gotten better from version to version - you won't believe the difference!
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Click to expand...
Click to collapse
I can't get it to boot to check the About Tablet section.
My latest nandroid is from April, I'd prefer not to lose all that data if there's anything at all I can do to keep it. I'm assuming just flashing the bootloader and new TWRP won't magically let me boot all of a sudden?
berfles said:
I'm using TWRP 2.3.3.0, I'll attach the list of kernels I have tried to install (I forget which I had at the time of running, one of the hundsbuah ones though), and I'm not sure which Cromi version I have, can I tell from recovery? It's an older version, I have a 3.2.1 folder on my computer so I think that's the version I'm running.
Click to expand...
Click to collapse
Hi there,
You have to be really careful about your situation. You have an old version of custom recovery, TWRP. WHATEVER YOU DO, PLEASE REMEMBER NOT TO INSTALL A NEW ROM VERSION. IT WILL HARDBRICK YOUR DEVICE. IT IS A KNOWN ISSUE. It would be best to wait for an expert to give you a better advise. At a moment, you can try to wipe both caches from your twrp to see if it would work. If you don't have anything important, you can try to restore from your backup. You can try to restore system back up file only to prevent data loss or you can move all your important files to your external SD before restore system, recovery, and data. If none of the above works, please wait patiently for an expert advise. DO NOT INSTALL A NEW ROM VERSION. Good luck.
Sounds like I have quite the fun times ahead of me then...
I'm guessing I can move files around with the file manager in TWRP, I think the only things I'd miss would be my pictures and videos. Don't care much about apps really, I can download them again and set them up.
LetMeKnow said:
Hi there,
You have to be really careful about your situation. You have an old version of custom recovery, TWRP. WHATEVER YOU DO, PLEASE REMEMBER NOT TO INSTALL A NEW ROM VERSION. IT WILL HARDBRICK YOUR DEVICE. IT IS A KNOWN ISSUE. It would be best to wait for an expert to give you a better advise. At a moment, you can try to wipe both caches from your twrp to see if it would work. If you don't have anything important, you can try to restore from your backup. You can try to restore system back up file only to prevent data loss or you can move all your important files to your external SD before restore system, recovery, and data. If none of the above works, please wait patiently for an expert advise. DO NOT INSTALL A NEW ROM VERSION. Good luck.
Click to expand...
Click to collapse
You do have to install the new bootloader and TWRP 2.5 before you intall a JB 4.2 rom. But that was exactly my advice!
If he/she flashes the bootlaoder/TWRP package from sbdags CROMi-X thread he/she will have a compatible bootloader/recovery combination installed. The 10.6.1.14.8 bootloader runs JB 4.1 based roms without a problem. This was tested and confirmed by _that. It doesn't get more expert than that IMO.
If you're 3.2.x rom is not corrupted it should boot once you have the new bootloader and recovery installed.
If you do a factory reset in TWRP it will delete user installed apps and it's data (to some extent), but not your personal data (files, pictures, movies etc).
Edit: As you unfortunately experience right now: Data not backed up is data not yet lost....
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
---------- Post added at 10:09 PM ---------- Previous post was at 09:56 PM ----------
berfles said:
Sounds like I have quite the fun times ahead of me then...
I'm guessing I can move files around with the file manager in TWRP, I think the only things I'd miss would be my pictures and videos. Don't care much about apps really, I can download them again and set them up.
Click to expand...
Click to collapse
As long as you have a working recovery you are in good shape.
TWRP 2.5 wipes the /data partition when doing a factory reset EXCEPT for the /data/media folder where your personal stuff is stored.
But since I am not sure on the file structure on a JB 4.1 system (it's been a while..), it's a VERY good idea to move your stuff to an external SD card in TWRP before you wipe.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
@berndblb, While I tried to reply to this post, you replied at the same time as I did. However, you were one step ahead of me without seeing your post. If I offended you somehow, I have to say sorry. I just want to make sure that he/she to wait for someone likes you to give him/her a good advise. I hoped that this will clear up the confusing. :good:
LetMeKnow said:
@berndblb, While I tried to reply to this post, you replied at the same time as I did. However, you were one step ahead of me without seeing your post. If I offended you somehow, I have to say sorry. I just want to make sure that he/she to wait for someone likes you to give him/her a good advise. I hoped that this will clear up the confusing. :good:
Click to expand...
Click to collapse
No problem, bud! No offense whatsoever taken!
Misunderstandings happen when cross-posting :sly:
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
If you can adb your last_kmsg or find it in your /proc and post it up, experts can identify your problem a lot easier and be able to help you a lot quicker.
LetMeKnow said:
Hi there,
You have to be really careful about your situation. You have an old version of custom recovery, TWRP. WHATEVER YOU DO, PLEASE REMEMBER NOT TO INSTALL A NEW ROM VERSION. IT WILL HARDBRICK YOUR DEVICE. IT IS A KNOWN ISSUE.
Click to expand...
Click to collapse
Installing a new ROM with an old recovery is not known to hardbrick your device. Choosing "Wipe data" from the bootloader with an old recovery does, as does any action that forces booting to recovery if the recovery doesn't work. I know that TWRP 2.4.1 and newer are compatible with the 10.6 bootloaders - 2.3.3 may be incompatible.
LetMeKnow said:
If you can adb your last_kmsg or find it in your /proc and post it up, experts can identify your problem a lot easier and be able to help you a lot quicker.
Click to expand...
Click to collapse
/proc/last_kmsg is only useful to diagnose kernel crashes (unexpected reboots). To diagnose a hanging boot, we need a logcat from the boot process.
I tried moving a file over to my SD card last night and it sat there saying Copying for about 35 minutes. The file wasn't even that big.
So a factory reset would leave me images and whatnot? I have to think about what else I would end up losing if I went that route, make sure there aren't things sitting in places that will be wiped.
Is it possible to do this "logcat" with my tablet in this condition?
berfles said:
I tried moving a file over to my SD card last night and it sat there saying Copying for about 35 minutes. The file wasn't even that big.
So a factory reset would leave me images and whatnot? I have to think about what else I would end up losing if I went that route, make sure there aren't things sitting in places that will be wiped.
Is it possible to do this "logcat" with my tablet in this condition?
Click to expand...
Click to collapse
Yes you can do a logcat. I would imagine it will report lots of errors with files or the file system
http://forum.xda-developers.com/showthread.php?t=1726238
Well I can see all sorts of stuff scrolling in the logcat but I can't get it to write to a file in ADB for some reason. I'll keep trying.
The main thing I'm seeing is a ton of stuff like this:
D/dalvikvm( 871): GC_CONCURRENT freed 472K, 6% free 10224K/10823K, paused 1ms+6ms
berfles said:
Well I can see all sorts of stuff scrolling in the logcat but I can't get it to write to a file in ADB for some reason. I'll keep trying.
The main thing I'm seeing is a ton of stuff like this:
D/dalvikvm( 871): GC_CONCURRENT freed 472K, 6% free 10224K/10823K, paused 1ms+6ms
Click to expand...
Click to collapse
Did you try "adb logcat -v long > log.txt"
Without the quotation marks of course.
To end the logcat Ctrl + C
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
I did, all I got in my output file was this:
C:\TF700T-ADB-Tool>TITLE Colored Logcat
C:\TF700T-ADB-Tool>mode con:cols=180 lines=50
C:\TF700T-ADB-Tool>call python coloredlogcat.py
125 DEBUG I
Terminate batch job (Y/N)?
In logcat look for F/ which are fatal errors and E/ errors