I Unlocked the bootloader 3 days ago and flashed Cyanogenmod 12.1 with exact gapps and was able to use the phone perfectly ,today I searched for xposed and found that it could be only installed by manual flashing for android lollipop , so I downloaded the zip file and rebooted my phone in Recovery Mode [ TWRP ] and flashed the zip file just after that the phone stuck at bootloop. Restarted the phone 3 time's but no luck so finally I got into bootloader by pressing the volume down button and the power button and opened recovery mode to factory reset the phone and reflashed the CM 12.1 with gapps , now the problem begin's when I restarted the phone it is stuck at "Warning Bootloader Unlocked" and even the recovery mode is stuck at beginning screen of twrp , Im only able to use the bootloader . Even tried to reflash TWRP Recovery from computer but thier's no change it is still stuck at the recovery screen .
Any help would be really appreciated
try reflashing and then wiping cache's before rebooting ?
like the regular cache and dalvik cache.
also don't expect the first boot to work quick.. leave it for a long time...
good luck.
Actully the problem is , when i try to open recovery mode it stucks at teamwin logo (twrp)
"I searched for xposed and found that it could be only installed by manual flashing for android lollipop"
Click to expand...
Click to collapse
that quote is confusing.. what did you mean exactly.
What TWRP ? From Where + what version # ?
If i were you i would re-download it then MD5 hash it.. verify it !
I always check the md5 hashes on any phone roms or firmware etc.
I have had tons of incomplete downloads and there is nothing wrong with my internet connection either.
The more detailed you can be the more likely someone can help.
Once you are positive your TWRP is downloaded properly if i were you
i would re-flash it with fastboot. (if you can)
Can you power off the phone and put it in bootloader mode then connect to pc ?
power it off then hold volume down + power then plug in USB
then right click the empty space in the windows folder (assuming no Linux)
select open command prompt here then type:
adb devices
Is it listed ?
I also assumed you have "Minimal ADB and Fastboot" installed.
Sounds like you flashed a 5.1 firmware package ?
yes ? which one ?
And watch out many sites have cut off my download on me while downloading them.
and if you then flashed a half completed download you could prob damage the phone.
for checking hashes on windows i use HashSlash.. it's clean / free and has a GUI ..google it
Basically , first I flashed Android 5.1.1 AOSP for my device and then Cyanogenmod 12.1 Nightly Surnia . and yes I tried to reflash TWRP Recovery but it is stuck at the same Teamwin Logo screen , and i flashed the latest version of twrp which was available on xda . Can you provide me worth some kind of image file which I can flash to Factory reset my device from computer or anything else which can help.
And by the way Thanks for the quick reply
sabungolfer0011 said:
Basically , first I flashed Android 5.1.1 AOSP for my device and then Cyanogenmod 12.1 Nightly Surnia . and yes I tried to reflash TWRP Recovery but it is stuck at the same Teamwin Logo screen , and i flashed the latest version of twrp which was available on xda . Can you provide me worth some kind of image file which I can flash to Factory reset my device from computer or anything else which can help.
And by the way Thanks for the quick reply
Click to expand...
Click to collapse
https://mega.nz/#F!rMIhDLgR!oq5Cz_XbgZLEEysmqoYtcA
i used that.. but didn't flash my phone yet.
that is all firmware packages stock for Moto-2015
You still have not mentioned a lot like where did you get TWRP and what version ?
What carrier is your phone ?
I take it you unlocked the bootloader or did you get it like that ?
I'm guessing the bootloader loads TWRP
so either of those is probably damaged i bet.
I would try and get it stock then work from there getting TWRP back on and rooting etc.
What i was trying to ask you is..
Was your phone on 5.02 and you tried to update it to v5.1 ?
Because i have seen other people here who had problems with that.
Relocking the bootloader can cause problems and so can reverting to an old ver from 5.1 to 5.02
I used a custom kernel and TWRP from Squid here on the forum and rooted
and his kernel is only good for me up to version 5 but he has way newer versions out..
but they are only for users who updated to 5.1
So you have to be VERY careful what your doing.
I might have screwed up my phone if i didn't notice the fine print.
Also just search the forum for some guides on flashing firmware
and verify the downloads
My Bootloader is unlocked , TWRP Recovery Version 2.8.6.0 . My phone was on Android 5.0.2 [ Official Non Rooted ] , so I thought of updating it to 5.1.1 which was available as custom rom So I unlocked the bootloader flashed TWRP version 2.8.6.0 by copying Recovery.img in minimal adb folder and oped CMD and flashed the custom recory and it was no problem , then 2 days ago I flashed Cyanogenmod.12.1.Surnia.20150829.zip and it worked fine no issues then I flashed Xposed Modular in recovery mode , now when I tried to restart the system it stuck at bootloop so I entered Bootloader and again restarted 2, 3 times but no luck so I again entered bootloader and entered Recovery Mode ( TWRP 2.8.6.0) and wiped all my data , But unfortunately I was outside so I dint had the firmware and gapps so I switched the phone off in hope that ill flash the firmware and gapps when i reach back home . So when I vame back home and pasted the firmware and gapps in memory card and inserted it baxk in the phone and tried to enter recovery mode , that was the first time when I experied That teamwork logo stuck at recover mode and the further story you laready know
Related
My Moto E Hangs when I try to boot a TWRP image
Attempted procedure:
(After booting into stock fastboot)
Code:
fastboot boot twrp-2.7.1.0-condor.img
A reboot to that TWRP was expected instead. But it freezes on bootloader.
TWRP used on the attempt:
dl.twrp.me/condor/twrp-2.7.1.0-condor.img.html
I don't want to flash a different recovery or anything else, just a clean root.
Moto E XT1025 DTV Dual BR
4.4.4
21.12.40.condor_retbr_tv_ds.retvr.en.BR.retbr
LucasBS1 said:
My Moto E Hangs when I try to boot a TWRP image
Attempted procedure:
(After booting into stock fastboot)
Code:
fastboot boot twrp-2.7.1.0-condor.img
A reboot to that TWRP was expected instead. But it freezes on bootloader.
TWRP used on the attempt:
dl.twrp.me/condor/twrp-2.7.1.0-condor.img.html
I don't want to flash a different recovery or anything else, just a clean root.
Moto E XT1025 DTV Dual BR
4.4.4
21.12.40.condor_retbr_tv_ds.retvr.en.BR.retbr
Click to expand...
Click to collapse
Sometimes booting recovery doesn't work...You will have to flash it. Perhaps you can flash the stock recovery after successful root? though i am not sure that will work
Also try booting into CWM
Tried the same method with CWM.img
Same result: fastboot frozen (volume buttons not responsive, and PC no longer sends commands)
To flash the stock recovery I would need to back it up first
But guess what's needed to backup ?
Yes, a temporary flashed bootloader with ZIP support
Would you know someone, who knows someone, who knows an master from MTI or Hogwarts or Narnia that knows an alternative ?
I would flash a mod right away if I could backup the original first...
(Unless, as I don't know exactly how this works, the ROM might come with the bootloader (?) Because the stock ROM I can download easily anywhere (already did))
LucasBS1 said:
Tried the same method with CWM.img
Same result: fastboot frozen (volume buttons not responsive, and PC no longer sends commands)
To flash the stock recovery I would need to back it up first
But guess what's needed to backup ?
Yes, a temporary flashed bootloader with ZIP support
Would you know someone, who knows someone, who knows an master from MTI or Hogwarts or Narnia that knows an alternative ?
I would flash a mod right away if I could backup the original first...
(Unless, as I don't know exactly how this works, the ROM might come with the bootloader (?) Because the stock ROM I can download easily anywhere (already did))
Click to expand...
Click to collapse
Hi,
Did you managed it to work? I have exactly the same problem. If I even flash twrp or cwm I still can't boot into it, there is only "no command" message.
I can't get any help anywhere, it makes me crazy. Do you have any custom recovery that worked for you after flashing?? I'm even starting to think that my device is broken somehow.
giaur said:
Hi,
Did you managed it to work? I have exactly the same problem. If I even flash twrp or cwm I still can't boot into it, there is only "no command" message.
I can't get any help anywhere, it makes me crazy. Do you have any custom recovery that worked for you after flashing?? I'm even starting to think that my device is broken somehow.
Click to expand...
Click to collapse
I did NOT flash the recovery yet
I'm trying to run the recovery without flashing it, to avoid problems like yours
You said you flashed both CWM and TWRP ?
And Neither one of them worked ?
I'm screwed too, then...
:crying:
See if you can find the stock recovery somewhere
And NOT here
This forum is not good for it
It's too much phone specific... too narrow... and we get no attention; specially with our "not-mainstream" phone
Generic instruction could work
If you take any action, or find any forum you find helpful, let me know
@giaur @LucasBS1
I too have tried booting the recovery ,but it doesn't work. You will have to flash it
if you are seeing 'no command' message it means that you still have stock recovery and the custom recovery wasn't flashed successfully.
try this one http://forum.xda-developers.com/mot...recovery-twrp-2-8-2-0-touch-recovery-t2971601
or this one http://forum.xda-developers.com/mot...recovery-twrp-2-8-6-0-touch-recovery-t3100879
LucasBS1 said:
I did NOT flash the recovery yet
I'm trying to run the recovery without flashing it, to avoid problems like yours
You said you flashed both CWM and TWRP ?
And Neither one of them worked ?
I'm screwed too, then...
:crying:
See if you can find the stock recovery somewhere
And NOT here
This forum is not good for it
It's too much phone specific... too narrow... and we get no attention; specially with our "not-mainstream" phone
Generic instruction could work
If you take any action, or find any forum you find helpful, let me know
Click to expand...
Click to collapse
None of them worked. I'm going to resign, because there is nothing I can do. Seems you have exactly the same problem as me. What I tried:
- fastboot boot recovery.img. Phone hangs on bootlogo
- flash recovery, then use go to recovery option in fastboot menu. In this case, 2 possibilities: with usb cable connected, it boots normally to system, not to recovery. With usb cable disconnected, screen goes black and phone looks like powered off. You will need to power it on and it will boot to system.
- On running system with usb debugging enabled. If you type "adb reboot recovery", you will end with dead robot and "no command" error. You can however press VolUP +Power on this screen and you will see Android 3e recovery.
If you have the same problem as me, you are completly lost and it's impossible to intall recovery on your device. I'm close to resign and say "**** this ****ty phone" because (as you already mentioned), there is no any attention on my questions, twrp support was dropped long time ago etc.
Flashing recovery should not wipe your data, so once you try to flash twrp or cwm, please let me know about your results. I'm sure I will never able to solve this problem, but I will feel better knowing that I'm not alone whit it
---------- Post added at 06:05 PM ---------- Previous post was at 06:00 PM ----------
mepsilon2 said:
@giaur @LucasBS1
I too have tried booting the recovery ,but it doesn't work. You will have to flash it
if you are seeing 'no command' message it means that you still have stock recovery and the custom recovery wasn't flashed successfully.
try this one http://forum.xda-developers.com/mot...recovery-twrp-2-8-2-0-touch-recovery-t2971601
or this one http://forum.xda-developers.com/mot...recovery-twrp-2-8-6-0-touch-recovery-t3100879
Click to expand...
Click to collapse
Still the same, I'm on stock recovery. In console, no errors:
Code:
[email protected]:~/android/DO_MOTOROLI/twrp/2.8.5$ fastboot flash recovery twrp2.8.5.0-recovery.img
target reported max download size of 299892736 bytes
sending 'recovery' (9046 KB)...
OKAY [ 0.312s]
writing 'recovery'...
OKAY [ 0.860s]
finished. total time: 1.172s
But "adb reboot recovery" - "No command". Damn it...
---------- Post added at 06:26 PM ---------- Previous post was at 06:05 PM ----------
Ok, I'm finished. It's not possible. F U C K Motorola and good night. My advice: don't waste your time if you have the same problem. You will get nothing, except wasted time. It's good that it's not my phone (I own OnePlus One). But I was asked to install CM12.1 on my friend's phone. It's impossible, so I will need to tell him I was failed with that.
mepsilon2 said:
@giaur @LucasBS1
I too have tried booting the recovery ,but it doesn't work. You will have to flash it
if you are seeing 'no command' message it means that you still have stock recovery and the custom recovery wasn't flashed successfully.
try this one http://forum.xda-developers.com/mot...recovery-twrp-2-8-2-0-touch-recovery-t2971601
or this one http://forum.xda-developers.com/mot...recovery-twrp-2-8-6-0-touch-recovery-t3100879
Click to expand...
Click to collapse
I see people complaining about bugs or not-working features on the first link
Are you sure it's safe ?
It's not the official TWRP (apparently)
When I google for this bootloader the official page shows version 2.7.1.0
Whereas on your second link they are on the 2.8.2.0
Which one should I trust ?
And to anyone who might answer:
Trough PC is the only/safest way to flash these recoveries ?
Seeing giaur on that situation puts me stepping back...
LucasBS1 said:
I see people complaining about bugs or not-working features on the first link
Are you sure it's safe ?
It's not the official TWRP (apparently)
When I google for this bootloader the official page shows version 2.7.1.0
Whereas on your second link they are on the 2.8.2.0
Which one should I trust ?
And to anyone who might answer:
Trough PC is the only/safest way to flash these recoveries ?
Click to expand...
Click to collapse
I tested both: latest official 2.7 and linked 2.8. So they are safe. Official support for Moto E was dropped long time ago.
giaur said:
I tested both: latest official 2.7 and linked 2.8. So they are safe. Official support for Moto E was dropped long time ago.
Click to expand...
Click to collapse
Cool
Regarding to safety
Should I flash CWM or TWRP ? Why ?
Regarding the method
Flash through usb->Fastboot or through Apk (like CWM)
Or a third method ?
And why
Between TWRP 2.7 and 2.8, which one is safer ?
And of course...why ?
And a last question, before I leave you guys alone:
Did you manage to root the phone, despite the poblems occurring to you, giaur ?
Once you succesfuly flash twrp, you need to flash supersu then and you are rooted. If you don't have your current system rooted, the only way to flash custom recovery is to flash via fastboot. TWRP is recommended, because it's way better
I can't say anything more, because my moto e is not flashable, so I can't replace stock recovery.
Yo !
Flashed TWRP
But wiped things I shouldnt
How to put the ROM back via USB ?
EDIT:
NEVERMIND
Found how to use SD to do that
giaur said:
Once you succesfuly flash twrp, you need to flash supersu then and you are rooted. If you don't have your current system rooted, the only way to flash custom recovery is to flash via fastboot. TWRP is recommended, because it's way better
I can't say anything more, because my moto e is not flashable, so I can't replace stock recovery.
Click to expand...
Click to collapse
I was also struggling a lot many days into getting twrp and cw loaded on to a Moto E. The problem was that I was pressing the Power button to activate the recovery menu and that will not activate the recovery option. You got to press the UP button instead of power after executing
Code:
fastboot.exe flash recovery twrp-2.8.1.0-condor.img
. This is quite counter intuitive but described well in most posts, but as experts we assume up button is to go up the menu.
Sunish Issac
so.. i have an Lg d618 rooted and running official L 5.0.2
i wanted to flash a custom recovery so i started with patching bootloader using this thread
http://forum.xda-developers.com/g2-mini/development/bootloader-d620-d618-t3127819
then i installed TWRP using this thread
http://forum.xda-developers.com/g2-mini/development/recovery-lg-g2-mini-d618-v10c-t2854493
by flashing the img file with Flashify
the the phone rebooted and i got the TWRP interface
http://img.wonderhowto.com/img/39/2...only-custom-recovery-youll-ever-need.w654.jpg
and when i press reboot i got this
http://img.wonderhowto.com/img/38/1...only-custom-recovery-youll-ever-need.w654.jpg
If I reboot into System - I wind up at the TWRP screen again after the LG logo.
If I reboot into Recovery - I got that android logo like i have no recovery installed
If I reboot into Bootloader - I wind up at the TWRP screen again after the LG logo.
If I reboot into Power Off - when I power on I wind up at the TWRP screen again after the LG logo.
i tried this solution http://androidforums.com/threads/twrp-bootloop-fix-after-update-ota.922585/ and it didn't help
dibik said:
so.. i have an Lg d618 rooted and running official L 5.0.2
i wanted to flash a custom recovery so i started with patching bootloader using this thread
http://forum.xda-developers.com/g2-mini/development/bootloader-d620-d618-t3127819
then i installed TWRP using this thread
http://forum.xda-developers.com/g2-mini/development/recovery-lg-g2-mini-d618-v10c-t2854493
by flashing the img file with Flashify
the the phone rebooted and i got the TWRP interface
http://img.wonderhowto.com/img/39/2...only-custom-recovery-youll-ever-need.w654.jpg
and when i press reboot i got this
http://img.wonderhowto.com/img/38/1...only-custom-recovery-youll-ever-need.w654.jpg
If I reboot into System - I wind up at the TWRP screen again after the LG logo.
If I reboot into Recovery - I got that android logo like i have no recovery installed
If I reboot into Bootloader - I wind up at the TWRP screen again after the LG logo.
If I reboot into Power Off - when I power on I wind up at the TWRP screen again after the LG logo.
i tried this solution http://androidforums.com/threads/twrp-bootloop-fix-after-update-ota.922585/ and it didn't help
Click to expand...
Click to collapse
Followed you from the other spot...
It sounds like Flashify plunked recovery on your boot/kernel partition (assuming your recovery you described is still stock - that is - Andy laying down with the front panel open). So, I would suggest to ADB push your official L 5.0.2 boot.img while in TWRP and flash that (to boot), and you should be golden.
Also, from my perspective it's hard for me to say your bootloader is acting up, as I have a different LG device and it's bootloader does not have fastboot. It's front-end is only a shim that makes you factory reset to get into recovery mode (it's only function).
Hope this helps.
OfficerJimLahey said:
Followed you from the other spot...
It sounds like Flashify plunked recovery on your boot/kernel partition (assuming your recovery you described is still stock - that is - Andy laying down with the front panel open). So, I would suggest to ADB push your official L 5.0.2 boot.img while in TWRP and flash that (to boot), and you should be golden.
Also, from my perspective it's hard for me to say your bootloader is acting up, as I have a different LG device and it's bootloader does not have fastboot. It's front-end is only a shim that makes you factory reset to get into recovery mode (it's only function).
Hope this helps.
Click to expand...
Click to collapse
thank you Jim for the reply
well my problem is solved.. i just flashed my device with the Official KDZ file using LG flash tool in "normal flash mode not CSE"
my phone turned on normally and everything (apps, pictures, files, messages.... ) and all my data were still there so i did'nt loose a thing
i just lost the root acces and that won't be a prblm cause i can root it all over again
thanks again Jim ^^
dibik said:
thank you Jim for the reply
well my problem is solved.. i just flashed my device with the Official KDZ file using LG flash tool in "normal flash mode not CSE"
my phone turned on normally and everything (apps, pictures, files, messages.... ) and all my data were still there so i did'nt loose a thing
i just lost the root acces and that won't be a prblm cause i can root it all over again
thanks again Jim ^^
Click to expand...
Click to collapse
Did you still have TWRP installed after flashing the KDZ file normal mode? Is your bootloader still unlocked?
ShadowBlade_20 said:
Did you still have TWRP installed after flashing the KDZ file normal mode? Is your bootloader still unlocked?
Click to expand...
Click to collapse
no i didn't
i re-unlocked the bootloader and installed TWRP 2.8.7.0 and it worked like a charm and now i'm on CM 13
Having sanw problem. Been stuck here on att lg gflex for 3 months. Can u help me please? [email protected]
Sent from my C6740N using Tapatalk
Hi. I just want to ask about TWRP recovery that is Compatible with my Phone :
Starmabile PLAY Click
Android 5.1 Lollipop
Spreadtrum SC7731
4.5"
Quadcore
Anyone with a Phone with same specs as mine that is using A TWRP ?
Please help. I wanna try yours.
Cant find on google with the same specs with my phone with twrp working.
I have tried those TWRP on google but none of them works. All of them take me Only to the Bootlogo. Only thing i know as of now is i have to port twrp to my stock recovery or to my phone.
Anyone please help.
maucerezo said:
Hi. I just want to ask about TWRP recovery that is Compatible with my Phone :
Starmabile PLAY Click
Android 5.1 Lollipop
Spreadtrum SC7731
4.5"
Quadcore
Anyone with a Phone with same specs as mine that is using A TWRP ?
Please help. I wanna try yours.
Cant find on google with the same specs with my phone with twrp working.
I have tried those TWRP on google but none of them works. All of them take me Only to the Bootlogo. Only thing i know as of now is i have to port twrp to my stock recovery or to my phone.
Anyone please help.
Click to expand...
Click to collapse
Hi Bro,
i have sc7731c (karbonn titanium 3D Plex ) device too. and i have tried many available img but none of them worked this would be because these devices are new and there no suitable recovery available simply because people have not made any till now..
There is many programs that allows u to create a new custom recovery if there is no recovery is available for your device try to goggle it.
On windows, philz magic touch recovery tool, android kitchen recovery image unpacker and so on.
Can i make you custom recovery using your stock image if you're too lazy
as i said above i have been trying to flash online available recoveries and accidentally flashed my stock u could help me out this
can u provide me you stock recovery image file ?
@Maucurezo
Hey dude! Im a pinoy. Im running with my STARMOBILE PLAY CLICK. As same as yours. Im running on the same Spreadtrum SC7731C and I flashed a Custom Recovery but it would only bring me to bootload. I kept finding solutions to get my Stock recovery but failed. We have the same Problem. I need the Custom recovery too. Help us admins
You can try and do it yourself. Porting TWRP and CWM to a new device. You'll need the stock rom for your device or simply make an image "dump" of the system files (boot.img, etc) via adb. Goodluck.
TWRP for sc7731c hope it helps
hi all a have a sc7731c phone on android 6.0 and i was able to install twrp on my device
it all started when i found a stock rom on the web (Google your device for stock - rom or - firmware)
once i had the rom i started searching for a way to extract the stock recovery from the rom
and i found this tool SPD_Upgrade_Tool_R4.0.0001 using this tool i extracted my stock
recovery from the ROM ( recovery.img ) , first stage complete i had a stock recovery
taken from a rom for my phone - brand and model must be right on the stock
firmware/rom or you risk damaging you phone (DO NOT CHEAT PLZ)
ps:wen you unpack the firmware/rom you should get a .pac file
ps:finding my stock rom took me several days of search.
now for STAGE 2 i had a stock recovery a needed to change it
for twrp another few days of search i came across a site
called hovatek here i found a tool to port (change) the
stock recovery to boot the twrp recovery the tool name is
[Hovatek] Spreadtrum (SPD) Auto TWRP Recovery Porter V1.0 by Team Hovatek (x86)
i run my stock recovery with this tool the tool creates a modified recovery on the
output folder( a few kb bigger ) stage 2 done.
STAGE 3
1- a fully working ADB, for this your best option is android-studio
2-turn on USB debuging and OEM unlock in DEV options
3-name the new recovery file recovery.img
4-your device has to be in USB MTP mode
5-if ADB is properly installed and Windows has the correct android device
driver you should be able to use these commands using android-studio's ADB
command-adb devices
-if the device is detected a serial number apears
command-adb reboot bootloader
-the device reboots to a black screen with small white letters saying FASTBOOT mode
command-fastboot devices
-the device displays the serial number again
command-fastboot flash recovery recovery.img
- if all went well it will say successful
command-fastboot reboot
-dont remenber if it booted straight to twrp or if i had to use power + volume up
-by the way on my phone to get in the default recover its 1 second hold power
and then with the power pressed for 1 sec add volume up 3 sec and let go of both
any way it worked i hope it helps ppl with these sc7731c phones
i have twrp 3.0.0 fully working
tips: youtube vídeos on how to use SPD_Upgrade_Tool_R4.0.0001
the hovatek site has a great tutorial on how to use the recovery porter tool
the last part the ADB commands was a ***** as Windows did not install my device
correctly and this is crucial -install phone driver manualy/Google device/Google android device. good luck
ps: all merit goes to the developers of these tool, a great ty to them :highfive:
ps: at the start i did NOT have root, the success flashing the ported twrp recovery
was followed bi the installation of the magisk15.3.zip and voila twrp+root
any one help me i port twrp using adb but after i flash my twrp upside down on sc7731ceb it works fine but the twrp upside down any help me
pauljack2 said:
any one help me i port twrp using adb but after i flash my twrp upside down on sc7731ceb it works fine but the twrp upside down any help me
Click to expand...
Click to collapse
humm,.. as far as i now adb does not port recovery image´s you mean you found an image for sc7731?? phone and there are at least 4 or 5 variations of the sc7731 board and you
flashed it on your phone, by shear luck you did not soft-brick or brick your phone and it actualy Works, :cyclops:
you need to search Google/xda/hovatek site for your brand and model´s stock recovery or even better your custom recovery
or as an alternative your stock ROM/FIRMWARE and then extract the stock recovery from ROM/FIRM port it and flash it
im prety shure someone out there has a phone like your´s and you can , when you find it download the stock recovery - the custom recovery - or the ROM/FIRMWARE file
the hovatek site has a great auto port tool all you need is your stock recovery follow the vídeo simple steps and flash it now that you have root just use
twrp oficial app to flash it ,se my tutorial above it will be easy once you have the stock recovery or rom/firmware
i have a 50 buck cheap phone wierd brand,it took me several days to find the stock rom/firmware once i did all worked just fine no strange stuff
hovetek site also has a lot of rom´s/firmware files for many brands and model´s , again search Google/xda/hovatek for your model + stock recovery or recovery.img, custom recovery.
good luck
i have stock recovery so i copy the recovery from my stock and i use carlivimg so i can unpack my recovery.img but i have really problem on upside down but i work fine i flash supersu on it now i have rooted my phone. my phone by the way is ding ding defi go SC7731ceb i use TWRP 3.0.2.0 it works fine but if you update the latest twrp you have problem on failed mount and .etc
ANY can help that upside down ??? thats my problem now on my recovery
but you can port recovery using fastboot
i commend
c:/adb>adb devices
adb>adb reboot bootleader
adb>fastboot flash recovery recovery.img
thats i port my recovery on sc7731ceb
using pc
pauljack2 said:
i have stock recovery so i copy the recovery from my stock and i use carlivimg so i can unpack my recovery.img but i have really problem on upside down but i work fine i flash supersu on it now i have rooted my phone. my phone by the way is ding ding defi go SC7731ceb i use TWRP 3.0.2.0 it works fine but if you update the latest twrp you have problem on failed mount and .etc
ANY can help that upside down ??? thats my problem now on my recovery
but you can port recovery using fastboot
i commend
c:/adb>adb devices
adb>adb reboot bootleader
adb>fastboot flash recovery recovery.img
thats i port my recovery on sc7731ceb
using pc
Click to expand...
Click to collapse
Go here https://forum.hovatek.com/thread-21669.html try and port again with this tool it worked fine for me.
hey all!
So this is a first for me... I've been rooting and playing with android for a very long time (going back to the g1 days) and this is the first time I've ever seen this.
So I was on an old version of CM and decided it was time to update finally. I had unrooted a long time ago, but was still running cm perfectly fine. I went to install a new version of recovery (so I could update) and now when I try to boot into recovery I just get the oneplus logo. Here's the strange part, the phone isn't soft bricked... I can still boot into android no problem.
Anyone else every seen this problem? Do I need to start over (unlock bootloader, root, recovery, rom)?
Anyone else ever seen this happen on Oneplus One or any other phone for that matter?
Thanks in advance!
Same Problem Here
I am having the same exact issue with my OPX: I wanted to update my old CyanogenMod and for that I needed to update my TWRP. After I flashed it successfully when trying to boot into Recovery it stucks on the 1+ Logo forever.
If I boot into OS it works (the same old CM since I haven't been able to upgrade), Fastboot as well, it's Recovery that doesn't work.
I found some post for the OP3 that state:
WHY AM I STUCK ON THE TWRP SPLASH SCREEN FOR 8 HOURS?
Be patient, wait another 8 hours.
Just kidding, try this while stuck on the loading screen:
adb shell wipe_misc; adb shell reboot recovery
Some devices might somehow get a flag set in misc that tells the bootloader to ignore the android boot image command line.
This results in the kernel not receiving the hardware name (qcom), which then confuses recovery and causes it to wait forever. FOREVER.
Click to expand...
Click to collapse
I tried it and I got the following error:
/system/bin/sh: wipe_misc: not found
Click to expand...
Click to collapse
I don't know what else to do now. Please help.
janc_z said:
I am having the same exact issue with my OPX: I wanted to update my old CyanogenMod and for that I needed to update my TWRP. After I flashed it successfully when trying to boot into Recovery it stucks on the 1+ Logo forever.
If I boot into OS it works (the same old CM since I haven't been able to upgrade), Fastboot as well, it's Recovery that doesn't work.
I found some post for the OP3 that state:
I tried it and I got the following error:
I don't know what else to do now. Please help.
Click to expand...
Click to collapse
I'm guessing we need to do a full wipe, and go back to the begining (root, reflash reocvery, reflash rom), but hoping not...
zbt1985 said:
I'm guessing we need to do a full wipe, and go back to the begining (root, reflash reocvery, reflash rom), but hoping not...
Click to expand...
Click to collapse
I guess you were right! Here's what I did:
- Tried to reflash TWRP using adb. It did flashed it but couldn't boot it and throws error "dtb not found".
- I found this post that first suggested to use the Blue Spark version of the TWRP. I tried adb-ing it and got the same error.
- In a later comment the following video was suggested: https://www.youtube.com/watch?v=kTdKmceC5xU.
- I the downloaded the stock recovery and the stock ROM from this page: https://devs-lab.com/download-oneplus-official-stock-rom.html. Be sure to find the OnePlus X section.
- Using adb I flashed the stock recovery, did a full wipe, rebooted and copied the stock ROM to my SD card.
- Reboot to Recovery, flash from local, selected the Stock ROM zip and let it do its thing.
- Again, from Fastboot I flashed the latest TWRP. I didn't get any errors now!
- Downloaded the Tesla ROM and flashed it using TWRP.
Everything is working fine now!
janc_z said:
I guess you were right! Here's what I did:
- Tried to reflash TWRP using adb. It did flashed it but couldn't boot it and throws error "dtb not found".
- I found this post that first suggested to use the Blue Spark version of the TWRP. I tried adb-ing it and got the same error.
- In a later comment the following video was suggested: https://www.youtube.com/watch?v=kTdKmceC5xU.
- I the downloaded the stock recovery and the stock ROM from this page: https://devs-lab.com/download-oneplus-official-stock-rom.html. Be sure to find the OnePlus X section.
- Using adb I flashed the stock recovery, did a full wipe, rebooted and copied the stock ROM to my SD card.
- Reboot to Recovery, flash from local, selected the Stock ROM zip and let it do its thing.
- Again, from Fastboot I flashed the latest TWRP. I didn't get any errors now!
- Downloaded the Tesla ROM and flashed it using TWRP.
Everything is working fine now!
Click to expand...
Click to collapse
Lucky you!
I on the other hand can't connect via adb, only fastboot...
So I bought a stock Xperia Z5 Compact E5823 on which I want to use LinageOS. I managed to set up Cyanogenmod and, later, LinageOS on my previous two phones, but I am not very confident about what I am actually doing, so please excuse if I express myself unclear or if I lack basic understanding. My main problem is that I cannot access recovery mode, neither via volume-down + power-button, nor via ADB.
Phone info: Android version 5.1.1, Kernel version 3.10.49-perf-g6b847e2, Build no. 31.0.A.4.11 (do you need something else?)
I followed the LinageOS guide: https://wiki.lineageos.org/devices/suzuran/install but I fail to flash TWRP.
I unlocked the bootloader, I am able to access my phone using ADB (I'm on a Linux machine) and I can boot into fastboot mode. There I should be able to flash a TWRP recovery in order to flash LinageOS, but if I do, nothing changes.
At first I tried the newest TWRP version (3.2.1): https://forum.xda-developers.com/crossdevice-dev/sony/twrp-3-1-0-z5-z5c-z5p-t3571050 - is this version even compatible?
When running fastboot flash recovery <twrp321-recovery.img>, it says target didn't report max-download-size (what does that mean?) and finishes without errors. However, booting to recovery is not working, the phone just boots normally.
When running fastboot boot <twrp321-recovery.img>, it says FAILED (remote: dtb not found) (what's "dtb"?)
Trying around with different TWRP versions, I found that version 2.8.something works for booting (fastboot boot recovery.img), so I end up in TWRP, but flashing this recovery still does not work, as above: Max-download-size note, no errors, no recovery mode, just normal boot.
I did several factory resets and tried to flash LinageOS using the booted recovery, but then it says something about missing partitions that I don't understand (I could do it again if this information is useful).
Generally: Shouldn't I be able to boot into recovery mode, irrespective of what I did? I did not try it before I started messing around, so I do not know if it had worked out of the box ...
Could I have accidentally messed up my recovery mode? Maybe when I tried to flash TWRP 3.2.1? If so, how do I revert this - how do I set up a working recovery? Do I need to erase/wipe anything specific? I fear bricking this phone ...
I also tried around with FlashTool (https://xperiafirmware.com/), trying to set up a new kernel, thinking that TWRP might need that, but I seem to be too unacquainted with Android OS architecture for this - actually, I do not even know what exactly a kernel is ...
Thank you very much in advance
Fred
fredduh said:
So I bought a stock Xperia Z5 Compact E5823 on which I want to use LinageOS. I managed to set up Cyanogenmod and, later, LinageOS on my previous two phones, but I am not very confident about what I am actually doing, so please excuse if I express myself unclear or if I lack basic understanding. My main problem is that I cannot access recovery mode, neither via volume-down + power-button, nor via ADB.
Phone info: Android version 5.1.1, Kernel version 3.10.49-perf-g6b847e2, Build no. 31.0.A.4.11 (do you need something else?)
I followed the LinageOS guide: https://wiki.lineageos.org/devices/suzuran/install but I fail to flash TWRP.
I unlocked the bootloader, I am able to access my phone using ADB (I'm on a Linux machine) and I can boot into fastboot mode. There I should be able to flash a TWRP recovery in order to flash LinageOS, but if I do, nothing changes.
At first I tried the newest TWRP version (3.2.1): https://forum.xda-developers.com/crossdevice-dev/sony/twrp-3-1-0-z5-z5c-z5p-t3571050 - is this version even compatible?
When running fastboot flash recovery <twrp321-recovery.img>, it says target didn't report max-download-size (what does that mean?) and finishes without errors. However, booting to recovery is not working, the phone just boots normally.
When running fastboot boot <twrp321-recovery.img>, it says FAILED (remote: dtb not found) (what's "dtb"?)
Trying around with different TWRP versions, I found that version 2.8.something works for booting (fastboot boot recovery.img), so I end up in TWRP, but flashing this recovery still does not work, as above: Max-download-size note, no errors, no recovery mode, just normal boot.
I did several factory resets and tried to flash LinageOS using the booted recovery, but then it says something about missing partitions that I don't understand (I could do it again if this information is useful).
Generally: Shouldn't I be able to boot into recovery mode, irrespective of what I did? I did not try it before I started messing around, so I do not know if it had worked out of the box ...
Could I have accidentally messed up my recovery mode? Maybe when I tried to flash TWRP 3.2.1? If so, how do I revert this - how do I set up a working recovery? Do I need to erase/wipe anything specific? I fear bricking this phone ...
I also tried around with FlashTool (https://xperiafirmware.com/), trying to set up a new kernel, thinking that TWRP might need that, but I seem to be too unacquainted with Android OS architecture for this - actually, I do not even know what exactly a kernel is ...
Thank you very much in advance
Fred
Click to expand...
Click to collapse
Hi Fred,
while searching for a similar (or maybe the same) problem on my new Z5 compact I came across your post.
I was trying to install LineageOS and therefore started with TWRP 3.2.1 linked from the LineageOS installation manual(link)
It failed. Many times. The only workaround was booting to recovery mode with the phone booted to stock rom via:
Code:
adb reboot recovery
but NOT ONCE it worked with the given key combination. Trying to install LineageOS from that resulted in a completely unusable phone, not even showing the sony logo on boot.
What helped my was flashing the phone with the sony tool "emma" with the latest custom rom (for me 32.4.A.0.160). Whatever magic this does (firmware upgrade maybe), it brought my device back to live and now I can install and boot into TWRP recovery, installed LineageOS.
You can do so by
1 installing and starting emma, just follow screen instructions
2 activate developer mode (tapping on the build number 7 multiple time (under settings/about phone)
3 activate adb debugging under settings/developer settings and authorize phone
4 power off the phone
5 connect the phone to the pc
6 press and hold volume down button until the led becomes green
The device will appear in Emma and you can flash it back to life.
Let me know how it worked for you,
Frank