Database Info

Nothing happens when I flash anything

I have tried, through Clockwork Recovery, to flash several ROMs and kernels.
I tried a Tiamat ROM. Looked promising. After flashing it and rebooting, the screen showed the proper custom boot animation and then it went into Honeycomb. Everything was the same as before. Looking in system information, it still says that I'm on stock 3.1 and using the stock kernel. I tried the Tiamat kernel and the Blue ROM, same thing, it just never changes anything except the boot animation.
Troubleshooting I've done:
Tried to flash it with older versions of CW recovery
Tried to flash it through ROM manager
Anybody know why it's doing this ****? It's rooted 3.1.

How did you root?

I used this
http://forum.xda-developers.com/showthread.php?t=1073884
I can confirm that the root is working perfectly fine.

Do you have access to your external SD card from honeycomb os?

The U.S. 3.1 doesn't work with MicroSD cards...does it?
EDIT: Nope, it doesn't work still. Just tested.

Do you have superuser? If not, you may want to reroot again. Something, may not have worked properly the first time.

cam30era said:
Do you have superuser? If not, you may want to reroot again. Something, ay not have worked properly the first time.
Click to expand...
Click to collapse
Yep, I got superuser. ROM Manager even makes Superuser ask for root privileges before rebooting to flash, so I know that the root method I know isn't the issue.

I'm having the same problem.
I tried flashing the kernel, ROM, anything - it won't work. It just boots back to stock. But now I have a problem my wifi has an error.

Arrgh! The problem is RomManager's CWM. You actually CAN get it to flash things if you go into "mounts and storage" and mount /system and /data and all of that but DON'T. It will not work out well because it can not properly wipe system and you will wind up with a wifi kernel version mismatch (which will display as "wifi error" in settings). You need to flash the Tiamat CWM recovery from fastboot. I detailed the process for another person in this thread:
http://forum.xda-developers.com/showthread.php?t=1152121
Relock US Xoom Tiamat 1.4.4 resulted in hanging at Motorola logo
By the way, you will have to do a full wipe of ALL of your internal storage (so make a backup on your computer) and flash the ROM from an SD card.
Sent from my Xoom using Tapatalk

mikeserv said:
Arrgh! The problem is RomManager's CWM. You actually CAN get it to flash things if you go into "mounts and storage" and mount /system and /data and all of that but DON'T. It will not work out well because it can not properly wipe system and you will wind up with a wifi kernel version mismatch (which will display as "wifi error" in settings). You need to flash the Tiamat CWM recovery from fastboot. I detailed the process for another person in this thread:
http://forum.xda-developers.com/showthread.php?t=1152121
Relock US Xoom Tiamat 1.4.4 resulted in hanging at Motorola logo
By the way, you will have to do a full wipe of ALL of your internal storage (so make a backup on your computer) and flash the ROM from an SD card.
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
Thanks mikeserv, I'm so glad you are helping people who get snagged by that CWM recovery. It was a nightmare, and I've on a tear about it.

I need some help: My TF101 won't recognise my internal storage

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.

[Q] Can't Flash ANYTHING!!!!

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

How can I get root and custom ROMming back?

Hi
At the weekend I tried to update my TF300T from CM10.1 to CM10.2. That didn't work as I ended up in a boot loop. Then I thought, maybe I need to flash the latest system blob.
So I did that, only to find that I then couldn't install anything from zip or sd card as the recovery would not mount anything at all. Still got fastboot, so I've tried TWRP 2.6. TWRP 2.5, TWRP 2.4 and CWM, none of them will mount anything at all.
So I find myself with stock ROM, but no way of rooting or installing any custom ROMs.
I'm sure I've made a bloop somewhere, so all suggestions to resolve welcome!
Thanks
Rob

What is your bootloader? Sometimes, if you reflash the same recovery, it *may* work properly the second time around.
I am using TWRP 2.6 with my 127.5 bootloader, just for your knowledge.

aarsyl said:
What is your bootloader? Sometimes, if you reflash the same recovery, it *may* work properly the second time around.
I am using TWRP 2.6 with my 127.5 bootloader, just for your knowledge.
Click to expand...
Click to collapse
That was the tip I needed - I knew I had the right bootloader but I had downloaded the wrong TWRP (I had flashed the JB version instead of the 4.3 version). Doh!
Now flashed CM10.2 and is running Android 4.3. CPU-Z tells me I'm rooted though at the moment I can't get any root apps to work with SuperSU. I'll leave that for another day!
Rob

[HELP THREAD] cm-13 on gt-p5100

