Related
hey guys since jerpelea has already got the custom kernels working, it will just be a matter of time before we see custom ROMs...
i am making this thread so as to answer the many questions that users are having on how to get back to stock when testing custom kernels / custom roms...
[--> WARNING <--]
PLEASE READ THE COMPLETE POST (1ST & 2ND) BEFORE U DO ANYTHING
I AM NOT RESPONSIBLE IF UR DEVICE GETS BRICKED BECAUSE U DID NOT READ THE WHOLE THING PROPERLY / U HAD SOME TYPO WHILE EXECUTING THE COMMANDS
MAKE SURE THAT UR PHONE BATTERY IS FAIRLY CHARGED (> 50%) BEFORE DOING ANY FLASHING AND THAT UR PC HAS A UPS BACKUP (BECAUSE IF FLASHING IS INTERRUPTED THEN IT CAN HAVE SERIOUS CONSEQUENCES)
[ BEFORE U BEGIN ]
Requirements:
Flashtool (it is advisable to use latest version)
Fastboot files
Stock Firmware FTF package
[OPTIONAL] PreRooted system.img files
7zip
How to use FlashTool:
FLASHTOOL GUIDE - HOW TO for n00bies
this was posted in X10 section but is even relevant for Arc/Play/Neo users
How to use FastBoot:
[Newbie Guide] adb/fastboot/bootloader/android 101
[ FLASHING CUSTOM KERNEL/ROM ]
Flashing Custom Kernel (boot.img):
this WILL NOT WIPE ur data
the custom kernel will be provided as boot.img file
just copy this file to fastboot folder
just power down device and get into FASTBOOT MODE (LED notification turns BLUE) with usb-cable connected to PC
once u are in fastboot mode open command prompt and navigate to the folder containing fastboot files then just use the following command to flash custom kernel:
Code:
fastboot flash boot boot.img
once flashing is complete you will get a prompt on pc saying that everything is ok
now just unplug ur device and u are on the custom kernel
Flashing Custom ROM/SYSTEM (system.img):
this WILL NOT WIPE ur data, it will only wipe ur /system partition
the custom ROM/system will be provided as system.img file
just copy this file to fastboot folder
just power down device and get into FASTBOOT MODE (LED notification turns BLUE) with usb-cable connected to PC
once u are in fastboot mode open command prompt and navigate to the folder containing fastboot files then just use the following command to flash custom ROM/system:
Code:
fastboot flash system system.img
once flashing is complete you will get a prompt on pc saying that everything is ok
now just unplug ur device and u on custom rom/system
[ GET BACK TO STOCK ]
jerpelea has posted an unbrick (softbrick) package in the FreeXperia project thread... details on how to use it can be found in Post #2 of this thread...
Following is much more generic information which can be applicable to any FW/ROM/Kernel
How to get back to Stock Firmware (FW):
this will get u back to COMPLETE STOCK SETTINGS
ALL ur data WILL BE WIPED
u will get back to stock kernel
u will get back to stock ROM/system
ur SDCARD data WILL NOT BE affected
you will need stock FTF package
get ur device into FLASH MODE (LED notification turns Green)
use flashtool to flash stock FTF package
for details refer to the above FlashTool guide
How to get back to Stock Kernel (boot.img / kernel.sin):
this WILL NOT WIPE ur data
using 7zip extract the FTF package to some directory
you will get many files with extension .sin
we are interested in the kernel.sin file, which is the stock kernel
just copy this file to fastboot folder
now for getting back to stock kernel just power down device and get into FASTBOOT MODE (LED notification turns BLUE) with usb-cable connected to PC
once u are in fastboot mode open command prompt and navigate to the folder containing fastboot files then just use the following command to flash stock kernel:
Code:
fastboot flash boot kernel.sin
once flashing is complete you will get a prompt on pc saying that everything is ok
now just unplug ur device and u are back to stock kernel
How to get back to Stock ROM (system.img / system.sin):
OPTION - 1 : stock unrooted system
this WILL NOT WIPE ur data, it will only wipe ur /system partition
using 7zip extract the FTF package to some directory
you will get many files with extension .sin
we are interested in the system.sin file, which is the stock rom/system
just copy this file to fastboot folder
now for getting back to stock system/ROM just power down device and get into FASTBOOT MODE (LED notification turns BLUE) with usb-cable connected to PC
once u are in fastboot mode open command prompt and navigate to the folder containing fastboot files then just use the following command to flash stock ROM/system:
Code:
fastboot flash system system.sin
once flashing is complete you will get a prompt on pc saying that everything is ok
now just unplug ur device and u are back to stock rom/system
OPTION - 2 : stock PreRooted system
this WILL NOT WIPE ur data, it will only wipe ur /system partition
use the prerooted system.img u downloaded from above links
just copy this file to fastboot folder
now for getting back to stock prerooted system/ROM just power down device and get into FASTBOOT MODE (LED notification turns BLUE) with usb-cable connected to PC
once u are in fastboot mode open command prompt and navigate to the folder containing fastboot files then just use the following command to flash stock ROM/system:
Code:
fastboot flash system system.img
once flashing is complete you will get a prompt on pc saying that everything is ok
now just unplug ur device and u are back to stock rom/system
[ TROUBLESHOOTING ]
sometimes u may run into problems after flashing back from custom system.img to stock system.img, like apps & core system crashes/force closes
if u face such problems then it is advisable to WIPE ur /data parition
this WILL WIPE ur data (apps, settings), ur SDCARD DATA WONT BE AFFECTED
just power down device and get into FASTBOOT MODE (LED notification turns BLUE) with usb-cable connected to PC
once u are in fastboot mode open command prompt and navigate to the folder containing fastboot files then just use the following command to wipe /data partition:
Code:
fastboot erase userdata
once flashing is complete you will get a prompt on pc saying that everything is ok
now just unplug ur device and the problems should be sorted out
if u still are facing problems just flash back to Stock Firmware using FLASHTOOL
[ FINAL THOUGHTS ]
I hope this answers most of ur questions...
in case of specific queries about flashtool/fastboot or prerooted images ask in THOSE SPECIFIC threads... if u have any queries other than that [RELATED TO THIS THREAD ] u can post ur questions here...
PLEASE DONT FILL UP DEV THREADS WILL REDUNDANT QUESTIONS
jerpelea has posted an unbrick (softbrick) package in the FreeXperia project thread...
here is how to use it to get back to stock!
Requirements:
Fastboot drivers already installed
unbrick (softbrick) package
7zip
How to get back to Stock Kernel & system:
this WILL WIPE ur data
using 7zip extract the unbrick (softbrick) package to some directory
now for getting back to stock kernel & ROM just power down device and get into FASTBOOT MODE (LED notification turns BLUE) with usb-cable connected to PC
once u are in fastboot mode just browse to the folder where u extracted the unbrick package double click on restoreme.cmd
once flashing is complete you will get a prompt on pc saying that everything is ok (or the command prompt window might just close in some time dont worry its expected)
ur device will now restart automatically
now just unplug ur device and u are back to stock kernel & ROM
Nice thread Mate ... I'm sure this be most useful
i just saw that jerpelea has posted an unbrick (softbrick) package...
i am downloading it now and will updated the info as per the files present in that package...
EDIT:
how to updated...
info on how to use the package updated in 2nd post
nice thread thanks for it gonna try this later this week
Man, what an amount of text, thanks for your efforts to get everything organized this well. Will try as soon as we have any reliable material to work with.
Sent from my arc or optimus 2x
Wow! Cool post man. Kudos
Nice thread man, thank you!!!
I have two questions.
1. How can I modify or create a custom boot.img (from kernel.sin)?
2. How can I create/compress a new system.img back from extracted system.sin (with sin2img tool)
If anyone want to share his knowledge please pm me!
Thanks for the guide!
I'm just wondering. In X10's XRecovery, there is a Backup and a Restore function. The Backup function practically saves the entire ROM including data. One can then proceed to flash custom ROMs/kernels. In the event that we want to revert back to the original ROM including data, we just have to use the Restore function.
Does any of the above methods achieve the same result?
hush66 said:
Thanks for the guide!
I'm just wondering. In X10's XRecovery, there is a Backup and a Restore function. The Backup function practically saves the entire ROM including data. One can then proceed to flash custom ROMs/kernels. In the event that we want to revert back to the original ROM including data, we just have to use the Restore function.
Does any of the above methods achieve the same result?
Click to expand...
Click to collapse
those are called NANDROID backups can be created using working RECOVERY...
no the above methods can ONLY WRITE to device... they cant take backups...
found this thread and it helped me a lot thanks for it works like a charm, flashed custom kernel and back to stock without losing my data
guys quick question here
i'm currently using rooted genericsg ROM
and i wanted to try J's CM7 beta005. i downloaded his files, saw boot.img and system.img, so i need to just fastboot those two files?
Rycon33 said:
guys quick question here
i'm currently using rooted genericsg ROM
and i wanted to try J's CM7 beta005. i downloaded his files, saw boot.img and system.img, so i need to just fastboot those two files?
Click to expand...
Click to collapse
yes
BUT be very careful as to which partition to flash it to...
DooMLoRD said:
yes
BUT be very careful as to which partition to flash it to...
Click to expand...
Click to collapse
thanks for the quick answer man, i'll give the beta a try
oh another thing, doest it matter which i fastboot first, boot or system image?
Rycon33 said:
thanks for the quick answer man, i'll give the beta a try
oh another thing, doest it matter which i fastboot first, boot or system image?
Click to expand...
Click to collapse
nope... shouldn't matter...
Thanks
Tried the beta 006 and it's looping on bootanimation only. Flashing of boot and system image went fine, I wonder what else could be wrong.
So i had flashedback to stock rom again for now.
- Sent from my Sony Arc
Rycon33 said:
Thanks
Tried the beta 006 and it's looping on bootanimation only. Flashing of boot and system image went fine, I wonder what else could be wrong.
So i had flashedback to stock rom again for now.
- Sent from my Sony Arc
Click to expand...
Click to collapse
please post the results of ROM tests in relevant threads so that the DEV of the the rom can track the issues/problem...
Should we have an unlocked hollowed in order to flash these kernels/roms ???
Sent from my LT15a using XDA App
Bootloader I mean lol
Sent from my LT15a using XDA App
PAVNEET101 said:
Bootloader I mean lol
Sent from my LT15a using XDA App
Click to expand...
Click to collapse
yes
u need unlocked bootloader to flash boot.img
Hi guys,
I have xperia sp, where I had a newest firmware installed. I decided to mod it to newest cyanogenmod (android 7.1).
Using night build, install boot.img and using adb install rest of system. Forgot to install gapps, but system ran smoothly.
So i decided to install cyanogen once again, following these steps:
1. fastboot - flash boot.img
2. system clean - wipe /system, /data, /cache (wipe all available from recovery menu)
3. Trying to upload system using adb, by selecting on recovery menu "sideload". ADB failed - mot recognise device
4. Upload system (cyanogenmod) to sd card and trying to update from recovery menu
5. SD card is fully visible, but when trying to update got an error: "E: unable to find /misc partition" (!!!)
6. 3,4,5 I tried many time, unsuccessful
7. Decided to downgrade to original firmware using flashtool.
8. All files *.sin uploaded successfully, except system.sin (size above 1GB)
9. Trying to upload system.sin manually using fastboot, but got the error "(file too large)
Now I have original boot, but phone is locked on "SONY" screen
I need any advice, how to upgrade phone to any system.
btw, I tried all available stock firmwares (254, 205, etc)
best regards
M.
Dunno and not sure but it doesn't cost nothing to try:
with fastboot flash kernel from 7.1 zip package and also flash twrp 3
then try to enter twrp recovery (VOL+ when lights up)
Don't use the latest version of flashtool and use version 0.9.18.6 instead to flash stock firmware
http://www.flashtool.net/downloads.php
Sent from my Xperia SP using Tapatalk
Thanks.,
it helps Previous version of flashtool did it correctly.
Now I have new question related to CM:
after sucessful installation of CM, I back to recovery
1. Copy OpenGAPPS to sdcard
2. Initiate aplly update from sdcard
3. Installation started but
4. Got an error "E: failed to map file"
tried different versions of OpenGAPPS (pino, nano, micro) with the same result.
Should I use recovery image from cyanogenmod?
And next, when I tried to execute:
fastboot flash recovery twrp.img
got an error:
(bootloader) Flash of partition 'recovery' requested
FAILED (remote: Partition not found)
I need to install open gapps.
best regards
M.M.
Ok, I fixed it
Installed TWRM recovery and install gapps finally.
Thanks for help
Hi guys,
I tried to root my P9 today but now I'stuck with a bricked P9.
I can fastboot and use TWRP
The main problem is that I get always failed to mount /data (Invalid argument)
I've tried to Change the file system with TWRP and Format Data but nothing
I've tried the unbrick procedure with Multi-Tool and an old firmware but nothing
Code:
19:21:37: Unbricking started. Your computer may freezes during the process.
19:21:37: flash boot "C:\Users\franc\Desktop\Nuova cartella\boot.img"
19:21:37: The Boot image is flashing successfully
19:21:37: flash system "C:\Users\franc\Desktop\Nuova cartella\system.img"
19:21:53: target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (449861 KB)...
OKAY [ 10.490s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 10.551s
19:21:53: Error#1
19:21:53: flash cust "C:\Users\franc\Desktop\Nuova cartella\cust.img"
19:21:58: Error! You are trying to flash the wrong image!
19:21:58: flash recovery "C:\Users\franc\Desktop\Nuova cartella\recovery.img"
19:22:00: The Recovery image is flashing successfully
19:22:00: Completed
19:22:00: Something went wrong (((
bomba697 said:
Hi guys,
I tried to root my P9 today but now I'stuck with a bricked P9.
I can fastboot and use TWRP
The main problem is that I get always failed to mount /data (Invalid argument)
I've tried to Change the file system with TWRP and Format Data but nothing
I've tried the unbrick procedure with Multi-Tool and an old firmware but nothing
Code:
19:21:37: Unbricking started. Your computer may freezes during the process.
19:21:37: flash boot "C:\Users\franc\Desktop\Nuova cartella\boot.img"
19:21:37: The Boot image is flashing successfully
19:21:37: flash system "C:\Users\franc\Desktop\Nuova cartella\system.img"
19:21:53: target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (449861 KB)...
OKAY [ 10.490s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 10.551s
19:21:53: Error#1
19:21:53: flash cust "C:\Users\franc\Desktop\Nuova cartella\cust.img"
19:21:58: Error! You are trying to flash the wrong image!
19:21:58: flash recovery "C:\Users\franc\Desktop\Nuova cartella\recovery.img"
19:22:00: The Recovery image is flashing successfully
19:22:00: Completed
19:22:00: Something went wrong (((
Click to expand...
Click to collapse
"P9" - EMUI 4 / Android MM, EMUI 5 / N or EMUI 8 / O
What was exacrly your full firmware name and number (like EVA-L09c532b505 or what)
"TWRP" - which/where from?
(diff TWRP installations must be used for MM, N or N), and if TWRP from TWRP site - that one is definitely not good for N and O
"root" - by SuperSU, Magisk or something else (hopefully not King.... tools or so)
So, from which Huawei firmware did you start, which steps did you perform and by which tools
Btw, rooting N by SuperSU or O by Magisk is pretty straightforward, but is important that proper, corresponding TWRPs are used.
And if anything goes wrong (brick or so) stock Boot partition (N) or stock Ramdisk partition (O) can be easily flashed over to go back
zgfg said:
"P9" - EMUI 4 / Android MM, EMUI 5 / N or EMUI 8 / O
What was exacrly your full firmware name and number (like EVA-L09c532b505 or what)
"TWRP" - which/where from?
(diff TWRP builds must be used for MM, N or N), and if TWRP from TWRP site - that one is definitely not good for N and O
"root" - by SuperSU, Magisk or something else (hopefully not King.... tools or so)
So, from which Huawei firmware did you start which steps did you perform and by which tools
Btw, rooting N by SuperSU or M by Magisk is pretty straightforward, but it is important that proper corresponding TWRPs are used.
And if anything goes wrong (brick or so) stock Boot partition (N) or stock Ramdisk partition (O) can be easily flashed over to go back
Click to expand...
Click to collapse
I'm sorry for the poor description but I was in panic.
Starting from EVA-L09C432B3xx, don't remember the exact version, N 5.0.1
TWRP 3.1.0.-1
SuperSU, https://forum.xda-developers.com/p9/development/root-supersu-2-81-emui-5-t3612258. I had big trouble trying to root because every time the phone rebooted before finishing the procedure.
I didn't use any tool at all for unlocking bootloader, flash recovery and root. Just adb and fastboot in cmd + TWRP.
BTW, I recovered the phone! Used DC-Phoenix to reset the phone from fastboot and then made a downgrade to b182.
PS: Why did you flash Cust?
For TWRP or to go back to stock Recovery, you only need to flash recovery (for N) or ramdisk_recovery (for O)
To flash root patch for SuperSU for N (or to restore back) you only need to flash boot partition, similarly for Magisk (O) ramdisk partution.
zgfg said:
PS: Why did you flash Cust?
For TWRP or to go back to stock Recovery, you only need to flash recovery (for N) or ramdisk_recovery (for O)
To flash root patch for SuperSU for N (or to restore back) you only need to flash boot partition, similarly for Magisk (O) ramdisk partution.
Click to expand...
Click to collapse
Because Multi-Tool 8 was asking to flash also CUST to apply unbrik procedure.
The problem was that I wasn't able to mount /data partition. Also from stock recovery I wasn't able to format /data, only wipe the cache
bomba697 said:
Because Multi-Tool 8 was asking to flash also CUST to apply unbrik procedure.
The problem was that I wasn't able to mount /data partition. Also from stock recovery I wasn't able to format /data, only wipe the cache
Click to expand...
Click to collapse
If you recovered and if you are on b182 now, you will hopefully receive OTA upgrades tp go back to N
Btw, working procedure for rooting N was described in thread
https://forum.xda-developers.com/p9/development/root-supersu-2-81-emui-5-t3612258
Again, if TWRP was not able to mount Data, was it really proper TWRP from XDA Huawei Nougat threads (adapred to support Huawei N and its encryption), like
https://forum.xda-developers.com/p9/development/twrp-t3565703
Some other TWRP 3.1.x.x, even declared for Huawei, maybe good for EMUI 4 / MM but not for EMUI 5 / N
EDIT: noticed that you fixed it through DC-Phoenix. Do you have a link where you found it and how to use? I don't mind downgrading coz I'm just gonna use the phone as a backup phone
I got the same issue. If you find an answer please tag me. I think i was using EVA-L19C636B180 Quite sure about the C636 part. TWRP 3.1.0.-3 and using SU but I can't recall the version
Quick background on mine:
I bricked my phone when I did a factory reset and deleted internal storage and accidentally deleted important files while doing so. I flashed a stock update from the warehouse and completely deleted the system instead. I then flashed Lineage ROM which reinstalled the system but now causes me to get stuck in bootup. When I installed Lineage ROM, I got the following error.
Attached photo
https://imgur.com/a/nx6U5bC
kazshizka said:
EDIT: ...DC-Phoenix. Do you have a link and how to use...
Click to expand...
Click to collapse
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
kazshizka said:
EDIT: noticed that you fixed it through DC-Phoenix. Do you have a link where you found it and how to use? I don't mind downgrading coz I'm just gonna use the phone as a backup phone
I got the same issue. If you find an answer please tag me. I think i was using EVA-L19C636B180 Quite sure about the C636 part. TWRP 3.1.0.-3 and using SU but I can't recall the version
Quick background on mine:
I bricked my phone when I did a factory reset and deleted internal storage and accidentally deleted important files while doing so. I flashed a stock update from the warehouse and completely deleted the system instead. I then flashed Lineage ROM which reinstalled the system but now causes me to get stuck in bootup. When I installed Lineage ROM, I got the following error.
Attached photo
https://imgur.com/a/nx6U5bC
Click to expand...
Click to collapse
I didn't use the method posted by @zgfg. What I did was: (this procedure is going to lock back your FRP setting and bootloader, so you can try it but at your own risk)
Use Multi-Tool 8 (https://forum.xda-developers.com/honor-8/development/tool-huawei-multi-tool-team-mt-t3523923) to reinstall stock recovery and recovery2
Download https://www.dc-unlocker.com/downloads/get/jvObBBIo
Put the phone in fastboot
Use the FRP Erase option to recover/format /data (it cost you 15 credit, $15), it was successful
Take empty SD card formatted in NFTS
Put in dload folder the rollback UPDATE.APP file taken from http://download-c1.huawei.com/download/downloadCenter?downloadId=92765&siteCode=it and install it
Last, put in dload folder b182 UPDATE.APP file from http://download-c1.huawei.com/download/downloadCenter?downloadId=91783&siteCode=it
This functioned for me, you can try to skip step 5 and install directly b182.
zgfg said:
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
Click to expand...
Click to collapse
bomba697 said:
I didn't use the method posted by @zgfg. What I did was: (this procedure is going to lock back your FRP setting and bootloader, so you can try it but at your own risk)
Use Multi-Tool 8 (https://forum.xda-developers.com/honor-8/development/tool-huawei-multi-tool-team-mt-t3523923) to reinstall stock recovery and recovery2
Download https://www.dc-unlocker.com/downloads/get/jvObBBIo
Put the phone in fastboot
Use the FRP Erase option to recover/format /data (it cost you 15 credit, $15), it was successful
Take empty SD card formatted in NFTS
Put in dload folder the rollback UPDATE.APP file taken from http://download-c1.huawei.com/download/downloadCenter?downloadId=92765&siteCode=it and install it
Last, put in dload folder b182 UPDATE.APP file from http://download-c1.huawei.com/download/downloadCenter?downloadId=91783&siteCode=it
This functioned for me, you can try to skip step 5 and install directly b182.
Click to expand...
Click to collapse
Will check out both methods. I'll try it through TWRP first since it should be easier to use an open bootloader rather than a locked one.
@bomba697 will reinstalling stock recovery fix my deleted system issue? coz I'm not sure if I flashed the custom ROM properly anymore
UPDATE:
Tried @bomba697 method and fixed my system but I skipped the FRP Erase portion. I just installed the stock recovery straight (thus not paying 15 credits) from the multi tool then rollback using dload then update to b182. Though it did change my system to C900 from C636.
Thank you very very much!!
kazshizka said:
UPDATE:
Tried @bomba697 method and fixed my system but I skipped the FRP Erase portion. I just installed the stock recovery straight (thus not paying 15 credits) from the multi tool then rollback using dload then update to b182. Though it did change my system to C900 from C636.
Thank you very very much!!
Click to expand...
Click to collapse
Happy that you found the solution! I tried directly flashing the rom but I wasn't able beacuse of the \data mount error.
Hello
I try to install a custom recovery on my tf701 (android 4.3, USB debug ON)
here are the previous steps i did :
1/ i have unlock the bootloader using ASUS tools : OK
2/ i have root the TF701 : OK
for this, I installed Minimal ADB and Fastboot
I copy the files found here
and I lauch the command : adb reboot bootloader
then : fastboot boot zImage_dtb ramfs.img.gz
the root is ok
-------------------------------------------------------------------
3/ i try to install recovery
i download the file here : droidbasement.com/asus/tf701t/recovery/
i put the file in the folder of Minimal ADB and Fastboot
and i launch the commande : adb reboot bootloader
then, when the fasboot usb mode is ready on the device : fastboot flash recovery recovery.img
first time :
target reported max download size of 64382
sending 'recovery' (6652 KB)...
FAILED (data write failure (Unknown error)
finished. total time: 5.050s
second time :
target didn't report max-download-size
sending 'recovery' (6652 KB)...
FAILED (remote: (Timeout))
finished. total time: 2.010s
Can you help me please ? I add that, when the device is ON in a normal mode (not fastboot) and connected to the PC with USB, the adb driver interface are ok :
"
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
* daemon not running; starting now at tcp:5037
* daemon started successfully
E1OKCY174091 device
"
i have tried to plug on other usb port ... it's the same ...
i have tried to reboot my computer : ... it's the same ...
i have tried to download another version of adp/fasboot (platform-tools_r28.0.2-windows.zip) : it's the same
without this installation, I can't install a custom rom ..
Many thanks in advance !
There are only two working recoveries for the TF701, one CWM without touch interface which I don't quite trust and a pretty good TWRP with touch here https://www.google.com/amp/s/forum....-kang-twrp-tf700t-2-8-x-xarea51-t3121989/amp/
The one you have there is probably the stock recovery...
The Kang TWRP is a little buggy though. You may come to a point where TWRP tells you it cannot mount /system or any other partition for that matter. All you have to do is convert the file system on /system to ext2, then convert it right back to ext4 and proceed with rom installation.
Good luck!
Sent from my Pixel 2 using Tapatalk
Hello berndblb
Many thanks for your help
The recovery I try to install is Recovery v6.0.4.6 CWM 11.
Which one is the easier to install for a beginner ?
Because what you said previously seems difficult for me ("convert the file system on /system to ext2, then convert it right back to ext4 and proceed with rom installation.")
Can you explain me how to do ?
Recovery v6.0.4.6 CWM 11 or Kang TWRP : can i install then the Rom "
ROM][N 7.1.2] [ KatKiss - Nougatella #037 ] for asus tf701
?
Many thanks in advance
They are equally easy to install since you just flash both of them in fastboot
But if you are asking which is easier to use, then it is the Kang TWRP. CWM does not have the drivers for the touch interface and you have to navigate everything with the vol buttons. More importantly I do not trust the "format data" function in CWM and that is crucial to install a custom rom. The issue with the corrupt file system in the Kang TWRP is a minor nuisance and you fix it right in TWRP. If you get the "cannot mount....." error, you just go to Wipe > Advanced > Change or repair file system, check the System partition and convert it to ext3 (or ext2 - does not matter). Swipe the button and when it is done (less than a minute) you repeat the step and change it back to ext4. After that everything should be good. If you want to read more about this issue search the Katkiss thread for "cannot mount"
Actually, there is another custom recovery out there which I have not tried and cannot vouch for. But maybe you go for that one, it does not seem to have the same issue and is based on a later version of TWRP: https://forum.xda-developers.com/tr...lopment/recovery-twrp-3-2-1-x-tf701t-t3720912
Read the thread, it seems to work fine. The Kang TWRP is 2.8, that one is based on 3.2.1 - both are fine to flash a Katkiss rom.
You do know that you have to fully format /data before you can flash a custom rom, right? You do that in your custom recovery (in TWRP: Wipe>Format Data, swipe the button). TWRP does a secure erase which wipes and trims every block. That's why this formatting takes around 60 minutes. Do not interrupt it!! CWM does not have this functionality, another reason I prefer TWRP..
hello berndblb and all helpers !
i have installed the Kang TWRP: it's ok
then I copy the custom rom KatKit for TF701 on /sdcard
i do a full wipe : error : "cannot mount..." : so I convert to ext2 and then I convert to ext4 the partition System and data
then i do a full wipe
my problem ... i'm sure you find it : i have erased all my data on /sdcard. No kitkat.zip yet !! :crying::crying::crying:
how to copy the rom on my tablet ?
for your information, when I am in TWRP, i can do "adb devices" on my computer :
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
15C4110C61C00000009FB01C0 recovery
But push commande is failed
C:\Program Files (x86)\Minimal ADB and Fastboot>adb push KatKiss.zip /sdcard/
adb: error: failed to copy 'KatKiss.zip' to '/sdcard/KatKiss.zip': no response:
Connection reset by peer
i put kitkat.zip on a USB Key and I plug it on my docks : it seems not be recognized ...
i 'm really lost
please help !!
Put the Rom on a microSD, mate. You can navigate in TWRP to the card and flash from there
Sent from my Pixel 2 using Tapatalk
Hello !!
I have nevers seen the microsd port ! I discover it 2 days ago !
Just before your answer, a 'adb push' was successfull ! I don't know why, and the next 'adb push' for gapps ans supersu were unsuccessful...it's strange !
But all IS ok now !
I have just a last 2 questions :
1/ next Time, where Can i copy the rom (.Zip) , somewhere it will not be deleted ?
2/my tablet is not rooted now ... Is the way to root depends on the Rom ?
If I follow the steps i did when my tf701 has the rom stock, IS still good ? (https://forum.xda-developers.com/showthread.php?t=2516215)
Thanks for your help !
1) the safest place is a microSD. You can flash the Rom straight from there. But as long as you do not format your data partition - and you only need to to that if you install a different rom - you can keep it on internal storage. In most cases you only need to wipe /data, not format, and that leaves /data /media where your files live, untouched.
2) First the question is: Do you need root? You should only root your rom for a good reason. If you are not sure if you need root - you don't.
Cyber threats are multiplying. You're safer if the tablet is not rooted.
That said: you can root by just flashing the zip in recovery.
BTW, if you did not flash gapps yet, you always should flash it together with the rom, not separate. To install gapps now flash the rom, then gapps, then root (if needed), reboot
Sent from my Pixel 2 using Tapatalk
Hi, I'm writing this to guide those who faced - and will face similar situation in the future - the problem of being stuck on the fastboot screen, where the recovery or booting in EDL is not available.
So, after failing to get root after upgrading to android 10 I was fiddling with TWRP to try to get it to recognize my storage so I can reflash it and flash Magisk, but I couldn't get it to mount the storage, so my stupid brain decided to go to the wipe page and wiped everything in the hope it might magically work!! well.. it didn't!! and I got stuck in the fastboot screen and I thought that I bricked my phone for good.
after hours of searching online and trying everything nothing helped... but finally I managed to fix it.
and btw when I tried to flash TWRP by (fasboot boot twrp.img) I got the following message:
"remote: Failed to load/authenticate boot image: Load Error"
So here is what I did to get my phone working again:
Download and install Tool All in One
Download Fastboot ROM for your phone from here
In the Tool All in One app click on the Flash Factory Images button.
Select the ROM and let it do its work,
hopefully this will work and your device will reboot into a fresh android.
Also it's good to know that the official TWRP of twrp.me does not support Android Q at the moment, that's why you couldn't decrypt and mount the storage. TWRP in Oneplus 7 Pro thread here on XDA does support Q, you just have to remember to boot into the inactive/upgraded slot before booting back to TWRP to flash Magisk as it only installs to the active slot and not the upgraded slot.
Skickat från min GM1913 via Tapatalk
vegatr0n said:
Hi, I'm writing this to guide those who faced - and will face similar situation in the future - the problem of being stuck on the fastboot screen, where the recovery or booting in EDL is not available.
So, after failing to get root after upgrading to android 10 I was fiddling with TWRP to try to get it to recognize my storage so I can reflash it and flash Magisk, but I couldn't get it to mount the storage, so my stupid brain decided to go to the wipe page and wiped everything in the hope it might magically work!! well.. it didn't!! and I got stuck in the fastboot screen and I thought that I bricked my phone for good.
after hours of searching online and trying everything nothing helped... but finally I managed to fix it.
and btw when I tried to flash TWRP by (fasboot boot twrp.img) I got the following message:
"remote: Failed to load/authenticate boot image: Load Error"
So here is what I did to get my phone working again:
Download and install Tool All in One
Download Fastboot ROM for your phone from here
In the Tool All in One app click on the Flash Factory Images button.
Select the ROM and let it do its work,
hopefully this will work and your device will reboot into a fresh android.
Click to expand...
Click to collapse
Or just use the MSM tool. Job done
All with varying levels of interpretation, steps, descriptions, and the solution. Not all are useful.
I had the same issue and this worked perfectly to get my device up and running again. Thanks again!!
Hi all!
Here is plan B!
First of all - BEFORE you do some upgrade - make OPSwitch backup and copy to PC !!!!!
If you stuck - it's mean that something is badly damaged and wrong. Some of the files reside in the areas where upgrade tools (including Fastboot!) can't change and repair them.
We don't have time, knowledge to sort out WHAT was damaged.
We make all straight from beginning:
1. MSM tools - make your phone like from the Factory with "clean" install (ver 9 for now)
2. "FlashAll" то ver 10E
3. If you need - install "global"
4. If you need - install TWRP and Magisk
5. Restore your backup from PC
At the end you will have "clean" phone with all programs working
EASY!!!
Same as OP, I wanted to flash twrp.img.
I had my OP7Pro stuck in 'fastboot mode', I thought. It wouldn't respond to any commands from console (device not found) and I couldn't turn it off with the power button any more.
For noobs, just like me, I learned that I just had to press the powerbutton + volume up button. My phone rebooted after this.
Now making a backup before rooting and such, phew.
vegatr0n
I was stuck in Fastboot after switching slots. Excelent stuf! 2,3 clicks , done! Thank you!
vegatr0n said:
Hi, I'm writing this to guide those who faced - and will face similar situation in the future - the problem of being stuck on the fastboot screen, where the recovery or booting in EDL is not available.
So, after failing to get root after upgrading to android 10 I was fiddling with TWRP to try to get it to recognize my storage so I can reflash it and flash Magisk, but I couldn't get it to mount the storage, so my stupid brain decided to go to the wipe page and wiped everything in the hope it might magically work!! well.. it didn't!! and I got stuck in the fastboot screen and I thought that I bricked my phone for good.
after hours of searching online and trying everything nothing helped... but finally I managed to fix it.
and btw when I tried to flash TWRP by (fasboot boot twrp.img) I got the following message:
"remote: Failed to load/authenticate boot image: Load Error"
So here is what I did to get my phone working again:
Download and install Tool All in One
Download Fastboot ROM for your phone from here
In the Tool All in One app click on the Flash Factory Images button.
Select the ROM and let it do its work,
hopefully this will work and your device will reboot into a fresh android.
Click to expand...
Click to collapse
Many people have found this problem. Thank you, I am working again.
i am not even able to flash the twrp in android 10 always getting stuck at fastbootlogo after flashing the recovery cmd
nitinvaid said:
i am not even able to flash the twrp in android 10 always getting stuck at fastbootlogo after flashing the recovery cmd
Click to expand...
Click to collapse
Then you have to use the MSM unbrick tool:
https://forum.xda-developers.com/oneplus-7-pro/how-to/op7pro-collection-unbrick-tools-t3956595/amp/
vegatr0n said:
Then you have to use the MSM unbrick tool:
https://forum.xda-developers.com/oneplus-7-pro/how-to/op7pro-collection-unbrick-tools-t3956595/amp/
Click to expand...
Click to collapse
Nope...
I was able to reboot holding both vol+ and - and power
I bricked my tmobile oneplus 7 pro and dont know which file is safe to try can anyone please point me in the right direction?
I already tried the steps using the tool and downloading the FASTBOOK os file and I get this error
"CreateProcess failed: %1 is not a valid Win32 application. (193)
fastboot: error: Cannot generate image for userdata"
Tried booting the device but boots to OOS recovery always.
---------- Post added at 11:54 PM ---------- Previous post was at 11:21 PM ----------
vegatr0n said:
Hi, I'm writing this to guide those who faced - and will face similar situation in the future - the problem of being stuck on the fastboot screen, where the recovery or booting in EDL is not available.
So, after failing to get root after upgrading to android 10 I was fiddling with TWRP to try to get it to recognize my storage so I can reflash it and flash Magisk, but I couldn't get it to mount the storage, so my stupid brain decided to go to the wipe page and wiped everything in the hope it might magically work!! well.. it didn't!! and I got stuck in the fastboot screen and I thought that I bricked my phone for good.
after hours of searching online and trying everything nothing helped... but finally I managed to fix it.
and btw when I tried to flash TWRP by (fasboot boot twrp.img) I got the following message:
"remote: Failed to load/authenticate boot image: Load Error"
So here is what I did to get my phone working again:
Download and install Tool All in One
Download Fastboot ROM for your phone from here
In the Tool All in One app click on the Flash Factory Images button.
Select the ROM and let it do its work,
hopefully this will work and your device will reboot into a fresh android.
Click to expand...
Click to collapse
I am getting the error
"Erasing 'userdata' OKAY [ 0.243s]
CreateProcess failed: %1 is not a valid Win32 application. (193)
fastboot: error: Cannot generate image for userdata"
I dont know how to proceed with this :crying:
moonbosques said:
I already tried the steps using the tool and downloading the FASTBOOK os file and I get this error
"CreateProcess failed: %1 is not a valid Win32 application. (193)
fastboot: error: Cannot generate image for userdata"
Tried booting the device but boots to OOS recovery always.
---------- Post added at 11:54 PM ---------- Previous post was at 11:21 PM ----------
I am getting the error
"Erasing 'userdata' OKAY [ 0.243s]
CreateProcess failed: %1 is not a valid Win32 application. (193)
fastboot: error: Cannot generate image for userdata"
I dont know how to proceed with this :crying:
Click to expand...
Click to collapse
Sounds like you're having problems with Windows Defender. I also got the same error messages suddenly once week ago. I did sfc /scannow and all that but all files were intact. After rebooting the PC two times the problem was gone, really strange.
Skickat från min GM1913 via Tapatalk
Anyone here know what fastboot rom i can use to fix my bricked tmobile oneplus 7 pro?
Can you explain this strange effect, please
pitrus- said:
Also it's good to know that the official TWRP of twrp.me does not support Android Q at the moment, that's why you couldn't decrypt and mount the storage. TWRP in Oneplus 7 Pro thread here on XDA does support Q, you just have to remember to boot into the inactive/upgraded slot before booting back to TWRP to flash Magisk as it only installs to the active slot and not the upgraded slot.
Skickat från min GM1913 via Tapatalk
Click to expand...
Click to collapse
After an update to Android Q twrp an root was lost.
I was going the normal way like this:
1. In fastboot boot twrp.img
2. In twrp install twrp.zip
3. Reboot to twrp
4. In twrp install magisk.zip
After this the phone stuck a while on this orange splash screen and then reboot to bootloader.
Reboot --> the same effect
Then:
1. Boot into twrp
2. install twrp.zip
3. Reboot system
Everything ok, but no root
Just one method is working for me:
1. Download the full package of OOS 10.x.x
2. Extract the boot.img
3. Patch boot.img with Magisk
4. Flash on fastboot boot magisk_patched.img
5. reboot
My phone is rooted now but without twrp.
Why can twrp an Magisk not work together?
And why I can´t find any information for this problem on the internet?
Well, since TWRP lives in the boot partition on this phone, you will have to boot TWRP using fastboot boot TWRP. Then you flash the unofficial TWRP build 74 installer zip downloaded from the link below (the one from twrp.me only works on OOS 9 and not 10). Reboot phone back into Magisk to switch slot, flash Magisk installer zip which will then install Magisk to both boot slot a and boot slot b. Reboot phone and you should have both Magisk root and working TWRP.
https://r.tapatalk.com/shareLink/to...2&share_fid=3793&share_type=t&link_source=app
Skickat från min GM1913 via Tapatalk
Fails anyway
Bricked my OnePlus and now I'm left with bootloader (no os, no twrp). Everything leads back to bootloader. Any attempts to apply fastboot boot lead to "Load Error". Now I tried with that tool and ended up with this:
Sending 'odm' (102400 KB) OKAY [ 2.576s]
Writing 'odm' FAILED (remote: '(odb_b) No such partition')
fastboot: error: Command failed
Press any key to exit...
P.S. Full log:
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........: e434a4c8
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
android-info.txt syntax error: я╗┐require product=msmnile
Setting current slot to 'b' OKAY [ 0.002s]
extracting boot.img (96 MB) to disk... took 0.776s
archive does not contain 'boot.sig'
Sending 'boot_b' (98304 KB) OKAY [ 2.389s]
Writing 'boot_b' OKAY [ 0.406s]
extracting dtbo.img (16 MB) to disk... took 0.151s
archive does not contain 'dtbo.sig'
Sending 'dtbo' (16384 KB) OKAY [ 0.393s]
Writing 'dtbo' OKAY [ 0.047s]
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta' (8 KB) OKAY [ 0.008s]
Writing 'vbmeta' OKAY [ 0.002s]
archive does not contain 'vbmeta_system.img'
archive does not contain 'super_empty.img'
archive does not contain 'boot_other.img'
extracting odm.img (100 MB) to disk... took 0.395s
archive does not contain 'odm.sig'
Sending 'odm' (102400 KB) OKAY [ 2.576s]
Writing 'odm' FAILED (remote: '(odm_b) No such partition')
fastboot: error: Command failed
Press any key to exit...
I am getting this error, any ideas what is going wrong? (please see attachment)
vegatr0n said:
Hi, I'm writing this to guide those who faced - and will face similar situation in the future - the problem of being stuck on the fastboot screen, where the recovery or booting in EDL is not available.
So, after failing to get root after upgrading to android 10 I was fiddling with TWRP to try to get it to recognize my storage so I can reflash it and flash Magisk, but I couldn't get it to mount the storage, so my stupid brain decided to go to the wipe page and wiped everything in the hope it might magically work!! well.. it didn't!! and I got stuck in the fastboot screen and I thought that I bricked my phone for good.
after hours of searching online and trying everything nothing helped... but finally I managed to fix it.
and btw when I tried to flash TWRP by (fasboot boot twrp.img) I got the following message:
"remote: Failed to load/authenticate boot image: Load Error"
So here is what I did to get my phone working again:
Download and install Tool All in One
Download Fastboot ROM for your phone from here
In the Tool All in One app click on the Flash Factory Images button.
Select the ROM and let it do its work,
hopefully this will work and your device will reboot into a fresh android.
Click to expand...
Click to collapse