Ran into a pretty big issue here and I'm not sure where to go. I've downloaded the HDX Mokee version and flashed it with the GAPPS from this thread. All went well until I rebooted and I see is a white box and then it boots into Chinese? A screen with a button came up and naturally I was gonna try to go through the installation so I pushed it and it rebooted my device into TWRP. TWRP went into a boot loop. So, I reboot into the bootloader and reflashed TWRP. I can now access twrp BUT there's NOW a password attached to my device...how the hell? I went to reflash the Mokee zip in bootloader thinking maybe it was a bad flash but i cant as it's a zip and not an img file. HELP lol!
Jon.StatiK said:
Ran into a pretty big issue here and I'm not sure where to go. I've downloaded the HDX Mokee version and flashed it with the GAPPS from this thread. All went well until I rebooted and I see is a white box and then it boots into Chinese? A screen with a button came up and naturally I was gonna try to go through the installation so I pushed it and it rebooted my device into TWRP. TWRP went into a boot loop. So, I reboot into the bootloader and reflashed TWRP. I can now access twrp BUT there's NOW a password attached to my device...how the hell? I went to reflash the Mokee zip in bootloader thinking maybe it was a bad flash but i cant as it's a zip and not an img file. HELP lol!
Click to expand...
Click to collapse
you dont have a password attached to your device? id try like 0000 or 1111.
Jon.StatiK said:
Ran into a pretty big issue here and I'm not sure where to go. I've downloaded the HDX Mokee version and flashed it with the GAPPS from this thread. All went well until I rebooted and I see is a white box and then it boots into Chinese? A screen with a button came up and naturally I was gonna try to go through the installation so I pushed it and it rebooted my device into TWRP. TWRP went into a boot loop. So, I reboot into the bootloader and reflashed TWRP. I can now access twrp BUT there's NOW a password attached to my device...how the hell? I went to reflash the Mokee zip in bootloader thinking maybe it was a bad flash but i cant as it's a zip and not an img file. HELP lol!
Click to expand...
Click to collapse
Start over from scratch. Word to the wise. Avoid the China based roms. There is a reason they are only on China based devices.
zelendel said:
Start over from scratch. Word to the wise. Avoid the China based roms. There is a reason they are only on China based devices.
Click to expand...
Click to collapse
So take it back to stock recovery and rom and then start over from there? Currently I can't flash anything in twrp. It's all bootloader.
Jon.StatiK said:
So take it back to stock recovery and rom and then start over from there? Currently I can't flash anything in twrp. It's all bootloader.
Click to expand...
Click to collapse
flash a factory image, become completely stock again. if you want to, reroot and flash twrp as well. then if you want, try flashing that rom again.
zelendel said:
Start over from scratch. Word to the wise. Avoid the China based roms. There is a reason they are only on China based devices.
Click to expand...
Click to collapse
simms22 said:
flash a factory image, become completely stock again. if you want to, reroot and flash twrp as well. then if you want, try flashing that rom again.
Click to expand...
Click to collapse
Yea, thanks. I went ahead and went back to stock. Everything seems good now.
Thanks.
Related
Hey,
I dont know how different things are now, i installed a RUU with lollipop and i've been trying to flash TWRP but after i try to get into recovery and i got stuck at the logo with "entering into recovery...", adb detects device and nothing happens, tried to delete cache still didnt work. I bet i'm missing something as stupid as a simple boot...
Terramoto said:
Hey,
I dont know how different things are now, i installed a RUU with lollipop and i've been trying to flash TWRP but after i try to get into recovery and i got stuck at the logo with "entering into recovery...", adb detects device and nothing happens, tried to delete cache still didnt work. I bet i'm missing something as stupid as a simple boot...
Click to expand...
Click to collapse
you flash the recovery for the m7wls.
Aldo101t said:
you flash the recovery for the m7wls.
Click to expand...
Click to collapse
what kind of statement was that? Or was it a question? Yep i flashed m7wls isn't that sprint version of TWRP?
EDIT: I think i know what you mean, TWRP is not working well with lollipop, is that it?
Terramoto said:
what kind of statement was that? Or was it a question? Yep i flashed m7wls isn't that sprint version of TWRP?
EDIT: I think i know what you mean, TWRP is not working well with lollipop, is that it?
Click to expand...
Click to collapse
no just checking you installed the correct recovery, for lollipop you should have the latest recovery, that's all
I can't either get root or flash a ROM without access to recovery?
what else can i do?
Terramoto said:
what else can i do?
Click to expand...
Click to collapse
Reflash latest firmware from here http://forum.xda-developers.com/showthread.php?t=2795856 (i recommend Modified Firmware....removed hboot, recovery & boot (fastboot flashable))
Then flash latest recovery twrp-2.8.6.0-m7wls..
crazykas said:
Reflash latest firmware from here http://forum.xda-developers.com/showthread.php?t=2795856 (i recommend Modified Firmware....removed hboot, recovery & boot (fastboot flashable))
Then flash latest recovery twrp-2.8.6.0-m7wls..
Click to expand...
Click to collapse
Didnt work, it tries to enter recovery but its like there's no recovery. The phone's not letting me flash the recovery only the stock one
Terramoto said:
Didnt work, it tries to enter recovery but its like there's no recovery. The phone's not letting me flash the recovery only the stock one
Click to expand...
Click to collapse
Did you flash the firmware first?
crazykas said:
Did you flash the firmware first?
Click to expand...
Click to collapse
yeah, i flashed the modified first then tried to flash recovery, it just wont go into recovery. Is there a way to downgrade back to kitkat? Everything was working good with kk, i had to replace the display, camera and battery so i flashed lollipop RUU thinking there wouldnt be any difference... Now i can't even get root
Terramoto said:
yeah, i flashed the modified first then tried to flash recovery, it just wont go into recovery. Is there a way to downgrade back to kitkat? Everything was working good with kk, i had to replace the display, camera and battery so i flashed lollipop RUU thinking there wouldnt be any difference... Now i can't even get root
Click to expand...
Click to collapse
Was there any error when you flashing recovery?It just doesn't boot to recovery?Then you should flash FULL RUU..It should be the fix
crazykas said:
Was there any error when you flashing recovery?It just doesn't boot to recovery?Then you should flash FULL RUU..It should be the fix
Click to expand...
Click to collapse
no error, everything went smooth its just the boot part, funny thing is im able to flash and boot twrp 2.5.0.0 but im not able to use it because it doesnt respond to touch. I'm currently with stock recovery but i'd like to root and remove crappy apps from my phone :\
Terramoto said:
no error, everything went smooth its just the boot part, funny thing is im able to flash and boot twrp 2.5.0.0 but im not able to use it because it doesnt respond to touch. I'm currently with stock recovery but i'd like to root and remove crappy apps from my phone :\
Click to expand...
Click to collapse
i faced that prob too,but i just had to update to latest firmware & recovery.Flash twrp 2.6.0 & try.
crazykas said:
i faced that prob too,but i just had to update to latest firmware & recovery.Flash twrp 2.6.0 & try.
Click to expand...
Click to collapse
I think i did that, isnt that what RUU's suppose to do?
Anyway, here's the log and last_kmsg if anyone knows how to trace this
log:
http://www.pastebin.ca/2978960
Last_kmsg:
http://pastebin.ca/2978961
@mdmower
I was told that since i replaced parts i might have replaced a part thats not the same as the original one and that i would need to make a custom recovery. I've already download the kmsg report (http://pastebin.com/USayUFqx) i just need some eyes that understand whats happening.
Hi everyone! So right now, I am on vacation, and I was messing around with my Nexus 6 when I decided to lower my DPI as I read that that would raise my battery life. So I did so, but as I was rebooting, I got stuck in a bootloop, with a message that read: "Android is starting; starting apps..." and then the screen would go black and it would start all over, indefinitely. So then I went into TWRP recovery and went to erase, but I accidentally erased everything. How do I get the OS back on the phone? I have the .tar file for the OS from Google's website, and I have ADB installed and prepped on my laptop, but how to I do the flash? Thanks!
Mod3 said:
Hi everyone! So right now, I am on vacation, and I was messing around with my Nexus 6 when I decided to lower my DPI as I read that that would raise my battery life. So I did so, but as I was rebooting, I got stuck in a bootloop, with a message that read: "Android is starting; starting apps..." and then the screen would go black and it would start all over, indefinitely. So then I went into TWRP recovery and went to erase, but I accidentally erased everything. How do I get the OS back on the phone? I have the .tar file for the OS from Google's website, and I have ADB installed and prepped on my laptop, but how to I do the flash? Thanks!
Click to expand...
Click to collapse
Mount as MTP in TWRP an transfer a ROM from your laptop. You may need to use fastboot and run:
fastboot format userdata
But just try to transfer a ROM first.
Evolution_Freak said:
Mount as MTP in TWRP an transfer a ROM from your laptop. You may need to use fastboot and run:
fastboot format userdata
But just try to transfer a ROM first.
Click to expand...
Click to collapse
I tried that, but my ROM is the stock Android ROM from Google's website, and it seems that TWRP can't flash a .tar file. Could I convert it to a functioning .zip somehow?
Mod3 said:
I tried that, but my ROM is the stock Android ROM from Google's website, and it seems that TWRP can't flash a .tar file. Could I convert it to a functioning .zip somehow?
Click to expand...
Click to collapse
I'm sorry I didn't know you were trying to flash a factory image. I would recommend downloading a ROM from the development section, something close to stock, and use that to get up and running first. Then you can return to stock if that is what you are trying to do.
Evolution_Freak said:
I'm sorry I didn't know you were trying to flash a factory image. I would recommend downloading a ROM from the development section, something close to stock, and use that to get up and running first. Then you can return to stock if that is what you are trying to do.
Click to expand...
Click to collapse
Thank you! It's up an running again! But how do I flash the stock ROM now?
Mod3 said:
Thank you! It's up an running again! But how do I flash the stock ROM now?
Click to expand...
Click to collapse
Read the sticky threads in general. All our guides are there.
I had TWRP installed and enrolled in the beta program. I just downloaded the official 7.0 through the push notification and clicked, "Restart and Install." Now, my phone boots automatically into TWRP. I've turned it off, then back on and same thing. Any ideas how to get out of this?
Boot into bootloader from recovery and select start.
prestige777 said:
Boot into bootloader from recovery and select start.
Click to expand...
Click to collapse
Yeah but it still can't install the update,any way fix it?
Boot to bootloader and flash the stock recovery from factory image. Then boot into stock recovery and the update should start.
The same happened to me. Disappointing, since the previews all worked (for me) in TWRP.
I just downloaded the OTA and sideloaded it, flashed TWRP, rebooted into TWRP and installed SuperSU 2.78. Worked fine.
https://developers.google.com/android/nexus/ota#shamu
dahawthorne said:
The same happened to me. Disappointing, since the previews all worked (for me) in TWRP.
I just downloaded the OTA and sideloaded it, flashed TWRP, rebooted into TWRP and installed SuperSU 2.78. Worked fine.
https://developers.google.com/android/nexus/ota#shamu
Click to expand...
Click to collapse
May I ask which version of TWRP did you use?
twrp-3.0.2-0-shamu.img
you cant flash an official factory image in twrp..this is a known fact...
Is that comment aimed at me? Did you actually read my post? Can you point me at the relevant part where I get it wrong?
Feel free to apologise any time.
dahawthorne said:
Is that comment aimed at me? Did you actually read my post? Can you point me at the relevant part where I get it wrong?
Feel free to apologise any time.
Click to expand...
Click to collapse
You are side loaded ota then flash twrp . But in op he was flashed ota via twrp and now os corrupted and he is not able to boot into system. All ota can flashed via stock recovery , i think. He have to flash firmware now via fast boot. Am i correct . If anything wrong ,you can correct.
Everybody should be friends in XDA.
It seems that people don't read posts before writing. The OP clearly said that he had applied the OTA. I clearly said that this was exactly what I did with the same result. I also clearly explained what I did to fix it. The next comment should be from the OP saying what he's doing to recover. If he does what I did he'll be fine.
drmuruga said:
You are side loaded ota then flash twrp . But in op he was flashed ota via twrp and now os corrupted and he is not able to boot into system. All ota can flashed via stock recovery , i think. He have to flash firmware now via fast boot. Am i correct . If anything wrong ,you can correct.
Everybody should be friends in XDA.
Click to expand...
Click to collapse
He can reinstall stock recovery and side load from there
Either flash the stock recovery.img through twrp or
Flash stock recovery through fastboot or
Install factory image through fastboot
Edit: oops didn't read the entire thread
itsagood said:
I had TWRP installed and enrolled in the beta program. I just downloaded the official 7.0 through the push notification and clicked, "Restart and Install." Now, my phone boots automatically into TWRP. I've turned it off, then back on and same thing. Any ideas how to get out of this?
Click to expand...
Click to collapse
To avoid issues, I'd say make sure you're 100% stock, recovery and all before installing an official update. Like I said, just to be sure it won't fail.
I got the the OTA notification before work yesterday. All day at work I was itching to install it but with no PC I couldn't risk it. I was on the DP5 with TWRP, no root, and unlocked. I couldn't wait. I flashed the OTA with TWRP after I restored a backup of when I first installed DP5. TWRP throw a couple of errors but after about 10 minutes of hanging on the boot animation it finally booted. My phone was encrypted but other then that it was fine. I was gonna root it afterwards but I was on stock recovery after flashing the OTA so I couldn't do anything until I got home. Made a noforc-nonverify boot IMG throw on TWRP reformatted. Running great now.
Edit: My DP5 boot.img was also noforc-nonverify.
Sent from my Nexus 6
I was trying to fix my google play "no connection error" but it didn't work so i just reset my phone as a last resort to try and fix this problem. It restarted in recovery mode i thought this was just a procedure and i just hit reboot -> system. it rebooted again into recovery mode i checked if there were any wtuck volume rockers but there aren't any help?
(FYI: one plus 3T: Rooted)
(FYI: link to what i used to try and fix my google play store:https: //forum.xda-developers.com/showthread.php?t=2273994)
What recovery are you running? Stock or TWRP?
bealer said:
What recovery are you running? Stock or TWRP?
Click to expand...
Click to collapse
TWRP
And telling TWRP to boot system just bring you back into TWRP?
Hmm... sounds like you might need to reflash whatever rom you were on.
bealer said:
And telling TWRP to boot system just bring you back into TWRP?
Hmm... sounds like you might need to reflash whatever rom you were on.
Click to expand...
Click to collapse
already did that but still brings me back into TWRP
TrappleV3 said:
already did that but still brings me back into TWRP
Click to expand...
Click to collapse
This happened to me. I installed custom rom then I went into fastboot and installed stock recovery. I would search in this forum for the stock recovery img file. Once installed, I rebooted and it loaded the rom. I had this problem on the latest twrp version. I installed the previous twrp and I am all good now.
Droid-2 said:
This happened to me. I installed custom rom then I went into fastboot and installed stock recovery. I would search in this forum for the stock recovery img file. Once installed, I rebooted and it loaded the rom. I had this problem on the latest twrp version. I installed the previous twrp and I am all good now.
Click to expand...
Click to collapse
you have a link to the file because i can't seem to find it. But thank you anyway for your help.
TrappleV3 said:
you have a link to the file because i can't seem to find it. But thank you anyway for your help.
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-3t/how-to/zip-flashable-firmware-modem-t3509015
mximer said:
https://forum.xda-developers.com/oneplus-3t/how-to/zip-flashable-firmware-modem-t3509015
Click to expand...
Click to collapse
Thank You.
Issue has been resolved. OP is my little cousin who's been messing around a bit too frantically [emoji14]
I restored his device with the unbrick tool by Haris K., all's peachy again. There are still some issues with TWRP for 3T, doesn't run nearly as smooth as on the OPO. It completely failed to restore any working system (both from backup or from reflashing). Sideloading seemingly worked, but rebooted to recovery again, adb push only resulted in errors. Are there any tweaked TWRP releases that can do better?
Cooked with Resurrected bacon!
Hello, I've softbricked a fair amount of phones and tablets in my time but I must admit never had this show up. After flashing Twrp and a dm-verity thingy, I received this shiny new error on my new 1+3t. While I'm assuming it's a straightforward fix such as:
Booting into Twrp and flashing stock 4.x Oxygen os and the stock recovery to bring phone back to where I started.
My question is, can't I just go straight about flashing a rom? I.e freedom rom, or is it advisable to just try start again?
And is me flashing stock os then recovery got to work?
Everything is still stock there is no root. All I have done is:
Code:
fastboot > oemunlock > reboot > fastboot flash Twrp > Twrp boot > Twrp > swiped to Modify > flashed dm-verity.
I did receive a password request first time round but after I rebooted phone it wasn't there again.
Thank you for helping in advance.
Archtects said:
Hello, I've softbricked a fair amount of phones and tablets in my time but I must admit never had this show up. After flashing Twrp and a dm-verity thingy, I received this shiny new error on my new 1+3t. While I'm assuming it's a straightforward fix such as:
Booting into Twrp and flashing stock 4.x Oxygen os and the stock recovery to bring phone back to where I started.
My question is, can't I just go straight about flashing a rom? I.e freedom rom, or is it advisable to just try start again?
And is me flashing stock os then recovery got to work?
Everything is still stock there is no root. All I have done is:
Code:
fastboot > oemunlock > reboot > fastboot flash Twrp > Twrp boot > Twrp > swiped to Modify > flashed dm-verity.
I did receive a password request first time round but after I rebooted phone it wasn't there again.
Thank you for helping in advance.
Click to expand...
Click to collapse
You had to flash supersu or Magisk after the process to disable force encryption also make sure your are on the nougat supported twrp 3.0.4-1 or later
You can flash any rom if you have an unlocked bootloader and a working twrp
Sent from my Funk Tuned 3T
Funk Wizard said:
You had to flash supersu or Magisk after the process to disable force encryption also make sure your are on the nougat supported twrp 3.0.4-1 or later
You can flash any rom if you have an unlocked bootloader and a working twrp
Click to expand...
Click to collapse
thanks I think that's where I went wrong. I should have flashed Magisk. The guide says so but I only intended to flash a rom. Eh. I'll see if I can flash Magisk. All is not lost. I'll update once I get home. I'm annoyed with my self lol.
-101 xda points
Archtects said:
thanks I think that's where I went wrong. I should have flashed Magisk. The guide says so but I only intended to flash a rom. Eh. I'll see if I can flash Magisk. All is not lost. I'll update once I get home. I'm annoyed with my self lol.
-101 xda points
Click to expand...
Click to collapse
No prob buddy, let me know if you get stuck anywhere :fingers-crossed:
Sent from my OnePlus 3T using XDA Labs
Funk Wizard said:
No prob buddy, let me know if you get stuck anywhere :fingers-crossed:
Click to expand...
Click to collapse
I will do, hopefully it be fine. I'll try different thing if stuff doesn't work and I'll post back what I did incase anyone else has similar problem .
Twrp doesn't see any internal storage what so ever. So Ive flashed stock recovery from fastboot and going to attempt to sideload the stock OS. fingers-crossed
Funk Wizard said:
No prob buddy, let me know if you get stuck anywhere :fingers-crossed:
Click to expand...
Click to collapse
Thanks for your help im back to a working phone!
For anyone who get stuck!
1) download op3t stock recovery and the oxygen OS from oneplus website
2) boot into fastboot.
3) with your pc get up Adb and:
Code:
fastboot flash recovery stock.img
Fastboot boot stock.img
[\CODE]
4) Once you boot into recovery navigate to install from adb.
5) in cmd again on pc type
[CODE] adb sideload filename.zip
[\CODE]
6) then reboot :). You can leave it here if you want.
So I'm back on stock. With Magisk installed. Only dm-verity still come up which I'm not keen on. But I guess I can live with it. But I'm stuck with a bunch of system apps I can't get rid of? I've tried titanium backup, and link2sd my go to but nothing any ideas? Anyone now how to get rid?
Archtects said:
So I'm back on stock. With Magisk installed. Only dm-verity still come up which I'm not keen on. But I guess I can live with it. But I'm stuck with a bunch of system apps I can't get rid of? I've tried titanium backup, and link2sd my go to but nothing any ideas? Anyone now how to get rid?
Click to expand...
Click to collapse
I can recommend OOS Aroma Debloater Credits: @siankatabg :good:
Funk Wizard said:
I can recommend OOS Aroma Debloater Credits: @siankatabg :good:
Click to expand...
Click to collapse
Cheers I found the zip you. Mentioned after I posted the question, worked sort of lol. Some still won't go but it's got rid of a fair chunk an dive just frozen any I don't want.