Database Info

[fix] to those having bootloop issues with CM5 based roms

I posted in the CM5 rom thread about my phone bootlooping when either
1)the phone froze and rebooted
2)i selected reboot
this meant that this rom was basically unusable because you lose everything when you have to reboot.
This problem was persistent throughout test 1-3
I had received multiple PMs about other users also experiencing this so i know its not just me.
Well... I finally got it working!
hers what i did:
1) go through the whole flashing procedure
2) boot it up
3) do not touch the phone for at least 10 minutes (i waited 15)
4) do not sign into google, skip everything
5) once it starts to load the home screen do not touch your phone again for 10 minutes
6) sign your google account in
7) while everything is syncing, do not touch phone for 15 minutes ( at least until its done)
8) take it slow and try to avoid any reboots due to freezing
eventually the rom will accept reboots and not bootloop, my phone finally rebooted itself the next morning when it froze up. But it booted up fine, i can now reboot without bootloop!
I hope this guide helps any other android users who are very angry at not having this wonderful rom work on their phones due to bootlooping after reboot.

no but there have been apps that are missing from market when running cyan roms . i pmed him but hes too busy to respond so back to ce for me !

My "solution" (workaround?): If your phone fall into bootloop do:
1. Go to recovery mode (you may have to remove the battery to restart the phone)
2. Go to console mode.
3. Type in console: "mount -a" and hit enter. It may take some time...
4. Type in console "umount -a" and hit enter.
if you did not do steps below you may need to step between 2 and 3 do
1. Type in console: "mount -a". Hit enter.
2. Type "mkdir /system/sd". Also hit enter
3. Type "umount -a".
These steps wil allow you to properly mount ext partition from sdcard. Perhaps these steps are not needed.
I'm using AmonRA recovery 1.6.2 and this solution works for me every time. Btw. I'm not sure but I think that bootloop cause is slightly damaged system files on one partition. Maybe system detects that partition wasn't unmounted properly and not allow to mount this partition and continuing to boot system.

[Q] CWM Recovery boot loop.

So I have the issue where my CWM version is boot looping. I know how to fix it by flashing the CWM roach fix but my SD card directory is not visible either. It's only showing the internal sd card. I unfortunately can not get my transformer driver to install on my pc. The driver that is provided from the asus website isn't working. That and the driver should be showing "APX" i believe, and it's showing "Transformer".
I've done a lot of searching for help and all the recommendations are saying connect it to the computer and use adb to push the file or to create a micro sdcaard directory. Or use nvflash.
Suggestions are appreciated.
And for info, i've used a pc with windows xp, and 2 laptops one with windows 7 and one with windows 8. No luck with the drivers.

same problem, I can't ADB either.

Brand New said:
same problem, I can't ADB either.
Click to expand...
Click to collapse
I'm still actively looking for a fix. I'm trying to see if I boot in linux if I can get the tablet recognized. I'll report back. If you find a fix yourself please share.

I wonder if we flash a new update.zip and just return to complete stock if it'll work?

No, the recovery (if you have the same one I have) is that it is a bug in the recovery that continually boot loops. I have nand and tried to install fresh and it doesn't fix. If you can read your sdcard not your internal memory you can easily just install the fixed roach recovery that doesn't boot loop and that will fix it for you.

If you guys are able to cold boot into the OS, use Terminal Emulator to do what
ADB would do.
1 - Cold boot into the OS and move files needed to internal sd storage.
2 - Reboot into your bad 5.5.0.4 cwm , install the new cwm through : install zip from sdcard , choose zip from ...
3 - Once installation is done , don't press "reboot system now" , do a cold boot directly (Vol down plus power button, wait till you get the option of cold boot or wipe data, choose cold boot)
4 - Once you've booted your rom , run terminal emulator.
type : su (if superuser appp ask to you , allow). will give you a #
type : echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
type : exit
type : reboot
NOTE: Someone say the above steps only work when they skipped the exit part so try it both way.

This helped. Step one was slightly pointless due to the fact that the CWM recovery doesn't read the SD card but the internal storage. But after doing the cold reboot, I loaded the new one, and then followed the steps 1-3 without the exit and it applied with no issue. I'm now on the new touch recovery with no boot loops. Thanks very much for your help.

