My One has been acting up lately. It started out that I couldn't turn off WiFi. I would turn it off but it would turn itself back on shortly thereafter. It has nothing to do with WiFi optimization or anything like that...I've fiddled with all those settings. Anyway, I updated to 38R thinking it might fix things, but no such luck. So I fire up titanium backup in preparation for a full wipe and find out that my device is no longer rooted. On top of that, TWRP is gone as well. No big deal, reflash TWRP and re-root. Nope. ADB says that TWRP flashes successfully, but when I boot into recovery I get the standard Cyanogen recovery instead of TWRP. Any thoughts?
Have you tried flashing stock and starting from scratch?
Did you remember to uncheck the option for updating fastboot with system update as well?
Sent from my Nexus 7 using XDA Premium HD app
Admeisterz said:
Have you tried flashing stock and starting from scratch?
Did you remember to uncheck the option for updating fastboot with system update as well?
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Unfortunately I missed the fastboot update bit. Did I **** myself with that?
If you could access CWM do a factory reset, and hopefully that clears up your problems, if not go back to stock via: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
the only reason why i could think that it'd say flashing is successful is it's flashing to the wrong partition (which doesn't make any sense), or the bootloaders locked, which it isn't since from your post it says you had TWRP installed, but try going back to stock fully via fastboot, then installing twrp and such.
Related
Okay so a little while back my phone had a huge freak out and I had to restore everything to stock in order for it to even turn on anymore. Well I was trying to reroot it the other day and when I installed twrp, my phone would show the twrp screen and then boot loop over and over to that screen while I was trying to get into the recovery. Does anyone know why this could be happening or even better. I fix for my problem.
I'd try to re-flash twrp. Then from twrp, wipe everything multiple times and factory reset. But it could be something with the phone is bad and not repairable
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Did you try restoring to stock using Odin and official Samsung update .tar? And also restoring to stock recovery beforehand? Try that, run the Rom for bit and see if it has any hiccups. If so, I'd say hardware issue. If not, try flashing twrp .tar file from sticky thread on how to root.
Sent from my SGH-I727 using xda premium
I have Verizons S3. I recently rooted and unlocked the bootloader and have TWRP recovery. I was on 4.1 JB. I made a Nandroid Backup of System and Data. I then flashed the CM10.1 Monthly ROM, and all seemed to be working fine. However, I was having some issues with my app backups and the weird "emulated" directory structure. So I decided to go back to my Nandroid Backup and start over.
I went into TWRP, did a factory reset, cleared System Data, cache/dvalick cache, then I restored the Nandroid Backup (system and data). TWRP said it was successful and asked to reboot. When I did, the Samsung logo flashes, and then the screen stays black. I tried going back into recovery, but it won't let me. I can get to download though.
I think I'm going to have to use Odin to reflash a ROM as I can't get into recovery, right? But I'm also trying to understand what I did wrong. Did I forget a step? Did it have something to do with differences between 4.1 and 4.2? I'm new to this, and have searched the forums but can't find anything that answers my questions specifically. I appreciate the help.
anacree said:
I have Verizons S3. I recently rooted and unlocked the bootloader and have TWRP recovery. I was on 4.1 JB. I made a Nandroid Backup of System and Data. I then flashed the CM10.1 Monthly ROM, and all seemed to be working fine. However, I was having some issues with my app backups and the weird "emulated" directory structure. So I decided to go back to my Nandroid Backup and start over.
I went into TWRP, did a factory reset, cleared System Data, cache/dvalick cache, then I restored the Nandroid Backup (system and data). TWRP said it was successful and asked to reboot. When I did, the Samsung logo flashes, and then the screen stays black. I tried going back into recovery, but it won't let me. I can get to download though.
I think I'm going to have to use Odin to reflash a ROM as I can't get into recovery, right? But I'm also trying to understand what I did wrong. Did I forget a step? Did it have something to do with differences between 4.1 and 4.2? I'm new to this, and have searched the forums but can't find anything that answers my questions specifically. I appreciate the help.
Click to expand...
Click to collapse
You're supposed to backup "boot.img" as well. I'm pretty sure boot.img is the kernel which you failed to backup. The phone won't boot into your nandroid because the kernel wasn't restored as well. In TWRP: system, data, and boot are all supposed to be backed up simultaneously if you want to restore the entire nandroid. Odin flash and make sure to do a proper nandroid with all three that I listed.
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
You're supposed to backup "boot.img" as well. I'm pretty sure boot.img is the kernel which you failed to backup. The phone won't boot into your nandroid because the kernel wasn't restored as well. In TWRP: system, data, and boot are all supposed to be backed up simultaneously if you want to restore the entire nandroid. Odin flash and make sure to do a proper nandroid with all three that I listed.
Click to expand...
Click to collapse
Ah, perhaps that "boot" checkbox wasn't check. =P So basically the CM10.1 boot.img is still there, but now the wrong ROM is there so it won't boot? Can I just flash the boot.img with Odin now, or will I need to do a full ROM flash?
anacree said:
Ah, perhaps that "boot" checkbox wasn't check. =P So basically the CM10.1 boot.img is still there, but now the wrong ROM is there so it won't boot? Can I just flash the boot.img with Odin now, or will I need to do a full ROM flash?
Click to expand...
Click to collapse
Flash nandroid and then try to flash a kernel. Might work Idk. Worth a shot.
sent telepathically
---------- Post added at 07:14 PM ---------- Previous post was at 07:13 PM ----------
jdub251 said:
Flash nandroid and then try to flash a kernel. Might work Idk. Worth a shot.
sent telepathically
Click to expand...
Click to collapse
Edit. Are you still not able to get into recovery? Sorry missed that in your post.
sent telepathically
jdub251 said:
Are you still not able to get into recovery? Sorry missed that in your post.
Click to expand...
Click to collapse
No, when I do the button combo for recovery, the word "Samsung" flashes, then "Galaxy S3" logo, but after that nothing...just blank screen. I was on stock Verizon s3 before this, so I guess I need to put that kernel back on the phone? Is the kernel the same as the bootloader? Can I use the unlocked bootloader referenced in this post: http://forum.xda-developers.com/showthread.php?t=1974114?
So, I tried using Odin to flash back the stock JB 4.1.1 kernel, which should have matched my Nandroid backup, but then I got an unlocked padlock on my splash screen and then the yellow triangle. blah. so i flashed a stock no wipe rom and that got me back into touchwiz, but I cant get into recovery no matter what i do. And I still have the padlock. I think I may need to do a stock full wipe rom?
anacree said:
So, I tried using Odin to flash back the stock JB 4.1.1 kernel, which should have matched my Nandroid backup, but then I got an unlocked padlock on my splash screen and then the yellow triangle. blah. so i flashed a stock no wipe rom and that got me back into touchwiz, but I cant get into recovery no matter what i do. And I still have the padlock. I think I may need to do a stock full wipe rom?
Click to expand...
Click to collapse
If you flashed a fully stock rom then you need to root, unlock, and install your custom recovery again.
Sent from my SCH-I535 using xda app-developers app
Ok, so I finally got time to try this again after flashing back to (what I thought) was stock Jelly Bean 4.1. I was following the directions here in this thread: http://forum.xda-developers.com/showthread.php?t=2046439
I get the VRALEC bootchain fine, phone reboots and all seems well. I got to flash TWRP 2.4, do a batter pull, and when I try to boot into recovery mode suddenly there is the Samsung splash screen with an unlocked padlock on it. Then the screen goes black and doesn't go into recovery. When I release the buttons, the phone then boots into the OS. I can still get to the download mode, but for some reason I can't get into a custom recovery. Any help on this? Please?
I used this file to wipe my phone back to stock JB: COMBINATION_I535VRBLK3_I535VZWBLK3_381038_REV09_user_low_ship.tar.md5
Thanks for the assistance. =)
Redo step three like the directions state.
Edit : In that thread, some folks even suggest waiting 5-10 mins after its successfully flashed before booting into recovery.
Sent from my SCH-I535 using xda app-developers app
Forgot to followup here, but I got it working. I left my phone plugged in after flashing the recovery for like 15 minutes. I also released the power button on trying to boot into recovery once the Samsung logo appeared. I finally got into recovery and was so happy. Thanks for the help!
Running mastamoon's unofficial CM 10.1. =)
anacree said:
Running mastamoon's unofficial CM 10.1. =)
Click to expand...
Click to collapse
Perfect! Glad you've got it all working properly!
Sent from my SCH-I535 using xda app-developers app
I originally was using TWRP the latest version, and every time I tried to make a backup, it would say error too many open files, data lost found and then error tarring split files... so I tried flashing CWM and when trying to make a backup it said error while making a backup image of /data. I really don't know what to do, as now I'm basically forced to stay on the rom I'm on, and I want to try out something new. Any help?
Bump.
So you are rooted and bootloader is unlocked correct. Are you sure you have the latest twrp. You could get goo manager app and get latest through there by going into settings and flash recovery. Then when in recovery don't select anything extra when you go to backup. Should work fine if your rooted and bootloader is unlocked. Remember if you took Verizon latest ota them your bootloader would be locked again, just putting that out there.
Sent from my SCH-I605 using xda premium
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
ive tried twrp and cwm, and both seem to have extremely bad problems on my phone. i haven't seen others have problem with their phones but mine has gone full retard. with twrp, wiping takes a super really long time and most of the time it does not wipe anything even though its says completed. it cant flash any rom either. it just immediately says failed. so i tried cwm thinking it was a twrp thing, but ive ran into the same issues. i flashed a rom thinking it had wiped (it said it had wiped) but id didnt, it just dirty flashed the rom over stock. can someone suggest what can be going wrong? :crying::crying:
Have you tried using the newest twrp?
Sent from my Nexus 5 using XDA Premium 4 mobile app
JCreazy said:
Have you tried using the newest twrp?
i have a mac and no access to a pc, so installing it has been manually through adb commands has been a real headache for me. i first installed it through a tool someone made in the forums for mac but i don't think they have updated it ever since the first release. then i tried using goo manager but it appears the servers are still down.ccc
Sent from my Nexus 5 using XDA Premium 4 mobile app[/QUmasmasclmlklcmxzklckxlzmcxlkmczklmczlkxcmklxzmcOTE]
Click to expand...
Click to collapse
In TWRP you can check -rom option in Settings menu to wipe the partitions instead of formatting them. The process will take less time.
To flash a rom try to boot into the bootloader then select Recovery mode and flash.
If you are rooted you can install TWRP via Flashify app or even with Terminal commands.