Help restoring S3 X522 to stock rom - LeEco Le 2 Questions & Answers

hi friends! I tried lineageos but can't live without reliable camera. Now trying to restore stock. but unsuccessful so far. My current status is,
1. I am able to boot to fastboot
2. I am able to boot to recovery. (twrp 3.2.1.0)
3. tried to flash OEM rom bellow (had to modify "updater-script", delete first two lines of code), after reboot, phone stuck on Leeco boot screen. This is the instructions I followed, https://youtu.be/v_aohNnvT_Q
S2_X522-NA-OP-IFXNAOP5802012141S-5.8.020S.zip
S2_X522-NA-OP-IFXNAOP5802102141S-5.8.021S.zip
Any helps are much appropriated. :good::good::good:

apparently, I didn't do anything wrong. tried to flash again and again, suddenly it booted back to stock.

What am I missing here, your description says x522, even the filenames you list and the video say x526...

leo221 said:
apparently, I didn't do anything wrong. tried to flash again and again, suddenly it booted back to stock.
Click to expand...
Click to collapse
Where are you from?

leo221 said:
hi friends! I tried lineageos but can't live without reliable camera. Now trying to restore stock. but unsuccessful so far. My current status is,
1. I am able to boot to fastboot
2. I am able to boot to recovery. (twrp 3.2.1.0)
3. tried to flash OEM rom bellow (had to modify "updater-script", delete first two lines of code), after reboot, phone stuck on Leeco boot screen. This is the instructions I followed,
S2_X522-NA-OP-IFXNAOP5802012141S-5.8.020S.zip
S2_X522-NA-OP-IFXNAOP5802102141S-5.8.021S.zip
Any helps are much appropriated. :good::good::good:
Click to expand...
Click to collapse
I am also having same problem on letv x526 indian version. After installing stock rom the phone stucks in bootloop. I tried using the chinese recovery also but no luck. I waited atmost 30 min for the phone to get out of boot loop.
Any solution. Pls help

amrit0 said:
I am also having same problem on letv x526 indian version. After installing stock rom the phone stucks in bootloop. I tried using the chinese recovery also but no luck. I waited atmost 30 min for the phone to get out of boot loop.
Any solution. Pls help
Click to expand...
Click to collapse
I flashed multiple times to make it work. you try the same. follow the exact wipe...restore sequence in the video.

leo221 said:
I flashed multiple times to make it work. you try the same. follow the exact wipe...restore sequence in the video.
Click to expand...
Click to collapse
Kk i will try that.
By the way which rom version have you flashed?

amrit0 said:
Kk i will try that.
By the way which rom version have you flashed?
Click to expand...
Click to collapse
S2_X522-NA-OP-IFXNAOP5802102141S-5.8.021S.zip
my phone is X522 US version.

leo221 said:
S2_X522-NA-OP-IFXNAOP5802102141S-5.8.021S.zip
my phone is X522 US version.
Click to expand...
Click to collapse
And which recovery were u using? Were you wiping cache immidiately after installing the rom?
Also should i wipe internal storage or not?

amrit0 said:
And which recovery were u using? Were you wiping cache immidiately after installing the rom?
Also should i wipe internal storage or not?
Click to expand...
Click to collapse
twrp 3210. I followed EXACT steps in the video and must be in that wiping sequence. if i don't, phone wouldn't boot.

leo221 said:
twrp 3210. I followed EXACT steps in the video and must be in that wiping sequence. if i don't, phone wouldn't boot.
Click to expand...
Click to collapse
I installed the rom 7-8 times but phone didnt booted. What should i do now?

Is this for rom mtk or not snapdragon?

When you flash stock rom via twrp successfully then before reboot flash andromax kernel for le2 after flash kernel then reboot system now this time your phone starts eui rom but remember first boot take some time maybe 2-5 minutes.

Use Red Wolf Recovery
For le S3 X522 US Version
--------------------------------
leo221 said:
hi friends! I tried lineageos but can't live without reliable camera. Now trying to restore stock. but unsuccessful so far. My current status is,
1. I am able to boot to fastboot
2. I am able to boot to recovery. (twrp 3.2.1.0)
3. tried to flash OEM rom bellow (had to modify "updater-script", delete first two lines of code), after reboot, phone stuck on Leeco boot screen. This is the instructions I followed, https://youtu.be/v_aohNnvT_Q
S2_X522-NA-OP-IFXNAOP5802012141S-5.8.020S.zip
S2_X522-NA-OP-IFXNAOP5802102141S-5.8.021S.zip
Any helps are much appropriated. :good::good::good:
Click to expand...
Click to collapse
Hi i also suffered from this problem very long time.
But phone stuck on Leeco boot screen
I accidentally found custom recovery "Red Wolf"
which supports EUI ROMs
which was mentioned in features as "Automatic EUi boot image patching"
Recovery X52X V3.1-017
You can download it from my Google drive also.
Steps to Install ( For le S3 X522 US Version)
----------------------------------------------
1. delete first two lines in update-script
2. Install red wolf recovery
3. This can be installed from fastboot
Or you can install it directly from
twrp. (if you dont know ask here / google)
4. Go to recovery > swipe to allow modifications
5. wipe all partitions (excluding boot)
6. plug your le S3 X522 to computer
7. Go to my computer and copy
S2_X522-NA-OP-IFXNAOP5802012141S-5.8.020S.zip
to internal storage
8. you can copy supersu also at same time
and root if you want
9. Steps from 9-11 only needed if you have ever
encountered no os installed after flashing and reboot
10. press power button long and restart system
your phone wont have any os this time so your phone
will go to boot screen and show leeco logo
11. wait 30 seconds and press volume up(+) button and power key
you will go to recovery
12. Now you have followed step 6 so you will have
S2_X522-NA-OP-IFXNAOP5802012141S-5.8.020S.zip
in internal storage(additionally supersu file if you copied)
13. install S2_X522-NA-OP-IFXNAOP5802012141S-5.8.020S.zip
and ( additionally you can install supersu).
wait until all install finishes.
14. reboot it eui should appear within 5 minutes
enjoy
Finally when you rebooting if wolf recovery said os not installed
system will stuck on boot screen so
concentrate on steps 9-11
I have tested installation more than 10 times around 4 times i received os not installed message.