Yeah I should have pointed out to cold boot first and put the files needed on the internal sd.
Edit above post to show that

How do you coldboot?

Brand New said:
How do you coldboot?
Click to expand...
Click to collapse
Vol down plus power button, wait till you get the option of cold boot or wipe data, choose cold boot

baseballfanz said:
Vol down plus power button, wait till you get the option of cold boot or wipe data, choose cold boot
Click to expand...
Click to collapse
Thanks buddy I owe you one.

Thank you guys

thanks
Hi guys, I just registered today, I have been using XDA for a while now, and hadn't created an account. I rooted my asus tf and Flashed CWM and ended up getting the recovery bootloop. Within 10 minutes I had found this post and used baseballfanz suggestion to use terminal emulator, and Flashed the touch Recovery and got out of the bootloop. Now running AOKP on my TF-101 and its smooth as butter. I felt i needed to make an account today just to thank baseballfanz. You guys rock, thanks again.
**EDIT** stryke504, i neglected to thank you as well in my earlier post.

This is what this place is all about. I created an account back in 2007 and just started posting last year for the same reason.

Sick!!!! It worked!!!

Hi guys I'm in trouble!! I have continuos bootloops in recovery. I tryed to flash a rom as usual but always bootlooping adn when I tryed to make a cold boot it remain in the same " colod booting linux ".. I can't restore my backup cause I move it on my memory card and cant restore it! Can I do something? I can't boot anymore... Any suggestions? I can only install the rom I have put in the internal memory..

same issue and nothing seems to work.....help
I was caught in a bootloop with CWM 3.2....something or other...couldnt adb. Couldn't cold boot...just clicked and stayed on screen...now I have lost the recovery I did have and feel like I am royally screwed....I am on tf101 b90....so nvflash doesn't work so I read....exactly how screwed am I?

What do you mean? You don't know what recovery you are using anymore?? Have you tried NVflash? Does your computer recognize the tablet?
Sent from my PG86100 using xda premium

thank you
helped fix my problem i was having but i was caught in the terminal and it kept denying root access the way i solved this was to
cold boot
re root using vipermod 4.5 and using option 1
http://bit.ly/Ac63pA
then following the steps with the terminal commands
fully working transformer

baseballfanz said:
If you guys are able to cold boot into the OS, use Terminal Emulator to do what
ADB would do.
1 - Cold boot into the OS and move files needed to internal sd storage.
2 - Reboot into your bad 5.5.0.4 cwm , install the new cwm through : install zip from sdcard , choose zip from ...
3 - Once installation is done , don't press "reboot system now" , do a cold boot directly (Vol down plus power button, wait till you get the option of cold boot or wipe data, choose cold boot)
4 - Once you've booted your rom , run terminal emulator.
type : su (if superuser appp ask to you , allow). will give you a #
type : echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
type : exit
type : reboot
NOTE: Someone say the above steps only work when they skipped the exit part so try it both way.
Click to expand...
Click to collapse
hum, sorry, i don't mean to be slow but im not understanding how i can install from zip (sdcard) if my bad cwm can't read it.
i can cold boot, i can use terminal but how can i flash the files if i need to be in recovery to do it and that recovery won't read the sd?
is it possible to flash from terminal?
thanks,

[Q] /sdcard0 gone.

I recently installed Linux mint and what not,
and figured out I'd be able to use ADB and fastboot commands off the bat.
So I wanted to try some,
1) adb devices ~ Got a response
2) adb shell ~ worked.
hmm, Lets try fastboot.
1) adb reboot-bootloader
2) fastboot erase cache (A harmless command as I believe)
2) fastboot reboot
Now, I wind up with no signal. APN's are removed and some apps don't function.
So i try and update CyanogenMod, And I'm greeted by an 'error' when trying to download the latest nightly.
At this point , I'm really tired and just leave my phone on and call it a night.
I wake up today and my battery is gone. Charge it for a an hour or so, and squeeze out 24%+ battery.
Try redownloading CM through chrome. No luck, still an error. A weird thought dawns on my that /sdcard0/ wasnt mounted.
So I try to go through in ES File explorer and it isn't able to explore anything except the system.
I boot into my recovery and I see my USB mount option is gone and no "internal sdcard" mount point.
Though i'm not getting any error in the logs.
So im just going to push the latest CM and Gapps and see this fixes it. Ill post my response after.
If anyone has any idea what happened, any response would be great Thank you

