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!
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 guys. Loving the forums - I've been a watcher for a while, but have only just joined.
I'm having trouble installing most ROMs. They all hang at the opening screen, or continually reboot depending on which one it is. I've tried flashing boot.img with no success. I've had luck with Stuart's ROM, but was really hoping to find a stable ROM with Jelly Bean.
I've read through the noob guides and FAQs, done a heap of searches but can't find the answer, yet I'm sure I'm not the first with this issue. It looks like this guy was having the same problems, but he posted in the wrong area and I can't find a follow up...
I've rooted and unlocked all ok, can access bootloader and TWRP without any issues.
Does anyone know what I could be doing wrong? Or know where this has been answered before? Thanks a mil.
http://forum.xda-developers.com/showthread.php?p=33303798
This is in the q&a stickies. See if this helps.
Sent from my One X using xda premium
itscoby said:
Hi guys. Loving the forums - I've been a watcher for a while, but have only just joined.
I'm having trouble installing most ROMs. They all hang at the opening screen, or continually reboot depending on which one it is. I've tried flashing boot.img with no success. I've had luck with Stuart's ROM, but was really hoping to find a stable ROM with Jelly Bean.
I've read through the noob guides and FAQs, done a heap of searches but can't find the answer, yet I'm sure I'm not the first with this issue. It looks like this guy was having the same problems, but he posted in the wrong area and I can't find a follow up...
I've rooted and unlocked all ok, can access bootloader and TWRP without any issues.
Does anyone know what I could be doing wrong? Or know where this has been answered before? Thanks a mil.
Click to expand...
Click to collapse
Give the members here more details. What exactly interests you in JB ROMS? What have you been trying to flash? What are you on right now?
If you wish to have a great Rom with no nonsense I'd suggest to you ViperXL. It's foolproof. I too asked questions after tons of research and tutorials. Asking questions is better than banging your head. And of course stick to this this forum for ROMS and you'll avoid a cool looking paperweight.
Jon
Sent from my HTC One XL using xda premium
subarudroid said:
http://forum.xda-developers.com/showthread.php?p=33303798
This is in the q&a stickies. See if this helps.
Click to expand...
Click to collapse
Thanks! I'd read through this one and had tried flashing the boot.img as it suggests for those experiencing my problem. Unfortunately it made no difference. It's a helpful guide though - unfortunately it came after I'd worked it all out for myself from other forums and posts!
ToxicWaste said:
What exactly interests you in JB ROMS? What have you been trying to flash? What are you on right now?
Click to expand...
Click to collapse
Thanks Jon. I'm after Jelly Bean primarily to check out Google Now. I head up digital customer experience for a big Aussie company and am interested to see how it might help our customers (READ: Really I want to know how it can help me!)
I was on a rooted stock Telstra ROM but couldn't get the OTA JB update to work. I tried ViperXL 3.0.0, CyanogenMOD 10 and Tachi91's v2.1 MOD. ViperXL is what I want to run ideally.
Currently on Scott's CleanROM 5.1. I'm running One XL with Firmware 2.20.502.7.
By all means download Viper and flash that bad boy. Firmware 2.20 and Viper are good friends. No need to flash .img separately. While you're at it, check out some kernels in the Venom Hub.
You came to the right place for help though. Never think you can't ask a quesrion hers if you think research hasn't answered it for you.
I've been trying Google Now but it's not doing much for me. Still playing with it.
ATT HOX Premium App--Stock is fine but modded is Creative
ToxicWaste said:
By all means download Viper and flash that bad boy. Firmware 2.20 and Viper are good friends. No need to flash .img separately. While you're at it, check out some kernels in the Venom Hub.
You came to the right place for help though. Never think you can't ask a quesrion hers if you think research hasn't answered it for you.
I've been trying Google Now but it's not doing much for me. Still playing with it.
ATT HOX Premium App--Stock is fine but modded is Creative
Click to expand...
Click to collapse
regarding Viper, I just downloaded 2.4.0 and honestly don't know what to do next. Do I just move the file to the phone while it's plugged in? I rooted and unlocked last night, and installed twrp. I didn't want to start a thread about this and am having trouble finding the answer. Any help is a big thanks.
In Flames said:
regarding Viper, I just downloaded 2.4.0 and honestly don't know what to do next. Do I just move the file to the phone while it's plugged in? I rooted and unlocked last night, and installed twrp. I didn't want to start a thread about this and am having trouble finding the answer. Any help is a big thanks.
Click to expand...
Click to collapse
First and foremost, go into recovery (twrp) and make a backup. The backup is just that, a backup in case something goes wrong.
Now that you have a backup, plug your phone into you pc (assuming that's what you have) and select your phone to be mounted as storage.
Next, open your file location for your phone.
Next, locate Viper Rom.
Now, copy Viper (just drag and drop) it into your phones sd card.
Ok. Now you should copy your backup you made in twrp previously. Now you have it backed up in two locations.
Let's get started:
Boot into recovery (twrp).
Select Wipe and do the next 4 steps INSIDE twrp!
Now wipe dalvick cache.
Now wipe cache.
Now wipe system.
Now do a factory reset.
Now Select Install in twrp.
Find your Viper folder zip.
Select it.
Swipe to flash!
Follow Aroma Installer options to your liking.
Please be patient as it takes a while. Also, when it first boots it takes a while.
Any more questions, just ask us
ATT HOX Premium App--Stock is fine but modded is Creative
Thanks a lot. Installing now.:good:
In Flames said:
Thanks a lot. Installing now.:good:
Click to expand...
Click to collapse
No prob, man. Let us know how it went.
ATT HOX Premium App--Stock is fine but modded is Creative
Install was flawless, only bad thing is I have to work and can't toy with it for 8 more hours Thanks again!
In Flames said:
Install was flawless, only bad thing is I have to work and can't toy with it for 8 more hours Thanks again!
Click to expand...
Click to collapse
That sucks but it will be fun to learn about all the tweaks and such. I would go back to the Venom thread and flash the 2.4.0-->::2.4.1 update. I did the ota reset file too. Same thing you did before by wiping but you don't do or need a factory reset. Just flash those files in twrp. All up to date then.
ATT HOX Premium App--Stock is fine but modded is Creative
ToxicWaste said:
By all means download Viper and flash that bad boy. Firmware 2.20 and Viper are good friends. No need to flash .img separately. While you're at it, check out some kernels in the Venom Hub.
Click to expand...
Click to collapse
Hmm. Viper 3.0.0 really did not work and I followed the instructions closely. Perhaps I will try Viper 2.4.0 and then, if successful, look at updating my kernel, and then updating to 3.0.0? Current kernel is 3.0.8-01558-g7f75e5b Could this be causing me problems?
itscoby said:
Hmm. Viper 3.0.0 really did not work and I followed the instructions closely. Perhaps I will try Viper 2.4.0 and then, if successful, look at updating my kernel, and then updating to 3.0.0? Current kernel is 3.0.8-01558-g7f75e5b Could this be causing me problems?
Click to expand...
Click to collapse
Before you started to install Viper 3.0.0, what we're you on?
Sure, if let's say you had-Viper 2.4.0 but wishing to go to 3.0.0, THEN you need to flash the boot img separate since its a JB Rom.
The directions I provided are fool proof and the other user had success. So I'm wondering what you started out on before you loaded the Rom.
--------------------
Also, Viper and CleanRom are identical in the fact you DON'T need to extract the boot.img from the Rom zip as long as its under 3.0.0 (if flashing Viper). It's basically pointing twrp to the Viper zip and swiping to goodness.
ATT HOX Premium App--Stock is fine but modded is Creative
ToxicWaste said:
Before you started to install Viper 3.0.0, what we're you on?
Sure, if let's say you had-Viper 2.4.0 but wishing to go to 3.0.0, THEN you need to flash the boot img separate since its a JB Rom.
The directions I provided are fool proof and the other user had success. So I'm wondering what you started out on before you loaded the Rom.
Click to expand...
Click to collapse
So I've finally had success! Installed both 3.0.0 and 2.4.1 - I realised that I was much better off on 2.4.1 with all the venom tweaks than on 3.0.0 for seemingly not much more OS-wise, especially since I want to bypass my corporate exchange security policy, and Google Now was available as a mod.
Turns out I was trying to install on top of ROMs that wouldn't boot, and when I was trying to install from working ROMs, I wouldn't think to go back in to make sure debugging was on and fast boot was off.
The key things I've learned (which I initially missed in my initial scan of pages and pages of forum posts):
You need to install from a stable ROM that will let you boot into it
...because having a stable ROM will allow you to make sure the fast boot setting in the Power settings is off and USB debugging is on in Developer tools
You may need to flash boot.img if you're running bootloader 1.13 or above - even if the ROM installer instructs you not to
boot.img must be flashed before the installation, not after
They might sound obvious now, but this might hopefully help anyone else in my situation.
Thanks for all your help guys!
PS - LOVING Viper.
itscoby said:
So I've finally had success! Installed both 3.0.0 and 2.4.1 - I realised that I was much better off on 2.4.1 with all the venom tweaks than on 3.0.0 for seemingly not much more OS-wise, especially since I want to bypass my corporate exchange security policy, and Google Now was available as a mod.
Turns out I was trying to install on top of ROMs that wouldn't boot, and when I was trying to install from working ROMs, I wouldn't think to go back in to make sure debugging was on and fast boot was off.
The key things I've learned (which I initially missed in my initial scan of pages and pages of forum posts):
You need to install from a stable ROM that will let you boot into it
...because having a stable ROM will allow you to make sure the fast boot setting in the Power settings is off and USB debugging is on in Developer tools
You may need to flash boot.img if you're running bootloader 1.13 or above - even if the ROM installer instructs you not to
boot.img must be flashed before the installation, not after
They might sound obvious now, but this might hopefully help anyone else in my situation.
Thanks for all your help guys!
PS - LOVING Viper.
Click to expand...
Click to collapse
Good to hear you got it up and running. Viper was recommended to me and man once I played with it and tweaked it I'm having a hard time wanting to flash anything else. If I do its going to be 3.0.0. The tweaks and ElementalX kernel are just unreal.
P.S. Hitting the Thanks button is a good way to show your appreciation.
Sent from my HTC One XL 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
Hello everyone and happy new year
I unlocked my asus tf700 using asus unlocker...
Rooted fine, with super user
Installed clockwork mod recovery 6.0.4.4
Tablet stock is 4.1.1
The problem is that no matter which rom I install... when it finally boots up it goes to the setup screen no problems.
I enter timezone etc etc then rom loads then after a minute or so the system freezes for a few seconds then restarts..
I cleared cache , have done a factory reset, and tried different roms listed in the tf700t section of xda.
I rooted countless phones and tablets and never had this problem.
Any help would be greatly appreciated.
Thank you inadvanced!!!!
xxkhbxx said:
Hello everyone and happy new year
I unlocked my asus tf700 using asus unlocker...
Rooted fine, with super user
Installed clockwork mod recovery 6.0.4.4
Tablet stock is 4.1.1
The problem is that no matter which rom I install... when it finally boots up it goes to the setup screen no problems.
I enter timezone etc etc then rom loads then after a minute or so the system freezes for a few seconds then restarts..
I cleared cache , have done a factory reset, and tried different roms listed in the tf700t section of xda.
I rooted countless phones and tablets and never had this problem.
Any help would be greatly appreciated.
Thank you inadvanced!!!!
Click to expand...
Click to collapse
Check your bootloader. You have to be on 10.6.1.14.4 or higher for any of the current roms.
berndblb said:
Check your bootloader. You have to be on 10.6.1.14.4 or higher for any of the current roms.
Click to expand...
Click to collapse
Hmmm i didnt know that, i never had to mess around with that with any of the phones or tablets that ive done in the past.
When i load up android it boots up and says bootloader 10.4.4.5 i guess thats not the correct version. For some reason I'm drawing a blank on how to update the boot loader...
Lol
xxkhbxx said:
Hmmm i didnt know that, i never had to mess around with that with any of the phones or tablets that ive done in the past.
When i load up android it boots up and says bootloader 10.4.4.5 i guess thats not the correct version. For some reason I'm drawing a blank on how to update the boot loader...
Lol
Click to expand...
Click to collapse
You tried different roms from XDA and missed the section in the OP about warnings, requirements and instructions in each one of them???
It's usually the part in red with the huge letters, the part that says: READ ME
To get your bootloader to a current version you can flash the latest firmware from Asus. You would have to reinstall the custom recovery via fastboot afterwards of course.
Or you can download the bootloader/TWRP package in the OP for CROMi-X and flash that. Again: depending on which rom you want to flash, you may have to change to a different recovery afterwards.
berndblb said:
You tried different roms from XDA and missed the section in the OP about warnings, requirements and instructions in each one of them???
It's usually the part in red with the huge letters, the part that says: READ ME
To get your bootloader to a current version you can flash the latest firmware from Asus. You would have to reinstall the custom recovery via fastboot afterwards of course.
Or you can download the bootloader/TWRP package in the OP for CROMi-X and flash that. Again: depending on which rom you want to flash, you may have to change to a different recovery afterwards.
Click to expand...
Click to collapse
The funny part of it all is that I'm color blind lol.
Ok I updated to the correct bootloader and so far so good.
I was honestly surprised that I missed that part as well, but as I read it I thought to myself hmm but you knew that!! Lol
One quick question though, now when I boot into boot loader holding down the power and up there's only 3 icons instead of 4. The USB icon isn't there anymore.. Is that normal
Btw I'm on a cm 11 update.. Fingers crossed
Thank you again for your time
xxkhbxx said:
The funny part of it all is that I'm color blind lol.
Ok I updated to the correct bootloader and so far so good.
I was honestly surprised that I missed that part as well, but as I read it I thought to myself hmm but you knew that!! Lol
One quick question though, now when I boot into boot loader holding down the power and up there's only 3 icons instead of 4. The USB icon isn't there anymore.. Is that normal
Btw I'm on a cm 11 update.. Fingers crossed
Thank you again for your time
Click to expand...
Click to collapse
Good! Glad you worked it out. Maybe wearing green colored glasses while reading forums would help
ICS: 4 icons in bootloader, push Volume Up on flashing USB to get into fastboot
JB: 3 icons and you're in fastboot by default.
Or was that from JB 4.1 to 4.2? Can't remember... My problem is a serious case of CRS...
The glasses would come in handy here again: Read the script: "Starting fastboot protocol" Admittedly the script is tiny, but still: Read man! Read! The stuff is there for a reason!
LMAO
berndblb said:
Good! Glad you worked it out. Maybe wearing green colored glasses while reading forums would help
ICS: 4 icons in bootloader, push Volume Up on flashing USB to get into fastboot
JB: 3 icons and you're in fastboot by default.
Or was that from JB 4.1 to 4.2? Can't remember... My problem is a serious case of CRS...
The glasses would come in handy here again: Read the script: "Starting fastboot protocol" Admittedly the script is tiny, but still: Read man! Read! The stuff is there for a reason!
LMAO
Click to expand...
Click to collapse
Very Good, everything worked out perfect and thank you!
You made me laugh with the green glasses comment lol.
I'm on kitkat nightly .. Seems OK. I notice some lag but nothing crazy.. I was thinking about going to paranoid or another ROM but who knows lol.
I installed cm on two kindle fires last night with the adb... Thank god for development ,damn that kindle skin blows.. No app store just the amazon app store, what a bunch of crapppp...
But thank you again for taking the time out to help.
So I've been waiting on a unified firmware before trying CM. Don't judge me. However, I can't get it to boot. CWM recovery works fine, wiping /data and /cache works fine, as does installing the zip.
I tried both nightlies, and both won't boot beyond the Moto 'BOOTLOADER UNLOCKED" warning. This is the Verizon RAZR HD.
Any thoughts?
same for me
I got the exact same behavior. I think todays nightly should be sorted out.
Ask in QA
Saludos
gustrick said:
Ask in QA
Saludos
Click to expand...
Click to collapse
I finally got it worked out. I have a feeling my recovery image may have been corrupted. It installed fine, but you never know.
Either way, these are the files I used (for others to reference)
recovery-clockwork-6.0.4.4-xt926
d688093be16b953f860b35341df3ab08
cm-11-20140220-NIGHTLY-moto_msm8960
847519fbff300dc35538bf61785065be
-- Also, don't forget to format /system. You'll have to dig for that option in the storage and mounts section of your recovery
SCFirefighter said:
I finally got it worked out. I have a feeling my recovery image may have been corrupted. It installed fine, but you never know.
Either way, these are the files I used (for others to reference)
recovery-clockwork-6.0.4.4-xt926
d688093be16b953f860b35341df3ab08
cm-11-20140220-NIGHTLY-moto_msm8960
847519fbff300dc35538bf61785065be
-- Also, don't forget to format /system. You'll have to dig for that option in the mounds section of your recovery
Click to expand...
Click to collapse
Use philz 6128 w/cwmr 6047.
I'm having a weird issue with the latest unified build, I get stuck on "warning bootloader unlocked" but only when I power off the phone to charge it lol
Sent from my RAZR HD
What is the difference between moto_msm8960 and moto_msm8960dt?
Sent from my Droid Razr Maxx HD
XBlackChaosX said:
What is the difference between moto_msm8960 and moto_msm8960dt?
Sent from my Droid Razr Maxx HD
Click to expand...
Click to collapse
The dt is for the Moto X I believe.
Sent from my DROID RAZR HD using Tapatalk
I can't see, to be able to get this rom to detect my T-Mobile Sim.
Sent from my Droid Razr Maxx HD
Hydr0id said:
I'm having a weird issue with the latest unified build, I get stuck on "warning bootloader unlocked" but only when I power off the phone to charge it lol
Sent from my RAZR HD
Click to expand...
Click to collapse
I have the same problem on unified from Feb21st. I'm afraid that when my battery goes, I'll have a soft-bricked phone because it won't charge.
When installing CM, one thing I did not do was formatting /system, because I couldn't find that option anywhere on CWM.
Does anyone know a way to fix this?
MauricioBR said:
I have the same problem on unified from Feb21st. I'm afraid that when my battery goes, I'll have a soft-bricked phone because it won't charge.
When installing CM, one thing I did not do was formatting /system, because I couldn't find that option anywhere on CWM.
Does anyone know a way to fix this?
Click to expand...
Click to collapse
I thought I was the only one, I can confirm the problem still persists on 2/24 nightly, on today's one I haven't tried yet. Also, the format/system is under mounts & storage in the main menu of CWM. I did a clean install of the unified nightlies, that hasn't solved my problem, I'm really concerned of what could happen if my phone powers off and there is no way to past the "bootloader unlocked" screen.
Sent from my RAZR HD using Tapatalk
While I certainly hope you guys can get back on your feet I would advise you to get the team black hat active USB connector. It allows your phone to boot and flash without battery.
eta: http://shop.teamblackhat.info/Factory-style-programming-cable-for-Motorola-FactCable.htm
I have no ties to these folks or this product, except for owning one. It has saved twice in 2 years. Don't need it much, but you'll be glad to have it when you need it.
It took me over 8 hours of on and off flashing before I got it right. I blamed it on my recovery, since the md5's of all the zips I downloaded were correct, even after copying them to the sd card via my laptop.
I would try this:
Find your original Motorola usb cable. I've seen a lot of posts over the years because of bad cables.
Make sure you have the right one, and re-flash CWM recovery. Check its md5 before flashing using the one from my earlier post.
Boot into CWM and format /data and /cache, and then find the option to format /system.
Flash the nighly from http://get.cm/?device=moto_msm8960
Flash the gapps package for CM11: http://wiki.cyanogenmod.org/w/Google_Apps
Reboot
Even if you've done this already, just try it again. Like I said I spent all day getting frustrated, and almost gave up on it. I am not entirely sure it was my recovery, but I have nothing else to blame it on.
Good luck.
SCFirefighter said:
While I certainly hope you guys can get back on your feet I would advise you to get the team black hat active USB connector. It allows your phone to boot and flash without battery.
[...]
I have no ties to these folks or this product, except for owning one. It has saved twice in 2 years. Don't need it much, but you'll be glad to have it when you need it.
It took me over 8 hours of on and off flashing before I got it right. I blamed it on my recovery, since the md5's of all the zips I downloaded were correct, even after copying them to the sd card via my laptop.
I would try this:
[...]
Even if you've done this already, just try it again. Like I said I spent all day getting frustrated, and almost gave up on it. I am not entirely sure it was my recovery, but I have nothing else to blame it on.
Good luck.
Click to expand...
Click to collapse
I just installed the last non-unified version and it's working as expected. I'll use this version for now, until the problem is fixed.
Are you using the official CWM? And which fastboot utility do you recommend? I know that the one that comes from SDK can cause issues with moto.
MauricioBR said:
I just installed the last non-unified version and it's working as expected. I'll use this version for now, until the problem is fixed.
Are you using the official CWM? And which fastboot utility do you recommend? I know that the one that comes from SDK can cause issues with moto.
Click to expand...
Click to collapse
Congrats! Try doing the OTA updates to the unified builds. I've read that is successful. I used snapdragon specific fastboots I found online a while ago. However, I've never really seen it specified, so I assume the normal one that come with the SDK will work just fine.
SCFirefighter said:
Congrats! Try doing the OTA updates to the unified builds. I've read that is successful. I used snapdragon specific fastboots I found online a while ago. However, I've never really seen it specified, so I assume the normal one that come with the SDK will work just fine.
Click to expand...
Click to collapse
The unified versions do not show up on the updater.
I tried to search another way to do the OTA, but had no luck. I tried installing the unified from the 24th over the non-unified (without wipes), but the charging problem came back.
Next step is to try flashing CWM over again and will go from that -- although I find hard to believe that the same CWM that works for one version is causing the other to bug out.
I've pushed and merged the fix for charge only mode: http://review.cyanogenmod.org/60302
It will be fixed in the next nightly.
kabaldan said:
I've pushed and merged the fix for charge only mode: [...]
It will be fixed in the next nightly.
Click to expand...
Click to collapse
Wow, thanks so much!
I saw it was added on the nightly and I'm downloading right now to test it.
Edit: It's fixed! Thanks again!
I can't believe how inconsistent this **** is. So I messed up my phone and wanted to start over. Now the same files I successfully flashed and booted (see first page) now don't boot past the bootloader screen again.
Even after flashing the Verizon stock image back into my phone, the same files that were still on my external sd card refuse to successfully boot.
w t f
ETA: I am so f'n pissed right now. I was so happy with CM and I spent the last hours trying to get this back on my phone. Ready to throw this thing out. 2 different recoveries, 5 different CM zips. NONE boot past the bootloader image!!!!!!!!!!!!!!!!
SCFirefighter said:
I can't believe how inconsistent this **** is. So I messed up my phone and wanted to start over. Now the same files I successfully flashed and booted (see first page) now don't boot past the bootloader screen again.
Even after flashing the Verizon stock image back into my phone, the same files that were still on my external sd card refuse to successfully boot.
w t f
ETA: I am so f'n pissed right now. I was so happy with CM and I spent the last hours trying to get this back on my phone. Ready to throw this thing out. 2 different recoveries, 5 different CM zips. NONE boot past the bootloader image!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
I take it that stock rsd restore was successful for a boot to stock & the 1st boot to google login & getting to homesreen & etc? You are referring to failures after this 1st stock boot right?
Just to be on the same page.
aviwdoowks said:
I take it that stock rsd restore was successful for a boot to stock & the 1st boot to google login & getting to homesreen & etc? You are referring to failures after this 1st stock boot right?
Just to be on the same page.
Click to expand...
Click to collapse
Flashing back to stock results in a fully functional phone. When I boot into the custom recovery and format everything followed by the zips I just don't get it to boot at all.it just hangs at the unlocked boot loader warning.