I'm running PN with Sharkey kernel but I don't know how to switch to Francokernel. What are the steps in fastboot. I used the tool skipsoft to install root on my phone. So can someone please explain? Thank you
trizzv said:
I'm running PN with Sharkey kernel but I don't know how to switch to Francokernel. What are the steps in fastboot. I used the tool skipsoft to install root on my phone. So can someone please explain? Thank you
Click to expand...
Click to collapse
Download fastboot below, extract it to a folder. Download the kernel and copy it to that folder. Power down the phone then hold power and volume down until it boots into fastboot mode.
Open a command prompt and type:
fastboot flash kernel
TonikJDK said:
Download fastboot below, extract it to a folder. Download the kernel and copy it to that folder. Power down the phone then hold power and volume down until it boots into fastboot mode.
Open a command prompt and type:
fastboot flash kernel
Click to expand...
Click to collapse
Thank you. Do I need to flash the PN ROM again to get rid of the Sharkey kernel?
trizzv said:
Thank you. Do I need to flash the PN ROM again to get rid of the Sharkey kernel?
Click to expand...
Click to collapse
Not sure on that. I doubt it, and I wouldn't. But not certain.
TonikJDK said:
Not sure on that. I doubt it, and I wouldn't. But not certain.
Click to expand...
Click to collapse
I used to have ElementalX and then switched to Sharkey using that method of flashing the PN ROM first. I'm just asking because this is now thru a different method
TonikJDK said:
Download fastboot below, extract it to a folder. Download the kernel and copy it to that folder. Power down the phone then hold power and volume down until it boots into fastboot mode.
Open a command prompt and type:
fastboot flash kernel
Click to expand...
Click to collapse
do i literally write "kernel" or the name of the kernel
trizzv said:
do i literally write "kernel" or the name of the kernel
Click to expand...
Click to collapse
You literally write fastboot flash kernel
Then on the end the actual filename of Franco's kernel, with a space between kernel and the filename.
You are telling Fastboot to Flash a Kernel....so it knows what you are up to.
TonikJDK said:
You literally write fastboot flash kernel
Then on the end the actual filename of Franco's kernel, with a space between kernel and the filename.
You are telling Fastboot to Flash a Kernel....so it knows what you are up to.
Click to expand...
Click to collapse
When I open the command prompt should I navigate to the folder that I have the fastboot and kernel on?
How do I do that
https://www.youtube.com/watch?v=a8wBj6ItrLE
is this a good video to follow?
Related
what is the standard procedure on changing the recovery? i have CWM on it right now. not sure on how to remove that and then install the smelkus one. found a video on yt saying to use terminal emulator to flash it, it "flashed it" but now it just goes to the bootloader menu where you choose fastboot or the other option. still boots into the OS fine tho
douellette said:
what is the standard procedure on changing the recovery? i have CWM on it right now. not sure on how to remove that and then install the smelkus one. found a video on yt saying to use terminal emulator to flash it, it "flashed it" but now it just goes to the bootloader menu where you choose fastboot or the other option. still boots into the OS fine tho
Click to expand...
Click to collapse
Try flashing it via fastboot.
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
Theonew said:
Try flashing it via fastboot.
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
how do i do that? terminal emulator? do i type anything else or just that and then reboot into recovery from the desktop?
douellette said:
how do i do that? terminal emulator? do i type anything else or just that and then reboot into recovery from the desktop?
Click to expand...
Click to collapse
No. You run those commands from your PC.
finally got it, opened rom manger and it had the option right in there to flash smelkus. so its all set, thanks!
douellette said:
finally got it, opened rom manger and it had the option right in there to flash smelkus. so its all set, thanks!
Click to expand...
Click to collapse
I guess that's the simpler way .
After update to cm-11-20140413 and instal newest kernel (Sultan-kernel-Pure-v1.4.0) my htc stuck at cyanogen loading screen. I don't know where's the problem. Maybe someone know the solution.
chmiela1991 said:
After update to cm-11-20140413 and instal newest kernel (Sultan-kernel-Pure-v1.4.0) my htc stuck at cyanogen loading screen. I don't know where's the problem. Maybe someone know the solution.
Click to expand...
Click to collapse
probably your kernel is the problem
try to flash the boot.img of the rom via fastboot command
fastboot flash boot boot.img
by the way are you on S-ON or S-OFF?
rzr86 said:
probably your kernel is the problem
try to flash the boot.img of the rom via fastboot command
fastboot flash boot boot.img
by the way are you on S-ON or S-OFF?
Click to expand...
Click to collapse
Thanks flashing new boot helped
rzr86 said:
probably your kernel is the problem
try to flash the boot.img of the rom via fastboot command
fastboot flash boot boot.img
by the way are you on S-ON or S-OFF?
Click to expand...
Click to collapse
I have the same problem, but i cant find the command in the bootloader
Noam_Nissel said:
I have the same problem, but i cant find the command in the bootloader
Click to expand...
Click to collapse
actually you type the command from pc
connect your device to pc in fastboot mode(in the hboot screen should say fastboot usb)
extract the boot.img from the rom and place it in your adb/fastboot folder
then open a cmd window in that folder and type the command
press enter
rzr86 said:
actually you type the command from pc
connect your device to pc in fastboot mode(in the hboot screen should say fastboot usb)
extract the boot.img from the rom and place it in your adb/fastboot folder
then open a cmd window in that folder and type the command
press enter
Click to expand...
Click to collapse
i don't fully understand what to do, can you be more detailed?
Noam_Nissel said:
i don't fully understand what to do, can you be more detailed?
Click to expand...
Click to collapse
ok
boot your device to the bootloader and select fastboot
then connect it to pc
now in your pc navigate to the folder where you have adb and fastboot(i assume you have installed sdk tools)
in that folder press shift + right click
you will see an option open a command window here
then a black window will appear
in that window type the command and press enter
but don't forget first to place the boot.img to the adb/fastboot folder
rzr86 said:
ok
boot your device to the bootloader and select fastboot
then connect it to pc
now in your pc navigate to the folder where you have adb and fastboot(i assume you have installed sdk tools)
in that folder press shift + right click
you will see an option open a command window here
then a black window will appear
in that window type the command and press enter
but don't forget first to place the boot.img to the adb/fastboot folder
Click to expand...
Click to collapse
i have this problem agian, and it doesnt help this time
Noam_Nissel said:
i have this problem agian, and it doesnt help this time
Click to expand...
Click to collapse
what kind of problem and what did you do now?
rzr86 said:
what kind of problem and what did you do now?
Click to expand...
Click to collapse
every rom im installing is getting me into bootloop, i've tried to install from revcovery and from fastboot, and it always the same problem
Noam_Nissel said:
every rom im installing is getting me into bootloop, i've tried to install from revcovery and from fastboot, and it always the same problem
Click to expand...
Click to collapse
i replied in the other thread
Does S-on and S-off matter for this issue?
Hi,
I am facing the same issue, my Sensation z710e is stuck in Cyanogenmod boot logo. following are the details.
bootloader unlocked
s-on
rooted
cwm recovery installed
tried latest CM10 for pyramid devices
I didnt try 'fastboot flash boot boot.img' command yet but i would like to know if s-on matters, my device is already rooted with cwm recovery.
I am having a similar issue as well. I have followed the instructions in this thread [ROM][STABLE][Android 4.4.4] CyanogenMod 11 with 3.0.16 kernel [July 18, 2014]. I have followed all the steps including doing a full wipe, flashed the ROM zip, gapps zip, and the aroma installer for the flash kernel several times with the same result. My screen keeps getting stuck on the white HTC loading screen.
Currently I have restored my phone to my previous ROM using a backup through 4ext recovery (v1.0.0.6 RC2). My HTC Sensation 4G T-mobile is unlocked and rooted with s-on. I have smartflash enabled on 4ext and my ROM is currently stock android 4.0.3. I did search the above mentioned thread for similar issues and a potential solution but none of the things I tried worked.
I would appreciate any help on how to fix this problem. If you need additional information I would be glad to provide it.
Tried another re-install today and everything worked fine, I guess the 5th time is the charm? I still don't know why it didn't work the other times, I did the exact same thing each time.
Tweaked for for performance, should work with any rom.
What kind of battery life effects should I expect if I use this?
Where does this file go? Sysctl? Because their is a lot of em
Here's the OTA 4.4 upgrade patched boot with sysctl baked in, unzip the boot.img and flash it through fastboot flash boot boot.img, updated twrp too. after installing, boot to recovery and flash updated SuperSU and busybox.
m0nt3s said:
Here's the OTA 4.4 upgrade patched boot with sysctl baked in, unzip the boot.img and flash it through fastboot flash boot boot.img, updated twrp too. after installing, boot to recovery and flash updated SuperSU and busybox.
Click to expand...
Click to collapse
So, can i use these with a rooted stock 4.3? To specify. I flash the boot using fastboot, then the recovery (is it twrp 3.0.2.2?)? Then reboot into the new recovery and flash SuperSU? I don't really need busybox? Or is it required?
@rkocour So, can i use these with a rooted stock 4.3? To specify. I flash the boot using fastboot, then the recovery (is it twrp 3.0.2.2?)? Then reboot into the new recovery and flash SuperSU? I don't really need busybox? Or is it required?[/QUOTE]
Yes, this boot image will work with 4.4,4.3,4.2 and I'm pretty sure it would work on 1.4 but I only have the wifi version. If some one with a new K1 tablet wouldn't mind testing by flashing this and letting me know if it works, if not I'll build one for the K1. This boot image is userdebug which grants you ultimate root. you'll notice when you flash SuperSu on it, instead of applying system-less root you get tmp-mksh.
so if your on windows, I'm attaching the best adb drivers that aren't intrusive. takes 15 seconds to install but by default it will install to C:\adb
open my computer, go to C:\adb and there should be adb.exe,adbwinapi.dll,adbwinusbapi.dll, and fastboot.exe
hold down the shift key and right click any where open in the window and you'll see open command prompt here. select it
boot your tablet into bootloader mode by powering it off and then holding down vol - and powering it back on. use the volume rock - to move to fastboot option and press the power button to select fastboot, you should have your tablet connected to your computer through usb. also unzip boot.img and recovery.img to c:\adb
from the command prompt type this command, it will look like this
C:\adb>fastboot flash boot boot.img
it will give you conformation that it wrote and then type
C:\adb>fastboot flash recovery recovery.img
same thing and after conformation unplug tablet from usb, use volume rocker to select recovery and boot into recovery.
It's important to flash both this boot and recovery together due to the fact that with much from every one on here, i'll throw in the @ later, we were able to get f2fsf working and the boot and recovery both have the updated fstab files needed, if you only flash one without the other it will error due to mismatching fstabs.
even if you don't think you use it, it's always good to install busybox, this is the newest updated version with 398 updated aplets. you're better off flashing it then not.
m0nt3s said:
Yes, this boot image will work with 4.4,4.3,4.2 and I'm pretty sure it would work on 1.4 but I only have the wifi version. If some one with a new K1 tablet wouldn't mind testing by flashing this and letting me know if it works, if not I'll build one for the K1. This boot image is userdebug which grants you ultimate root. you'll notice when you flash SuperSu on it, instead of applying system-less root you get tmp-mksh.
so if your on windows, I'm attaching the best adb drivers that aren't intrusive. takes 15 seconds to install but by default it will install to C:\adb
open my computer, go to C:\adb and there should be adb.exe,adbwinapi.dll,adbwinusbapi.dll, and fastboot.exe
hold down the shift key and right click any where open in the window and you'll see open command prompt here. select it
boot your tablet into bootloader mode by powering it off and then holding down vol - and powering it back on. use the volume rock - to move to fastboot option and press the power button to select fastboot, you should have your tablet connected to your computer through usb. also unzip boot.img and recovery.img to c:\adb
from the command prompt type this command, it will look like this
C:\adb>fastboot flash boot boot.img
it will give you conformation that it wrote and then type
C:\adb>fastboot flash recovery recovery.img
same thing and after conformation unplug tablet from usb, use volume rocker to select recovery and boot into recovery.
It's important to flash both this boot and recovery together due to the fact that with much from every one on here, i'll throw in the @ later, we were able to get f2fsf working and the boot and recovery both have the updated fstab files needed, if you only flash one without the other it will error due to mismatching fstabs.
even if you don't think you use it, it's always good to install busybox, this is the newest updated version with 398 updated aplets. you're better off flashing it then not.
Click to expand...
Click to collapse
Thank you for the detailed instructions. :good:
NinjaCoool said:
Thank you for the detailed instructions. :good:
Click to expand...
Click to collapse
can someone post the shield tablet drivers please?
supertory said:
can someone post the shield tablet drivers please?
Click to expand...
Click to collapse
here you go
m0nt3s said:
here you go
Click to expand...
Click to collapse
Thanks , flashed it and everything but got a bootloop , running 10.6 DU , could it be due to having regular root from before and flashing the systemless one?
works good, small performance boost. shield k1, optimized stock rom
pietras83 said:
works good, small performance boost. shield k1, optimized stock rom
Click to expand...
Click to collapse
How's battery life?
@supertory
Are you using the OG tablet or the k1?
supertory said:
Thanks , flashed it and everything but got a bootloop , running 10.6 DU , could it be due to having regular root from before and flashing the systemless one?
Click to expand...
Click to collapse
did you use kingoroot? or superSU as root before?
pietras83 said:
works good, small performance boost. shield k1, optimized stock rom
Click to expand...
Click to collapse
How much of a boost did it give? Did you becnhmark?
Thanks
m0nt3s said:
did you use kingoroot? or superSU as root before?
Click to expand...
Click to collapse
Was using superSU
tinybilbo said:
How much of a boost did it give? Did you becnhmark?
Thanks
Click to expand...
Click to collapse
Yes I benchmarkt it, i get 96000 pts ~3000 more than before flash
So I finally got around to scripting my sysctl setting and other misc performance settings into a script that every one can use. You can either throw it in your init.d folder or run it from script manager. I've attched a init.d enabler for our device as well as the performance script. Let me know if you have any problems but I've tested and it works. feedback welcomed. the zip is not flashable, extract to your sd card and run with script manager.
m0nt3s said:
So I finally got around to scripting my sysctl setting and other misc performance settings into a script that every one can use. You can either throw it in your init.d folder or run it from script manager. I've attched a init.d enabler for our device as well as the performance script. Let me know if you have any problems but I've tested and it works. feedback welcomed. the zip is not flashable, extract to your sd card and run with script manager.
Click to expand...
Click to collapse
where should I place the files so I can see them in the init.d section in kernel auditor ?(sp)
m0nt3s said:
@supertory
Are you using the OG tablet or the k1?
Click to expand...
Click to collapse
just seeing this and the OG tablet
Hello,
I have MIX 3 Chinese version, unlocked bootloader, flashed latest global. Fine
For security purposes, tried to lock bootloader with fastboot - I knew it may be risky- now the device is in Mi recovery 3, refused to reboot even after erase data.
How to bring it back to life.
Thanks
Use the XiaoMiTool V2.
Google it
Can you enter fastboot mode?, If yes use mi flash and flash original chinese rom.
GVN.Gallus said:
Can you enter fastboot mode?, If yes use mi flash and flash original chinese rom.
Click to expand...
Click to collapse
Yes I can enter fastboot. Even I check bootloader status now locked.
Could you refer a link where all the process is explained? I am not conversant with mi flash.
visit https://www.xiaomitool.com/V2/ and good luck
Nakbleu said:
Yes I can enter fastboot. Even I check bootloader status now locked.
Could you refer a link where all the process is explained? I am not conversant with mi flash.
Click to expand...
Click to collapse
Follow instruction here, make sure to download lastest Miflash and correct rom, for fastboot rom use mifirm.net
grandman1701 said:
visit https://www.xiaomitool.com/V2/ and good luck
Click to expand...
Click to collapse
XiaoMiTool V2 won't be able to unbrick your device in the cases "This MIUI Version can't be installed on this device" error
Nakbleu said:
Yes I can enter fastboot. Even I check bootloader status now locked.
Could you refer a link where all the process is explained? I am not conversant with mi flash.
Click to expand...
Click to collapse
Fastboot is fairly simple. Download the latest Chinese from from miui.com, unzip it, connect your device in fastboot mode, and run the flash_all.bat file. It will take a while and the command prompt window will close when it is finished and your device will reboot.
jcsww said:
Fastboot is fairly simple. Download the latest Chinese from from miui.com, unzip it, connect your device in fastboot mode, and run the flash_all.bat file. It will take a while and the command prompt window will close when it is finished and your device will reboot.
Click to expand...
Click to collapse
I am downloading the ROM.
Please can provide step by step instructions?
My understanding is to:
1. copy the rom in minimal fastboot directory
2. unzip all files in that same directory (or should I create new one?)
3. Execute the command below:
fastboot flash_all.bat
By the way, can I use fastboot with locked bootloader?
Thanks again
Nakbleu said:
I am downloading the ROM.
Please can provide step by step instructions?
My understanding is to:
1. copy the rom in minimal fastboot directory
2. unzip all files in that same directory (or should I create new one?)
3. Execute the command below:
fastboot flash_all.bat
By the way, can I use fastboot with locked bootloader?
Thanks again
Click to expand...
Click to collapse
If you have ADB installed system wide, then it doesn't matter where you unzip the full image to. The best way to have ADB installed system wide is through this method.
You don't need to type anything. Just open the folder the ROM was decompressed in, right click the flash_all.bat, and run it as administrator with your device connected in fastboot mode. It will literally do everything else.
jcsww said:
If you have ADB installed system wide, then it doesn't matter where you unzip the full image to. The best way to have ADB installed system wide is through this method.
You don't need to type anything. Just open the folder the ROM was decompressed in, right click the flash_all.bat, and run it as administrator with your device connected in fastboot mode. It will literally do everything else.
Click to expand...
Click to collapse
I unzip the rom using 7zip, but couldn't find flash_all.bat file!
Nakbleu said:
I unzip the rom using 7zip, but couldn't find flash_all.bat file!
Click to expand...
Click to collapse
Did you install ADB 1.4.3 from the thread linked to? Do you have your device connected to a USB 3 port or USB 2 port? Are you using the cable that came with your device to flash it? Were you booted into the bootloader when trying to flash?
Edit: Read that post wrong. You need to download the fastboot version. You can't flash the TWRP image using fastboot.
jcsww said:
Did you install ADB 1.4.3 from the thread linked to? Do you have your device connected to a USB 3 port or USB 2 port? Are you using the cable that came with your device to flash it? Were you booted into the bootloader when trying to flash?
Edit: Read that post wrong. You need to download the fastboot version. You can't flash the TWRP image using fastboot.
Click to expand...
Click to collapse
Yes I did all that.
I am getting error: Erase is not allowed in lock state.
Any workaround please?
re-unlock the device. it's locked right now.
erbsenmatsch said:
re-unlock the device. it's locked right now.
Click to expand...
Click to collapse
Won't be possible with the Mi unlock software as the phones been wiped - no account, no OEM allowed ticked etc.
in that case, your only hope is: sending it back to china
where did you buy it?
erbsenmatsch said:
in that case, your only hope is: sending it back to china
where did you buy it?
Click to expand...
Click to collapse
In UK. Gray import. I really don't understand why a manufacturer should let this be possible. Why not just make it unlockable with global rom? This will avoid such unwanted situation for everybody. Pissed off by Xiaomi
Hi
I can't flash my redmi note 7 pro.
Bootloader is unlocked: I did the procedure, there is the unlocked logo at boot, and Dev options says "OEM unlock: device already unlocked".
I tried the Pixel Experience way, I ran the command "fastboot flash recovery" under Windows (opens a shell window that immediately closes) and under Linux (nothing happens), and I also tried the Xiaomi flash tool which ends up with a "cannot find the file flash all bat".
Would someone have any idea?
Thanks!!
pata2000 said:
Hi
I can't flash my redmi note 7 pro.
Bootloader is unlocked: I did the procedure, there is the unlocked logo at boot, and Dev options says "OEM unlock: device already unlocked".
I tried the Pixel Experience way, I ran the command "fastboot flash recovery" under Windows (opens a shell window that immediately closes) and under Linux (nothing happens), and I also tried the Xiaomi flash tool which ends up with a "cannot find the file flash all bat".
Would someone have any idea?
Thanks!!
Click to expand...
Click to collapse
Hello,
download platform-tools (ADB) zip and extract it.
download fastboot rom and extract it.
1) copy all the files from "violet_in_global_images_V11.0.5.0.PFHINXM_20191022.0000.00_9.0_in" (Total 12 items) folder into extracted platform tools folder.
2) boot device in Fastboot mode and connect it to pc.
3) now open cmd and check if device is detected by pc.
(use following command -> fastboot devices)
4) now close cmd.
5) now go to platform tools folder and double click on "flash_all.bat" file.
6) it will flash ur device with MIUI. DONE.
rasik107 said:
Hello,
download platform-tools (ADB) zip and extract it.
download fastboot rom and extract it.
1) copy all the files from "violet_in_global_images_V11.0.5.0.PFHINXM_20191022.0000.00_9.0_in" (Total 12 items) folder into extracted platform tools folder.
2) boot device in Fastboot mode and connect it to pc.
3) now open cmd and check if device is detected by pc.
(use following command -> fastboot devices)
4) now close cmd.
5) now go to platform tools folder and double click on "flash_all.bat" file.
6) it will flash ur device with MIUI. DONE.
Click to expand...
Click to collapse
Thanks a lot for your reply. I'll try that as soon as I have some time.
Just another question:
I am running MIUI Global 11.0.4.0 | Stable (PFGMIXM) at the moment. Which is not the same as you indicated (I believe yours is Indian version dated 22 Oct 2019).
This page does not include any Global rom: https://xiaomifirmwareupdater.com/archive/firmware/violet/
And the Global ROM available on MIUI website under the RN7Pro page (https://c.mi.com//miuidownload/detail?device=1700360) is noted "lavender" and not "violet" - and I do not want to risk installing the wrong firmware, I've read a few topics and it does not ends well.
So bottom line: which one should I work with?
thanks again!
pata2000 said:
Thanks a lot for your reply. I'll try that as soon as I have some time.
Just another question:
I am running MIUI Global 11.0.4.0 | Stable (PFGMIXM) at the moment. Which is not the same as you indicated (I believe yours is Indian version dated 22 Oct 2019).
This page does not include any Global rom: https://xiaomifirmwareupdater.com/archive/firmware/violet/
And the Global ROM available on MIUI website under the RN7Pro page (https://c.mi.com//miuidownload/detail?device=1700360) is noted "lavender" and not "violet" - and I do not want to risk installing the wrong firmware, I've read a few topics and it does not ends well.
So bottom line: which one should I work with?
thanks again!
Click to expand...
Click to collapse
No need to flash Firmware.
just download fastboot rom of your region and u r good to go.
rasik107 said:
No need to flash Firmware.
just download fastboot rom of your region and u r good to go.
Click to expand...
Click to collapse
OK, I've found 2 options:
This one here on XDA:
https://forum.xda-developers.com/redmi-note-7-pro/how-to/miui-11-public-beta-violet-t3973921
(dowloading the "Fastboot ROM V11.0.6.0")
But it is 11.0.6.0 while my phone is under 11.0.4.0: is this a problem?
This other one:
Note 7 Europe V11.0.4.0.PFGEUXM at: https://www.leakite.com/xiaomi-redmi-note-7-pro-firmware-fastboot-recovery-rom/
It's not exactly the same code (PFGEUXM instead of PFGMIXM), I don't know if it makes any difference?
Sorry for keeping asking question, but I'd better be safe since I am very new to this kind of things...
and thanks a lot for your help and patience.
pata2000 said:
OK, I've found 2 options:
This one here on XDA:
https://forum.xda-developers.com/redmi-note-7-pro/how-to/miui-11-public-beta-violet-t3973921
(dowloading the "Fastboot ROM V11.0.6.0")
But it is 11.0.6.0 while my phone is under 11.0.4.0: is this a problem?
This other one:
Note 7 Europe V11.0.4.0.PFGEUXM at: https://www.leakite.com/xiaomi-redmi-note-7-pro-firmware-fastboot-recovery-rom/
It's not exactly the same code (PFGEUXM instead of PFGMIXM), I don't know if it makes any difference?
Sorry for keeping asking question, but I'd better be safe since I am very new to this kind of things...
and thanks a lot for your help and patience.
Click to expand...
Click to collapse
https://forum.xda-developers.com/redmi-note-7-pro/how-to/miui-11-public-beta-violet-t3973921
this one looks fine.
but make sure it is a fastboot file (.tgz) :good:
rasik107 said:
https://forum.xda-developers.com/redmi-note-7-pro/how-to/miui-11-public-beta-violet-t3973921
this one looks fine.
but make sure it is a fastboot file (.tgz) :good:
Click to expand...
Click to collapse
HI again
it still won't flash no matter what.
I'll deal with it
the reason I wanted to flash was essentially to remove all non necessarry stuff, which I did by following the "remove bloatware" thread.
thanks anyway
pata2000 said:
HI again
it still won't flash no matter what.
I'll deal with it
the reason I wanted to flash was essentially to remove all non necessarry stuff, which I did by following the "remove bloatware" thread.
thanks anyway
Click to expand...
Click to collapse
flash aosp recovery, then adb sideload PE rom
Srikanth0721 said:
flash aosp recovery, then adb sideload PE rom
Click to expand...
Click to collapse
Thanks!
Based on PE instructions (https://telegra.ph/Flashing-PE-for-the-first-time-using-the-AOSP-Recovery--Or-updating-12-06) and if I understand properly:
- I download the firmware and Aosp recovery
- I enter in fastboot and connect the phone to PC, then I type fastboot flash recovery.img (in folder Download+Recovery)
- Then reboot into the new recovery
- Then Tap the power + vol up(2 times vol up) together once or twice and the AOSP recovery menu will pop up
- I then type adb sideload NameofthePErom.zip
- Then: Use the volume keys to select Factory Reset and confirm. ( If you want to format data if not just ignore this part )
- Reboot!
Am I correct?
I'll give it a try even though I don't understand why flashing aosp would work when flashing other stuff didn't... But who knows!
Will let you guys know anyway.
pata2000 said:
Thanks!
Based on PE instructions (https://telegra.ph/Flashing-PE-for-the-first-time-using-the-AOSP-Recovery--Or-updating-12-06) and if I understand properly:
- I download the firmware and Aosp recovery
- I enter in fastboot and connect the phone to PC, then I type fastboot flash recovery.img (in folder Download+Recovery)
- Then reboot into the new recovery
- Then Tap the power + vol up(2 times vol up) together once or twice and the AOSP recovery menu will pop up
- I then type adb sideload NameofthePErom.zip
- Then: Use the volume keys to select Factory Reset and confirm. ( If you want to format data if not just ignore this part )
- Reboot!
Am I correct?
I'll give it a try even though I don't understand why flashing aosp would work when flashing other stuff didn't... But who knows!
Will let you guys know anyway.
Click to expand...
Click to collapse
Also check the recovery in the extracted folder, I got a twrp recovery so I guess I have facee issues with flashme.bat (immediate close).
If u face that issue, download aosp recovery separately or from their telegram channel and flash using fastboot cmd and do the rest..
Srikanth0721 said:
Also check the recovery in the extracted folder, I got a twrp recovery so I guess I have facee issues with flashme.bat (immediate close).
If u face that issue, download aosp recovery separately or from their telegram channel and flash using fastboot cmd and do the rest..
Click to expand...
Click to collapse
well it would not work either. that is not a problem though, I'll survive with the MIUI rom!
thanks