Update: 1
Weird, I am still able to access the Sdcard when the screen prompts me to the directory to install the zip.
unfortunately , I pushed CM to the /data/ folder before trying /sdcard0/.
But well see what happens when i re-install.

No fastboot, TWRP flickering screen

Hello people,
First of all, I'm not an expert so pardon on that.
I had a MicroSD card in my tablet and it was partitioned using GParted, 2 partitons - fat32 and ext4. I erased the whole tablet with Wipe option in TWRP and installed move2sd.zip.
Anyway... When I pressed Reboot to recovery, tablet restared, showed TWRP and screen went on and off showing TWRP logo, like it was trying to load TWRP. Now... Since I installed that .zip file it might have written some code to use MicroSD card as boot? I reinstalled TWRP by flashing it via fastboot and was able to enter TWRP again.
Now the stupid part... Since it read 0mb on internal card (tablet), I wanted to fix it by formating Data... It didnt do the trick cause /data and other folders couldn't have been found. That's where I restarted the tablet and pressed Wipe data on the screen with 3 icons (RCK, Android, Wipe data)... Since then I only see 2 screens - bootup screen with Asus logo and message: Device is unlock and the next screen is TWRP and it flickers again, goes on and off just as if it was trying to load TWRP.
I cannot reflash recovery cause there is no fastboot?
I just hope this is not an expensive paper...

djakolis said:
Hello people,
First of all, I'm not an expert so pardon on that.
I had a MicroSD card in my tablet and it was partitioned using GParted, 2 partitons - fat32 and ext4. I erased the whole tablet with Wipe option in TWRP and installed move2sd.zip.
Anyway... When I pressed Reboot to recovery, tablet restared, showed TWRP and screen went on and off showing TWRP logo, like it was trying to load TWRP. Now... Since I installed that .zip file it might have written some code to use MicroSD card as boot? I reinstalled TWRP by flashing it via fastboot and was able to enter TWRP again.
Now the stupid part... Since it read 0mb on internal card (tablet), I wanted to fix it by formating Data... It didnt do the trick cause /data and other folders couldn't have been found. That's where I restarted the tablet and pressed Wipe data on the screen with 3 icons (RCK, Android, Wipe data)... Since then I only see 2 screens - bootup screen with Asus logo and message: Device is unlock and the next screen is TWRP and it flickers again, goes on and off just as if it was trying to load TWRP.
I cannot reflash recovery cause there is no fastboot?
I just hope this is not an expensive paper...
Click to expand...
Click to collapse
You can still enter RCK ??

Not that this helps your situation, so apologies.
Just started getting the screen flicker/lines randomly when handeling it. So my guess was just the loosining of something internally.
I`m also freecarding it. So that hadden`t crossed my mind.
Time for a tear down vid I guess.
Best of luck tho.

I'll make a quick video. Be right back to you...
Edit: I cannot post a video due to XDA rules, but you can search for it: TF700 no fastboot, recovery stuck (search for recent uploads, d jakolis is my username on YouTube) If you guys cannot find it, I can email the link to you.

As you can see in the video, there is not much left to do with the tablet.
However, when I selected Wipe Data on bootloader, did it wipe kernel too? I'm asking this cause I had installed data2sd.zip along with its corresponding kernel.
What would happen if someone else with the same device installed the custom ROM on MicroSD card and handed me his MicroSD card to pop in my tablet? Would it boot off it? Would I be able to enter Android and maybe somehow re-flash recovery and stock kernel along with stock ROM?

You should still be able to connect via adb. Try adb pull /tmp/recovery.log and adb logcat.

_that said:
You should still be able to connect via adb. Try adb pull /tmp/recovery.log and adb logcat.
Click to expand...
Click to collapse
Tried adb pull /tmp/recovery.log and got recovery.txt file.
Adb logcat showed this: /sbin/sh: exec: line 1: logcat: not found

