Related
After 3 days tried to find out how to recovered or fix bootloop/brick ME170C, here is the way which was succeed for me.
1. Download latest firmware from ASUS website
the best way using complete firmware (containing stock rom) like this version UL-K017-WW-11.2.3.18.2-user, if succeed then later on you can continue with OTA system update
2. Rename the firmware file to K017_sdupdate.zip and put on SD card then Insert the SD card into a tablet. (Use good one SD card, Sandisk perfect I don't know others)
3. Download flashtools and USB driver at the bottom of this thread
4. Enter the DROIDBOOT, for this purpose on the tablet off push and hold button volume + and power then connect USB cable to tablet and PC.
5. Open your firmware archive and copy or drag & drop the boot.img, fastboot.img, splashscreen.img into Flashtools folder ( in computer )
6. go to flashtools folder and then push button shift and right click together and choose “Open command windows here”, to start open CMD on the right folder (in computer)
7. Test your device by typing fastboot devices on that cmd (in computer)
8. Enter the queue codes on CMD; (in computer)
fastboot erase cache
fastboot erase userdata
fastboot erase system
fastboot flash boot boot.img
fastboot flash fastboot fastboot.img
fastboot flash splashscreen splashscreen.img
fastboot reboot-bootloader
8. Disconnect the USB cable and select the SD update or Recovery.
9. Take your coffee and sit, walaaaaaaa I see you are smiling
I am curious , is it work for others ASUS tablet? do with your own risk, but btw with this step I did wake up a hard brick devices.
Tag [ Asus memopad fonepad zenfone ME170 brick, bootloop, stuck on asus logo, boot problem, solved brick, guide how to]
So awesome you figured this out! Glad it worked out for you and I'll be saving this in case I find myself in the same boat. Thank you for this!!
Sent from my Nexus 6
K01A, aka ASUS MeMO Pad ME170CX
Prod date 2014-10 IIRC.
I appreciate you taking time to create this thread, have been unable to flash stock firmware to the ME170CX using just the ME170CX itself. ASUS website just mentions a SOP method and when I insert SD that has had the firmware files which have been extracted (1) time to the SD card, the prompt that is supposed to "pop-up" on the taskbar as mentioned in the PDF's I found online about the SOP method does NOT occur.
(I have 2 ME170CX's about 30-days old running 4.4.2, firmware Version WW_V11.2.3.27 in which one of them all the sudden the camera app crashes 100% of the time, then gives a "No camera is found" error message.
Beyond a hardware issue no-one knows what causes this beyond (1) poster that mentioned he thought problem first occurred after hitting the "Home" button right after hitting the cam icon and the thought is the app gets confused by this and the app/firmware for the camera gets corrupted.
Reset via OS itself. Wiping data and choosing "Recovery" in DROIDBOOT with "FASTBOOT" text at bottom of screen didn't make any difference. Camera is dead, dead, dead.
Figured I'd re-flash with same Version WW_V11.2.3.27, if that doesn't work try Version WW_V11.2.3.28 before RMA'ing it back to ASUS so I appreciate you listing the steps, and also attaching the needed files.)
***************
Question about Step 2, Please clarify:
2. Extract (archive in archive) and throws to the SD card. Rename the file to K017_sdupdate.zip and Insert the flash drive into a tablet. (Use good one SD card)
Click to expand...
Click to collapse
To clarify you are saying to extract the firmware from the "zip" package of zip that matches the firmware specific to the device from ASUS, which itself contains a zip file named IFWI.ZIP (1 ), one time, then rename the file named IFWI.ZIP (which contains 4 Bin files) to K017_sdupdate.zip.
Upon extraction process completing and renaming the zip you then copy the contents over to a known good MiroSD of at least 2GB which is formatted FAT32 to the ROOT of the drive.
IE: You do not extract the zip within the archive, you're just renaming IFWI.ZIP to K017_sdupdate.zip?
OR are you saying to extract the BINS also?
If so do these go in the ROOT of the SD card?
Another question, is there a reason for renaming IFWI.zip to K017_sdupdate.zip?
.
WeAreNotAlone said:
K01A, aka ASUS MeMO Pad ME170CX
Prod date 2014-10 IIRC.
I appreciate you taking time to create this thread, have been unable to flash stock firmware to the ME170CX using just the ME170CX itself. ASUS website just mentions a SOP method and when I insert SD that has had the firmware files which have been extracted (1) time to the SD card, the prompt that is supposed to "pop-up" on the taskbar as mentioned in the PDF's I found online about the SOP method does NOT occur.
(I have 2 ME170CX's about 30-days old running 4.4.2, firmware Version WW_V11.2.3.27 in which one of them all the sudden the camera app crashes 100% of the time, then gives a "No camera is found" error message.
Beyond a hardware issue no-one knows what causes this beyond (1) poster that mentioned he thought problem first occurred after hitting the "Home" button right after hitting the cam icon and the thought is the app gets confused by this and the app/firmware for the camera gets corrupted.
Reset via OS itself. Wiping data and choosing "Recovery" in DROIDBOOT with "FASTBOOT" text at bottom of screen didn't make any difference. Camera is dead, dead, dead.
Figured I'd re-flash with same Version WW_V11.2.3.27, if that doesn't work try Version WW_V11.2.3.28 before RMA'ing it back to ASUS so I appreciate you listing the steps, and also attaching the needed files.)
***************
Question about Step 2, Please clarify:
To clarify you are saying to extract the firmware from the "zip" package of zip that matches the firmware specific to the device from ASUS, which itself contains a zip file named IFWI.ZIP (1 ), one time, then rename the file named IFWI.ZIP (which contains 4 Bin files) to K017_sdupdate.zip.
Upon extraction process completing and renaming the zip you then copy the contents over to a known good MiroSD of at least 2GB which is formatted FAT32 to the ROOT of the drive.
IE: You do not extract the zip within the archive, you're just renaming IFWI.ZIP to K017_sdupdate.zip?
OR are you saying to extract the BINS also?
If so do these go in the ROOT of the SD card?
Another question, is there a reason for renaming IFWI.zip to K017_sdupdate.zip?
.
Click to expand...
Click to collapse
some firmware when you download it from asus site ZIP compresed twice, you can rename it directly from WW_V11.2.3.28.zip to K017_sdupdate.zip, if your device is K01A try to renaming firmware to K01A_sdupdate.zip and then put in SD card (do not created any folder in SD card ). the key to success is the SD card compatibility with ASUS DROIDBOOT, I was using Sandisk SD card. I did format fat32 the SD card and insert in another android devices first and then put the renamed firmware file there.
inside firmware file there is boot.img, fastboot.img and splashscreen.img you need to extract it in flashtool/fasboot folder and then flashing it your tablet. this trick to make firmware recognize correct devices to be update.
try again.
sevensvr said:
some firmware when you download it from asus site ZIP compresed twice, you can rename it directly from WW_V11.2.3.28.zip to K017_sdupdate.zip, if your device is K01A try to renaming firmware to K01A_sdupdate.zip and then put in SD card (do not created any folder in SD card ). the key to success is the SD card compatibility with ASUS DROIDBOOT, I was using Sandisk SD card. I did format fat32 the SD card and insert in another android devices first and then put the renamed firmware file there.
inside firmware file there is boot.img, fastboot.img and splashscreen.img you need to extract it in flashtool/fasboot folder and then flashing it your tablet. this trick to make firmware recognize correct devices to be update.
try again.
Click to expand...
Click to collapse
RE: boot.img, fastboot.img and splashscreen.img you need to extract it in flashtool/fasboot folder ???????
Having some progress, renaming ifwi.zip which contains (4) bin files when Recovery was selected caused the robot with the Updating System Settings to appear, but a couple of seconds later it said ERROR with the robot laying on it's back, then it exits. Device reboots as normal.
To clarify:
WW_V11.2.3.28.zip download from ASUS was extracted with a Windows computer,
WW_V11.2.3.28.zip extracting /creating following folders, files, then the contents were copied to the ROOT of a MicroSD card formated Fat32
1: boot.img, fastboot.img and splashscreen.img (TO ROOT)
2: ifwi.zip to ROOT. (contains (4) bin files, is this supposed to be extracted to I assume folder by same name off root? OR does this ZIP file just get renamed?)
3: System folder
4: Recovery folder
5: META-INF folder
I do not see a flashtool/fasboot folder. (Fastboot, right?)
Q: Is boot.img, fastboot.img and splashscreen.img supposed to be in a folder named "Flashtool" OR are they supposed to be in folder named "Fastboot" with a pathway of Root (Drive) D:/Flashtool/fastboot ?
.
(NOTE ALL OF THIS IS BEING DONE ON THE DEVICE ITSELF, with contents on SD card.)
Still getting the ERROR! message wit the Adroid robot that is laying on his back.
The zip file that extracts from the main zip WW_V11.2.3.28.zip is named:
ifwi.zip...
I have left a copy of it in the ROOT, plus copied it and renamed it to
K01A_sdupdate.zip
K017_sdupdate.zip
LEAVING COPIES OF ALL IN THE ROOT OF THE SDCARD.
Q: If more than (1) zip is present does this confuse fastboot? OR does fastboot automatically look for zip zip which matches model ID of device? (K01A)
I have left copies of boot.img, fastboot.img and splashscreen.img in the ROOT of the drive.
AND
Created: (ROOT) flashtools/fastboot with *img files in it.
Created: (ROOT) fastboot with *img files in it.
Copied the *img files to under "Flashtools" folder in flashtools/fastboot.
Figuring all the bases would be covered. (EG: *img Files in ROOT, files in Flashtools, Flashtools/fastboot, and a folder named fastboot as well.
Q: I've noticed on the SD card files appearing that previously were not there, when the flash aborts is there some kind of file or files you need to delete, or is it ok to leave the newly generated files there?
---------- Post added at 03:43 AM ---------- Previous post was at 03:37 AM ----------
Deleted:
ifwi.zip.
K017_sdupdate.zip
Tried:
K01A_sdupdate.zip
Still getting robot on it's back with ERROR!
who said you need to renaming ifwi.zip, What you need is read all instruction carefully,
do not put more than 1 zip file in SD card only firmware file which is already renamed to K017_sdupdate.zip, and use good brand SD card.
I successfully complete all step after "Installing system update" nothing change again stuck on asus logo.
commando987 said:
I successfully complete all step after "Installing system update" nothing change again stuck on asus logo.
Click to expand...
Click to collapse
when installing update, the robot end with error or not?, the installing bar moved till finish ? the installing process will take 3 to 5 minutes.
if you did all above and still got stuck on asus logo, try to change the firmware with this version UL-K017-WW-11.2.3.18.2-user, if succeed then you can continue with OTA system update
My Asus MemoPad ME170C has risen again!
sevensvr said:
After 3 days tried to find out how to recovered or fix bootloop/brick ME170C, here is the way which was succeed for me.
1. Download latest firmware from ASUS website
2. Rename the firmware file to K017_sdupdate.zip and put on SD card then Insert the SD card into a tablet. (Use good one SD card, Sandisk perfect I don't know others)
3. Download flashtools and USB driver at the bottom of this thread
4. Enter the DROIDBOOT, for this purpose on the tablet off push and hold button volume + and power then connect USB cable to tablet and PC.
5. Open your firmware archive and copy or drag & drop the boot.img, fastboot.img, splashscreen.img into Flashtools folder ( in computer )
6. go to flashtools folder and then push button shift and right click together and choose “Open command windows here”, to start open CMD on the right folder (in computer)
7. Test your device by typing fastboot devices on that cmd (in computer)
8. Enter the queue codes on CMD; (in computer)
fastboot erase cache
fastboot erase userdata
fastboot erase system
fastboot flash boot boot.img
fastboot flash fastboot fastboot.img
fastboot flash splashscreen splashscreen.img
fastboot reboot-bootloader
8. Disconnect the USB cable and select the SD update or Recovery.
9. Take your coffee and sit, walaaaaaaa I see you are smiling
I am curious , is it work for others ASUS tablet? do with your own risk, but btw with this step I did wake up a hard brick devices.
Tag [ Asus memopad fonepad zenfone ME170 brick, bootloop, stuck on asus logo, boot problem, solved brick, guide how to]
Click to expand...
Click to collapse
I bought my memopad 170c just a couple of days ago and because of excitement i flash the wrong firmware and it went dead i tried the recovery method but nothing happens i'm beginning to get nervous as this tablet is a gift for my daughter but thankfully i found this site especially to your instruction did every step with my finger crossed and like what you said sit back and walaaaaa! my tablet err my daughter's tablet has risen again. thank you for sharing your knowledge.
sevensvr said:
when installing update, the robot end with error or not?, the installing bar moved till finish ? the installing process will take 3 to 5 minutes.
if you did all above and still got stuck on asus logo, try to change the firmware with this version UL-K017-WW-11.2.3.18.2-user, if succeed then you can continue with OTA system update
Click to expand...
Click to collapse
Installing bar not complete at the end but not give error and restart. After restart stuck on asus logo. Now i download version UL-K017-WW-11.2.3.18.2 and check it.
mapagmatyag said:
I bought my memopad 170c just a couple of days ago and because of excitement i flash the wrong firmware and it went dead i tried the recovery method but nothing happens i'm beginning to get nervous as this tablet is a gift for my daughter but thankfully i found this site especially to your instruction did every step with my finger crossed and like what you said sit back and walaaaaa! my tablet err my daughter's tablet has risen again. thank you for sharing your knowledge.
Click to expand...
Click to collapse
you welcome friend
commando987 said:
Installing bar not complete at the end but not give error and restart it. After restart stuck on asus logo. Now i download version UL-K017-WW-11.2.3.18.2 and check it.
Click to expand...
Click to collapse
it seems the tablet didn't read your SD card, to assure SD card problem when the robot appear while system update press buttom vol + and - rapidly to show installing status.
if the tablet didn't read ur SD card try to use another SD card
BIG Thanks
I've been stuck with the bricked 2 day old tablet for at least 3 months. Today I did the procedure you described and it worked. I had to install version V11.2.3.18.2 and then, once unbricked, apply latest version update.
Again, thanks a lot!.. Best regards.
mnabarro said:
I've been stuck with the bricked 2 day old tablet for at least 3 months. Today I did the procedure you described and it worked. I had to install version V11.2.3.18.2 and then, once unbricked, apply latest version update.
Again, thanks a lot!.. Best regards.
Click to expand...
Click to collapse
happy to heard it
Hi, am trying to fix my ME170CX because an original root attempt that failed and am getting a demo error message that won't go away.
I tried following all your instructions to fix this but it gets stuck "waiting for device" once I begin entering the commands.
I have tried multiple sd cards (including a sandisk) and both the V11.2.3.27 & V11.2.3.28 firmware versions to no avail.
I also tried naming the zip file K017 & K01A.
I am also wondering why we need to download the USB driver file? I don't see anywhere in your instructions on what to do with this.
Any help would be greatly appreciated.
Mike
mashton70 said:
Hi, am trying to fix my ME170CX because an original root attempt that failed and am getting a demo error message that won't go away.
I tried following all your instructions to fix this but it gets stuck "waiting for device" once I begin entering the commands.
I have tried multiple sd cards (including a sandisk) and both the V11.2.3.27 & V11.2.3.28 firmware versions to no avail.
I also tried naming the zip file K017 & K01A.
I am also wondering why we need to download the USB driver file? I don't see anywhere in your instructions on what to do with this.
Any help would be greatly appreciated.
Mike
Click to expand...
Click to collapse
Youll want to get your answer from him but i think i may be able to help. You need to install usb drivers so you can access abd and give commands to your tablet. Which i think is why it just says waiting for device... I could be wrong though....
Sent from my Nexus 6
anthonyg45157 said:
Youll want to get your answer from him but i think i may be able to help. You need to install usb drivers so you can access abd and give commands to your tablet. Which i think is why it just says waiting for device... I could be wrong though....
Sent from my Nexus 6
Click to expand...
Click to collapse
OK, I finally got the usb drivers working on my computer and made it through all commands which is much further than I was getting before.
I got to step 8 "Disconnect the USB cable and select the SD update or Recovery" and selected "Recovery" in DROIDBOOT (I don't have an "SD update" option there) and after like 1 second of "installing system updates" I get the android falling over guy error and then it hangs on the asus splash screen for ever.
download ME70CX for ME170CX
anthonyg45157 said:
Youll want to get your answer from him but i think i may be able to help. You need to install usb drivers so you can access abd and give commands to your tablet. Which i think is why it just says waiting for device... I could be wrong though....
Sent from my Nexus 6
Click to expand...
Click to collapse
have you been able to restore it ?
Can NOT use download of ME170C
Use download of ME70CX. Just did it, and tablet back to "almost" normal.
I have wifi button issue now. Button is stuck.
bye
ydobon.999 said:
have you been able to restore it ?
Can NOT use download of ME170C
Use download of ME70CX. Just did it, and tablet back to "almost" normal.
I have wifi button issue now. Button is stuck.
bye
Click to expand...
Click to collapse
That did it!
I used the firmware ME70CX and renamed the file "K01A_sdupdate.zip" and followed all of the other steps as per the original instructions and got my ME170CX working again but for one problem. . . I was still getting the "demo has stopped" error! So I proceeded to attempt root again, this time with RootZenFone-1.4.6r and and now it's working perfectly and rooted as well!
Many thanks to all!!
Hi,
I made a mistake installing Cyanogenmod on my phone, forgot to make a backup in TWRP.
This Cyanogenmod version requires me to delete my former EMUI fingerprints for the fingerprint function to work. I forgot to do that also...
So now I'm trying to reinstall my custom ROM. I found the UK PLK-L01 firmware on Huawei support page, downloaded that and put it on my (not external sd)sdcard/dload/UPDATE.APP.
Then I try the Volume UP+Volume Down+Power for it to install the rom, but only thing that happens is that the phone boots into TWRP, and in there, there is no option to install a .APP file.
Please help
frederikahrenst said:
Hi,
I made a mistake installing Cyanogenmod on my phone, forgot to make a backup in TWRP.
This Cyanogenmod version requires me to delete my former EMUI fingerprints for the fingerprint function to work. I forgot to do that also...
So now I'm trying to reinstall my custom ROM. I found the UK PLK-L01 firmware on Huawei support page, downloaded that and put it on my (not external sd)sdcard/dload/UPDATE.APP.
Then I try the Volume UP+Volume Down+Power for it to install the rom, but only thing that happens is that the phone boots into TWRP, and in there, there is no option to install a .APP file.
Please help
Click to expand...
Click to collapse
couldnt you just locate files and delete in root explorer or similar app?
You can open the update.app in Huawei update extractor and use adb to manually flash the system, custom, cache, boot and recovery partitions back to stock then once you boot into the stock emui os you can reflash twrp. I'm busy atm but I'll write you a proper guide soon. Or you could Google it but be careful becuase there are a lot of guide that don't work anymore
Edit: This won't require you to wipe your user data so you can keep your setting contacts apps etc.
---------- Post added at 09:07 PM ---------- Previous post was at 08:28 PM ----------
Here is my guide it's a bit long but should be easy. I recommend reading it all first before following it just so you know what each step is doing.
Ok step one. Go to This link and download the emui version for you phone.
step two. You need to download Huawei update extractor from This link and install it on your pc.
Step three. unzip the update you extracted to a new folder on your desktop (It can be called anything bu I recommend calling it "EMUI") and put the update.app file in this folder.
Step four. open Huawei update extractor and select profile "Unknown (worstenbrood)" if it is not selected already.
Step five. Under the section where it says update file click on the ".." button navigate to the folder you made on your desktop and double click the update.app file.
Step six. Right click on the file named "BOOT.img" and click extract selected then once the green loading bar has gotten to 100% click close on the extracting window since it does not automatically do it its self.
Step seven. Repeat step six for the files named "CACHE.img", "CUST.img", "RECOVERY.img", "SYSTEM.img" and "USERDATA.img" (Only extract USERDATA.img if you want to wipe all of you apps, setting, contacts and messages)
Step eight. Open the folder you create on your desktop and copy all of the files you extracted (Only the .img files since Huawei update extractor also create some other files which you don't need) and paste them into the folder which you have adb installed into (It should be "C:\Program Files (x86)\Android\android-sdk\platform-tools" if you used the sdk version but if you have a diffrent version of adb paste them into the folder which you have that installed to)
Step nine. Boot your phone into bootloader mode on you phone. There are a few ways to do this but use whatever way you used when you flashed twrp.
step ten. In widowns explorer (Your pc's file manager) Shift click in the folder you have adb installed into and click "Open cmd window here"
Step eleven. type the following commands into cmd "fastboot flash boot BOOT.img", "fastboot flash cust CUST.img", "fastboot flash recovery RECOVERY.img", "fastboot flash system SYSTEM.img" and if you decided to reset all of you data (Like apps, contacts, messages, setting, etc) "fastboot flash userdata USERDATA.img" Some of these may take a long time (Especially SYSTEM.img but it shouldn't take more than 10 minute if it doesn't finish within 20 minute press ctrl + c in the cmd windows and start again).
Step twelve. Type "fastboot reboot" into cmd and you will boot into stock emui. Now you can reflash TWRP if you want and re install root.
Feel free to message me if you need help.
Warning!!! I’m not responsible for anything (death, destruction, or nuclear war) which happens to you & your stuffs after following this guide.
Downloads :-
RR-Magisk-Root-vivo-Y51L.zip
TipsyOS Prerooted ROM
How to Install ?
1. Make sure you have RR rom installed(Get it Here) before flashing RR-Magisk-17.2-vivo-Y51L.zip
2. Reboot to TWRP recovery
3. Install RR-Magisk-17.2-vivo-Y51L.zip or TipsyOs-prerooted.zip, whatever your choice is.
4. Reboot to System.
5. If root worked, Come back and the hit the thanks button below!
:Video Tutorial on the same:
https://www.youtube.com/watch?v=omUggCUJGGk
-:NOTES FOR VIVO Y51L DEVS:-1. Played with Magisk once for around 3 hours
2. You wanna know ? Seriously ? Okay
3. Disable Selinux which isn't needed by root ! (Just for fun)
4. Downlad Magisk-latest.zip
5. Extract magiskinit from arm folder
6. Push magiskinit to /data/local/tmp
7. Run :
adb shell
cd data/local/tmp
chmod 755 magiskinit
./magiskinit -x magisk magisk
exit
adb pull /data/local/magiskinit8. Now you will get an file with name magisk in the current dir
9. Place it in the /system/xbin/ folder of your rom
10. Place Magisk Manager apk in /sytem/app/Magisk
11. Now, boot.img part :
Following things to be done in boot.img :
Created /sbin/permissive.sh
Patched default.prop, fstab.qcom, init.environ.rc, init.rc, init.recovery.service.rc, init.root.rc, init.superuser.rc (create one if..), sepolicy, service_contexts
If you wanna know the stuff i added in these files, just search 'Naveen' in all those files (Yeah, i reckon that, i'm Superlazy to find & write those here even though i can write 55wpm)12. What about how to patch sepolicy ? Uh, I used supolicy by @Chainfire (Thanks man....)
13. How to find selinux denies ? Install audit2allow in your linux system & :
adb shell dmesg | audit2allow -p (your sepolicy here, use 'adb pull /sys/fs/selinux/policy') > selinux.error
Now push supolicy to phone (Download SuperSU.zip)
adb push ./ /data/local/tmp/tony/
adb shell
cd /data/local/tmp/tony/
chmod 755 *
./supolicy --live "error here"
./supolicy --save /data/local/tmp/tony/new_sepolicy
exit
adb pull /data/local/tmp/tony/new_sepolicy
Rename new_sepolicy to sepolicy & replace your original one in boot.img
Repack your boot.img13. This won't work with stock rom since we get operation not permitted errors while trying to exec su, i think it's Linux Capabilities (Read more about that here : http://man7.org/linux/man-pages/man7/capabilities.7.html) Don't ask me why it works in cm roms if kernel is the problem
14. Whatever you wanna ask me, reply here please (I'm don't check private messages anymore)
Official Telegram Group for Vivo Y51L/Y21L : https://t.me/vivodevelopment
Fix for bugs
Please fix the bugs asap....i am facing audio and video playback problems
#ask
are you facing mic and call problem?
use y51l kernal
bro.
can you use y51l kernal to patch file?
so that y51l may get rooted with no bugs
Bugs are there
*Front camera not working
*Flash light not working
*Magisk not installing
y51 kernal source restore
can you make tutorial to restore y51 kernal source .also there a wifi bug wont turn on
device stuck at app starting up....pls hlp
installed the miui root boot.img and twrp.img but after rebooting the device was stuck
Can't root
How to download
Magisk cannot run in third-party ROM
It's a pity that my favorite ROM cannot be ROOT. It's not that the installation fails, but it always stops working.
I have a more useful method for rooting vivo y51L
Requirements:-
OTG
Data cable
A second phone
Bootloader unlock
Bugjaeger application
Root checker application
Your custom ROM or stock ROM zip file
Firstly we have to unzip our stock or custom ROM zip file, after unzipping file we have to move out boot.img file and save it in our internal storage . After that we have to flash the boot.img file in magisk and after flashing we will get a magisk patch in our download folder . We have to send that patch to our second phone and save it in it's internal storage .after that we have to boot our phone in fastboot mode and for that we have to power off our device and press volume down and power button .After booting the device in fastboot mode you have to connect otg in your second device and data cable in fastboot device . After that connect data cable and otg , after connecting the Bugjaeger application will open automatically . after that find an icon which looks like lightning in app and click that , after that you will find a blue dot at the bottom of the screen . Click that button and you will get inside command section after that type the first command :- Fastboot devices and click the play button at the right side. After that you will see a serial number which means you are connected. After that write the second command :- Fastboot flash boot , after writing it we will find a paper clip type button at the top right corner , just click that and attach the magisk patch which we sent to our second device and tap the play button at the right side . After the command has succeeded we have have to reboot our fastboot phone after removing data cable and otg . After rebooting just open root checker application and keep internet on , Click on verify root. Your phone is rooted now.
Now do whatever you want to do
Fun fact :- this method works on every phone
Those who want to say me thanks for this method please reply me
What You Need?
1. Your Mobile [Rooted]
2. Computer
3. USB Cable
How?
if you need PARAM.bin file that means you know how things work, so i'm not gonna explain every little step.
1. Make folder on your desktop and Open 2 command line programme windows in that directory.
2. choose one window and run this commands
adb shell
su
dd if=/dev/block/platform/13540000.dwmmc0/by-name/PARAM of=/sdcard/PARAM.bin bs=4096
Block Path in above dd command can be different in your device. if you failed to open renamed zip file, you need to Find Correct Block and replace that in dd command
3. goto second command line window and run
adb pull /sdcard/PARAM.bin
4. To Extract Files from bin Just rename .bin file to zip (param.bin.zip)
Done.
Thanks,but how do i extract this file?
already tried with "tar xf " but gives me nothing
AndroidSamsungFreak said:
Thanks,but how do i extract this file?
already tried with "tar xf " but gives me nothing
Click to expand...
Click to collapse
same problem with me
AndroidSamsungFreak said:
Thanks,but how do i extract this file?
already tried with "tar xf " but gives me nothing
Click to expand...
Click to collapse
Just rename it to zip (param.bin.zip)
wings110 said:
same problem with me
Click to expand...
Click to collapse
Just rename it to zip (param.bin.zip)
AUPMA said:
Just rename it to zip (param.bin.zip)
Click to expand...
Click to collapse
my device is g9300 cpu is 820 rename zip can not be opened
wings110 said:
my device is g9300 cpu is 820 rename zip can not be opened
Click to expand...
Click to collapse
Seems Like your block is different. So you need to Find Correct block and replace that on dd command
Samsung A50 booting on logo
AUPMA said:
What You Need?
1. Your Mobile [Rooted]
2. Computer
3. USB Cable
How?
if you need PARAM.bin file that means you know how things work, so i'm not gonna explain every little step.
1. Make folder on your desktop and Open 2 command line programme windows in that directory.
2. choose one window and run this commands
adb shell
su
dd if=/dev/block/platform/13540000.dwmmc0/by-name/PARAM of=/sdcard/PARAM.bin bs=4096
Block Path in above dd command can be different in your device. if you failed to open renamed zip file, you need to Find Correct Block and replace that in dd command
3. goto second command line window and run
adb pull /sdcard/PARAM.bin
4. To Extract Files from bin Just rename .bin file to zip (param.bin.zip)
Done.
Click to expand...
Click to collapse
hello sir i have Samsung galaxy A50 (505F)my phone was ok and i kept it on my bed after using and went to do some work when i came back & saw my phone was restarting automatically whereas no body touched it, it does not happened before then i thought its ok maybe some reason it happen but after restarting my phone its continuously booting on Samsung logo and some strange lines are coming behind the logo every time its not getting on properly only restarting, so after that i tried soft rest even hard rest\wipe data factory rest but same issue is there and i tried software with latest stock firmware with latest and different version of Odin its just stuck on CM software not starting even i tried combination file but stuck on boot i tried PIT file also it passed but nothing is happened
(Bootloader lock by OEM) And In
Recovery Mode on top
BIN MODE (By Param) (not sure BIN or Something else because of curved screen)
Cause: BL:Recovery Mode Set by Key,
Even i visit to Samsung service center and they tried to do software but unable to do and they just simply said it will change the board but i know its some kind of software issue and i'm not able to spend so much money in this situation :crying: please give me some solution i want to share some pictures of my device with you please give me your mail Id so i can share with you please help and give some solution
Note:-there is not any third party app installed in my device still it happen....please give me solution
I think this does not work anymore with the latest Android 10 Updates.
Funciona en Android 10 para S9+ Snapdragon? Alguien lo probó?No logro sacar el paran.bin, ayuda porfa.
AUPMA said:
Seems Like your block is different. So you need to Find Correct block and replace that on dd command
Click to expand...
Click to collapse
my parab file is mmcblk0p12. it did not open with tar or zip. i aleardy use custom rom, there's any chance install custom rom by some how encrypt the file so i can not open it. did i should reflash the stock rom then try change the logo image?
my phone is j5
Please Help!
I did something very stupid today.
Unlocked my RMX2170, got into fastboot.
Tried to flash PBRP as recovery, and some vbmeta.img image as vbmeta of my phone.
Disaster! My phone got stuck in a bootloop of just repeatedly booting into fastboot.
No recovery, nothing.
From there, I installed SHRP using the fasboot flash recovery command, and now I have SHRP.
SHRP, however, cannot flash ANYTHING as a result of an error that it "failed to mount /system_root and /vendor"
The phone can effectively boot into Qualcomm EDL and fastboot.
I've tried countless tools and software to get back to stock. Nothing works. MSM requires a login to function, so it won't work.
Anyone at all, please, can you tell me how to get back to FULL stock?
Through sheer trial and error,
Procedure:
1. Downloaded A37 ofp file from www.gsmmafia.com/realme-7-pro-rmx2170-flash-file/ (or mediafire download)
2. Extracted it using bkerler/oppo_decrypt's ofp_qc_extract.py into a folder:
Code:
py -3 -m pip install -r requirements.txt
py -3 ofp_qc_extract.py a37_ofp_file.ofp .\extracted
3. Rebooted the phone into fastboot, ready for flashing (Power + Volume Down for me)
5. Ran:
Code:
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash super super.img
fastboot flash boot boot.img
(keep in mind these .img files came from the extracted ofp's folder!)
6. Rebooted into system using the fastboot menu (START)
7. I'm pretty sure my phone ran A41 before today... so I gave the phone an update from inside Android, that seemed to work fine.
As a bonus, my bootloader seems to have remained unlocked? Nice!
Also interesting: holding volume up does not boot into recovery. This is an issue for another day lads.
Can you explain me step 2? I have bootloped phone and I don't understand how to use oppo decrypt
Domac5 said:
Can you explain me step 2? I have bootloped phone and I don't understand how to use oppo decrypt
Click to expand...
Click to collapse
1. Download and install Python on your computer.
2. Press Windows + R, then type cmd, hit enter to access a terminal.
3. Make sure Python works by trying py -3 in the terminal. (Type exit() to exit the Python shell)
4. Download oppo_decrypt's repository zip and extract it in a folder anywhere.
5. Use cd in the terminal to navigate to the extracted folder.
6. Run this command to install the dependencies of oppo_decrypt:
Bash:
py -3 -m pip install -r requirements.txt
7. You should have already downloaded the ofp file for the phone. If not, get it from here.
8. You need to run the Python script in order to extract the images you need, so, you should copy it to the folder where your ofp file is.
Bash:
cp ofp_qc_decrypt.py /where/the/ofp/file/is/ofp_qc_decrypt.py
9. Go into the directory with the script and ofp file, and extract it.
Bash:
py -3 ofp_qc_extract.py the_ofp_file.ofp .\extracted
The extracted images you need, if you were on Android 10, should be in the extracted folder in the terminal's working directory.
Best of luck, although I can't really help you step-by-step for everything, so I suggest you visit r/realme's Discord.
Go to the Discord for more help!
Codian said:
1. Download and install Python on your computer.
2. Press Windows + R, then type cmd, hit enter to access a terminal.
3. Make sure Python works by trying py -3 in the terminal. (Type exit() to exit the Python shell)
4. Download oppo_decrypt's repository zip and extract it in a folder anywhere.
5. Use cd in the terminal to navigate to the extracted folder.
6. Run this command to install the dependencies of oppo_decrypt:
Bash:
py -3 -m pip install -r requirements.txt
7. You should have already downloaded the ofp file for the phone. If not, get it from here.
8. You need to run the Python script in order to extract the images you need, so, you should copy it to the folder where your ofp file is.
Bash:
cp ofp_qc_decrypt.py /where/the/ofp/file/is/ofp_qc_decrypt.py
9. Go into the directory with the script and ofp file, and extract it.
Bash:
py -3 ofp_qc_extract.py the_ofp_file.ofp .\extracted
The extracted images you need, if you were on Android 10, should be in the extracted folder in the terminal's working directory.
Best of luck, although I can't really help you step-by-step for everything, so I suggest you visit r/realme's Discord.
Go to the Discord for more help!
Click to expand...
Click to collapse
Step 8 not working for me
Do you have original recovery.img file,please send me? I just can't extract it from ofp file, 2 days trying and just can't
Domac5 said:
Step 8 not working for me
Click to expand...
Click to collapse
Sorry, instead of "cp" the command is "copy", my mistake.
Domac5 said:
Do you have original recovery.img file,please send me? I just can't extract it from ofp file, 2 days trying and just can't
Click to expand...
Click to collapse
You can't flash recovery.img. It won't work, I tried. You need to re-flash all of the system partitions like in my post.
I don't have the files anymore, as I did this a while ago. Sorry.
Codian said:
Sorry, instead of "cp" the command is "copy", my mistake.
Click to expand...
Click to collapse
Still doesnt work
I did it, problem was in python3 comand, that one should be typed without number 3 because that doesn't work in windows. Now it's extracting
did you had these problem?