So, I flashed my p3100 with unofficial cyanogenmod 13. At first everything was working just fine and then I lent it to a friend then something funny happened. Now the tab can start just fine but it will restart itself after a minute or two. I've tried factory reset but nothing, everything remains the same. I tried formatting the storage in recovery mode but it's the same. I even tried flashing cmw recovery, currently it's on twrp, but it won't change. It's still on twrp. I tried flashing with stock rom using Odin but it always failed. I tried deleting some files... at first it seemed they were deleted but they were back again. It's like nothing can be done to the storage! Can you tell me what's wrong with my tab??? And possible solution? Thanks!
hypersongster said:
So, I flashed my p3100 with unofficial cyanogenmod 13. At first everything was working just fine and then I lent it to a friend then something funny happened. Now the tab can start just fine but it will restart itself after a minute or two. I've tried factory reset but nothing, everything remains the same. I tried formatting the storage in recovery mode but it's the same. I even tried flashing cmw recovery, currently it's on twrp, but it won't change. It's still on twrp. I tried flashing with stock rom using Odin but it always failed. I tried deleting some files... at first it seemed they were deleted but they were back again. It's like nothing can be done to the storage! Can you tell me what's wrong with my tab??? And possible solution? Thanks!
Click to expand...
Click to collapse
sounds like emmc. for more info read here http://andi34.github.io/faq.html
This is happening for me too. I'll use heimdall or something to flash twrp, it reports success but then rebooting into recovery has it still as stock.
It'll reboot after a minute or so, and any changes i made (uninstalling apps, removing widgts) get undone next reboot.
not working
Same thing happen with me, I am also try to flash my device, but after reboot it will recover all my previous setting. I need to update my OS. It is on TWRP 2.8.7. Please help us.
raghvedra said:
Same thing happen with me, I am also try to flash my device, but after reboot it will recover all my previous setting. I need to update my OS. It is on TWRP 2.8.7. Please help us.
Click to expand...
Click to collapse
See smart's post. Two post back. Click the link that he posted. Scroll to the bottom.
Related
Hi all,
not sure why this predicament is happening to me, but currently I can't push any custom rom to my photon Q...
0. I installed a millions of ROMs and know how to do and using TWRP 2.6
1. Yesterday I experienced several File I/O errors during installing Pac-man ROM.
2. after TWRP full format, Installation was okay and it was also bootable, you can set up your phone just like everyday, but you cannot reboot... stuck in the moto logo everytime you reboot, and I had to RSD/FXZ restore :crying:
3. Nothing can bring this phone back with TWRP, Only RSD / FXZ restore can save the situation...
4. a stock ROM of FXZ seems okay and normally reboot, but I went back to #2, but in vain...
Any clue? My phone's flash simply borked?
palmwangja said:
Hi all,
not sure why this predicament is happening to me, but currently I can't push any custom rom to my photon Q...
0. I installed a millions of ROMs and know how to do and using TWRP 2.6
1. Yesterday I experienced several File I/O errors during installing Pac-man ROM.
2. after TWRP full format, Installation was okay and it was also bootable, you can set up your phone just like everyday, but you cannot reboot... stuck in the moto logo everytime you reboot, and I had to RSD/FXZ restore :crying:
3. Nothing can bring this phone back with TWRP, Only RSD / FXZ restore can save the situation...
4. a stock ROM of FXZ seems okay and normally reboot, but I went back to #2, but in vain...
Any clue? My phone's flash simply borked?
Click to expand...
Click to collapse
yes,i have the same problem,i try a lot times.
use cwmrecovery,it will solve all
Try CWM or Open Recovery. Try also installing custom rom from internal storage.
Thanks for the input, but neither CWM nor open recovery helped a lot after each tests, unfortunately exactly the same problem.
Only the first boot was possible with the first custom ROM right after RSD recovery.
This is extremely weird and I don't understand what this situation means.
Stock ROM looks okay since I can restore from the TWRP backup, but no other roms were recoverable from my last backups none the less flesh installation... stuck in the red moto logo, not even in the boot screen...
palmwangja said:
Thanks for the input, but neither CWM nor open recovery helped a lot after each tests, unfortunately exactly the same problem.
Only the first boot was possible with the first custom ROM right after RSD recovery.
This is extremely weird and I don't understand what this situation means.
Stock ROM looks okay since I can restore from the TWRP backup, but no other roms were recoverable from my last backups none the less flesh installation... stuck in the red moto logo, not even in the boot screen...
Click to expand...
Click to collapse
Try to remove sdcard and see if phone boots normaly without it.
What is "twrp full format"?
Thanks,
suddenly all got back to normal. I simply don't know what happened and what I have missed. maybe I have been too jittery to wait for a boot time ?
If anyone happened to have experienced any of my symptom, just wait for another min to diagnose something !
BTW, when I refer to 'twrp full format', I meant there was a format menu inside TWRP wipe section.
Using ROM Manager and the latest version of CWM I tried installing today's (12-08) nightly build of CM11 to try it out. After doing a complete backup and then wipe data/cache the install failed. I'm not sure why but it said it was aborted and to check log and report the error to ROM Manager.
After that it asked if I wanted to reboot and I wanted to make sure I restored from my backup so I backed out of the screen but then it booted up on its own. It did not get past the S3 loading screen with the CM Android/alien guy it just turned off, back to that screen again and then back into recovery.
At this point I went to recover from my backup file and it said MD5 mismatch and won't load. I've since tried wiping data/cache/dalvik cache all manually and then boot up, or wipe everything and try to install the rom again... every time it just loops back to recovery mode. The last time I tried installing the rom again it told me I might have lost root access and asked if I wanted to repair it... I'm not sure what that means.
Any suggestions? I am lost at this point. I have no experience with ADB (I'm not sure if that's my only option) but I've used ODIN mode a few times. Easiest solution would be best.
bejahu said:
Using ROM Manager and the latest version of CWM I tried installing today's (12-08) nightly build of CM11 to try it out. After doing a complete backup and then wipe data/cache the install failed. I'm not sure why but it said it was aborted and to check log and report the error to ROM Manager.
After that it asked if I wanted to reboot and I wanted to make sure I restored from my backup so I backed out of the screen but then it booted up on its own. It did not get past the S3 loading screen with the CM Android/alien guy it just turned off, back to that screen again and then back into recovery.
At this point I went to recover from my backup file and it said MD5 mismatch and won't load. I've since tried wiping data/cache/dalvik cache all manually and then boot up, or wipe everything and try to install the rom again... every time it just loops back to recovery mode. The last time I tried installing the rom again it told me I might have lost root access and asked if I wanted to repair it... I'm not sure what that means.
Any suggestions? I am lost at this point. I have no experience with ADB (I'm not sure if that's my only option) but I've used ODIN mode a few times. Easiest solution would be best.
Click to expand...
Click to collapse
I had the exact same issue when trying to flash that same CM11 nightly build but with TWRP...
I just pulled the battery took my SD card out and reinserted it and I just kept booting into recovery and turning the phone off until it let me reflash a rom or backup. Obviously this isnt the most legitimate solution but that could work for you! It did for me!...
This could have been caused by needing an update of CWM or TWRP to better support 4.4 perhaps?
Badouken said:
I had the exact same issue when trying to flash that same CM11 nightly build but with TWRP...
I just pulled the battery took my SD card out and reinserted it and I just kept booting into recovery and turning the phone off until it let me reflash a rom or backup. Obviously this isnt the most legitimate solution but that could work for you! It did for me!...
This could have been caused by needing an update of CWM or TWRP to better support 4.4 perhaps?
Click to expand...
Click to collapse
I tried that to no avail. I unfortunately had to revert to stock unrooted via ODIN mode and it got me to boot back up. I can just reroot now. Luckily I made a backup with Titanium and uploaded it to my Google Drive.
I unlocked my bootloader and then tried to flash CWM, but after rebooting it goes back to stock recovery.
Creating a backup via CWM worked fine though, but somehow it won' flash over stock recovery
Anyone else having this problem ?
ma_moto said:
I unlocked my bootloader and then tried to flash CWM, but after rebooting it goes back to stock recovery.
Creating a backup via CWM worked fine though, but somehow it won' flash over stock recovery
Anyone else having this problem ?
Click to expand...
Click to collapse
Yes it happened to me too. There was an option that I could select just before rebooting to prevent this, but it didn't work. I was on stock kk4.4.2 at that time, after installing cm11 nightly, the recovery partition was ok after the reboot. When I later restored the kk4.4.2 to see if it is possible, I had to flash the recovery partition again in order to restore cm11.
enaon said:
Yes it happened to me too. There was an option that I could select just before rebooting to prevent this, but it didn't work. I was on stock kk4.4.2 at that time, after installing cm11 nightly, the recovery partition was ok after the reboot. When I later restored the kk4.4.2 to see if it is possible, I had to flash the recovery partition again in order to restore cm11.
Click to expand...
Click to collapse
So you just flashed CM11, even though it booted back into stock recovery ?
ma_moto said:
So you just flashed CM11, even though it booted back into stock recovery ?
Click to expand...
Click to collapse
Yes eventually Idid. Just like you, I made a backup while at cwm. After the reboot, the recovery partition was gone, and the fallen robot was shown when I selected it. I powered the motog off, did the volume down-power combination, reconnected the usb cable and entered the 'fastboot flash recovery xxxxxx.img' . After a sec or so I pressed vol down , then vol up, and I was back in revovery. Did a test to verify that the backed up kk4.4.2 worked, it did, did it all over again, and flashed cm11. This time, the question about persisting on reboot was not asked, and the revovery persisted.
Ps
I am trying to reach 10 posts in order to report a bug in the developers forum, so if it sounds like I am pulling your leg, I am not.
enaon said:
Yes eventually Idid. Just like you, I made a backup while at cwm. After the reboot, the recovery partition was gone, and the fallen robot was shown when I selected it. I powered the motog off, did the volume down-power combination, reconnected the usb cable and entered the 'fastboot flash recovery xxxxxx.img' . After a sec or so I pressed vol down , then vol up, and I was back in revovery. Did a test to verify that the backed up kk4.4.2 worked, it did, did it all over again, and flashed cm11. This time, the question about persisting on reboot was not asked, and the revovery persisted.
Ps
I am trying to reach 10 posts in order to report a bug in the developers forum, so if it sounds like I am pulling your leg, I am not.
Click to expand...
Click to collapse
I did pretty much the same thing right now and just flashed CM11 and it's working. I did delete personal and system files before via CWM but somehow some pictures i took were still there after CM11 installed I'm also still running stock recovery
Everythings seems to work fine but still...strange
ma_moto said:
I did pretty much the same thing right now just flashed CM11 and it's working. I did delete personal and system files before via CWM but somehow some pictures i took were still there after CM11 installed I'm also still running stock recovery
Everythings seems to work fine but still...strange
Click to expand...
Click to collapse
Yes I did a factory reset or something like that while on cwm just before restoring. Allways do that for a cleaner install. Since you see your photos, I guess you didn't do that part corectly.
If I where you, I whould do it once more, making sure you are flashing 'CWM 6.0.4.7 Swipe Recovery for 4.4 bootloader: CWM-swipe-6.0.4.7-falcon.img' from the thead of dhacker29.
Also make sure you flash the latest nightly directly from cyanogen. This compination will give you a persistant cwm and a 'official' dhacker29 cyanogen rom.
Only problem I have is with audio on csipclient, and the embeded one, but I will eventually reach 10 posts
enaon said:
Yes I did a factory reset or something like that while on cwm just before restoring. Allways do that for a cleaner install. Since you see your photos, I guess you didn't do that part corectly.
If I where you, I whould do it once more, making sure you are flashing 'CWM 6.0.4.7 Swipe Recovery for 4.4 bootloader: CWM-swipe-6.0.4.7-falcon.img' from the thead of dhacker29.
Also make sure you flash the latest nightly directly from cyanogen. This compination will give you a persistant cwm and a 'official' dhacker29 cyanogen rom.
Only problem I have is with audio on csipclient, and the embeded one, but I will eventually reach 10 posts
Click to expand...
Click to collapse
I used CWM directly from their site, maybe that's why it isn't working probably.
You're right i should do a clean reflash, but I'm getting sick of constantly reinstalling and configuring everything
Ok this is giving me cancer! I'm flashing TWRP 2.8.1.0 and can enter this recovery immediately after flashing it. But, as soon as I reboot the phone, or boot the OS and then reboot into recovery, the recovery is restored to stock. I've flashed recoveries an unhealthy amount of times on several different devices but I've never seen this behavior before. I'm on stock Android 5.0 LRX21O.
I had this, but i reinstalled, but now it is working just fine, just needed to reinstall it
gefilus said:
I had this, but i reinstalled, but now it is working just fine, just needed to reinstall it
Click to expand...
Click to collapse
Reinstalling the recovery?
Yup, just flashed it again, same image
Look here:
http://forum.xda-developers.com/google-nexus-5/general/warning-lollipop-aosp-roms-broken-t2930512
My tab 3 wouldn't boot past the Samsung logo and was stuck in a boot loop. I tried a hard/factory reset but this did not fix the issue. I managed to flash it with the latest stock Tom. This gave me access to the tablet. The issue now is it get past the setup menus then resets it's self to the start. I've tried to wipe the cache partition but keep getting the error
E:format_volume: make_extf4ft failed on /dev/block/mmcbl k0p15
I've also been trying to root the device to try a custom rom but this also keeps failing.
Could it be faulty memory.
Thanks for the help.
Gavshell
gavshell said:
My tab 3 wouldn't boot past the Samsung logo and was stuck in a boot loop. I tried a hard/factory reset but this did not fix the issue. I managed to flash it with the latest stock Tom. This gave me access to the tablet. The issue now is it get past the setup menus then resets it's self to the start. I've tried to wipe the cache partition but keep getting the error
E:format_volume: make_extf4ft failed on /dev/block/mmcbl k0p15
I've also been trying to root the device to try a custom rom but this also keeps failing.
Could it be faulty memory.
Thanks for the help.
Gavshell
Click to expand...
Click to collapse
Which model? There are a few different tab 3's.
Sent from my SM-T210 using Tapatalk
Hi,
The model is SM-T210
I forgot to mention in my first post. One the tablet starts and ive completed the setup pages im also getting the following errors
google account manager has stopped
the process com.google.process has stopped
the process com.google.process.gapps has stopped
Then the tablet reboots as if a factory reset has been done.
Thanks.
Gavshell
gavshell said:
Hi,
The model is SM-T210
I forgot to mention in my first post. One the tablet starts and ive completed the setup pages im also getting the following errors
google account manager has stopped
the process com.google.process has stopped
the process com.google.process.gapps has stopped
Then the tablet reboots as if a factory reset has been done.
Thanks.
Gavshell
Click to expand...
Click to collapse
Flash twrp via odin, get twrp from here
http://forum.xda-developers.com/showthread.php?t=2437219
Then you can check my ROM out it is here
http://forum.xda-developers.com/showthread.php?t=3510449
If I helped you, please hit the "like" button. Thank you.
RealWelder said:
Flash twrp via odin, get twrp from here
http://forum.xda-developers.com/showthread.php?t=2437219
Then you can check my ROM out it is here
http://forum.xda-developers.com/showthread.php?t=3510449
If I helped you, please hit the "like" button. Thank you.
Click to expand...
Click to collapse
I manage to flash twrp without any issues. When i boot into recovery mode twrp isnt showing. Its booting to the arp. Ive tried a few versions of odin and old and new versions of twrp.
Regards.
Gavshell
gavshell said:
I manage to flash twrp without any issues. When i boot into recovery mode twrp isnt showing. Its booting to the arp. Ive tried a few versions of odin and old and new versions of twrp.
Regards.
Gavshell
Click to expand...
Click to collapse
What is arp? I use @gr8nole twrp 3 on my T210 and it works flawlessly.
sorry. I meant asr (android system recovery)
gavshell said:
sorry. I meant asr (android system recovery)
Click to expand...
Click to collapse
That's strange. I use odin 3.4. (I don't think it's the newest) Mine is a T210R but I am running regular T210 firmware. I'll do some research, I thought the recovery worked for both.
Thanks for the help. Its really appreciated. Ive also been trying the files from @gr8nole from his post here
http://forum.xda-developers.com/showthread.php?t=2433853
Still cant get anything to load. It flashes fine with odin. Just wont boot on the tablet.
gavshell said:
Thanks for the help. Its really appreciated. Ive also been trying the files from @gr8nole from his post here
http://forum.xda-developers.com/showthread.php?t=2433853
Still cant get anything to load. It flashes fine with odin. Just wont boot on the tablet.
Click to expand...
Click to collapse
What is the extension on the file? Is it a .zip, a .tar, or a .tar.md5? Are you in download mode when flashing? (This is probably not a necessary question but Odin will read the device even if it is booted to Android. Lol)
If I helped you, please hit the "like" button. Thank you.
The extension is tar.md5. And it's in download mode.
Ive just noticed from watching the video again. im not getting the downoad status bar on the tablet when odin is saying ifs flashing the tablet. Its definietly in download mode. When i flashed the stock rom i had the progress bar. Its jsut not showing when trying to flash twrp.