I've flashed a couple ROMs without any issues, now after I do a factory reset, then try to wipe data in TWRP, it always fails. I still can wipe cache and Dalvik, but any ROM I try to install also fails. Anyone know what I can do to get the data wipe working? I suspect that's why my ROM installs are failing.
Thanks for any help you can give!
crjjr said:
I've flashed a couple ROMs without any issues, now after I do a factory reset, then try to wipe data in TWRP, it always fails. I still can wipe cache and Dalvik, but any ROM I try to install also fails. Anyone know what I can do to get the data wipe working? I suspect that's why my ROM installs are failing.
Thanks for any help you can give!
Click to expand...
Click to collapse
post a little more information on what you are getting when they fail, ie; what rom are you on, what are you flashing, are you unlocked, rooted? Think if you factory reset you might have lost root and may have to try again, or it may have messed up your unlocked bootloader.
Another thing to check is to make sure you have MD5 Check unchecked. IF it is checked, and you didn't download the MD5, it will fail your install
also, make sure you are flashing VZW Roms; with a lot of different versions out there, those ROMs made for sprint, at&t and TMO are likely to fail.
and as a last resort, might want to odin back to stock and try again. sometimes something gets out of whack and that's the only resort.
goldsmitht said:
post a little more information on what you are getting when they fail, ie; what rom are you on, what are you flashing, are you unlocked, rooted? Think if you factory reset you might have lost root and may have to try again, or it may have messed up your unlocked bootloader.
Another thing to check is to make sure you have MD5 Check unchecked. IF it is checked, and you didn't download the MD5, it will fail your install
also, make sure you are flashing VZW Roms; with a lot of different versions out there, those ROMs made for sprint, at&t and TMO are likely to fail.
and as a last resort, might want to odin back to stock and try again. sometimes something gets out of whack and that's the only resort.
Click to expand...
Click to collapse
Right now I'm on Liquid Smoot RC 7 that I've restored from Backup. I've also went back to my stock rooted backup and tried to install one. My bootloader is unlocked, and I'm rooted. I always check the bootloader before I boot into recovery.
I'm also only using ROMs in the VZ download list, like CleanRom (which failed), the JellyWiz (also failed). Even tried to go to Liquid Smooth RC 9 and it failed. The MD5 Check is unchecked.
Thanks for the advice, seems we think the same way. I just sooooo don't want to use Odin. I did it once, and didn't enjoy it at all.
Related
I'll try to remember the steps of what happened as best I can.
T989 All Stock Running Gingerbread (Not sure what Firmware)
1)Installed CWM via ODIN
2)nstalled SuperUser via CWM
3)Installed latest AOKP from here http://aokp.co/devices/hercules
Booted up just fine but two problems
1: No Service
2: Touch screen calibration was WAY OFF
BYAM DURP OOPS
Realized that I needed to get the latest Firmware before flashing the latest AOKP!
4)Full Wipe(I think?)
5)Install latest Firmware (T989UVMC6, right?) (Also did a factory reset/wipe)
Phone boots into Stock with latest firmware, however the touch screen is still calibrated way off!
Do steps 1-3 above again.
Touch screen calibration is still way off!
My only guess on the reason/fix for this is that maybe this is still some lingering problem of flashing the ROM on the outdated firmware, so I need to perform some sort of deeper wipe than just a Full Wipe via ClockWorkMod in order to get rid of any lingering problems. And then flash the latest firmware, and do steps 1-3 above.
Any ideas or suggestions?
Any other information needed?
Thanks in advance!
YoHoJo said:
I'll try to remember the steps of what happened as best I can.
T989 All Stock Running Gingerbread (Not sure what Firmware)
1)Installed CWM via ODIN
2)nstalled SuperUser via CWM
3)Installed latest AOKP from here http://aokp.co/devices/hercules
Booted up just fine but two problems
1: No Service
2: Touch screen calibration was WAY OFF
BYAM DURP OOPS
Realized that I needed to get the latest Firmware before flashing the latest AOKP!
4)Full Wipe(I think?)
5)Install latest Firmware (T989UVMC6, right?) (Also did a factory reset/wipe)
Phone boots into Stock with latest firmware, however the touch screen is still calibrated way off!
Do steps 1-3 above again.
Touch screen calibration is still way off!
My only guess on the reason/fix for this is that maybe this is still some lingering problem of flashing the ROM on the outdated firmware, so I need to perform some sort of deeper wipe than just a Full Wipe via ClockWorkMod in order to get rid of any lingering problems. And then flash the latest firmware, and do steps 1-3 above.
Any ideas or suggestions?
Any other information needed?
Thanks in advance!
Click to expand...
Click to collapse
wipe /system
didn't work??
prantoroy said:
wipe /system
didn't work??
Click to expand...
Click to collapse
I've done wipes like this
Via CWM I do the Factory Reset/Full wipe, then cache and dalvik cache.
Is there a way to more deeply wipe?
I saw in some other places that you can mount some locations and also wipe those too, I assume maybe doing that will result in a "fuller" wipe and also wipe the firmware too?
Care to explain exactly how I should be wiping?
Also after doing the wipe, do I just flash latest firmware, install CWM/root, and then a ROM?
Thanks
YoHoJo said:
I've done wipes like this
Via CWM I do the Factory Reset/Full wipe, then cache and dalvik cache.
Is there a way to more deeply wipe?
I saw in some other places that you can mount some locations and also wipe those too, I assume maybe doing that will result in a "fuller" wipe and also wipe the firmware too?
Care to explain exactly how I should be wiping?
Also after doing the wipe, do I just flash latest firmware, install CWM/root, and then a ROM?
Thanks
Click to expand...
Click to collapse
First,
Go to CWM
and go to mounts&stroage
then format everything except /sdcard
.
.
then flash latest Firmware.
then do whatever u like
like root,cwm or flash custom rom
prantoroy said:
First,
Go to CWM
and go to mounts&stroage
then format everything except /sdcard
.
.
then flash latest Firmware.
then do whatever u like
like root,cwm or flash custom rom
Click to expand...
Click to collapse
So without a doubt I can wipe/format everything except SD Card and just flash a firmware via ODIN and be just fine?
Just double checking because it sounds scary to wipe/format so many things!
YoHoJo said:
So without a doubt I can wipe/format everything except SD Card and just flash a firmware via ODIN and be just fine?
Just double checking because it sounds scary to wipe/format so many things!
Click to expand...
Click to collapse
no.its fine.
I do it everytime I flash a rom
prantoroy said:
no.its fine.
I do it everytime I flash a rom
Click to expand...
Click to collapse
Formatted data, system, cache, and emmc.
Did Factory Wipe/Reset, Wiped cache and Dalvik cache.
Used ODIN to flash T989UVMC6, and still the touch screen is not calibrated properly.
However (I've seen other people report that problem but haven't seen a fix) when the phone is plugged in, it works just fine, but whenever it is unplugged the touch screen very unusable due to being calibrated so wrong. :/ After wiping and formatting everything and flashing a stock Firmware I'm all out of hope now!
YoHoJo said:
Formatted data, system, cache, and emmc.
Did Factory Wipe/Reset, Wiped cache and Dalvik cache.
Used ODIN to flash T989UVMC6, and still the touch screen is not calibrated properly.
However (I've seen other people report that problem but haven't seen a fix) when the phone is plugged in, it works just fine, but whenever it is unplugged the touch screen very unusable due to being calibrated so wrong. :/ After wiping and formatting everything and flashing a stock Firmware I'm all out of hope now!
Click to expand...
Click to collapse
Me TOO
sorry unable to help
Bump
YoHoJo said:
Bump
Click to expand...
Click to collapse
Try using this app. It may help you. Worked for me!
play.google.com/store/apps/details?id=br.shop4apps.touchscreenbooster.com
My Oukitel's k4000 Touch Screen Calibration Messed Up After Flashing ROM on Wrong ROM
Hello,
Please help me. I tried to see if a ROM for 'Oukitel k4000 pro' could fit 'Oukitel k4000'.
Since it didn't work out, I flashed back to the original ROM of 'Oukitel k4000', but since then, my screen behaves wrongly to touches.
Could anyone faced and managed to beat this issue?
I saw several different posts on the net, but none of them actually helped me.
One more thing:
Please try to explain, as if you explaining a child, since my android experience is not that vast to follow all the shortcuts and proffecional terms.
Thank you,
Michael
Hey there!
I'm hoping that someone can help me out. My nephew who's a wanna-be geek was going to update my ROM (which didn't to be done really, but he wanted to show me what he was able to do). He went and downloaded the latest CM 11, rebooted and went into TWRP 2.7.0.1, did a factory reset, an advanced wipe, and did the Format Data. When he did that, it got stuck in a loop. Nothing happened. He tried to install the ROM he downloaded, and NOTHING! Long story short, by him doing the Format Data, he wiped out my partitions. TWRP, no matter what I try to do tells me it's unable to mount 'data' or 'media' etc. etc. Which is leading me to believe I have no partitions left. I've tried installing the latest update from Asus, and no dice. I've tried restoring backups that I have on my micro SD, and that's not working.
Can someone please help me and tell me how to fix this? Can I get my partitions back? I'm really hoping that I don't have to send this tablet off to Asus in Dallas, TX to have it repaired.
I'm using a loaner tablet from a rental store, hoping I can get my TF 300 fixed.
Any help is deeply and sincerely appreciated.
Omega
Sent from my SM-P600 using Tapatalk
I was about to suggest you look in the correct forum, but I see you posted there as well. Anyway, your partitions are probably okay, they have just been wiped out, that doesn't mean you lost them. Have you tried reflashing the recovery? Were you able to flash anything with said recovery before that? Wiping the partitions in the recovery shouldn't have any effect on the flashing functionality, no matter which partitions were selected (except for sdcard, since that's where the ZIPs are stored), so there might be a problem with the recovery itself. Are you sure you have the correct one for your device?
Duchman said:
I was about to suggest you look in the correct forum, but I see you posted there as well. Anyway, your partitions are probably okay, they have just been wiped out, that doesn't mean you lost them. Have you tried reflashing the recovery? Were you able to flash anything with said recovery before that? Wiping the partitions in the recovery shouldn't have any effect on the flashing functionality, no matter which partitions were selected (except for sdcard, since that's where the ZIPs are stored), so there might be a problem with the recovery itself. Are you sure you have the correct one for your device?
Click to expand...
Click to collapse
Hey there Duchman ...
Thanks for your reply. I have tried reflashing the recovery like you suggested. And after that tried to reinstall CM11.Afterwards reflashing the recovery it says “Unable to mount data." I don't know if I need to flash a more recent version of TWRP, if that would even help.
Before all of this happened I could flash almost any ROM of my choice as long as it was KitKat supported. All of my backups and restores are kept on my micro SD so they aren't accidentally deleted. As far as I know it's the correct version of TWRP. It's worked for me so far, ever since I updated to KitKat.
Sent from my SM-P600 using Tapatalk
Omega Recon said:
Hey there Duchman ...
Thanks for your reply. I have tried reflashing the recovery like you suggested. And after that tried to reinstall CM11.Afterwards reflashing the recovery it says “Unable to mount data." I don't know if I need to flash a more recent version of TWRP, if that would even help.
Before all of this happened I could flash almost any ROM of my choice as long as it was KitKat supported. All of my backups and restores are kept on my micro SD so they aren't accidentally deleted. As far as I know it's the correct version of TWRP. It's worked for me so far, ever since I updated to KitKat.
Sent from my SM-P600 using Tapatalk
Click to expand...
Click to collapse
You could try flashing a newer recovery first, I think 2.7.1.0 is available for your device. Also try doing a hard reset by cold booting - here's a how-to: https://www.youtube.com/watch?v=oTU38Ewh8qo (wipe the cache afterwards)
If that doesn't help, reverting to stock is probably your best option. Try this: http://forum.xda-developers.com/showthread.php?t=1757077 (be sure to grab the correct firmware and back up your files)
Have you tried installing any other custom ROM? Does it give you the same error when you try to restore your backup?
Here's what I've come across so far. I did the reset, and that did nothing.
Tried to flash the stock version, after a few seconds, TWRP popped up with FAILED.
I've tried flashing Omni ROM. It will flash, load up, and gets stuck at the boot screen or boot animation. This happens with just about every ROM I try to flash.
Been looking for TWRP 2.7.1.0. I'm not seeing it listed on TWRPs site. Where can I get a copy? Thanks!
Sent from my SM-P600 using Tapatalk
Here you go: http://forum.xda-developers.com/showthread.php?t=2772093
Also do try flashing another recovery, PhilZ for instance: http://forum.xda-developers.com/showthread.php?t=2597860
Did you try wiping all of the partitions again?
So I was using Calkulin's stock 33R with AK kernel, which has been running fine. I deciced that I should try PA, so i did my regular thing of making a nandroid backup, wiping /data, /system and /cache. Flashed PA and the relevant Gapps, and got stuck on PA bootscreen. So I tried it again, and upon closer inspection, in, the flashing of Gapps failed because it was unable to find build.prop.
So I tried it all over again just with PA, no Gapps, no anything else. Same result, just the PA boot animation staring at me for over 20 minutes.
I then tried flashing Clakulin's stock again, and no luck, still stuck on OPO logo screen. I thought perhaps my partitions were messed up, so I wiped everything and flashed stock 33R from CM. Well, at least that booted and my EFS data was intact. I then tried reverting to Calkulin's stock by sideloading, and it never went past the boot screen.
Bottomline: I cannot use any ROM apart from stock 33R. Installing a kernel on top bootloops, installing root bootloops, installling a ROM bootloops, almost anything I flash bootloops. This is driving me nuts.
I am using the latest Philz recovery and my BL is unlocked. I am also a very seasoned flasher and I know what I am I am doing. Yet, this issue is boggling the crap outta me.. I know the solution is probably simple, yet I'm overseeing it.
PLS DON'T KILL ME FOR NOT PROVIDING A LOGCAT. I'll provide anything requested by those helping.
EDIT 1: When I say flash stock 33R, I am referring to the factory image provided by CM on their site. Also, remmeber the nandroid backup I made? That failed to restore. Yea, it failed hard on me.
EDIT 2: I remmeber reading in another device forum where his recovery was mounting the wrong partition when flashing, which makes sense since Philz's recovery produces an error where gapps can't find build.prob. I checked the recovery settings and the only mount I can change is SD from /media/0 to /media/
EDIT 3: I want to shoot the phone, and then myself.
Perhaps try using TWRP, just to rule it out?
EddyOS said:
Perhaps try using TWRP, just to rule it out?
Click to expand...
Click to collapse
Tried TWRP, no error on flashing the Gapps, but still stuck on boot animation.
If you flash the stock factory image does that work? I know you say you can 'use stock' but you don't say whether that was your backup or the factory image
EddyOS said:
If you flash the stock factory image does that work? I know you say you can 'use stock' but you don't say whether that was your backup or the factory image
Click to expand...
Click to collapse
I meant the stock factory image. My nan droid failed to restore.
I'm stumped cause if the factory image works so should everything else. Bizarre!
Hope you get it fixed soon, bud!
One last thought - I assume the md5s matched on the files you tried to flash, correct?
EddyOS said:
I'm stumped cause if the factory image works so should everything else. Bizarre!
Hope you get it fixed soon, bud!
One last thought - I assume the md5s matched on the files you tried to flash, correct?
Click to expand...
Click to collapse
All md5s matched with the files. It IS really bizzare indeed. I searched about this problem for several hours, even on other devices. But no luck!
Try an older factory image and let it boot and do all the ota updates and try then that's what i did
gavin-phelan said:
Try an older factory image and let it boot and do all the ota updates and try then that's what i did
Click to expand...
Click to collapse
Tried that too. Started off from 25, moved to 30 and still no luck.
Ok guys I'm stumped on this one. I got the OTA notification for 5.1 yesterday on my XT1034 and so I decided to preempt any issues I might have and just flash everything back to stock 5.0.2 in order to install the update.
I was able to flash everything fine then went to reboot, got the unlocked bootloader screen and...... nothing. It just stayed on the unlocked bootloader screen. I figured I did something wrong so I reset back to fastboot mode, tried again and sure enough I missed sparsechunk 3. So I tried again, restarted, and.... same thing.
OK then, reset again and reboot into recovery mode. It booted to the Motorola splash screen, ok this is different..... nope still not loading. Reset again and try flashing a custom recovery.
CWM, flashed ok, reset again, Moto splash
TWRP, flashed ok, reset, Moto splash
Philz, flashed, reset, splash
OK.. so I'm clearly doing something wrong. Did some research and tried:
- formatting the cache and userdata partitions
> cache formatted fine, userdata refused to format, not supported for filesystem type 'raw'
- tried flashing again without erasing the partitions
> flashed fine, no change in booting
- tried flashing back to 4.4.4
> flashed fine, no change in booting
- tried flashing all the custom recoveries with 4.4.4, no change
- I found a thread where someone else had a somewhat similar issue, and apparently resolved by unlocking their bootloader
> mines already unlocked, but sure it can't hurt, tried again, but nothing since it's already unlocked
I looked for anyone that had a stock 5.1 image other than the OTA, but couldn't find anything. I gave up on trying stock and looked at some custom roms, but all of them just start with, unlock your bootloader, load a custom recovery and flash the update zip file.
Soooo I'm stumped. I've tried just about everything I can think of. I made backups of everything so I'm not worried about the data I just want a working phone again. I refuse to accept that it's borked at this point since I can still get to fastboot.
OK so, no clue what changed, but I was finally able to boot into recovery, Philz
I wiped and reformatted everything and tried flashing 5.0.2 again
rebooted and it still hung on the bootloader unlocked screen
I'll try flashing Philz again and updating through there
Captains log, startdate much too late oh clock
I reflashed Philz and wiped everything again, then sidloaded CM 12.
I'm just thankful to have a working phone again so I'll go with this for now.
tapman said:
Captains log, startdate much too late oh clock
I reflashed Philz and wiped everything again, then sidloaded CM 12.
I'm just thankful to have a working phone again so I'll go with this for now.
Click to expand...
Click to collapse
Have you tried installing the stock firmware again?
I'm having exactly the same problem, any recovery says it succeeded flashing but when i try to boot it, it goes to stock motorola recovery.
Sorry for being off-topic but what are requirements of receiving OTA?
Stock ROM, stock recovery and a locked or unlocked bootloader?
Umer520 said:
Sorry for being off-topic but what are requirements of receiving OTA?
Stock ROM, stock recovery and a locked or unlocked bootloader?
Click to expand...
Click to collapse
My experience is that you need to be unrooted, unmodified system partition and stock recovery
It's usually much easier to reflash a stock image and update than trying to unroot, uninstall, xposed tweaks, restore original build.prop settings, restore original hosts file, etc
moralesnery said:
Have you tried installing the stock firmware again?
I'm having exactly the same problem, any recovery says it succeeded flashing but when i try to boot it, it goes to stock motorola recovery.
Click to expand...
Click to collapse
I haven't tried reflashing the stock again over CM12, but I was able to find a link for stock 5.1 image, you can try going straight there skipping this whole pain.
Here's a link, you can also find it on the stock firmware sticky post that I can't seem to find anymore
https://www.androidfilehost.com/?fid=24052804347819474
tapman said:
I haven't tried reflashing the stock again over CM12, but I was able to find a link for stock 5.1 image, you can try going straight there skipping this whole pain.
Here's a link, you can also find it on the stock firmware sticky post that I can't seem to find anymore
https://www.androidfilehost.com/?fid=24052804347819474
Click to expand...
Click to collapse
Already tried to flash the full firmware again without luck, after rebooting the phone gets stuck at the Unlocked bootloader warning.
Thanks for the link.
tapman said:
My experience is that you need to be unrooted, unmodified system partition and stock recovery
It's usually much easier to reflash a stock image and update than trying to unroot, uninstall, xposed tweaks, restore original build.prop settings, restore original hosts file, etc
Click to expand...
Click to collapse
Yeah, I'll reflash stock firmware.
Just wanna confirm about bootloader.
Umer520 said:
Yeah, I'll reflash stock firmware.
Just wanna confirm about bootloader.
Click to expand...
Click to collapse
Yeah unlocking your bl doesn't affect ota's
moralesnery said:
Already tried to flash the full firmware again without luck, after rebooting the phone gets stuck at the Unlocked bootloader warning.
Thanks for the link.
Click to expand...
Click to collapse
I think at least in part what my issue was, was that the partition formatting got borked. If you can boot to a custom recovery you can wipe and reformat them. Then you should be able to reflash it normally.
I was just so tired of dealing with my phone at that point so I only tried once and gave up with stock, but I'm pretty sure that's what I need to do to fix it.
Hi guys!
I got a G3 yesterday and decided to root it. I installed TWRP and decided to install Cloudy G3.
Immediately on boot, all services stop responding. There's a loop of popups saying things like "System UI has stopped responding." The same with download manager and other things. So I figured the rom didn't install properly. I went to my backup to restore it and TWRP doesn't have it listed. I looked in all directories I could (saved it initially to /sdcard/) but it's not there. The weird part is that when you click the restore button going into the list of your backups, my backup pops up for like a quarter of a second and goes away.
I decided to use TWRP's wipe function to do a system restore. It completed and now my android version is "Cloudy g3 2.5." So... System restore installed the rom? I'm just really confused at all of this. Anybody have any insight to the stuff I've mentioned?
it0ken said:
Hi guys!
I got a G3 yesterday and decided to root it. I installed TWRP and decided to install Cloudy G3.
Immediately on boot, all services stop responding. There's a loop of popups saying things like "System UI has stopped responding." The same with download manager and other things. So I figured the rom didn't install properly. I went to my backup to restore it and TWRP doesn't have it listed. I looked in all directories I could (saved it initially to /sdcard/) but it's not there. The weird part is that when you click the restore button going into the list of your backups, my backup pops up for like a quarter of a second and goes away.
I decided to use TWRP's wipe function to do a system restore. It completed and now my android version is "Cloudy g3 2.5." So... System restore installed the rom? I'm just really confused at all of this. Anybody have any insight to the stuff I've mentioned?
Click to expand...
Click to collapse
Did you use wipe before flashing the rom? If not that's Why you had the issue you didn't wipe. You MUST wipe when flashing a rom.
hyelton said:
Did you use wipe before flashing the rom? If not that's Why you had the issue you didn't wipe. You MUST wipe when flashing a rom.
Click to expand...
Click to collapse
Did not know that, and no I didn't. But I appreciate you letting me know that, probably some volatile information I should've been aware of.
May I ask why the device fixed the CloudyG3 rom when I did wipe it? I thought wiping through TWRP sends the phone back to factory settings, but it just fixed the rom and booted fine.
it0ken said:
Did not know that, and no I didn't. But I appreciate you letting me know that, probably some volatile information I should've been aware of.
May I ask why the device fixed the CloudyG3 rom when I did wipe it? I thought wiping through TWRP sends the phone back to factory settings, but it just fixed the rom and booted fine.
Click to expand...
Click to collapse
Your welcome
It wiped your current install, current rom being cloudy it reset it to factory settings. Doing a wipe won't put you back to stock.
hyelton said:
Your welcome
It wiped your current install, current rom being cloudy it reset it to factory settings. Doing a wipe won't put you back to stock.
Click to expand...
Click to collapse
Ah, so flashing the stock lg firmware would be the only way to send a device back to factory settings? I'm enjoying this learning process for sure.
it0ken said:
Ah, so flashing the stock lg firmware would be the only way to send a device back to factory settings? I'm enjoying this learning process for sure.
Click to expand...
Click to collapse
Correct