Related

Can't Boot Into System, Only TWRP

Here's the whole story:
I was on an unofficial build of RR CM13, encrypted, using TWRP 3.0.2-1.
I wiped data, dalvik, cache, and flashed the newest Official RR 7.1.1 and open-gapps.
I boot into the new ROM and start setting stuff up.
I restore some apps' data using Titanium Backup, then reboot.
On reboot I'm greeted with the device setup screen
I reboot, wipe, reflash a bunch of times
A few times:
When I rebooted after using the system my PIN doesn't decrypt the system/data (booting into the system)
When I rebooted after using TWRP my PIN does decrypt (booting into the system)
At some point during this I try wiping everything from TWRP, but it freezes, goes black, and then the notification LED turns white. I hold the power button and boot back to TWRP.
Apparently wiping /data is the problem (everything else wipes just fine if I do them individually)
I boot back into the system, set it up, and do a full factory reset from there (after offloading my stuff from Internal Storage)
Back to TWRP, now no matter what I flash or restore, I don't end up booting into the system, only into TWRP
I've also tried TWRP 3.0.4-0 (which wouldn't decrypt my data), and I've reflash TWRP a few times.
How do I actually boot into my system? It's been 7 hours, and I'm losing my mind.
Deleted
Boot to your ROM through the power button...
Manually..
Just Passing By said:
Not sure if you've tried this yet, but considering you've already backed your phone up, I'd just recommend to start clean and use the unbricker tool.
Click to expand...
Click to collapse
Do what he said. You've already wiped your internal storage, so just start from scratch.
Just Passing By said:
Not sure if you've tried this yet, but considering you've already backed your phone up, I'd just recommend to start clean and use the unbricker tool.
Click to expand...
Click to collapse
Thanks, that worked, but now when I try to boot into recovery I get a black screen.
I was able to use the Toolkit to boot into TWRP and flash my ROM. Any ideas how to fix this?
RustySpackleford said:
Thanks, that worked, but now when I try to boot into recovery I get a black screen.
I was able to use the Toolkit to boot into TWRP and flash my ROM. Any ideas how to fix this?
Click to expand...
Click to collapse
flash twrp
adb push os zip
adb push su
flash all , if needed format data.
This is what I have done yesterday,
edit: If u brick I don't take any responsibility.
Deleted
TWRP has enormous potential and so does ADB try to use them.
First ensure TWRP is working, If it works you're 80℅ safe , then further do some XDA search as per your need. I am sure it will work again.
This is purely my experience since 6 years I am flashing .
uttam.ace said:
TWRP has enormous potential and so does ADB try to use them.
First ensure TWRP is working, If it works you're 80℅ safe , then further do some XDA search as per your need. I am sure it will work again.
This is purely my experience since 6 years I am flashing .
Click to expand...
Click to collapse
hi bro, i facing 'white led black screen' on my 3T, can you explain what should i do for fix this?
please.. :crying:
bluuquthug said:
hi bro, i facing 'white led black screen' on my 3T, can you explain what should i do for fix this?
please.. :crying:
Click to expand...
Click to collapse
Hi ! Do not worry try this
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
uttam.ace said:
Hi ! Do not worry try this
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Click to expand...
Click to collapse
it cant bro, i tried using that unbrick tool but still facing same problem after i update or flashing ROM again.
or can you explain step by step to fix that? almost all ROM i tried but still happening, am i wrong?
bluuquthug said:
it cant bro, i tried using that unbrick tool but still facing same problem after i update or flashing ROM again.
or can you explain step by step to fix that? almost all ROM i tried but still happening, am i wrong?
Click to expand...
Click to collapse
Your TWRP is working right!
go to TWRP/ Advanced/ADB Sideload
type "adb sideload /path/to/rom.zip"
Mate, recommend using ADB Sideload on TWRP itself is the only viable option you have. OR if that doesn't work and you still have the PIN issues, you should definitely use the Unbrick Tool and get everything back to Stock, and then reflash everything
Note: Using the unbrick tool will cause it to relock bootloader, so you're gonna have to start over again.
Cheers!

[GUIDE] Fix TWRP Recovery Script Loop & Unable to boot

