Related
Went to flash an updated Rom on my ATT One X. Been using CWM recovery.
Reboot into recovery, wipe/factory reset.
Go to find the file, SDCard is almost completely gone/items deleted.
I load up TWRP, mount the SDCard, nothing, all gone. So I just format the SDCard, copy the new Rom over to the SDCard root.
Reboot into recovery. Try to install, when I select it in TWRP, swipe, it sits, then just reboots the app and goes back to the main screen.
At a loss right now, phone apparently soft bricked. Maybe bad Rom zip?
Rooted/Unlocked of course, been working fine the past week. Only had the phone 1 week.
Ideas? Help..haha...
Easy, except you gonna have to reunlock boot loader.you can't boot into fast boot OEM relock bootloader and run ruu. You could also try using fast boot to flash something.
Sent from my HTC One X using xda app-developers app
Or it might be a case of twrp going bad. Fast boot flash recovery img and boot back into recovery.
Sent from my HTC One X using xda app-developers app
ethantarheels123 said:
Or it might be a case of twrp going bad. Fast boot flash recovery img and boot back into recovery.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
It was clockwork I was using at the time.
Everytime I rebooted into recovery and selected the file to install, more stuff was missing.
I'm wondering if the SDCard got corrupt, recovery went crazy and wiped etc...or bad Rom.
Redownloaded Rom.
Reformatted SDCard for good measure since it was all pretty much gone.
Flashed TWRP back as the recovery.
Installing the Rom now. CleanRom 4.1SE.
But...all my Sh&t is gone off the SDCard. Backups, photos etc...buh-bye forever.
Side note, my camera lens area on the phone has been getting hot. Not sure where the processor is located on this phone, maybe it is just doing that while trying to install Rom and CPU is running a little hot and normal?
techlogik said:
It was clockwork I was using at the time.
Everytime I rebooted into recovery and selected the file to install, more stuff was missing.
I'm wondering if the SDCard got corrupt, recovery went crazy and wiped etc...or bad Rom.
Redownloaded Rom.
Reformatted SDCard.
Flashed TWRP back as the recovery.
Installing the Rom now.
But...all my Sh&t is gone off the SDCard. Backups, photos etc...buh-bye forever.
Click to expand...
Click to collapse
Cwm has been known to have instability which is why almost everyone suggests using twrp, which is officially supported.
Sent from my HTC One X using xda app-developers app
ethantarheels123 said:
Cwm has been known to have instability which is why almost everyone suggests using twrp, which is officially supported.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Ok. I noticed it was nowhere near as complete and slick at say 4EXT recovery on my Inspire and suspected some weirdness was going on.
Back on TWRP now and seems to be installing the new Rom I just downloaded again.
Rebooting now...guess I should start copying my SDCard to my computer
Go to cnet.com and download recuva. Do a deep scam and it will recover most of your stuff.. worked for me.. do it on your computer.
Sent from my HTC One X using xda app-developers app
rpomponio said:
Go to cnet.com and download recuva. Do a deep scam and it will recover most of your stuff.. worked for me.. do it on your computer.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Ok, cool, will give it a look.
The CleanRom thread blew up, apparently me and bunch of others had this happen using CWM and the latest build....
All working again, now if I can recovery some stuff, like the photos I had, that would be nice.
Appreciate the replies and help.
Edit: recuva didn't find anything useful. SDCard was blasted for good somehow.
techlogik said:
The CleanRom thread blew up, apparently me and bunch of others had this happen using CWM and the latest build....
Click to expand...
Click to collapse
scrosler warned very clearly (even before the latest 4.1 build) not to use CWM. Why so many people chose to ignore him, I have no idea. For some reason the SD card wipe issue was much worse on CleanROM 4.1 than previous versions (and other ROMs).
Take note that the SD wipe issue has also happened on TWRP. Safest approach is to backup SD data to your desktop computer before flashing anything. In particular, your Titanium folder and anything not easily replaceable (photos, etc.). Its a bit of an annoyance to have to do this whenever you want to flash something. But until the cause of the issue is found and fixed, this is the safest way.
Not sure why everyone is blaming the Recovery's for loosing pictures and stuff from there internal SD card. Same thing happened to me with my HTC Touch Diamond, We all came to the conclusion it was from so much flashing. I have used both recovery's and lost pictures and My Documents. Just my 2cents worth.
Is there a tutorial somewhere showing how to switch from CWM to TWRP?
bTrizzy said:
Is there a tutorial somewhere showing how to switch from CWM to TWRP?
Click to expand...
Click to collapse
Doload goo manager and use it to install recovery. Or you can go to twrp dev thread directions are there.
Sent from my HTC One X
Just rooted and s-off a replacement one S. Everything went fine until i got to the point i was going to flash a rom. Ive been using the viper rom. after starting the installer it seemed out that all it did was format the memory. After it finished it rebooted and stayed on the HTC splash screen for probably twenty minutes before i did a hard boot. after getting back into recovery and trying again it did the same thing. i decided to just start over and do reboot from recovery but it is saying there is no OS. so i went back to view my card from recovery and everything on it was erased. Now im trying to copy the viper rom back over via recovery but the transfer speed is down to about 50kbps and keeps saying its timing out. any ideas
What recovery are u using? I read several times, that ViperRom and the latest twrp don't fit. In case of using twrp u should try an older version.
Sent from my HTC One S using xda app-developers app
customromfan said:
What recovery are u using? I read several times, that ViperRom and the latest twrp don't fit. In case of using twrp u should try an older version.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
I guess i was using the twrp with that all in one toolkit i would switch to cwm but i cant get my computer now to reconigze the phone. i keep getting the htc mtp driver issue and haven't been able to figure it out. I figured if i can get the other recovery installed i should be able to flash a os
Jayster06 said:
I guess i was using the twrp with that all in one toolkit i would switch to cwm but i cant get my computer now to reconigze the phone. i keep getting the htc mtp driver issue and haven't been able to figure it out. I figured if i can get the other recovery installed i should be able to flash a os
Click to expand...
Click to collapse
go into bootloader, then fastboot usb mode.
the flash the new recovery via fastboot command, or with the all in one toolkit (chose custom, then locate your file)
i switched over to cwm and tried copying a viper rom to my phone but it keeps erroring out during the transfer. I tried a smaller rom and it copied over but all its doing with i click install is going to a black screen then back to cwm
i also tried several other roms that were smaller in size and it was doing the same thing
I was running CleanROM Inheritance 3.4.something. I had just rebooted the tablet, battery was around 95%. I launched an app while reboot was still going on, as evidenced by the toasts that came up regarding superuser permissions.
And then it happened. The display went blank. I still had sound. Hardware buttons did nothing until I held the power button down. Device went into reboot and stalled at the bootanimation. More than 5 minutes went by so I rebooted into recovery.
While in recovery, I poked around for a backup to revert to. I have misplaced my recovery SD card...but no big deal. I was considering updating to CleanROM Inheritance 3.4.7. I downloaded that from the interwebs, copied it to an SD, then booted the device into recovery and flashed it. The flashing process had no issues and I rebooted the device.
Now the device is still doing the same thing. Still stuck at the bootanimation. Been another 5 minutes on this one too.
I compel thee to opine.
duckredbeard said:
I was running CleanROM Inheritance 3.4.something. I had just rebooted the tablet, battery was around 95%. I launched an app while reboot was still going on, as evidenced by the toasts that came up regarding superuser permissions.
And then it happened. The display went blank. I still had sound. Hardware buttons did nothing until I held the power button down. Device went into reboot and stalled at the bootanimation. More than 5 minutes went by so I rebooted into recovery.
While in recovery, I poked around for a backup to revert to. I have misplaced my recovery SD card...but no big deal. I was considering updating to CleanROM Inheritance 3.4.7. I downloaded that from the interwebs, copied it to an SD, then booted the device into recovery and flashed it. The flashing process had no issues and I rebooted the device.
Now the device is still doing the same thing. Still stuck at the bootanimation. Been another 5 minutes on this one too.
I compel thee to opine.
Click to expand...
Click to collapse
Sounds like something got corrupted. Might be worth doing a factory reset and reflash the rom to see if it boots?
Factory reset from recovery. Reflashed 3.4.7. Rebooted to clean install. Joy.
Ty sdbags...you rock. Now that I'm at square one again I should go with a 4.2.2 ROM.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
duckredbeard said:
Factory reset from recovery. Reflashed 3.4.7. Rebooted to clean install. Joy.
Ty sdbags...you rock. Now that I'm at square one again I should go with a 4.2.2 ROM.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
I reckon so
I shall get everything to an SD card and do it at work tonight. Is everything done from flashing or do I need a PC interface ?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
duckredbeard said:
I shall get everything to an SD card and do it at work tonight. Is everything done from flashing or do I need a PC interface ?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Yeah you need to flash twrp with fastboot, download stock firmware from asus unzip it and flash it with twrp then re-flash twrp again with fastboot (the asus firmware zip will wipe twrp) then install CROMi-X
JoinTheRealms said:
Yeah you need to flash twrp with fastboot, download stock firmware from asus unzip it and flash it with twrp then re-flash twrp again with fastboot (the asus firmware zip will wipe twrp) then install CROMi-X
Click to expand...
Click to collapse
Δεν είμαι σίγουρος αν κατάλαβα καλά όλα αυτά.
Yeah means I need a PC or just do it all from TWRP recovery (I think I have 2.3.1). I was looking at the CROMi-X thread and didn't see any need for a PC if I am already running a custom recovery and ROM. I might just stick with what I have for now...don't want to get in too deep. Been a while since I've done anything with the TF700 anyway, barely even used it last month.
If I can't do it all from flashing from recovery, I need to do more thinking and reading before I do anything else.
Thanks again for your support.
duckredbeard said:
Δεν είμαι σίγουρος αν κατάλαβα καλά όλα αυτά.
Yeah means I need a PC or just do it all from TWRP recovery (I think I have 2.3.1). I was looking at the CROMi-X thread and didn't see any need for a PC if I am already running a custom recovery and ROM. I might just stick with what I have for now...don't want to get in too deep. Been a while since I've done anything with the TF700 anyway, barely even used it last month.
If I can't do it all from flashing from recovery, I need to do more thinking and reading before I do anything else.
Thanks again for your support.
Click to expand...
Click to collapse
Oh I actually didnt see The bootloader package on the Cromi-x thread, that should work fine. I tried this method long ago, but my bootloader package didn't have a custom recovery included so i still needed to use a pc to fastboot one on. The cromi one should be fine
Yes I prepared the recovery and bootloader as one so as long as you have any custom recovery installed you can use my package to get to the right supported versions. Twrp 2.6 still has issues hence why I haven't upgraded yet.
I have done all the flashing. All is good. I am happy with the update but I need to thin out my apps. I am curious why there isn't an advanced power menu (shutdown, reboot, recovery, hot boot).
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
duckredbeard said:
I have done all the flashing. All is good. I am happy with the update but I need to thin out my apps. I am curious why there isn't an advanced power menu (shutdown, reboot, recovery, hot boot).
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
You on Cromi yet? 4.7 certanly does, power menu looks like this
power off
restart
-reboot
-hot boot
-bootloader
-recovery
airplane mode
So I've downloaded all my apps and mods for my stock rooted Nexus 5(running android 4.4), how could I get and android 4.4.1 without unrooting?
Sent from my Nexus 5 using XDA Premium 4 mobile app
If you're using the stock kernel and haven't changed anything at all in /system, you can just flash the update in recovery. I'm stock rooted with TWRP, and it flashed just fine for me.
Could you give me a link to the update please!?
Sent from my Nexus 5 using XDA Premium 4 mobile app
roelmmata said:
Could you give me a link to the update please!?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It's on the first page of general.
Did not work for me. Running stock with twrp. It mentioned something about unexpected info in build/prop file. Is it because I'm running art?
Sent from my Nexus 5 using Tapatalk
fytr4lyf223 said:
Did not work for me. Running stock with twrp. It mentioned something about unexpected info in build/prop file. Is it because I'm running art?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
You must have modified your build.prop. Revert it back to stock and it should work.
posted this in another thread but wasn't getting much action, this one seems busier
Just flashed the official 4.4.1 zip file using TWRP onto my phone and rebooted...
Now i'm getting constant errors with every google application.
non-stop popups saying "unfortunately google play store has stopped"
My APN's all deleted themselves as well and now I can't even add any back in, I fill all the information in and I hit save and it doesn't save anything. No service now..
couldn't do a factory reset, button wouldn't respond
anyone else have any problems like this. I've tried wiping my dalvik and cache but that failed. had to wipe data first, then cache worked, then dalvik finally wiped...
I'll set my phone back up and see if it works now, just going through first boot procedures
Mines worked perfectly, no problems and camera loads and captures faster
Sent from my GN5 [D821]
djkorben said:
posted this in another thread but wasn't getting much action, this one seems busier
Just flashed the official 4.4.1 zip file using TWRP onto my phone and rebooted...
Now i'm getting constant errors with every google application.
non-stop popups saying "unfortunately google play store has stopped"
My APN's all deleted themselves as well and now I can't even add any back in, I fill all the information in and I hit save and it doesn't save anything. No service now..
couldn't do a factory reset, button wouldn't respond
anyone else have any problems like this. I've tried wiping my dalvik and cache but that failed. had to wipe data first, then cache worked, then dalvik finally wiped...
I'll set my phone back up and see if it works now, just going through first boot procedures
Click to expand...
Click to collapse
I actually had the same things you mentioned in my stock n5, I wasn't even rooted (just unlocked) and it suddenly did all the things you said. I did all the same you did haha but I had to reflash factory images and it worked again, but I have no idea of what happened.
Sent from my Nexus 5 using Tapatalk
_MetalHead_ said:
You must have modified your build.prop. Revert it back to stock and it should work.
Click to expand...
Click to collapse
I did, but still got the error. But then I pasted in my backup build.prop from ROM toolbox and it worked! Then while in TWRP I reflashed TWRP (TWRPception!). However, when I went to reboot it did not prompt me to root the device. So I'm running 4.4.1 stock kernel with TWRP, but no root. TWRP never prompts to root. Does anyone know of a .zip I can flash to root the N5 via TWRP?
fytr4lyf223 said:
Does anyone know of a .zip I can flash to root the N5 via TWRP?
Click to expand...
Click to collapse
Have a look in the sticky threads, at the top of general. It should be obvious which one
fytr4lyf223 said:
I did, but still got the error. But then I pasted in my backup build.prop from ROM toolbox and it worked! Then while in TWRP I reflashed TWRP (TWRPception!). However, when I went to reboot it did not prompt me to root the device. So I'm running 4.4.1 stock kernel with TWRP, but no root. TWRP never prompts to root. Does anyone know of a .zip I can flash to root the N5 via TWRP?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1538053
I was able to root using CF auto root :cyclops:
Did you maybe delete data for Google Framework in order to get the OTA quicker?
Dan Morrill (an Android engineer) said that that is REALLY not recommended because it can have all sorts of problems with all google apps. Doing that erases your device fingerprint used for push notifications, device identification etc. The playstore was definitely affected by this as well.
Source: http://www.reddit.com/r/Android/com...ear_data_for_google_service_framework/cdiymrp
I ran the causal root applet on a new SG3 on 4.1.2. Ran root, the unlock script and installed TWRP. Booted into recovery and I got the error for a locked bootloader. I used download mode to get back to the stock rom and then used E-Z unlock to unlock the bootloader. Was able to boot into recovery this time but TWRP read internal and external memory as 0mb, unable to make a backup, and gave a no OS error when went to reboot. I updated TWRP with TWRP manager but the problems are still persistent. Phone boots fine and reboots fine at the moment.
I'm not sure what to do now though. I'm at the point were I don't care if I get stuck with the OTA update but I'm afraid that will brick the phone. I'm not sure what went wrong with TWRP, since this is the second S3 I've rooted.
Any sugestions? I'm afraid to use odin or try anything else since the phone currently works fine. But I'd prefer to not have to sleep in fear it might force the OTA update while I'm asleep and wake up to a bricked phone.
I tried searching, the best I could find is that newer versions of TWRP can't read the memory on a 4.1.2 rom, but the problems were there when I originally started with the recommended version.
Thanks for any help anyone can give.
Try to use cwm or philz and see if you have the same issue.
Sent from my SCH-I535 using Tapatalk 2
Xx
BadUsername said:
Try to use cwm or philz and see if you have the same issue.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Can you install a different custom recovery over one using the causal applet? I was planning on trying to reinstall TWRP but I wasn't sure if I had to do it a certain way like through odin or Using the unified tool kit?
Thanks for the help so far!
Smogon said:
Can you install a different custom recovery over one using the causal applet? I was planning on trying to reinstall TWRP but I wasn't sure if I had to do it a certain way like through odin or Using the unified tool kit?
Thanks for the help so far!
Click to expand...
Click to collapse
No.
Download latest philz touch recovery d2lte zip, then flash it in recovery, then reboot recovery.
Then check and see if you're getting a similar error message.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
No.
Download latest philz touch recovery d2lte zip, then flash it in recovery, then reboot recovery.
Click to expand...
Click to collapse
I can't, recovery doesn't detect my internal or external memory. That's my main issue.
Smogon said:
I can't, recovery doesn't detect my internal or external memory. That's my main issue.
Click to expand...
Click to collapse
OK.
Then download the Odin version and flash through that. Then boot the phone into recovery.
Or download ez recovery, and the latest cwm image file, and flash through that from your rom.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
OK.
Then download the Odin version and flash through that. Then boot the phone into recovery.
Or download ez recovery, and the latest cwm image file, and flash through that from your rom.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I'll try the second option, Thanks!
BadUsername said:
OK.
Or download ez recovery, and the latest cwm image file, and flash through that from your rom.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I tried CWM and the stock recovery through EZ, both gave the same error as TWRP, unable to mount /
I'm really confused as to whats wrong. At this point I don't care if I get stuck with the OTA 4.3, but I don't want to try to update it with the recovery still not reading either my SD cards.
Any Ideas?
Are you sure of your phone model? I believe it puts it on the screen in download mode and also on a sticker under the battery. I'm mostly curious because you mention that this is a new phone with 4.1.2. Are you trying older versions of cwm as well?
Sent from my SCH-I535 using XDA Premium 4 mobile app
Smogon said:
I ran the causal root applet on a new SG3 on 4.1.2. Ran root, the unlock script and installed TWRP. Booted into recovery and I got the error for a locked bootloader. I used download mode to get back to the stock rom and then used E-Z unlock to unlock the bootloader. Was able to boot into recovery this time but TWRP read internal and external memory as 0mb, unable to make a backup, and gave a no OS error when went to reboot. I updated TWRP with TWRP manager but the problems are still persistent. Phone boots fine and reboots fine at the moment.
I'm not sure what to do now though. I'm at the point were I don't care if I get stuck with the OTA update but I'm afraid that will brick the phone. I'm not sure what went wrong with TWRP, since this is the second S3 I've rooted.
Any sugestions? I'm afraid to use odin or try anything else since the phone currently works fine. But I'd prefer to not have to sleep in fear it might force the OTA update while I'm asleep and wake up to a bricked phone.
I tried searching, the best I could find is that newer versions of TWRP can't read the memory on a 4.1.2 rom, but the problems were there when I originally started with the recommended version.
Thanks for any help anyone can give.
Click to expand...
Click to collapse
by any chance did u try to setup dualboot? I have a similar issue where nothing gets mounted and o mb for storage, .only receovery i get to work is cwm. im pretty sure its a partition issue but idk. i tried flashing pit files for my phone but so far the issue remains.
xevildoerxx said:
by any chance did u try to setup dualboot? I have a similar issue where nothing gets mounted and o mb for storage, .only receovery i get to work is cwm. im pretty sure its a partition issue but idk. i tried flashing pit files for my phone but so far the issue remains.
Click to expand...
Click to collapse
No I just used the causal tool.
dpeeps74 said:
Are you sure of your phone model? I believe it puts it on the screen in download mode and also on a sticker under the battery. I'm mostly curious because you mention that this is a new phone with 4.1.2. Are you trying older versions of cwm as well?
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm pretty sure, has all the verizon bloat and logos, also I'm pretty sure the causal applet bricks the international ones. I don't remember the version of twrp that the causal script flashed, but I tried that one, the most recent one, and 2.5 i think from EZ recovery. The stock recovery from EZ has the same issue now though which is what really confuses me. at the moment I have root dissabled and the bootloader is locked and its back with the stock recovery, it still says custom when i reboot the phone though.