Related
Frustration ! Still couldn´t update my At&t ATRIX to Gingerbread. Would really apreciate some help from the forum. Please !
Actual status: Original AT&T ATRIX 4G / System version 4.1.83.MB860.ATT.en.US / Android 2.2.2 /rooted (Gingerbreak)
To update I did the four following steps (as explained in the xda forum):
1. STEP Unlook Bootloader (to be able to flash CWM)
2. STEP Flash CWM (to be able to flash Gingerbread.img)
3. STEP Flash Gingerbread
4. Done
1. Unlock Bootloader
The first STEP "Unlock the bootloader" I did according to Kenneth Pennington on briefmobile
( http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader )
and the video from MobileTechVideos
( http://www.youtube.com/watch?v=H02N4p9vEg0 )
Thanks to both.
Every message is looking on my ATRIX as it it discribed / show on the video. My ATRIX shows "Unlocked" now on the boot screen.
-> So it seems the bootloader is unlocked.
I even did this twice (when I had no success with the update) and second time when I tiped
moto-fastboot oem unlock ####, I got the message that my bootloader is already unlocked.
Question: Is there any way to proove that it is unlocked ?
Question: Is the prove that CWM could be installed ?
2. Flash CWM
This step I did exactly how it is explained in the thread [Unlocked Only][Release]CWM Recovery Mod for Atrix 4G 2011-06-30 updated again!
( http://forum.xda-developers.com/showthread.php?t=1138541 )
Everything fine so far. When I booted my ATRIX in recovery mode, now the menu of CWM is shown.
I did a backup of my system with CWM without problems.
Question: Is there any possibility that something went wrong with the installation of CWM, even if the menu is displayed and backup is working ?
3. Flash Gingerbread
For this step I used the howto by Kenneth Pennington on briefmobile and his update Gingerbread-4.5.91.zip. Link in the same howto.
(http://briefmobile.com/download-android-2-3-4-gingerbread-for-motorola-atrix-4g)
No success. The update process starts and after "two" seconds it stopped with the following failure messages. First one with update on the external SD card, second one on the internal SD card.
Support:bbs.goapk.com
-- Installing: /sdcard/Gingerbread-4.5.91.zip
Finding update package...
Opening update package...
Installing update...
Installation aborted
-- Installing: /internal/Gingerbread-4.5.91.zip
Finding update package...
Opening update package...
Installing update...
Installation aborted
Any ideas ? What went wrong ? Would be really happy for support.
Try using this recovery..
http://forum.xda-developers.com/showthread.php?t=1204500
When booting up do you see the word unlocked up in the left corner? If so you are unlocked but I would recommend flashing romracers cwm. You might also have a corrupted file of 4.5.91. I would re download a new copy and put it in your sd card and see how that goes. Make sure to wipe/factory reset and wipe your davlik cache as well.
1.ATRIX-in-PT said:
-- Installing: /sdcard/Gingerbread-4.5.91.zip
Finding update package...
Opening update package...
Installing update...
Installation aborted
-- Installing: /internal/Gingerbread-4.5.91.zip
Finding update package...
Opening update package...
Installing update...
Installation aborted
Any ideas ? What went wrong ? Would be really happy for support.
Click to expand...
Click to collapse
Are you selecting "Install update" when in CWM? Cuz if you are, don't. I believe that is for official updates if you're unable to do them OTA.
Next, install romracer's recovery. You want "Install zip from SD Card". Exact wording might be a little off, but you get the idea. Locate your ROM and you should be good to go.
XRange, Phoneguy589, ghost_op. Thanks for your ideas.
@ XRange
Instead of CWM (Android Recovery) I should use the moto-fastboot (flash recovery) ? Is this an alternative method to CWM ?
@ Phoneguy589
Not sure if the file could be corrupted. Seemed a lot of people used this file for their update without any problems. In my opinion the problem related in some way to my phone, but in which way ?
Something missing ? Something (CWM?) not installed correctly ?
I can download the file again. Which was the file you used to update for example ?
Don't understand your "wipe/factory reset and wipe davlik cache". I haven't done any of these operations, as I never read about this in one of these howtos.
Should it be necessary ? Isn't CWM (on Android Recovery) working on such an early level (before any system is booted) that it really doesn't matter what is installed on the smartphone. Or am I wrong ?
@ ghost_op
Yes, I did the "Install from SD card". Tried both, internal and external.
Not clearing the previous data that was stored can cause an issue. Its usually a process every user does when installing a new rom. Davlik cache will be located under advanced in cwm. The file you downloaded may have not downloaded properly which is why I gave you the suggestion of re downloading the file just in case something during the transfer didn't properly copy.
I am confused now. It seems the Gingerbread.zip I downloaded has to be flashed with moto-fastboot.
OK. Three questions now:
- Is it possible to flash to Gingerbread with CWM or fastboot ?
- What is the difference to flash to Gingerbread with CWM or fastboot ? I mean the difference in a result.
- Is the img (zip) file the same to flash with CWM or fastboot, or is it different ? Has to be a proper one for fastboot and a different proper one for CWM ?
Because, now I think my problem is I got a wrong Gingerbread.img to flash with CWM. To be honest, if it is possible to update to Gingerbread in both ways (CWM and fastboot), I think the CWM method is a lot "better".
1.ATRIX-in-PT said:
I am confused now. It seems the Gingerbread.zip I downloaded has to be flashed with moto-fastboot.
OK. Three questions now:
- Is it possible to flash to Gingerbread with CWM or fastboot ?
- What is the difference to flash to Gingerbread with CWM or fastboot ? I mean the difference in a result.
- Is the img (zip) file the same to flash with CWM or fastboot, or is it different ? Has to be a proper one for fastboot and a different proper one for CWM ?
Because, now I think my problem is I got a wrong Gingerbread.img to flash with CWM. To be honest, if it is possible to update to Gingerbread in both ways (CWM and fastboot), I think the CWM method is a lot "better".
Click to expand...
Click to collapse
Based on the filename you originally posted, it definitely looks like you downloaded the .img files zip from the bottom of the briefmobile page. Fastboot would be used to install those manually, as opposed to all at once with CWM.
CWM and fastboot will both get you the same end result. They're just different ways of getting there. This should give you the correct CWM version.
CWM isn't better, just easier for some. It allows you to flash ROMS and other mods on the go, without having to be connected to a computer with fastboot. There is a script present in the CWM version that controls how the files are installed. That is why you were getting an error earlier, there was no script to tell the recovery what to do.
Thanks ghost_og for the link and Phoneguy589 for the tip "wipe/factory reset" and "cache". So the files are different for CWM and fastboot.
Now I looked into the zip file and the structure is the following:
Gingerbread-4.5.91.zip
boot.img
data.img
radio.img
system.img
webtop.img
-> This is the correct zip file for fastboot
Gingerbread-Atrix-Beta-4-5.zip
META-INF
osh
system
boot.img
The first three are directories with subdirectories a couple of files
-> This is the correct zip file for CWM
However I do not know, why the size of both files is quite different
Gingerbread-4.5.91.zip / 409,4 MB
Gingerbread-Atrix-Beta-4-5.zip / 298,6 MB
-> A difference of 100 MB (!). As both should have the same result, this seems to be strange.
-> Why the CWM file is labled Beta. Is it Beta compared with the fastboot file ?
So in the end what do you advise ?
- To update with fastboot and Gingerbread-4.5.91.zip (409,4 MB)
- To update with CWM and Gingerbread-Atrix-Beta-4-5.zip (298,6 MB)
Reading a lot of threads, I got the idea to brick the phone might be more easy with fastboot than with CWM (Android recovery). Maybe I am wrong. Luckily no experience (brick) yet.
YES we can. It is done.
In the end wasn't very difficult and just running fine without any issues. My problem was to be nervious (do not want my phone bricked, it's my only one) and as it was the first time for me to flash a ROM.
Don't want to write a new howto, there are the experts in the forum to do this. Only a short summery for anybody how has similar problems.
So my updated from Android 2.2.2 to Gingerbread was done in this way:
1. STEP Unlook Bootloader (to be able to flash CWM)
2. STEP Flash CWM (to be able to flash Gingerbread.img)
3. STEP Flash Gingerbread
4. STEP Reboot & Done
Two things which troubled me, because I overlooked first:
- you definitely need to remove "install_recovery.sh" in /system/etc/ otherwise you will get a problem with installation of CWM
- check that you get the right ROM image, because they are different for fastboot and CWM.
I can highly recommend to do the update with CWM
( http://forum.xda-developers.com/show....php?t=1138541 )
and with the ROM from Kenneth
( http://briefmobile.com/download-android-2-3-4-gingerbread-for-motorola-atrix-4g )
worked perfect for me.
Thank you for your support / ideas in the xda forum. Love this forum ! Thread can be closed.
So I realized that there wasn't much support out there for the padfone X. I love my padfone X regardless of its tiny battery, lack of developer support, and unpopularity. So I decided to embrace my love for tech and support the device myself.
So, Asus is still showing love to the padfone S(not X). That being the case it's the international version of the AT&T X; the hardware is almost identical. I decided to turn my X into an S, unlock the bootloader, upgrade to Android 5(I know its not the latest but it's better than 4.4.2), root and enjoy.
Breaking, bricking, whatever... This is all on you, this is what I did to my phone. I'm only sharing my experience. Make sure your phone is fully charged before you begin. Don't say I broke your phone, your taking a risk. I take no credit if this does or doesn't work. This process is time consuming and might not work for you. Don't blame me for wasted time.
This should give you carrier unlock as well.(not tested) and you should be able to use the Padstation with Lollipop. I'll leave download links below.
Steps
#1 back up all your data(titanium etc)
#2 download and run New Kingroot(took 5 tries to work)
#3 download and run superSume Pro
#3a step 3 should have installed SuperSU... Uninstall Kingroot & update SuperSU (use normal method); get a root checker and check root
#4 download a custom recovery(I personally like TWRP, but its buggy on this phone whatever) store the recovery.img on your phone's internal storage(not sd)
#5 install a flash tool(rashr or flashify will do) flash the custom recovery img.
#5a you should have root and custom recovery now, even if the bootloader is locked.
#6 The hard part. Put the S firmware on your internal storage(not sd card)
#7 in recovery mode you need to make another back up(back ups are awesome) do a factory reset in recovery(also wipe cache)
#7a install S firmware(do this in recovery mode) and restart phone. (Initial boot takes about 2 minutes). This might not work the first time(took 5 restores for me to finally get it)
Congratulations!!! You now have a "Padfone S"
#8 preferably using clockwork mod, install crowlock zip file by quarx to unlock bootloader
#9 to upgrade from 4.4.2 to 5.0 you need to go through about 4 updates from the Asus website. Follow this link(only use WW upgrades)
#10 after the upgrades you may have lost root. Just follow steps 2 and 3 again.
Asus "says" they will be releasing Android 6 for the Padphone S... Don't know how true that is, hope so. ENJOY!!!
Downloads and links
Kingroot:
http://www.appsandroidapk.com/tools/kingroot/
S firmware: thank you to tjsnooley!!!
http://forum.xda-developers.com/padfone-x/general/i-have-done-it-t3053207
TWRP/Cwm: thanks quarx!!!
http://quarx2k.ru/asus_padfone_s/recovery/
Crow Lock:
http://quarx2k.ru/asus_padfone_s/
Asus upgrades:
https://www.asus.com/support/Download/29/1/0/10/6vHIzvNAKBCV4v9w/32/
The superSume Pro costs money, you'll have to find it on your own, sorry...
This is a good write up but doesn't work on new units that was recently pushed out...I have tried multiple custom recoveries and none will even write to the phone.I keep getting a response remote device doesn't allow operation.I do have it rooted with the intel tool.Any advice would be great.Thanks in advance.
Surgeman said:
This is a good write up but doesn't work on new units that was recently pushed out...I have tried multiple custom recoveries and none will even write to the phone.I keep getting a response remote device doesn't allow operation.I do have it rooted with the intel tool.Any advice would be great.Thanks in advance.
Click to expand...
Click to collapse
Think it's because 7a and 8 should be switched around. You can't flash the Padfone S firmware on a Padfone X until you unlock the bootloader.
So basically, the steps:
1. Root
2. Install Flashify from the Play Store
3. Use Flashify to flash the Padfone X/S TWRP
4. Boot into TWRP and make a backup.
5. In TWRP, flash the Crowlock bootloader unlocker zip
6. Wipe internal storage except for /sdcard
7. Flash the Padfone S firmware zip
8. Reboot and enjoy
Also, #9 and #10 don't have to be done. The firmware update zips that ASUS publishes are full system images, so you can just flash the newest one and be good to go. (but make sure to flash WW)
This is an other on how to do a conversion in a different way.
There are other guides that are written up that do the exact same thing.
I have also written a guide to do this as well if that helps, its kinda of different but it is comprehensive.
One difference is that to root the padfone x I did towelrootv1 (other versions don't work) because its easier and not worrisome by default. ( I haven't mentioned that because I assumed people have rooted it already and know what they are doing)
Another difference is that you don't need to keep updating the device to the latest, that's just wasting time.
You could just go from the at&t 4.4.2 version, to the absolute latest version of the padfone s firmware.
I just don't want to see any confusion out of this guide in general, but keep in mind that this is a similar but different guide to a conversion.
---------- Post added at 10:04 AM ---------- Previous post was at 10:01 AM ----------
Surgeman said:
This is a good write up but doesn't work on new units that was recently pushed out...I have tried multiple custom recoveries and none will even write to the phone.I keep getting a response remote device doesn't allow operation.I do have it rooted with the intel tool.Any advice would be great.Thanks in advance.
Click to expand...
Click to collapse
Wait what device do you have?
Padfone x mini?
Thanks for the advice xtermmin but something has changed with the newer units.Flashify just crashes and if you fastboot flash the recovery you get this command has been stubbed.Also...towelroot won't even touch it for root now.I did manage to get it rooted with the intel tool with a temp cwm recovery,and flashed the SU zip beta.I have tried flashing the recovery with terminal emulator no go.If you boot with the intel temp cwm recovery and flash the Crowlock zip it errors out.I have followed several threads and so far nothing will tough it...Asus has been watching us....lol...
Oh the device is AT&T Padfone X mini by the way.
Surgeman said:
Thanks for the advice xtermmin but something has changed with the newer units.Flashify just crashes and if you fastboot flash the recovery you get this command has been stubbed.Also...towelroot won't even touch it for root now.I did manage to get it rooted with the intel tool with a temp cwm recovery,and flashed the SU zip beta.I have tried flashing the recovery with terminal emulator no go.If you boot with the intel temp cwm recovery and flash the Crowlock zip it errors out.I have followed several threads and so far nothing will tough it...Asus has been watching us....lol...
Oh the device is AT&T Padfone X mini by the way.
Click to expand...
Click to collapse
The Padfone x mini contains an intel processor so they have a different kind of bootloader than the Padfone x, which has a Snapdragon 800.
Towelroot was patched when newer updates came along, but it still works with the original padfone x since they never got an update from at&t in the last year.
Also the padfone s fw is not compatable with the padfone x mini, since there is a different dock involved. (different screen and resolution).
Overall both devices may look similar but have completely different hardware, so that why it will not work for you.
Thanks for verifying the regular X processor..I seen it said it had the Snapdragon but was curious of the fact.Well I guess I'm on my own,and maybe I need to start a support thread for this thing.lol...Thanks for everyone's help...
How Can I unlock bootloader ATT 11.10.8.16? is posible? help me pls
leo025 said:
How Can I unlock bootloader ATT 11.10.8.16? is posible? help me pls
Click to expand...
Click to collapse
xtermmin said:
Think it's because 7a and 8 should be switched around. You can't flash the Padfone S firmware on a Padfone X until you unlock the bootloader.
So basically, the steps:
1. Root
2. Install Flashify from the Play Store
3. Use Flashify to flash the Padfone X/S TWRP
4. Boot into TWRP and make a backup.
5. In TWRP, flash the Crowlock bootloader unlocker zip
6. Wipe internal storage except for /sdcard
7. Flash the Padfone S firmware zip
8. Reboot and enjoy
Also, #9 and #10 don't have to be done. The firmware update zips that ASUS publishes are full system images, so you can just flash the newest one and be good to go. (but make sure to flash WW)
Click to expand...
Click to collapse
Simple and works!!! LL 5.0 in my Padfone X :highfive:
Easy as pie
xtermmin said:
Think it's because 7a and 8 should be switched around. You can't flash the Padfone S firmware on a Padfone X until you unlock the bootloader.
So basically, the steps:
1. Root
2. Install Flashify from the Play Store
3. Use Flashify to flash the Padfone X/S TWRP
4. Boot into TWRP and make a backup.
5. In TWRP, flash the Crowlock bootloader unlocker zip
6. Wipe internal storage except for /sdcard
7. Flash the Padfone S firmware zip
8. Reboot and enjoy
Also, #9 and #10 don't have to be done. The firmware update zips that ASUS publishes are full system images, so you can just flash the newest one and be good to go. (but make sure to flash WW)
Click to expand...
Click to collapse
Yeah this is exactly what I did, but in case of rooting (for some bizarre reason) the only method that worked for me was using Kingroot and then to purchase the app Super Sume Pro in order to get root access. After that I strictly followed the above procedure and now both devices are functioning flawlessly!!!
Big thanks to all doing the tutorials on the padfone x to s!
For the folks following this thread - any issues with band 17 like described in the other threads? I think the twrp.img link is not the one that allows restoring of EFS (Nexus5repack-A01) so just curious if anyone having issues with LTE or band 17 (if you care )?
I also received a software update from ATT recently - got excited it was finally Lollipop but it turned out to be updated built ATT_11.10.11.1. Anyone else get this, any issues converting / unlocking BL on this build before I plunge L)
Thanks again!
Phone: Padfone X
Build: ATT_11.10.11.1
Mods: TowelRootv1, TWRP (twrp_2.8.7.8_v5.img)
synergysemantics said:
Big thanks to all doing the tutorials on the padfone x to s!
For the folks following this thread - any issues with band 17 like described in the other threads? I think the twrp.img link is not the one that allows restoring of EFS (Nexus5repack-A01) so just curious if anyone having issues with LTE or band 17 (if you care )?
I also received a software update from ATT recently - got excited it was finally Lollipop but it turned out to be updated built ATT_11.10.11.1. Anyone else get this, any issues converting / unlocking BL on this build before I plunge L)
Thanks again!
Phone: Padfone X
Build: ATT_11.10.11.1
Mods: TowelRootv1, TWRP (twrp_2.8.7.8_v5.img)
Click to expand...
Click to collapse
Wow at&t pushed an update to this device, I thought that was the end of the suport due to this thing not selling much at all.
At&t will probably not update the Padfone x to lollipop as there are rumors that the Padfone X2 might be coming out around march.
I flash those different versions of twrp to keep my band 17 and for call settings to actually work.
With out that I cannot make my phone number show up on caller id, and call forwarding to work.
Using PFS Fw, This phone is incredibly stable and all of the features actually work despite doing that conversion.
Probably worried as to what could happen if Marshmallow gets pushed out for the S, would we still be able to use the firmware then? We'll see from there. Its probably better to go to CM13, once everything starts working. (its been improving, but not suitable for being a daily driver as some apps FC and tablet support almost works.)
As always you could check my guide, a bit longer, though its understandable and help you prevent losing Band 17 and call settings
youngson87 said:
So I realized that there wasn't much support out there for the padfone X. I love my padfone X regardless of its tiny battery, lack of developer support, and unpopularity. So I decided to embrace my love for tech and support the device myself.
So, Asus is still showing love to the padfone S(not X). That being the case it's the international version of the AT&T X; the hardware is almost identical. I decided to turn my X into an S, unlock the bootloader, upgrade to Android 5(I know its not the latest but it's better than 4.4.2), root and enjoy.
Breaking, bricking, whatever... This is all on you, this is what I did to my phone. I'm only sharing my experience. Make sure your phone is fully charged before you begin. Don't say I broke your phone, your taking a risk. I take no credit if this does or doesn't work. This process is time consuming and might not work for you. Don't blame me for wasted time.
This should give you carrier unlock as well.(not tested) and you should be able to use the Padstation with Lollipop. I'll leave download links below.
Steps
#1 back up all your data(titanium etc)
#2 download and run New Kingroot(took 5 tries to work)
#3 download and run superSume Pro
#3a step 3 should have installed SuperSU... Uninstall Kingroot & update SuperSU (use normal method); get a root checker and check root
#4 download a custom recovery(I personally like TWRP, but its buggy on this phone whatever) store the recovery.img on your phone's internal storage(not sd)
#5 install a flash tool(rashr or flashify will do) flash the custom recovery img.
#5a you should have root and custom recovery now, even if the bootloader is locked.
#6 The hard part. Put the S firmware on your internal storage(not sd card)
#7 in recovery mode you need to make another back up(back ups are awesome) do a factory reset in recovery(also wipe cache)
#7a install S firmware(do this in recovery mode) and restart phone. (Initial boot takes about 2 minutes). This might not work the first time(took 5 restores for me to finally get it)
Congratulations!!! You now have a "Padfone S"
#8 preferably using clockwork mod, install crowlock zip file by quarx to unlock bootloader
#9 to upgrade from 4.4.2 to 5.0 you need to go through about 4 updates from the Asus website. Follow this link(only use WW upgrades)
#10 after the upgrades you may have lost root. Just follow steps 2 and 3 again.
Asus "says" they will be releasing Android 6 for the Padphone S... Don't know how true that is, hope so. ENJOY!!!
Downloads and links
Kingroot:
http://www.appsandroidapk.com/tools/kingroot/
S firmware: thank you to tjsnooley!!!
http://forum.xda-developers.com/padfone-x/general/i-have-done-it-t3053207
TWRP/Cwm: thanks quarx!!!
http://quarx2k.ru/asus_padfone_s/recovery/
Crow Lock:
http://quarx2k.ru/asus_padfone_s/
Asus upgrades:
https://www.asus.com/support/Download/29/1/0/10/6vHIzvNAKBCV4v9w/32/
The superSume Pro costs money, you'll have to find it on your own, sorry...
Click to expand...
Click to collapse
Hello, thanks for you work, a have a question, the padstation work fine after change padfone x to padfone s firmware?
Regards.
i think i need help, in twrp i cant do wipe data cache dalvik, i try to do data factory reset from options, but after insert code, nothing... doesn't start.. i try to install a rom ww of padfone S, doesn't work.. T___T my internal storage is near to full and my telephone have stock icons and no other applications.. Any suggestions to do ?
colla.paolo said:
i think i need help, in twrp i cant do wipe data cache dalvik, i try to do data factory reset from options, but after insert code, nothing... doesn't start.. i try to install a rom ww of padfone S, doesn't work.. T___T my internal storage is near to full and my telephone have stock icons and no other applications.. Any suggestions to do ?
Click to expand...
Click to collapse
Hmmm Try it with a different recovery such as cwm, thats strange that twrp would not work. After boot into it and factory reset then flash cm12.1 just to make sure that the internal storage not full, then it will be best to install twrp afterwards to flash the padfone s firmware.
unable to mount cache, i cant clean
edit: i do wipe cache and system with cwm, now i have bootloop in cwm,
i try to install romname.zip ... system say, this is ASUS_T00N file, this is t00n.
Failed.
i try with ADB too, at 94% *failed to write data 'protocol fault p' * .
i try with the last firmware *failed to write data
i can't explore cellphone via usb, sd card can't readed.
im totally a noob.
i try to follow all steps, but nothing.
Thanks for brick my cellphone and now it's a totally useless.
thanks regards
colla.paolo said:
unable to mount cache, i cant clean
edit: i do wipe cache and system with cwm, now i have bootloop in cwm,
i try to install romname.zip ... system say, this is ASUS_T00N file, this is t00n.
Failed.
i try with ADB too, at 94% *failed to write data 'protocol fault p' * .
i try with the last firmware *failed to write data
i can't explore cellphone via usb, sd card can't readed.
im totally a noob.
i try to follow all steps, but nothing.
Thanks for brick my cellphone and now it's a totally useless.
thanks regards
Click to expand...
Click to collapse
I have never had luck with CWM on this phone, that is why I use TWRP.
If you still have difficulty mounting: From TWRP, go to wipe, advanced wipe, select the partition you are having difficulty with, tap Repair or Change File System, tap Repair. If that isn't successful, tap Change File System, then choose EXT4.
For the error: ASUS_T00N file, this is t00n
1. open the rom.zip, do not extract, just open.
2. Browse to \META-INF\com\google\android\ then open updater-script. Most people suggest to use a unix based text editor, but wordpad works fine for me.
3. Delete the first line containing: getprop("ro.product.device") == "ASUS_T00N" || abort("This package is for "ASUS_T00N" devices; this is a "" + getprop("ro.product.device") + "".");
4. Save and close. (this is the part where I have trouble with using Note++ or other unix based editor, I can't get it to save within a zip file. That is why I just use wordpad which i have never had issue with.)
5. Transfer to phone and flash.
6. Profit.
If that doesn't work, just use ADB sideload through TWRP.
1. From TWRP go to Advanced, ADB Sideload, tick checkboxes, swipe to Start Sideload. (Note, make sure phone is connected to PC.
2. From PC command prompt, run command ADB Devices to verify device is connected and detected as being in Sideload mode.
3. From PC command prompt, run command ADB Sideload filename.zip
Note: To make using ADB easier, I just drop the rom into the folder where adb.exe is located. From Windows explorer, CTRL+Shift+Right Click Folder containing ADB, click Open Command Window Here This way I don't have to do a bunch of CD commands or provide file path to ROM that I am using.
^ Follow his guide first ^
colla.paolo said:
unable to mount cache, i cant clean
edit: i do wipe cache and system with cwm, now i have bootloop in cwm,
i try to install romname.zip ... system say, this is ASUS_T00N file, this is t00n.
Failed.
i try with ADB too, at 94% *failed to write data 'protocol fault p' * .
i try with the last firmware *failed to write data
i can't explore cellphone via usb, sd card can't readed.
im totally a noob.
i try to follow all steps, but nothing.
Thanks for brick my cellphone and now it's a totally useless.
thanks regards
Click to expand...
Click to collapse
I assume that you did unlock the bootloader prior to that, but if not do that in cwm (if its still installed) since that works well by putting the file into the sd card.
Ok, but you were able to fix cache, I wouldn't say its bricked as you could just boot a different recovery through fastboot, so twrp is what you must use to flash the ww fw to the phone since cwm doesn't like that fw.
So put your phone to fastboot mode which is power and volume up at the same time, the logo should be frozen, which is good. Then put in the usb cable into the computer afterwards, and let the computer recogonize the device. If it does good, and thats when you need to get fastboot running on your computer and hope that the phone gets detected. If it does great.
The next step is putting the twrp recovery in a place that would be able to be activated from the computer, there are many tutorials how to get it to set up perfectly, but as long as the command you are about to put in should give you "cannot" locate file. Heres a nice guide: https://aubykhan.wordpress.com/2013...t-into-twrp-or-cwm-recovery-without-flashing/
The command is fastboot boot (then the file name).img and presto you got a recovery rolling for you to flash a rom on to the phone.
After flashing the fw the bootloader does get locked and the recovery will be replaced with stock so make sure to reflash the bootloader unlock through flashing the zip file and the twrp recovery file under img flash. (there should be an option there)
I've been there and that sucks but as long as you are careful and know what your'e doing I think you could get yourself out of that state where there is no rom installed.
The guy who posted above me does have the other solutions with the other errors if you run into them.
Good Luck
How to turn Padfone x to s
Am new at this How i can my Padfone x to s
King 242 said:
Am new at this How i can my Padfone x to s
Click to expand...
Click to collapse
Read the first page of this thread.
The basic steps:
0. Grab the following and throw them on your microSD card:
Latest Padfone S Worldwide (WW) firmware from ASUS: https://www.asus.com/support/Download/29/1/0/10/6vHIzvNAKBCV4v9w/32/
CrowLock: http://quarx2k.ru/asus_padfone_s/CrowLock_RC3.zip
TWRP Recovery: http://quarx2k.ru/asus_padfone_s/recovery/twrp_3.0.0.img1. Root (via Kingroot, Towelroot v1, whatever)
2. Install Flashify from the Play Store
3. Use Flashify to flash the TWRP recovery on your microSD card
4. Boot into TWRP recovery and make a backup.
5. In TWRP, flash the Crowlock bootloader unlocker zip
6. Wipe internal storage except for /sdcard
7. Flash the Padfone S firmware zip
8. System > Reboot > say yes to rooting the device. Enjoy.
This is for real, folks. The first working custom recovery for Asus ZenPad 8.0 Z380M and a method to flash it under a locked bootloader. This took quite a bit of work to make, partly due to having to find a way to bypass the locked bootloader. And because of a kernel configuration issue that limited the size of the initial ramdisk, which took some serious effort to weed out. @lss1977 helped to port it to this device. And of course, credits to TeamWin for TWRP.
In addition to this thread, the current Z300M/Z301M TWRP thread and the the old Z300M recovery/rooting thread may be helpful. These models share the same hardware and software base, so most things that apply to one tablet also apply to the other.
DISCLAIMER
As usual, you do anything described in this post at your own risk. No one but you is responsible for any data loss, bricking or damage of your device.
REQUIREMENTS
Windows PC
SP Flash Tool version 5.1532 (only this version will bypass security checks)*
MediaTek VCOM drivers (available through Windows Update)
Z380M scatter file, attached
Recovery image, attached
Z380M preloader file (optional), available inside the stock firmware download
ZenPad Z380M tablet upgraded to Android N
* If you prefer to use a more recent SP Flash Tool, check out the special image file below.
This won't be a guide on how to use SP Flash Tool. There are plenty of good guides out there like this one on how to set up drivers, load scatter files, flash and make backups with SP Flash Tool. If you're not familiar with this software or how to flash MediaTek devices in general, please do your research before attempting this. I will just get straight to the specifics about the ZenPad 8.
FIRST TIME INSTALLATION
For a locked bootloader:
At this point you should have your tablet powered off, the drivers installed, all of your data backed up, and SP Flash Tool v5.1532's Download tab open and loaded with the tablet's scatter file. Open the download agent file DA_PL.bin, replacing the default MTK_AllInOne_DA.bin. (You can use the AllInOne DA if you want, but the procedure involves extra steps as described below.) Load the extracted TWRP recovery image (twrp-3.2.1-0-z380m.img) under the recovery partition line in the partition table. Click the Download button inside SPFT. Now just connect the USB cable to your tablet and your computer's USB port. It should start the download process automatically and disconnect when finished.
Alternative Method:
If you're using MTK_AllInOne_DA.bin, you have to hold the Volume Up key as you insert the cable, which puts the device into an emergency download mode. In addition, you will need to have the stock preloader*.bin file loaded inside SPFT for it to be able to communicate with your tablet. The preloader is available inside the official zip file download. Do not flash the preloader (untick the box) or any partitions other than recovery. You just need to have a valid bin file selected under the Preloader line.
For an unlocked bootloader:
If you have used the Asus unlock tool to unlock your device, you will still not be able to use fastboot flash to install a custom recovery. However, you can do a "hot boot" or a tethered boot of TWRP. This method doesn't require SP Flash Tool. Download the TWRP image, put your tablet in fastboot mode and connect to PC. Then run this command to boot TWRP dynamically:
fastboot boot twrp-3.2.1-0-z380m.img
Once inside TWRP, flash twrp-3.2.1-0-z380m.img to Recovery using Install -> Install Image. Then reboot to recovery. You may be able to use TWRP in the tethered boot mode, but that could result in glitches due to different parameters passed by the bootloader to the kernel. That's why flashing is recommended.
To update from your installed TWRP version to a new one, just transfer the image to your tablet, then boot to TWRP and install it by going to Install -> Install Image and flashing to Recovery.
START RECOVERY
With the tablet powered off, hold the Volume Up and Power keys together until you get to a menu where you can select "recovery". Use Vol. Up to scroll and Vol. Dn to select. If you have a locked bootloader, it will show a Yellow State message because the recovery is not signed by the OEM. Just press volume up to boot it. On the welcome screen of TWRP it will ask you about modifying the system partition, I suggest you go with Keep System Read-only. Doing otherwise will complicate your OTA updates.
WARNING: Never start the stock recovery from the bootloader menu on this device. It is programmed by the bootloader to instantly wipe your data without any warning. Also, be aware that Android installs the stock recovery at every normal boot cycle. So you either have to flash the TWRP every time you want to run it, or disable the automatic recovery installation in the stock firmware. Any kind of mod to the boot image will prevent the automatic recovery installation. If you're not sure which recovery you have installed, you can always do a 'adb reboot recovery' from Android without risk of data loss.
What works: Basically everything... access to major partitions, decrypted userdata partition, decrypted adoptable storage, external SD card, ADB, USB-OTG, touch interface, splash screen, installing stock Asus OTA/web FW updates
What doesn't work: (no known problems yet, but please report any)
Not guaranteed to work: factory reset
DOWNLOAD
(Updated February 3, 2018: updated kernel to firmware 5.3.18; up-to-date TWRP 3.2.1 sources)
SP Flash Tool v5.1532
Z380M Scatter file for all storage sizes (right click, Save link as...)
Recovery image
Signed image for Flash Tool only -- may be flashed with recent SP Flash Tool versions -- DO NOT INSTALL USING ANY OTHER METHOD -- tested with SPFT 5.1736.
Development and experimental files
Source code
P.S. The thanks button doesn't bite.
Nice one now lets get some custom roms done.
Has anyone installed this yet? I see the file has been downloaded a few times. Any feedback is welcome.
If you want the recovery to stick after reboot either rename or remove system/bin/install_recovery.sh.
lss1977 said:
If you want the recovery to stick after reboot either rename or remove system/bin/install_recovery.sh.
Click to expand...
Click to collapse
The way I did it was to edit the init.rc file inside the boot ramdisk and comment out the service block that calls install_recovery.sh. I used the MTK boot image unpack/repack tools. I don't know, it seems like changing anything on the system partition will break OTA updates because of dm-verity. Because that depends on verifying each block of the file system. I have never even mounted the system as R/W in recovery.
how to create scater file from text posted? I copied all text to MT8163_Android_scatter.txt file but when open with splash tools give error "scatter file is invalid"
please atach your working scatter file to other atachments
PxYra said:
how to create scater file from text posted? I copied all text to MT8163_Android_scatter.txt file but when open with splash tools give error "scatter file is invalid"
please atach your working scatter file to other atachments
Click to expand...
Click to collapse
OK, I added the scatter file as a download. It was a pain in the ass to copy & paste. (But it did work.)
Problem fixed downloaded new version of flashtool 5.16 and scatter working
Ok I installed TWRP on Z380M P00A, and wanna say to other
1. Use VCOM drivers only from splash tool official site
2. To install VCOM drivers first need enter chinese recovery tablet, then in windows device manager you see USB device, install manualy drivers (don forget in windows disable driver signature)
3. Use only SP-Flash-Tool-v5.1532.00, newer or older version not properly working with this phone
Ok, thanks for the update, PxYra. Just to let you know, there are signed versions of VCOM drivers floating around so you don't need to mess with signature enforcement. Here's one: https://www.androidfilehost.com/?fid=24591000424943663. They are also updated by Windows so you can just let Windows Update install them.
Thanks for your work.
Flashing procedure works only with "MTK_AllInOne_DA.bin" method for me. But this is OK!
(Updated May 6, 2017: added kernel from firmware 5.3.7, source code cleanup)
Click to expand...
Click to collapse
is it possible to get the older versions? I need Android 6.x, because of xposed-Framework for my Zenpad 8.0 Z380M.
Greets Freisei
Hey freisei...
I never posted a version for Android 6. There was just one based on the 5.3.6 kernel, practically the same as the current one. That's why I didn't keep it. I could try to build one for you if you want, but I can't test it of course. Does this recovery not boot at all on the old firmware?
It's strange that the DA_PL.bin method didn't work for you. What happened when you tried it? I suppose the old preloader doesn't allow it(?).
hello guys, you think lineage os official version for asus z380kl (p024) will work on our z380m ?
---------- Post added at 08:19 PM ---------- Previous post was at 08:05 PM ----------
Can anyone help me? after selecting recovery img, pressing download and inserting usb cable, nothing happens. Thanks in advance
lss1977 said:
If you want the recovery to stick after reboot either rename or remove system/bin/install_recovery.sh.
Click to expand...
Click to collapse
hello friend, can you please upload that file? I deleted it, but now I need it to revert to official recovery, as my zenpad is bricked! It would be of great help! thanks!
Pires_7 said:
hello friend, can you please upload that file? I deleted it, but now I need it to revert to official recovery, as my zenpad is bricked! It would be of great help! thanks!
Click to expand...
Click to collapse
Your ZenPad didn't brick because you deleted install_recovery.sh. It's because you modified the system partition. Making any mods to system is bad advice unless you know exactly what you're doing. Even mounting it in r/w mode can break it. That's because dm-verity has tripped and is blocking access to changed blocks of the file system. So you have 3 options: mod your boot image fstab file to disable dm-verity, restore the original system image block-for-block (either from backup or official firmware converted to an img file), or wipe userdata (lss reported that to work).
Pires_7 said:
hello guys, you think lineage os official version for asus z380kl (p024) will work on our z380m ?
Click to expand...
Click to collapse
Nope, no chance.
diplomatic said:
Your ZenPad didn't brick because you deleted install_recovery.sh. It's because you modified the system partition. Making any mods to system is bad advice unless you know exactly what you're doing. Even mounting it in r/w mode can break it. That's because dm-verity has tripped and is blocking access to changed blocks of the file system. So you have 3 options: mod your boot image fstab file to disable dm-verity, restore the original system image block-for-block (either from backup or official firmware converted to an img file), or wipe userdata (lss reported that to work).
Nope, no chance.
Click to expand...
Click to collapse
Ok. I made some real s*it, I think I deleted every partition except recovery. Can you provide me a twrp backup or some way around my problem?
What do you mean you deleted every partition except recovery? There's like 28 partitions. You would have to work hard to accomplish that.
My first suggestion is to extract a system.img from the Asus stock firmware zip using this. Then flash it with SP Flash Tool. You might also try to install a full firmware zip from TWRP. Although I have no idea if that will work or if it's even safe to try.
diplomatic said:
What do you mean you deleted every partition except recovery? There's like 28 partitions. You would have to work hard to accomplish that.
My first suggestion is to extract a system.img from the Asus stock firmware zip using this. Then flash it with SP Flash Tool. You might also try to install a full firmware zip from TWRP. Although I have no idea if that will work or if it's even safe to try.
Click to expand...
Click to collapse
i was able to extract system.new.dat from stock firmware zip, but it extracts to a system folder. How do I flash this through sp flash tool?
OK, the system folder you don't need. It should have produced a system.img file also. That's the file you need to flash. Just select it for the system partition row in the partition list and then Download. Hopefully that will be enough.
EDIT: I just looked at the script, and realized the system.img.img file gets deleted in the process. So what you need to do is start the extraction, then after it makes system.img.img, when it starts extracting individual files, hit Ctrl+C. Then you'll end up with the img file.
Thank you very much! it works! YOU are the BEST!
please tell me, in your scatter file, address partition_name: frp (0x80a5000) is correct? if i format this partition (frp), google account remove?
This is basically a copy of my Z380M TWRP thread adopted for the ZenPad 10. I decided to start a new one since the OP of justshaun's original recovery/rooting thread has gone stale, even as I had posted several new releases of TWRP over the months. Its instructions are also a little outdated. I've also compiled a version for the new Z301M(F) models and needed a place to post it. This is where I will be posting TWRP updates from now on.
In addition to this thread, referring to the Z380M TWRP thread and the original Z300M thread (links above) may be helpful. These models share the same hardware and software base, so most things that apply to one tablet also apply to the others.
DISCLAIMER
As usual, you do anything described in this post at your own risk. No one but you is responsible for any data loss, bricking or damage of your device.
REQUIREMENTS
Windows or Linux PC
SP Flash Tool version 5.1532 (only this version will bypass security checks)
MediaTek VCOM drivers (available through Windows Update)
ZenPad 10 scatter file for SPFT, attached (choose the one for your tablet)
Recovery image, attached (choose the one for your tablet)
ZenPad Z300M, Z301M or Z301MF tablet upgraded to Android N
This won't be a guide on how to use SP Flash Tool. There are plenty of good guides out there like this one on how to set up drivers, load scatter files, flash and make backups with SP Flash Tool. If you're not familiar with this software or how to flash MediaTek devices in general, please do your research before attempting this. I will just get straight to the specifics about the ZenPad 10.
FIRST TIME INSTALLATION
For a locked bootloader:
At this point you should have your tablet powered off, the drivers installed, all of your data backed up, and SP Flash Tool v5.1532's Download tab open and loaded with the tablet's scatter file. Open the download agent file DA_PL.bin, replacing the default MTK_AllInOne_DA.bin. (You can use the AllInOne DA if you want, but the procedure involves extra steps as described below.) Load the extracted TWRP recovery image for your device (twrp-3.2.1-0-z30*m.img) under the recovery partition line in the partition table. Click the Download button inside SPFT. Now just connect the USB cable to your tablet and your computer's USB port. It should start the download process automatically and disconnect when finished.
Alternative Method:
If you're using MTK_AllInOne_DA.bin, you have to hold the Volume Up key as you insert the cable, which puts the device into an emergency download mode. In addition, you will need to have the stock preloader*.bin file loaded inside SPFT for it to be able to communicate with your tablet. The preloader is available inside the official zip file download. Do not flash the preloader (untick the box) or any partitions other than recovery. You just need to have a valid bin file selected under the Preloader line.
For an unlocked bootloader:
If you have used the Asus unlock tool to unlock your device, you will still not be able to use fastboot flash to install a custom recovery. However, you can do a "hot boot" or a tethered boot of TWRP. This method doesn't require SP Flash Tool. Download the TWRP image, put your tablet in fastboot mode and connect to PC. Then run this command to boot TWRP dynamically:
fastboot boot twrp-3.2.1-0-z30*m.img
Once inside TWRP, flash twrp-3.2.1-0-z30*m.img to Recovery using Install -> Install Image. Then reboot to recovery. You may be able to use TWRP in the tethered boot mode, but that could result in glitches due to different parameters passed by the bootloader to the kernel. That's why flashing is recommended.
To update from your installed TWRP version to a new one, just transfer the image to your tablet, then boot to TWRP and install it by going to Install -> Install Image and flashing to Recovery.
START RECOVERY
With the tablet powered off, hold the Volume Up and Power keys together until you get to a menu where you can select "recovery". On the Z301M/Z301MF, that option is labeled Factory Reset. Use Vol. Up to scroll and Vol. Dn to select. If you have a locked bootloader, it will show a Yellow State message because the recovery is not signed by the OEM. Just press volume up to boot it. On the welcome screen of TWRP it will ask you about modifying the system partition, I suggest you go with Keep System Read-only. Doing otherwise will complicate your OTA updates.
WARNING: Never start the stock recovery from the bootloader menu on this device. It is programmed by the bootloader to instantly wipe your data without any warning. Also, be aware that Android installs the stock recovery at every normal boot cycle. So you either have to flash the TWRP every time you want to run it, or disable the automatic recovery installation in the stock firmware. Any kind of mod to the boot image will prevent the automatic recovery installation. If you're not sure which recovery you have installed, you can always do a 'adb reboot recovery' from Android without risk of data loss.
WARNING 2: Make sure you use the correct scatter file for your device (i.e. don't mix up the Z300 and Z301 files). For the initial flash, there is no check for scatter file correctness. If you use the wrong one, SP Flash Tool will alter and lock your GPT to that scatter file layout, possibly bricking your device. It will not be easy to restore it. Flashing with the correct scatter file later on will not work because Flash Tool will not allow you to use a different file than the one you used initially.
What works: Basically everything... access to major partitions, decrypted userdata partition, decrypted adoptable storage, external SD card, ADB, USB-OTG, touch interface, splash screen, installing stock Asus OTA/web FW updates
What doesn't work: (no known problems yet, but please report any)
Not guaranteed to work: factory reset
DOWNLOAD
SP Flash Tool v5.1532
Z300M Scatter file for all storage sizes (right click, Save link as...) -- do not use for other models
Z300M TWRP 3.2.1-0 image -- updated March 15, 2018
Z301M(F) series Scatter file for all storage sizes (right click, Save link as...) -- do not use for Z300M or other devices
Z301M TWRP 3.2.1-0 image -- updated March 13, 2018
Z301MF TWRP 3.2.3-0 image -- updated August 29, 2018
Development and experimental files
Source code
P.S. The thanks button doesn't bite.
Heya, thanks for the new thread..
Stupid question(coming from Samsung flashing)
Ive got Zenpad S3 10 P027, is this TRWP not ideal for this?
Currently, have some su (root) issues. Recovery shows Android icon chest with ! and says "No Command"
When running su in Terminal ADB via PC, says command not recognized.
Looks like I need to reflash recovery. When in TRWP (launched via fastboot boot twrp on PC) I flashed stock recovery but had system mounted read only. Could that be the problem?
Bro, I think you need to do some more homework on root, su, dm-verity, mods, etc. and read the instructions more carefully before applying these hacks. You are making a lot of simple mistakes and ending up shooting yourself in the foot for it. I don't think there's anything wrong with the Z500 TWRP. It can handle installing the stock firmware just fine. The problem is elsewhere. The unlock tool also works fine in TWRP as well in my testing.
The No Command screen is normal. That's been answered many times... you need to hold power+vol. up (or down) to get to the menu. There is no way the stock recovery image can be broken and still boot up.
The su thing, IDK what the problem is, but I'm sure if you install Magisk Manager and make your own patched image from your currently installed firmware, and fastboot-boot with it, you will have su functionality. Just like what it says in the unlock tool instructions.
Lastly and most important, never mount system in read-write mode, as I've repeated several times and exactly as it says in the directions:
7. At the TWRP welcome screen, do not select to modify the system partition and touch Keep System Read-only instead. Doing otherwise will render your tablet unbootable.
8. Mount system in TWRP (in read-only mode)
Click to expand...
Click to collapse
The only time you can mount it in read-write mode is when you are absolutely sure you have disabled dm-verity in your boot image.
I've successfully installed TWRP on Z301M using the instructions from the first post, but then I somehow managed to lose the system. Yes, I should have backed up like the OP suggests.
I thought I should be able to reinstall the original firmware downloaded from Asus (e.g. UL-ASUS_P028_1-WW-3.3.12.0-user.zip) but both the 'adb sideload' method and the TWRP failed to install that firmware zip. My device looks bricked. The only thing I can do is to boot into TWRP (I actually need to select Factory Reset on the bootloader screen to get into TWRP). The folder 'system' is empty.
Can anyone suggest what I am doing wrong when trying to restore the Asus firmware?
When I try to sideload the zip, setting TWRP in the sideload mode, the computer begins uploading but after a few seconds gives the message "Total xfer: 0.01x" and stops, while Android errors with "set boot part fail. can not open misc-sd".
When I install the firmware zip from TWRP it also starts installing fine but shortly gives the same error "set boot part fail. can not open misc-sd".
Thanks
@ahacker, first of all, thank you for the feedback on the Z301M platform. You are literally the first person to have said anything about that version of TWRP.
To see the files on system, you first have to mount the system partition. Did you do that? If not, I suggest mounting it read-only. If there was any corruption on it, then reinstalling the firmware should have fixed it. The "misc-sd" errors are normal. Pretty sure they happen on stock recovery too. The stock firmware does not have dm-verity enabled, so letting TWRP modify system to prevent overwriting recovery should not have caused any problems.
At which point did it stop booting? Also, did you use the scatter file from first post? And can you tell me if the touch screen works fine in TWRP on your tablet?
I'm not sure what the deal is with adb sideload. I don't think I've ever actually tried it....
diplomatic, thanks for replying!
diplomatic said:
[MENTION=4776997]
To see the files on system, you first have to mount the system partition. Did you do that?
Click to expand...
Click to collapse
I do mount the system partition. It appears empty. When I reboot into system TWRP says that the OS is not installed.
I don't remember the details of how I lost the system partition. First time I entered into TWRP it asked for a password, probably to mount some partition. I pressed cancel or something. Then I might have cleaned the caches. But I am sure I haven't wiped system. I might have pressed Factory Reset somewhere, because I don't have any data yet on the new tablet.
I would indeed try to mount the system read only. This is not the first Android system I rooted (maybe fifth), and I was always able to restore the system either from sideload or recovery. But here it seems Asus is making us jump extra hoops to do that.
diplomatic said:
[MENTION=4776997]
Reinstalling the firmware should have fixed it.
Click to expand...
Click to collapse
That seems to be my main problem now. I cannot reinstall the Asus firmware. It may look like I might be installing a wrong version, but I am positive that I have Z301M tablet. This is what I bought and what the boot-loader says. I download Z301M firmware from the Asus website (e.g.). So it must be a correct firmware.
diplomatic said:
[MENTION=4776997]
The "misc-sd" errors are normal. Pretty sure they happen on stock recovery too. The stock firmware does not have dm-verity enabled, so letting TWRP modify system to prevent overwriting recovery should not have caused any problems.
Click to expand...
Click to collapse
Thank you for the information.
diplomatic said:
[MENTION=4776997]
Also, did you use the scatter file from first post? Does the touch screen work fine in TWRP on that tablet?
Click to expand...
Click to collapse
Yes. I found that to be the only scatter file that worked. I tried scatter.txt from the firmware zip, but the Flash Tool refuses tio pick it up. TWRP seems to be working fine with touches working as expected.
diplomatic said:
[MENTION=4776997]
I'm not sure what the deal is with adb sideload. I don't think I've ever actually tried it....
Click to expand...
Click to collapse
This is the unbricking method described here. It probably does the same thing as the "Install Zip" from recovery, because the errors that both methods give are the same.
---------- Post added at 01:19 AM ---------- Previous post was at 12:57 AM ----------
Now system refuses to mount
ahacker said:
I don't remember the details of how I lost the system partition. First time I entered into TWRP it asked for a password, probably to mount some partition. I pressed cancel or something. Then I might have cleaned the caches. But I am sure I haven't wiped system. I might have pressed Factory Reset somewhere, because I don't have any data yet on the new tablet.
Click to expand...
Click to collapse
Er, the password should have been for decrypting your userdata. If you didn't have one set up, there might be something wrong there.... Or possibly just unformatted.
ahacker said:
That seems to be my main problem now. I cannot reinstall the Asus firmware. It may look like I might be installing a wrong version, but I am positive that I have Z301M tablet. This is what I bought and what the boot-loader says. I download Z301M firmware from the Asus website (e.g.). So it must be a correct firmware.
Click to expand...
Click to collapse
Yeah, that has to be the right one. The installation script has to match the model name reported by the recovery. Otherwise it would simply abort.
ahacker said:
Yes. I found that to be the only scatter file that worked. I tried scatter.txt from the firmware zip, but the Flash Tool refuses tio pick it up. TWRP seems to be working fine with touches working as expected.
Click to expand...
Click to collapse
Great! Guess my kernel patch was on the dot and the partition layout has not changed from the Z300.
ahacker said:
This is the unbricking method described here. It probably does the same thing as the "Install Zip" from recovery, because the errors that both methods give are the same.
Click to expand...
Click to collapse
When you installed the zip, did you unmount system completely? BTW, when you mentioned the errors, the installation does keep going for like 5 to 10 minutes afterwards, right?
If you still can't resurrect it, please post or send me the recovery & kernel log that has your installation attempt.
diplomatic said:
When you installed the zip, did you unmount system completely? BTW, when you mentioned the errors, the installation does keep going for like 5 to 10 minutes afterwards, right?
Click to expand...
Click to collapse
I've tried both ways, with and without system mounted, a few times. The installation would fail after something like 5 seconds.
diplomatic said:
If you still can't resurrect it, please post or send me the recovery & kernel log that has your installation attempt.
Click to expand...
Click to collapse
I think I am giving up on this cheap tablet. I cannot even format it in the Flash Tool: it says "To format code area is forbidden on this phone". Asus is forbidding too much for me to ever buy it again. Attached the logs.
Thanks, diplomatic
OK, found the problem. Check your PMs, ahacker.
diplomatic said:
OK, found the problem. Check your PMs, ahacker.
Click to expand...
Click to collapse
I have replied (twice), but the reply does not appear in my Sent Items. I hope it has reached you. If not, I'll paste the reply here, if you don't mind.
i not understand... i have Asus ZenPad 10 LTE Z301MFL.. a root method has been released ???
@diplomatic
Would this be compatible with Z0310M ? can't find anything for this damn model...
Hi, NeBouse,
Are you sure you have the correct information? It looks like just a misspelling of Z301M, aka P028....
I have z301m.
One thing that was a surprise for me is that the TWRP recovery flashed with the method described in the original post does not stick. You have to flash it each time you use it. If you are like me this information is important, because the original recovery plainly wipes your data without asking or warning.
After you have flashed TWRP on the device, to go to the recovery mode you have to chose "Factory Reset" in the bootloader. Then it will complain about wrong OS, which is the sign that flashing TWRP worked; choose 'yes'. The first thing you should do in TWRP is a ful nandroid backup. (Not listening the OP's advice about backing up when Installing TWRP with a wrong scatter file almost cost me the device. Thankfully diplomatic managed to remotely fix my problem, probably spending a lot of his personal time. The scatter file in the original post is a correct one now.)
Creating a nandroid backup in TWRP takes unusually long time, I even once decided that it hanged. Taking long time, like 10-30 minutes, for a full backup is normal.
Asus Z300M , Magisk 16.3 (beta) and FW 5.3.19 WW now works!
z301m, WW-3.3.12.0 firmware
For rooting I've installed in TWRP Magisk v15.3 (diplomatic warned against 16.x, someone else against 15.4) - link.
Installed in TWRP xPosed framework 88.2 - link, and xPosed Installer apk from within Android - link.
So far, so good.
What I've found is that TWRP seems to have problems with external sd cards (lots of fs corruption). I found it safer to unmount by hand by unticking the sd card checkbox in "Mount". Not very conclusive about this though.
Thanks, ahacker. Good feedback. Although to be fair, I didn't say to avoid Magisk 16.x. I said 16.0. I'm pretty sure whatever bug it had is already fixed in the latest version.
Now that you've installed root, TWRP will stick around on the emmc. The stock recovery only gets installed if you have the original unpatched boot image on it. I mean, this is not unique to these devices. That's been standard Android functionality since some 4.x or 5.x version. And this is essentially what's in the warning on the OP.
The backup I'm talking about in the installation method is done with the SP Flash Tool readback function. That will pull the partition tables and your device's "metadata" that's unique to your unit. I don't think nandroid covers that...
Oh, and what is this SD corruption you're talking about? What file system is it formatted in? Have you checked your card for errors in Windows?
Asus releases so many difference Z301M model, so I am curious if this also works on Z301MF model?
Notice Z300MF has the MTK8163BA (or MTK8163A?) CPU model while Z301M uses : 8163B
Anyone tested that already? Thanks.
my zenpad 10 has frp lock. it this a solution to remove the frp lock?
Pls help how i flash original software via fastboot ?????
Hi, I've just bought a Cubot P50, it's a Chinese brand and seems more than decent for the price, I've rooted it with Magisk and I want to install TWRP on it but can't find anything for that brand. Has anyone came across a TWRP that might work on it?
Marko Lyno said:
Hi, I've just bought a Cubot P50, it's a Chinese brand and seems more than decent for the price, I've rooted it with Magisk and I want to install TWRP on it but can't find anything for that brand. Has anyone came across a TWRP that might work on it?
Click to expand...
Click to collapse
I have the same phone how did you root it ? If there a guide that is safe to use ? Thank you
Unlock the bootloader first, this step will factory reset your phone https://romprovider.com/unlock-bootloader-android/
On your PC:
1. Install Fastboot driver
2. Install MediaTek_Preloader_USB_VCOM_Drivers_Setup_Signed
3. Extract platform-tools
4. On your phone, Enable Developer Options, USB debugging and OEM Unlocking
5. Unlock bootloader (this step will factory reset your phone): Phone in fastboot mode, open command prompt on PC > fastboot devices > fastboot flashing unlock. Note this will cause the phone to show the "Orange State" warning on boot up. You can ignore this or remove it later.
(If device is unauthorised in ADB or Fastboot, go to Developer Options on phone, revoke USB debugging authorisation, disable then enable USB debugging. You should now get an authorisation confirmation dialogue when you try to connect with ADB/Fastboot. If not, type "adb kill-server", then "adb devices" or "adb start-server" in the command prompt).
6. Place boot.img on phone with USB file transfer (either from stock ROM, or read from phone using SP_Flash_Tool_v5.1924_Win) and patch it with Magisk v5.2. NO need to patch vbmeta.img
7. Transfer patched boot.img back to PC
8. Flash the patched boot.img to phone either with SP Flash Tool or Fastboot command in ADB (fastboot flash boot boot.img). Take care here, make sure it's the right image going to the right location and that ALL other files are de-selected, especially the preloader file, always de-select this when flashing any firmware unless you know what you're doing!
Phone is now rooted.
How to remove orange state warning on this device:
How to remove Orange, Yellow & Red state warnings on MTK
This guide will explain how to hide or remove Yellow, Red and Orange state warnings on a Mediatek Android device. Its ideal for those who feel irritated by constantly seeing these warnings on reboot.
www.hovatek.com
Edit: If you need a stock ROM for the phone it's here https://www.cubot.net/Support/id/78/cid/19.html#hh
Good evening, I would like to know if in the future it is possible to install a twrp with a custom rom?
Thank you have a nice day.
Good evening, I would like to know if in the future it is possible to install a twrp with a custom rom on the Cubot p50?
Thank you have a nice day.
Mark8:9 said:
Good evening, I would like to know if in the future it is possible to install a twrp with a custom rom on the Cubot p50?
Thank you have a nice day.
Click to expand...
Click to collapse
It is possible that in the future, developers may create custom ROMs and TWRP recoveries for the device, especially if it becomes popular among the Android community.
If a custom ROM and TWRP recovery becomes available for your device in the future, you will be able to flash it by following the instructions provided by the developer. Keep in mind that installing custom ROMs and recoveries comes with some risks, and it is important to backup your data and follow the instructions carefully to avoid damaging your device.
Good evening, can you tell me the correct procedure for how to Root the Cubot p50 smartphone? Thank you.
Mark8:9 said:
Good evening, can you tell me the correct procedure for how to Root the Cubot p50 smartphone? Thank you.
Click to expand...
Click to collapse
Well if you really want to know that, surely you would have read the entire thread? It's not that long. I gave complete instructions 5 posts up
Marko Lyno said:
Well if you really want to know that, surely you would have read the entire thread? It's not that long. I gave complete instructions 5 posts up
Click to expand...
Click to collapse
Good evening, be patient ... but where do I find Magisk 5.2 to download and how do I install it? Thanks good evening.
Download Magisk Manager Latest Version 26.1 For Android 2023
Magisk Manager is an app which helps users to root their phone. With the help of Magisk you can run banking apps and also pass SafetyNet tests.
magiskmanager.com
Just get the latest version and follow the instructions I posted.
Thanks for your work on the Cubot phone .Im a fan of them also. I found that twrp recovery 3.40 works on the Note 20/20Pro you just have to flash vbmeta BEFORE and AFTER you flash twrp to the device. Im also seeing separate websites claiming twrp 3.40 is also used with the Cubot P40 model. I dont see why it wouldnt work with the P50. Its worth a shot. Also theres alot more "familiars" with Mediatek phones like these in Hovatek forum. Since you already have information on how to root maybe consider starting your own P50 thread over there.
My references: https://www.hovatek.com/forum/thread-44810-post-233457.html#pid233457
elimoviebuff said:
Thanks for your work on the Cubot phone .Im a fan of them also. I found that twrp recovery 3.40 works on the Note 20/20Pro you just have to flash vbmeta BEFORE and AFTER you flash twrp to the device. Im also seeing separate websites claiming twrp 3.40 is also used with the Cubot P40 model. I dont see why it wouldnt work with the P50. Its worth a shot. Also theres alot more "familiars" with Mediatek phones like these in Hovatek forum. Since you already have information on how to root maybe consider starting your own P50 thread over there.
My references: https://www.hovatek.com/forum/thread-44810-post-233457.html#pid233457
Click to expand...
Click to collapse
Thanks for that. Is there a specific vbmeta to patch it with?
Good evening, can you give me the link to download a compatible cust recovery for the cubot p50? Thank you
The link is on the page just posted above. Here's the direct link to the file:
Hovatek
Download files
www.hovatek.com
Let us know if it works please, and what steps you took.
Good evening, how will I flash the lk file? Thanks.
Hi, you will have, or should have, downloaded a zip file containing a recovery.img. The recovery.img is the file you need to flash. Then follow the instructions here:
How to Install TWRP Recovery on Any Android 2022 [100% Working]
In this article, I will be showing you how you can install TWRP recovery on any Android smartphone. By following this guide you will be able to install
magiskapp.com
The TWRP Recovery file it refers to is the one you (hopefully) downloaded from this link:
Hovatek
Download files
www.hovatek.com
BUT, you also need to flash a vbmeta file BEFORE and AFTER the recovery.img, and I'm still unsure which vbmeta file it is, as elimoviebuff hasn't replied to my question regarding that.
Marko Lyno said:
Hi, you will have, or should have, downloaded a zip file containing a recovery.img. The recovery.img is the file you need to flash. Then follow the instructions here:
How to Install TWRP Recovery on Any Android 2022 [100% Working]
In this article, I will be showing you how you can install TWRP recovery on any Android smartphone. By following this guide you will be able to install
magiskapp.com
The TWRP Recovery file it refers to is the one you (hopefully) downloaded from this link:
Hovatek
Download files
www.hovatek.com
BUT, you also need to flash a vbmeta file BEFORE and AFTER the recovery.img, and I'm still unsure which vbmeta file it is, as elimoviebuff hasn't replied to my question regarding that.
Click to expand...
Click to collapse
I get it, but I have to flash the .bin to remove the yellow/red state on boot. I don't know how to install the lk.bin file. If you can help me. Thank you.
Ah I see, you're rooting the phone first. Ok I've just checked my own notes on this, so, if you have edited the lk.img file as described in that Hovatek thread, then do as follows:
When flashing with SP Flash Tool, make sure the correct lk.img file is chosen as SP Flash Tool chooses lk-verified.img by default (click along to the right of the file list under "Location" and choose your edited lk.img file here).
OR, flash with ADB (fastboot flash lk lk.img).
Then install Magisk on your phone if you haven't already.
boot.img is for rooting the phone, lk.img is only to remove the orange state message and the 5 second delay when the phone boots, it does not actually remove it's orange state and is not needed for the phone to be rooted.
To un-root, you should just flash the original boot.img and lk-verified.img from the stock firmware ROM file.
Marko Lyno said:
Ah I see, you're rooting the phone first. Ok I've just checked my own notes on this, so, if you have edited the lk.img file as described in that Hovatek thread, then do as follows:
When flashing with SP Flash Tool, make sure the correct lk.img file is chosen as SP Flash Tool chooses lk-verified.img by default (click along to the right of the file list under "Location" and choose your edited lk.img file here).
OR, flash with ADB (fastboot flash lk lk.img).
Then install Magisk on your phone if you haven't already.
boot.img is for rooting the phone, lk.img is only to remove the orange state message and the 5 second delay when the phone boots, it does not actually remove it's orange state and is not needed for the phone to be rooted.
To un-root, you should just flash the original boot.img and lk-verified.img from the stock firmware ROM file.
Click to expand...
Click to collapse
Good morning. Thank you for the information given.
I wanted to ask: is it necessary or useful to install an antivirus on your smartphone now that it's been rooted? Thank you.
I haven't but that's just down to personal choice really. It's certainly useful if you like to try stuff from unknown sources, although personally I've rarely encountered viruses on Android. I'm not saying they don't exist though.
Have you successfully rooted your phone then? What about TWRP, have you tried that yet?