Related
Hello all,
2 days ago when on vacation i decided to temper around with my OnePlus one that i recently bought (have bought the Chinese version but it was already rooted and had cyanoged mod on it)
All was fine until i decided to flash Paranoid Android and i posted a question here, about how to bypass the always apearing CyanogenMod Simple Recovery tool.
After trying what everyone suggested and not getting result i had 1 last thing that someone suggested:
http://forum.xda-developers.com/showthread.php?p=54717885
If you still have not fixed this issue, for some reason when I was flashing my recovery it would NOT work for the life of me until I changed the name of the custom recovery file to 'recovery.img'. Everytime I flash (for example) openrecovery-twrp-blah-bacon.img it would say success, but it kept rebooting into CM fastboot mode.
Click to expand...
Click to collapse
I misunderstood and i renamed the .zip file from paranoid sources into recovery.img and flash (Kernel) it via some app from play store, i thin it was TRWL
Now my phone is stuck into loading faze and the only thing i can do is enter Fastboot mode.
I tried to do a:
fastboot erase cache
But it did not work, its still stuck in loading and will not do anything.
Could you help me out ? I have a really bad feeling i just lost my phone due to hurrying and not having a pc around to read more.
You can try to fastboot flash recovery(original or proper one that works) but I don't know the exact commands.
In the first case where your recovery would not switch from CM to TWRP/CWR was because you had "Update CM Recovery" enabled in Developer Options. If you ticked that off, then it would have replaced CM Recovery. Its confusing yeah.
So wait... you renamed the .zip to a .img? Thats not good. But at least you can enter fastboot mode so thats at least something. Is your bootloader still unlocked? Are you able to boot into recovery mode? Try fastboot boot <name-of-recovery-for-twrp>.img and see if you can get into recovery.
If you can then perform a wipe and then enable adb sideload within TWRP and then type,
adb sideload <name-of-zip>.zip and then after its done sideloading, reboot
Thanks for the answer.
I managed last night out of 10 flash resets to get the Custom Recovery Tool to booth up.
I was about to give up when i saw it boot and i immediately flashed the CM .zip i had on the phone from last time.
I even managed to get Paranoid android to flash and im very happy.
Thanks for the help
vidockq said:
Thanks for the answer.
I managed last night out of 10 flash resets to get the Custom Recovery Tool to booth up.
I was about to give up when i saw it boot and i immediately flashed the CM .zip i had on the phone from last time.
I even managed to get Paranoid android to flash and im very happy.
Thanks for the help
Click to expand...
Click to collapse
I'd appreciate it if we helped give us a thanks.
Sent from my One using Tapatalk
Today I wanted to flash a CM12 lollipop ROM
I unlocked the bootloader with succes, adb commands said that the recovery .img was flashed okay!,
So i got the following issue,
My oneplus one won't boot in to recovery, or is stuck at the Oneplus logo, or the 1+ logo just disappears and the screen goes crazy with green and blue lines... and i see weird things on screen. a normal boot and fastboot is fine everything is just ok, but not recovery,
I tried TWRP, PHILZ TOUCH,CWM, even to stock CM recovery doesn't flash anymore
i did many tutorials and followed step by step im sure thats not the problem.
I tried with the oneplus one toolbox and command window but nothing
Need help!
DaiMinzz said:
Today I wanted to flash a CM12 lollipop ROM
I unlocked the bootloader with succes, adb commands said that the recovery .img was flashed okay!,
So i got the following issue,
My oneplus one won't boot in to recovery, or is stuck at the Oneplus logo, or the 1+ logo just disappears and the screen goes crazy with green and blue lines... and i see weird things on screen. a normal boot and fastboot is fine everything is just ok, but not recovery,
I tried TWRP, PHILZ TOUCH,CWM, even to stock CM recovery doesn't flash anymore
i did many tutorials and followed step by step im sure thats not the problem.
I tried with the oneplus one toolbox and command window but nothing
Need help!
Click to expand...
Click to collapse
Hi, maybe your recovery images are corrupt. Had that once, thought I was going crazy. Redownload, compare md5 sums (I know it sucks...), perhaps use a different browser to download, then flash again. Good luck!
stevekind said:
Hi, maybe your recovery images are corrupt. Had that once, thought I was going crazy. Redownload, compare md5 sums (I know it sucks...), perhaps use a different browser to download, then flash again. Good luck!
Click to expand...
Click to collapse
Still the same problem didn't work
Im sure everthing on the pc went ok, but my Oneplus has recovery bug
I was trying to fix my girlfriends nexus 5 that was doing the restart loop after an update. Everything seemed to go fine. Unlocked the bootloader, etc. Flashed the newest rom (6.0.1 (MMB29S) ce1d670f61061c3902f3997510ea55d7 6bfcdfa4f4840898e5d76fa044f5e6a0f71343bf) and then something obviously went wrong (not quite sure, dont think i touched anything) and it's now stuck in a different kind of loop that only loops while it's plugged in. Ive uploaded a video to youtube, but since im a new user i cant actually link it properly yet. Hopefully this wont annoy any mods, I promise it's not spam. youtube . be / yNSoiTPnGZw
Is there any way to get it to stay on for more than a couple seconds to retry the flashing?
Any help is appreciated.
atomkrieg said:
I was trying to fix my girlfriends nexus 5 that was doing the restart loop after an update. Everything seemed to go fine. Unlocked the bootloader, etc. Flashed the newest rom (6.0.1 (MMB29S) ce1d670f61061c3902f3997510ea55d7 6bfcdfa4f4840898e5d76fa044f5e6a0f71343bf) and then something obviously went wrong (not quite sure, dont think i touched anything) and it's now stuck in a different kind of loop that only loops while it's plugged in. Ive uploaded a video to youtube, but since im a new user i cant actually link it properly yet. Hopefully this wont annoy any mods, I promise it's not spam. youtube . be / yNSoiTPnGZw
Is there any way to get it to stay on for more than a couple seconds to retry the flashing?
Any help is appreciated.
Click to expand...
Click to collapse
What was your flashing procedure, did u is a toolkit or do it manually, can u get it into bootloader or recovery? What files did u is for update and where did u get them?
Sent from my XT1526 using Tapatalk
soupysoup said:
What was your flashing procedure, did u is a toolkit or do it manually, can u get it into bootloader or recovery? What files did u is for update and where did u get them?
Sent from my XT1526 using Tapatalk
Click to expand...
Click to collapse
First i followed the guide here on xda to unlock the bootloader(guide-nexus-5-how-to-unlock-bootloader-t2507905), installed twrp, which went fine. Then i realized that i couldnt (or didnt realize how to via command line) to copy the stock rom and install it via twrp, so then i followed this guide here on xda (tutorial-how-to-flash-factory-image-t2513701) with the factory img (6.01 hammerhead), got to this point in the guide: ★After everything finished, select "Recovery" using the volume buttons. then it stalled out,turned off and now just cycles on and offf through the google logo with the lock picture or if i hold down the volume button it will go into the bootloader briefly then restart, rinse repeat.
atomkrieg said:
First i followed the guide here on xda to unlock the bootloader(guide-nexus-5-how-to-unlock-bootloader-t2507905), installed twrp, which went fine. Then i realized that i couldnt (or didnt realize how to via command line) to copy the stock rom and install it via twrp, so then i followed this guide here on xda (tutorial-how-to-flash-factory-image-t2513701) with the factory img (6.01 hammerhead), got to this point in the guide: ★After everything finished, select "Recovery" using the volume buttons. then it stalled out,turned off and now just cycles on and offf through the google logo with the lock picture or if i hold down the volume button it will go into the bootloader briefly then restart, rinse repeat.
Click to expand...
Click to collapse
Have u tried messing with the power button, there are a lot of issues on the nexus 5 with the power button causing loops, simply from getting stuck, try playing with the power button a little and see of that helps, it might just need to be replaced
Wait, did u flash the factory img with twrp, or did u flash it using fastboot?
Sent from my XT1526 using Tapatalk
soupysoup said:
Have u tried messing with the power button, there are a lot of issues on the nexus 5 with the power button causing loops, simply from getting stuck, try playing with the power button a little and see of that helps, it might just need to be replaced
Wait, did u flash the factory img with twrp, or did u flash it using fastboot?
Sent from my XT1526 using Tapatalk
Click to expand...
Click to collapse
in the end fastboot, since i coulndt see how i could copy the img over to install via twrp
im pretty sure the button is fine, since it was cycling from the ota update install, then was working fine unlocking the bootloader, but after the flash, it crapped the bed.
Different problem
I had a problem where the google logo keeps on booting up with a slight vibration.This started to happen when my was dropped.I initially thought that was a software issue and thought of installing new ROM's but eventually my device was not detected :crying:
So i took it to repair shop near my house and they said it would cost 2500
I did some google research and found the reason was due to the power button being stucked during the fall.I got that repaired and my device is good to go
siddhu007 said:
I had a problem where the google logo keeps on booting up with a slight vibration.This started to happen when my was dropped.I initially thought that was a software issue and thought of installing new ROM's but eventually my device was not detected :crying:
So i took it to repair shop near my house and they said it would cost 2500
I did some google research and found the reason was due to the power button being stucked during the fall.I got that repaired and my device is good to go
Click to expand...
Click to collapse
ok, took it into a shop, got the power button fixed. It must have been on the way out because literally one minute it worked and the second it didnt. now i think ive got it narrowed down. it's saying it's unable to mount /persist. ive tried the various fixes:
e2fsck/dev/block/platform/msm_sdcc.1/by-name/persist
and
make_ext4fs/dev/block/platform/msm_sdcc.1/by-name/persist
but all i get is a not found error. not sure what to do from here on.
success!! i ended up stumbling on a bit how to restore the persist partition i didnt try. got a custom rom installs and everything works. thanks to everyone who tried to help!!
stuck in bootloop while flashing cataclysm rom
i tried to flash cataclysm rom in my n5..i unlock bootloader, flash custom recovery using TWRP and flash cataclysm rom following the instructions in this thread http://forum.xda-developers.com/goo...s-5-how-to-unlock-bootloader-t2507905...after that it was stuck in bootloop...i tried to open recovery but it wont open anymore it will only go back to loop....how can open the recovery? is it safe to flash CWM recovery?..tnx in advance..
When it was stuck in the loop, I had to hold vol up and down with the power button (wait a few secs until it was completely off) then reboot holding down + power till it opened the bootloader. if that doesnt work, try reflashing the bootloader via fastboot. I only found out i couldnt mount the persist partition by looking at the terminal window in twrp after trying to install a rom which kept it in the boot loop. I then used the cmd: make_ext4fs /dev/block/platform/msm_sdcc.1/by-name/persist to rebuild it.
jpau11 said:
i tried to flash cataclysm rom in my n5..i unlock bootloader, flash custom recovery using TWRP and flash cataclysm rom following the instructions in this thread http://forum.xda-developers.com/goo...s-5-how-to-unlock-bootloader-t2507905...after that it was stuck in bootloop...i tried to open recovery but it wont open anymore it will only go back to loop....how can open the recovery? is it safe to flash CWM recovery?..tnx in advance..
Click to expand...
Click to collapse
After flashing TWRP, use the volume and power button to select recovery. Once in TWRP, wipe cache, data, reboot.
audit13 said:
After flashing TWRP, use the volume and power button to select recovery. Once in TWRP, wipe cache, data, reboot.
Click to expand...
Click to collapse
problems solved!!i flashed TWRP again and it it already to the recovery so i reflashed the cataclysm rom and it worked...my n5 is now working..tnx guys!
jpau11 said:
problems solved!!i flashed TWRP again and it it already to the recovery so i reflashed the cataclysm rom and it worked...my n5 is now working..tnx guys!
Click to expand...
Click to collapse
Great to hear it. Congratulations:good:
does anyone know how to fix this issue im having.i was on android 6.0 when trying to boot into twrp recovery would only have a black screen,only once in a blue moon it will boot into twrp regular.i updated to 7.0 thought it might fix the issue but it is the same .ive tried all the twrp versions through adb,but when booting into twrp just presented a black screen,ive tried factory reset,reflash firmware,still the same.The only way to get to twrp normal is to adb (fastboot/boot/twrp.img/,on my computer
You're doing MUCH better than i am. After loading twrp & making a backup, it appears the bootloader corupted when i tested it with the restore. Now, if i try & reboot, all it does is vibrate. If it's pluged in while rebooting, it'll vibrate & the red led blinks. In other words, hard bricked. I got 2 disney tickets offered to anyone who can un-hardbrick it. I've un bricked several Samsung's, but the Zp3ultra has me stumped. If i were you, i'd try reloading the original OS.
hillg001 said:
You're doing MUCH better than i am. After loading twrp & making a backup, it appears the bootloader corupted when i tested it with the restore. Now, if i try & reboot, all it does is vibrate. If it's pluged in while rebooting, it'll vibrate & the red led blinks. In other words, hard bricked. I got 2 disney tickets offered to anyone who can un-hardbrick it. I've un bricked several Samsung's, but the Zp3ultra has me stumped. If i were you, i'd try reloading the original OS.
Click to expand...
Click to collapse
Hey funny you should say that. I'm actually on my second Asus 3 ultra. The same thing happened to my first one got stuck during a firmware update, or corrupted firmware zip.,now the phone won't boot to twrp or bootloader, just vibrates like yours. If I plug the charging cord in vibrates then just get those red led notification light blinks,computer won't even recognize the device so can't flash the bootloader back to the phone to fix, so I guess it's hard bricked paperweight. I only had it for about a week before the brick, had to buy a new one. The thing that's funny to me the first one would boot to twrp no problem, now this new one seems to boot to twrp but just presented a black screen, it's in twrp recovery because you can feel the vibrations for the buttons, just can't see the screen. I would love to be able to fix the bricked one it's brand new, and can't send for warranty because I'm in the US, sucks.
If you have the address for the foreign country's location of manufacturing, you can send it in for repairs. That's what we are working on doing. The horrible thing is, after reading about stories of other customers, Asus really rakes you over the coals price wise for the repair, & then does similarly for return shipping. So we are still trying to find a way around the high shipping prices, at least.
.
gubbilo144 said:
does anyone know how to fix this issue im having.i was on android 6.0 when trying to boot into twrp recovery would only have a black screen,only once in a blue moon it will boot into twrp regular.i updated to 7.0 thought it might fix the issue but it is the same .ive tried all the twrp versions through adb,but when booting into twrp just presented a black screen,ive tried factory reset,reflash firmware,still the same.The only way to get to twrp normal is to adb (fastboot/boot/twrp.img/,on my computer
Click to expand...
Click to collapse
What stock keeping unit (SKU) is your phone? WW, TW, CN, or JP?
What version of TWRP did you flash?
hillg001 said:
You're doing MUCH better than i am. After loading twrp & making a backup, it appears the bootloader corupted when i tested it with the restore. Now, if i try & reboot, all it does is vibrate. If it's pluged in while rebooting, it'll vibrate & the red led blinks. In other words, hard bricked. I got 2 disney tickets offered to anyone who can un-hardbrick it. I've un bricked several Samsung's, but the Zp3ultra has me stumped. If i were you, i'd try reloading the original OS.
Click to expand...
Click to collapse
i got the same problem when i use TWRP to install the oldest rom from asus website UL-ASUS_A001-WW-13.6.6.17-user.zip, the installation completed but i got black screen the same signs like you did, i offer 50 Euros for those who could help me unbrick my zenfone ultra
thanks a lot in advance!!!
Cordially
CHUNG
qbchung said:
i got the same problem when i use TWRP to install the oldest rom from asus website UL-ASUS_A001-WW-13.6.6.17-user.zip, the installation completed but i got black screen the same signs like you did, i offer 50 Euros for those who could help me unbrick my zenfone ultra
thanks a lot in advance!!!
Cordially
CHUNG
Click to expand...
Click to collapse
i think the mistake people may be making is flashing stock rom through twrp
twrp only for supersu zip and other things imo
stock rom just flash through the stock recovery apply update from sd (microsd card) need to make sure the recovery and rom match
can you get to stock recovery? also charge it first to a good 80 to 90 if not 100 percent
gubbilo144 said:
does anyone know how to fix this issue im having.i was on android 6.0 when trying to boot into twrp recovery would only have a black screen,only once in a blue moon it will boot into twrp regular.i updated to 7.0 thought it might fix the issue but it is the same .ive tried all the twrp versions through adb,but when booting into twrp just presented a black screen,ive tried factory reset,reflash firmware,still the same.The only way to get to twrp normal is to adb (fastboot/boot/twrp.img/,on my computer
Click to expand...
Click to collapse
After you get that black screen, just press once the power button to close and then press it again to open, just like you do when you normally close and open the screen. You will see after that the twrp interface.
qbchung said:
i got the same problem when i use TWRP to install the oldest rom from asus website UL-ASUS_A001-WW-13.6.6.17-user.zip, the installation completed but i got black screen the same signs like you did, i offer 50 Euros for those who could help me unbrick my zenfone ultra
thanks a lot in advance!!!
Cordially
CHUNG
Click to expand...
Click to collapse
read your post again...noticed...
one thing-if you were on ww-14 i.e. android nougat then cannot simply flash the ww 13 marshmallow as I believe the bootloader is different - think that is why the flash did not work (know this from other zenfone forums where you cannot simply downgrade by flashing a previous android level rom) if it was not a case of downgrading then maybe because of using twrp for stock rom instead of the update process using stock recovery
I tried to flash ww 13 when on ww 14 through stock recovery and it was giving me an error (saying version is not ww which was not the case anyway)-found out through other forums that it is because one cannot downgrade in that manner - therefore I think cause of flash error is the bootloader version. For downgrading one needs the raw file. I found raw file for our ultra (WW13 level) at a Vietnamese site and the flashing tool but have not tried it (no reason to) but am keeping it just in case.
you can get stock recovery from here (note the ww 13 or ww 14 types pick the right one)
https://mega.nz/#F!9tEj2azZ!QKmvc-VJZR1Iqk6H7alQnQ
flash it through fastboot
need to have fastboot drivers installed
https://developer.android.com/studio/releases/platform-tools
or
https://androidmtk.com/download-minimal-adb-and-fastboot-tool
make sure path variable has fastboot folder in it in environment variables of computer
preferably have recovery image in that folder too so you don't have to type some long path names
power off
volume up press and hold then press power
get to bootloader fastboot mode
connect by usb
open command prompt window in folder where fastboot installed
check fastboot devices to verify phone is seen
filename.img = filename of the twrp.img
twrp flash recovery filename.img
if successful then
twrp boot filename.img
may have to press power or volume up to get to the screen
while in stock recovery better to do factory reset too before update
then apply update from sd card
btw I have successfully used the twrp march version 3.2.1 (also at the above mega link) with the latest stock ww 14 (from jan 8 2018) backed up restored successfully, rooted, and have xposed as well
a note on twrp restore if ever having to (just don't check system image restore in twrp when restoring)
trying to do miui port
Can anyone help me???My device isn't opening after twrp flashing.when I reboot I see dark screen,not twrp recovery... please somebody help me,fast.....
Same problem with my iball tablet
Even flashing stock recovery doesn't give me recovery back i have also tried philz recovery but no luck i need help too
I unlocked the bootloader on my phone, then flashed twrp. I rebooted to twrp and installed boot.img, TWRPWorkingInstaller.zip, TWRP-BLUE-FIX.zip, and Root.zip. Rebooting worked fine, but I saw that there was a newer twrp (twrp-3.2.1-3-wOOSkernel.img, so I tried installing it from twrp. The problem is that I installed it to the system image partition. After that, everything got wonky, unsurprisingly. Now, if I try to boot to twrp, it loads and I get to the first menu, but I cannot interact with it at all. Then the screen goes black and the led lights up blue. It doesn't respond to anything except shutting it down. I can hold the power button down to power off, but it reboots instead to a black screen with the blue LED. I can also boot into the bootloader. I can reflash twrp. When I restart to recovery then, I get the screen asking if I want to keep the system files locked or swipe to unlock it. The device seems to work fine for about 5 seconds from the time I get to the first twrp menu, then it doesn't respond. About 5-8 seconds later, the screen goes black and the blue led comes on. I also cannot power-off the device. If I try, it reboots.
Is there anything I can do to recover from this? I've got the stock recovery files (OnePlus6Oxygen_22_OTA_009_all_1805172226_f7d1518e0e704ca3.zip), but I can't copy them to the device because it won't boot to the OS.
Yippee38 said:
I unlocked the bootloader on my phone, then flashed twrp. I rebooted to twrp and installed boot.img, TWRPWorkingInstaller.zip, TWRP-BLUE-FIX.zip, and Root.zip. Rebooting worked fine, but I saw that there was a newer twrp (twrp-3.2.1-3-wOOSkernel.img, so I tried installing it from twrp. The problem is that I installed it to the system image partition. After that, everything got wonky, unsurprisingly. Now, if I try to boot to twrp, it loads and I get to the first menu, but I cannot interact with it at all. Then the screen goes black and the led lights up blue. It doesn't respond to anything except shutting it down. I can hold the power button down to power off, but it reboots instead to a black screen with the blue LED. I can also boot into the bootloader. I can reflash twrp. When I restart to recovery then, I get the screen asking if I want to keep the system files locked or swipe to unlock it. The device seems to work fine for about 5 seconds from the time I get to the first twrp menu, then it doesn't respond. About 5-8 seconds later, the screen goes black and the blue led comes on. I also cannot power-off the device. If I try, it reboots.
Is there anything I can do to recover from this? I've got the stock recovery files (OnePlus6Oxygen_22_OTA_009_all_1805172226_f7d1518e0e704ca3.zip), but I can't copy them to the device because it won't boot to the OS.
Click to expand...
Click to collapse
Do you have a TWRP backup from when your phone worked on an external drive?
Can you access fastboot? Just use the fastboot ROM files to reflash the OS. Or if that doesn't work try the unbrick tool.
Yeah. I can use fastboot. However, I wasn't able to get to ROM to flash. I'm not sure if I'm using the correct parameters in the command. I googled, but all I came up with was flashing custom ROMs. Where can I find the unbrick tool?
NM. Found the unbrick tool. I may try it. I'll let you know how it works.
Thanks for your help @NateDev!. The Unbrick Tool helped me fix it.
Yippee38 said:
Thanks for your help @NateDev!. The Unbrick Tool helped me fix it.
Click to expand...
Click to collapse
Glad you got it solved