Hey I've encountered this issue when my S7 Edge boots up it jumps to twrp but it's stuck on the teamwin logo screen and does not advance to menu.
It occurred when I tried to format the data partition to ext4 via twrp and it stuck there for hours so I rebooted it and now i'm stuck here!
I googled some solutions and few suggested flashing a stock via odin but when i try that it fails, flashing twrp also fails i'm sorta stuck right now.
this post https://forum.xda-developers.com/s7-edge/help/stuck-loading-twrp-t3834144 which is the closest scenario suggested adb flash but i can't seem to uncompress boot.img.lz4 with 7zip zstandard
if you know how or if you guys have fixed this issue before please drop a solution thank you in advance !
Boot to download mode and flash twrp again
kpwnApps said:
Boot to download mode and flash twrp again
Click to expand...
Click to collapse
Thanks for your answer, I have tried this like i mentioned and it does flash with success but when it boots to twrp it's just stuck on the teamwin logo, I have even flashed a newer version and i did notice the version changing in the logo but nothing happens.
EDIT: I ended up flashing a stock rom via odin and somehow it worked this time (I updated the usb drivers & changed the cable)
Dantefesse said:
Thanks for your answer, I have tried this like i mentioned and it does flash with success but when it boots to twrp it's just stuck on the teamwin logo, I have even flashed a newer version and i did notice the version changing in the logo but nothing happens.
EDIT: I ended up flashing a stock rom via odin and somehow it worked this time (I updated the usb drivers & changed the cable)
Click to expand...
Click to collapse
Okay then flash twrp again and in odin select nand erase. Dont worry this doesnt wipe your complete system only userdata
kpwnApps said:
Okay then flash twrp again and in odin select nand erase. Dont worry this doesnt wipe your complete system only userdata
Click to expand...
Click to collapse
doesn't Nand erase everything and you're left with download mode ? and why would I do it if i've managed to fix my previous issue ?
Dantefesse said:
doesn't Nand erase everything and you're left with download mode ? and why would I do it if i've managed to fix my previous issue ?
Click to expand...
Click to collapse
Nand erase all doesnt wip everything. Its a big myth. It is actually erasing userdata partition and if ur issue is fixed never mind
kpwnApps said:
Nand erase all doesnt wip everything. Its a big myth. It is actually erasing userdata partition and if ur issue is fixed never mind
Click to expand...
Click to collapse
nah bro, if his issue is fixed, then he needs to reflash the stock firmware, reflash TWRP, boot into twrp, go into the file manager and delete EVERYTHING on the internal storage.
just to be clear, OP, do NOT do any of that
youdoofus said:
nah bro, if his issue is fixed, then he needs to reflash the stock firmware, reflash TWRP, boot into twrp, go into the file manager and delete EVERYTHING on the internal storage.
just to be clear, OP, do NOT do any of that
Click to expand...
Click to collapse
Yea its just showing you dont understand anything. Erasing userdata partition is enough but yeah you know everything
kpwnApps said:
Yea its just showing you dont understand anything. Erasing userdata partition is enough but yeah you know everything
Click to expand...
Click to collapse
nah dude, just trying to insert some very missing humor here. I see it got a ton of traction with you
Related
"Hi! I'm messaging you in regards to my issue while flashing Cyanogenmod 10. I will try to explain exact details of what happened. First I successfully rooted flash clockwork recovery mod superuser etc. using your amazing step by step videos. I decided to flash CM10. I did the beginning part by opening cmd prompt and doing the boot.img etc. While I was on fastboot mode I noticed you had an option for hboot. I did not have that option so instead I clicked Bootloader, opened into to recovery, and tried vigorously installing cm10 from sd card but it always said it could not open it and aborted it. I panicked and wipe data/cache/dalvik cache. I tried multiple times and I still could not install it. On the bootloader I decided to click Factory Reset. It took me too recovery but now I cannot open my sdcard and this error keeps popping up: "E: Can't mount". Now I am panicking big time because I know this could by a soft brick but I have no idea how to undo everything. Please help! It would be greatly appreciated! ".
This is the message i sent to the person who made the video but I am also posting it here because I was wondering how to undo all of this and fix it. This is his video he does a good job of explaning but I just want to fix this and get it back to normal: http://www.youtube.com/watch?v=elDvcVot7qo
Thanks everyone!
First things first... Don't use clock work use twrp second r u sure that cm10 is for our phone not the int one...third don't factory reset from bootloader you corrupted your sd reformat your sd flash twrp from fastboot go into recovery and drag over a Ron from your comp and flash
omario8484 said:
First things first... Don't use clock work use twrp second r u sure that cm10 is for our phone not the int one...third don't factory reset from bootloader you corrupted your sd reformat your sd flash twrp from fastboot go into recovery and drag over a Ron from your comp and flash
Click to expand...
Click to collapse
This, also note what version your hboot is, 1.14 means you have to flash the boot.img first from fastboot before you can install that .zip fromTWRP
omario8484 said:
First things first... Don't use clock work use twrp second r u sure that cm10 is for our phone not the int one...third don't factory reset from bootloader you corrupted your sd reformat your sd flash twrp from fastboot go into recovery and drag over a Ron from your comp and flash
Click to expand...
Click to collapse
I just found out that there is a version specifically for the AT&T builds. Yeah I did that and corrupted my sdcard and now I'm stuck on how to reformat it. I have to admit I am quite a noob at this but I've been flashing since my old Samsung Captiviate.
Myrder said:
This, also note what version your hboot is, 1.14 means you have to flash the boot.img first from fastboot before you can install that .zip fromTWRP
Click to expand...
Click to collapse
Yes you're right I have to fastboot the boot.img first. I'm just stuck on how to get back because the CM10 I put on my phone was for a different version of the One X and I've corrupted my sd card.
omario8484 said:
First things first... Don't use clock work use twrp second r u sure that cm10 is for our phone not the int one...third don't factory reset from bootloader you corrupted your sd reformat your sd flash twrp from fastboot go into recovery and drag over a Ron from your comp and flash
Click to expand...
Click to collapse
I did exactly as you said and I did reformat SD from windows using TWRP and successfully flashed CM10/GAAPS etc. But my phone is just on a bootloop with the HTC screen popping up and a message saying "This build is for development purposes only. Do not distribute outside of HTC without HTC's written permission. Failure to comply may lead to legal action". Now what lol?
sam10037 said:
I did exactly as you said and I did reformat SD from windows using TWRP and successfully flashed CM10/GAAPS etc. But my phone is just on a bootloop with the HTC screen popping up and a message saying "This build is for development purposes only. Do not distribute outside of HTC without HTC's written permission. Failure to comply may lead to legal action". Now what lol?
Click to expand...
Click to collapse
You'll always see that screen that's our splashy screen after we unlock our bl...but it seems as your forgetting to flash the boot IMG manually through fastboot AFTER you flash the rom
omario8484 said:
You'll always see that screen that's our splashy screen after we unlock our bl...but it seems as your forgetting to flash the boot IMG manually through fastboot AFTER you flash the rom
Click to expand...
Click to collapse
+1. You need to manually flash boot.img via fastboot first, and then flash the CM10 rom w/ GApps. fastboot flash boot boot.img
once you've flashed the boot.img via fastboot (hopefully that'll clear up your bootloop issue). There is an app around called FlashImageGUI for flashing img files (straight from the zip too) so you don't need a computer to flash the boot.img. This is a great timesaver.
stopped at clockwork recovery .....
CheesyNutz said:
stopped at clockwork recovery .....
Click to expand...
Click to collapse
exactly, dude screwed up. time to start from scratch.
I'm trying to flash an update to PAC Rom, but I can't get my phone to reboot to recovery (or even shut down).
When I use the power menu, no matter what I choose, the phone does a hot boot. When I hold power and volume down it will go to bootloader then I can access TWRP, but I can't clear dalvik or cache as it says that it can't mount the partitions. The ROM runs fine however and I can access all my data so the cache can't be corrupt.
What can I do here? Thanks to those who help!
Sounds like somethings wrong with your recovery. Get into the bootloader and reflash TWRP using "fastboot flash recovery FileNameOfTWRP.img"
Chromium said:
Sounds like somethings wrong with your recovery. Get into the bootloader and reflash TWRP using "fastboot flash recovery FileNameOfTWRP.img"
Click to expand...
Click to collapse
Would using flashify work here?
It's been a recurring theme on the PAC forum
Synyster06Gates said:
Would using flashify work here?
It's been a recurring theme on the PAC forum
Click to expand...
Click to collapse
Yea that should work too, but if not, fastboot is the way to go.
EDIT : Very very strange. Flashing TWRP again via Flashify got it to work. It seems something in PAC Rom is corrupting the recovery. I think if I get this all worked out then I'm going to have to go back to DK until it's all worked out. I wish there was another ROMs with all the same features as these two but got updates (whereas DK doesn't any more) and is stable enough to DD (lots of FC with PAC).
EDIT 2: Just tried to reboot into recovery again. After booting teh ROM just for a few minutes the recovery was corrupted. I can't access internal memory from recovery any more, even if I get it to boot. It doesn't make any sense as the ROM has full access to it all.
To be clear, TWRP says Internal Storage - 0
Synyster06Gates said:
EDIT : Very very strange. Flashing TWRP again via Flashify got it to work. It seems something in PAC Rom is corrupting the recovery. I think if I get this all worked out then I'm going to have to go back to DK until it's all worked out. I wish there was another ROMs with all the same features as these two but got updates (whereas DK doesn't any more) and is stable enough to DD (lots of FC with PAC).
EDIT 2: Just tried to reboot into recovery again. After booting teh ROM just for a few minutes the recovery was corrupted. I can't access internal memory from recovery any more, even if I get it to boot. It doesn't make any sense as the ROM has full access to it all.
To be clear, TWRP says Internal Storage - 0
Click to expand...
Click to collapse
Here could be the solution. http://forum.xda-developers.com/showthread.php?t=2513701
Flash the cache.img
if it wont work, will have to flash-all
GUGUITOMTG4 said:
Here could be the solution. http://forum.xda-developers.com/showthread.php?t=2513701
Flash the cache.img
if it wont work, will have to flash-all
Click to expand...
Click to collapse
That worked! Thank you!
I actually used to go around the Q&A forum telling people to do just that when they were having issues with wiping on early TWRP versions. Surprised I didn't think to try it. All back on DK now and hunting for a new ROM. :victory:
Synyster06Gates said:
That worked! Thank you!
I actually used to go around the Q&A forum telling people to do just that when they were having issues with wiping on early TWRP versions. Surprised I didn't think to try it. All back on DK now and hunting for a new ROM. :victory:
Click to expand...
Click to collapse
Sounds like you solved it, but I think you could've also done an adb reboot recovery command. Not sure if that works though since I usually only use fastboot.
Sent from my Nexus 5 using Tapatalk
numel007 said:
Sounds like you solved it, but I think you could've also done an adb reboot recovery command. Not sure if that works though since I usually only use fastboot.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
After flashing teh recovery again, I could get INTO it, but the data was not showing up so I couldn't actually do anything from within TWRP. It read I had 0mb internal storage.
LG D821 16GB after power on continue rebooting with Google logo..
I flashed factory image successfully except image version 5.
any help here?
Make sure you're using the latest adb/fastboot files from the SDK
Have you tried to remove the erase userdata flag and then running it? Or maybe you'll need to flash each image individually as some people are doing.
srkhan said:
LG D821 16GB after power on continue rebooting with Google logo..
I flashed factory image successfully except image version 5.
any help here?
Click to expand...
Click to collapse
I also had the same error last night. Just wipe data/factory reset from stock recovery and reboot.
varuntis1993 said:
I also had the same error last night. Just wipe data/factory reset from stock recovery and reboot.
Click to expand...
Click to collapse
not solved
srkhan said:
not solved
Click to expand...
Click to collapse
Have you done what I said?
srkhan said:
not solved
Click to expand...
Click to collapse
are you trying to flash again? No need to if u are doing that.You have flashed, now go into stock recovery and just wipe and reboot the phone. That did it for me.
Can't say whether its an issue with old fastboot files or not because I have setup my device after flashing 4 times with that error and dont want to flash it again just now. In case it matters I had no issue with flashing flo , but got that error with hammerhead.
Do what @EddyOS says. Maybe that's the issue.
Flashing/Booting up L for the first time takes a lot more time than previous Android versions, as ART pre-compiles everything. Give it time, just let it boot. If you used flash-all, you'll be fine.
varuntis1993 said:
are you trying to flash again? No need to if u are doing that.You have flashed, now go into stock recovery and just wipe and reboot the phone. That did it for me.
Can't say whether its an issue with old fastboot files or not because I have setup my device after flashing 4 times with that error and dont want to flash it again just now. In case it matters I had no issue with flashing flo , but got that error with hammerhead.
Do what @EddyOS says. Maybe that's the issue.
Click to expand...
Click to collapse
recovery and just wipe and reboot the phone. That did not work for me.
beekay201 said:
Flashing/Booting up L for the first time takes a lot more time than previous Android versions, as ART pre-compiles everything. Give it time, just let it boot. If you used flash-all, you'll be fine.
Click to expand...
Click to collapse
i flashed all . but still rebooting after Google logo with a lock sign bottom of the screen.
Hi! I recently installed a cm12 nightly on my nexus 5 and now I can't get rid of it ad return back to stock. I tried using nrt and doing it manually but after everything is finished my device doesn't reboot like it's supposed to, it just stays in fastboot mode and when I manually reboot it it boots into cm again and messages pop up saying that system UI has stopped etc so I can't use the device. I tried using force flash mode in nrt and although it did reboot it rebooted in cm again and the same messages pop up.
Any help is appreciated! Thank you!
Did you restore stock kernel?
.
I thought the google factory image would do that? Do i have to do it manually and if yes how do i do it?
ftsagkris said:
I thought the google factory image would do that? Do i have to do it manually and if yes how do i do it?
Click to expand...
Click to collapse
If you are using WugFreshs NRT you can do this within Advanced Utilities - Fastboot Flash - press Boot (Kernel). Restore stock one and then flash stock image.
You can also try if phone will boot up immediately after you restore kernel. If I remember wright, that is enough.
I should also note that when I try to manually install the factory image manually it successfully installs the bootloader the radio and all the other imgs except the system img. It fails to install that
ftsagkris said:
I should also note that when I try to manually install the factory image manually it successfully installs the bootloader the radio and all the other imgs except the system img. It fails to install that
Click to expand...
Click to collapse
It hapeness somethime, but just try again. It also hapenned to me. So. First select your device with current version of android you are using. Leave NRT to update all necessary files. Restore stock kernel. Flash stock image that you downloaded.
You should be ok.
I tried that. When i asked it to download it manually during hashcheck it said mismatched. So I installed it manually and then tried to factory reset with force flash mode off and it said system img was missing. So I enabled force flash and it said it couldn't load system.img. After that it booted in CM again
ftsagkris said:
I tried that. When i asked it to download it manually during hashcheck it said mismatched. So I installed it manually and then tried to factory reset with force flash mode off and it said system img was missing. So I enabled force flash and it said it couldn't load system.img. After that it booted in CM again
Click to expand...
Click to collapse
Hashcheck of what file?
That happened when I pressed boot(kernel) from advanced option. so it was the hashcheck of boot.img when i asked nrt to automatically download it
ftsagkris said:
That happened when I pressed boot(kernel) from advanced option. so it was the hashcheck of boot.img when i asked nrt to automatically download it
Click to expand...
Click to collapse
Pull boot.img from downloaded factory image and flash it.
zagorteney said:
Pull boot.img from downloaded factory image and flash it.
Click to expand...
Click to collapse
Ok. I have already done that. I tried formatting the device and did everything again. I manually installed everything but when I get to system.img I get an error message saying "cannot load system.img"
I also tried re-downloading the factory image from google's site to make sure that I didn't have any corrupted files but the same problem keeps coming up
ftsagkris said:
Ok. I have already done that. I tried formatting the device and did everything again. I manually installed everything but when I get to system.img I get an error message saying "cannot load system.img"
I also tried re-downloading the factory image from google's site to make sure that I didn't have any corrupted files but the same problem keeps coming up
Click to expand...
Click to collapse
Flash bootloader and radio first. Boot in fastboot. Fastboot flash recovery, boot and system. If this doesn't work I don't know how to help you.
Regards, Zagor
zagorteney said:
Flash bootloader and radio first. Boot in fastboot. Fastboot flash recovery, boot and system. If this doesn't work I don't know how to help you.
Regards, Zagor
Click to expand...
Click to collapse
I have done that several times now and it just won't flash system.img
Thank you very much for your help though.
ftsagkris said:
I have done that several times now and it just won't flash system.img
Thank you very much for your help though.
Click to expand...
Click to collapse
After flashing the bootloader/radio, you need to reboot the bootloader.
This is important.
I will put myself in recovery now.
zagorteney said:
After flashing the bootloader/radio, you need to reboot the bootloader.
Click to expand...
Click to collapse
Thank you. I knew that I have read almost every tutorial I could find online. I just did it on my mac and it worked. I don't know why it would't work on my pc.
Thank you very much for your time though!
ftsagkris said:
Thank you. I knew that I have read almost every tutorial I could find online. I just did it on my mac and it worked. I don't know why it would't work on my pc.
Thank you very much for your time though!
Click to expand...
Click to collapse
No problemo. I didn't do anything, but I really hate that things like that, hapeness to people like you.
I just remembered that I have exactly same situation and resolve it that way. That's why I preffered stock from then on.
Regards, Zagor
I keep getting crashes when trying to flash zips in TWRP. the phone reboots as soon as i start to flash any rom or even the magisk zip. Using the boost version of the J7 perx. latest twrp 3.2.1 any help would be greatly appreciated.
J727P
IsaiahWade said:
I keep getting crashes when trying to flash zips in TWRP. the phone reboots as soon as i start to flash any rom or even the magisk zip. Using the boost version of the J7 perx. latest twrp 3.2.1 any help would be greatly appreciated.
Click to expand...
Click to collapse
OK it's time for you to flash stock firmware threw Odin 3.12.5 an start over !
when you install twrp you have to factory reset first then flash twrp in download mod an boot right into recovery an flash superSU zip or magisk !
peter couniaz said:
OK it's time for you to flash stock firmware threw Odin 3.12.5 an start over !
when you install twrp you have to factory reset first then flash twrp in download mod an boot right into recovery an flash superSU zip or magisk !
Click to expand...
Click to collapse
Okay thanks for the reply!
I realized i was using an old version of odin.. maybe thats why it wasnt completely flashing the firmware before.. it would get to almost a full bar and fail. then i would have to flash BL or twrp to get it to boot again.. got the latest odin and it flashed fully this time.
still waiting on my phone to boot up though idk if its stuck on bootloop or not..
Edit *looks like im stuck in bootloop now* ill try formatting and flashing again
Edit #2: I booted into default recovery and wiped data & cache and the phone booted up just fine we'll see how this goes *fingers crossed* lol
IsaiahWade said:
Okay thanks for the reply!
I realized i was using an old version of odin.. maybe thats why it wasnt completely flashing the firmware before.. it would get to almost a full bar and fail. then i would have to flash BL or twrp to get it to boot again.. got the latest odin and it flashed fully this time.
still waiting on my phone to boot up though idk if its stuck on bootloop or not..
Edit *looks like im stuck in bootloop now* ill try formatting and flashing again
Edit #2: I booted into default recovery and wiped data & cache and the phone booted up just fine we'll see how this goes *fingers crossed* lol
Click to expand...
Click to collapse
Tried it still not working.. i even factory reset before flashing twrp. it still reboots immediately when trying to flash anything
Step 2
I presume you're flashing from an SD card. Please backup its data and format it.
Then re-download one of the zips and test flash in TWRP.
dodo2244 said:
Step 2
I presume you're flashing from an SD card. Please backup its data and format it.
Then re-download one of the zips and test flash in TWRP.
Click to expand...
Click to collapse
Correct. Thanks ill try that.
is it normal that my carrier switches to sprint when i flash the stock rom? when i flash CSC it switches back to boost
IsaiahWade said:
Correct. Thanks ill try that.
is it normal that my carrier switches to sprint when i flash the stock rom? when i flash CSC it switches back to boost
Click to expand...
Click to collapse
The memory card thing worked! i forgot i had formatted it as adoptable storage before.
after formatting it actually let me flash the zip this time
only thing is i got an error right at the very end
Unable to repack boot image!
-unmounting partitions
Updater process ended with ERROR: 1
Error installing zip file '/sdcard/Magisk-v16.0.zip
updating partition details
. . . done
J727P
IsaiahWade said:
Tried it still not working.. i even factory reset before flashing twrp. it still reboots immediately when trying to flash anything
Click to expand...
Click to collapse
Ok do the firmware thing then factory reset in the stock recovery ! Then flash twrp in Odin with auto reboot unchecked in options ! Then pull an replace battery ! Then boot right into twrp an flash superSU SR5 2.8.2 zip an reboot ! Or you can boot twrp an Rom instead !
Glad to be of help. Peter's tricks should solve your final hurdles.
Sent from my SM-J700F using Tapatalk