I have tried everything I think would remotly work, but my phone simply won't go through with the rooting process. I tried flashing chainfire through twrp 2.7.8.0 but everytime the log gets to replacing files, the phone reboots itself into the system, stopping the root. This issues seems to be pretty rare for I can't seem to find any past cases. Could it be something I did that singled me out?
Maybe this list of what I did can help?
1. Bought phone at t-mobile.
2. Got home and immediatly ran a software update with the stock os
3. Updated to 5.1 and proceded to unlock bootloader.
4. Flashed twrp 2.8.7.0
5. Made a nandroid backup of stock os
6. Flashed cyanogenmod 12.1 unofficial build beta 2 for m9 and gapps package.
7. Found ramdom crashes to much to bare, so i restored to factory settings (from the previous nandroid backup)
8. Attepted to root using chainfire beta.
9. Panick ensues as I tried both chainfire cersions with both twrp recovery.
Here is all the logs I can currently get my hands on:
Abnormal bootup notification in the actual OS: http://pastebin.com/BzAvTXxF
Twrp log before flashing root: http://pastebin.com/tDkgSaWd
I am trying to find a way to get the twrp last_log file after twrp crashes so I would have something to go on, but, sense twrp outright crashes, I can't use the copy log button. Adb can't access cache when the phone is booted up either. Is there any other way?
Extra info:
Phone: T-mobile htc m9 hima
OS: 5.1 (latest one availible for my carrier)
Bootloader: unlocked
Safety: S-on
Recovery: Twrp 2.8.7.0 and 2.8.5.0 (I tried both)
Root: Chainfire beta 2.49 and the lastest official stable build (I tried both)
Firmware version: 2.7.531.6
Thankyou in advance for all that took the time to read this. I am completly out of tricks so any help is greatly appreciated.
Jerry060599 said:
I have tried everything I think would remotly work, but my phone simply won't go through with the rooting process. I tried flashing chainfire through twrp 2.7.8.0 but everytime the log gets to replacing files, the phone reboots itself into the system, stopping the root. This issues seems to be pretty rare for I can't seem to find any past cases. Could it be something I did that singled me out?
Maybe this list of what I did can help?
1. Bought phone at t-mobile.
2. Got home and immediatly ran a software update with the stock os
3. Updated to 5.1 and proceded to unlock bootloader.
4. Flashed twrp 2.8.7.0
5. Made a nandroid backup of stock os
6. Flashed cyanogenmod 12.1 unofficial build beta 2 for m9 and gapps package.
7. Found ramdom crashes to much to bare, so i restored to factory settings (from the previous nandroid backup)
8. Attepted to root using chainfire beta.
9. Panick ensues as I tried both chainfire cersions with both twrp recovery.
Here is all the logs I can currently get my hands on:
Abnormal bootup notification in the actual OS: http://pastebin.com/BzAvTXxF
Twrp log before flashing root: http://pastebin.com/tDkgSaWd
I am trying to find a way to get the twrp last_log file after twrp crashes so I would have something to go on, but, sense twrp outright crashes, I can't use the copy log button. Adb can't access cache when the phone is booted up either. Is there any other way?
Extra info:
Phone: T-mobile htc m9 hima
OS: 5.1 (latest one availible for my carrier)
Bootloader: unlocked
Safety: S-on
Recovery: Twrp 2.8.7.0 and 2.8.5.0 (I tried both)
Root: Chainfire beta 2.49 and the lastest official stable build (I tried both)
Firmware version: 2.7.531.6
Thankyou in advance for all that took the time to read this. I am completly out of tricks so any help is greatly appreciated.
Click to expand...
Click to collapse
BRO........YOUR ISSUE IS REALLY EASY TO SOLVE I HAD KIND THE SAME ISSUE, JUST MAKE SURE YOU DO AS FOLLOWS:
1.-FOLLOW EXACTLY AS TOLD BY THE VERY SAME DEVELOPERS OF THE RECOVERY:
https://twrp.me/devices/htconem9.html
2.-INSTALL THE 2.8.7.1-b BETA VERSION NOT THE REGULAR 2.8.7.0
3.-INSTAL SUPERSU 2.49BETA NOT THE 2.46 REGULAR.
IF YOU DO AS I SAY, YOU WILL HAVE A PERFECT M9 WITH TWRP AND ROOTED.
LLegion said:
BRO........YOUR ISSUE IS REALLY EASY TO SOLVE I HAD KIND THE SAME ISSUE, JUST MAKE SURE YOU DO AS FOLLOWS:
1.-FOLLOW EXACTLY AS TOLD BY THE VERY SAME DEVELOPERS OF THE RECOVERY:
https://twrp.me/devices/htconem9.html
2.-INSTALL THE 2.8.7.1-b BETA VERSION NOT THE REGULAR 2.8.7.0
3.-INSTAL SUPERSU 2.49BETA NOT THE 2.46 REGULAR.
IF YOU DO AS I SAY, YOU WILL HAVE A PERFECT M9 WITH TWRP AND ROOTED.
Click to expand...
Click to collapse
tks for the help . will be trying it out.
Jerry060599 said:
tks for the help . will be trying it out.
Click to expand...
Click to collapse
Of u still have issues i can give whatsapp and help you with further assistance
LLegion said:
Of u still have issues i can give whatsapp and help you with further assistance
Click to expand...
Click to collapse
Ok. About that 2.8.7.1 twrp image, may I have a link to it? I found some with a google search but none explicitly specifies hima compatibility.
Jerry060599 said:
tks for the help . will be trying it out.
Click to expand...
Click to collapse
Of u still have issues i can give whatsapp and help you with further assistance
Jerry060599 said:
Ok. About that 2.8.7.1 twrp image, may I have a link to it? I found some with a google search but none explicitly specifies hima compatibility.
Click to expand...
Click to collapse
Look at post 3 in this thread. Best is you read all information in the first three posts.
Here u havebaccess to my personal folderhttps://drive.google.com/folderview?id=0B--58xBx8PTOfmYyeDdXeFJ1ZnRSdGJTVnVhQTJQZUZiMG5uRWl0blNackNWMVU1NUNoVjg&usp=sharing
Flippy498 said:
Look at post 3 in this thread. Best is you read all information in the first three posts.
Click to expand...
Click to collapse
Ok. I just tried to flash it. The recovery still crashes/reboots the phone at the line replacing files. :/
Edit: Ill try to do adb sideload instead of flashing it directly from the recovery. Hopfully, I will get some sort of log if I do. Will take another half an hour to update my adb though.
Edit 2: Nope. phone still crashes. This time at "extracting files". Could'nt get logs either. :/ Does anyone know if it is OK to sideload supersu through the stock recovery? This might potentailly eleminate any issues from twrp.
Jerry060599 said:
Ok. I just tried to flash it. The recovery still crashes/reboots the phone at the line replacing files. :/
Edit: Ill try to do adb sideload instead of flashing it directly from the recovery. Hopfully, I will get some sort of log if I do. Will take another half an hour to update my adb though.
Edit 2: Nope. phone still crashes. This time at "extracting files". Could'nt get logs either. :/ Does anyone know if it is OK to sideload supersu through the stock recovery? This might potentailly eleminate any issues from twrp.
Click to expand...
Click to collapse
I had the same . Problem was when reverting a nandroid.
So i did restore again same nandroid but ticking only system image. that fixed the problem. then was all normal, zip are flashing good now
dragonesdenano said:
I had the same . Problem was when reverting a nandroid.
So i did restore again same nandroid but ticking only system image. that fixed the problem. then was all normal, zip are flashing good now
Click to expand...
Click to collapse
Sorry for the (extremly) late reply. I had not been home for the past week. I tried restoring to stock system image and flashin su binaries before. It didnt work. At this point, I suspect that the only reason why I can't flash supersu is because of my firmware version. So I'll be wimpering in a corner untill some kind devs at htc decide to release the source for my version.
Hi guys,
As soon as I got the OP3 in July, I somehow managed to successfully perform all the steps to get it rooted. I was running OnePlus3Oxygen_16_OTA_013_all_1608061823_765c081a5c8e4dad.zip
OnePlus has been showing me a "new version available" since September, but I very patiently and calmly didn't install it OTA because I didn't want to lose the root.
Finally had a bit of time today, decided I'd finally upgrade. Looked around for the "most recent stable version" and picked this one: OnePlus3Oxygen_16_OTA_035_all_1612310359_e10cadfb2af7.zip
Followed the steps for flashing using TWRP (twrp-3.0.2-1.28-oneplus3) here:
https://forum.xda-developers.com/oneplus-3/how-to/oxygenos-4-0-android-nougut-official-t3529684
It worked. Yay. Then (god dammit **** ****) I still saw this "new version available" and couldn't swipe it away... I accidentally clicked it and it downloaded the OTA. Fine.
Now I'm stuck in a TWRP boot loop. I tried re-installing the OTA_035.zip from TWRP -- I tried restoring my Nandroid Backup (only had enough room to save "Boot / Recovery / System" partitions, NOT data) -- and I tried ADB Sideloading 16_OTA_013.zip.
I'm stuck rebooting in TWRP 3.0.2-1.
Is there anything I can try before going ballistic and wiping my data?
Thanks.
Marc
Have you tried the newest blu-spark twrp? https://forum.xda-developers.com/devdb/project/?id=15934#downloads
Puddi_Puddin said:
Have you tried the newest blu-spark twrp? https://forum.xda-developers.com/devdb/project/?id=15934#downloads
Click to expand...
Click to collapse
Hey Puddi_Puddin, thanks for replying.
I never heard of blu-spark, but gave it a shot. Even though the guide seems to apply only to OP3T: https://forums.oneplus.net/threads/...-or-custom-recovery-without-data-loss.479265/
Anyways I flashed blu-spark with ADB. Booted into blu-spark. Wiped Dalvik/Cache, re-installed OnePlus3Oxygen_16_OTA_035_all_1612310359_e10cadfb2af7.zip, wiped Dalvik/Cache, rebooted -- keeps booting into blu-spark TWRP.
Get the "device unlocked" error screen, then the dm-verity error screen, then the OnePlus logo for about 2 seconds, and then back to blu-spark. Repeat ad nauseum.
What state is my device even in? I wouldn't call it bricked... I assume it's still rooted, bootloader works, I can flash different TWRP versions, ...
Any other ideas ... ?
Zingapuro said:
Hey Puddi_Puddin, thanks for replying.
I never heard of blu-spark, but gave it a shot. Even though the guide seems to apply only to OP3T: https://forums.oneplus.net/threads/...-or-custom-recovery-without-data-loss.479265/
Anyways I flashed blu-spark with ADB. Booted into blu-spark. Wiped Dalvik/Cache, re-installed OnePlus3Oxygen_16_OTA_035_all_1612310359_e10cadfb2af7.zip, wiped Dalvik/Cache, rebooted -- keeps booting into blu-spark TWRP.
Get the "device unlocked" error screen, then the dm-verity error screen, then the OnePlus logo for about 2 seconds, and then back to blu-spark. Repeat ad nauseum.
What state is my device even in? I wouldn't call it bricked... I assume it's still rooted, bootloader works, I can flash different TWRP versions, ...
Any other ideas ... ?
Click to expand...
Click to collapse
After you've flashed the full zip, flash also the latest stable version of SuperSu (2.79) and latest TWRP from @eng.stk (the v11, it solves the dm-verity error). Then reboot to recovery, it should appear TWRP and the error should't appear.
Zingapuro said:
Hey Puddi_Puddin, thanks for replying.
I never heard of blu-spark, but gave it a shot. Even though the guide seems to apply only to OP3T: https://forums.oneplus.net/threads/...-or-custom-recovery-without-data-loss.479265/
Anyways I flashed blu-spark with ADB. Booted into blu-spark. Wiped Dalvik/Cache, re-installed OnePlus3Oxygen_16_OTA_035_all_1612310359_e10cadfb2af7.zip, wiped Dalvik/Cache, rebooted -- keeps booting into blu-spark TWRP.
Get the "device unlocked" error screen, then the dm-verity error screen, then the OnePlus logo for about 2 seconds, and then back to blu-spark. Repeat ad nauseum.
What state is my device even in? I wouldn't call it bricked... I assume it's still rooted, bootloader works, I can flash different TWRP versions, ...
Any other ideas ... ?
Click to expand...
Click to collapse
There are quite a few versions of TWRP from eng.stk (bluspark). Which one did you install? Try version 11 which is supposedly for N or 3.0.2-19 or 23.
Thanks for your help everyone.
I downloaded SuperSU-v2.79 here http://downloadmirror.co/Utz/UPDATE-SuperSU-v2.79-20161211114519.zip
I flashed both ZIPs OnePlus3Oxygen_16_OTA_035_all_1612310359_e10cadfb2 and UPDATE-SuperSU-v2.79-20161211114519.zip
I confirm I'm using twrp-3.0.2-0_blu_spark_v11-op3.img (from the link provided by Puddi_Puddin)
Still see dm-verity error ... still keeps booting into blu_spark TWRP. :crying:
Zingapuro said:
Thanks for your help everyone.
I downloaded SuperSU-v2.79 here http://downloadmirror.co/Utz/UPDATE-SuperSU-v2.79-20161211114519.zip
I flashed both ZIPs OnePlus3Oxygen_16_OTA_035_all_1612310359_e10cadfb2 and UPDATE-SuperSU-v2.79-20161211114519.zip
I confirm I'm using twrp-3.0.2-0_blu_spark_v11-op3.img (from the link provided by Puddi_Puddin)
Still see dm-verity error ... still keeps booting into blu_spark TWRP. :crying:
Click to expand...
Click to collapse
Try the other two given by me.
Zingapuro said:
Thanks for your help everyone.
I downloaded SuperSU-v2.79 here http://downloadmirror.co/Utz/UPDATE-SuperSU-v2.79-20161211114519.zip
I flashed both ZIPs OnePlus3Oxygen_16_OTA_035_all_1612310359_e10cadfb2 and UPDATE-SuperSU-v2.79-20161211114519.zip
I confirm I'm using twrp-3.0.2-0_blu_spark_v11-op3.img (from the link provided by Puddi_Puddin)
Still see dm-verity error ... still keeps booting into blu_spark TWRP. :crying:
Click to expand...
Click to collapse
From where have you dowloaded the OTA? XDA or OnePlus forum?
I saw a thread regarding the OnePlus 3T update some post above, if you've downloaded from there you've made a mistake if you own a OnePlus 3.
tnsmani said:
Try the other two given by me.
Click to expand...
Click to collapse
You mean 3.0.2-19 or 23. Not blu_spark, right? Ok I tried twrp-3.0.2-23-oneplus3.img from here (https://www.androidfilehost.com/?fid=529152257862684308)
I tried flashing my old images I used last year (I just wanted the phone to boot into *something*) Oxygen_16_OTA_013 & SuperSU-v2.74. Managed to boot. Updated 4 Apps (??) But as soon as the login screen came up, it would reboot ... and keep looping. So I couldn't use the phone, but at least I managed to boot into something other than TWRP.
Next I tried to reinstall OOS4, 16_OTA_035 with SuperSU-v2.79 SR2. Still get the verity error, but at least I managed to boot! But - the phone is *super* buggy/unusable... SIM cards aren't working - I can't access my options screen - and "Developer options are not available for this user".
Now from my "About" screen I have OOS 4.0, Android 7.0, Kernel version 3.18.31-perf+ [email protected] <-- (that's from my TWRP version. right?)
Did the OTA I install from OnePlus directly screw everything up? For that brief moment before I installed it, I tasted a seemingly properly working OOS 4, so I know it's possible...
A few lessons I've learned are -- I can use any recovery (TWRP) to use MTP and flash files and stuff... but in order for the phone to work properly, I have to a) flash the SuperSU (not just the ROM) and b) make sure I have the "correct/proper" TWRP (kernel?) matched with each ROM. Is that kind of right? That's where I'm stuck I guess.
let92 said:
From where have you dowloaded the OTA? XDA or OnePlus forum?
I saw a thread regarding the OnePlus 3T update some post above, if you've downloaded from there you've made a mistake if you own a OnePlus 3.
Click to expand...
Click to collapse
I downloaded from here
https://forum.xda-developers.com/oneplus-3/how-to/oxygenos-4-0-android-nougut-official-t3529684
I'm sure I'm making a ton of mistakes -- that's why I'm here
(I read here https://forum.xda-developers.com/on...mple-trick-t3530685/post70415499#post70415499 that .28 shouldn't be used)
This post mentions a procedure to get rid of verity https://forum.xda-developers.com/oneplus-3/how-to/fix-device-mapper-verity-simple-trick-t3530685
I'm currently backing up my data, and I'll attempt to follow these instructions to switch to f2fs (hopefully get rid of the verity error) and install OxygenOS 4.0.1 (http://otafsc.h2os.com/patch/amazon...n_16_OTA_037_all_1701041839_aa64b084a40a4.zip)
I'm also a bit confused about the best version of SuperSU-v2.79 to use, because blu_spark was writing somewhere (can't find where) that SR1 and SR2 were the cause of battery issues ... So yeah, I've got other things to try, but should the ROM from OOS4.0.1 work with any of them?
THANKS.
Zingapuro said:
You mean 3.0.2-19 or 23. Not blu_spark, right? Ok I tried twrp-3.0.2-23-oneplus3.img from here (https://www.androidfilehost.com/?fid=529152257862684308)
I tried flashing my old images I used last year (I just wanted the phone to boot into *something*) Oxygen_16_OTA_013 & SuperSU-v2.74. Managed to boot. Updated 4 Apps (??) But as soon as the login screen came up, it would reboot ... and keep looping. So I couldn't use the phone, but at least I managed to boot into something other than TWRP.
Next I tried to reinstall OOS4, 16_OTA_035 with SuperSU-v2.79 SR2. Still get the verity error, but at least I managed to boot! But - the phone is *super* buggy/unusable... SIM cards aren't working - I can't access my options screen - and "Developer options are not available for this user".
Now from my "About" screen I have OOS 4.0, Android 7.0, Kernel version 3.18.31-perf+ [email protected] <-- (that's from my TWRP version. right?)
Did the OTA I install from OnePlus directly screw everything up? For that brief moment before I installed it, I tasted a seemingly properly working OOS 4, so I know it's possible...
A few lessons I've learned are -- I can use any recovery (TWRP) to use MTP and flash files and stuff... but in order for the phone to work properly, I have to a) flash the SuperSU (not just the ROM) and b) make sure I have the "correct/proper" TWRP (kernel?) matched with each ROM. Is that kind of right? That's where I'm stuck I guess.
I downloaded from here
https://forum.xda-developers.com/oneplus-3/how-to/oxygenos-4-0-android-nougut-official-t3529684
I'm sure I'm making a ton of mistakes -- that's why I'm here
(I read here https://forum.xda-developers.com/on...mple-trick-t3530685/post70415499#post70415499 that .28 shouldn't be used)
This post mentions a procedure to get rid of verity https://forum.xda-developers.com/oneplus-3/how-to/fix-device-mapper-verity-simple-trick-t3530685
I'm currently backing up my data, and I'll attempt to follow these instructions to switch to f2fs (hopefully get rid of the verity error) and install OxygenOS 4.0.1 (http://otafsc.h2os.com/patch/amazon...n_16_OTA_037_all_1701041839_aa64b084a40a4.zip)
I'm also a bit confused about the best version of SuperSU-v2.79 to use, because blu_spark was writing somewhere (can't find where) that SR1 and SR2 were the cause of battery issues ... So yeah, I've got other things to try, but should the ROM from OOS4.0.1 work with any of them?
THANKS.
Click to expand...
Click to collapse
Unfortunately I haven't tried to update the phone yet, so I don't know what else you can do. But you can also follow the guide posted by @Viper The Ripper here:
https://forum.xda-developers.com/showpost.php?p=70499899&postcount=5
I think that it's simpler and I'll follow that one this weekend when trying to updating my phone
Zingapuro said:
Hi guys,
As soon as I got the OP3 in July, I somehow managed to successfully perform all the steps to get it rooted. I was running OnePlus3Oxygen_16_OTA_013_all_1608061823_765c081a5c8e4dad.zip
OnePlus has been showing me a "new version available" since September, but I very patiently and calmly didn't install it OTA because I didn't want to lose the root.
Finally had a bit of time today, decided I'd finally upgrade. Looked around for the "most recent stable version" and picked this one: OnePlus3Oxygen_16_OTA_035_all_1612310359_e10cadfb2af7.zip
Followed the steps for flashing using TWRP (twrp-3.0.2-1.28-oneplus3) here:
https://forum.xda-developers.com/oneplus-3/how-to/oxygenos-4-0-android-nougut-official-t3529684
It worked. Yay. Then (god dammit **** ****) I still saw this "new version available" and couldn't swipe it away... I accidentally clicked it and it downloaded the OTA. Fine.
Now I'm stuck in a TWRP boot loop. I tried re-installing the OTA_035.zip from TWRP -- I tried restoring my Nandroid Backup (only had enough room to save "Boot / Recovery / System" partitions, NOT data) -- and I tried ADB Sideloading 16_OTA_013.zip.
I'm stuck rebooting in TWRP 3.0.2-1.
Is there anything I can try before going ballistic and wiping my data?
Thanks.
Marc
Click to expand...
Click to collapse
In my opinion, the only thing you can try is to make a data backup from recovery to any external storage (like a pendrive) by Otg, but it takes some risks. In case this partition has been damaged, you can get issues when you install the rom.
The safest you can do is clean installation in spite of you lose data so, full wipes and a new full rom.
Enviado desde mi ONEPLUS A3003 mediante Tapatalk
You have to install stock recovery, and then reboot into recovery, you will have a instalation error, reboot and loop solved Then, you can flash your twrp and su without loosing data
I discovered following this threath desesperate and going to do a clean install, dowload the files and try to do it steap by steap: https://forum.xda-developers.com/oneplus-3/how-to/fix-device-mapper-verity-simple-trick-t3530685
Good luck :good:
P.D.: I have formated system partition, so I lost the android configuration
satisastur said:
You have to install stock recovery, and then reboot into recovery, you will have a instalation error, reboot and loop solved Then, you can flash your twrp and su without loosing data
I discovered following this threath desesperate and going to do a clean install, dowload the files and try to do it steap by steap: https://forum.xda-developers.com/oneplus-3/how-to/fix-device-mapper-verity-simple-trick-t3530685
P.D.: I have formated system partition, so I lost the android configuration
Click to expand...
Click to collapse
Hey Satisastur,
Thanks for taking the time to comment. Yes, actually that's exactly the guide I wanted to follow. But I'm stuck before even starting -- if I make Nandroid Backup now (in ext4) I can't load it back once filesystem changes to f2fs -- isn't that right?
(I also asked the question in that thread: https://forum.xda-developers.com/on...rity-simple-trick-t3530685/page8#post70525818 )
And uh... sorry... what exactly do you mean "android configuration"... like ringtones and stuff?
Zingapuro said:
Hey Satisastur,
Thanks for taking the time to comment. Yes, actually that's exactly the guide I wanted to follow. But I'm stuck before even starting -- if I make Nandroid Backup now (in ext4) I can't load it back once filesystem changes to f2fs -- isn't that right?
(I also asked the question in that thread: https://forum.xda-developers.com/on...rity-simple-trick-t3530685/page8#post70525818 )
And uh... sorry... what exactly do you mean "android configuration"... like ringtones and stuff?
Click to expand...
Click to collapse
Yes, I was on f2fs before this happens, so I only have to install all without formating data. You should do a manual backup to do that, once on recovery, you be able to enter phone data partition from windows. Copy all folders you want to save before formating to f2fs in recovery. Other setup and configuration like ringtones and stuff, all cache and configuration of apps, wallpaper, led, colors and themes... you will lost it. I don't know how to backup that, but its the worst part of formating data... google backup doesn't save all the config
You will start with the android phone start menu, like new, with new dactilar and patron security, etc...
@Zingapuro
Try TWRP 3.0.2_19 and Supersu 2.79 stable. For some people this works and according to eng. stk, only Supersu 2.79 stable is compatible with N.
tnsmani said:
Try TWRP 3.0.2_19 and Supersu 2.79 stable. For some people this works and according to eng. stk, only Supersu 2.79 stable is compatible with N.
Click to expand...
Click to collapse
Tried flashing twrp-3.0.2-19-oneplus3.img and from TWRP installing:
OnePlus3Oxygen_16_OTA_037_all_1701041839_aa64b084a40a4.zip
UPDATE-SuperSU-v2.79-20161211114519.zip
Same issues as described above: boots into 4.0.1, but buggy, SIM cards don't work, no Dev options, etc...
satisastur said:
Copy all folders you want to save before formating to f2fs in recovery.
Click to expand...
Click to collapse
Yeah, I have a feeling this is my only choice. This is the next thing I'll try.
Zingapuro said:
Tried flashing twrp-3.0.2-19-oneplus3.img and from TWRP installing:
OnePlus3Oxygen_16_OTA_037_all_1701041839_aa64b084a40a4.zip
UPDATE-SuperSU-v2.79-20161211114519.zip
Same issues as described above: boots into 4.0.1, but buggy, SIM cards don't work, no Dev options, etc...
Yeah, I have a feeling this is my only choice. This is the next thing I'll try.
Click to expand...
Click to collapse
Try this guide: https://forum.xda-developers.com/oneplus-3/how-to/guide-flashing-oos-v4-0-1-custom-rom-t3537757
It will fix most of your issues.
For going back to full stock use this guide: https://forums.oneplus.net/threads/guide-how-to-unroot-your-oneplus-3-and-go-back-completely-to-stock.456232/
I hope everything will go back to normal.
Hi everyone,
Just want to update that my phone is back up and running. Thanks for your all your help.
More details here:
https://forum.xda-developers.com/on...rity-simple-trick-t3530685/page9#post70588707
Is there any way to update this thread to [SOLVED] ?
Zingapuro said:
Hi everyone,
Just want to update that my phone is back up and running. Thanks for your all your help.
More details here:
https://forum.xda-developers.com/on...rity-simple-trick-t3530685/page9#post70588707
Is there any way to update this thread to [SOLVED] ?
Click to expand...
Click to collapse
Great!
I think you can edit the thread title
Boot into your recovery [Vol+ and Power]
Connect your phone to your PC
Execute the following fastboot command on your PC (More informations on fastboot)
Code:
fastboot continue
Your phone will start right away. :good:
Hello.
I bought the BLACKVIEW BV9900 running Android 9.
I want to install the latest version of Lineageos with Android 10 on this phone, but first I want to know if my phone is compatible and if it works fine on it?
Is it also possible to root this phone?
Are there people on this forum who have already installed Lineageos and rooted this model?
Thanks for your feedback.
natouche said:
Hello.
I bought the BLACKVIEW BV9900 running Android 9.
I want to install the latest version of Lineageos with Android 10 on this phone, but first I want to know if my phone is compatible and if it works fine on it?
Is it also possible to root this phone?
Are there people on this forum who have already installed Lineageos and rooted this model?
Thanks for your feedback.
Click to expand...
Click to collapse
Never heard of lineageOS for that phone.
kurtn said:
Never heard of lineageOS for that phone.
Click to expand...
Click to collapse
When i search on google "lineageOS BV9900" there are sites that offer tutorials to install it. But having also seen on XDA a person who could not boot LineageOS installed on this model, it is for this reason that I would like to have the opinion of other people who have already installed it.
i may give it a try i recently got twrp working on it so its a good a time as any to look around.
(gotta find a way to backup my stuff first tough as its still encrypted and twrp doesnt wanna play with that)
annoyed
I had also a lot of problems ...
I had to reinstall the stock ROM over SP Flash Tool because of bootloop
I then managed to install twrp
- by activating oem in android setting
- activating usb debug mode
- fastboot flashing unlock
- fastboot flash recovery recovery.img (Took the bv9900 TWRP 331 found on the internet)
- Then tried to wipe, but I get an error that twrp is unable to mount partitions...
After searching I was able to get a workaround, a made a "Format Data"
- Install lineage img from twrp and reboot => got boot loop again !
- Then I reinstall only stock system partition through SP Flash Tool, and working again, but TWRP is away ???
Is the scatter File from the stock rom wrong ? How is it possible, that on flashing only the system partition, the recovery gets overwrited ???