djakolis said:
Tried adb pull /tmp/recovery.log and got recovery.txt file.
Adb logcat showed this: /sbin/sh: exec: line 1: logcat: not found
Click to expand...
Click to collapse
Looks like your /data partition is not formatted properly. Try this (don't type "#" and the following comment):
Code:
adb shell # connect to a shell on the device
killall -19 recovery # suspend the recovery so that it doesn't interfere with formatting
make_ext4fs /dev/block/mmcblk0p8 # format /data
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=64 count=1 # remove "wipe data" request
reboot

Wow... I don't know what to say. I'm looking at the fastboot screen! :highfive:
I didn't type the last line of your code because it rebooted itself after format data was complete - make_ext4fs... Is there any consequence for not typing the last line?
Alright, I'm in recovery right now. Question: What is installed on the tablet right now? If anything... May I proceed with installing stock ROM and maybe do nvflash process to have an unbrickable device?
P.S. What does it take to learn all these things? I'm curious cause I like coding, so if you feel happy to share it, I'm all ears.

djakolis said:
Wow... I don't know what to say. I'm looking at the fastboot screen! :highfive:
I didn't type the last line of your code because it rebooted itself after format data was complete - make_ext4fs... Is there any consequence for not typing the last line?
Click to expand...
Click to collapse
Maybe the "killall -19" stuff didn't work and the recovery was not suspended, so it may have somehow determined that the wipe was finished and initiated a reboot.
djakolis said:
Alright, I'm in recovery right now. Question: What is installed on the tablet right now? If anything... May I proceed with installing stock ROM and maybe do nvflash process to have an unbrickable device?
Click to expand...
Click to collapse
What is installed? Whatever recovery, kernel and ROM you installed last. No other apps since you just formatted /data.
Since the nvflash (flatline) process saves only BCT, bootloader, partition table and unlock token (basically all the stuff you need to get fastboot working on a hard bricked tablet), you can do that now.
djakolis said:
P.S. What does it take to learn all these things? I'm curious cause I like coding, so if you feel happy to share it, I'm all ears.
Click to expand...
Click to collapse
Lots of reading here, lots of googling and more reading. Experience with Linux on PCs helps too.

where can i wirte this codes i dont know , can anyone help me??? i have same problem

i can not connect device also in adb mode pc didnt accept the drivers

y3akup said:
i can not connect device also in adb mode pc didnt accept the drivers
Click to expand...
Click to collapse
If you can still enter recovery (which one do you have?) you can use the build in Terminal.
Otherwise you have to get the adb drivers installed and working. There is no other way if you do not have a working recover and cannot get into fastboot.
Try this tool: http://forum.xda-developers.com/showthread.php?t=2588979
Once you get the drivers installed boot the tablet to recovery and post what you get with this command:
Code:
adb devices

berndblb said:
If you can still enter recovery (which one do you have?) you can use the build in Terminal.
Otherwise you have to get the adb drivers installed and working. There is no other way if you do not have a working recover and cannot get into fastboot.
Try this tool: http://forum.xda-developers.com/showthread.php?t=2588979
Once you get the drivers installed boot the tablet to recovery and post what you get with this command:
Code:
adb devices
Click to expand...
Click to collapse
i tried this tool before but still in the device manager page i have transformer device with yellow flag

y3akup said:
i tried this tool before but still in the device manager page i have transformer device with yellow flag
Click to expand...
Click to collapse
You need to install the drivers - right click on the yellow ? and choose install drivers
Use these ones here:
http://www.androidfilehost.com/?fid=23329332407571009
http://www.androidfilehost.com/?fid=2332933240

now i have
0123456789ABCDEF recovery
but commands that from other posts didnt work

y3akup said:
now i have
0123456789ABCDEF recovery
but commands that from other posts didnt work
Click to expand...
Click to collapse
Try this command only:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=64 count=1
Copy and paste it into your cmd window

sorry but it says dd is not inside or outsite command and bla bla i cant translate directly but like this
is not recognized as an internal or external command, operable program or batch file

berndblb said:
Try this command only:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=64 count=1
Copy and paste it into your cmd window
Click to expand...
Click to collapse
now i could enter the recovery and nearly ten times i installed rom but still it couldnt open twrp and bootloader numbers i checked but i think i did something wrong what can i do now??

y3akup said:
now i could enter the recovery and nearly ten times i installed rom but still it couldnt open twrp and bootloader numbers i checked but i think i did something wrong what can i do now??
Click to expand...
Click to collapse
Splendid!
Now - did you a full wipe in TWRP before installing the rom? Select the Wipe option and swipe the button. Then re-install the rom.
On the last page of the Aroma installer you have the option of saving the installation log. Do it.
Then back to TWRP, go to Advanced and also save the recovery log.
If the ROM still doesn't boot, post both of those logs.
Also try to capture a logcat of the boot process
Code:
adb logcat -v long > logcat.txt
Post that one too.

[Q] P5113 can't write to internal storage

I have a P5113 that's been running the CM 11 nightlies just fine until a few days ago. For some unknown reason, the internal storage is stuck in read only mode which is causing applications to fail and the tablet to reboot every few minutes. I've tried using CWM recovery to do a factory reset as well as wipe cache and reformat all partitions with no effect. Have also tried to install the latest CM 11 but after reboot the older version of the image is still installed. I also cannot write or delete any files from the file system as they reappear after a reboot. I've tried to use Odin to install a factory ROM but it keeps failing and I've tried to write a PIT file to fix the partition which has also had no affect. I've tried using adb to set read/write permissions but after a reboot, the permission revert back to read only.
I would like to know if there is anything else that can be done to repartition the internal storage and reload a factory ROM so that I can start over.
Thanks
....Mike

michaelgwilson007 said:
For some unknown reason, the internal storage is stuck in read only mode
Click to expand...
Click to collapse
As you seem to know your way around: Could you try and fetch a logcat as well as the kernel dmesg output upon boot and post it for review (pastebin or similar)? If it even fails with re-flashing a Stock ROM maybe the logs give a hint about what's going on (maybe the NAND chip became corrupted leaving fsck without a possibility to fix the filesystem?).

BoneWithABeagle said:
As you seem to know your way around: Could you try and fetch a logcat as well as the kernel dmesg output upon boot and post it for review (pastebin or similar)? If it even fails with re-flashing a Stock ROM maybe the logs give a hint about what's going on (maybe the NAND chip became corrupted leaving fsck without a possibility to fix the filesystem?).
Click to expand...
Click to collapse
Thanks for the reply. I've been doing a lot of reading to work my way around. I have never reviewed the logs or know where they are but I'll see if I can figure it out. Any info on how to extract this info would be greatly appreciated.
....M

michaelgwilson007 said:
Thanks for the reply. I've been doing a lot of reading to work my way around. I have never reviewed the logs or know where they are but I'll see if I can figure it out. Any info on how to extract this info would be greatly appreciated.
....M
Click to expand...
Click to collapse
You already used "adb", so access to Settings -> Developer Options must already be enabled and "USB debugging" turned on.
Now, simply connect the tablet to the PC and open a Command Promt (or Terminal if you're on Linux). Issue a restart on the Tablet (if turned on). Once the "Galaxy Tab 2.0" kernel logo shows up issue "adb logcat >> Downloads\logcat.txt" (Windows) or "adb logcat >> Download/logcat.txt" (Linux - you may need to add a "sudo" before adb if your udev rules aren't properly set).
adb will now display "connecting" and once Android has start "adbd", should happen rather early in the boot process, it will start logging into the text file. Once the ROM has fully booted up wait for a minute, so the system settles with starting up everything, before you press CTRL+C to interrupt adb logging.
Next would be "adb shell dmesg >> Downloads\dmesg.txt" (Windows) or "adb shell dmesg >> Downloads/dmesg.txt" (Linux). That dumps the kernel output into a text file. IF you get a error here it may relate to...: 1. Your ROM is not rooted. / 2. "adb+apps" is not set in the Developer options / 3. You are running a Sammy Stock ROM where adbd has no root powers.
If you're on a Stock ROM ... Install Chainfire's adbd Insecure (you need root!), run the app, apply the patch and reboot. Now adbd behaves like in CM or OMNI (root priviledges).
You can review the text files for yourself. If you see any obvious errors that should give you a hint about what's going on. If not, then put them up for review. Though... be warned: The files contains some private data (like the MAC address of the tablet as well as some information from your WiFi). If you don't want it to be displayed to the greater public send me a PM.

BoneWithABeagle said:
You already used "adb", so access to Settings -> Developer Options must already be enabled and "USB debugging" turned on.
Now, simply connect the tablet to the PC and open a Command Promt (or Terminal if you're on Linux). Issue a restart on the Tablet (if turned on). Once the "Galaxy Tab 2.0" kernel logo shows up issue "adb logcat >> Downloads\logcat.txt" (Windows) or "adb logcat >> Download/logcat.txt" (Linux - you may need to add a "sudo" before adb if your udev rules aren't properly set).
adb will now display "connecting" and once Android has start "adbd", should happen rather early in the boot process, it will start logging into the text file. Once the ROM has fully booted up wait for a minute, so the system settles with starting up everything, before you press CTRL+C to interrupt adb logging.
Next would be "adb shell dmesg >> Downloads\dmesg.txt" (Windows) or "adb shell dmesg >> Downloads/dmesg.txt" (Linux). That dumps the kernel output into a text file. IF you get a error here it may relate to...: 1. Your ROM is not rooted. / 2. "adb+apps" is not set in the Developer options / 3. You are running a Sammy Stock ROM where adbd has no root powers.
If you're on a Stock ROM ... Install Chainfire's adbd Insecure (you need root!), run the app, apply the patch and reboot. Now adbd behaves like in CM or OMNI (root priviledges).
You can review the text files for yourself. If you see any obvious errors that should give you a hint about what's going on. If not, then put them up for review. Though... be warned: The files contains some private data (like the MAC address of the tablet as well as some information from your WiFi). If you don't want it to be displayed to the greater public send me a PM.
Click to expand...
Click to collapse
Thanks for the guidance. I'll work on getting the log files when I get home. I'm currently on CM11 with root so hopefully I'll be able to dump the kernel without too much trouble.
Once I get the files, I'll send you a PM.
.......M

Just to wrap the thread up so it won't hang around without some conclusion as we had a private exchange...
The logs showed that there's a major problem, along with some smaller ones, going on. The kernel is spamming a "command error" message, in a infinite loop at some high repetition rate, in relation to mmcblk0 to the kernel console, and logcat shows re-occurring problems with "MtpServer" which eventually crashes the "VM" (Dalvik).
Since michaelgwilson007 already attempted the "last resort" solution to flash back to Stock with a PIT for his type of SGT2 (as he said his "sdcard0" partition wasn't even there) to restore NAND partitioning and Stock firmware... the PIT goes through but he then gets a NAND write error while attempting to flash the stock firmware. Relating what the logs have to tell to what's going on the device we seem to agree that the likelyhood of the NAND chip being defective (dead flash memory cells) is very high.
Case isn't really solved, but at least we worked out a 99% probability of a hardware malfunction.
If some of the kernel dev, knowing a bit more about the low-level layer, happens to have an idea - feel free to maybe add some idea.

I sent @michaelgwilson007 a PM. You could try running an ADB command from recovery to reformat the internal storage partition. Just make sure to wait until it finishes. The instructions are in the PM.
Sent from my Nexus 4 using XDA Premium HD app

shakatu said:
I sent @michaelgwilson007 a PM. You could try running an ADB command from recovery to reformat the internal storage partition. Just make sure to wait until it finishes. The instructions are in the PM.
Sent from my Nexus 4 using XDA Premium HD app
Click to expand...
Click to collapse
Thanks for your assistance. It turns out that I had a corrupt NAND chip based on a few other tests. I replaced the motherboard and I'm good to go again.

I'm having the exact same problem, but it's not stuck, and I can certainly open apps, or run the system, can't seem to delete or rewrite or even write anything. From a brief search I came to this thread, any solution other than giving it to Samsung service for repair?

Following