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
Related
So I might very well get crap for this since I know this has been brought up in numerous locations, however none of the answers seem to quite fit my direct problem and the information is so entirely scattered around the forums that it's a wee bit hard piecing it all together. I do apologize in advance if there is some post that details this already, it's rather late and I'm at my wits end.
So I decided to root the old Transformer today and toss on CWM to flash Revolver (yeah you guys see where this problem is headed). Upon loading up CWM and flashing the rom, I promptly rebooted, at which point it just hung on the title screen. After figiting with it a bit I got it to the point that it simply boot loops into CWM directly now (not sure if that would be what we call an improvement). Now, most solutions to this problem involve cold booting linux (this seems to work for most people) however for me it just hangs. NVflash (is that it?) doesn't seem to be an option since I'm one of the unlucky ones that it wont work for (b80 serial) and I'm not sure where to go from here.
Windows won't recognize it at any stage (CWM/hung at linux boot) however I can load it into APX mode and can successfully run Root Toolkit (though I'm not sure that will help me much).
Now I promise I have at least a wee bit of intelligence, I'm not asking for a complete walkthrough or anything but at the very least if there is an answer buried on the forums somewhere, could someone point me in the right direction?
First of all nvflash now work almost all model of TF101 even above B60. You check in general thread..
Sent from my awesome rooted Defy: 2.3.6 XDA premium
Thank you thank you!
Ysed wheelie and a stock rom file to get back to safety, used peri to get root and recovery back, tried to reflash revolver and BAM same problem lol. Guess I'll be giving another ROM a shot.
farsight73 said:
First of all nvflash now work almost all model of TF101 even above B60. You check in general thread..
Sent from my awesome rooted Defy: 2.3.6 XDA premium
Click to expand...
Click to collapse
dotpkmdot said:
Thank you thank you!
Ysed wheelie and a stock rom file to get back to safety, used peri to get root and recovery back, tried to reflash revolver and BAM same problem lol. Guess I'll be giving another ROM a shot.
Click to expand...
Click to collapse
What version of CWM are you using?
The rogue touch recovery that the PERI installs.
Are you completely wiping your TF before installing the ROM? You MUST wipe before installing anything in CWM generally.
dotpkmdot said:
The rogue touch recovery that the PERI installs.
Click to expand...
Click to collapse
Huh. Did you factory reset and wipe data/cache?
Without looking at the options, wiping data/factory reset option, wipe cache, wipe dalvic cache.
Afterwards installing Revolver and next the update.
Tried the whole process again without doing the update, results the same.
Try installing a different ROM and see if you get the same result, if you do I'd reflash everything except the SOS partition stock.
Will do, downloading Revolution now to try and give it a shot.
Thing O Doom said:
Try installing a different ROM and see if you get the same result, if you do I'd reflash everything except the SOS partition stock.
Click to expand...
Click to collapse
So, different rom, same results. After flashing and rebooting, I simply get stuck at the Eee Pad screen. Is there any where you can point me to so I can read up on what I would need to do to reflash everything? I'd rather not turn the tablet into a nifty paperweight.
Search for
'wheelie NvFlash'
You can use that to reflash everything, or if you can Cold-Boot into Android (Hold volume-down then press power and wait 30 seconds, still holding volume-down)
You can use dd if=/sdcard/blob of=/dev/block/mmcblk0p4 (Staging partition) to reflash a blob.
See blob tools for extracting partitions from stock blobs to reflash, it's probably EBT (bootloader) that is messed up.
Hi all.
I wanted to thank all of the devs and modders on this device forum for all your hard work and feedback.
I have the unlocked/software updated/rooted/deodexed system, now I am wondering if your custom kernels will be compatible with the
system update? I tried the AdrenalineInjector sans Fugo option, ummmm.....nope. Didn't like that at ALL lol.
Let's hear it for Nandroids.
I have, well, more than my share of Nandroids and working TWRP recovery, so I am confident to the point of reckless with experimental flashes/mods. I have just tweaked out my DeOdexed system with the power boot menu, and just finished customizing my launcher, homescreen, apps, etc.
That being said, I am doing yet one more Nandroid of this one and trying both aaarrrggghhhs kernel (I apologize for the misspell) and shabby's p's and q's kernel.
I will post an update of either "woohoo!!" or "nnnyohhhhhh..."
Keep the mods coming, I am ready to try them all!
drakeheart77
drakeheart77 said:
Hi all.
I wanted to thank all of the devs and modders on this device forum for all your hard work and feedback.
I have the unlocked/software updated/rooted/deodexed system, now I am wondering if your custom kernels will be compatible with the
system update? I tried the AdrenalineInjector sans Fugo option, ummmm.....nope. Didn't like that at ALL lol.
Let's hear it for Nandroids.
I have, well, more than my share of Nandroids and working TWRP recovery, so I am confident to the point of reckless with experimental flashes/mods. I have just tweaked out my DeOdexed system with the power boot menu, and just finished customizing my launcher, homescreen, apps, etc.
That being said, I am doing yet one more Nandroid of this one and trying both aaarrrggghhhs kernel (I apologize for the misspell) and shabby's p's and q's kernel.
I will post an update of either "woohoo!!" or "nnnyohhhhhh..."
Keep the mods coming, I am ready to try them all!
drakeheart77
Click to expand...
Click to collapse
You didn't like the adrenaline injector? I just flashed that and I really don't see any negative effects so far.
What didn't you like about it?
None that work completely. You can flash arrrghhh's kernel if you'd like. You can overclock up to 1.89 GHz and underclock down to 96 MHz ... but it will break your wifi until the kernel gets updated. I'm not sure how long that will take though. Other than that, everything else works perfectly fine on it. Other than that, I believe a few options are in the works, but nothing's been finaled yet.
It wasn't that I didn't like Adrenaline, it's that it wouldn't boot lol. I don't think I did a proper clean before installing, plus my question is since my system is already deodexed, would it do more harm than good?
As far as the kernel goes, I both am not put out yet slightly perturbed by the wifi issue. Whenever a custom ROM does come our way, kernel devs will have to be leery of that little bug...could delay a port to our system a bit. I don't really OC for any reason, but many users do and will want a working kernel. MY desire for a kernel is one that is ready for wifi tethering for root users....Net-something lol i forgot the term.
Sent from my XT897 using xda premium
Please don't post question threads in the Development sections as they have no place there and we have a Q&A section designed for all your questions.
Thanks
AvRS
drakeheart77 said:
As far as the kernel goes, I both am not put out yet slightly perturbed by the wifi issue. Whenever a custom ROM does come our way, kernel devs will have to be leery of that little bug...could delay a port to our system a bit. I don't really OC for any reason, but many users do and will want a working kernel. MY desire for a kernel is one that is ready for wifi tethering for root users....Net-something lol i forgot the term.
Click to expand...
Click to collapse
The only reason the wifi won't work on the update with the old kernels is because of the changes the update made. Any ports should have that issue resolved prior to release, and once stable depending on what gets updated I doubt we'll run into kernel/wifi issues although I cannot guarantee that. I know the current OTA made changes to the modem drivers which I'm sure is part of the reason the kernels are incompatable.
I know when I was running the OTA and broke my wifi and tried restoring the stock boot.img (with original oem kernel) it wouldn't even boot the updated system. They're almost like two completely different softwares with the same UI lol.
How do we get new updated stock boot and recovery images? I rely on restoring pre-update Nandroids for whatever flub I may have yet to pull off lol. Anything I can do to help.
Sent from my XT897 using xda premium
drakeheart77 said:
It wasn't that I didn't like Adrenaline, it's that it wouldn't boot lol. I don't think I did a proper clean before installing, plus my question is since my system is already deodexed, would it do more harm than good?
As far as the kernel goes, I both am not put out yet slightly perturbed by the wifi issue. Whenever a custom ROM does come our way, kernel devs will have to be leery of that little bug...could delay a port to our system a bit. I don't really OC for any reason, but many users do and will want a working kernel. MY desire for a kernel is one that is ready for wifi tethering for root users....Net-something lol i forgot the term.
Sent from my XT897 using xda premium
Click to expand...
Click to collapse
Did you replace the update binary?
Sorry for the laziness on my replies. All I did was cache/dalvik wipe and success.
However I do need some help, I am uploading to Dropbox my non-rooted system and boot images. How do I share the links to my DP URL?
Also, where do I locate the stock recovery? Wouldn't the recovery be the same, because it wasn't a total ROM/system revamp? if that is the case then shabby has posted links for stock system and boot.
Sent from my XT897 using xda premium
Oh btw the files are for the 77.1.80 system update and NO root, and completely bare and odexed.
Sent from my XT897 using xda premium
http://db.tt/7p2Gv4cl
System
http://db.tt/qzu66AyF
System md5
http://db.tt/T2N0vYne
Stock recovery
http://db.tt/gbnt0Ddg
Boot
http://db.tt/oz8QPkP8
Boot md5
Sorry they are not clickable links, just copy & paste until I figure out the process lol.
Hope these files help!!
Sent from my XT897 using xda premium
drakeheart77 said:
http://db.tt/7p2Gv4cl
System
http://db.tt/qzu66AyF
System md5
http://db.tt/T2N0vYne
Stock recovery
http://db.tt/gbnt0Ddg
Boot
http://db.tt/oz8QPkP8
Boot md5
Sorry they are not clickable links, just copy & paste until I figure out the process lol.
Hope these files help!!
Sent from my XT897 using xda premium
Click to expand...
Click to collapse
Seeing as its been a while since I have had to do anything manually (so spoiled these days!)
I know I can use fastboot to push the img for the recovery, but how do I go about getting the system/boot flashed over?
Thanks!
EDIT: TBQH, never had to deal with .win files...
Hammerfest said:
Seeing as its been a while since I have had to do anything manually (so spoiled these days!)
I know I can use fastboot to push the img for the recovery, but how do I go about getting the system/boot flashed over?
Thanks!
EDIT: TBQH, never had to deal with .win files...
Click to expand...
Click to collapse
You need the TWRP recovery installed. If you've never used it before, you'll need to make a backup in order to generate the correct folders necessary. The directory will be either on your memory card (/external1) or internal memory (/sdcard). The folder path will be TWRP/BACKUPS/**your**phone's**serial**number**/
Inside that folder, create a folder and name it "stock backup" or whatever you want to name it. Then put the *.win and the *.md5 files in there. Put the stock recover in whatever folder you have your adb installed.
Reboot to recovery.
Restore the boot and system partitions from this backup (will show as "stock backup" or whatever you named it)
Once the restore is complete, back out to the main menu ... go to reboot -> choose bootloader
Flash your stock recovery ( fastboot flash recovery **whatever you named your recovery file**.img )
I typically flash this twice one right after the other just in case
Reboot your system ( fastboot reboot )
From there you should be all set.
drakeheart77 said:
http://db.tt/7p2Gv4cl
System
http://db.tt/qzu66AyF
System md5
http://db.tt/T2N0vYne
Stock recovery
http://db.tt/gbnt0Ddg
Boot
http://db.tt/oz8QPkP8
Boot md5
Sorry they are not clickable links, just copy & paste until I figure out the process lol.
Hope these files help!!
Sent from my XT897 using xda premium
Click to expand...
Click to collapse
Thanks for the files Drake!
However, I must be missing something because I flashed that system file and when I go to about phone it shows 7.7.1Q 8/3/12 not 7.7.80.
I'm pretty sure I flashed it right because I lost root and got back a bunch of the stupid Sprint stuff that I had removed and got your spiffy boot logo. I'm thinking about doing the OTA update from this baseline with stock recovery and then reinstalling twrp and re-running root.
*edit*
And that just put me back to infinite reboots again. I'm going to delete the stupid update from cache again and cut my losses for now, I've been up 22 hours so perhaps a fresh look tomorrow will help.
Not sure about the update not being there...don't know if that is system-specific or not all I know is that I made that back-up after the update was installed. Please leave any other feedback thank u for the reply. I may try and post a new system file.!
Sent from my XT897 using xda premium
Were u looking at the Build # or SW Version in "settings/about phone"?
The only thing simple is the belief in simplicity.
Also u cannot install Any OTA updates with ANY custom recovery on this phone. Stock recovery is necessary that's why I posted the image.
The only thing simple is the belief in simplicity.
afidel said:
Thanks for the files Drake!
However, I must be missing something because I flashed that system file and when I go to about phone it shows 7.7.1Q 8/3/12 not 7.7.80.
I'm pretty sure I flashed it right because I lost root and got back a bunch of the stupid Sprint stuff that I had removed and got your spiffy boot logo. I'm thinking about doing the OTA update from this baseline with stock recovery and then reinstalling twrp and re-running root.
*edit*
And that just put me back to infinite reboots again. I'm going to delete the stupid update from cache again and cut my losses for now, I've been up 22 hours so perhaps a fresh look tomorrow will help.
Click to expand...
Click to collapse
I'm having/had the same exact results.
Just got the phone today, rooted it, installed CWM, then decided to do the update not realizing the issue that would cause. Of course it failed in CWM and then I got into a reboot loop.
Flashed TWRP, restored the files listed here, got me back to a bootable ROM. Then, downloaded the update, told it to apply, shuts down,...bam,...boot loop. :silly:
All I want to do is get back to a completely stock (unlocked bootloader is fine), so I can update to 7.7.80, then mod & tweak from there.
This phone is so dang frustrating after coming from an Epic which was pretty brainless to flash. This Photon is kicking my butt..
Finally got past it, not sure how...then I fubar'd it again by trying to do the 1% & toggle mods. Ugh...so frustrating..
Just putting this out there, may not be true for all phones, but with my Q I got a lot of boot loops restoring backups from my external sd card, the ones I restored from internal storage worked okay. Obviously it could be corruption with the backups/sd card as well. With the toggles make sure you flash the toggles for the updated systemui and framework files and not the stock system files if you have taken the ota update. In other words make sure you match the version of the mods to your current software version. I found this phone very frustrating from a modder's perspective at first, I have really come to love the qwerty and hardware over time... the Snap Dragon s4 is fast!
Sent from my XT897 using xda app-developers app
I have unlocked my TF700. I was able to root the stock rom with Kangaroot with no problem. I then tried to load a custom rom, and got stuck in boot loop. I was trying Stable CM10, then I went on to try 5 other nightlies in reverse (from current as of yesterday) order. All have the same problem. I have cleared Cache Partition and Davlik Cache multiple times. I can flash to the stock rom from ASUS site and get through boot with no problem. Each time I do that I need to re-flash CWM. I've since also tried Clean and LiquidSmooth. Nothing gets past boot animation. I've let all attempts sit there for at least 10-15 minutes just to be sure it wasn't just slow.
Any idea where to start in troubleshooting?
CWM Log shows:
Code:
ClockworkMod Recovery v6.0.2.7
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
init.svc.ueventd=running
init.svc.recovery=running
init.svc.mishelp=restarting
init.svc.adbd=running
service.adb.root=1
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
I:Can't format unknown volume: /external_sd
I:Can't partition non-vfat: datamedia
I tried without the microsd card in as well.
I'd make sure the latest 4.1 is installed.
Push TWRP thru ADB
Download A ROM zip to the external card
Boot to custom recovery
Then try installing a ROM from TWRP after backing up
Hope this might help you.
Thats OK said:
I'd make sure the latest 4.1 is installed.
Push TWRP thru ADB
Download A ROM zip to the external card
Boot to custom recovery
Then try installing a ROM from TWRP after backing up
Hope this might help you.
Click to expand...
Click to collapse
Well after trying CM10 Stable, 2 nightlies, Liquid Smooth, all through TWRP (which is way better than CWM in my book now), I was able to get past boot with CleanRom. Unfortunately it doesn't look like wifi works, nor bluetooth, or full screen resolution Maybe because the rom is meant for Nexus 10. Oddly it shows the liquidsmooth loader and options too.
[Edit] Wifi and bluetooth started working after another reboot. After that I was able to switch over to CM10 Nightly. Still no full resolution, but better than broken. Yay for TWRP.
You've installed Cleanrom for the Nexus 10 on your TF700? I'm surprised that it boots at all. Why don't you install the one for the Tf700?
I read this yesterday and felt dumb for not knowing what Kangaroot was. :S
@OP: you've taken an immense risk, and are darned lucky to get out of this with only a malfunctioning device and not a brick. Next time, read up a bit.
Sent from a comfortable chair from the outer ring of Purgatory. The red guy asked me to say 'hi'.
sbdags said:
You've installed Cleanrom for the Nexus 10 on your TF700? I'm surprised that it boots at all. Why don't you install the one for the Tf700?
Click to expand...
Click to collapse
I thought I was downloading the TF700 version. When it loaded, however, it said Nexus10. I've not been able to find one that is for the TF700 on Scott's site. I really like how it guides the user through install options, which more Roms had this. Helps us noobs.
ngMondo said:
I thought I was downloading the TF700 version. When it loaded, however, it said Nexus10. I've not been able to find one that is for the TF700 on Scott's site. I really like how it guides the user through install options, which more Roms had this. Helps us noobs.
Click to expand...
Click to collapse
OK, here is the correct Cleanrom for tf700 http://forum.xda-developers.com/showthread.php?t=2049274
MartyHulskemper said:
@OP: you've taken an immense risk, and are darned lucky to get out of this with only a malfunctioning device and not a brick. Next time, read up a bit.
Click to expand...
Click to collapse
So that I can avoid the risk later, what was it that I did wrong as you see? Or are you referring to the Nexus10 build of CleanRom? If so, its the only one I found, and the page I downloaded from said it was TF700.
Scott no longer makes or supports CleanROM for the TF700 (or Nexus 7 for that matter), I do He has removed it from his site.
I don't know how you did it but somehow you got confused and downloaded and flashed CleanROM for the Nexus 10.
You have now given me an idea, seeing as you guinea pigged it and it booted
SO an indirect thank you!!
Wow my friend,
You really did dodge a bullet there!
Looks like the Nexus drivers and framework must be close.
Interesting...
sbdags said:
Scott no longer makes or supports CleanROM for the TF700 (or Nexus 7 for that matter), I do He has removed it from his site.
I don't know how you did it but somehow you got confused and downloaded and flashed CleanROM for the Nexus 10.
You have now given me an idea, seeing as you guinea pigged it and it booted
SO an indirect thank you!!
Click to expand...
Click to collapse
So, oddly enough the "correct" version of CleanRom 3.2.2 doesn't boot, but the Nexus 10 one did. Tried wipe and everything right before and after, 3 times... no dice.
ngMondo said:
So, oddly enough the "correct" version of CleanRom 3.2.2 doesn't boot, but the Nexus 10 one did. Tried wipe and everything right before and after, 3 times... no dice.
Click to expand...
Click to collapse
Well I suspect you have also managed to flash the Google Nexus 10 bootloader or some part of a kernel. I have no idea how to help you, but what is certain is you currently can't use any roms designed for the TF700 .....
sbdags said:
Well I suspect you have also managed to flash the Google Nexus 10 bootloader or some part of a kernel. I have no idea how to help you, but what is certain is you currently can't use any roms designed for the TF700 .....
Click to expand...
Click to collapse
Well, I think I've redone bootloader and kernel multiple times by now. I was actually about to ask you if there was a specific kernel option I should choose in the CleanRom installer, but it looks like I'm up and running again. I tried the DeOdexed version about 4 times with no luck. The Odexed version worked the first time through. So far everything looks to be working (wifi, bluetooth, dock, sd, gapps, etc).
Buhohitr had mentioned in another thread that TWRP has an option to wipe the eMMC (internal card erase) without hurting the recovery partition.
Last resort however if the system is a mess.
If all is at least running a new version of CROMi I'd just sit tight.
I am kind of curious to see if you have any more problems with user incurred shutdown and reboots.
ngMondo said:
So that I can avoid the risk later, what was it that I did wrong as you see? Or are you referring to the Nexus10 build of CleanRom? If so, its the only one I found, and the page I downloaded from said it was TF700.
Click to expand...
Click to collapse
Yeah, I was referring to flashing the N10 build. You were lucky, my friend. The TF700 makes one expensive paperweight. My remark seems to have gotten your feathers ruffled a bit: I did not mean it that way. Sorry if I offended you in any way.
sbdags said:
You have now given me an idea, seeing as you guinea pigged it and it booted
SO an indirect thank you!!
Click to expand...
Click to collapse
Opportunism FTW!
Hey guys. Semi newb here. I unlocked my TF300t a while back on the first offical JB update from ASUS. I then followed all the steps to unlock it and use fastboot to install TWRP. This was months back. I have been steadily updating CleanROM Inheritance as the revisions are released.
This latest revision to 3.4.4 flash was easy....as always. I wiped all and installed. When the system came back up I noticed my wifi was broken. I couldnt get it to initialize. So I booted to recovey so I could wipe all and reflash again just in case. Well, TWRP asked me for a password. Ive never encrypted my tablet nor have I used passwrods in the past as I know they can cause issues with access or permissions. I can hit cancel and use twrp but it wont mount anything or allow me to do anything until I 'decrypt' it. Not sure where to go from here. I guess Id like to flash the new official 4.2 from asus but I need advice on how to do this using fastboot.
Any help or pointers are welcomed. I only used the fastboot once to install twrp so I dont completely remember how to use it or if I can use it to flash a full ROM to hopefully reset the tablet. Thanks for any help! Cause I am stumped...
EDIT:
So I tried to turn off the tablet and pressed VOL DN + PWR to get to recovery options and choose fastboot, it just boot loops back to the asus logo twice then goes back in to TWRP. I cant even get into the OS now like I could. I need to unlock TWRP. PLEASE HELP!
EDIT 2:
I just wanted to add that by no means am I putting any blame on the ROM. Its a badass ROM that I love. The issue I am having is most definitely due to the bootloader and TWRP I suspect. I just dont know what I can do in TWRP locked down the way it is to regain some control...or at least fastboot.
cubaniche1 said:
Hey guys. Semi newb here. I unlocked my TF300t a while back on the first offical JB update from ASUS. I then followed all the steps to unlock it and use fastboot to install TWRP. This was months back. I have been steadily updating CleanROM Inheritance as the revisions are released.
This latest revision to 3.4.4 flash was easy....as always. I wiped all and installed. When the system came back up I noticed my wifi was broken. I couldnt get it to initialize. So I booted to recovey so I could wipe all and reflash again just in case. Well, TWRP asked me for a password. Ive never encrypted my tablet nor have I used passwrods in the past as I know they can cause issues with access or permissions. I can hit cancel and use twrp but it wont mount anything or allow me to do anything until I 'decrypt' it. Not sure where to go from here. I guess Id like to flash the new official 4.2 from asus but I need advice on how to do this using fastboot.
Any help or pointers are welcomed. I only used the fastboot once to install twrp so I dont completely remember how to use it or if I can use it to flash a full ROM to hopefully reset the tablet. Thanks for any help! Cause I am stumped...
EDIT:
So I tried to turn off the tablet and pressed VOL DN + PWR to get to recovery options and choose fastboot, it just boot loops back to the asus logo twice then goes back in to TWRP. I cant even get into the OS now like I could. I need to unlock TWRP. PLEASE HELP!
EDIT 2:
I just wanted to add that by no means am I putting any blame on the ROM. Its a badass ROM that I love. The issue I am having is most definitely due to the bootloader and TWRP I suspect. I just dont know what I can do in TWRP locked down the way it is to regain some control...or at least fastboot.
Click to expand...
Click to collapse
It sounds like you flashed the 4.2 update, as that has a new bootloader which causes the behavior you describe. Did you update it to 4.2 before flashing? If so, then check the threads associated with rooting/recovery with 4.2. Basically, you need to install a patched TWRP 2.4.4.0.
jimpmc said:
It sounds like you flashed the 4.2 update, as that has a new bootloader which causes the behavior you describe. Did you update it to 4.2 before flashing? If so, then check the threads associated with rooting/recovery with 4.2. Basically, you need to install a patched TWRP 2.4.4.0.
Click to expand...
Click to collapse
Hey thanks for the reply! Actually, no I was not installing 4.2. I would like to install a newer version of twrp but I cant do anything in twrp because it says its encrypted. I did read that other thread but all the options given are not available to me. I cant get to fastboot.
BUT heres an update:
I got the PC to recognize my device as a Transformer. But I couldn't get the naked drivers nor the newer Asus drivers to work. So I modified the .ini file for both the MTP install and USB driver install to include the Hardware ID shown in windows under device manager properties for the device. Basically I modded the .ini so that it also looks for the device ID, then saved and had windows look at the folder I gain to install the driver and this time is installed. So now I am going to try to use a fastboot command....Ill update if this works. Otherwise I may need to try adb and Im a total newb at adb...
UPDATE:
Got the driver installed but 2 issues:
1: Device manager says Device Cannot Start
2: I cant get recovery menu to show. Tablet goes right into TWRP recovery after looping through the ASUS boot screen twice.
I am stumped. I don't want to give up but I think I may have to
UPDATE
Just an update for those who were following:
I can boot into APX but since I never loaded NVFLASH I was screwed. Nothing I did to try to force it into download mode worked. Bootloader must be screwed. In any case, I went on ebay and bought a TF300T mainboard that was pulled from a damaged screen unit. It was 80 bukcs and should be here soon. I figure 80 bucks is better that 180 from ASUS or drop another 300-400 on a new tablet. I wish there was a JIG for the tablet. I used it on a SG SII once.
cubaniche1 said:
Just an update for those who were following:
I can boot into APX but since I never loaded NVFLASH I was screwed. Nothing I did to try to force it into download mode worked. Bootloader must be screwed. In any case, I went on ebay and bought a TF300T mainboard that was pulled from a damaged screen unit. It was 80 bukcs and should be here soon. I figure 80 bucks is better that 180 from ASUS or drop another 300-400 on a new tablet. I wish there was a JIG for the tablet. I used it on a SG SII once.
Click to expand...
Click to collapse
300-400? buy nexus10 for strong cpu and gpu. and retina display. asus build quality very bad. And support only need money.
chanhny said:
300-400? buy nexus10 for strong cpu and gpu. and retina display. asus build quality very bad. And support only need money.
Click to expand...
Click to collapse
Nexus 10 has it's drawbacks too, I love my TF300T.
UPDATE:
Installed new mainboard and got her back up and running quickly. Already updated to 4.2.1. I like it. Well done ASUS!
chanhny said:
300-400? buy nexus10 for strong cpu and gpu. and retina display. asus build quality very bad. And support only need money.
Click to expand...
Click to collapse
Lol. I love my TF300T. Sure, i can buy a better tablet but I would also have to spend a lot more money. I've only got $299 invested in my 32gb tablet plus $49 in my dock. I'm a happy camper. My tablet , when connected to the dock, will last almost twice as long as the Nexus on one charge. I can also keep using the tablet while the dock is charging. I really never even need to put the tablet itself into the charger. You can't do that with the more expensive Nexus 10.
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD
This feature is one of the reasons I love this tab. I'm having the same problem as op. I can still get into my 4.2 is though but cannot get recovery to read anything. Maybe ill have to wait for a twrp update.
For now as long as the tab works I can deal with it. I would like to get it working the right way again though.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
klownin5643 said:
This feature is one of the reasons I love this tab. I'm having the same problem as op. I can still get into my 4.2 is though but cannot get recovery to read anything. Maybe ill have to wait for a twrp update.
For now as long as the tab works I can deal with it. I would like to get it working the right way again though.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
Have you added the patch yet? This will allow TWRP to pick up your sd card.
I tried flashing the patched one via fastboot but it did not seem to take. Its still encrypted. I'm thinking its not flashing properly. I'm not the only one having this issue. Hopefully I can just wait it out till a fix is found. I'm afriad of screwing it up to where its completely unuseable.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
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