Hello!
This is actually a common "thing" across many devices so just because this thread is on the Oneplus 5 forum doesn't mean it won't work for your device!
So I know exactly what you're going through....
THE PROBLEM
You've flashed a Zip file, everything seemed to work fine, you pressed the reboot button.... But then... Black screen, blue LED (or something like that)....
You then try to reboot to recovery and then you see "Running Open Recovery Script" and you manage to decipher "Wiping Data", either you clean flashed your ZIP file and this is not a problem or you dirty flashed it and so you're screaming at your phone because it just wiped everything without you asking (I mean, this never happened to me or anything I'm just trying to imagine what it would look like :crying
You then try a few things but you're phone won't even get close to the Bootanimation and keeps trying to boot up into recovery and keeps on Wiping your data which is now non-existent.
THE FIX :fingers-crossed:
Method 1/
This is the most convenient and easiest method but it might not work for you, I'm not even entirely sure how I made it work for me... Anyway:
Once the phone has booted up into recovery and is flashing the ZIP, try the following:
WILL UPDATE AS SOON AS I FIND THE EXACT METHOD
-Taking a screenshot (Power+volume)
-Pressing the back, home and récents button as many times as you can
-Pressing the power button
Basically, for now until I'm certain on what gets you out of this script thing, press every button on the phone a few times (that's what I did)
Click to expand...
Click to collapse
Method 2 [FAILSAFE]/
This method will work no matter what (if your problem is the one this thread covers that is), but it's quite teedious!
Step1/ Boot into the Bootloader (Power+Volume up)
Step2/ Install ADB & Fastboot on your PC (Google)
Step3/Download Stock recovery & TWRP
Step 4/Move both files to the ADB folder for ease of access
Step5/Type in
Code:
fastboot flash recovery STOCK_RECOVERY.img
(change file name)
Step 6/Boot into this new recovery
Step 7/ Ponder for a minute at how useless it is
Step 8/Boot into Bootloader again
Step 9/Type into terminal
Code:
fastboot flash recovery TWRP_RECOVERY.img
(change file name)
Step 10/Boot into recovery and wipe everything except Internal storage
Step 11/Flash ROM again!
VOILA! :fingers-crossed:
Hope it helped, if you have any questions, feel free to ask me!
Cheers, Matt
I had this issue when I was flashing various roms, in my case it ended up being that some of the roms were incompatible with data being formatted as ext4 (mainly oos based ones, but a few others as well) since I went full f2fs, haven't seen this issue. That might be something to consider adding, it's pretty destructive, though, as going with f2fs on /data formats /sdcard, too
I had this issue when I was flashing various roms (xXx NoLimits, ExperienceOS) on the encrypted data partition. Only FreedomOS flashing and booting ok
dragynbane222 said:
I had this issue when I was flashing various roms, in my case it ended up being that some of the roms were incompatible with data being formatted as ext4 (mainly oos based ones, but a few others as well) since I went full f2fs, haven't seen this issue. That might be something to consider adding, it's pretty destructive, though, as going with f2fs on /data formats /sdcard, too
Click to expand...
Click to collapse
Ahh, that's interesting
R0iZ said:
I had this issue when I was flashing various roms (xXx NoLimits, ExperienceOS) on the encrypted data partition. Only FreedomOS flashing and booting ok
Click to expand...
Click to collapse
I had it on my old phone once (Oneplus X) so it's not rom/device specific... And I don't think it's a bug, more a compatibility issue...
first method doesnt work for me (and i have not expecting it to work)
second method should work but i have a little problem, i cant boot into bootloader
can someone help me with this
phone: Doogee X5
Fyzik753 said:
first method doesnt work for me (and i have not expecting it to work)
second method should work but i have a little problem, i cant boot into bootloader
can someone help me with this
phone: Doogee X5
Click to expand...
Click to collapse
You can't boot into bootloader? Are you sure? Long less power + Volume up
Fyzik753 said:
first method doesnt work for me (and i have not expecting it to work)
second method should work but i have a little problem, i cant boot into bootloader
can someone help me with this
phone: Doogee X5
Click to expand...
Click to collapse
Are you trying to install/fix TWRP designed for OnePlus 5 into a different phone? Good luck!
i have a problem with instaling twrp ...
example:
phone have bootloader unlocked
flashing original 4.5.14 firmware .... all good ... boot phone ... settings ... done
reboot to bootloader ... flash twrp (or blu_spark twrp) ... done ... reboot to twrp .. all good
reboot to system ... done. poweroff (or restart)...
boot to recovery ... surprise ... original recovery ... not twrp
flash again twrp ... done ... boot to system ... reboot to recovery ... original recovery ....
saw .. what is going on ?
thanks
aoprea said:
i have a problem with instaling twrp ...
example:
phone have bootloader unlocked
flashing original 4.5.14 firmware .... all good ... boot phone ... settings ... done
reboot to bootloader ... flash twrp (or blu_spark twrp) ... done ... reboot to twrp .. all good
reboot to system ... done. poweroff (or restart)...
boot to recovery ... surprise ... original recovery ... not twrp
flash again twrp ... done ... boot to system ... reboot to recovery ... original recovery ....
saw .. what is going on ?
thanks
Click to expand...
Click to collapse
OxygenOS overwrites the recovery with stock one when you boot into the OS..
to avoid this, after flashing twrp, (without rebooting to system) flash SuperSU or Magisk immediately..
iamelton said:
OxygenOS overwrites the recovery with stock one when you boot into the OS..
to avoid this, after flashing twrp, (without rebooting to system) flash SuperSU or Magisk immediately..
Click to expand...
Click to collapse
thanks ... solved with install magisk
ps. I was accustomed with samsung phones where this does not happen...
Hi, I hope there's somebody who can help me with this.
I think, method could help me, but when I try to flash the recovery, I get this message:
Code:
target reported max download size of 535822336 bytes
sending 'recovery' (27525 KB)...
OKAY [ 0.914s]
writing 'recovery'...
(bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.954s
Any Ideas to solve this?
iamelton said:
OxygenOS overwrites the recovery with stock one when you boot into the OS..
to avoid this, after flashing twrp, (without rebooting to system) flash SuperSU or Magisk immediately..
Click to expand...
Click to collapse
i have op5
i don't know what should i do - i install magisk and twrp - is it in the twrp i do that i wipe and i flash rom
but i find the some problem open and after boot i don't found the twrp and my recovery return to official recov
please help
my phone without root is worthless
Im_Mattgame said:
Hello!
This is actually a common "thing" across many devices so just because this thread is on the Oneplus 5 forum doesn't mean it won't work for your device!
So I know exactly what you're going through....
THE PROBLEM
You've flashed a Zip file, everything seemed to work fine, you pressed the reboot button.... But then... Black screen, blue LED (or something like that)....
You then try to reboot to recovery and then you see "Running Open Recovery Script" and you manage to decipher "Wiping Data", either you clean flashed your ZIP file and this is not a problem or you dirty flashed it and so you're screaming at your phone because it just wiped everything without you asking (I mean, this never happened to me or anything I'm just trying to imagine what it would look like :crying
You then try a few things but you're phone won't even get close to the Bootanimation and keeps trying to boot up into recovery and keeps on Wiping your data which is now non-existent.
THE FIX :fingers-crossed:
Method 1/
This is the most convenient and easiest method but it might not work for you, I'm not even entirely sure how I made it work for me... Anyway:
Once the phone has booted up into recovery and is flashing the ZIP, try the following:
Method 2 [FAILSAFE]/
This method will work no matter what (if your problem is the one this thread covers that is), but it's quite teedious!
Step1/ Boot into the Bootloader (Power+Volume up)
Step2/ Install ADB & Fastboot on your PC (Google)
Step3/Download Stock recovery & TWRP
Step 4/Move both files to the ADB folder for ease of access
Step5/Type in
Code:
fastboot flash recovery STOCK_RECOVERY.img
(change file name)
Step 6/Boot into this new recovery
Step 7/ Ponder for a minute at how useless it is
Step 8/Boot into Bootloader again
Step 9/Type into terminal
Code:
fastboot flash recovery TWRP_RECOVERY.img
(change file name)
Step 10/Boot into recovery and wipe everything except Internal storage
Step 11/Flash ROM again!
VOILA! :fingers-crossed:
Hope it helped, if you have any questions, feel free to ask me!
Cheers, Matt
Click to expand...
Click to collapse
You saved me bro my life is your from now thankyou love u♥

[STOCK BACKUP] P8 LITE 2017 Alternative method

TWRP needed
Many people still have problems with bringing the device back to the ROM and Recovery stock, so once and for all I decided to make a simple post guide:
​ This is the backup.
​ https://mega.nz/#F!dQJAAJiT!9GCaOUGCjiahuNBkEbKIZQ
ONLY FOR P8 LITE 2017 [PRA-LX1C55] (but you can try with another branded or unbranded same device)
I do not feel responsible for any problems.
1: Put the ''BACKUPS'' folder in a new folder called ''TWRP'' in external_sd then reboot to TWRP.
2: In TWRP; Wipe cache and Dalvik cache, data and system. (Also Vendor if it was previously flashed)
3: Click on the restore option and select the backup; swipe and wait. When the installation finishes in my case, if an error appears you do not have to worry, you only need this backup to restore the original ROM and recovery after with eRecovery.
4: Reboot the device and when it shows the ''initial unlocked bootloader screen'', press vol +; it boot on eRecovery.
5: In eRecovery, if it shows erase data click on it firstly, if not, click directly on download and install fw and rom on the first option.
6: Insert your wifi password, and wait for the download of rom and recovery . An Italian TIM Branded c55b105 will be downloaded .
Installation performs automatic recovery, and twrp recovery will be overwritten.
Do not worry if you restart a couple of times, if all goes well you will have to wait for the device to boot and everything will be restored, if you want, you can also relock the bootloader.
I hope I can solve your problem:laugh::laugh::laugh:.​
you are awesome!
you saved me! thanks!!!!!!:good::fingers-crossed:
SandXFX said:
you saved me! thanks!!!!!!:good::fingers-crossed:
Click to expand...
Click to collapse
Fr0nK said:
Click to expand...
Click to collapse
can someone give me a stock bakcup for pra-lx2
dazokevin28 said:
can someone give me a stock bakcup for pra-lx2
Click to expand...
Click to collapse
None here has lx2 version sorry , but you can also try this guide to back stock fw (without download lx1 fw obv)
GreenScreen problem
Hello, tried to perform that solution, but encounter a major problem.
In 2nd point I did wiped the Vendor as well (cause was using the haky's LinOS 14.1 previously);
then restored files from your backup (get warning "createTarFork() process ended with ERROR=255" at the end), and reboot.
Then some wierd stuff shows up - instead of any Huawei logo or unlocked bootload screen - I've got GreenScreen witch 2 rectangles (Blue&Red).
But it enters eRecovery; so yet without any worries tried to start recovery over there - "Getting package info failed" made that impossible.
And now I'm bricked a little bit - cause can not enter TWRP, can not flash the TWRP again, only thing that is possible - the eRecovery mode.
Anyone have any ideas how ot unbrick it?
<!-- Edit -->
Sorry for troubles, as just realized the steps made my phone locked again, so "fastboot oen unlock [...]" it again, and now everything is like before.
<!-- Edit2 -->
Already installed SlimOS and everything seems just fine. Therefore the spectacular GreenScreen still showing up every rebooting, even though I did wiped eveything (every single position) in TWRP since then. x)
Would be greatfull for any informations about this phenomenon.
Sixter said:
Hello, tried to perform that solution, but encounter a major problem.
In 2nd point I did wiped the Vendor as well (cause was using the haky's LinOS 14.1 previously);
then restored files from your backup (get warning "createTarFork() process ended with ERROR=255" at the end), and reboot.
Then some wierd stuff shows up - instead of any Huawei logo or unlocked bootload screen - I've got GreenScreen witch 2 rectangles (Blue&Red).
But it enters eRecovery; so yet without any worries tried to start recovery over there - "Getting package info failed" made that impossible.
And now I'm bricked a little bit - cause can not enter TWRP, can not flash the TWRP again, only thing that is possible - the eRecovery mode.
Anyone have any ideas how ot unbrick it?
<!-- Edit -->
Sorry for troubles, as just realized the steps made my phone locked again, so "fastboot oen unlock [...]" it again, and now everything is like before.
<!-- Edit2 -->
Already installed SlimOS and everything seems just fine. Therefore the spectacular GreenScreen still showing up every rebooting, even though I did wiped eveything (every single position) in TWRP since then. x)
Would be greatfull for any informations about this phenomenon.
Click to expand...
Click to collapse
unfortunately I have not encountered this problem
to restore the phone check here
https://forum.xda-developers.com/p8...uide-unbrick-huawei-p8-lite-2017-pra-t3713574
regards
Plz upload as a single zip, not a whole folder on mega .
Can someone give me a stock back up for PRA-LX1C432B### Single Sim please and thanks
Fr0nk0 said:
TWRP needed
Many people still have problems with bringing the device back to the ROM and Recovery stock, so once and for all I decided to make a simple post guide:
​ This is the backup.
​ https://mega.nz/#F!dQJAAJiT!9GCaOUGCjiahuNBkEbKIZQ
ONLY FOR P8 LITE 2017 [PRA-LX1C55] (but you can try with another branded or unbranded same device)
I do not feel responsible for any problems.
1: Put the ''BACKUPS'' folder in a new folder called ''TWRP'' in external_sd then reboot to TWRP.
2: In TWRP; Wipe cache and Dalvik cache, data and system. (Also Vendor if it was previously flashed)
3: Click on the restore option and select the backup; swipe and wait. When the installation finishes in my case, if an error appears you do not have to worry, you only need this backup to restore the original ROM and recovery after with eRecovery.
4: Reboot the device and when it shows the ''initial unlocked bootloader screen'', press vol +; it boot on eRecovery.
5: In eRecovery, if it shows erase data click on it firstly, if not, click directly on download and install fw and rom on the first option.
6: Insert your wifi password, and wait for the download of rom and recovery . An Italian TIM Branded c55b105 will be downloaded .
Installation performs automatic recovery, and twrp recovery will be overwritten.
Do not worry if you restart a couple of times, if all goes well you will have to wait for the device to boot and everything will be restored, if you want, you can also relock the bootloader.
I hope I can solve your problem:laugh::laugh::laugh:.​
Click to expand...
Click to collapse
thanks for your tread it's very helpfully but i flashed the oeminfo only without restore everything just the oeminfo backup i changed in img mode and i flashed with twrp and done. I reboot to eRecovery mode, connect to WiFi and done i installed the firmware pra-lx1c55b105 with success TIM firmware
thanks for your great job ?
jalel25 said:
thanks for your tread it's very helpfully but i flashed the oeminfo only without restore everything just the oeminfo backup i changed in img mode and i flashed with twrp and done. I reboot to eRecovery mode, connect to WiFi and done i installed the firmware pra-lx1c55b105 with success TIM firmware
thanks for your great job
Click to expand...
Click to collapse
Nice to hear. :fingers-crossed:

Need help with Me176c, fastboot.... 123# screen

My Asus memo pad 7 is stuck on fastboot.... 123# screen. I've tried temporary recovery and had success installation with lineage-14.1 but nothing changed. Please help. Thanks.
Did you have Lollipop installed before?
Also, do I understand it correctly that you're able to get into the temp recovery session?
Yes lollipop was installed and rooted long time ago, after the issue I decided to put it away. I did loads after that though, so I don't think lollipop is still there.
It was first at boot screen, got this fastboot... 123# after I flashed a fastboot image. Flashed loads of recoveries, systems and boot images before and after the fastboot issue.
Hope this helps you understand the state it's in. Thanks for replying.
MJMJ7 said:
Yes lollipop was installed and rooted long time ago, after the issue I decided to put it away. I did loads after that though, so I don't think lollipop is still there.
It was first at boot screen, got this fastboot... 123# after I flashed a fastboot image. Flashed loads of recoveries, systems and boot images before and after the fastboot issue.
Hope this helps you understand the state it's in. Thanks for replying.
Click to expand...
Click to collapse
If the tablet boots into the screen with the 3 fastboot lines you are in DNX mode, which means you've likely messed up your bootloader. To restore the bootloader, follow the steps outlined in https://forum.xda-developers.com/showpost.php?p=73672837&postcount=5
If everything works, you should get to a second Fastboot screen with NORMAL BOOT etc. From there you can either start the temporary TWRP recovery session (see https://forum.xda-developers.com/showpost.php?p=73673438&postcount=7) to flash the Lollipop package you've downloaded earlier (UL-K013-WW-12.10.1.36-user.zip) or flash LineageOS.
If you want to flash LineageOS you need to unlock your bootloader. Download https://www.androidfilehost.com/?fid=312978532265362065, take the ESP.img from the ZIP and download https://github.com/me176c-dev/devic...recovery-3.1.1-20171119-UNOFFICIAL-me176c.img. Then run:
Code:
fastboot flash ESP ESP.img
fastboot flash recovery twrp-recovery-3.1.1-20171119-UNOFFICIAL-me176c.img
Power off your device, then press Volume Down + Power. Intel logo should show up, and ask if you want to go into recovery or fastboot. Go into recovery using Volume Down. Do a Factory reset again (it's under Wipe), then flash https://github.com/me176c-dev/devic...ge-14.1-20171119-UNOFFICIAL-me176c-signed.zip (e.g. put it on your external SD).
I will try these steps and update you. Thank you very much.
O yes! It worked. Tablet is now back in operation on lineageos. Going and get Gapps now. Thanks a lot lambdadroid
I believe my work on this tablet is not complete as I can't install Gapps. Installation failing every time. So I tried to reinstall lineage as this was installed before when I was trying all sorts to fix it.
Then when I followed the procedures you sent me, it booted into lineage after I unlocked the bootloader and installed twrp. So the system still had lineage from my fastboot installation attempts. What I can install now is the original version (ul k013 ww-12.10.1.36-user) and that works but I don't want this.
Any help on getting lineage to complete the installation? as it gets to the end with a little to go hut just never finishes (left this overnight)
Thanks.
lambdadroid said:
If the tablet boots into the screen with the 3 fastboot lines you are in DNX mode, which means you've likely messed up your bootloader. To restore the bootloader, follow the steps outlined in https://forum.xda-developers.com/showpost.php?p=73672837&postcount=5
If everything works, you should get to a second Fastboot screen with NORMAL BOOT etc. From there you can either start the temporary TWRP recovery session (see https://forum.xda-developers.com/showpost.php?p=73673438&postcount=7) to flash the Lollipop package you've downloaded earlier (UL-K013-WW-12.10.1.36-user.zip) or flash LineageOS.
If you want to flash LineageOS you need to unlock your bootloader. Download https://www.androidfilehost.com/?fid=312978532265362065, take the ESP.img from the ZIP and download https://github.com/me176c-dev/devic...recovery-3.1.1-20171119-UNOFFICIAL-me176c.img. Then run:
Code:
fastboot flash ESP ESP.img
fastboot flash recovery twrp-recovery-3.1.1-20171119-UNOFFICIAL-me176c.img
Power off your device, then press Volume Down + Power. Intel logo should show up, and ask if you want to go into recovery or fastboot. Go into recovery using Volume Down. Do a Factory reset again (it's under Wipe), then flash https://github.com/me176c-dev/devic...ge-14.1-20171119-UNOFFICIAL-me176c-signed.zip (e.g. put it on your external SD).
Click to expand...
Click to collapse
I believe my work on this tablet is not complete as I can't install Gapps. Installation failing every time. So I tried to reinstall lineage as this was installed before when I was trying all sorts to fix it.
Then when I followed the procedures you sent me, it booted into lineage after I unlocked the bootloader and installed twrp. So the system still had lineage from my fastboot installation attempts. What I can install now is the original version (ul k013 ww-12.10.1.36-user) and that works but I don't want this.
Any help on getting lineage to complete the installation? as it gets to the end with a little to go hut just never finishes (left this overnight)
Thanks.
MJMJ7 said:
I believe my work on this tablet is not complete as I can't install Gapps. Installation failing every time. So I tried to reinstall lineage as this was installed before when I was trying all sorts to fix it.
Then when I followed the procedures you sent me, it booted into lineage after I unlocked the bootloader and installed twrp. So the system still had lineage from my fastboot installation attempts. What I can install now is the original version (ul k013 ww-12.10.1.36-user) and that works but I don't want this.
Any help on getting lineage to complete the installation? as it gets to the end with a little to go hut just never finishes (left this overnight)
Thanks.
Click to expand...
Click to collapse
No need to reply twice.
Please clarify: What exactly is failing? The LineageOS ZIP or the OpenGApps ZIP? Do you get an error during installation or does it never finish the boot after installation?
Things you can try: Check TWRP log for errors (usually marked red if you click the bottom right button in TWRP). Try a factory reset in TWRP.
lambdadroid said:
No need to reply twice.
Please clarify: What exactly is failing? The LineageOS ZIP or the OpenGApps ZIP? Do you get an error during installation or does it never finish the boot after installation?
Things you can try: Check TWRP log for errors (usually marked red if you click the bottom right button in TWRP). Try a factory reset in TWRP.
Click to expand...
Click to collapse
Just thought you wouldn't be notified if I don't quote.
The gapps file is giving an error and failing, the lineageOS just stalls and never complete the installation.
I will try again now.....
patching system image unconditionally....
This is going on and on, about 10% left to complete but it never does. LineageOS installation.
Updater process ended with ERROR: 1
Error installing zip file '/external_sd/0-System zips/
Asus Memo pad 7 K013/gapps 7.1.zip'
And that's what I'm getting from the gapps installation.
Installation failed.
Got the Gapps to install, had to choose x86 version. Still no improvement from lineage.
MJMJ7 said:
patching system image unconditionally....
This is going on and on, about 10% left to complete but it never does. LineageOS installation.
Updater process ended with ERROR: 1
Error installing zip file '/external_sd/0-System zips/
Asus Memo pad 7 K013/gapps 7.1.zip'
And that's what I'm getting from the gapps installation.
Installation failed.
Click to expand...
Click to collapse
Maybe the file wasn't downloaded/copied properly. Enable ZIP file signature verification in the TWRP settings and flash the LineageOS package again. Does it print "Zip signature verified successfully"?
lambdadroid said:
Maybe the file wasn't downloaded/copied properly. Enable ZIP file signature verification in the TWRP settings and flash the LineageOS package again. Does it print "Zip signature verified successfully"?
Click to expand...
Click to collapse
Did it again with another copy and enabled the verification and all came out successfully. Thanks for your help.:good:

[Stock Rom] Huawei *Prague* PRA-xxxC432B182

[Stock Rom] Huawei (Prague) PRA-xxxC432B182
For restoring/ rescue your device.​P8 Lite 2017 - PRA-LX1, LX2, LX3, LA-1
P9 Lite 2017
Nova Lite
Honor 8 Youth
Created and tested on this device:
Huawei P8 lite 2017 [PRAGUE]
Model number: PRA-LX1
Build number: PRA-LX1C432B182
free device
The PRA is extrem sensitiv.
Any unconsidered, unofficial intervention, don't forgive it.
Hundreds of users have already "bricked" their device.
The response to the dealers is enormous.
To restore your devices,
I'll provide a complete rom.
It is 100% functional and rooted with SuperSu.
It is to be applied to the device via TWRP restoring.
But it is also suitable for this purpose without an OTA update,
to get the current firmware.
Be sure to read the following instructions carefully.
You're doing it at your own risk!
Rom installation:
In the download folder:
2017-12-30-PRAstockB182root (zip)
there are 26 backup files compressed as Zip files.
After downloading, unpack all files individually into this directory. Then delete all zip's. Now copy the whole directory to your TWRP backup folder. Where your other backups are.
Now flash the stock recovery and perform a factoryreset.
Now flash TWRP and make a wipe of the data and system partitions in TWRP.
Then restore my backup and reboot.
The firmware and the kernel are already rooted.
If necessary, you can install Busybox.
If the device does not boot, the bootloader must be unlocked again with the Huawei unlockcode.
It is a little bit more work for you to unpack everything individually, but this way a faultless installation is possible.
I have tested the up- and download, unpacking and restoring several times. It works perfectly. The rom is bug free.
Now create a new TWRP backup
and remove all older backups from the TWRP backup folder, otherwise they could cause problems later.
Save it to another folder or to
USB-/Stick, or HD.​
I would now like to make a few comments on the end of the year:
I've had the P8 lite 2017 for a year.
The first rooting was developed by me.
The SuperSu and the first rooted kernel,
enabled the developers
@Tecalote and KangVip.
TWRP was provided by the LineageOS team. Again and again I have added fresh rootings and roms.
Nevertheless, increased Bricks are not missing.
It took an enormous amount of time to find
help the users. Unfortunately, this didn't work out for everyone.
My recommendation:
Now set up your device completely. Then create a complete backup with the ingenious Huawei Backup App. Now you take the recovery back.
"fastboot flash recovery recovery. img"
Removes TWRP from your brain for the time being.
Your device is now perfect and the firmware is original. You also have root and the OTA update authorization. When OREO comes, you just wait until I announce the new rooting."
I wish you all the best for 2018.
WARNING !
If all this has worked on my device, it does not mean that it goes with everyone else. Follow exactly the instructions to prevent damage. The execution is your risk.
Never make a factory reset in TWRP. Brick !!! Wipes only in stock recovery.
NOTE: Despite careful preparation I can not guarantee that through the implementation of this Guidance does not create damage to the device or operating system, and therefore assume no liability for ensuing damage and malfunction of hardware and software! If you are still unsure, follow these steps: Only perform the procedure if any mentioned conditions (model number, Android version, etc.) apply to you or your device. Read the instructions carefully and completely, check unfamiliar terminology by google or xda. Downloaded files check for viruses. A backup of important settings and data make. The instructions do not perform, if you do not know what you're doing.
Thank you very much: @Tecalote, KangVip,Chainfire, Stephen (Stericson), Jmz Software, LinageOs team, JRummy, as well as.
Huawei Technologies Co., Ltd.
Update 2017-12-31:
I removed the part "dual recovery".
The support on xda is finished.
Only here:
https://www.android-hilfe.de/forum/huawei-p8-lite-2017.2980/​
I couldn't restore my phone. I followed all of your instructions and after restoring, when I reboot, the phone goes only in TWRP (no volume keys pressed). Any ideas on what I can do?
In any case thank you for the thread, it's good to have a well described procedure for these things
Restore your last backup and repeat the procedure.
Try this one first:
Root again with the SU (B182) from the download.
Tip for life: try not to trust random nerds on forums, offering "ROMs" and what they call "tutorials". Stick to the outlet which sold you the phone, and deal with them and/or the manufacturer, and you can't go far wrong.
afit5 said:
I couldn't restore my phone. I followed all of your instructions and after restoring, when I reboot, the phone goes only in TWRP (no volume keys pressed). Any ideas on what I can do?
In any case thank you for the thread, it's good to have a well described procedure for these things
Click to expand...
Click to collapse
I had the same situation. It's a bit tricky and you must really know, what you are doing
I rebooted to bootloader an repeated the oem unlock -> this caused a factory reset!!
I am on dual recovery and so I rebooted to twrp, repeated the restore with the b182 stock rom and could reboot to the system
mbwf said:
Tip for life: try not to trust random nerds on forums, offering "ROMs" and what they call "tutorials". Stick to the outlet which sold you the phone, and deal with them and/or the manufacturer, and you can't go far wrong.
Click to expand...
Click to collapse
100% useless post. This does not help anyone.
ChinHon tries to help others and i would trust him more than you...
KuGeSch said:
I had the same situation. It's a bit tricky and you must really know, what you are doing
I rebooted to bootloader an repeated the oem unlock -> this caused a factory reset!!
I am on dual recovery and so I rebooted to twrp, repeated the restore with the b182 stock rom and could reboot to the system
Click to expand...
Click to collapse
UPDATE: I solved in another way, which is: booted to fastboot mode, restored the stock recoveries (recovery1 to recovery1, erecovery to recovery2), then the phone booted normally as it should have had. At that point I could reflash twrp to recovery1, but that is optional.
I think the phone tried to boot but having the wrong recovery in recovery2 slot caused problems (just a random hypothesis). Hope this helps
afit5 said:
UPDATE: I solved in another way, which is: booted to fastboot mode, restored the stock recoveries (recovery1 to recovery1, erecovery to recovery2), then the phone booted normally as it should have had. At that point I could reflash twrp to recovery1, but that is optional.
I think the phone tried to boot but having the wrong recovery in recovery2 slot caused problems (just a random hypothesis). Hope this helps
Click to expand...
Click to collapse
What you call erecocery is this the stock erecovery or is it prague311.img from ChinHon? If it is the stock erecovery, where can I find it for download?
Thanks a lot!
KuGeSch said:
What you call erecocery is this the stock erecovery or is it prague311.img from ChinHon? If it is the stock erecovery, where can I find it for download?
Thanks a lot!
Click to expand...
Click to collapse
-prague311.img is TWRP
-recovery.img is the stock recovery on recovery partition 1
-recovery2.img is the stock eRecovery on recovery partition 2
https://www.mediafire.com/file/r33el93w5wyqwde/recovery2.img
ChinHon said:
-prague311.img is TWRP
-recovery.img is the stock recovery on recovery partition 1
-recovery2.img is the stock eRecovery on recovery partition 2
https://www.mediafire.com/file/r33el93w5wyqwde/recovery2.img
Click to expand...
Click to collapse
Thanks a lot! You are doing a great job!
Hello!
I want to follow this guide, it should be fine for my Dual SIM Variant, right?
I have a problem with one file, that is 'version.emmc.win.md5.zip' that can't be downloaded from MEGA. Can someone please provide a working link for that file?
Also a doubt: when all the files will be ready my idea is to restore your TWRP backup, flash stock recovery then lock bootloader, to make it as near to stock as possible: will this work? I have another TWRP backup that is running on my phone, but if I lock the bootloader it won't start, if I unlock the bootloader there no problems at all.
Thanks for your interesting topic!
SnoopyDog said:
100% useless post. This does not help anyone.
ChinHon tries to help others and i would trust him more than you...
Click to expand...
Click to collapse
Very good. Keep smiling.
baffo92 said:
Hello!
I want to follow this guide, it should be fine for my Dual SIM Variant, right?
I have a problem with one file, that is 'version.emmc.win.md5.zip' that can't be downloaded from MEGA. Can someone please provide a working link for that file?
Also a doubt: when all the files will be ready my idea is to restore your TWRP backup, flash stock recovery then lock bootloader, to make it as near to stock as possible: will this work? I have another TWRP backup that is running on my phone, but if I lock the bootloader it won't start, if I unlock the bootloader there no problems at all.
Thanks for your interesting topic!
Click to expand...
Click to collapse
Here's the link.
https://mega.nz/#!4sd3DI6Z!BOfI0teLD_m3aLUROhiMVZuePySmp329RXZpjsH3AM0
Please tell me why you want to take the rom. What's happening?
ChinHon said:
Here's the link.
https://mega.nz/#!4sd3DI6Z!BOfI0teLD_m3aLUROhiMVZuePySmp329RXZpjsH3AM0
Please tell me why you want to take the rom. What's happening?
Click to expand...
Click to collapse
The link works perfectly. Thanks!
I can now give this stock ROM a try!
EDIT 1: I'm trying to install the ROM but I have a problem with TWRP: I launch the command 'fastboot flash recovery prague311.img' then boot to TWRP, but the touchsceen of the phone is unresponsive and I can't do anything to make it work. Have you got any suggestion?
EDIT 2: I made some mistakes here and there, but the TWRP booted and now I have the phone on your ROM Version! I'm trying to clean everything and do a clean install if I can...
EDIT 3: I've done a full phone clean by using the 'Factory Reset' option in 'Settings'... now the phone boots, but:
1. NFC/GPS are not working, they are blinking
2. FM Radio is not working (it says com.huawei.... and has an Android icon instead of the original icon)
baffo92 said:
The link works perfectly. Thanks!
I can now give this stock ROM a try!
EDIT 1: I'm trying to install the ROM but I have a problem with TWRP: I launch the command 'fastboot flash recovery prague311.img' then boot to TWRP, but the touchsceen of the phone is unresponsive and I can't do anything to make it work. Have you got any suggestion?
EDIT 2: I made some mistakes here and there, but the TWRP booted and now I have the phone on your ROM Version! I'm trying to clean everything and do a clean install if I can...
Click to expand...
Click to collapse
To get the rom completely clean you do the following:
Go to my root thread section: Threadupdate: 2018-01-02 and work through the instructions. Then you have a perfect clean stock rom.
ChinHon said:
To get the rom completely clean you do the following:
Go to my root thread section: Threadupdate: 2018-01-02 and work through the instructions. Then you have a perfect clean stock rom.
Click to expand...
Click to collapse
Your support is very helpful, thanks!
I have problems on the steps to reproduce, even after reading your guide :')
This is what I do:
1. Wipe Data/Factory Reset + Wipe cache with stock recovery
2. Flash TWRP
3. Open TWRP, clean data, system and also cache + dalvik
4. Reboot the phone to a fully working with B182, in English with Dual SIM fully recognised
5. What I have to do from now on to have a fully stock experience (remove custom Kernel, reflash stock recovery and erecover, re-lock bootloader and fully ready to Oreo)?
Can you please guide me?
Thanks and sorry for my problems, but I work with Nexus devices thare a bit more 'elastic' in flashing
The kernel is stock. You just have to flash the eRecovery and recovery. That's all.
ChinHon said:
The kernel is stock. You just have to flash the eRecovery and recovery. That's all.
Click to expand...
Click to collapse
Ok, thanks!
This is what I did before, but I can't do a factory reset due to the problems described (Radio FM not working, NFC not working).
I can't also relock the bootloader, because the phone will boot to erecovery (recovery2) and won't let me reach the boot of the ROM. Have you got any suggestion?
If leave it as it is now (unlocked bootloader with stock recovery1 and recovery2) will Oreo arrive without any problems?
Your support is awesome, thanks
If you now take my UPDATE.APP via dload the problems should be gone.
ChinHon said:
If you now take my UPDATE.APP via dload the problems should be gone.
Click to expand...
Click to collapse
Sounds good!
If I flash the stock recovery, then update officially with an UPDATE.APP from SD Card everything should be ok.
Where can I find your UPDATE.APP? I didn't find it in your MEGA Folder
Thanks, again, for your incredible support!

Categories

Resources