Those who are looking for stock 19s ROM, the g drive link is here
https://drive.google.com/uc?id=0BwU--kMdOmZiREUxUXR2eTgwX2s&export=download
How to flash?
Put the file downloaded in root directory
Boot into fastboot mode
Flash stock recovery
Now boot into TWRP recovery using following command
fastboot boot TWRP.img
Wipe Cache, dalvik cache and system.
Reboot to recovery
Now you will be in stock recovery
Update from here.
First boot might take time.
Is it possible to flash this with twrp?
Sent from my X520 using Tapatalk
lak2004mi said:
Is it possible to flash this with twrp?
Sent from my X520 using Tapatalk
Click to expand...
Click to collapse
No only via stock recovery
djdeve said:
Those who are looking for stock 19s ROM, the g drive link is here
https://drive.google.com/uc?id=0BwU--kMdOmZiREUxUXR2eTgwX2s&export=download
How to flash?
Put the file downloaded in root directory
Boot into fastboot mode
Flash stock recovery
Now boot into TWRP recovery using following command
fastboot boot TWRP.img
Wipe Cache, dalvik cache and system.
Reboot to recovery
Now you will be in stock recovery
Update from here.
First boot might take time.
Click to expand...
Click to collapse
if i flash stock recovery thn if i try to boot into recovery thn phone will open in stock recovery only thn hw cn i flash?
cjcool_123 said:
if i flash stock recovery thn if i try to boot into recovery thn phone will open in stock recovery only thn hw cn i flash?
Click to expand...
Click to collapse
True..
Use Chinese twrp and flash .. Works for me and many others .. Ensure to flash no verity zip post flashing
Or do changes in updater script and repack the zip
cjcool_123 said:
if i flash stock recovery thn if i try to boot into recovery thn phone will open in stock recovery only thn hw cn i flash?
Click to expand...
Click to collapse
After flashing stock recovery don't reboot you phone in stock recovery, bcoz you can't wipe system in stock recovery to do so ,
Reboot your phone into fastboot mode by pressing vol down and power button and connect your phone to PC and from CMD prompt run the following command
Fastboot boot twrp.img
Actually my phone was bootlooped when i tried installing twrp img of chinese version and im unable to flash ROM. Before this i used latest twrp and flashed RR and lineage OS. Volte worked fine in both the roms and in stock rom too. After this happened i installed AIO tool kit and flashed chinese twrp again. Then done flashing with lineage OS there the volte is broken. I thought it would be some software error and i tried flashing RR and found the same broken volte! Can anyone help me out in enabling volte in my le eco le2 (s2) x526.
Bootloader and Modem S2
Try flashing 19s bootloader and modem from here
https://host.llamasweet.tech/codeworkx/lineage/s2/
Thankx @codeworkx for this.
one more link for stock 19s rom
https://drive.google.com/file/d/1BgXejpbVug4KR5Mc6-eFWom6gVR96UhK/view?usp=drivesdk
custom to stock rom
if we are in custom rom and we have to go back for stock rom with stock recovery will it work by just copying the zip file into the phone and rename into update.zip
And then clicking on update will it work Guys ??
error while installing This package is for "le_s2_ww" devices;this is a "s2'.
bootloop
I tried to install the stock ROM provided by 2 ways :-
1) booting into previous version of twrp using fastboot commands and then the regular install after wiping required files.
2) Renaming it to update.zip and placing it into sdcard then via stock recovery.
it gets installed every time without any error but gets into boot loop with both steps.
Is there any way to get completely stock again ?
akakumar said:
I tried to install the stock ROM provided by 2 ways :-
1) booting into previous version of twrp using fastboot commands and then the regular install after wiping required files.
2) Renaming it to update.zip and placing it into sdcard then via stock recovery.
it gets installed every time without any error but gets into boot loop with both steps.
Is there any way to get completely stock again ?
Click to expand...
Click to collapse
Flash twrp via following toolkit .beacause only this recovery works to flash stock roms
https://forum.xda-developers.com/devdb/project/?id=16391#downloads
Open twrp do factory reset and wipe data , cache , dalvik cache . Dont wipe system . Then flash the rom . Dont flash magisk or any root app . Reboot . You got a notification from twrp that replace stock recovery . Dont replace recovery . Once rom boot setup everything .now bootloader is locked and twrp replaced via stock recovery .
Deepjashan said:
Flash twrp via following toolkit .beacause only this recovery works to flash stock roms
https://forum.xda-developers.com/devdb/project/?id=16391#downloads
Open twrp do factory reset and wipe data , cache , dalvik cache . Dont wipe system . Then flash the rom . Dont flash magisk or any root app . Reboot . You got a notification from twrp that replace stock recovery . Dont replace recovery . Once rom boot setup everything .now bootloader is locked and twrp replaced via stock recovery .
Click to expand...
Click to collapse
Hard Luck !!
its been more than half an hour and still at the same boot loop. the installation was successful as well , screenshot attached below.
PS: Ignore the cracked screen.
akakumar said:
Hard Luck !!
its been more than half an hour and still at the same boot loop. the installation was successful as well , screenshot attached below.
PS: Ignore the cracked screen.
Click to expand...
Click to collapse
I use this mathod everytime when i need stock rom. It works for me
my phone caps my speed to 4 Mbps after few minutes. It's not a isp or router based problem.
Actually I faced this problem after I flashed back to Eui 19s from 21s.
akakumar said:
I tried to install the stock ROM provided by 2 ways :-
1) booting into previous version of twrp using fastboot commands and then the regular install after wiping required files.
2) Renaming it to update.zip and placing it into sdcard then via stock recovery.
it gets installed every time without any error but gets into boot loop with both steps.
Is there any way to get completely stock again ?
Click to expand...
Click to collapse
Deepjashan said:
Flash twrp via following toolkit .beacause only this recovery works to flash stock roms
https://forum.xda-developers.com/devdb/project/?id=16391#downloads
Open twrp do factory reset and wipe data , cache , dalvik cache . Dont wipe system . Then flash the rom . Dont flash magisk or any root app . Reboot . You got a notification from twrp that replace stock recovery . Dont replace recovery . Once rom boot setup everything .now bootloader is locked and twrp replaced via stock recovery .
Click to expand...
Click to collapse
Alright I found a way ...I read it in some other discussion on le2 .
The step by step procedure to get stock back is listed :-
1) As usual reboot to recovery
2) wipe cache, dalvik, system and data
3)install the stock ROM
Now when you reboot you will get stuck into boot loop at the leeco logo.... wait for 5 mins and test your luck if it works otherwise follow next
4) go back to recovery by pressing vol up and power button.
5) install Andromodx kernel
Reboot and voila you have it running.
Also you can flash the stock recovery and lock OEM by fastboot commands
The only issues I have right now are two
1) the display scale is set to zoom and even if I set it to standard it reboots but doesn't change. I scaled down pixel density by adb commands but still its weird at some places
2) it crashes a lot ... sometimes when I press home or multitasking button it just goes black and EUI reboots. I also did a factory reset but no use.
If anyone can help me in that ....:laugh:
flash
djdeve said:
No only via stock recovery
Click to expand...
Click to collapse
give complted process for flash stock rom to letv le 2 x526
Error while flashing
Error while installing This package is for "le_s2_ww" devices;this is a "s2'.
Can you do something about it ?
akakumar said:
Hard Luck !!
its been more than half an hour and still at the same boot loop. the installation was successful as well , screenshot attached below.
PS: Ignore the cracked screen.
Click to expand...
Click to collapse
Just figured this out with the help of another post on a separate thread.
It seems that the latest twrp for x526 (v 3.2.1.0) has a bug such that when you format the data partition - it writes a wrong partition size.
This causes the boot loop with the stock ROM (other custom ROMs seems to be happy living with the error).
An associated side effect of the wrong partition size is that you wont be able to encrypt your phone on the custom ROM (the encryption process simply causes the phone to reboot without doing anything).
To resolve this, downgrade twrp to v 3.0.2. Then format cache/system/data.
Then mount the phone to your PC (enable MTP) and copy the stock ROM of your choice.
You need to update the "updater-script" and comment out the version check - and then you can install the stock ROM using twrp.
This worked for me.
Hope it works for you as well.
PS: Once you install the stock ROM, the data partition gets encrypted and first boot takes a lot of time.
Be patient and also know that twrp will no longer be able to decrypt your data partition (I think either twrp is broken OR the stock ROM uses some other default password to encrypt the data partition and hence decryption fails. I have tried using my screen lock PIN and it doesn't work and "default_password" does not work either.
All the best.
---------- Post added at 06:56 AM ---------- Previous post was at 06:52 AM ----------
satyamsahu366 said:
Error while installing This package is for "le_s2_ww" devices;this is a "s2'.
Can you do something about it ?
Click to expand...
Click to collapse
Open the update.zip file on your PC and navigate to META-INF/com/google/android.
You will find a file by the name updater-script.
Use your favourite text editor to open this file and then find the following line:
get_device_compatible("le_s2_ww") == "OK" || abort("This package is for "le_s2_ww" devices; this is a "" + getprop("ro.product.device") + "".");
Insert a # at the beginning of the line to get the installer to ignore the version mismatch and you should be good to go.
It should now look like this:
#get_device_compatible("le_s2_ww") == "OK" || abort("This package is for "le_s2_ww" devices; this is a "" + getprop("ro.product.device") + "".");
Now save this file and update the zip file / create a zip file again and then proceed with the installation as usual.
Related
what i did -->
1. Unlock bootloader
2. Flash cwm via "fastboot flash recovery recovery.zip"
3. Boot to recovery
4. Factory reset
5. Flash cm zip from sd card.
what i got -->
1. "E:Can't open /sdcard/cm.zip
(bad)
Installation aborted."
Then -->
1. Rebooted, copied again, booted to bootloader
2. selected recovery
Now -->
1. shows the android mascot with its lid open and "No command"
2. no cwm (where did it go ?!?!)
Everytime i flash recovery, it boots the first time (till the time I've not rebooted after flashing recovery) and still won't flash my zip file, and then the recovery won't show.
EDIT (FIXED)
WHAT WENT WRONG...
1. Was using CWM (When i was last active in android flashing, twrp was just another custom recovery, cwm was needed for cm)
2. When i did use TWRP, it was an older version, and did not work (did not even boot to recover, in fact)
3. When i did get twrp working, i used a bad cm.zip file (corrupted)
nishant_713 said:
what i did -->
1. Unlock bootloader
2. Flash cwm via "fastboot flash recovery recovery.zip"
3. Boot to recovery
4. Factory reset
5. Flash cm zip from sd card.
what i got -->
1. "E:Can't open /sdcard/cm.zip
(bad)
Installation aborted."
Then -->
1. Rebooted, copied again, booted to bootloader
2. selected recovery
Now -->
1. shows the android mascot with its lid open and "No command"
2. no cwm (where did it go ?!?!)
Everytime i flash recovery, it boots the first time (till the time I've not rebooted after flashing recovery) and still won't flash my zip file, and then the recovery won't show.
Click to expand...
Click to collapse
first mistake here is u used Flash cwm via "fastboot flash recovery recovery.zip" which is wrong u need to use .img after recovery but not zip so try once again and flash latest twrp as cwm support is ended
bloodhound42 said:
first mistake here is u used Flash cwm via "fastboot flash recovery recovery.zip" which is wrong u need to use .img after recovery but not zip so try once again and flash latest twrp as cwm support is ended
Click to expand...
Click to collapse
Thanks for the promt reply mate. Actually it was recovery. IMG only, not zip, i typed it wrong here otherwise the recovery wouldn't have loaded at all, as mentioned earlier. Moreover, I did try flashing twrp, but using twrp, I can't even get recovery to boot once (which does happen on cwm 6.0.4.7)
P.S - can it anyhow be related to bootloader ? I am on stock Lollipop. And device is dual sim (xt1033)
nishant_713 said:
Thanks for the promt reply mate. Actually it was recovery. IMG only, not zip, i typed it wrong here otherwise the recovery wouldn't have loaded at all, as mentioned earlier. Moreover, I did try flashing twrp, but using twrp, I can't even get recovery to boot once (which does happen on cwm 6.0.4.7)
P.S - can it anyhow be related to bootloader ? I am on stock Lollipop. And device is dual sim (xt1033)
Click to expand...
Click to collapse
If u r on stock lollipop then u boot loader is already upgraded and its good for twrp recovery can u try flashing twrp v 2.8.6.0 and check it out using adb if it is already rooted then try flashing by flashify and let me know
bloodhound42 said:
If u r on stock lollipop then u boot loader is already upgraded and its good for twrp recovery can u try flashing twrp v 2.8.6.0 and check it out using adb if it is already rooted then try flashing by flashify and let me know
Click to expand...
Click to collapse
Ok did that. When it booted to cwm (which is all i can manage to boot to, if at all) i selected root phone option. But it didn't root actually. Then i rooted successfully using cf auto root. Then used flashify to flash twrp image, and now when i select recovery from bootloader, it boots normally, not even showing the "no command" screen. (And yea, I'm pressing vol up to select, not power)
Update -- Ok flashed 2.8.6.0 and now boots to revovery (even after a restart) but still can't flash cm. Something pops on screen for a fraction of screen and then recovery reboots. It says "no md5 file found". Any chance of zip being corrupt ?
Update 2 -- Now my internal memory has stopped working :/ can't even take a screenshot, nor a photo. says memory full. Doesn't even copy file to memory when connected to pc. Although in recovery mode (twrp) , with usb mounted, it does copy.
nishant_713 said:
Ok did that. When it booted to cwm (which is all i can manage to boot to, if at all) i selected root phone option. But it didn't root actually. Then i rooted successfully using cf auto root. Then used flashify to flash twrp image, and now when i select recovery from bootloader, it boots normally, not even showing the "no command" screen. (And yea, I'm pressing vol up to select, not power)
Click to expand...
Click to collapse
weird did u flash normal recovery or gpe recovery ? U have to flash normal recovery and one more thing are u sure that its going into cwm recovery ?
May be the ROM is corrupted buddy download again and flash or try other Roms
Haha. After a hell lot of effort, i did get TWRP installed, and after breaking my head on why cm nightly won't install, i downloaded another one, and it installed fine. Now rocking CM 12.1 (4th device which I'm using on CM, and yet never had so much trouble getting it running..)
Hallo,
I have a problem. I flashed newest TWRP 2.8.7.1 (I also tried 2.8.7.0) onmy Mi4C and installed some ROMS (sMiUI, Decato, CM12.1) but even if flash of TWRPs and installation of ROMS was successful without error, the device is always booting into Recovery/TWRP.
So problem is that device is not starting into system!
- I tried with power button reset
- I tried with "reboot to system"
- I tried with battery removal!
- I also tried new installation of TWRP and/or several ROMS. (e.g. sideloading ADP is also working)
- I also made some (full) WIPEs / Fix Permissions
but it is always starting only to TWRP.
After device is starting, MUI-symbol appears for 5-10 seconds and then TWRP is loading, but not ROM.
What can I do? Maybe installation a new Kernel or something?
thanks in advance,
Jimmy
jjeans said:
Hallo,
I have a problem. I flashed newest TWRP 2.8.7.1 (I also tried 2.8.7.0) onmy Mi4C and installed some ROMS (sMiUI, Decato, CM12.1) but even if flash of TWRPs and installation of ROMS was successful without error, the device is always booting into Recovery/TWRP.
So problem is that device is not starting into system!
- I tried with power button reset
- I tried with "reboot to system"
- I tried with battery removal!
- I also tried new installation of TWRP and/or several ROMS. (e.g. sideloading ADP is also working)
- I also made some (full) WIPEs / Fix Permissions
but it is always starting only to TWRP.
After device is starting, MUI-symbol appears for 5-10 seconds and then TWRP is loading, but not ROM.
What can I do? Maybe installation a new Kernel or something?
thanks in advance,
Jimmy
Click to expand...
Click to collapse
Download fastboot rom and flash it
thank you that worked..
but I have still the problem when I flash several versions of TWRP, that a reboot/start of the system will always end up within the recovery.
Only a a reflash of fastboot rom helps, but then I have the old mi recovery that does not work for other ROMs :/
a strange behaviour.
So I can flash TWRP, but it is not possible to boot into the system...
Without a newer TWRP that can "boot into system" I cannot use Custom ROMS
jjeans said:
thank you that worked..
but I have still the problem when I flash several versions of TWRP, that a reboot/start of the system will always end up within the recovery.
Only a a reflash of fastboot rom helps, but then I have the old mi recovery that does not work for other ROMs :/
a strange behaviour.
So I can flash TWRP, but it is not possible to boot into the system...
Without a newer TWRP that can "boot into system" I cannot use Custom ROMS
Click to expand...
Click to collapse
How do you flash recovery tell me the procedure?
Talha7866 said:
How do you flash recovery tell me the procedure?
Click to expand...
Click to collapse
Hallo,
I used some manuals for flashing.
e.g.
en.miui.com/thread-166465-1-1.html
gammerson.com/2015/10/install-twrp-recovery-mi4c-root-it.html
+ some manuals from decuro rom and sMiUI Rom
In summary:
1. Pre steps: Download USB & Adb drivers / Download TWRP Recovery 2.8.7.0 for Xiaomi Mi4C / I also tried 2.8.7.1
2. Flashing: Boot phone into fastboot --> Connect phone with USB (I tried before and after boot to fastboot) --> CMD --> "fastboot flash recovery" <recovery-name>.img
3. After successful flash of 40-50 MB TWRP recovery I tried CMD "fastboot reboot" / I tried also without reboot command (with Vol+ & Power) / I tried also only with power button
Always system boots to TWRP recovery.
When I choose ROM afterwards with new TWRP recovery and flash it, it says successful installed, but reboot does not start to ROM
At the moment I always do fastboot rom reflash, that old system will come back and work. Flashing ROMS with old system (via updater app and old Miui recovery) is not working, it is always update error, even if I rename ROM to "update.zip".
What I never did rooting the phone, so flashify says "device not rooted". I do not know If I have to root, I assume not. I do not want root, because I will use a company app that needs an unrooted phone.
thanks,
Jimmy
jjeans said:
Hallo,
I used some manuals for flashing.
e.g.
en.miui.com/thread-166465-1-1.html
gammerson.com/2015/10/install-twrp-recovery-mi4c-root-it.html
+ some manuals from decuro rom and sMiUI Rom
In summary:
1. Pre steps: Download USB & Adb drivers / Download TWRP Recovery 2.8.7.0 for Xiaomi Mi4C / I also tried 2.8.7.1
2. Flashing: Boot phone into fastboot --> Connect phone with USB (I tried before and after boot to fastboot) --> CMD --> "fastboot flash recovery" <recovery-name>.img
3. After successful flash of 40-50 MB TWRP recovery I tried CMD "fastboot reboot" / I tried also without reboot command (with Vol+ & Power) / I tried also only with power button
Always system boots to TWRP recovery.
When I choose ROM afterwards with new TWRP recovery and flash it, it says successful installed, but reboot does not start to ROM
At the moment I always do fastboot rom reflash, that old system will come back and work. Flashing ROMS with old system (via updater app and old Miui recovery) is not working, it is always update error, even if I rename ROM to "update.zip".
What I never did rooting the phone, so flashify says "device not rooted". I do not know If I have to root, I assume not. I do not want root, because I will use a company app that needs an unrooted phone.
thanks,
Jimmy
Click to expand...
Click to collapse
I have had the same issue, and read somewhere that it is because you tried flashing a rom in stock recovery and failed, that causes recovery bootloop. I was in same position other than i erased most og my partitions except recovery, and then installed fastboot rom, and it was all good again. Not saying ypu should erase any partitions! Rather not try and flash anything in stock recovery ever.
zhart said:
I have had the same issue, and read somewhere that it is because you tried flashing a rom in stock recovery and failed, that causes recovery bootloop. I was in same position other than i erased most og my partitions except recovery, and then installed fastboot rom, and it was all good again. Not saying ypu should erase any partitions! Rather not try and flash anything in stock recovery ever.
Click to expand...
Click to collapse
Thank you for your answer.
So I can do:
1. Wipe all data (it is the only option in recovery)
2. Re-flash fastboot rom
3. Try again to flash new recovery & install custom ROM
Is that correct?
What partition can I securely erase? and how? because erase is only possible with newer Recovery.
jjeans said:
Thank you for your answer.
So I can do:
1. Wipe all data (it is the only option in recovery)
2. Re-flash fastboot rom
3. Try again to flash new recovery & install custom ROM
Is that correct?
What partition can I securely erase? and how? because erase is only possible with newer Recovery.
Click to expand...
Click to collapse
I would clean install fastboot rom, and then install the latest recovery, and try to install a rom. All from buttom so you know exactly what you have done
I accidentaly erased my partitions with fastboot. Data, boot, and internal ? I think. Would not recomend it.
Sorry, what exaclty is a fastboot rom and where do i get it?
zhart said:
I would clean install fastboot rom, and then install the latest recovery, and try to install a rom. All from buttom so you know exactly what you have done
I accidentaly erased my partitions with fastboot. Data, boot, and internal ? I think. Would not recomend it.
Click to expand...
Click to collapse
I don't know what happens all the time.
Currently I used MiFlash to make a clean fastboot install. I choosed in MiFlash "flash_all.bat" to do it. (flash_all.bat means everything was reinstalled, also recovery.img). Afterwards everything was normal, MiRecovery 2.x and Mi4C MiUI 7 chinese version was installed without error. But after manual flashing TWRP with "fastboot flash recovery xxx", the recovery loop was again! :/
So AGAIN I made a clean fastboot install again with MiFlash application, but this time I REPLACED the recovery.img with the newest TWRP (renamed to recovery.img) within the fastboot rom installation folder "images". I could see that MiFlash flashed THIS! recovery.img, but after that again the old Mi Recovery was on the device and no TWRP. But why? I replaced the original recovery.img file! How can that happen?
The flash_all.bat included flashing recovery and I could confirm it during the fastboot flash. Strange.
I used fastboot rom libra_images_V7.0.16.0.LXKCNCI_20151104.0000.4_5.1_cn
MiFlash newest version and I tried with 2 TWRP versions (one from decuro and one from sMiUI)
Maybe my phone has a problem with flahing recoverys in general I don't know.
jjeans said:
Maybe my phone has a problem with flahing recoverys in general I don't know.
Click to expand...
Click to collapse
it sound very strange i did all these steps and my phone was all good after it. is it the newest recovery? the one with material theme and touch fix you are using? if not, then thats the only difference between your procedure and mine :/
i hope you can fix it
Edit: I can see that i have the following fastboot roms downloaded, so i used one of these:
libra_images_V7.0.6.0.LXKCNCI_20150917.0000.1_5.1_cn_4dd76a55cb.tgz
or libra_images_V7.0.15.0.LXKCNCI_20151104.0000.4_5.1_cn_f6e955ee14.tgz
What I would do, is fastboot original ROM, reboot to recovery, factory reset, recboot to fastboot to re-flash TWRP and then command "fastboot boot recovery" to get to TWRP and install your ROM.
Didn't has this pb on Mi4c, but had it a few times on Nexus5.
Hope this helps...
Hello, don't know if applicable. I've read on mi forums that dev Roms need dev recovery, that's different from twrp for stock rom.....
guegangster said:
What I would do, is fastboot original ROM, reboot to recovery, factory reset, recboot to fastboot to re-flash TWRP and then command "fastboot boot recovery" to get to TWRP and install your ROM.
Didn't has this pb on Mi4c, but had it a few times on Nexus5.
Hope this helps...
Click to expand...
Click to collapse
Hallo,
thank you, that worked for me finally
I have now used another TWRP 2.8.7.1 with touch-issue, but that is now no problem.
I flashed also xiaomi.eu rom, for now seems to be stable and cleaned.
strange everything, but now it is fixed.
BR,
Jimmy
Hi,
was trying to install new ROM & completly wipe out OPO (Including OS). to do so got some error in zip file execution.
So tried to update TWRP (2.8.6 to 3.0.2) and now stuck into OPO boot screen.
Please help!
Thanks in advance!
BR//
Ashok
ashokyadav668 said:
Hi,
was trying to install new ROM & completly wipe out OPO (Including OS). to do so got some error in zip file execution.
So tried to update TWRP (2.8.6 to 3.0.2) and now stuck into OPO boot screen.
Please help!
Thanks in advance!
BR//
Ashok
Click to expand...
Click to collapse
Can you boot into the recovery? Or fastboot? Also before trying to install a new ROM did you backup your previous?
Durso81 said:
Can you boot into the recovery? Or fastboot? Also before trying to install a new ROM did you backup your previous?
Click to expand...
Click to collapse
Can't boot into recovery mode, maybe something went wrong while updating TWRP to 3.0.2 but can boot into fastboot.
also had backup of previous rom but since i can't boot into TWRP now so can't restore it. Earlier on TWRP 2.8.6 i was getting zip file execution error while restoring/installing new ROM.
So for now i have only access to fastboot mode, how to proceed futher?
ashokyadav668 said:
Can't boot into recovery mode, maybe something went wrong while updating TWRP to 3.0.2 but can boot into fastboot.
also had backup of previous rom but since i can't boot into TWRP now so can't restore it. Earlier on TWRP 2.8.6 i was getting zip file execution error while restoring/installing new ROM.
So for now i have only access to fastboot mode, how to proceed futher?
Click to expand...
Click to collapse
You have 2 options you can flash the stock rom and recovery via fastboot here is a guide http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541 (Just skip step 4 don't relock the bootloader specially if you want to install TWRP) Make sure you download the correct file there is a 64gb and a 16gb listed in this guide or you can download the stock file straight from cynogen OS here https://cyngn.com/support
Or you can reinstall TWRP via fastboot by downloading TWRP here https://dl.twrp.me/bacon/ and install your backup if its still there. If its not there you can either download and install any custom rom you want or if you want the stock rom go with option 1 above and then re-install twrp. (Always remeber after installing TWRP don't fully boot into the system or you will loose TWRP, boot straight to recovery once its done flashing TWRP by holding the power button and volume down. )
Durso81 said:
You have 2 options you can flash the stock rom and recovery via fastboot here is a guide http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541 (Just skip step 4 don't relock the bootloader specially if you want to install TWRP) Make sure you download the correct file there is a 64gb and a 16gb listed in this guide or you can download the stock file straight from cynogen OS here https://cyngn.com/support
Or you can reinstall TWRP via fastboot by downloading TWRP here https://dl.twrp.me/bacon/ and install your backup if its still there. If its not there you can either download and install any custom rom you want or if you want the stock rom go with option 1 above and then re-install twrp. (Always remeber after installing TWRP don't fully boot into the system or you will loose TWRP, boot straight to recovery once its done flashing TWRP by holding the power button and volume down. )
Click to expand...
Click to collapse
Thanks!
Do you recommend any video guide for option 2 (TWRP via Fastboot).
ashokyadav668 said:
Thanks!
Do you recommend any video guide for option 2 (TWRP via Fastboot).
Click to expand...
Click to collapse
Never watched a video so can't recommend one particular. But here is a link to all guides and how to http://forum.xda-developers.com/oneplus-one/general/index-oneplus-one-resources-compilation-t2843675
Also there is a one click tool here to make it easy
http://forum.xda-developers.com/oneplus-one/development/toolbox-oneplus-one-toolbox-t2808987
ashokyadav668 said:
Thanks!
Do you recommend any video guide for option 2 (TWRP via Fastboot).
Click to expand...
Click to collapse
Thank you Durso81,
i have successfully installed TWRP & ROM.
Thanks for your time & effort for a beginner.
Hi !
I installed TWRP to root my honor view 10 3/4 weeks ago.
Today I installed an update. And since then, the phone won't boot past TWRP (which I can access) or Huawei eRecovery mode.
When I land in the eRecovery mode it offers me to shutdown, reboot, or connect to wifi and do a factory reset. When I attempt the factory reset it tells me that downloading package info failed.
I tried to do a reset from TWRP without success gives me ERROR 9. I also tired to install the stock rom (update.zip) from TWRP and I also get ERROR 9.
I'm a complete noob when it comes to phones. Anyone have an idea of a solution ?
Thank you for reading !
Get a microsd card flash Dload file
aditya desai said:
Get a microsd card flash Dload file
Click to expand...
Click to collapse
Tried and it tells me system installation failed, maybe I have the wrong file ?
Thanks for your help!
ouamakavoula said:
Tried and it tells me system installation failed, maybe I have the wrong file ?
Thanks for your help!
Click to expand...
Click to collapse
Whats your model, if it is L09 then get the stock ramdisk image from magisk thread in development section and also search for recovery image. Flash it via fastboot and boot normally.
Never ever try ota on rooted phone.
shashank1320 said:
Whats your model, if it is L09 then get the stock ramdisk image from magisk thread in development section and also search for recovery image. Flash it via fastboot and boot normally.
Never ever try ota on rooted phone.
Click to expand...
Click to collapse
My model is L09, I flashed the stock ramdisk image and now I can no longer get into TWRP but I am unsure of what to do now ?
Thanks
ouamakavoula said:
My model is L09, I flashed the stock ramdisk image and now I can no longer get into TWRP but I am unsure of what to do now ?
Thanks
Click to expand...
Click to collapse
Able to boot to system now? You cam always flash twrp from fastboot. Avoid as of now and boot to stock rom first
shashank1320 said:
Able to boot to system now? You cam always flash twrp from fastboot. Avoid as of now and boot to stock rom first
Click to expand...
Click to collapse
When I try to boot the phone it displays the message that the phone in unlocked and should no be trusted, it shows the honor booting screen and after a few seconds shuts down and the process is repeating.
If i try to press the volume up key when booting it takes me to huawei eRecovery where I can either shutdown the phone or download recovery but it fails everytime.
Thanks
Try flash the No check recovery, boot into and wipe cache. Then reboot
Powered by View 10
Try this
1. Flash stock ramdisk img
2. Flash stock recovery img
3. Reboot to recovery with button combination ie; power and vol down together
4. Wipe data and cache
5. Reboot.
Hopefully it'll work if it doesn't flash system.img after 1 & 2 steps and follow the next steps
Hi please specify model
And what update you installed...
If the update was genuinely meant for phone I believe a data and cache partation format should fix this..
I hope you are atleast seeing the honor bootscreen...
Specify model so that we could point you to correct system.img
Also did twrp gave any errors formatting cache memory?
same here
BKL-L09
Prerequisite
1. Unlocked Bootloader
2. OrangeFox Recovery or TWRP Recovery
3. Latest adb & fastboot files
4. Stock ROM ZIP files
5. Stock Recovery [OPTIONAL]
Custom Recovery Method:
1. Enable USB-Debugging: adb reboot recovery or hold the volume up while rebooting or hold the volume down to enter bootloader & choose Reboot to Recovery by volume buttons, power key to enter.
2. Copy the Stock ROM zip to your device via adb push RMX1851_flashable_*.zip /sdcard or MTP
3. Wipe data, cache & dalvik (format data if stuck at boot animation)
4. Locate the zip file & Install
5. Flashing all the partitions with stock files takes time. Hold for a while.
6. After successful install of the zip. Your device will have Stock Recovery with Stock ROM. Finally Reboot.
Fastboot Method:
Note: Following process formats internal storage, so backup the internal storage files. If your device is in Stock ROM & somehow system partition is messed up just flash only system.
1. Download required Fastboot files
2. If downloaded 7z files, extract system.img file.
3. Enter
Code:
fastboot -w && fastboot erase system && fastboot flash recovery recovery.img && fastboot flash boot boot.img && fastboot flash vbmeta vbmeta.img && fastboot flash dtbo dtbo.img && fastboot flash system system.img && fastboot reboot
4. It takes a while to flash System partition, have patience.
5. Device reboots to system if everything is flashed successfully.
Stock Recovery Method:
1. Download Stock ROM OZIP Files & Stock Recovery
2. Copy *.ozip to sdcard or internal storage.
2. Goto fastboot & enter fastboot flash recovery recovery.img
3. Reboot to recovery, wipe (1st option). Then go back to main menu Install from storage locate the *.ozip file & install.
I'm sorry, but this doesn't work for me..stuck with the rooted but uninstalled magisk OS.. :'(
ceesiama said:
I'm sorry, but this doesn't work for me..stuck with the rooted but uninstalled magisk OS.. :'(
Click to expand...
Click to collapse
zip isn't installed successfully? can you also send screenshot, so I can help you.
4j17h said:
zip isn't installed successfully? can you also send screenshot, so I can help you.
Click to expand...
Click to collapse
https://forum.xda-developers.com/realme-3-pro/how-to/guide-unlock-bootloader-install-twrp-t3938845
I followed this guide, everything went smooth, magisk was also installed and rooted. But I tried setting fingerprint and set lock pin, But it says wrong pin everytime, so i had to reset the phone again. I used the same method above. But this time magisk won't install no matter how many times I reset my phone using the above method. So I thought if I could revert back to stock, maybe I can root and install magisk again. So i followed your guide.
After installing the stock zip and reboot to system, it stuck on bootloop(realme logo), then I flash back using the above method again, I can log in to the phone, and red notification says root has been detected, but magisk is not installed, ive tried many things but still i cannot install magisk. I've tried your guide 2/3 bootloop everytime. What could be the problem? I am not very much of a tech genus :'(
ceesiama said:
https://forum.xda-developers.com/realme-3-pro/how-to/guide-unlock-bootloader-install-twrp-t3938845
I followed this guide, everything went smooth, magisk was also installed and rooted. But I tried setting fingerprint and set lock pin, But it says wrong pin everytime, so i had to reset the phone again. I used the same method above. But this time magisk won't install no matter how many times I reset my phone using the above method. So I thought if I could revert back to stock, maybe I can root and install magisk again. So i followed your guide.
After installing the stock zip and reboot to system, it stuck on bootloop(realme logo), then I flash back using the above method again, I can log in to the phone, and red notification says root has been detected, but magisk is not installed, ive tried many things but still i cannot install magisk. I've tried your guide 2/3 bootloop everytime. What could be the problem? I am not very much of a tech genus :'(
Click to expand...
Click to collapse
ok no problem, so what do you want to know about? Clear data, cache, dalvik after or before flashing stock zip it won't bootloop. Yes, since device is decrypted lock screen doesn't work. Coming to Magisk, yes that method is not reliable. I have figured out 100% working way which works for everyone & doesn't fail anytime. Maybe I will make a new guide soon or ...Mod edit: Link to Telegram removed
4j17h said:
ok no problem, so what do you want to know about? Clear data, cache, dalvik after or before flashing stock zip it won't bootloop. Coming to Magisk, yes that method is not reliable. I have figured out 100% working way which works for everyone & doesn't fail anytime. Maybe I will make a new guide soon or ...Mod edit: Link to Telegram removed
Click to expand...
Click to collapse
I'm sorry I mistyped in the above comment, when i followed your method, zip installed successfully but it bootlooped into stock recovery everytime. I hope that clarifies a bit. I''ll be very grateful if you can help me..
ceesiama said:
https://forum.xda-developers.com/realme-3-pro/how-to/guide-unlock-bootloader-install-twrp-t3938845
I followed this guide, everything went smooth, magisk was also installed and rooted. But I tried setting fingerprint and set lock pin, But it says wrong pin everytime, so i had to reset the phone again. I used the same method above. But this time magisk won't install no matter how many times I reset my phone using the above method. So I thought if I could revert back to stock, maybe I can root and install magisk again. So i followed your guide.
After installing the stock zip and reboot to system, it stuck on bootloop(realme logo), then I flash back using the above method again, I can log in to the phone, and red notification says root has been detected, but magisk is not installed, ive tried many things but still i cannot install magisk. I've tried your guide 2/3 bootloop everytime. What could be the problem? I am not very much of a tech genus :'(
Click to expand...
Click to collapse
Try install magisk manager, maybe ur device still rooted
haditriw said:
Try install magisk manager, maybe ur device still rooted
Click to expand...
Click to collapse
no that's not how magisk works in Realme 3 Pro, if device is restarted there will be no magisk. You need to goto fastboot then goto recovery, it boots to system. We have magisk. Yes this method tricky. I am going to publish new guide, it will be simple & straight forward.
Bricked/ Bootlooping
4j17h said:
Prerequisite
1. Unlocked Bootloader
2. OrangeFox Recovery or TWRP Recovery or Pitch Black Recovery
3. Latest adb & fastboot files
4. Stock ROM zip files: RMX1851_A15
5. Stock Recovery [OPTIONAL]
Follow the below steps:
1. Enable USB-Debugging: adb reboot recovery or hold the volume up while rebooting or hold the volume down to enter bootloader & choose Reboot to Recovery by volume buttons, power key to enter.
2. Copy the Stock ROM zip to your device via adb push RMX1851_flashable_A15.zip /sdcard or MTP
3. Wipe data, cache & dalvik
4. Locate the zip file & Install
5. Flashing all the partitions with stock files takes time. Hold for a while.
6. After successful install of the zip, Reboot to System. You get the stock Recovery & stock ROM.
Previous Firmware: RMX1851_A14 Google Drive || AndroidFileHost || Mega Cloud storage
Note: This guide will be updated in coming days with fastboot flash files & custom recovery flashable files with latest versions.
Click to expand...
Click to collapse
pls help me, im stuck on bootlooop :'(
---------- Post added at 04:53 PM ---------- Previous post was at 04:52 PM ----------
4j17h said:
Prerequisite
1. Unlocked Bootloader
2. OrangeFox Recovery or TWRP Recovery or Pitch Black Recovery
3. Latest adb & fastboot files
4. Stock ROM zip files: RMX1851_A15
5. Stock Recovery [OPTIONAL]
Follow the below steps:
1. Enable USB-Debugging: adb reboot recovery or hold the volume up while rebooting or hold the volume down to enter bootloader & choose Reboot to Recovery by volume buttons, power key to enter.
2. Copy the Stock ROM zip to your device via adb push RMX1851_flashable_A15.zip /sdcard or MTP
3. Wipe data, cache & dalvik
4. Locate the zip file & Install
5. Flashing all the partitions with stock files takes time. Hold for a while.
6. After successful install of the zip, Reboot to System. You get the stock Recovery & stock ROM.
Previous Firmware: RMX1851_A14 Google Drive || AndroidFileHost || Mega Cloud storage
Note: This guide will be updated in coming days with fastboot flash files & custom recovery flashable files with latest versions.
Click to expand...
Click to collapse
pls help me, im stuck on bootloop :'(
malakaz27 said:
pls help me, im stuck on bootlooop :'(
---------- Post added at 04:53 PM ---------- Previous post was at 04:52 PM ----------
pls help me, im stuck on bootloop :'(
Click to expand...
Click to collapse
I have seen you have started a new thread of bootloop. Is this because you flashed one of these stock zip? you were going back to stock from los?
this method worked perfectly fine for me. i tried both lineage os roms available and both of them caused bootloop or end up destroying boot. so thanks to developer for making this zip file.
4j17h said:
I have seen you have started a new thread of bootloop. Is this because you flashed one of these stock zip? you were going back to stock from los?
Click to expand...
Click to collapse
hi i am stuck in bootloop after flashing all stuff in fastboot guide
leo77g said:
hi i am stuck in bootloop after flashing all stuff in fastboot guide
Click to expand...
Click to collapse
bootloop to recovery? have you tried fastboot -w usually this should boot to system or else flash stock recovery, wipe full. This should definitely get back the device to system.
4j17h said:
bootloop to recovery? have you tried fastboot -w usually this should boot to system or else flash stock recovery, wipe full. This should definitely get back the device to system.
Click to expand...
Click to collapse
formatting worked and thanx for help )
Moderators' Announcement: I've removed the links to Telegram and references to it. This is not a development thread, and support is to be provided through XDA. Many posts proved this has not been the case!
You may be asking, "Why was my Telegram or Whatsapp thread closed?"
Well, it's just becoming too much.
Going forward, we will only allow one Telegram chat link on a development thread by the ROM's developer and only if thorough support is still provided in the ROM thread on XDA.
All discussion channels, photography channels, whatnot channels will be strongly discouraged and removed with immediate effect. Please reference the forum rules:
Self-promotion is forbidden, this includes blogs, social media and video channels etc. Random links will be removed.
Click to expand...
Click to collapse
Also, we now have an official XDA Discord Server. We would encourage you to try it out.
Announcing the Official XDA-Developers Discord Server
FYI
Thanks,
The Moderation Team
Click to expand...
Click to collapse
Need Help
Hi, everybody. Really need help.
There is a phone Realme X Lite. Write that it is Realme 3 Pro for the Chinese market, as well as firmware.
My version was: RMX1851_11_A.05
Tried to flash RMX1851EX_11_OTA_0150_all_2Zfcensdoezk.ozip, recovery gave an error, *_0140_* wrote that the current version is newer.
In depth test APK on the version out of the box wrote that this version of the phone is not supported, so the bootloader could not unlock.
But in the official website came across an offer to join the testing of Android Q
r1.realme.net/general/20190522/1558492614147.pdf
There are two files, the second for rollback.
I installed P2Q, everything went well, but the SnapDragon camera is used and it is terrible if there is not enough light. In depth test is not even installed, apparently not supported in the new version.
I decided to roll back, chose in Recovery Q2P archive, there were no errors, but after rebooting the phone hangs on the initial screen saver and after 10 minutes throws in the recovery with the error "Data error, select wipe data to recovery system". Wipe doesn't help. The same with other archives for Realme 3 Pro.
Also found RMX1851_11_A.12_190423_abecd1fa.ofp for firmware via MsmDownloadTool, but it requires authorization and support refuses to call login details.
Can who faced a similar problem on this or other phone.
Please help, pay for the time spent =)
ResSetOk said:
Hi, everybody. Really need help.
There is a phone Realme X Lite. Write that it is Realme 3 Pro for the Chinese market, as well as firmware.
My version was: RMX1851_11_A.05
Tried to flash RMX1851EX_11_OTA_0150_all_2Zfcensdoezk.ozip, recovery gave an error, *_0140_* wrote that the current version is newer.
In depth test APK on the version out of the box wrote that this version of the phone is not supported, so the bootloader could not unlock.
But in the official website came across an offer to join the testing of Android Q
r1.realme.net/general/20190522/1558492614147.pdf
There are two files, the second for rollback.
I installed P2Q, everything went well, but the SnapDragon camera is used and it is terrible if there is not enough light. In depth test is not even installed, apparently not supported in the new version.
I decided to roll back, chose in Recovery Q2P archive, there were no errors, but after rebooting the phone hangs on the initial screen saver and after 10 minutes throws in the recovery with the error "Data error, select wipe data to recovery system". Wipe doesn't help. The same with other archives for Realme 3 Pro.
Also found RMX1851_11_A.12_190423_abecd1fa.ofp for firmware via MsmDownloadTool, but it requires authorization and support refuses to call login details.
Can who faced a similar problem on this or other phone.
Please help, pay for the time spent =)
Click to expand...
Click to collapse
since your bootloader is locked, all you can do is wipe full data or flash back P2Q then format & then flash Q2P.
4j17h said:
since your bootloader is locked, all you can do is wipe full data or flash back P2Q then format & then flash Q2P.
Click to expand...
Click to collapse
I did Wipe before and after firmware, on P2Q is stitched without problems, but under firmware in Q2P in recovery writes, that not managed wipe userdata. The data was not encrypted, the password is not asked.
do you have video for Fastboot Method ?
[No message]