Hello guys,
I installed cm-13 successfully and it was operating fine until yesterday. Today I tried to install a theme or something and it hung. So i just felt like doing a factory reset and I did it through my cwm recovery. But before that i made a backup, then i did the reset, then i did the restore...ever since then i havent been able to open the OS...it gets stuck on the samsung GALAXY Tab2 10.1 screen. I can however access the cwm recovery. I did infact try to unzip the cm-13 that i had previously used, and it doesnt work...
Please help guys!
I am pretty new to this and i feel like i cant figure out what to do next.

Is there a way to maybe restart the whole process, like get rid of the cm-13 that is already installed and redo the whole thing again?
Kindly help guys, i was really enjoying the cm experience and i messed it up :/

killermara said:
Is there a way to maybe restart the whole process, like get rid of the cm-13 that is already installed and redo the whole thing again?
Kindly help guys, i was really enjoying the cm experience and i messed it up :/
Click to expand...
Click to collapse
you did a backup before factory reset, then you restored the same data after reset. this hardly changed anything. the reason it didn't boot, is that The problem lies at the system partition, you should wipe system partition, data partition as well and flash the same cm-13 zip again along with gapps, if you had.
now let the system start. it should boot up with a clean installation. you can then try to advance restore and chose only data partition.
later just switch to twrp recovery by Android-Andi

HELP!
billysam said:
you did a backup before factory reset, then you restored the same data after reset. this hardly changed anything. the reason it didn't boot, is that The problem lies at the system partition, you should wipe system partition, data partition as well and flash the same cm-13 zip again along with gapps, if you had.
now let the system start. it should boot up with a clean installation. you can then try to advance restore and chose only data partition.
later just switch to twrp recovery by Android-Andi
Click to expand...
Click to collapse
Hello, actually I did exactly that, i wiped system partition and all of that...then i did try with cwm, and it didnt work, what is happening is that i select the option to flash the ROM, then the screen goes blank for a second and comes back to the home screen of the cwm recovery. So basically i selected the zip and nothing happened! I then tried flashing using twrp and the problem now was that there was the "no md5 file found" message and the installation would not stop, it would go on for too long, like some sort of loop. I then switched back to cwm and tried again and it still doesnt seem to work...kindly advice on what to do next

killermara said:
Hello, actually I did exactly that, i wiped system partition and all of that...then i did try with cwm, and it didnt work, what is happening is that i select the option to flash the ROM, then the screen goes blank for a second and comes back to the home screen of the cwm recovery. So basically i selected the zip and nothing happened! I then tried flashing using twrp and the problem now was that there was the "no md5 file found" message and the installation would not stop, it would go on for too long, like some sort of loop. I then switched back to cwm and tried again and it still doesnt seem to work...kindly advice on what to do next
Click to expand...
Click to collapse
first thing check if you have updated to last official stock jellybean rom prior to cm13 upgrade.
this thread will help you to update your bootloader to jb from ics. if you have a jb bootloader already. you can skip this.
forum.xda-developers.com/showthread.php?t=2642005
next thing you should get twrp 3.0.2.8
https://www.androidfilehost.com/?w=files&flid=48848&sort_by=date&sort_dir=DESC
after wiping, restart recovery, then flash the Rom zip
it takes time with the new CM13 builds to complete installation. some earlier twrp recoveries had issues(3.0.0.1 and 0.2, not sure right now, try latest only). cwm is not supported and twrp is the only preferred recovery by the Rom developers to flash the newer roms.
remember p5100 tab is called espresso3g now, since development has been unified. you need files marked as espresso3g for your p5100.
I don't which files are you using, development has changed so confirm the files that you're using are for unified builds and not device specific.

billysam said:
first thing check if you have updated to last official stock jellybean rom prior to cm13 upgrade.
this thread will help you to update your bootloader to jb from ics. if you have a jb bootloader already. you can skip this.
forum.xda-developers.com/showthread.php?t=2642005
next thing you should get twrp 3.0.2.8
https://www.androidfilehost.com/?w=files&flid=48848&sort_by=date&sort_dir=DESC
after wiping, restart recovery, then flash the Rom zip
it takes time with the new CM13 builds to complete installation. some earlier twrp recoveries had issues(3.0.0.1 and 0.2, not sure right now, try latest only). cwm is not supported and twrp is the only preferred recovery by the Rom developers to flash the newer roms.
remember p5100 tab is called espresso3g now, since development has been unified. you need files marked as espresso3g for your p5100.
I don't which files are you using, development has changed so confirm the files that you're using are for unified builds and not device specific.
Click to expand...
Click to collapse
I followed all the steps that you suggested, and the thread suggested.
I installed custom recovery, then I updated the bootloader.
Then i flashed the new twrp, which is alot more easier to operated compared to the cwm .
then i wiped , restarted recovery, then flashed the rom,
the exact same thing that was previously happening with the cwm happened : I tapped on the rom, then a blank screen appeared and it went back to the main menu of the twrp...
The ROM i am using is: cm-13.0-20160220-1347-UNOFFICIAL-p5100.zip
i also tried using the ROM i got from get.cm : cm-11-20160822-NIGHTLY-p5100.zip
Okay so i played a slow mo video to see what the screen says before it goes back to the welcome screen:
Updating partition details. . .
. . . done
Full SElinux support is present.
MTP Enabled
Then after this pops up, it goes back to the main menu of the twrp.
What if i just reinstall the stock OS then do the whole process of getting cyanogenmod again from rooting onwards?
Kindly assist!!

