Related
I bought this 3D used but like new and wanted to flash it to Boost so I was doing some preliminary pre-flash things like rooting and loading a custom recovery and rom. I used the HTC unlock method for the bootloader and flashed Eternity and it stuck at Beats screen (boot animation). I downloaded a different rom to see if it was the rom but that one froze at the animation screen as well. I attempted to do an RUU stock reset on my PC from bootloader but it returned an error saying update failed. I'm basically locked out of this phone. I read everything it said about flashing custom kernels and how you are supposed to flash them from bootloader. I know Eternity has a stock kernel don't know about the other one. My last resort is to download a zip of a stock rom and flash that from recovery. If it freezes on me I'm not sure what I'll do next. Any help is appreciated...
xlxcrossing said:
I bought this 3D used but like new and wanted to flash it to Boost so I was doing some preliminary pre-flash things like rooting and loading a custom recovery and rom. I used the HTC unlock method for the bootloader and flashed Eternity and it stuck at Beats screen (boot animation). I downloaded a different rom to see if it was the rom but that one froze at the animation screen as well. I attempted to do an RUU stock reset on my PC from bootloader but it returned an error saying update failed. I'm basically locked out of this phone. I read everything it said about flashing custom kernels and how you are supposed to flash them from bootloader. I know Eternity has a stock kernel don't know about the other one. My last resort is to download a zip of a stock rom and flash that from recovery. If it freezes on me I'm not sure what I'll do next. Any help is appreciated...
Click to expand...
Click to collapse
Did you follow the root instructions all the way through to install Superuser and the recovery? If so, did you boot into fastboot, connect usb, then do the fastboot boot recovery.img before flashing the rom?
Sent from my PG86100 using XDA App
JayDaKissEP said:
Did you follow the root instructions all the way through to install Superuser and the recovery? If so, did you boot into fastboot, connect usb, then do the fastboot boot recovery.img before flashing the rom?
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
I did not use that method to flash, no. I'm assuming you mean from my PC execute the command. I did follow the instructions to install TWRP which is a custom recovery and I flashed a ZIP from TWRP for Superuser and checked it to be working which it was. (I tested Root Explorer and Terminal Emulator for root)
I was operating off the assumption that custom roms with a STOCK kernel could be flashed by booting into recovery. I went to bootloader then recovery then flashed the rom. Obviously I did something wrong since both roms wouldn't load. I will use your method of PC commands from fastboot into recovery and see where that gets me....pease let me know if this is correct or anything else I need to do....thanks a bunch.
UPDATE : I tried the method of loading recovery from fastboot usb - it worked thank you. The rom loaded. I'm wondering why since it was a custom rom with a stock kernel why I couldn't flash it from recovery.
xlxcrossing said:
UPDATE : I tried the method of loading recovery from fastboot usb - it worked thank you. The rom loaded. I'm wondering why since it was a custom rom with a stock kernel why I couldn't flash it from recovery.
Click to expand...
Click to collapse
While the kernel is stock, Virus has a bunch of binaries and such that will be mismatched without flashing the boot.img properly ... So while some of his builds say "stock" not always completely stock.
ifly4vamerica said:
While the kernel is stock, Virus has a bunch of binaries and such that will be mismatched without flashing the boot.img properly ... So while some of his builds say "stock" not always completely stock.
Click to expand...
Click to collapse
cool cool thanks for the info. So I need to load the recovery.img file from usb fastboot EVERY time I want to flash a rom? Any way to eliminate this hassle....I just assume flash less often if not...thanks
xlxcrossing said:
cool cool thanks for the info. So I need to load the recovery.img file from usb fastboot EVERY time I want to flash a rom? Any way to eliminate this hassle....I just assume flash less often if not...thanks
Click to expand...
Click to collapse
With hboot 1.5, the ONLY way to flash a ROM correctly is with fastboot>recovery.
Twolazyg said:
With hboot 1.5, the ONLY way to flash a ROM correctly is with fastboot>recovery.
Click to expand...
Click to collapse
Not true. You can flash a ROM but if you don't use fastboot it won't touch the kernel. I always change roms with the stock kernel. He must have done something wrong
Sent from my PG86100 using XDA App
JayDaKissEP said:
Not true. You can flash a ROM but if you don't use fastboot it won't touch the kernel. I always change roms with the stock kernel. He must have done something wrong
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
If the kernel is pure stock with no added binaries or stuff it will work. Virus puts lots of little tweaks in that require it. Now if you can load a completely stock kernel and ramdisk then load Eternity (of course some eternity builds did have a completely stock kernel) then you may be onto something.
As far as flashing with hboot 1.50 easiest way to do that without the computer is with joeykrm's flash image gui. I don't have 1.50 but I have used his gui to do partial updates on svn builds in tandem with adb sync and it works great. His post with the apk is in development section. just read the instructions and flash away.
ifly4vamerica said:
If the kernel is pure stock with no added binaries or stuff it will work. Virus puts lots of little tweaks in that require it. Now if you can load a completely stock kernel and ramdisk then load Eternity (of course some eternity builds did have a completely stock kernel) then you may be onto something.
As far as flashing with hboot 1.50 easiest way to do that without the computer is with joeykrm's flash image gui. I don't have 1.50 but I have used his gui to do partial updates on svn builds in tandem with adb sync and it works great. His post with the apk is in development section. just read the instructions and flash away.
Click to expand...
Click to collapse
Yeah I read all about it I'm still stuck on why if I had a stock kernel installed with a stock rom and I do a custom rom flash and as stated it doesn't touch the kernel why the rom wouldn't simply run off the stock kernel - that's what confuses me. I understand the issue of the kernel not being flashed which is obviously what happened with me. I just don't really know where I stand with what kernel to ALWAYS have loaded since if that's the thing with the issue I would want to for purposes of not doing tons of work stay away from flashing kernels and stick to flashing roms when I want to change it up. But if the STOCK kernel won't load with a custom rom which technically it should I guess I'll just have to flash a universal custom kernel and assume any rom I flash will simply use that kernel. Kind of a nightmare compared to my 4G....welcome to the world of the 3D I guess.
I guess going into recovery from hboot with the volume and power buttons wouldn't count - I have to stick with PC commands?
I have a Nexus 6P that has some weird issue where it is not being recognized by any PC or any USB port as a USB device. So I can't get it to work with fastboot as an adb device. It has stock android 6.0.1 on it and TWRP. This is how I got it. I think there is something wrong with the software not allowing the USB mode to work properly so I wanted to flash to another stock image. I've already downloaded the stock anglr image and uses Google Drive to transfer the files over, both the complete image and also the independent IMG files. Is it possible to use TWRP to flash the phone back to stock?
Two questions before I venture an answer -
a. When you mean flash back to stock, I am assuming you mean your TWRP stays and all you want is to flash stock android. Right?
b. Your custom recovery is TWRP right?
tropicanapure said:
Two questions before I venture an answer -
a. When you mean flash back to stock, I am assuming you mean your TWRP stays and all you want is to flash stock android. Right?
b. Your custom recovery is TWRP right?
Click to expand...
Click to collapse
a: Yes, unrooted and a different stock image to see if maybe this version on the phone is buggy with the USB connection not working.
b: Yes, TWRP 2.8.7.2
Great. Then the simple answer is yes. Subject to the fact that whatever you trying to flash is "flashable" (i.e. usable by TWRP). To be honest I have been flashing using TWRP for last 3 years and never once have I used a PC.
Slightly longer answer. To do this
a. (ALWAYS) Backup original Android install using TWRP
b. Factory reset (NOT wipe - unless you know what you are doing!)
c. Look for the Flashable ZIP containing your stock image - and flash.
and voila! You are back to stock!
Good luck!
tmar89 said:
a: Yes, unrooted and a different stock image to see if maybe this version on the phone is buggy with the USB connection not working.
b: Yes, TWRP 2.8.7.2
Click to expand...
Click to collapse
tropicanapure said:
Two questions before I venture an answer -
a. When you mean flash back to stock, I am assuming you mean your TWRP stays and all you want is to flash stock android. Right?
b. Your custom recovery is TWRP right?
Click to expand...
Click to collapse
tropicanapure said:
Great. Then the simple answer is yes. Subject to the fact that whatever you trying to flash is "flashable" (i.e. usable by TWRP). To be honest I have been flashing using TWRP for last 3 years and never once have I used a PC.
Slightly longer answer. To do this
a. (ALWAYS) Backup original Android install using TWRP
b. Factory reset (NOT wipe - unless you know what you are doing!)
c. Look for the Flashable ZIP containing your stock image - and flash.
and voila! You are back to stock!
Good luck!
Click to expand...
Click to collapse
Thanks. So if I download the stock android image from google developers page, I can copy that over to the device and use TWRP to flash it?
Actually, I've been reading that I cannot flash a factory image with recovery, only fastboot. But fastboot doesn't work for me because device won't recognize when connected with USB (trust me, I tried everything with drivers and cables, computers, etc). I think I need to find a flashable stock image for my device.
tmar89 said:
Thanks. So if I download the stock android image from google developers page, I can copy that over to the device and use TWRP to flash it?
Click to expand...
Click to collapse
No. Which is why I said - "flashable". I dont have a Nexus 6p so I dont know where you can find a TWRP flashable stock image for that device. But a quick search of your device specific sub-forum on XDA yielded this link.
The link in the first para should help you find a "flashable factory/ stock image". I would suggest you follow instructions on that post and ask further questions there as the folks in there will have the same device as you and provide better help.
Again, good luck!
Thanks, I appreciate this advice as it helps.
tmar89 said:
Thanks, I appreciate this advice as it helps.
Click to expand...
Click to collapse
No worries. Pass it on
PS: Here's another XDA thread that has a flashable version of the STOCK rom.
PPS: Found via Google search terms nexus 6p stock rom flashable
Beginner question
I've already rooted the Redmi using a none-TWRP guide.
But for every other guide there is a mention of: making a custom boot.img either by using Android Image Kitchen, flashing something called Universal boot.img, or flashing different versions of TWRP (alka, cofface) that solves the boot.img problem.
However I haven't found an article that explains what boot.img is and why it's a problem for this phone, since flashing my moto only required TWRP + Supersu. Also, it wasn't mentioned at all in the guide I followed.
Sorry if this is pretty obvious, I'm wondering if I missed a pretty big post somewhere.
UniAyeDee said:
Beginner question
I've already rooted the Redmi using a none-TWRP guide.
But for every other guide there is a mention of: making a custom boot.img either by using Android Image Kitchen, flashing something called Universal boot.img, or flashing different versions of TWRP (alka, cofface) that solves the boot.img problem.
However I haven't found an article that explains what boot.img is and why it's a problem for this phone, since flashing my moto only required TWRP + Supersu. Also, it wasn't mentioned at all in the guide I followed.
Sorry if this is pretty obvious, I'm wondering if I missed a pretty big post somewhere.
Click to expand...
Click to collapse
+99 points for asking this question .
As per my knowledge the main problem lies in the boot.img file of MIUI roms because when you are flashing the TWRP you are messing with phone's orignal partition pattern,the boot.img's of MIUI rom checks evrytime if there is any tampering in phone's partition and as you know by flashing TWRP you tampered already , so as result your phone won't boot and gets in bootloop.
So to solve this problem devs developed some methods either you can make a cooked boot.img and flash it evrytime you get a new update to prevent bootloop,
Or you can flash lazyflasher.zip via twrp evrytime after installing new MIUI rom which will patch boot.IMG itself,
Or you can use cofface based recoveries which have lazyflash patch inbuilt and will patch the boot.IMG file evrytime you flash a MIUI rom.
NVDX11 said:
+99 points for asking this question .
As per my knowledge the main problem lies in the boot.img file of MIUI roms because when you are flashing the TWRP you are messing with phone's orignal partition pattern,the boot.img's of MIUI rom checks evrytime if there is any tampering in phone's partition and as you know by flashing TWRP you tampered already , so as result your phone won't boot and gets in bootloop.
So to solve this problem devs developed some methods either you can make a cooked boot.img and flash it evrytime you get a new update to prevent bootloop,
Or you can flash lazyflasher.zip via twrp evrytime after installing new MIUI rom which will patch boot.IMG itself,
Or you can use cofface based recoveries which have lazyflash patch inbuilt and will patch the boot.IMG file evrytime you flash a MIUI rom.
Click to expand...
Click to collapse
Thanks, clears things up. I think I've heard of tampering before but for some reason it wasn't a problem on the moto.
Is there an article or something I can read?
UniAyeDee said:
Thanks, clears things up. I think I've heard of tampering before but for some reason it wasn't a problem on the moto.
Is there an article or something I can read?
Click to expand...
Click to collapse
Yea i know what you are saying,previously i had xperia devices there wasn't a problem too but xiaomi phones have some diff. Methods i think,actually there is not an article about this thing but i am sure i had read that in some developer's post.
UniAyeDee said:
Beginner question
I've already rooted the Redmi using a none-TWRP guide.
But for every other guide there is a mention of: making a custom boot.img either by using Android Image Kitchen, flashing something called Universal boot.img, or flashing different versions of TWRP (alka, cofface) that solves the boot.img problem.
However I haven't found an article that explains what boot.img is and why it's a problem for this phone, since flashing my moto only required TWRP + Supersu. Also, it wasn't mentioned at all in the guide I followed.
Sorry if this is pretty obvious, I'm wondering if I missed a pretty big post somewhere.
Click to expand...
Click to collapse
Update:
The system is known as "dm-verity"
Which enables verfying boot partiton evrytime a system boots if there is any modification.
It is included after 4.4 kitkat for security purpose.
Miui is using Boot.img with enabled dm-verity check.
So after rooting or flashing twrp phone won't boot.
So,what lazyflasher does is disables it.which is inbuilt part of cofface based recoveries.
Read more on dm-verity:
https://source.android.com/security/verifiedboot/
Custom super su from somewhere which roots boot via patch. Flash with twrp
There is an official twrp for zl1(x720), some people here say you can use it on zl0(x722) as well. Can someone confirm?
And what about CrisbalGreece and codeworkx versions? How do they differ from the official twrp for x720, any specific x722 modifications? I tried, but couldn't find their git repos for this.
I mean no disrespect to anyone, but I think we should focus more on having source code and easy build instructions. Otherwise we're just tolerating flying binaries and not helping people to develop their knowledge, turning them into mere consumers.
Sorry for bumping but this thread is really important.
Codeworkx:
Can you please tell us why did you make a 3.2.1 x722 version of twrp?(x720 3.1.1 seems to work on x722)
Also can you provide the source code/modifications?
btw I tried it and the touch screen did not work with it.
Everyone:
Is the x720 3.1.1 version ok to use?
Tried booting it and it seemed to work fine, touch screen and everything.
PS.
We can boot twrp without flashing it via "fastboot boot twrp.img" and then backup whatever we want.
So you can use twrp without flashing it and also backup stock recovery if you want to.
Why aren't more people aware of this?
randxor said:
Sorry for bumping but this thread is really important.
PS.
We can boot twrp without flashing it via "fastboot boot twrp.img" and then backup whatever we want.
So you can use twrp without flashing it and also backup stock recovery if you want to.
Why aren't more people aware of this?
Click to expand...
Click to collapse
Hi, I just read your thread.... I explored that path here..... https://forum.xda-developers.com/showpost.php?p=75451375&postcount=81
Lemme see what you think 'bout it.
It's quite easy to do a full backup or a partial one.
You can use adb while in twrp, just do fastboot boot twrp.img. Afterwards while in twrp, do adb pull /dev/recovery_partition.
To find the exact recovery partition you will nees to look around in dev. Ie. ls, df,lsblk.
I can provide a step by step tutorial.
But all of this has nothing to do with why are there many different twrp versions?
Ie. I know codeworkx supports encryption, but what about his older version? And CrisbalGreece?
ctrl-alt-del
Hello XDA developers, I'm in urgent and I have a really big problem. It sounds funny but, I deleted my realme ui recovery ,_,
I was trying to install PPUI 4.1 on my Realme 7 but I saw a tutorial that you have to erase the recovery to install TWRP. Please, I need a solution of how can I get it back. I also tried flashing a lot of recoveries and their vbmeta but nothing works. Sadly.
Edit: I'm on RMX2151_11_C.17 | Realme UI 2.0 Latest version
Here is the stock recovery
Chenes said:
Here is the stock recovery
Click to expand...
Click to collapse
You sure? I'm on RMUI2.0 and how do I flash it? Can I type 'fastboot boot recovery.img'? Are my data will be wiped?
Sorry for a lot of questions, haha
iOussamato_ said:
You sure? I'm on RMUI2.0 and how do I flash it? Can I type 'fastboot boot recovery.img'? Are my data will be wiped?
Click to expand...
Click to collapse
From what I read before, fastboot boot will only boot to that recovery file temporarily but I haven't tried it myself. It should be
Code:
fastboot flash recovery recovery.img
I'm not 100% sure it will work without problems, but if it did, your data will not be wiped.
I suggest you wait for someone else to answer coz I'm not expert. I only learned from guides in the telegram group.
Chenes said:
From what I read before, fastboot boot will only boot to that recovery file temporarily but I haven't tried it myself. It should be
Code:
fastboot flash recovery recovery.img
I'm not 100% sure it will work without problems, but if it did, you're data will not be wiped.
I suggest you wait for someone else to answer coz I'm not expert. I only learned from guides in the telegram group.
Click to expand...
Click to collapse
Can I have that Telegram group invite?
iOussamato_ said:
Can I have that Telegram group invite?
Click to expand...
Click to collapse
Realme 7 • Narzo 20 Pro • Global
Welcome To Realme 7 | Narzo 20 Pro Group • RM6785_updates(official-A12/A13)- @RM6785 / https://t.me/realme7updater • RM6785_Gaming- @RM6785Gaming • Realme 7 Cloud: @realme_7_cloud
t.me
iOussamato_ said:
You sure? I'm on RMUI2.0 and how do I flash it? Can I type 'fastboot boot recovery.img'? Are my data will be wiped?
Sorry for a lot of questions, haha
Click to expand...
Click to collapse
You can try, first, if fastboot works in your device, type adb reboot fastboot, once the script ends, quickly disconnect device from your PC and again reconnect it, you will be redirected to fastboot, if the bootloader is unlocked, you could flash it using fastboot commands.
If you can´t get it to work then you can flash it using SPFT https://spflashtool.com/, put the recovery, in the same folder, with the attached files. All the sources to can use the tool, here https://www.getdroidtips.com/bypass-mediateks-sp-flash-tool-authentication-protection/
SubwayChamp said:
You can try, first, if fastboot works in your device, type adb reboot fastboot, once the script ends, quickly disconnect device from your PC and again reconnect it, you will be redirected to fastboot, if the bootloader is unlocked, you could flash it using fastboot commands.
If you can´t get it to work then you can flash it using SPFT https://spflashtool.com/, put the recovery, in the same folder, with the attached files. All the sources to can use the tool, here https://www.getdroidtips.com/bypass-mediateks-sp-flash-tool-authentication-protection/
Click to expand...
Click to collapse
I have never used SPFlashTool before honestly, I'm just scared to break my phone or lost my data in it. I just wish to install a custom ROM
iOussamato_ said:
I have never used SPFlashTool before honestly, I'm just scared to break my phone or lost my data in it. I just wish to install a custom ROM
Click to expand...
Click to collapse
Most of the custom roms I've seen requires formatting data. Just to be sure have you unlocked bootloader already? That requires wiping data iirc.
If not then nothing will really work with what you're doing.
iOussamato_ said:
I have never used SPFlashTool before honestly, I'm just scared to break my phone or lost my data in it. I just wish to install a custom ROM
Click to expand...
Click to collapse
What you are saying now is totally different from what you firstly posted.
Installing a custom ROM doesn't require a stock recovery (just in case you are confusing), and obviously, to can switch from a stock ROM to a custom ROM, that has a total different basement, it's mandatory to format data, anyway, you should back up your data previously to do so.
SubwayChamp said:
What you are saying now is totally different from what you firstly posted.
Installing a custom ROM doesn't require a stock recovery (just in case you are confusing), and obviously, to can switch from a stock ROM to a custom ROM, that has a total different basement, it's mandatory to format data, anyway, you should back up your data previously to do so.
Click to expand...
Click to collapse
I meant, I wish to install a custom ROM but I cannot install a working recovery and wanted the stock one. Sorry
Chenes said:
Most of the custom roms I've seen requires formatting data. Just to be sure have you unlocked bootloader already? That requires wiping data iirc.
If not then nothing will really work with what you're doing.
Click to expand...
Click to collapse
Yes my bootloader is already unlocked
iOussamato_ said:
Yes my bootloader is already unlocked
Click to expand...
Click to collapse
Then you can root your phone 1st then backup your files to a computer and use migrate backup to backup app data. Note that migrate backup is limited to 4gb. Then do the fastboot flash i mentioned before
iOussamato_ said:
I meant, I wish to install a custom ROM but I cannot install a working recovery and wanted the stock one. Sorry
Click to expand...
Click to collapse
Why you are saying that you cannot install a working recovery, I don't know of any attempt you did to achieve it.
A stock recovery is not needed to install a custom ROM, and even you can't install a custom ROM using a stock recovery.
If you want to join, flashing your device and stuff like this, better learn how to use SPFT, also you have this tool https://github.com/bkerler/mtkclient, this can save your device, if something in the process goes wrong.
SubwayChamp said:
Why you are saying that you cannot install a working recovery, I don't know of any attempt you did to achieve it.
A stock recovery is not needed to install a custom ROM, and even you can't install a custom ROM using a stock recovery.
If you want to join, flashing your device and stuff like this, better learn how to use SPFT, also you have this tool https://github.com/bkerler/mtkclient, this can save your device, if something in the process goes wrong.
Click to expand...
Click to collapse
I wanted to flash stock rom to downgrade into Realme UI 1.0 then flash the custom recovery so I can flash a custom rom
iOussamato_ said:
I wanted to flash stock rom to downgrade into Realme UI 1.0 then flash the custom recovery so I can flash a custom rom
Click to expand...
Click to collapse
OK, then what you are trying to install is an "old" Android 10 based ROM, if this is the case, then just download a stock Android 10 ROM, flash it through SPFT, then use SPFT to flash the custom recovery, transfer the custom ROM to your external SD Card (preferably) or sideload it, through recovery, and flash it. In the process you need to unlock bootloader, and immediately to flash the custom recovery, boot to it, using hardware buttons.
SubwayChamp said:
OK, then what you are trying to install is an "old" Android 10 based ROM, if this is the case, then just download a stock Android 10 ROM, flash it through SPFT, then use SPFT to flash the custom recovery, transfer the custom ROM to your external SD Card (preferably) or sideload it, through recovery, and flash it. In the process you need to unlock bootloader, and immediately to flash the custom recovery, boot to it, using hardware buttons.
Click to expand...
Click to collapse
Do you know a tutorial of how to use SPFlashTool?
iOussamato_ said:
Do you know a tutorial of how to use SPFlashTool?
Click to expand...
Click to collapse
How to use SP Flash Tool
This is a step-by-step tutorial on how to flash stock rom to a Mediatek device using Smart Phone Flash tool. SP Flash tool is one application you could find very useful in fixing extreme cases of a br
www.hovatek.com
Alright so, it might sound funny but I think I fixed it. I was playing with my downloaded recoveries until I downloaded the stock recovery, it is compatible but when I do fastboot reboot recovery I get stuck at Orange State for like 30min and it boots me into the recovery so does anyone know a solution for this? And thank you for everything and sorry for wasting y'all's time. Sincereley.
iOussamato_ said:
Alright so, it might sound funny but I think I fixed it. I was playing with my downloaded recoveries until I downloaded the stock recovery, it is compatible but when I do fastboot reboot recovery I get stuck at Orange State for like 30min and it boots me into the recovery so does anyone know a solution for this? And thank you for everything and sorry for wasting y'all's time. Sincereley.
Click to expand...
Click to collapse
You have to boot to recovery using hardware buttons (PWR + vol. down), in regard to orange state, this is absolutely normal when bootloader was unlocked, it's not an issue but a cosmetic thing.