Database Info

[Q] Can't get it to boot

So I installed this --> showthread.php?t=1197768
However, my phone doesn't like getting into recovery, so what I did was odin to KD1 and after the installation finishes, for some reason phone always boot into recovery (stock). I applied update.zip, then got to orange recovery. Wiped data/factory and cache, then checked mounts UMMU, and installed zip from sdcard (deodexed root kg6), installs completes ok but after rebooting its on a boot loop. Nothing happens.
What can I do to get this working? I'm going to odin back to kf2+root for the time being. Is there a way to install leak KG6 and apply root?
ps: this is my 2nd time attempting to install via CWM. the first time failed as well, the robot voice would say that my partition was, something, not enough space (probably has to do with not disabling voodoo, however I didn't find any option to do that). But that was another rom.

Odin to KG4, might have to root. Then do it again

Showcase mounting error problem

I've just rooted a Showcase and I followed Cyanogen mod guide for installing their rom. Everything went smooth. Minutes later I started having problems with signal. Since I did a nandroid backup I decided to restore. Everything said completed successfully. When I reboot it stuck into boot loop.
I went back into recovery and tried to wipe cache and dalvik. Error mounting cache. Error mounting system. Error mounting /datadata
I tried to go back to cyanogen and the same Error mounting cache. Error mounting system. Error mounting /datadata. I changed into various clockwork mod versions and the same.
I tried restoring on two versions with Odin and I dont get any logo at all but straight into recovery. saying invalid argument and the same Error mounting cache. Error mounting system. Error mounting /datadata
Did cyanogen changed partition ext (MTD/BML?)? Im out of ideas. I spent the entire day yesterday checking different forums and trying out anything within the showcase area to make this phone boot.
I even tried to find a way to manually restore with the nandroid backup but the partitions wont mount. The only ones that does are /boot and /data and the /sdcard.
The nandroid backup is there. All i need is to be able to restore. The clockworkmod 4 I have now doesn't activate adb so I cant access the phone via command prompt.
UPDATE: I managed to restore my phone. After trying different tars and making tar with nandroid images I found a tar file of {EI20} 2.3.5. I tried it an it boot up well. I install a voodoo CWM and let me restore! Though the phone is not activated on the cdma network, at least its on factory state with the own carrier's software. Its only a matter of them activating the phone back.
UPDATE: I managed to boot it up with a Verizon Odin tar but the Phone is from another carrier so it wont go past the activate screen. I tried flashing the clockworkmod and restoring but im getting the same error mount on system. Any ideas?

lilizblack said:
I've just rooted a Showcase and I followed Cyanogen mod guide for installing their rom. Everything went smooth. Minutes later I started having problems with signal. Since I did a nandroid backup I decided to restore. Everything said completed successfully. When I reboot it stuck into boot loop.
I went back into recovery and tried to wipe cache and dalvik. Error mounting cache. Error mounting system. Error mounting /datadata
I tried to go back to cyanogen and the same Error mounting cache. Error mounting system. Error mounting /datadata. I changed into various clockwork mod versions and the same.
I tried restoring on two versions with Odin and I dont get any logo at all but straight into recovery. saying invalid argument and the same Error mounting cache. Error mounting system. Error mounting /datadata
Did cyanogen changed partition ext (MTD/BML?)? Im out of ideas. I spent the entire day yesterday checking different forums and trying out anything within the showcase area to make this phone boot.
I even tried to find a way to manually restore with the nandroid backup but the partitions wont mount. The only ones that does are /boot and /data and the /sdcard.
The nandroid backup is there. All i need is to be able to restore. The clockworkmod 4 I have now doesn't activate adb so I cant access the phone via command prompt.
UPDATE: I managed to boot it up with a Verizon Odin tar but the Phone is from another carrier so it wont go past the activate screen. I tried flashing the clockworkmod and restoring but im getting the same error mount on system. Any ideas?
Click to expand...
Click to collapse
Which carrier is the Showcase from? You are correct, CyanogenMod changes the partition ext to MTD.
You're probably going to need stock Odin files for your carrier, so that you can repartition back to stock.
Did you take a look at the guide HERE? A lot of info, but explains everything.

jbreakfield said:
Which carrier is the Showcase from? You are correct, CyanogenMod changes the partition ext to MTD.
You're probably going to need stock Odin files for your carrier, so that you can repartition back to stock.
Did you take a look at the guide HERE? A lot of info, but explains everything.
Click to expand...
Click to collapse
The carrier is Open Mobile; its a local carrier on PR. The is no way to get an odin tar of this company unless you take another showcase and via command prompt extract it directly from the phone or another user who did it share it over the internet. The only way I can make the restore say completed is flashing verzon odin tar, flashing CWM 4, flashing cyanogen and rebooting into recovery via cyanogen. I noticed the flashed CWM via odin is only good for flashing cyanogen. It would give allot of error. If I boot into recovery via cyanogen rom I get a CWM 5.0 instead of 4 (when booting on key commands). The CWM 5.0 allow me to restore nandroid and mount partitions but when i reboot device Im stuck at the samsung logo. I left it a few minutes and nothing.
Do you think an MTD to BML converter in a flashable zip will help booting my restore?

jbreakfield said:
Which carrier is the Showcase from? You are correct, CyanogenMod changes the partition ext to MTD.
You're probably going to need stock Odin files for your carrier, so that you can repartition back to stock.
Did you take a look at the guide HERE? A lot of info, but explains everything.
Click to expand...
Click to collapse
I already tried it and get the invalid argument error. no boot image and straight to recovery

lilizblack said:
The carrier is Open Mobile; its a local carrier on PR. The is no way to get an odin tar of this company unless you take another showcase and via command prompt extract it directly from the phone or another user who did it share it over the internet. The only way I can make the restore say completed is flashing verzon odin tar, flashing CWM 4, flashing cyanogen and rebooting into recovery via cyanogen. I noticed the flashed CWM via odin is only good for flashing cyanogen. It would give allot of error. If I boot into recovery via cyanogen rom I get a CWM 5.0 instead of 4 (when booting on key commands). The CWM 5.0 allow me to restore nandroid and mount partitions but when i reboot device Im stuck at the samsung logo. I left it a few minutes and nothing.
Do you think an MTD to BML converter in a flashable zip will help booting my restore?
Click to expand...
Click to collapse
When you flash the verizon odin tar file, are you using an .pit file, and checking repartition? This will get you converted back to BML. The tar file must be a full flash for the repartition to work.

So I am probably breaking a rule but you need help go over to www.rootwiki.com . Go to there forums and look there they have a bunch of people over there developing for the showcase.
Sent from my SCH-I500 using Xparent Blue Tapatalk 2

[Q] CWM Data Wipe/Factory Reset gets stuck on formatting SD card

I waited 2 nights to register so I could wade through fixes and tips and have seem to come up with little to nothing. I have CWM flashed on my phone through ROM Manager with the recovery file replaced in the system/bin and the update zip in the root of the SD card.
When I access CWM and click on Wipe Data/Factory reset it breezes through the first few steps pretty quickly and then gives me this error:
E: format_volume: rfs format failed on /dev/block/mmcblk0p2
It continues past this and then goes on to "formatting sd_card" and then just freezes. I left it on for 30mins and there was absolutely no progress. I've tried battery pulls and re-attempting the wipe with the same result. Have re-flashed CWM, ODIN'ed back to stock, etc etc and still run into the same snag. I'm beyond frustrated because since it never gets past this part I can't install the custom ROM I'm eying and it wipes enough data to have to ODIN every single time and re-root all over again. Just to be clear this error is NOT popping up on bootup but only during Data Wipe/Factory Reset and the only way out of the freeze is to do a battery pull which results in a soft brick.
If it helps any here is what I did prior to ever having run into this problem.
Rooted with SuperOneClick V.2.3.3
Installed ROM Manager
Installed RootBrowser Lite
Downloaded recovery and update zip
Placed both into root of SD card
Used RootBrowser Lite to move recovery file into system/bin
Booted into recovery mode
Attempted to Wipe Data/Factory Reset
Ran into snag on first try and every try thereafter
Can someone please tell me what I'm doing wrong, how to fix it or a workaround?
If possible a very detailed walk through would be appreciated as this is my first ROM flashing. Your help is greatly appreciated!

MidniteKitten said:
I waited 2 nights to register so I could wade through fixes and tips and have seem to come up with little to nothing. I have CWM flashed on my phone through ROM Manager with the recovery file replaced in the system/bin and the update zip in the root of the SD card.
When I access CWM and click on Wipe Data/Factory reset it breezes through the first few steps pretty quickly and then gives me this error:
E: format_volume: rfs format failed on /dev/block/mmcblk0p2
It continues past this and then goes on to "formatting sd_card" and then just freezes. I left it on for 30mins and there was absolutely no progress. I've tried battery pulls and re-attempting the wipe with the same result. Have re-flashed CWM, ODIN'ed back to stock, etc etc and still run into the same snag. I'm beyond frustrated because since it never gets past this part I can't install the custom ROM I'm eying and it wipes enough data to have to ODIN every single time and re-root all over again. Just to be clear this error is NOT popping up on bootup but only during Data Wipe/Factory Reset and the only way out of the freeze is to do a battery pull which results in a soft brick.
If it helps any here is what I did prior to ever having run into this problem.
Rooted with SuperOneClick V.2.3.3
Installed ROM Manager
Installed RootBrowser Lite
Downloaded recovery and update zip
Placed both into root of SD card
Used RootBrowser Lite to move recovery file into system/bin
Booted into recovery mode
Attempted to Wipe Data/Factory Reset
Ran into snag on first try and every try thereafter
Can someone please tell me what I'm doing wrong, how to fix it or a workaround?
If possible a very detailed walk through would be appreciated as this is my first ROM flashing. Your help is greatly appreciated!
Click to expand...
Click to collapse
Did you hit apply update.zip after booting into recovery the first time I don't see that listed in your steps
Sent from my Team Nightmare Amaze4G with Sense 4.0

azcledel said:
Did you hit apply update.zip after booting into recovery the first time I don't see that listed in your steps
Sent from my Team Nightmare Amaze4G with Sense 4.0
Click to expand...
Click to collapse
No, actually, I didn't. I haven't seen a guide point it out or a video that went through this step. Lemme' give this a shot and see if that helps with the problem I'm running into Thanks for the quick response, hoping this is what I was missing!

azcledel said:
Did you hit apply update.zip after booting into recovery the first time I don't see that listed in your steps
Sent from my Team Nightmare Amaze4G with Sense 4.0
Click to expand...
Click to collapse
Unfortunately this didn't seem to fix my problem. Still encountering:
E:format_volume: make_ext4fs failed on /dev/block/mmblk0p2
Formatting /sdcard/ .android_secure...
And frozen again -_- It's bad enough that the sidekick sucks as stock (took me this long to finally want to do something about it) and that it's being difficult and resisting change.

Hmmm was your phone stock before you did anything to it? Or did you get the phone used or something?
My advice would be Odin to stock and start over try redownloading the recovery.zip to make sure it wasn't a bad download. And try again go slow and tripple check to make sure your following the instructions word for word. I've messed them up a few times cuz I got cocky but I got everything down from doing it so much and checking my work. The first time I rooted my sk4g I did it with adb not superoneclick and it was my first android phone it took me 2 hours of reading and following steps perfectly.
Sent from my Team Nightmare Amaze4G with Sense 4.0

go back to stock with odin,
Then root http://forum.xda-developers.com/showthread.php?t=1100513
Flash cwm http://forum.xda-developers.com/showthread.php?t=1124453
And them flash this kernel http://forum.xda-developers.com/showthread.php?t=1663622 (dont freak out with the first boot with this kernel let it convert the partitions to ext4 and a loud voice will tell you what is going on)
Ive had that problem from flashing recovery from rom manager, and when it comes up i just return to stock. try to save and remove the update.zip from the sd card and see if you can get into recovery again and just flash the kernel(if cwm come up)

ultraprimeomega said:
go back to stock with odin,
Then root http://forum.xda-developers.com/showthread.php?t=1100513
Flash cwm http://forum.xda-developers.com/showthread.php?t=1124453
And them flash this kernel http://forum.xda-developers.com/showthread.php?t=1663622 (dont freak out with the first boot with this kernel let it convert the partitions to ext4 and a loud voice will tell you what is going on)
Ive had that problem from flashing recovery from rom manager, and when it comes up i just return to stock. try to save and remove the update.zip from the sd card and see if you can get into recovery again and just flash the kernel(if cwm come up)
Click to expand...
Click to collapse
You are my saviour! I seriously love you! This worked PERFECTLY! I'm now running Glorious Overdos v3.3 and loving every single second of it. Because of you my phone is no longer a nightmare. You deserve a thanks

G930F, LineageOS Install Fail, TWRP Frozen (Help?)

Hey all,
I'm not a total noob, but I do this so infrequently that I can't commit it to memory. Would really appreciate some help here.
I followed the official LineageOS Guide for Herolte, over here.
I had done this previously on my Nexus 7 so I was fairly confident.
Everything worked well, I got TWRP installed using Heimdall from Linux, and successfully pushed the latest LineageOS and open_Gapps images to the phone.
Rebooted into TWRP, and followed the recommendation to wipe System, Cache and data partitions. This failed with red text stating that ti was unable to mount data.
I googled some, and found a suggestion to reformat the partitions, first to a different file system and then back to their original file systems again. I tried formatting /data to exFat, and it took forever, eventually erroring out with an error message. After this I can't get into TWRP anymore. When I try the phone boots to the TWRP startup screen, and just freezes there.
I have tried reflashing TWRP using Heimdall and this does nothing. Flash succeeds, nut still freezes at TWRP splash screen.
I googled some more and found a suggestion to flash stock Samsung firmware, and then try again, this time formatting data system and cache without trying to first wipe them. Problem is I can't successfully flash stock firmware.
I tried using this method in Heimdall, but it complains "Local and device PIT files don't match and repartition wasn't specified!" and fails.
I've also tried booting into Windows and using Odin, but it never works. The screen turns grey, and no progress indicators ever start. I assumed this was because I had the incorrect drivers for the phone, and tried using zadiag.exe to replace them, but the driver install fails.
I'd greatly appreciate any help. I can't seem to force the phone to shut off, it just keeps rebooting and getting stuck on either the TWRP spash screen or on the download mode screen. I know this is solveable, but unless I figure it out fast, I'm worried I am going to burn in the screen.
Any suggestions appreciated!

Never mind. I must just have had a bad stock image.
I downloaded a different one, and retried heimdall and it flashed properly.
I am now able to re-flash and boot into TWRP again.
Hopefully I won't have the same problem again when I try to wipe the partitions...

Alright,
So I solved this issue by (once I reflashed stock, and then reflashed TWRP again) formatting the data partition twice, first to ext3, and then back to ext4. This looks to have cleared the encryption issues that were causing thsi problem ,and allowed everything to continue working as expected.

Unable to keep flashed recovery or rom. Device restores everything after reboot

I've got an old Samsung Galaxy Note 10.1 (N8010) which was flashed to a custom ROM (Cyanogenmod) in 2016. I'm not sure what version because I'm unable to boot it. A few weeks ago, the tablet rebooted without reason and got stuck on the Cyanogenmod bootscreen forever. I've let it run for 24 hours without result.
So this is what I tried:
Reboot into recovery mode (TWRP 2.8.6.0) and wipe everything. Then I tried to flash a different ROM, but when the device reboots, everything seems to be reset and it tries to boot the old corrupted ROM again. I also tried a newer version of LineageOS. But for that, I need a newer TWRP version. So I download and put the newest TWRP version on it using ODIN mode. Flash Passes says ODIN, but after reboot, TWRP 2.8.6.0 is still being loaded. I tried it again without 'reboot' checked so I can reboot directly back into recovery manually, but this also, didn't worked. (by the way, ADB works when loading TWRP, FASTBOOT doesn't work when loading ODIN mode, fastboot doesn't recognize the device)
I tried to flash stockrom back onto the device, also using ODIN mode. Flash passes, no errors. Device reboots and.. nope! It still tries to load the old Cyanogenmod forever.
I'm basically stuck here. I can't update to a newer Recovery and I cant flash the rom because everytime I reboot the device, everything change i made is gone.
I noticed that when I list files in /data the folder seems to be empty.
I also tried to reformat /data to fat and back to ext4 but formatting to fat fails and formatting to ext4 succeeds, however, after a reboot, everything i did seems to be undone by the device. Even the time and date is reset.
Is there a way I can bring back my tablet back to life? Thank you!
I have pulled the recovery.log file and uploaded it to pastebin.
I can't post a link to it because I do not have made 10 posts yet.. (very anoying). So i put the adress here:
https://pastebin.com/3muqPMzz

FSCK check on /data returned this:
Code:
~ # e2fsck /dev/block/platform/dw_mmc/by-name/USERDATA
e2fsck 1.41.14 (22-Dec-2010)
/dev/block/platform/dw_mmc/by-name/USERDATA: recovering journal
Superblock needs_recovery flag is clear, but journal has data.
Run journal anyway<y>? y
yes
e2fsck: unable to set superblock flags on /dev/block/platform/dw_mmc/by-name/USERDATA
And Odin mode: NAND ERASE ALL returns
Code:
<ID:0/006> Complete(Write) operation failed.
It seems like my Note 10.1 tablet is suffering from the emmc brick bug.

niquedegraaff said:
I've got an old Samsung Galaxy Note 10.1 (N8010) which was flashed to a custom ROM (Cyanogenmod) in 2016. I'm not sure what version because I'm unable to boot it. A few weeks ago, the tablet rebooted without reason and got stuck on the Cyanogenmod bootscreen forever. I've let it run for 24 hours without result.
So this is what I tried:
Reboot into recovery mode (TWRP 2.8.6.0) and wipe everything. Then I tried to flash a different ROM, but when the device reboots, everything seems to be reset and it tries to boot the old corrupted ROM again. I also tried a newer version of LineageOS. But for that, I need a newer TWRP version. So I download and put the newest TWRP version on it using ODIN mode. Flash Passes says ODIN, but after reboot, TWRP 2.8.6.0 is still being loaded. I tried it again without 'reboot' checked so I can reboot directly back into recovery manually, but this also, didn't worked. (by the way, ADB works when loading TWRP, FASTBOOT doesn't work when loading ODIN mode, fastboot doesn't recognize the device)
I tried to flash stockrom back onto the device, also using ODIN mode. Flash passes, no errors. Device reboots and.. nope! It still tries to load the old Cyanogenmod forever.
I'm basically stuck here. I can't update to a newer Recovery and I cant flash the rom because everytime I reboot the device, everything change i made is gone.
I noticed that when I list files in /data the folder seems to be empty.
I also tried to reformat /data to fat and back to ext4 but formatting to fat fails and formatting to ext4 succeeds, however, after a reboot, everything i did seems to be undone by the device. Even the time and date is reset.
Is there a way I can bring back my tablet back to life? Thank you!
I have pulled the recovery.log file and uploaded it to pastebin.
I can't post a link to it because I do not have made 10 posts yet.. (very anoying). So i put the adress here:
https://pastebin.com/3muqPMzz
Click to expand...
Click to collapse
Some of what you describe seems to suggest that your internal sdcard is corrupted, but, you still have TWRP booting. I would think that TWRP wouldn't boot if the internal was damaged.
Sent from my LGL84VL using Tapatalk

I can boot twrp but anything I do in there is temporary. I can't write to the internal SD. Only read. Seems like the emmc brick bug to me. I wish there was a way to check if this is absolutely true.