Hi Guys,
After flashing Revolver in CWM , it started putting me on a reboot loop. I've searched and all the fixes require some sort of .zip file and a reflash. This is not working for me as CWM does not detect my SD card thus I am unable to put these fixes onto my device.
What can I do to get out of this horrible reboot loop ?
Cheers
Firmin
welcome Firminator,
did you try this?
http://forum.xda-developers.com/showthread.php?t=1688012
Thanks,
I managed to fix it through a cold boot + one of the patches.
However no matter how many times I try it. Revolver still doesn't flash properly and I still end up with the stock ROM.
I have the same problem, how do you do a patch? Im pretty new so any help would be greatfull. I see where roach has a code that supposedly fixes this but i don't know how to use it. Thank you
Firminator said:
Hi Guys,
After flashing Revolver in CWM , it started putting me on a reboot loop. I've searched and all the fixes require some sort of .zip file and a reflash. This is not working for me as CWM does not detect my SD card thus I am unable to put these fixes onto my device.
What can I do to get out of this horrible reboot loop ?
Cheers
Firmin
Click to expand...
Click to collapse
Where is this CWM 5.8.3.4 coming from? If it's ROM Manager then that is probably your biggest problem. ROM Manager is known to bring mostly problems to the Transformer. Use either Roach's latest fixed version Touch Recovery if you can get by with only internal sdcard access or Rogue XM's latest Touch Recovery if you need access to internal and external sdcards.
---------- Post added at 02:02 AM ---------- Previous post was at 01:58 AM ----------
Richbyrd1981 said:
I have the same problem, how do you do a patch? Im pretty new so any help would be greatfull. I see where roach has a code that supposedly fixes this but i don't know how to use it. Thank you
Click to expand...
Click to collapse
This post explains how to fix the boot loops:
http://forum.xda-developers.com/showpost.php?p=23339963&postcount=249
It requires that you have adb setup and are able to access your device through adb while in Recovery.
Used Easyflasher and flashed CWM for a permanent fix.
Installed Megatron , OCed . All is well.
I give up - selling tablet on ebay
For those of you who can fix this problem, have an otherwise perfectly functional Asus TF101 up for sale on eBay, seller "wiegie." I only hope that someone can get it working and usable again.
Related
Hi guys,
I followed the guide here after confirming I had Android 3.1 installed on my Xoom 3.2GB wifi only (Cdn market):http://forum.xda-developers.com/showthread.php?t=1078019&highlight=bootloop
I am able to load ClockworkMod no problem, and I flashed the WiFi_RootTool_3.1.zip no problem and it scrolled through it's text and told me it was done. I then told ClockworkMod to reboot.
However, upon reboot my Xoom is stuck in infinite 'boot loop' - Can anyone provide some thoughts on how to Root it? I've returned it to stock and tried doing it again, but with the same problem....
am0rak said:
Hi guys,
I followed the guide here after confirming I had Android 3.1 installed on my Xoom 3.2GB wifi only (Cdn market):http://forum.xda-developers.com/showthread.php?t=1078019&highlight=bootloop
I am able to load ClockworkMod no problem, and I flashed the WiFi_RootTool_3.1.zip no problem and it scrolled through it's text and told me it was done. I then told ClockworkMod to reboot.
However, upon reboot my Xoom is stuck in infinite 'boot loop' - Can anyone provide some thoughts on how to Root it? I've returned it to stock and tried doing it again, but with the same problem....
Click to expand...
Click to collapse
Check your version of CWM recovery. You are best off using the Tiamat custom recovery 3.2.0.0 R4c from here: http://forum.xda-developers.com/showthread.php?t=1074979 with an external microsd card. containing the file you want to flash in your Xoom. If you use Rom Manager, it will install v4004 which doesn't recognize the microsd card, and won't let you flash from it or back up to it. From your description, I'm guessing that that is your problem.
If this is not the problem and you have the right recovery file, and you are using the external microsd card in your Xoom to flash, then it may be that the zip file you are flashing is either a bad download or incomppatible with the 3.1 update on your Xoom. At any rate, once we figure out the cause we can solve the problem.
okantomi said:
If this is not the problem and you have the right recovery file, and you are using the external microsd card in your Xoom to flash, then it may be that the zip file you are flashing is either a bad download or incomppatible with the 3.1 update on your Xoom. At any rate, once we figure out the cause we can solve the problem.
Click to expand...
Click to collapse
My guess would be that the user is trying to use the Wifi root tool for the US 3.1 rom, to try to root the Canadian 3.1 rom, which is very different. There will definitely be problems with this method.
My suggestion would be to just install the Tiamat Hammerhead Rom, which will turn his xoom into a USA 3.2 xoom, and give him lots of useful features which the stock roms are lacking
also be patient...the screen loops for a good few minutes after a new root or ROM flash. Try waiting for five minutes...I was surprised at how patient I needed to be
Koush has released the latest CWM recovery for the xoom (Wi-Fi only), also as a touch version. This recovery installs without a problem using Rom Manager, however, if you want to install a zip from sdcard or do a backup it won't mount your sdcard and gives you an error message.
I know people recommend eos or rouge recoveries but I'm curious if someone managed to get Koush's one to work?
To be honest, Koush's CWM recoveries are awesome, but for the xoom, the EOS and Rogue recoveries are the recoveries to go. They are somewhat based off of Koush's recovery, but the EOS and Rogue recoveries revolve around working with the xoom. They can mount the external sd card and perform operations on it without a problem.
While we all appreciate the official CWM recovery being updated for the xoom, I don't think there is much interest in actually using it, especially when the other recoveries fit the xoom just a bit better.
ddsouza said:
Koush has released the latest CWM recovery for the xoom (Wi-Fi only), also as a touch version. This recovery installs without a problem using Rom Manager, however, if you want to install a zip from sdcard or do a backup it won't mount your sdcard and gives you an error message.
I know people recommend eos or rouge recoveries but I'm curious if someone managed to get Koush's one to work?
Click to expand...
Click to collapse
Not sure if you are also aware of this but flashing recoveries from Rom Manager could be a problem as well. As with most of my android devices using Rom Manager is not recommended. Go into Development and wait to see if it shows up there and flash it by the right means......
Just my suggestion
I've tried flashing the touch recovery version as well, manually via fastboot, and it doesn't mount /sdcard/ for me either. Has anyone managed to get this to work?
I know people really like EOS recovery and rogue but I was never a fan of rogue and EOS soft touch is a bit sensitive with the toggles. Not that I don't appreciate the efforts, just a matter of preference. Good to see I'm not the only one with the mounting issue though.
Cubanluke88 said:
I've tried flashing the touch recovery version as well, manually via fastboot, and it doesn't mount /sdcard/ for me either. Has anyone managed to get this to work?
I know people really like EOS recovery and rogue but I was never a fan of rogue and EOS soft touch is a bit sensitive with the toggles. Not that I don't appreciate the efforts, just a matter of preference. Good to see I'm not the only one with the mounting issue though.
Click to expand...
Click to collapse
Fully working touch recovery with ability to mount internal / external SD cards is twrp. Myself I am impressed of how amazing and stable it is...
Sent from my MZ601 using Tapatalk 2
---------- Post added at 01:02 AM ---------- Previous post was at 01:00 AM ----------
And here is the link for twrp recovery by runandhide05
http://forum.xda-developers.com/showthread.php?p=28988754
Sent from my MZ601 using Tapatalk 2
Oh I forgot about twrp. I'll check that out next.
I only really started looking at cwm touch recovery because thats what I'm using on my gnexus and it looks really nice and is fully functional. Is the xoom twrp official or a port?
and suddenly my xoom won't turn on....
---------- Post added at 08:23 PM ---------- Previous post was at 08:10 PM ----------
I'm running a B90 TF101 and I run CM9. I tried a few other ROMs and decided to go back to CM9, so I used CWM to restore one of my backups. Problem is, now my installation does not see the internal memory (the one it thinks is the sd card), so I cannot get at my backups or use ROM Manager (because it requires an SD card to be mounted).
However, my card does seem to be mounted in the usual places (/sdcard, /storage, etc.) so I cannot figure out why it's not seeing it, and I need it mounted to do anything useful on my tablet.
I did read of a bug in CM9 where we need to create certain directories (/Removable) on each boot, but the script provided didn't seem to make a difference, so I'm a little lost at the moment about how to fix this. Can anyone suggest any articles/posts/info, or give me some advice on this?
Hi,
Sorry, but it is not the bootloop issue. I've had (and solved) that problem several times before, with the exact solution you detailed below. It is something else, because I am able to boot into Android, but not able to see the internal storage memory.
guiloma said:
Hi, i think i might help you. I've just solved this issue(i think). Do you have the recovery bootloop problem?(this means the only way to get into the ROM is pressing PWR+VolDown and Cold Boot). That was my case, and i wasn't able to access de sdcard from the ROM, althought a can access it through ADB. If thats your case, next lines can be helpful.
I just applied the the fix for the recovery loop fix and i get it solved.(You can find this fix on several forums)
(Through ADB)
su
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
reboot
I think this may be related with "forcing" the deviced to coldbot, not exiting properly from CWM Recovery. I hope this helps you!
P.D.: I apologize for my english, i've done my best to get undestood
Click to expand...
Click to collapse
Well, if I find out, I'll post it here (unless someone else has a solution)
guiloma said:
Sorry it didn't help. That worked for me. I still think that the issue must be somehow related to a previous uncorrect dismount of the storage, or something similar. I hope you can sort it out!.
Click to expand...
Click to collapse
lingh said:
Well, if I find out, I'll post it here (unless someone else has a solution)
Click to expand...
Click to collapse
Same thing happened to me today after trying the official CM10 nightly and then trying to revert to an AOKP (ICS) nandroid. Did you try a JB ROM and then try to go back to ICS?
I read in the CM10 preview thread that nandroid backups don't include kernels (which was a surprise to me)...I'd suggest either reflashing the ROM that you're trying to use over itself (immediately after restoring your backup), or just reflashing the kernel itself (if you were using a custom one). I reflashed guevor's kernel after my nandroid restore and that fixed the problem for me. Reflashing the entire ROM should maintain your data/settings and also include the kernel.
My guess is that options or mount points for the internal storage are just not compatible between ICS and JB.
Yes, I tried CM10 preview, then tried to revert to my CM9 CWM backup. And reflashing CM9 did not work. I have had to flash Android Revolution to get my system workable again.
buck2202 said:
Same thing happened to me today after trying the official CM10 nightly and then trying to revert to an AOKP (ICS) nandroid. Did you try a JB ROM and then try to go back to ICS?
I read in the CM10 preview thread that nandroid backups don't include kernels (which was a surprise to me)...I'd suggest either reflashing the ROM that you're trying to use over itself (immediately after restoring your backup), or just reflashing the kernel itself (if you were using a custom one). I reflashed guevor's kernel after my nandroid restore and that fixed the problem for me. Reflashing the entire ROM should maintain your data/settings and also include the kernel.
My guess is that options or mount points for the internal storage are just not compatible between ICS and JB.
Click to expand...
Click to collapse
guiloma said:
Hi, i think i might help you. I've just solved this issue(i think). Do you have the recovery bootloop problem?(this means the only way to get into the ROM is pressing PWR+VolDown and Cold Boot). That was my case, and i wasn't able to access de sdcard from the ROM, althought a can access it through ADB. If thats your case, next lines can be helpful.
I just applied the the fix for the recovery loop fix and i get it solved.(You can find this fix on several forums)
(Through ADB)
su
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
reboot
I think this may be related with "forcing" the deviced to coldbot, not exiting properly from CWM Recovery. I hope this helps you!
P.D.: I apologize for my english, i've done my best to get undestood
Click to expand...
Click to collapse
Dude you Rock! Fixed my problem
Alright, problem fixed, but it took a lot of work.
What I did first is downloaded and flashed Android Revolution for my TF101 (link on these forums), then, after verifying it picked up my storage correctly, I downloaded and installed SuperSU, ROM Manager and ROM Manager Premium (the last I had paid for previously anyway).
I downloaded via the manager the CGM 10 Nightly for my TF101 (I guess this would also work with CGM 9 Nightly, RC or Full Release)
I opted to Backup the current rom, clear the Dalvik cache and also to wipe system and data and let it do its work. And bingo, it booted into CGM with a working internal storage, and also on JB now, since this is the CGM10 nightly which uses JB instead of ICS as base.
Every time I try to flash something my tablet fails, and I have to revert back my backup. It doesn't matter if I download on PC or from the tablet itself. HELP!!!!
Galaxy Tab 2 7.0
Can you post what rom you are using right now, as well as what recovery version.
Also, what rom are you trying to flash ? You are rooted, right ?
If you can post some more details - am sure people will chime in
Good luck,
bill_in_mtl said:
Can you post what rom you are using right now, as well as what recovery version.
Also, what rom are you trying to flash ? You are rooted, right ?
If you can post some more details - am sure people will chime in
Good luck,
Click to expand...
Click to collapse
I'm running stock 4.0.4, Rooted, Clockworkmod recovery. I have tried to flash several different roms. Romswell, AOKP, CM nightlies thru ROM manager. all of them fail in recovery. I flash stuff all the time on my SIII so I'm not really a Noob to flashing and what not, but I can't figure this one out. Thanks for any help.
What are you using for recovery? When you say failed what is the error message? Sounds like you should prolly reflash a current official recovery. If by failing you mean it hangs on first boot then your not wiping system before flashing. Factory reset and wipe system before you flash.
Are you by chance running any scripts for sd card swap, etc ?
I am running this script, http://forum.xda-developers.com/showthread.php?t=1961097 which swaps my 32GB external sd for the internal sd, which runs great - no issues, except with rom manager and flashing from recovery.
I have to go back and de-activate the script, reboot, and then dowload - or transfer file from PC, and it flashes without issue
Otherwise, I have had no flashing issues of any kind - using CWM 6.0.1.5 for the p3113
Good luck,
Bill
Hi Everyone,
Long time silent reader here that is now posting.
I was trying to upgrade from stock to one of the CFW, but ran into an issue. For the first half I was able to load TWRP 2.5. Then I tried loading the 4.4.4-CROMBi-kk and it finished with an error. So I tried wiping a few things and still would not work. Finally, I loaded CWM as I was more familiar with it. I did whatever wipe I can do and now I can't boot any thing other than CWM.
Now I can't load anything. It says it count mount SD card. I tried doing a factory restore and that did not work. No Fastboot available. Just CWM.
Attached is the screenshot of CWM.
Am I out of luck? I definitely will not be drinking and upgrading next time:crying:
Any help is appreciated.
crispyb said:
Hi Everyone,
Long time silent reader here that is now posting.
I was trying to upgrade from stock to one of the CFW, but ran into an issue. For the first half I was able to load TWRP 2.5. Then I tried loading the 4.4.4-CROMBi-kk and it finished with an error. So I tried wiping a few things and still would not work. Finally, I loaded CWM as I was more familiar with it. I did whatever wipe I can do and now I can't boot any thing other than CWM.
Now I can't load anything. It says it count mount SD card. I tried doing a factory restore and that did not work. No Fastboot available. Just CWM.
Attached is the screenshot of CWM.
Am I out of luck? I definitely will not be drinking and upgrading next time:crying:
Any help is appreciated.
Click to expand...
Click to collapse
This should be helpful:
http://forum.xda-developers.com/transformer-tf300t/help/guide-t2854495
cmendonc2 said:
This should be helpful:
http://forum.xda-developers.com/transformer-tf300t/help/guide-t2854495
Click to expand...
Click to collapse
Thanks for the link. I actually found this thread 2 nights ago and was able to restore the boot loader.
http://forum.xda-developers.com/showthread.php?t=2283563
The issue I was I installed the incorrect CWM that was incompatible with the latest boot loader. I followed the mentioned instructions on the 2nd page post#14 and I was able to install the correct version of twrp. Then I was able to install Crombi-KK without any issues.
Everything is working smoothly now.
crispyb said:
Thanks for the link. I actually found this thread 2 nights ago and was able to restore the boot loader.
http://forum.xda-developers.com/showthread.php?t=2283563
The issue I was I installed the incorrect CWM that was incompatible with the latest boot loader. I followed the mentioned instructions on the 2nd page post#14 and I was able to install the correct version of twrp. Then I was able to install Crombi-KK without any issues.
Everything is working smoothly now.
Click to expand...
Click to collapse
Great to see you up and running....
Can you add 'SOLVED' to your thread title ....
Thx Josh