I was on fulmics 2.7 and decided to update to M.
I downloaded N&N Custom ROM based on stock ROM.
I booted to TWRP (newest version), wiped everything, format data.
Then I pushed the ROM according to dev instructions to the phone and installed.
Reboot, booting, bootanimation and then a white screen:
"Enter pin to unlock. 30/30 tries"
I do not have a PIN on the SIM card activated, but I entered the correct one - didnt work, not accepted.
Booted without SIM - same question.
I downloaded the files again, same problem.
I flashed a stock ROM with flashable system from XDA - same problem.
I downloaded MM kdz and tried to flash with LGUP. Error with "port open is failed after dload change".
I downloaded fulmics 2.7 and flashed in TWRP, not booting, stuck at LG logo, LED is green-blue.
Current status:
I still have TWRP but no TWRP backup.
I am not a newb about flashing:
ZTE Blade, Hannspad, Galaxy Nexus, Galaxy S, Nexus 4, Huawei something, Arcos something, Asus ME301T Tablet, but this is the first flash that went haywire.
Help?
Under stock rom you mean this?
http://forum.xda-developers.com/lg-g3/development/stock-d855-30b-images-kdz-flashables-t3282012
Thats one of the stock ROMs I tried.
The N&N is this:
http://www.htcmania.com/showthread.php?t=1120602
there is unbrick method under Bender007 signature
But you probably have to wait for more solutions. It is good that your TWRP is still there.
Direct link:http://www.androidbrick.com/unbrick-recover-your-dead-lg-g3-g2-all-variants/
Edit:
Maybe this info can help. the guy had some problems with lgup.
http://forum.xda-developers.com/showpost.php?p=64762900&postcount=2915
wohooo....
latest CM13 nightly works...
So the problem is the ROM...
r0tati0n said:
wohooo....
latest CM13 nightly works...
So the problem is the ROM...
Click to expand...
Click to collapse
No offense but you are totally INCORRECT my friend, there is no ROM problem. You have been answered to your problem in the original thread, me one of who answered to your issue. Please, report there if you downloaded the full v1.3 rom or just thev 1.4 update.
Thanks
I reflashed N&N 1.3 again, after CM13 (Wipe of course).
The problem happened again.
flashed CM13 again - no white screen.
I installed 1.3 and then 1.4 update, second try only 1.3.
To me: It is the ROM.
r0tati0n said:
I reflashed N&N 1.3 again, after CM13 (Wipe of course).
The problem happened again.
flashed CM13 again - no white screen.
I installed 1.3 and then 1.4 update, second try only 1.3.
To me: It is the ROM.
Click to expand...
Click to collapse
Sorry to hear that my friend.
Best of luck.
Works again....
What did I do?
Flashed original MM using LGUP and 0.5 DLL using these drivers:
http://download1443.mediafire.com/4grbrdu70t6g/yb4z4zereo3ax4g/LG-Mobile-Driver_v4.0.3.0.zip
Full Reset in LGUP.
TWRP gone. KingRoot installed, rooted.
AutoRecMMD855 installied, this installs TWRP from the system.
booted into TWRP, flashed TWRP again for security using original img.
flashed N&N 1.4, 1.5, flykernel, xposed and xpirt fix.
Only Odysseus Odyssey was longer
Related
So, I have root (confirmed), unlocked bootloader (I guess), TWRP 2.7
I tried:
- omni-4.4.2-20140514-v500-HOMEMADE.zip
- cm-11-20140618-NIGHTLY-v500.zip
- cm-11-20140619-INFECTED-v500.zip
But it always says, that my device is a "palman" and no "v500". I made it to get the Slim-v500-4.4.3.build.5.9-INFECTED-20140616-1124.zip installed once, but then I ended up in a Boot-Loop wit the original "LG Logo - Security Error" screen. So I reverted everything with TWRP. Now I can only boot in TWRP and cannot get any ROM to run.
Any suggestions?
Addition:
Now I was able to Flash cm-11-20140618-NIGHTLY-v500.zip, although i edited the update script and removing the first line where it verifies the model. So it flashed the ROM correctly, but upon restarting, I ended up with the 'official' "LG Logo - Security Error".
So I did a restart via Power+Vol- into All three buttons. The Factory Reset screen comes up, when I hit Vol+ twice I gets me back into TWRP, but on the way there it also shows up the
Secure booting Error!
Cause : Device Unlock!, so Boot Success!!!
.... and now?
Aight, Now with the LG Mobile Support Tool and using Download-Mode on the device, I am hopefully able to go back to stock... Needs to DL 1,2 gig though -.-
So I guess I'll stick with the stock, except anyone is able to tell me where I went wrong...
I'm thinking:
1. towelroot
2. flashify for TWRP
3. choose rom and flash
right? Or do I have to do something extra to the bootloader?
AhNe said:
Aight, Now with the LG Mobile Support Tool and using Download-Mode on the device, I am hopefully able to go back to stock... Needs to DL 1,2 gig though -.-
So I guess I'll stick with the stock, except anyone is able to tell me where I went wrong...
I'm thinking:
1. towelroot
2. flashify for TWRP
3. choose rom and flash
/right? Or do I have to do something extra to the bootloader?
Click to expand...
Click to collapse
If you have the palman device, you have the Google Play edition, and should not be trying to install Roms for the 500 device. All that is out for the palman device is the sleekai kernel, and a base ROM with no extras. If you have the palman device, install the sleekai kernel and exposed and you will be better off anyway.
Is palman is the one have v510?? so awifi is v500 that i have, lol.
I got it to work after all and was able to install the latest CM nightly. After I did the reinstallation of everything (with the LG tool), I did the following:
- root via towelroot
- installed TWRP 2.7.0
- installed TWRP 2.7.1
- installed CM via TWRP 2.7.1
Still, I have no idea why it was recognized wrong during the first tries...
AhNe said:
I got it to work after all and was able to install the latest CM nightly. After I did the reinstallation of everything (with the LG tool), I did the following:
- root via towelroot
- installed TWRP 2.7.0
- installed TWRP 2.7.1
- installed CM via TWRP 2.7.1
Still, I have no idea why it was recognized wrong during the first tries...
Click to expand...
Click to collapse
Good to hear bro.
@AhNe
Just to get it clear. You have a v500 and you rooted it with towelroot and flashed the recovery sucessfully with Flashify ?
something wrong in Loki, try to give it a search...
Sent from my LG-V500 using Tapatalk
Hi,
I have tried to install many custom roms but all get stuck on their own boot logos
eg
*Resurrection remix 5.6.5 marshmallow was stuck on its rr logo ( Tried installation with twrp 3.0, 2.4. 2.6 but still same thing)
*Cyanide 5.1 also gets stuck on its boot logo
Phone gets passes note 2 thing but gets stuck on respective roms logos i install
# Yes i Rooted phone before installation
# TWRP 3.0 installed
# Did clean installs (Formatted EVERYTHING and installed)(Read somewhere twrp cant format stock stuff properly, i dont know) Should i try different recovery? (Please suggest best to install RR Marshmallow)
# Presently I m on stock 4.4.2
# tried this too >> custom rom zip install >> SU Install >> Gapps >>restart (Did without SU install too but doesnt work that way too)
I got it SOLVED finally
HOW?
Yup sure i ll tell how
I followed the following steps
1. Flash stock rom ( I mean stock rom by odin, Not factory reset or anything (as that didnt work) and my baseband was also lost (showed 'Unknown'))
2. Didnt add anything to it (gmail account or any settings etc)
3. Booted it completely once again ( restarted after first boot)
4. got to Download mode
5. Rooted it using cf auto root ( for sgh-i317m as i m using same phone)
6. restarted
7. got to Download mode again
8. Flashed twrp 2.8.7.0 from Odin
9. restarted again
10. got to Recovery
11. Flashed Resurrection Marshmallow (I think 5.6.5)
12. Flashed SU manually after that
13. Flashed OpenGapps Mini 6.0
14. Wiped Dalvikcache / Cache
15. Reboot
16. Wait for about FIVE Mins and
VOILA....
Enjoying new Marshmallow
Hope this helps someone who is also stuck in my situation.
Thanks for all your help
are you sure that should work? you have i317 and as far as I know it differs from N7100 and N7105
I too am experiencing the same issue, I have an at&t SGH-i317
I tried latest TWRP as well as CWM and Philz recovery
I tried like 4 different ROM's some based off stock and some based of Cyanogen mods.
I even wiped cache and davlik cache after ROM install as suggested by some of the threads, I actually tried every combination I could think of and all ROM's get stuck on the boot logo splash screen.
Is there something I am missing or doing wrong, this is certainly the the first phone I tried this on.
yaro666 said:
are you sure that should work? you have i317 and as far as I know it differs from N7100 and N7105
Click to expand...
Click to collapse
I m not sure about it. Do they actually differ ? i317 and n7105 (My thoughts they are same, Actually ALL Canadian versions of note 2 are same)
xtacydima said:
I too am experiencing the same issue, I have an at&t SGH-i317
I tried latest TWRP as well as CWM and Philz recovery
I tried like 4 different ROM's some based off stock and some based of Cyanogen mods.
I even wiped cache and davlik cache after ROM install as suggested by some of the threads, I actually tried every combination I could think of and all ROM's get stuck on the boot logo splash screen.
Is there something I am missing or doing wrong, this is certainly the the first phone I tried this on.
Click to expand...
Click to collapse
Can this be because of stock kernel? Because i m still on stock kernel
And thats the only thing i didnt change, despite all other random changes in steps to follow to install custom rom.
First and foremost TWRP 3.0 might be your problem, Its buggy and doesnt work right some people couldnt install it and all others have had issues with flashing roms, I would downgrade twrp to 2.8.5 if I were you.
the only other thing I think you already said you did but when you wipe go to advanced wipe make sure system is checked so system, cache, delvik cache, and data...but I think mainly TWRP is probably your problem.
lsdhillon said:
Hi,
I have tried to install many custom roms but all get stuck on their own boot logos
eg
*Resurrection remix 5.6.5 marshmallow was stuck on its rr logo ( Tried installation with twrp 3.0, 2.4. 2.6 but still same thing)
*Cyanide 5.1 also gets stuck on its boot logo
Phone gets passes note 2 thing but gets stuck on respective roms logos i install
# Yes i Rooted phone before installation
# TWRP 3.0 installed
# Did clean installs (Formatted EVERYTHING and installed)(Read somewhere twrp cant format stock stuff properly, i dont know) Should i try different recovery? (Please suggest best to install RR Marshmallow)
# Presently I m on stock 4.4.2
# tried this too >> custom rom zip install >> SU Install >> Gapps >>restart (Did without SU install too but doesnt work that way too)
Click to expand...
Click to collapse
yaro666 said:
are you sure that should work? you have i317 and as far as I know it differs from N7100 and N7105
Click to expand...
Click to collapse
majicmazo said:
First and foremost TWRP 3.0 might be your problem, Its buggy and doesnt work right some people couldnt install it and all others have had issues with flashing roms, I would downgrade twrp to 2.8.5 if I were you.
the only other thing I think you already said you did but when you wipe go to advanced wipe make sure system is checked so system, cache, delvik cache, and data...but I think mainly TWRP is probably your problem.
Click to expand...
Click to collapse
I m gonna go to twrp 2.8.5. Hopefully it works. Will be back with results soon.
i get this error after installation (Using twrp 2.8.5.0 now)
"unmount of /system failed; no such volume"
Probably this is cause?
How to fix it?
and
I m using twrp for t0lte (i have SGH-i317m) I hope its all right with that.
lsdhillon said:
Can this be because of stock kernel? Because i m still on stock kernel
And thats the only thing i didnt change, despite all other random changes in steps to follow to install custom rom.
Click to expand...
Click to collapse
Actually yes I never updated the kernel, and now I am wondering if that is the reason why. Perhaps the latest ROM's need the latest kernel. Unfortunately, the links for that are down, if anyone can repost please.
[UPDATE]
I found the latest kernel and flashed it within Philz latest recovery and sure enough that did the trick, now I got two ROM's I tried and both booted fine. I guess that's the fix.
that's weird, I'm using stock kernel since the 1st day and never had boot problem. See if your emmc chip is sane or insane
xtacydima said:
Actually yes I never updated the kernel, and now I am wondering if that is the reason why. Perhaps the latest ROM's need the latest kernel. Unfortunately, the links for that are down, if anyone can repost please.
[UPDATE]
I found the latest kernel and flashed it within Philz latest recovery and sure enough that did the trick, now I got two ROM's I tried and both booted fine. I guess that's the fix.
Click to expand...
Click to collapse
Could you please guide me to stable risk-free custom kernel for my sgh-i317
yaro666 said:
that's weird, I'm using stock kernel since the 1st day and never had boot problem. See if your emmc chip is sane or insane
Click to expand...
Click to collapse
Stock kernel with latest 6.x ROM's? Only thing I can think of is your stock kernel was updated with an Android update, since this isn't my phone I din't know how on queue my family member who owns it was with updates. Everything is working fine now I just settled on a ROM after trying a few, so I think my emmc chip is fine.
---------- Post added at 03:20 PM ---------- Previous post was at 03:00 PM ----------
lsdhillon said:
Could you please guide me to stable risk-free custom kernel for my sgh-i317
Click to expand...
Click to collapse
Here is the kernel I downloaded (it's a zip so I flashed via Phil'z latest recovery)
http://d-h.st/JUm
Here is latest modem (same flashed via Philz)
http://d-h.st/WTp
xtacydima said:
Stock kernel with latest 6.x ROM's? Only thing I can think of is your stock kernel was updated with an Android update, since this isn't my phone I din't know how on queue my family member who owns it was with updates. Everything is working fine now I just settled on a ROM after trying a few, so I think my emmc chip is fine.
Click to expand...
Click to collapse
really stock kernel with MJ5 modem and old bootloader up until this year january, as I updated to RR 5.1.1 and then updated bl, modem to OC and flashed CM13
xtacydima said:
Stock kernel with latest 6.x ROM's? Only thing I can think of is your stock kernel was updated with an Android update, since this isn't my phone I din't know how on queue my family member who owns it was with updates. Everything is working fine now I just settled on a ROM after trying a few, so I think my emmc chip is fine.
---------- Post added at 03:20 PM ---------- Previous post was at 03:00 PM ----------
Here is the kernel I downloaded (it's a zip so I flashed via Phil'z latest recovery)
http://d-h.st/JUm
Here is latest modem (same flashed via Philz)
http://d-h.st/WTp
Click to expand...
Click to collapse
I flashed AGNI kernel but the results were still same. Now gonna flash http://d-h.st/JUm as xtacydima suggested(Thanks).
Hope it works.
Will be back with results soon.
Do i need to update modem? to install RR (Marshmallow)?
With http://d-h.st/JUm as xtacydima suggested
It doesnt pass note 2 logo
Just goes blank after note 2 logo, So i think it isnt supported.
i m on 4.4.2 stock now.
Another thing i note is that my baseband is "unknown".
Any suggestions?
I got it SOLVED finally
HOW?
Yup sure i ll tell how
I followed the following steps
1. Flash stock rom ( I mean stock rom by odin, Not factory reset or anything (as that didnt work) and my baseband was also lost (showed 'Unknown'))
2. Didnt add anything to it (gmail account or any settings etc)
3. Booted it completely once again ( restarted after first boot)
4. got to Download mode
5. Rooted it using cf auto root ( for sgh-i317m as i m using same phone)
6. restarted
7. got to Download mode again
8. Flashed twrp 2.8.7.0 from Odin
9. restarted again
10. got to Recovery
11. Flashed Resurrection Marshmallow (I think 5.6.5)
12. Flashed SU manually after that
13. Flashed OpenGapps Mini 6.0
14. Wiped Dalvikcache / Cache
15. Reboot
16. Wait for about FIVE Mins and
VOILA....
Enjoying new Marshmallow
Hope this helps someone who is also stuck in my situation.
Thanks for all your help
I took my 5.1.1 VZW Note 4, and rooted it with King Root. I proceeded to follow the instructions to change my CID here. I used adb, performed the commands, and everything seemed golden. I used odin to flash TWRP, but something went wrong. I booted into the recovery, and tried to "update from external storage". I soon recieved a "dm-verity verification failed in recovery" messaged. It did not occur to me that I was still in the stock recovery; I did not bother to check it's initial look and feel, and assumed the TRWP programmers were just lazy. After reading up on this "dm-verity" error, xda posters said I should flash it with Kies. Thinking nothing wrong could happen, I gave it a shot. It updated to 6.0.1. This is where the problems start happening.
Since then, I can't reflash to 5.1.1. I've tried every version I could get my hands on, including the 5.1.1/6.0.1 hybrid posted here. I have 3 total verions of 5.1.1. I then tried to downgrade to 5.0.1. The first version of 5.0.1 started artifacting the screen, but booted and stopped promptly. It only artifacted the "Samsung" loading screen. I couldn't, however, root the device. Feeling desperate, I tried the only other version of 5.0.1. Success! I rooted and reran the adb commands and the script provided to change CID. This time, it skipped the first half of the script. It went directly to "backup up loader to external card". This tells me something about my CID will forever be changed, and is probably the reason my phone is boot looping. This time, I was able to flash TWRP. I installed CM 13 only to find out my sim wasn't recognized (when I used it to download King Root in 5.0.1 before). I figured it was because I was usig a 5.0.1 bootloader/modem. I tried reflashing to 5.1.1, the 5.1.1/6.0.1 hybrid, and 5.0.1 again. 5.11 boot loops and 5.0.1 hangs. Advice please... Thanks
Versions flashed:
"N910VVRU2BPA1_N910VVZW2BPA1_N910VVRU2BPA1_HOME.tar" - 5.1.1, boot loops at Verizon screen
"N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar" - 5.1.1/6.0.1 hybrid, boot loops
"N910VVRU2BOG5_N910VVZW2BOG5_N910VVRU2BOG5_HOME.tar" -5.0.1, boots but artifacts and cannot root
"N910VVRU2BOF1_N910VVZW2BOF1_N910VVRU2BOF1_HOME.tar" - 5.0.1, booted and rooted/flashed to TWRP, caused hiccups in MM custom roms, cannot get to boot again after a reflash
"N910VVRU2BPA1_StockRestore.tar" -5.1.1 unincremented stock restore, fails on ~90% of odin flash
"N910VVRU2BPA1_StockRestore_Incremented.tar" - 5.1.1 incremented stock restore, flashes, boot loops
Edit: Success!! I flashed the Incremented Stock Restore for 5.1.1 to no avail. It keep boot looping. I cleared the cache and data twice in a last ditch effort, and pulled the USB cord. It booted! Can anyone instruct me on how to proceed to flash only the modem/required portion of 6.0.1 after flashing TWRP? Do I just flash the 6.0.1 modem or modem and kernel?
Edit 2: I flashed the 6.0.1 modem over top of my 5.1.1 full firmware. I have TWRP and CM 13 loaded and working perfectly. From previous experiences, I've noticed CM 13 is more forgiving than some other 6.0.1 custom ROMs. Should I attempt to reflash the Lollipop on MM Stock Rom to obtain the MM bootloader, and then unlock it? This is working fine at the moment.
Edit 3: I reflashed to the hybrid rom and everything's okay. I had to wipe the cache..
mods, you can delete this thread. I solved my issue
av00va said:
mods, you can delete this thread. I solved my issue
Click to expand...
Click to collapse
Hey bud I'm on 6.0.1 can you give me the link to downgrade to 5.1.1 So I can root and unlock
Sent from my VS990 using Tapatalk
mwebb34 said:
Hey bud I'm on 6.0.1 can you give me the link to downgrade to 5.1.1 So I can root and unlock
Sent from my VS990 using Tapatalk
Click to expand...
Click to collapse
http://forum.xda-developers.com/note-4-verizon/general/note-4-verizon-bootloader-unlock-t3358913 and http://forum.xda-developers.com/not...t/howto-bootloader-unlock-upgrade-to-t3398144 Use the 2nd link 1st to downgrade to 5.1
I had to use Kingoroot(Google it) to root. It was a pain but once you root you have to be patient and leave the phone until it stabilizes after rooting. It took me a few attempts but in the end I'm golden. Part of my problem is a bad battery too but that's another story....
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:
If it can, how? I'm having bootloop issues trying to do that. Thank you.
Bootloop in logo S9
RpRAUC said:
Bootloop in logo S9
Click to expand...
Click to collapse
follow up
Piereligio said:
If it can, how? I'm having bootloop issues trying to do that. Thank you.
Click to expand...
Click to collapse
http://forum.xda-developers.com/galaxy-s9/how-to/one-ui-2-beta-rooting-installing-twrp-t4012961
https://forum.xda-developers.com/ga...rooting-installing-twrp-t4012961/post81084623
The patched kernel contained here was the solution for me
S9 ROOT
I did it.I flashed twrp format data and and installed SoldierR9312 mod. lock screen,samsung account and magisk root all work
http://www.renovate-ice.com/soldier9312/#stable_g96x-q
viktorvlahov11 said:
I did it.I flashed twrp format data and and installed SoldierR9312 mod. lock screen,samsung account and magisk root all work
http://www.renovate-ice.com/soldier9312/#stable_g96x-q
Click to expand...
Click to collapse
This worked great, thanks. Only issue I met was that I couldn't see the OEM unlock switch, so it didn't let me to flash TWRP from Odin (even though it was already unlocked), giving me "only official released binaries are allowed to be flashed(recovery)" error.
The solution for that was following these steps: https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/
EDIT: no wait, maybe it's bootlooping.
EDIT2: yes it is. I'm using italian carrier, you?
EDIT3: at the end I created a custom boot.img by using Magisk and I flashed it. In this way I kept encryption and stock recovery, but this doesn't give me write permissions in /system. But I do have root.
it stucks for me on the samsung logo
aidenpearce296 said:
it stucks for me on the samsung logo
Click to expand...
Click to collapse
Try flashing the twrp flashable firmware it may fix your problem
---------- Post added at 08:41 AM ---------- Previous post was at 08:37 AM ----------
viktorvlahov11 said:
Try flashing the twrp flashable firmware it may fix your problem
Click to expand...
Click to collapse
Piereligio said:
This worked great, thanks. Only issue I met was that I couldn't see the OEM unlock switch, so it didn't let me to flash TWRP from Odin (even though it was already unlocked), giving me "only official released binaries are allowed to be flashed(recovery)" error.
The solution for that was following these steps: https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/
EDIT: no wait, maybe it's bootlooping.
EDIT2: yes it is. I'm using italian carrier, you?
EDIT3: at the end I created a custom boot.img by using Magisk and I flashed it. In this way I kept encryption and stock recovery, but this doesn't give me write permissions in /system. But I do have root.
Click to expand...
Click to collapse
I got it to work on a Bulgarian unlocked model
Maybe try flashing the twrp flashable firmware after the mod
omg it was so easy!
after you flashed twrp and formated data you just have to flash magisk and that's it
viktorvlahov11 said:
omg it was so easy!
after you flashed twrp and formated data you just have to flash magisk and that's it
Click to expand...
Click to collapse
I done that, but still stuck on SAMSUNG logo, no boot loop or what. I was waiting 10min, nothing happened.
Any advice?
Hi there,
after having tried different methods to root my S9, which has updated to Android 10 One UI 2.0 this morning, maybe the solution that finally worked for me will help you too.
First I tried to root just like in Pie, as found on the net: flashed TWRP 3.2.3 via Odin, then flashed Magisk with TWRP plus this no-verity-opt-encrypt. Got stuck in bootloop, tried different no-verity/dm-verity versions, Magisk 18.x and Magisk 20.1. Nothing worked, got stuck again every time i rebootet the system again.
Then, after realising that I CANT get back to Android 9 (old rom wasnt Odin flashable anymore, phone didnt boot, BSoD), I first downloaded the new stock rom and bootloader as zip, got it from here:
https://forum.xda-developers.com/showpost.php?p=81615561&postcount=1830.
You have to check if that fits with your version / phone. Once downloaded, I copied both onto my SD card. So now I was able to install at least the new clean stock rom. Oh, and now I used the TWRP version 3.3.1.
Then I found this:
https://forum.xda-developers.com/galaxy-s9/development/root-s9plus-exynos-android10-t4065343
At first I tried to root without the SoLdieR9312's mod, only with MAGISK 20.3 and no-verity. Stuck again, it only bootet to download mode, nothing else. So flashed again the clean stock rom, and after first not keeping the right order (I suppose) I finally followed EXACTLY the instructions 1 - 4 in above manual including SoLdieR9312's mod (I highly recommend first a complete Wipe, format data, and then flash the clean new Rom with Android 10 and bootloader from above link).
Now, to save you the time I spent today: once your phone is bootet (and succesfully rooted via Magisk 20.3, which will happen automatically due to the SoLdieR9312's mod), DONT LET MAGISK UPDATE TO VERSION 20.4!!!! Magisk Manager asks you to update, but when I did update to 20.4, everything fell apart again, it only bootet to download mode.
Now I seem to have it stable and running with 20.3 and the [email protected]. I rebootet 5 times so far just for the sake of it, and it works fine and rootet.
If I can be of further help, please let me know. I spent the last 12 hours on this matter, so dont hesitate.
Greetz from me minus a bunch of nerves
PS: After I wrote the above, I deleted the Knox family in the rootet system, and then it collapsed again and, after BSoD, it only rebootet into download mode. I can not exclude the possibility, that this might have been the reason for some system breakdowns before, as I had to re-do the wipe-clean-install-then-root-then-customize worksteps aroung 8 times yesterday before it was stable as it is now. Now I´ll leave Knox on it, though that itches me a bit. But I´m exhausted for now
PPS: IMPORTANT when I try to create a PIN or a pattern for the lock screen, phone reboots to SIM card PIN screen and then keeps rebooting and rebooting. It looks like there are some interferences with root and PIN / security. I did NOT create a Samsung account, only a google one, cause in the beginning i suspected it might have been a Sam acct problem (I constantly couldnt log into it on the phone). Turns out that might not have been the case, rather a prob between root and setting a lock screen security.