killermara said:
I followed all the steps that you suggested, and the thread suggested.
I installed custom recovery, then I updated the bootloader.
Then i flashed the new twrp, which is alot more easier to operated compared to the cwm .
then i wiped , restarted recovery, then flashed the rom,
the exact same thing that was previously happening with the cwm happened : I tapped on the rom, then a blank screen appeared and it went back to the main menu of the twrp...
The ROM i am using is: cm-13.0-20160220-1347-UNOFFICIAL-p5100.zip
i also tried using the ROM i got from get.cm : cm-11-20160822-NIGHTLY-p5100.zip
Okay so i played a slow mo video to see what the screen says before it goes back to the welcome screen:
Updating partition details. . .
. . . done
Full SElinux support is present.
MTP Enabled
Then after this pops up, it goes back to the main menu of the twrp.
What if i just reinstall the stock OS then do the whole process of getting cyanogenmod again from rooting onwards?
Kindly assist!!
Click to expand...
Click to collapse
OKAY! So i have had some progress in the situation i got myself into! Now i just changed the sd card and tried to flash the ROM, so it didnt successfully flash, it says:
Zip file is corrupt!
Error installing zip file ..*the directory of the ROM*
This doesnt make sense though because i used the exact same ROM earlier and it worked, i used it for a whole day and it was fine...

killermara said:
OKAY! So i have had some progress in the situation i got myself into! Now i just changed the sd card and tried to flash the ROM, so it didnt successfully flash, it says:
Zip file is corrupt!
Error installing zip file ..*the directory of the ROM*
This doesnt make sense though because i used the exact same ROM earlier and it worked, i used it for a whole day and it was fine...
Click to expand...
Click to collapse
do what @billysam said.
dont use device specific stuff. the latest twrp will only work with unified builds. for your device you need espresso3g builds.
you will find the latest roms on android-andis github site http://andi34.github.io/index.html

killermara said:
OKAY! So i have had some progress in the situation i got myself into! Now i just changed the sd card and tried to flash the ROM, so it didnt successfully flash, it says:
Zip file is corrupt!
Error installing zip file ..*the directory of the ROM*
This doesnt make sense though because i used the exact same ROM earlier and it worked, i used it for a whole day and it was fine...
Click to expand...
Click to collapse
you're using device specific Rom build, cm13.0 unofficial p5100, the latest twrp recovery you have, is a unfied espresso3g one.
latest roms, are build upon espresso3g for p5100,p3100 and espressowifi for p5110,p5113 p3113.
use latest cm13 rom zip, marked espresso3g.
there are device specific roms and recovery, which developers have stopped working on, your issue is because of this. get unified recovery and rom.

billysam said:
you're using device specific Rom build, cm13.0 unofficial p5100, the latest twrp recovery you have, is a unfied espresso3g one.
latest roms, are build upon espresso3g for p5100,p3100 and espressowifi for p5110,p5113 p3113.
use latest cm13 rom zip, marked espresso3g.
there are device specific roms and recovery, which developers have stopped working on, your issue is because of this. get unified recovery and rom.
Click to expand...
Click to collapse
Yea i thought so too, thats why i downloaded the cm-13.0-20161117-NIGHTLY-espresso3g.zip, then i wiped and tried to flash this rom, this also gave me the same error,
i also noticed that before the lines
Zip file is corrupt
there was:
Checking for MD5 file. . .
Skipping MD5 check: no MD5 file found.

killermara said:
Yea i thought so too, thats why i downloaded the cm-13.0-20161117-NIGHTLY-espresso3g.zip, then i wiped and tried to flash this rom, this also gave me the same error,
i also noticed that before the lines
Zip file is corrupt
there was:
Checking for MD5 file. . .
Skipping MD5 check: no MD5 file found.
Click to expand...
Click to collapse
maybe the zip got corrupted, checked your pc with anti-virus? are you downloading the zip file from androidfilehost of android-andi? or some other source? checked your sd card as well?