Hello,
I used oneplus 3t toolkit to force decryption and then was able to boot into rom
But when I go to TWRP it just gives black screen with continuous led light on.
I tried flashing twrp again with same toolkit, ends with success message but still not able to get into twrp.
Please help
Same Problem here...
Alter flashing twrp I First was able to Start it and Flash supersu and debloat. Now I just get a white LED.
Booting to oos 4.0 works fine.
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
Freeze on Pecovery screen
I am running leaked version Nougat (build 19-12-2016) and phone starts normal. Phone is rooted. When I start in recovery...phone freezes on recovery logo image (team-win) screen. So no more possible to get in menu of recovery. I also flashed other recovery via fastboot (3.0.2.0, 3.0.2.1 and 3.0.3.0) but same issue. What to do??
Edit...after more than 1 minut waiting time on recovery screen 3.0.3.0 got further in menu.
Solex49 said:
I am running leaked version Nougat (build 19-12-2016) and phone starts normal. Phone is rooted. When I start in recovery...phone freezes on recovery logo image (team-win) screen. So no more possible to get in menu of recovery. I also flashed other recovery via fastboot (3.0.2.0, 3.0.2.1 and 3.0.3.0) but same issue. What to do??
Edit...after more than 1 minut waiting time on recovery screen 3.0.3.0 got further in menu.
Click to expand...
Click to collapse
Did you do anything other than flash the older version of TWRP? After the Nougat update when I boot into recovery it only boots to the stock recovery. I've flashed numerous versions of TWRP and even run the following command to force the boot into TWRP (this worked for me last time) 'fastboot boot twrp-3.0.3-0-oneplus3t.img'. Still no luck. All I get is the TWRP splashscreen for 15+ minutes.
AustinVillan said:
Did you do anything other than flash the older version of TWRP? After the Nougat update when I boot into recovery it only boots to the stock recovery. I've flashed numerous versions of TWRP and even run the following command to force the boot into TWRP (this worked for me last time) 'fastboot boot twrp-3.0.3-0-oneplus3t.img'. Still no luck. All I get is the TWRP splashscreen for 15+ minutes.
Click to expand...
Click to collapse
Nil...can't remember anymore what I have done more. Maybe better to install original full Rom 4.0.2 and thereafter root again..
Related
Whenever my recovery is TWRP I am not able to boot into any type of ROM. Every time I reboot my phone it will be past the "your bootloader is unlock" and always boots straight into TWRP. When I flash stock recovery I am stuck at a image of a Android and it just stays at "erasing..." till it reboots itself. I have attempted to flash different types of roms by sideloading through TWRP and also attempted to flash stock recovery through fastboot with no luck at all.
The issue started whenever I was on stock 6.0 and flashed TWRP. Once I was in TWRP at the end when I was rebooting my phone I said yes to install supersu, which I know now was a mistake. Afterwards I was stuck in a bootloop were I finally attempted to do a factory reset which seemed to have made things worse. That was when I was stuck at the "erasing..." whenever I attempted to boot through stock recovery. Not sure what else to try at this point.
Any help would be great at this point.
I'm in the same boat. Exact same problem with no idea how to fix. I can get into fastboot screen, but that's it. Suggestions? Thanks in advance.
Hello Guys,
Yesterday I tried to root my Moto 2g.
Unlocked it's bootloader,Installed Twrp and installed supersu. Also downloaded a custom mod(the most famous one I guess) and installed it,only to find out that the phone would no longer boot
but keep looping on the unlocked bootloader warning screen.While thinking that I had downloaded a non-compatible mod I Installed another one.After that,booting the phone would Instantly
take me to the recovery mode and keep looping the Teamwin logo.
I decided not to mess anymore with it and reinstall the stock firmware for moto 2g. After Installing it the Motorola logo comes up and then I am taken to the fastboot screen once again with the error saying:
"Fastboot reason,Fell through from boot recovery mode".Tried to flash CWM to see If I could get into recovery mode from there but I would get CWM logo loops exactly the same way they appeared with Teamwin logo.
Seems like phone is dead to me but still have a bit of hope,although the only place I can get is fastboot.
Edit:I tried to fastboot flash boot boot.img the stock image and I got and error saying that boot.img(10mb) exceeded the partition limit
shatterbb said:
Hello Guys,
Yesterday I tried to root my Moto 2g.
Unlocked it's bootloader,Installed Twrp and installed supersu. Also downloaded a custom mod(the most famous one I guess) and installed it,only to find out that the phone would no longer boot
but keep looping on the unlocked bootloader warning screen.While thinking that I had downloaded a non-compatible mod I Installed another one.After that,booting the phone would Instantly
take me to the recovery mode and keep looping the Teamwin logo.
I decided not to mess anymore with it and reinstall the stock firmware for moto 2g. After Installing it the Motorola logo comes up and then I am taken to the fastboot screen once again with the error saying:
"Fastboot reason,Fell through from boot recovery mode".Tried to flash CWM to see If I could get into recovery mode from there but I would get CWM logo loops exactly the same way they appeared with Teamwin logo.
Seems like phone is dead to me but still have a bit of hope,although the only place I can get is fastboot.
Edit:I tried to fastboot flash boot boot.img the stock image and I got and error saying that boot.img(10mb) exceeded the partition limit
Click to expand...
Click to collapse
try flashing the whole Stock Firmware
It might help,
U said u flashed a MOD over stock ROM?
If so, u should have boot first Just After unlocking the bootloader before Flashing any MODs
raj_45 said:
try flashing the whole Stock Firmware
It might help,
U said u flashed a MOD over stock ROM?
If so, u should have boot first Just After unlocking the bootloader before Flashing any MODs
Click to expand...
Click to collapse
I did boot after unlocking and normally flashed whole stock firmware.This morning I woke up and the error message in fastboot is 'boot up failed' for bot normal and recovery mode
shatterbb said:
I did boot after unlocking and normally flashed whole stock firmware.This morning I woke up and the error message in fastboot is 'boot up failed' for bot normal and recovery mode
Click to expand...
Click to collapse
is this your problem
raj_45 said:
is this your problem
Click to expand...
Click to collapse
Ok let me explain the situation better.Last night I used a stock firmware I found and flashed it.When I tried to boot I would see motorola logo once
fore boot mode,Then it would go to recovery so I would see it for a second time and then I would see teamwin logo looping so the phone was not
able to get into recovery mode but only into bootloader.
After That I flashed CWM and the same thing would happen with CWM logo looping now in recovery mode.
Today I woke up and flashed CWM again,and for some reason I could get into CWM and use it normally
So what I did is Installed Supersu and a mod for my xt1068 and tried to boot but phone stuck in the same endless loop again and I also cant get
into CWM again as its logo keeps flashing instead of taking me into the menu.
I believe there is an error with my data folder or partition or w/e.
Most of all I want to be able to get into CWM again
shatterbb said:
Ok let me explain the situation better.Last night I used a stock firmware I found and flashed it.When I tried to boot I would see motorola logo once
fore boot mode,Then it would go to recovery so I would see it for a second time and then I would see teamwin logo looping so the phone was not
able to get into recovery mode but only into boot loader.
After That I flashed CWM and the same thing would happen with CWM logo looping now in recovery mode.
Today I woke up and flashed CWM again,and for some reason I could get into CWM and use it normally
So what I did is Installed Supersu and a mod for my xt1068 and tried to boot but phone stuck in the same endless loop again and I also cant get
into CWM again as its logo keeps flashing instead of taking me into the menu.
I believe there is an error with my data folder or partition or w/e.
Most of all I want to be able to get into CWM again
Click to expand...
Click to collapse
So u are not able to get into Recovery
And u can get to Fast boot Mode?
If yes Flash TWRP latest(3..1.0-0)
Boot into TWRP
Reset or Install any Custom ROM like LiniageOS or AOSP
I think it's the problem with SuperSU?
Which MOD did u install?
raj_45 said:
So u are not able to get into Recovery
And u can get to Fast boot Mode?
If yes Flash TWRP latest(3..1.0-0)
Boot into TWRP
Reset or Install any Custom ROM like LiniageOS or AOSP
I think it's the problem with SuperSU?
Which MOD did u install?
Click to expand...
Click to collapse
Thanks for the replies,I managed to solve the problem and install Cyanogenmod.I guess everything came up to this:
After the first time I installed twrp I decided to wipe my data folder but somehow it was deleted and the partition became raw type which caused
all the bootlooping problems.
Using CWM I was able to get into recovery mode and then I chose to format my data folder and sd card(as ext4 I guess) and the data folder was
recreated.
After that I normally flashed Cyanogenmod and device booted just fine
Hi guys.
I can't install TWRP on my CHE2-L11 with terminal emulator (dd if=/sdcard........ ) neither with fastboot.
The strangest thing is that every method says success message bbut when I reboot, the phone always boots into stock recovery.
I remember that about two years ago I managed to install before cwm, and about 2 months later twrp without any problem.
Now I'd like to install RR rom, but I'm still can't install this damn recovery.
Anyone can help me?
Thanks.:fingers-crossed:
Are you sure it boots to recovery and not to eRecovery. (What options it has.) Otherwise it's very weird that it boots to stock recovery after using dd.
No, I'm not... is that eRecovery?
https://www.google.it/search?q=eRec...rmd=ivsn&biw=458&bih=733#imgrc=2Sr1sxsjXA5qtM
Anyway, how to boot into twrp if fastboot command "fastboot reboot recovery" doesn't work?
I downloaded and installed the official Pie update today, then procedeed to unlock the bootloader which was a success. However now I found that the phone wont boot (not flash) a custom recovery (latest TWRP).
I'm only interested into booting a custom recovery so I can root, otherwise I'd prefer the phone to remain as close to stock as possible.
When trying to boot into TWRP using "fastboot boot twrp.img", I get a success message, phone reboots and then gets stuck at the Android Logo (fastboot commands still work, it doesnt say 'download mode' tho).
Any solutions?
Hello, i have a Mi8 global version, unlocked and actually i'm on latest xiaomi.eu dev (9.1.24), but i have some problems with twrp and custom kernels.
I don't know why, but almost every recovery won't boot.
Actually i'm on TWRP 3.2.2-0711 (the only one that works) and managed to flash xiaomi.eu rom as written before.
But every other recovery on the forum won't boot, tried to flash and boot from cmd, only boot from cmd, flash with some tools, flash and with apps from playstore, restart from cmd with vol up, disconnect phone and use keys combination, but same result: only 3.2.2 works.
Every other recovery i try to flash does nothing, it just reboots normally without enter in twrp.
I have similar problem with custom kernel: only francoKernel_r4 boots fine. With every other miui compatible kernel i have bootloop.
I've tried to reflash fastboot rom with XiaomiFlash but still have same results.
Can anyone help me please? I have no more ideas what to do
IronJacob said:
Hello, i have a Mi8 global version, unlocked and actually i'm on latest xiaomi.eu dev (9.1.24), but i have some problems with twrp and custom kernels.
I don't know why, but almost every recovery won't boot.
Actually i'm on TWRP 3.2.2-0711 (the only one that works) and managed to flash xiaomi.eu rom as written before.
But every other recovery on the forum won't boot, tried to flash and boot from cmd, only boot from cmd, flash with some tools, flash and with apps from playstore, restart from cmd with vol up, disconnect phone and use keys combination, but same result: only 3.2.2 works.
Every other recovery i try to flash does nothing, it just reboots normally without enter in twrp.
I have similar problem with custom kernel: only francoKernel_r4 boots fine. With every other miui compatible kernel i have bootloop.
I've tried to reflash fastboot rom with XiaomiFlash but still have same results.
Can anyone help me please? I have no more ideas what to do
Click to expand...
Click to collapse
Did you know this thread?
https://xiaomi.eu/community/threads...neage-compatible-global-rom-compatible.48432/
lolo9393 said:
Did you know this thread?
https://xiaomi.eu/community/threads...neage-compatible-global-rom-compatible.48432/
Click to expand...
Click to collapse
No i did know. Just tried but both twrp don't work.
Btw i'll try to write in that thread too.
Thank you
Fastboot flash the recovery img, then fastboot boot the recovery img.
Then reflash recovery zip file from within twrp you just fastboot booted
https://forum.xda-developers.com/showpost.php?p=78693530&postcount=71
Use TWRP 3.2.3-1208 version from OP in this link
Stoffl_ said:
Fastboot flash the recovery img, then fastboot boot the recovery img.
Then reflash recovery zip file from within twrp you just fastboot booted
https://forum.xda-developers.com/showpost.php?p=78693530&postcount=71
Use TWRP 3.2.3-1208 version from OP in this link
Click to expand...
Click to collapse
As written on eu forum, the only recovery working is the 3.2.2.
Every other recovery, 1208 too give me:
Mi logo (unlocked) - black screen - Mi logo (unlocked) - system. But no recovery.
Tried to flash a custom rom different to xiaomi.eu but got bootloop, same with kernel flashable zips on xda. Only bootlooo...
I really don't know what to do anymore...
Yeah weird, I've literally guided a friend through the process just yesterday with that method.
Zero issues