I opened a new thread because i haven't found a solution
my problem:
- black screen after motorola boot animation
- not working if i restore firmare (5.0.2 or 4.4.4) o if i flash a custom recovery, seem that doesn't write because sometimes i get for 1 second "booting applications" popup with Lollipop theme (also if i flash kitkat), also recovery remains stock if i flash twrp.
bootloader is unlocked
thank you
Related
EDIT : I got rid of the problem and managed to root my phone.
I'm having trouble rooting the K3 note flashed with VIBE UI 3.0. I'm using Lenovo K50a40, Indian Version and I flashed the Dev version of Vibe UI ROM (v 3.0 from hackerpower's signature) . The flashing went all fine. Then I tried to reroot the phone but I noticed that the recovery was the stock one. So I proceeded to reflash the recovery using fastboot but it showed that the file had been downloaded but could not be flashed to the recovery partition. I thought of using SP Flash Tool to flash the recovery. I flashed AthlonX's material TWRP recovery and it flashed okay. Then on rebooting the phone I find it remains stuck on the boot logo with Lenovo written on white backdrop. There's also text written in a small black strip on the bottom left which says "=>Tool DL Image Fail" . The phone stays on that screen for a minute or two and then goes out. Earlier I couldn't boot into the phone due to the above mentioned problem. Then I waited for the battery to drain and then powered the phone on normally (without pressing the button combination for recovery mode) and the phone booted up just fine but the recovery was the stock one .
From all this, there's one thing I've concluded- that this phone has some kind of defense mechanism that protects against installing a custom recovery. This occurred even when I tried rooting on Stock 2.5 VIBE UI. That time I overcame the problem by flashing recovery using fastboot and then booting directly into the recovery instead of system. Now, however, fastboot isn't able to flash the recovery (the transfer of the image is successful but the flashing fails) .
Finally, I request anyone who can help me in any way to Root the phone or to get a recovery installed to please reply.
Thanks.
how were you able to root it
Lord AJ said:
EDIT : I got rid of the problem and managed to root my phone.
I'm having trouble rooting the K3 note flashed with VIBE UI 3.0. I'm using Lenovo K50a40, Indian Version and I flashed the Dev version of Vibe UI ROM (v 3.0 from hackerpower's signature) . The flashing went all fine. Then I tried to reroot the phone but I noticed that the recovery was the stock one. So I proceeded to reflash the recovery using fastboot but it showed that the file had been downloaded but could not be flashed to the recovery partition. I thought of using SP Flash Tool to flash the recovery. I flashed AthlonX's material TWRP recovery and it flashed okay. Then on rebooting the phone I find it remains stuck on the boot logo with Lenovo written on white backdrop. There's also text written in a small black strip on the bottom left which says "=>Tool DL Image Fail" . The phone stays on that screen for a minute or two and then goes out. Earlier I couldn't boot into the phone due to the above mentioned problem. Then I waited for the battery to drain and then powered the phone on normally (without pressing the button combination for recovery mode) and the phone booted up just fine but the recovery was the stock one .
From all this, there's one thing I've concluded- that this phone has some kind of defense mechanism that protects against installing a custom recovery. This occurred even when I tried rooting on Stock 2.5 VIBE UI. That time I overcame the problem by flashing recovery using fastboot and then booting directly into the recovery instead of system. Now, however, fastboot isn't able to flash the recovery (the transfer of the image is successful but the flashing fails) .
Finally, I request anyone who can help me in any way to Root the phone or to get a recovery installed to please reply.
Thanks.
Click to expand...
Click to collapse
i have been using the sp flash tool to download the recovery i want and every time goes back to the stock one
obviously i lost my gapps with the update
but i dont have the google play services issue since i had to re install stock rom and never update google services and just when ahead and applied the updates 2.8 and 3.0,
do you have any ideas
daniiaroxyo said:
i have been using the sp flash tool to download the recovery i want and every time goes back to the stock one
obviously i lost my gapps with the update
but i dont have the google play services issue since i had to re install stock rom and never update google services and just when ahead and applied the updates 2.8 and 3.0,
do you have any ideas
Click to expand...
Click to collapse
If the recovery goes back to stock then you should probably try to boot into the recovery before rebooting to system after SP Flash Tool has done it's job.
Hi so I down loaded one more time the recovery thru sp tool
But this time I took the battery out for few seconds instead of rebooting right away
And it worked
Once I rooted back the phone I tried flashing the gapps but it didn't work
I tried changing the permission s thru root explorer for the google base app as I so on a post and nothing
Any ideas
hello guys ...i am trying to install/update on stock kitkat rom on my htc vivid currently having stock gingerbread...
1. i have tried using PH39IMG.zip (stock at&t rom) by copying it in sdcard...update goes smooth and installation is successful...but later when i reboot the mobile, it gets stuck on white screen which green htc logo
2. then i tried updating it using htc sync and stock at&t RUU...it gives the error 132:signature problem
3. tried installing rom via twrp and cwm recoveries ...installation is smooth without any problem but the result is same that when i reboot the mobile, it gets stuck on white screen which green htc logo
4. i also tried to restore backup via cwm recovery ...again the result is when i reboot the mobile, it gets stuck on white screen which green htc logo...
my boot loader is unlocked when i tried PH39IMG.zip, CWM and TWRP recoveries for stock rom (relocked it when required for RUU).....but S lock is ON.....do i need to have S-OFF for all this ??
I have a similar problem. I have an unlocked bootloader, S-on, an NO OS. The phone has an old version of TWRP on it that won't allow me to flash an image. The OS is gone because I removed it trying to remove a software bug in the factory OS. I'm used to flashing Samsung/ LG phones using ODIN and never had an issue just reflashing a stock ROM.
I'm just looking for a way to get the stock rom back on the phone with or without retaining the stock recovery.
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..
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
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?