Hello
here i am posting here because i cant post on Miscellaneous Android Development , how ever i think i post there before while working on B5512
I Just got new G700 it came with B115 middle east channel , phone is good but as a start is there is a update i must ask my self is root ready , and CWM for sure so i start the digging
@chamaruco thank you for your great thread which saved and helped many people
now i got a file and i think you were looking for it ""G700-U10_V100R001C00B124CUSTC432D001_Firmware_Portugal_Channel-Others_4.2.1_EMUI 1.8_05021LMW.zip"" it contain usb upgrade and sd upgrade with drv and flash tool
i notice EMUI 1.8 not 1.6 which i saw for example a permission manager with it on P6 is that here in that rom too ?
is that rom improved than mine b115 phone is good for first look but
(in B115)
1-camera quality is strange i dont mean bad but it look very strange it is like very poor on quality
2-in call volume is too low in my opinion all " in test mode"
Question now did any one get that update "EMUI 1.8 B124" can tell is there is any improvements ?!
Question am i able to flash CWM image directly with flash tool to save some annoying procedures ?!
a member here provide flasher and cwm.img and orginal recovery.img
i did not work with the phone yet need to shift data from old phone remove ext2 part and prepare for change , and feeling lost here
want to strike it all once
i will upload "EMUI 1.8 B124" soon as it came from a private server
any suggestions are welcome
When you install 1.8 you will notice there is only a tap error from uploader..it is a 1.6 emui. That's all.
Hello
some info to add
incase of softbrick the phone and unable to flash using spflash tool and receive " not allowed , forbidden "
solution
inside the usb upgrade >> flash "Rework-Secro" using scatter in same folder then you will be able to use download mode again
how to install this firmware i.e. B124 on G700-10
chamaruco said:
When you install 1.8 you will notice there is only a tap error from uploader..it is a 1.6 emui. That's all.
Click to expand...
Click to collapse
chamaruco; Thanks for the best of the best user guides you have been making for all of us, but what i want to know is to be able to install the B124 into my phone i.e. G700-10, i have rooted my phone using farmaroot, made a back up of my factory shipped OS and make all my data backup safe through Hisuit, have downloaded the firmware B124 Purtogal version, extracted the zip, (it is now carrying META-INF, boot.img, cust.img, logo.bin, sdload.log, system.img) i have made a folder in my SD card named dload and copied the files in it, uninstalled mobileuncle, reinstalled new mobileuncletool, copied my backuped recovery.img into my SDcard and somehow installed the recovery in to my mobile,
now please show me the way forward, what i need to do and how, please step by step if you kindly can. please.
YOU ARE THE BEST CHAMARUCO
talvigi said:
chamaruco; Thanks for the best of the best user guides you have been making for all of us, but what i want to know is to be able to install the B124 into my phone i.e. G700-10, i have rooted my phone using farmaroot, made a back up of my factory shipped OS and make all my data backup safe through Hisuit, have downloaded the firmware B124 Purtogal version, extracted the zip, (it is now carrying META-INF, boot.img, cust.img, logo.bin, sdload.log, system.img) i have made a folder in my SD card named dload and copied the files in it, uninstalled mobileuncle, reinstalled new mobileuncletool, copied my backuped recovery.img into my SDcard and somehow installed the recovery in to my mobile,
now please show me the way forward, what i need to do and how, please step by step if you kindly can. please.
YOU ARE THE BEST CHAMARUCO
Click to expand...
Click to collapse
Dload inside put update.app file, restart in updatemode
chamaruco said:
Dload inside put update.app file, restart in updatemode
Click to expand...
Click to collapse
But my mobile does not boot into CWM recovery mode as i have seen in my previous Qmobile A8 it always restarts in the defualt recovery mode which only give options to "1. reboot, 2. update from SDcard, 3. update from cashe, 4. wipe/delete user data and wipe/delete cache and in the last there is a calibarate TP, AND OFF COURSE THESE ALL ARE THE ANDROID BUILTIN RECOVERY STEPS NOT OF THE CWM
And off course there is not any file or folder named update.app in the downloaded .zip/extracted file. "as i have mentioned above the folder contains a folder named META-INF and three img files named as boot cust and system while a .bin file named logo too.
THANKS FOR YOUR TIME AND HELP.
foffa said:
Hello
some info to add
incase of softbrick the phone and unable to flash using spflash tool and receive " not allowed , forbidden "
solution
inside the usb upgrade >> flash "Rework-Secro" using scatter in same folder then you will be able to use download mode again
Click to expand...
Click to collapse
So after I select the Reworked scatter file there is only the sec_ro partition checked to flash. So after flashing it do I now select the previous scatter file and then flash everything (including preloader)?
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!!
I rooted my phone, and then i was trying to flash a Marshmallow Rom. For this, i wiped my system, boot, dalvik cache, internal memory. I forgot to take a nandroid backup. For some reasons, there was some error in flashing that zip file, so i tried to reboot my phone normally and it failed. When i reboot my phone, the company logo appears and it remain sticked there. For now, i could only access the recovery and fastboot. Please HELP me..... Thank you.....
You got exactly same problem with me but i have model: Honor7 Premium (PLK-L01)
Hi,
what did you expect? If you wipe de system partition then obviously the operating system is gone.
What you need to do is to download the full stock rom of your phone somewhere on the internet (needrom.com for instance if available).
You need to take the closest version of your old system and also the same technical name (PLK-UL00).
For instant if you were already on Android 6.0, you can no longer use a stock rom of Android 5.x.
When you have that full stock rom on your computer, you need to use multi-tools and use the unbrick option. Meaning you will be asked to extract the most important img files from the stock rom and to put them into a specified folder. The tool will then restore that rom on the partition file.
Kind reg,
I had android lollipop 5.0.2. Is it possible that i install the backup file of any other person's honor 7 PLK-UL00 running same android?
Hi,
please have a look there and use the stock rom that fits with your model and version.
https://yadi.sk/d/ZD8hXFjenRFHf
Kr,
how do i flash an UPDATE. APP file?
Create folder called dload on your SDCard and copy Update.app file to your SDCard inside that "dload" folder.
Then shutdown your device and use 3-Button method(Vol- & Vol+ & Power button) to boot that to recovery, that should start installing "recovery" file what is that Update.app inside dload folder.
Sent from my PLK-L01 using XDA-Developers mobile app
i don't know but the 3-button method is not working. When i do so, it boots to the recovery and nothing happens. Anyways, i have copied the dload folder with update.app file to the sdcard.
Use Multi-Tools available in the forum. There is a little app where you will be able to extract all required files from the file update.app.
Then in multi-tools use unbrick option and it will install the stock rom correctly. ++
http://forum.xda-developers.com/honor-7/general/honor-7-multi-tool-t3281176
Thank you!!!!! Sebastien_be and everyone to help me... It worked very well.. Thank u guys so much for the help...
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.
Hi All -
I have a Xiaomi Redmi Pro with an unlocked bootloader which is stuck in a boot loop. It has some very recent pics and videos of my 8 months old daughter that I desperately want to save. Thre is no SD card in the phone. However, I cannot get the phone to be detected by the computer/ boot in recovery etc. I have tried a few DIY(TWRP) from online forums but to no avail. I flashed it with MI flash tool(fastboot rom) using save user data; Flash was successful but the phone is still stuck in a bootloop.
I came across an article on Gizbeat with the title " Flash ROM upgrade firmware without losing user data cache" which showed how to save user data while flashing the phone with SP Flash tool. The author has advised deselecting certain parts of the scatter file. I have downloaded Redmi Pro china stable fastboot rom, but the scatter file has different parts to what was shown in the tutorial. At this stage, I do not know what to deselect.
Can the experts on this forum please advise which options should be selected/deselected to save user data while flashing? I have attached a screenshot of the scatter file. Thanks already.
Sid
sid_aj said:
Hi All -
I have a Xiaomi Redmi Pro with an unlocked bootloader which is stuck in a boot loop. It has some very recent pics and videos of my 8 months old daughter that I desperately want to save. Thre is no SD card in the phone. However, I cannot get the phone to be detected by the computer/ boot in recovery etc. I have tried a few DIY(TWRP) from online forums but to no avail. I flashed it with MI flash tool(fastboot rom) using save user data; Flash was successful but the phone is still stuck in a bootloop.
I came across an article on Gizbeat with the title " Flash ROM upgrade firmware without losing user data cache" which showed how to save user data while flashing the phone with SP Flash tool. The author has advised deselecting certain parts of the scatter file. I have downloaded Redmi Pro china stable fastboot rom, but the scatter file has different parts to what was shown in the tutorial. At this stage, I do not know what to deselect.
Can the experts on this forum please advise which options should be selected/deselected to save user data while flashing? I have attached a screenshot of the scatter file. Thanks already.
Sid
Click to expand...
Click to collapse
Hi,
It seems like you've posted in the wrong section. The correct section would be this one: https://forum.xda-developers.com/redmi-pro/help
Regarding the question, however, you can uncheck "userdata" part (and probably "cache" too). Doing so will leave your pictures untouched (hopefully the phone boots).
Also, if you can boot to TWRP, there is no need of this. You should be able to access your internal storage in TWRP from your computer. Otherwise, you can backup the userdata partition with TWRP, copy it to your computer and then try to access the contents of the backup. You can also try to boot to stock recovery, there SHOULD BE an option to backup the userdata. If such option exists (recent MTK phones do have this option by default), you can give it a shot. I have no idea how it works, though.
Nonta72 said:
Hi,
It seems like you've posted in the wrong section. The correct section would be this one: https://forum.xda-developers.com/redmi-pro/help
Regarding the question, however, you can uncheck "userdata" part (and probably "cache" too). Doing so will leave your pictures untouched (hopefully the phone boots).
Also, if you can boot to TWRP, there is no need of this. You should be able to access your internal storage in TWRP from your computer. Otherwise, you can backup the userdata partition with TWRP, copy it to your computer and then try to access the contents of the backup. You can also try to boot to stock recovery, there SHOULD BE an option to backup the userdata. If such option exists (recent MTK phones do have this option by default), you can give it a shot. I have no idea how it works, though.
Click to expand...
Click to collapse
Thanks Nonta72. I have tried but cannot boot to TWRP. My phone is either stuck in a bootloop or I can boot it to fastboot screen. without being able to boot to TWRP, how can I backup the userdata partition?
sid_aj said:
Thanks Nonta72. I have tried but cannot boot to TWRP. My phone is either stuck in a bootloop or I can boot it to fastboot screen. without being able to boot to TWRP, how can I backup the userdata partition?
Click to expand...
Click to collapse
Can you flash things with SP Flash Tool?
Try to flash just the boot.img (uncheck everything else) to see if you can do that.
Nonta72 said:
Can you flash things with SP Flash Tool?
Try to flash just the boot.img (uncheck everything else) to see if you can do that.
Click to expand...
Click to collapse
I haven't tried it yet, and that is why made this post so that I don't end up screwing things whilst using SP Flash tool. You mean flash the full rom with just boot.img selected in the scatter file? Thanks much.
sid_aj said:
I haven't tried it yet, and that is why made this post so that I don't end up screwing things whilst using SP Flash tool. You mean flash the full rom with just boot.img selected in the scatter file? Thanks much.
Click to expand...
Click to collapse
When you open SP Flash Tool program and then select the scatter file by clicking "Scatter Loading", you will be given the possibility to choose which partitions to flash. So, you have to uncheck every partition in SP Flash Tool except "boot" (on the left side, you can see the checkboxes). After that, click "Download", power off the phone, plug it in. It will flash just the boot.img and the process will be very quick (few seconds).
If you want to be ABSOLUTELY sure (even though, unchecking the other partitions is enough), you can go to your stock rom's folder containing the scatter file and then delete the userdata.img file. If the corresponding file isn't found in the folder containing the scatter file, the program will automatically uncheck that partition and will remain so untill you manually provide a usable file for that partition.
Nonta72 said:
When you open SP Flash Tool program and then select the scatter file by clicking "Scatter Loading", you will be given the possibility to choose which partitions to flash. So, you have to uncheck every partition in SP Flash Tool except "boot" (on the left side, you can see the checkboxes). After that, click "Download", power off the phone, plug it in. It will flash just the boot.img and the process will be very quick (few seconds).
If you want to be ABSOLUTELY sure (even though, unchecking the other partitions is enough), you can go to your stock rom's folder containing the scatter file and then delete the userdata.img file. If the corresponding file isn't found in the folder containing the scatter file, the program will automatically uncheck that partition and will remain so untill you manually provide a usable file for that partition.
Click to expand...
Click to collapse
Many thanks. I will give it a shot over the weekend. Fingers crossed!
Nonta72 said:
When you open SP Flash Tool program and then select the scatter file by clicking "Scatter Loading", you will be given the possibility to choose which partitions to flash. So, you have to uncheck every partition in SP Flash Tool except "boot" (on the left side, you can see the checkboxes). After that, click "Download", power off the phone, plug it in. It will flash just the boot.img and the process will be very quick (few seconds).
If you want to be ABSOLUTELY sure (even though, unchecking the other partitions is enough), you can go to your stock rom's folder containing the scatter file and then delete the userdata.img file. If the corresponding file isn't found in the folder containing the scatter file, the program will automatically uncheck that partition and will remain so untill you manually provide a usable file for that partition.
Click to expand...
Click to collapse
Hi,
I tried, but it did not work. Getting PMT error(screenshot attached). Thanks.
sid_aj said:
Hi,
I tried, but it did not work. Getting PMT error(screenshot attached). Thanks.
Click to expand...
Click to collapse
It appears that you have held an incompatible scatter file. Please note that the scatter file isn't the same for the 3 versions.
The Note 4 (Mediatek) comes in 3 versions:
- 16+2
- 64+3
- 64+4 (You probably can use 64+3 scatter in 64+4 and vice versa but 16+2 scatter is likely not compatible with 64GB versions and also vice versa).
I may be wrong! But you have to make sure that it's the correct firmware that you have.
Nonta72 said:
It appears that you have held an incompatible scatter file. Please note that the scatter file isn't the same for the 3 versions.
The Note 4 (Mediatek) comes in 3 versions:
- 16+2
- 64+3
- 64+4 (You probably can use 64+3 scatter in 64+4 and vice versa but 16+2 scatter is likely not compatible with 64GB versions and also vice versa).
I may be wrong! But you have to make sure that it's the correct firmware that you have.
Click to expand...
Click to collapse
Hi Nonta72 -
I have downloaded the Redmi pro fastboot stable rom from here - http://en.miui.com/a-234.html and using the scatter file that came along with it. My phone is 3gb/64gb Helio x25(6797T). The rom page does not have different roms for different versions of processor - just stable or developer. I have attached my scatter file for your reference. Thanks
sid_aj said:
Hi Nonta72 -
I have downloaded the Redmi pro fastboot stable rom from here - http://en.miui.com/a-234.html and using the scatter file that came along with it. My phone is 3gb/64gb Helio x25(6797T). The rom page does not have different roms for different versions of processor - just stable or developer. I have attached my scatter file for your reference. Thanks
Click to expand...
Click to collapse
I really can't tell whether you have the correct scatter file or not.
But I do know that it's really rare that different versions of the phone share the same scatter file especially when there is a big gap between the storages.
If SP Flash Tool doesn't work, you can try to backup the device and maybe you'll get a working scatter file.
Here is an interesting guide that will teach you how to backup your phone (and possibly create a scatter file from it as well).
https://forum.hovatek.com/thread-13347.html
Notes:
You may want to turn off your computer's internet connection before using the program
On step 9, make sure you tick the USERDATA checkbox! If it succeeds, you'll get your pictures in that file. Since the phone has a huge 64GB storage, make sure your computer has enough space (70GB or more) just to make sure!
Hello everyone
I hope somebody can help me. I have a Huawei y6 scc-u21 that I need to fix. I have downloaded a firmware flash file to reflash the phone however, after doing so, I found that the gapps are not installed. I tried to download and install every update but still I did not have gapps installed.
Also, I noticed that after flashing and everytime I do a factory reset, the phone would not prompt me to a setup process and just automatically goes to the normal interface. Some settings are missing too.
Please help. Without GAPPS this phone is basically useless. Doesn't even get a signal even though a SIM card is inserted.
Thanks.
I had the same problem.. here is what i do to solve it:
1- download u21 cm2 backup file from here:
http://www.mobilekse.com/2018/09/huawei-y6-scc-u2131-all-file-firmware.html?m=1
2. Extract it with 7zip.
3 download an sd card update "update.app".
4. install the update with sd card.
5- extract the file with "huawei update extractor" and get "BOOT.img" , "ABOOT.img" and "CUST.img" rename them to lowercase and put them to the folder of the first firmware of step 1/
6- open qfil, select flat buit, select the programmer path from the firmware folder then select from the top: tools then partition manager.
7- select boot.img partition and with a right click select manage partition.
8- choose the boot.img extracted and replaced.
9- do the same for aboot.img and cust.img
10- the phone will exit this dump mode and you will find playstore, keyboard, notfications..
Ask me if you found anything not clear