My phone and recovery H60-L04 B805, TWRP.
While I was rooting phone via multitool I bricked it.
It restarts over and over.
Could anybody help me?
I can access fastboot, twrp.
Sorry for my English
I don't know how but I fix it. Installed another version of SuperSU and cleared dalvik and normal cache phone started but it took very long time.
kmlnvm said:
I don't know how but I fix it. Installed another version of SuperSU and cleared dalvik and normal cache phone started but it took very long time.
Click to expand...
Click to collapse
Can you post which version of SuperSU did you flash?
First I tried 2.46 via multitool (sideload) but won't work, then tried 2.64 via zip from twrp and again no results at the end I tried 2.46 via zip and it works
use supersu 2.50 beta
Related
I installed the TWRP V2.8.6.1 I as described in TWRP web site.
After installation I rebooted the phone and it rebooted to recovery so I tried to reboot to system but it rebooted back to recovery.
Any idea how to address this issue?
AmnonD said:
I installed the TWRP V2.8.6.1 I as described in TWRP web site.
After installation I rebooted the phone and it rebooted to recovery so I tried to reboot to system but it rebooted back to recovery.
Any idea how to address this issue?
Click to expand...
Click to collapse
I decided to WIPE and re-install the ROM instead of tracing the cause of this issue and fixing it.
Everything works fine afterwards.
Thanks.
Is it possible to instal the compatible cwm recovery at huawei P8max and how? I tried different versions using FlashFire and one apk with loader.zip, but without success. After rebooting recovery, i got some strange rescue screen with 2 faults: 11. recovery and 2: boot (update your system).
Unlocked Bootloader?
Why not use the working TWRP that existing?
same problem after b210 from dload on sd card it seems emui 4 does not support thre local cwm
@Hirs
I wrote already that i have a lot of problems with "working TWRP". When i flashed it the first time, it was ok, but later, rebooting sytem was not working, every time i was reverted to twrp screen. I flashed the stock recovery, then twrp again, the same situation.
drpainster said:
@Hirs
I wrote already that i have a lot of problems with "working TWRP". When i flashed it the first time, it was ok, but later, rebooting sytem was not working, every time i was reverted to twrp screen. I flashed the stock recovery, then twrp again, the same situation.
Click to expand...
Click to collapse
Thats normal that you cant reboot to system sometimes with a installed TWRP, then you flash stock back and reboot.
You can easily flash TWRP do the things you want and then reboot to bootloader flash stock and use the phone.
I dont think there is a CWM especially for the P8Max, but you can try the P8 one.
Hello everyone.
I had a problem flashing TWRP on my Google Nexus 5, or better the problem comes when I try to enter the recovery.
I followed this pattern from stock android 6.0.1 with august security patch:
1) unlock bootloader
2) downloaded lastest TWRP (3.0.2 hammerhead) recovery from the official website
3) flash it with "fastboot flash recovery recovery.img"
Until this point everything's alright but then when I unplug my phone from the laptop and click on enter recovery something strange happens.
I can see the TWRP boot image but as soon as I go in I see tons of errors related to "cannot mount ..." and some partitions name like /data, /cache, and then starts the bootloop without let me any chance to do something. Sorry but I can't see every error beacuse this happen too fast.
Any idea on what is going on?
I've tried the TWRP 3.0.1 but is the same shuold I go down or maybe I have to change it beacuse of compatibily issues with the monthly patches?
Thank you for your help, I hope I explained my problem clearly.
After unlocking the bootloader, phone wipe all data? Did you reboot after unlocking bootloader?
audit13 said:
After unlocking the bootloader, phone wipe all data? Did you reboot after unlocking bootloader?
Click to expand...
Click to collapse
No I've just unlocked and then tryied to flash the recovery without wipe.
But data is already wiped by unlocking the bootloader isn't it?
Anyway thanks for your reply as soon as I can I'll try what you have written.
Yes, the data should be automatically wiped. Try TWRP 2.87. If the phone still doesn't boot into TWRP, reflash stock recovery, flash userdata.img, immediately boot into stock recovery using the button combo without rebooting, perform a factory wipe, reboot into fastboot, and flash TWRP again.
audit13 said:
Yes, the data should be automatically wiped. Try TWRP 2.87. If the phone still doesn't boot into TWRP, reflash stock recovery, flash userdata.img, immediately boot into stock recovery using the button combo without rebooting, perform a factory wipe, reboot into fastboot, and flash TWRP again.
Click to expand...
Click to collapse
Thank you so much for telling me to flash the 2.8.7, i've choosen the 2.8.7.1 without success (it did't flash i don't know why) but then after another wipe all I've flashed the 2.8.7.0 and it seems to work.
The only thing I would like to ask now is: I'm going to flash superSU and elementalX over stock AOSP (I don't want custom ROM for now) and can this recovery cause problem because of it is not the last update?
Thank you again for the answer!
I have not tried 2.87 with Elemental X. The only way to determine whether it will work would be to try it. I recommend creating a nandroid backup before flashing Elemental so you can restore if something goes wrong.
TWRP Restore problem
Hi, I have an issue with the resotre of TWRP...
Here's what I did:
-Downloaded the latest OTA image https://developers.google.com/android/nexus/ota
-Downloaded latest SuperSU http://download.chainfire.eu/supersu-stable
-Downloaded latest ElementalX http://elementalx.org/devices/nexus-5/
-reboot to TWRP
Choose OTA, then SuperSU, then ElementalX
Luunch the restore..
And my screen is "blocked" from 5 hours on Install Zip 1 of 3.
"blocked" means doesn't move to the Zip2 but the clock is moving... the screen is locking itself after few seconds and I am able to unlock it...
Any idea how to exit properly ?
I have rebooted...deleted all my music... (I think that the issue may come from insufficient disk space) and relaunched...
Will see...
download Nexus Root Toolkit-type in google Nexus Root Toolkit - and watch from yuotoube how it work's
good luck
hunter-dz said:
download Nexus Root Toolkit-type in google Nexus Root Toolkit - and watch from yuotoube how it work's
good luck
Click to expand...
Click to collapse
My N5 was already rooted... and it's the second time that I update the OTA using directly TWRP... and for the August patch it has worked fine.
I don't know what's happen now...
kevtuning said:
My N5 was already rooted... and it's the second time that I update the OTA using directly TWRP... and for the August patch it has worked fine.
I don't know what's happen now...
Click to expand...
Click to collapse
Download thé nrt and i Will teach how to root ur n5
And type in Google nrt n5 xda
audit13 said:
I have not tried 2.87 with Elemental X. The only way to determine whether it will work would be to try it. I recommend creating a nandroid backup before flashing Elemental so you can restore if something goes wrong.
Click to expand...
Click to collapse
Now I can confirm that I was able to flash the lastest SuperSU and ElementalX with TWRP 2.8.7.0 without any problem, so thank you again for your help.
kevtuning said:
Hi, I have an issue with the resotre of TWRP...
Here's what I did:
-Downloaded the latest OTA image https://developers.google.com/android/nexus/ota
-Downloaded latest SuperSU http://download.chainfire.eu/supersu-stable
-Downloaded latest ElementalX http://elementalx.org/devices/nexus-5/
-reboot to TWRP
Choose OTA, then SuperSU, then ElementalX
Luunch the restore..
And my screen is "blocked" from 5 hours on Install Zip 1 of 3.
"blocked" means doesn't move to the Zip2 but the clock is moving... the screen is locking itself after few seconds and I am able to unlock it...
Any idea how to exit properly ?
Click to expand...
Click to collapse
Hi, I've have successfully installed the last OTA update but not with zip file, instead I downloaded the factory image and flashed with fastboot boot.img and system.img (also vendor.img if you have one) then rebooted into TWRP and installed the lastest ElementalX and SuperSU.
I'm not sure but I think that factory image zip file are not installable via recovery but only with the flash-all that comes with them. This script use fastboot to flash everything you need of the factory image
You can find this procedure on the ElementalX website, here is the link hope it can help out: http://elementalx.org/how-to-install-android-monthly-security-updates/
Finally... I installed CM13 and ElementalX... in some minutes ...
I suppose the the problem was in my zip file...
Hi,
Just for you to know:
Model: r7plusf
Recovery: TWRP 3.0.2-0
----------------------------------------
So earlier today I did an OTA update (cm-14.1-20161205-NIGHTLY-r7plus.zip), but couldn't get my phone to boot.
So naturally, I tried wiping Cache and ART cache, but was still bootlooping.
Thought there might be someting wrong with my ROM and data, so I formated data and Installed ROM and GAPPS again after ADB pushing them onto my phone.
Now, and although CM14.1 and GAPPS are successfully installed on my Oppo R7 Plus, I can't boot into the OS. Every time I try reboot system, whether through POWER_BUTTON, RECOVERY or ADB, I just boot into Recovery.
Worst of all, for some unknown reason, I can't get into BOOTLOADER, neither through button combination, nor through Recovery nor ADB.
I found this article (http://forum.xda-developers.com/tmobile-lg-g3/general/fix-recovery-loop-twrp-computer-t2873386) in the LG G3 thread about executing some shell commands, but I haven't tested testing it with my phone's variables because it might hard brick it...
Please Help!
[EDIT] I now have access to fastboot but still recovery looping like crazy.
I installed the same update via CyanDelta , worked like a charm ! hopefully you get back up and running.
[UPDATE] strangely I tried to flash stock recovery and boot CM13 and it worked!
Will try to flash twrp again and insall CM14
keep you up to date
Same thing happened to me! Where did you get a copy of the stock recovery? Link?
resverse said:
[UPDATE] strangely I tried to flash stock recovery and boot CM13 and it worked!
Will try to flash twrp again and insall CM14
keep you up to date
Click to expand...
Click to collapse
I had the same problem. Can't remember exactly how I resolved it. But I think, I use CM recovery to flash nightly. Then flash TWRP to flash gapps. For some strange reason, using CM recovery also show no enough disk space whenever I try to flash opengapps. But TWRP recovery can flash opengapps successfully.
Don't use the OTA, use adb sideload to flash the nightly next time. So far, adb sideload has not given me any issue to flash nightly.
Same problem...
I tried a lot of things nothing works and now I've installed the cm recovery but I have the "unauthorized phone" in terminal when I try to flash the ROM... I can do nothing because I can't enable the usb debugging. I don't know what to do.
If somebody can help I appreciate.
corbalan12 said:
Same problem...
I tried a lot of things nothing works and now I've installed the cm recovery but I have the "unauthorized phone" in terminal when I try to flash the ROM... I can do nothing because I can't enable the usb debugging. I don't know what to do.
If somebody can help I appreciate.
Click to expand...
Click to collapse
Since then I found how to fix it :
first of all I flashed cm13 through TWRP,
Then I flashed the stock recovery (Google it, I found it in OPPO forums) with fastboot,
After that I did a factory reset in the stock recovery,
Booted cm13 with stock recovery,
Then re-flashed TWRP,
From TWRP, I wiped both data and system partitions,
Then fresh installed cm14 and Gapps
And it worked!
Not sure if those are the exact steps I followed because all I did was a hole lot of messing around and trying absurd things out, but think this is how I fixed it.
Let me know if it worked for you or if you still can't fix your problem
Best of luck
Resverse
resverse said:
Since then I found how to fix it :
first of all I flashed cm13 through TWRP,
Then I flashed the stock recovery (Google it, I found it in OPPO forums) with fastboot,
After that I did a factory reset in the stock recovery,
Booted cm13 with stock recovery,
Then re-flashed TWRP,
From TWRP, I wiped both data and system partitions,
Then fresh installed cm14 and Gapps
And it worked!
Not sure if those are the exact steps I followed because all I did was a hole lot of messing around and trying absurd things out, but think this is how I fixed it.
Let me know if it worked for you or if you still can't fix your problem
Best of luck
Resverse
Click to expand...
Click to collapse
Thank you very much!!!! I'll try tomorrow and tell you.
I appreciate a lot!
First of all now works but to be honest, I don't know if the way I fix makes sense or if is correct but not for the same reason I do but I'll try to explain...
I had cm-14.1-20161218-NIGHTLY and I tried to update via OTA to 20161220 the phone reboot and I get the bootloop. The first I thought, install again the ROM making wipe data and blabla... nothing work.
I tried to "reflash" the recovery, nothing. Flashed cm recovery, it always gave me error trying to flash the rom. I tried to install with stock recovery, errors too.
I was reading hundred of post looking for my issues, device unauthorized, "error 7" in twrp... I was crazy.
At last I thought, I've been trying to install from SDcard, if I try to install from internal memory? and I install again the twrp to transfer the ROM and Gapps to the internal memory and... it worked!!!!
Long story but with happy ending.
Thank you for your help I appreciate and sorry for my english.First of all now works but to be honest, I don't know if the way I fix makes sense or if is correct but not for the same reason I do but I'll try to explain...
I had cm-14.1-20161218-NIGHTLY and I tried to update via OTA to 20161220 the phone reboot and I get the bootloop. The first I thought, install again the ROM making wipe data and blabla... nothing work.
I tried to "reflash" the recovery, nothing. Flashed cm recovery, it always gave me error trying to flash the rom. I tried to install with stock recovery, errors too.
I was reading hundred of post looking for my issues, device unauthorized, "error 7" in twrp... I was crazy.
At last I thought, I've been trying to install from SDcard, if I try to install from internal memory? and I install again the twrp to transfer the ROM and Gapps to the internal memory and... it worked!!!!
Long story but with happy ending.
Thank you for your help I appreciate and sorry for my english.
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