So you've bricked your phone. Well as long as the boot loader works then your "brick" is just a soft-brick. Follow this simple guide and flash a custom rom in a couple of minutes. I am not claiming ownership of this method, but its the first time Ive seen it and it helped me so here Good Luck!
Download the attachments.
Unzip both files to a folder on your desktop.
Run the adb setup file and press (Y) all 3 times.
Next unzip the twrp.zip folder. Then flash the twrp recovery by using the "fastboot flash recovery twrp.img" command. Make sure phone is in fastboot mode.
Next boot the phone into the recovery and select advanced. Then click on terminal command and navigate to the /sdcard/ folder.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Lastly click "select" on the bottom right corner.
Now download whatever rom and gapps you would like to install on your phone and rename them to something short. Then open a command prompt at the directory where the rom and gapps are. In the command prompt enter these commands "adb push NAMEOFROM.zip /sdcard/" and "adb push NAMEOFGAPPS.zip /sdcard/".
The command prompt will not show change for a few minutes. After you notice the command prompt is ready for the next command it is okay to exit it.
Now just flash the rom and gapps normally and hopefully your phone will be okay.
Need any additional help? Feel free to ask This should work on all Moto G models that have a TWRP image and have a bootloader unlocked.
eg0097 said:
So you've bricked your phone. Well as long as the boot loader works then your "brick" is just a soft-brick. Follow this simple guide and flash a custom rom in a couple of minutes. I am not claiming ownership of this method, but its the first time Ive seen it and it helped me so here Good Luck!
Download the attachments.
Unzip both files to a folder on your desktop.
Run the adb setup file and press (Y) all 3 times.
Next unzip the twrp.zip folder. Then flash the twrp recovery by using the "fastboot flash recovery twrp.img" command. Make sure phone is in fastboot mode.
Next boot the phone into the recovery and select advanced. Then click on terminal command and navigate to the /sdcard/ folder. Lastly click "select" on the bottom right corner.
Now download whatever rom and gapps you would like to install on your phone and rename them to something short. Then open a command prompt at the directory where the rom and gapps are. In the command prompt enter these commands "adb push NAMEOFROM.zip /sdcard/" and "adb push NAMEOFGAPPS.zip /sdcard/".
The command prompt will not show change for a few minutes. After you notice the command prompt is ready for the next command it is okay to exit it.
Now just flash the rom and gapps normally and hopefully your phone will be okay.
Need any additional help? Feel free to ask This should work on all Moto G models that have a TWRP image and have a bootloader unlocked.
Click to expand...
Click to collapse
Everything went well till step 5.
In terminal window of phone i could find select..... but after that how to proceed I donot know.......... what commands should i use on TWRP terminal...........
Phone didn't get detected in ADB even in TWRP terminal
pl. help
subodhverma21 said:
Everything went well till step 5.
In terminal window of phone i could find select..... but after that how to proceed I donot know.......... what commands should i use on TWRP terminal...........
Phone didn't get detected in ADB even in TWRP terminal
pl. help
Click to expand...
Click to collapse
TWRP termnal is just so that your phone will connect as adb to your pc.
eg0097 said:
TWRP termnal is just so that your phone will connect as adb to your pc.
Click to expand...
Click to collapse
my problem got resolved.........
actually driver was the only problem which was not allowing ADB to detect device in RECOVERY mode, though device was detected in FASTBOOT mode
So I reinstall the driver to get ADB Interface installed in system> device manager
and then followed your remaining steps i.e. 6 onwards
Thanks a lot.....
Not really sure about the following, but I hard-bricked my phone while rooting it a few days ago. Black screen, phone wasn't visible in ADB / fastboot, LED didn't change after plugging in the charger etc.
The only thing that helped: holding the power button for at least 2 minutes. The device restarted afterwards w/o any issues.
Can't find the source of it anymore ...
Very useful guide, I revived my soft - bricked Moto G
still not working
on my xt1032 moto g 16gb version I just have the warning screen that the bootloader is unlocked.
followed a lot threads but nothing helped till now.
tried your verswion and from point 1 to 7 all went well.
But I can't flash the rom. i've tried out about 6 various rom's but everything it says fail. on the screen in the twrp always stands unable to mount /data /system /storage
what can I do to fix this problem?
sascha-1102 said:
on my xt1032 moto g 16gb version I just have the warning screen that the bootloader is unlocked.
followed a lot threads but nothing helped till now.
tried your verswion and from point 1 to 7 all went well.
But I can't flash the rom. i've tried out about 6 various rom's but everything it says fail. on the screen in the twrp always stands unable to mount /data /system /storage
what can I do to fix this problem?
Click to expand...
Click to collapse
|Could someone help please? I am in the same boat and when try to run the above command, I also get this error and no file appears in the sdcard hence cant flash it.
Thanks
My Moto G is working again since one week with stock 4.4.2. I had to do it ain a bit different way...
First, I could get into bootloader and recovery. after several hours my pc recognizes my phone again, but till now I don't know why and how.
Wanted to reflash stock 4.4.2 kitkat again, but this won#t work. so I figured out that after unpacking, I had to replace the gpt.bin with the one from the 4.4.4 stock update. (see down as zip file)
Then I flashed the 4.4.2 stock again to my phone and all went well. It started again. (now I'm on stock recovery)
If you want to do the OTA 4.4.4 Update, there have to be a few things on your phone, otherwise update always fails.
1. if you have x-posed frameworks installed - uninstall it completely
2. if rooted, go into super su preferences and activate unroot all
3. do not activate developper options, or if done before, just uncheck the mark
4. you must be on stock recovery!
5. restart your phone
6. now search after update in about phone.
if bootloader is unlocked - doesn't matter - can stay unlocked
with me it first installed the 176.* OTA because my flashed stock was still 175.*
this went well, then again searched for update and 210.* (4.4.4 kitkat) could be downloaded ota. after it was done, click to install and it should work well - took a bit time.
now you are on stock 4.4.4, but without root atm.
if you want root back - now flash the newest twpr recovery 2.7.7.1 to phone, because here an OTG USB stick will be also recognized - OTG cable needed before. (don't need to push files first to phone)
copied before the su.zip to usb stick and sticked it to phone, then go into recovery. here you can install super user or better su.zip. restart phone and you got your root back on 4.4.4 stock kitkat rom
I solved this issue with twrp sideload.It worked great.
Thanks it worked for me..BUT !!!
Hi and thanks a lot.. it worked for me but you have to add some more option for who are still having troubled in unbricking. like i had..
but it can't be done without your method as on OP..
how i got bricked !!! my Moto g dual (indian)
i tried to downgrade from 4.4.4 to 4.4.2 to flash custom Rom and got system partition corrupt.
again i tried to flash stock images but no use, actual problem was System and data was not formatting.
even if you try million times and you can never successfully flash stock images without error..
however i was checking many threads in xda to resolve this problem but couldn't figured it out, as i was not new to XDA i had confidence that i can come out from this issue. until this thread gave me a hint but not a solution but still this thread is a part of the solution
let come to the unbricking method (only for those who cant flash Stock firmware from fastboot)
Reboot to fastboot..
flash Philz recovery first. get it from here.. http://forum.xda-developers.com/showthread.php?t=2639626
better to use Kernel Flasher by my old buddy Ghostfreak NB http://forum.xda-developers.com/showthread.php?t=2214724,
you just need to extract and copy the recovery to extracted kernel Kernel_Flashing_Tool_v2.0 in IMG folder and run kernel Kernel_Flashing_Tool_v2.0.bat.
press 1 and it will flash recovery, press enter it will reboot to Philz recovery,
now format System, data and whatever you can!!\
next reboot to Bootloader from Recovery,
and then follow procedure as OP
if you want to flash stock rom get from here http://forum.xda-developers.com/moto-g/development/4-4-3-moto-g-stock-rom-t2804891 and adb push as advise by OP. now you have stock rom running without any issues
Edit..
You can also flash custom ROMs with ease.
Note you better flash recovery through kernel flasher tool..
Ysharief said:
Hi and thanks a lot.. it worked for me but you have to add some more option for who are still having troubled in unbricking. like i had..
but it can't be done without your method as on OP..
how i got bricked !!! my Moto g dual (indian)
i tried to downgrade from 4.4.4 to 4.4.2 to flash custom Rom and got system partition corrupt.
again i tried to flash stock images but no use, actual problem was System and data was not formatting.
even if you try million times and you can never successfully flash stock images without error..
however i was checking many threads in xda to resolve this problem but couldn't figured it out, as i was not new to XDA i had confidence that i can come out from this issue. until this thread gave me a hint but not a solution but still this thread is a part of the solution
let come to the unbricking method (only for those who cant flash Stock firmware from fastboot)
Reboot to fastboot..
flash Philz recovery first. get it from here.. http://forum.xda-developers.com/showthread.php?t=2639626
better to use Kernel Flasher by my old buddy Ghostfreak NB http://forum.xda-developers.com/showthread.php?t=2214724,
you just need to extract and copy the recovery to extracted kernel Kernel_Flashing_Tool_v2.0 in IMG folder and run kernel Kernel_Flashing_Tool_v2.0.bat.
press 1 and it will flash recovery, press enter it will reboot to Philz recovery,
now format System, data and whatever you can!!\
next reboot to Bootloader from Recovery,
and then follow procedure as OP
if you want to flash stock rom get from here http://forum.xda-developers.com/moto-g/development/4-4-3-moto-g-stock-rom-t2804891 and adb push as advise by OP. now you have stock rom running without any issues
Edit..
You can also flash custom ROMs with ease.
Note you better flash recovery through kernel flasher tool..
Click to expand...
Click to collapse
I get this error
When im typing adb push AOSP ( i renamed to that name ) /sdcard/ attacks me this: not found. Any help?:crying: Plez :c
eg0097 said:
So you've bricked your phone. Well as long as the boot loader works then your "brick" is just a soft-brick. Follow this simple guide and flash a custom rom in a couple of minutes. I am not claiming ownership of this method, but its the first time Ive seen it and it helped me so here Good Luck!
Download the attachments.
Unzip both files to a folder on your desktop.
Run the adb setup file and press (Y) all 3 times.
Next unzip the twrp.zip folder. Then flash the twrp recovery by using the "fastboot flash recovery twrp.img" command. Make sure phone is in fastboot mode.
Next boot the phone into the recovery and select advanced. Then click on terminal command and navigate to the /sdcard/ folder.
Lastly click "select" on the bottom right corner.
Now download whatever rom and gapps you would like to install on your phone and rename them to something short. Then open a command prompt at the directory where the rom and gapps are. In the command prompt enter these commands "adb push NAMEOFROM.zip /sdcard/" and "adb push NAMEOFGAPPS.zip /sdcard/".
The command prompt will not show change for a few minutes. After you notice the command prompt is ready for the next command it is okay to exit it.
Now just flash the rom and gapps normally and hopefully your phone will be okay.
Need any additional help? Feel free to ask This should work on all Moto G models that have a TWRP image and have a bootloader unlocked.
Click to expand...
Click to collapse
I haven't actually bricked my phone but looks like my ROM.
So, I am trying to make a ROM previously in First Built the ROM didn't even wrote System [That was my fault as I wrote the the 'system' folder in Zip as 'System' and in update scripts 'system' to be extracted in '/system']
But , now the ROM has written /system but remains on Warning Boot loader Locked screen and starts to warm up I have tried Installing Kernels to fix it but no luck please help.
Device->Moto G Falcon XT1033
ROM Details->Custom ROM based on stock 5.1
Priority of problem->5 ,as I use MultiRom and have this Custom ROM as Secondary and CM 13 as primary ,but suggest a fix ASAP .
@Sid_Sun - Flash the latest factory firmware image for your model. Once that boots, proceed to custom ROMs if desired.
Factory Firmware Image: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
lost101 said:
@Sid_Sun - Flash the latest factory firmware image for your model. Once that boots, proceed to custom ROMs if desired.
Factory Firmware Image: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
My device is booting up I am trying to make a ROM which is not booting and the booting method is by MultiRom the not booting ROM is as secondary so I can use CM 13 as primary but not boot my Custom ROM I want a fix to that issue.
Sid_Sun said:
My device is booting up I am trying to make a ROM which is not booting and the booting method is by MultiRom the not booting ROM is as secondary so I can use CM 13 as primary but not boot my Custom ROM I want a fix to that issue.
Click to expand...
Click to collapse
The MultiROM thread would be the place to ask:
http://forum.xda-developers.com/moto-g/development/modmultirom-v30wip08-01-2014-t2997071
I have no experience with MultiROM, but I believe a Kernel with kexec-hardboot support is required.
lost101 said:
The MultiROM thread would be the place to ask:
http://forum.xda-developers.com/moto-g/development/modmultirom-v30wip08-01-2014-t2997071
I have no experience with MultiROM, but I believe a Kernel with kexec-hardboot support is required.
Click to expand...
Click to collapse
This isn't MiltiRom's Fault probably but nvm I will flash The Custom ROM as primary and see how it goes .
Friend in step 3 you say "Run the adb setup file and press (Y) all 3 times." But what is the file?
In the list there are only 2 to download files
adb-setup-1.3.zip
twrp.zip
Where do i put the command in the 4th step?
Please help
Related
Flashing ROMs/Mirror Links - Sending Files in CWM Via ADB! & Flashed TF201 Recovery?
I'm seeing alot of people are having issues with people loosing system images/soft bricking devices but its all avoidable!
If you download a Custom ROM also make sure you download the latest ASUS Stock ROM
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you create a folder on your internal SD called ROMs if anything happens you can always flashboot CWM and then you can use CWM to install new ROMS.
ROM MIRRORS: https://docs.google.com/folder/d/0B_7VIwxjudWvLUllSVpyUW9oSDQ/edit
At the moment we dont have mount via USB or external SD so if you loose access to your internal system you could be stuffed without these files.
Also make sure you create a CWM backup
Pushing files in Recovery via ADB
Step 1: Boot into recovery ( To access it, shutdown your tablet and press Power + Vol Down, then press Vol Up before the 5s timeout)
See Picture: https://docs.google.com/open?id=0B_7VIwxjudWvUWRJRmpOd3M4WFk
Step 2:Open Windows device manager and you will probably see https://docs.google.com/open?id=0B_7VIwxjudWvNUhOVWVmSDhjWjA Transformer device listed but not mounting in ADB Devices.
Step 3:Download the ASUS USB Drivers from https://docs.google.com/open?id=0B_7VIwxjudWvLTJuQnlZU1B1TVU and extract them to where you want.
Step 4: Watch this video to install the ADB Drivers https://docs.google.com/open?id=0B_7VIwxjudWvXzJmT09RZjlPdlE
Step 5: Using ADB "Adb Push c:\romfolder\rom.zip /sdcard" wait for it to finish then using recovery you should be able to flash it now.
Flashed TF201 Recovery in ROM Manager?
Follow these steps to recover your semi-bricked TF300T Tablet All the files you need are in the ROM Mirrors link. You need to make sure you have installed the drivers as above to be able to send recovery via Fastboot. You need our TF300T Recovery and the Asus Stock ROM.
Step 1: We need to flash our recovery onto the tablet. As you probably have already done this I have copied the info from http://forum.xda-developers.com/showthread.php?t=1668173 Thanks to XpLoDWilD for this!
Step-by-step guide
Unlock your bootloader with Asus Unlock app
Connect your tablet to your computer
Shutdown your tablet
Hold Power + Vol Down until a message appears ("Press Vol. Up to enter RCK (5s)") : DON'T PRESS VOL UP
After 5 seconds, a new menu appears. Press Vol Down once to change to the USB icon, then press Vol. Up to validate (you have to do this in less than 10 seconds, otherwise your tablet will boot Android OS)
At this point, your computer should recognize Fastboot device (Windows will notify you here, OSX/Linux stays calm)
Flash recovery image with fastboot: fastboot -i 0x0B05 flash recovery recovery.img (if we suppose recovery.img is in your current directory)
Once the operation is done, type fastboot -i 0x0B05 reboot to reboot your tablet
You now have CWM installed. To access it, shutdown your tablet and press Power + Vol Down, then press Vol Up before the 5s timeout. After a few seconds, you'll be in CWM interface.
Step 2:Repeat Steps 4-6 to boot back into Fastboot
Step 3:NB: If you have followed what I said about keeping Stock ROMs on the Internal SD Card just use CWM to reflash that and you are done! If not contiune with these steps
Now you need to have the Asus Stock ROM you want to flash, Extract the ZIP so you can see the BLOB file and take note of the location you have extract too! This is the file we will send via Fastboot. You can rename the file to update.blob so it follows the picture below and save into the directory you have your fastboot command.
At the command Prompt type fastboot -i 0x0B05 flash system update.blob
Step 4: fastboot -i 0x0B05 reboot
Picture https://docs.google.com/open?id=0B_7VIwxjudWveFlOVFdHT2ZjeHM
Special Thanks to XpLoDWilD for the Dev work and BlakeC90 for recovering his tablet through this brick. I copied the details for the thread below.
http://forum.xda-developers.com/showthread.php?t=1687015
Good idea to do this, thanks!
Great post, should be stickied. This will help the people new to flashing immensely.
Cheers guys, I've also uploaded some ROMs now.
I will Mirror the CM9 ROMs and will also mirror Stock ones
I have my tf300, acer a100 and my Samsung galaxy blaze all rooted, but have yet to flash a custom rom. if someone can just clarify something that would be awesome
a nandroid back is same thing as backing up current rom threw recovery?
to even get into recovery, do you have to unlock ur bootloader first? if so after you unlock it. will you still receive firmware updates threw Asus ota. If not, is all you do is wait till rom or build.prop gets updated with the same features and just update that way. if not, what the hell do you do then. kinda confused about that lol
lastly, this might be a stupid question but a custom rom is basically a tweaked
operating system. that has more features then HC or ICS. and all the good stuff like overclocking build in? am i missing any other major features. if im even on the right track in the first place lol
if anybody can help. will be appreciated
Trevor OBrion
trevor7428 said:
I have my tf300, acer a100 and my Samsung galaxy blaze all rooted, but have yet to flash a custom rom. if someone can just clarify something that would be awesome
a nandroid back is same thing as backing up current rom threw recovery? Yes
to even get into recovery, do you have to unlock ur bootloader first? if so after you unlock it. will you still receive firmware updates threw Asus ota. If not, is all you do is wait till rom or build.prop gets updated with the same features and just update that way. if not, what the hell do you do then. kinda confused about that lol If you device unlock then you wont get OTA updates, you need to manual install them or install custom ROM
lastly, this might be a stupid question but a custom rom is basically a tweaked
operating system. that has more features then HC or ICS. and all the good stuff like overclocking build in? am i missing any other major features. if im even on the right track in the first place lol
ROMs like CM9 are based off pure Google Code rather than all the tweak/bloatware that Asus put in and yes OC is possible with custom kernals
if anybody can help. will be appreciated
Trevor OBrion
Click to expand...
Click to collapse
See above
Unlock is a permanent voiding of your warranty as well.
Sent from my SCH-I510 using XDA
Updated to recover from Flashing TF201 Recovery
Thanks for the nice Thread.
What if the TF300T cannot boot into recovery?
Code:
Android cardhv-user bootloader <2.10 e> released by "WW_epad-9.4.3.29-20120511" A03
Checking for android ota recovery
Booting recovery kernel image
Jake2kOne said:
Thanks for the nice Thread.
What if the TF300T cannot boot into recovery?
Code:
Android cardhv-user bootloader <2.10 e> released by "WW_epad-9.4.3.29-20120511" A03
Checking for android ota recovery
Booting recovery kernel image
Click to expand...
Click to collapse
Can you get into the fastboot menu?
Step 1 of the TF201 recovery?
Nope. When pressing Power + Vol Down will directly show message above.
I think it's over, but maybe someone has an idea.
Jake2kOne said:
Nope. When pressing Power + Vol Down will directly show message above.
I think it's over, but maybe someone has an idea.
Click to expand...
Click to collapse
Just a thought if seems it looking for a stock image? So have you tried putting the ww.29 zip file on the external SD card and seeing if it picks it up?
Also see if it detects in Windows Device manager?
Oh, forgot to mention: It even won't boot up.
It boots neither Android, nor recovery.
No joke.
Jake2kOne said:
Oh, forgot to mention: It even won't boot up.
It boots neither Android, nor recovery.
No joke.
Click to expand...
Click to collapse
Yeah I don't mean into Android, if you put the ww.29 on a external card and boot it into
Code:
Android cardhv-user bootloader <2.10 e> released by "WW_epad-9.4.3.29-20120511" A03
Checking for android ota recovery
Booting recovery kernel image
It might be looking for a firmware, last fail attempt recovery?
When its switched on in the above state does anything show in device manager?
Although its for the TF101 seems you are having the same issue http://forum.xda-developers.com/showthread.php?t=1622343 ?
It's not mine so I have to forward each idea.
Tried with the external SD card but didn't work. Too bad.
Tested with normal boot up (stucked on ASUS logo) and tested it with the recovery mode (or whatever it is called like...)
The link could be the same problem but has no solution.
Tomorrow UPS get the tf300.
The ASUS Bootloader Unlock Tool bricked it totally. Seems like to be the first device at all.
The User said he just used the tool, restarted, stucked. Really good.
Jake2kOne said:
It's not mine so I have to forward each idea.
Tried with the external SD card but didn't work. Too bad.
Tested with normal boot up (stucked on ASUS logo) and tested it with the recovery mode (or whatever it is called like...)
The link could be the same problem but has no solution.
Tomorrow UPS get the tf300.
The ASUS Bootloader Unlock Tool bricked it totally. Seems like to be the first device at all.
The User said he just used the tool, restarted, stucked. Really good.
Click to expand...
Click to collapse
Let us know how you get on with the warranty, if Asus reject it under its been unlocked or not.
All I have to say is I hope this works. I was dumb and was curious to see after installing sparky's stock rooted rom I selected factOry restore from the devices menu in settings. It erased all! Luckily I have my tiBU saved on my ext sd.
It's pushing virtuous now by using the \data media option
My experience in using the adb push method
everything went smoothly. I didnt back up everything properly the first time i flashed a rom so i had to push a rom on the transformer.
This is important and please add it on the first post. If the files you pushed on the device dont appear on it. Restart your computer and try again. (i didnt get any errors while pushing but i couldnt find the files on the device and i fixed it by restarting my pc and pushing them again)
ok, so im lost!.. lol
I have a soft brick, im trying to push a stock rom to my tab, but can not for the life of me get my tab to show up as a ADB. It will show as a Fastboot Interface, and if i go into recovery it just shows Transformer like in the pic in the original post. I have tried installing the driver just like the youtube vid shows, but its not working.
backstory is i tried to flash a new custom ROM over another custom ROM, i wiped my usual, cache, dalvik, and wiped system, to have a fresh install, but kept getting a broken ROM with the new one, and when i flashed back to my old one. i then clicked format internal data like a tard and wiped my entire SD Card.
Any advice you guys can give would be appreciated.
UPDATE: Ok i got ADB working (i think... lol) it shows in device manager, but im not getting anything when typing adb devices in cmd prompt. I also got fastboot to reboot the device but when i try to flash the update.blob i get.... error: cannot load 'update.blob'
If i use qtADB it will flash the recovery.img for some reason i just cant get it to wok when using the actual cmd prompt. (in cmd prompt i was getting the error cant load xxxx.blob or xxxx.img regardless of where ii placed the image or blob file on my computer)
Now you need to have the Asus Stock ROM you want to flash, Extract the ZIP so you can see the BLOB file and take note of the location you have extract too! This is the file we will send via Fastboot. You can rename the file to update.blob so it follows the picture below and save into the directory you have your fastboot command.
At the command Prompt type fastboot -i 0x0B05 flash system update.blob
Step 4: fastboot -i 0x0B05 reboot
I try this but i get this error
C:\Users\VaHiD\Desktop\Fastboot>fastboot -i
0x0b05 flash system blob
sending 'system' (799748 KB)...
OKAY [138.170s]
writing 'system'...
FAILED (remote: (InvalidSize))
finished. total time: 214.335s
what is the ((InvalidSize)) error?!
I try to install recovery twrp and cwm but do not install any .....
Can you help me?
Asus released the new Android 4.2 to our beloved devices and you may be wondering how can you update if you are unlocked and how can you root it.
Note: this guide was updated with the 2.5.0.0 TWRP. For this to work properly, you will need to use the last 10.6.1.27.1 version of the tablet, or a newer one. If you are already on a previous 4.2.1 version, please update to the new one using this same guide. If you flash this recovery with the older versions of the 4.2.1 bootloaders, you will end up with a double screen! New TWRP versions won't be able to mount boot and recovery, and won't work with all SD cards, not to talk about backup issues!
Things you should know before you start:
- I marked each title of this guide with [LOCKED BL], [UNLOCKED BL] and [BOTH BL] to specify witch ones will work with locked/unlocked or both bootloaders, respectively.
- Please verify if you have the correct drivers for the tablet installed on your computer. Windows 7/8 should install these automatically.
- The new 4.2 updates the bootloader, removing the USB icon that used to appear there and allowed you to enter fastboot. It's OK, you will be able to use it right from the bootloader menu, without selecting any option at all.
- Do this at your own risk! I'm not responsible if you break your tablet!
- Don't forget to make BACKUPS!
- If you are already on 4.2, then you can skip to the Recovery and Root parts of this guide
-- Installing / Updating to 4.2.1 --
There are three methods you can use to update your tablet to the latest Android stock version. All of them will require you to download the
firmware file located at Asus website. You can download them from here. Select Android as the OS, firmware and choose the right firmware for you SKU. You can find your SKU by following the instructions on the website itself. Don't forget to unpack the zip file you downloaded: there's another inside!
[BOTH BL] Method 1: Updating directly from stock ROM
Notes:
You must have a stock ROM installed
You need to put the update file on an SD card
You will keep all your data
I do not recommend this method: sometimes it ends up on a brick
If your tablet is stock, or have some custom ROM based on stock installed, you can directly update the tablet by simply inserting a SD Card with the firmware file inside. Android will prompt you with a notification asking if you want to update. Touch it and wait until the update is done
[UNLOCKED BL] Method 2: Update using fastboot
Notes:
You will keep all your data
This is the best method to update your tablet if you want to keep all your data, and the safest one
Ensure you have the correct drivers for the tablet installed on your computer, or you will have a "waiting for device" error
To update using fastboot, follow this steps:
If you don't have fastboot yet, download it from here an unpack it somewhere on your computer
Extract the Asus firmware file and put the blob file inside fastboot folder
Open a command line on fastboot folder (write "cmd" on Windows search bar at the Start menu, and then
Code:
cd "FOLDER WHERE YOU EXTRACTED FASTBOOT"
, or you can just use SHIFT + RIGHT CLICK on the folder and select "Open command line window here" or something like that)
Reboot the tablet holding the volume down key until you see some icons. Use the volume down key to select the USB icon and then volume up to select it
Connect the tablet to the computer if you didn't do so
Write
Code:
fastboot -i 0x0B05 flash staging blob
, hit enter and wait until it completes
Hold the power button for 10 seconds to reboot the tablet
You are now updated to Android 4.2
[UNLOCKED BL] Method 3: Update using TWRP recovery
Notes:
You must have TWRP installed
You need to put the update file on an SD card
This was the method I used since I wanted to prevent any bugs due to old data and to ensure the new partitions from 4.2 would be OK
You will keep your data as long as you don't wipe Data and Factory reset (including internal memory)
Follow the steps bellow if you want to update to 4.2.1 DELETING ALL YOUR DATA , STARTING FROM SCRATCH!
Insert the SD card with the update file on the tablet
Reboot to recovery
Wipe Cache, Dalvik and System. Wipe Data if you want a fresh start on your tablet, but remember, THIS WILL WIPE ALL YOUR DATA AND INTERNAL MEMORY!!. You can also do a Factory Reset instead of data wipe if you want to remove all your android configurations/apps keeping your internal storage.
Install the Asus Firmware
Reboot (ignore the "no OS installed message) and let it finish
You have now the latest Android 4.2.1
[UNLOCKED BL]-- Installing TWRP (Recovery) --
Since this new update brings a new bootloader, older recovery versions from 4.1 won't work at all. Don't try to flash one!
This guide will give you a recovery that works just fine on the new bootloader. And yes, it can read/write to an external SD just fine. Follow this steps to install the new recovery on your device:
Connect the tablet to the computer
Reboot the tablet using the proper button on the power menu, holding Volume down until you see three icons (RCK, Android and Wipe Data)
Download this file and unpack it (it contains fastboot and the TWRP 2.5.0.0 which works with the new bootloader)
Open a command line on the extracted folder (you can use the instructions I wrote in Method 2 if you don't know how to do this) and type
Code:
fastboot -i 0x0b05 flash recovery twrp.blob
Wait for the script to complete. Once it is done, reboot the tablet by holding volume down and power button for 10 seconds. Don't enter recovery directly!
You have now the new recovery for Android 4.2 .
[BOTH BL] -- Rooting --
Note: If you are willing to install a custom ROM like CROMI you don't need this. Custom ROMs have root by default.
Rooting the tablet once you have a recovery is pretty easy. Here's how you can do it:
- Unlocked devices
Download SuperSu zip file from here (choose the flashable version) ]and place it on a SD card or inside the root of your tablet's internal memory
Reboot the tablet holding vol down, and when the three icons appear, hit volume up to enter recovery
When the recovery prompts you a password, hit cancel (this is a bug from the current version of TWRP, and it should be fixed soon. It is ok to ignore it!)
Flash the zip you just downloaded
Wipe Dalvik/Cache (just in case)
Reboot
You are now rooted!
- Locked devices
If you have your bootloader locked you can root Android 4.1/4.2 by using the method discovered by Morlok8k, here: http://forum.xda-developers.com/showthread.php?t=2228613 (note that this isn't tested yet for the latest 10.6.1.27.5 firmware!)
[UNLOCKED BL] -- Downgrading to 4.1 or other firmware --
I was going to write a downgrade method but it seems that there is a good one here: http://forum.xda-developers.com/showthread.php?t=2195883
Again, do it at your own risk.
[LOCKED BL] -- Recovering your tablet from scratch --
If you are on a stock locked device and somehow got a bootloop and you can't do anything with your tablet you follow this steps to completely restore your tablet. Note that all data will be lost.
Pretoriano80 said:
========= Recover /Downgrade from Jelly Bean to ICS/Clean Factory Restore with stock recovery =========
1) Download the latest firmware from Asus website
2) Extract the .zip file somewere on your desktop (the result will be another .zip file,use it for step 3)
3) Rename the extracted archive to "EP201_768_SDUPDATE.ZIP" (without the " ") and upload it to a MicroSD card
4) Insert the MicroSD card in your tablet and use this button combination to Power ON and go to recovery --> Start the tablet by pressing Volume Down and POWER togheter for 5 seconds ,a message will inform you that you have 5 seconds to enter the recovery,press Volume UP before the 5 seconds expire.
At this point the device will go in recovery and should start updating your firmware .
Note: Keep in mind that Windows doesn't show the known file extensions so most users don't have to put the .ZIP extension in the filename.
Click to expand...
Click to collapse
This tutorial is made of things I gathered on the forums: I do not own anything! Hit thanks if I helped you :angel: I will keep it updated once new things come out
A special thanks to elesbb for the fastboot methods
This is great. Just one question for clarification: Users have reported not being able to see their External microSD's in TWRP. Is this still the case, or did the patch to TWRP alleviate this issue?
would i need to unlock the bootloader to do this?
MrCHUPON said:
This is great. Just one question for clarification: Users have reported not being able to see their External microSD's in TWRP. Is this still the case, or did the patch to TWRP alleviate this issue?
Click to expand...
Click to collapse
Here TWRP is recognizing the external SD It lists the files and I'm doing right now a backup to it . No errors whatsoever
Here is a photo of me backing up to an 4GB SD card
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And the end of it
jobankler said:
would i need to unlock the bootloader to do this?
Click to expand...
Click to collapse
Check the OP...First item. "You must be unlocked".
So yes.
Re: [Tutorial] Rooting and installing a recovery on Android 4.2.1 (10.6.1.8+)
Hoi
My device is unlocked
Must i unlocked again for 4.2.1
Thanks hope you can help my
Sent from my ASUS Transformer Pad TF300T using xda premium
Re: [Tutorial] Rooting and installing a recovery on Android 4.2.1 (10.6.1.8+)
jackie1234 said:
Hoi
My device is unlocked
Must i unlocked again for 4.2.1
Thanks hope you can help my
Sent from my ASUS Transformer Pad TF300T using xda premium
Click to expand...
Click to collapse
So I've read, upgrading does not relock you, so you shouldn't need to. For those that are locked and upgrade to 4.2.1 there is a new unlock tool to do it.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Verified that this works for me. If you read ahead and placed the SuperSu zip on your SD card BEFOREhand, you can even skip one of the reboots.
WARNING
Your instructions are wrong... You cannot flash the update using custom recovery, it will result in a brick..
Already happened with me!!! I've followed your tutorial blindly and had to sweat a bit to recover my tablet.
Change it ASAP.
Best solution to unbrick/flash is to go into fastboot and use
fastboot -i 0x0B05 flash system blob
fastboot -i 0x0B05 flash system "name of the update"
joelalmeidaptg said:
Hey guys! Asus released the new Android 4.2 to our beloved devices and now we are able to root it using a few steps.
Notes:
- You must be unlocked
- If you don't have 4.2.1 on your tablet yet, download it via the Asus website, unpack it, and place the file on your SD car and flash it using a custom recovery or the update notification on a stock ROM
- If you have 4.2 and want to unlock it, remember to check Asus website to download the new unlock tool available for 4.2 devices
- Please verify if you have the correct drivers for the tablet installed on your computer
Lets get started!
Connect the tablet to the computer
Reboot the tablet using the proper button on the power menu, holding Volume down until you see three icons (RCK, Android and Wipe Data)
Download this file and unpack it (it contains fastboot and a patched version of TWRP 2.4.4.0)
Open a command line on the extracted folder and type fastboot -i 0x0b05 flash recovery twrp.blob
Wait for the script to complete. Once it is done, reboot the tablet by holding volume down and power button for 10 seconds. Don't enter recovery directly!
Once the tablet boots up, download SuperSu zip file from here and place it on the root of your tablet's internal memory
Reboot the tablet again holding vol down, and when the three icons appear, hit volume up to enter recovery
When the recovery prompts you a password, hit cancel
Flash the zip you just downloaded
Wipe Dalvik/Cache (just in case)
Reboot
Aaaaand... Congratulations, you have now a rooted stock Android 4.2.1 !!
This tutorial is made of things I gathered on the forums: I do not own anything! Hit thanks if I helped you :angel:
Click to expand...
Click to collapse
:good: :fingers-crossed: :victory: :laugh: I have no words to thank you friend, excellent contribution.
Re: [Tutorial] Rooting and installing a recovery on Android 4.2.1 (10.6.1.8+)
avatar_pt said:
Your instructions are wrong... You cannot flash the update using custom recovery, it will result in a brick..
Already happened with me!!! I've followed your tutorial blindly and had to sweat a bit to recover my tablet.
Change it ASAP.
Best solution to unbrick/flash is to go into fastboot and use
fastboot -i 0x0B05 flash system blob
fastboot -i 0x0B05 flash system "name of the update"
Click to expand...
Click to collapse
Did you unpack the zip downloaded from Asus?
Sent from my ST25a using xda app-developers app
Tamaskan said:
Did you unpack the zip downloaded from Asus?
Sent from my ST25a using xda app-developers app
Click to expand...
Click to collapse
Again, I followed the tutorial blindly for the flash
Maybe it was something else, dunno. I just bricked, but I be managed to recover
Re: [Tutorial] Rooting and installing a recovery on Android 4.2.1 (10.6.1.8+)
avatar_pt said:
Again, I followed the tutorial blindly for the flash
Maybe it was something else, dunno. I just bricked, but I be managed to recover
Click to expand...
Click to collapse
Then you didn't brick, bud. What exactly did it do? Why do you think it "bricked".
Sent from my EVO using Tapatalk 2
pl
avatar_pt said:
Your instructions are wrong... You cannot flash the update using custom recovery, it will result in a brick..
Already happened with me!!! I've followed your tutorial blindly and had to sweat a bit to recover my tablet.
Change it ASAP.
Best solution to unbrick/flash is to go into fastboot and use
fastboot -i 0x0B05 flash system blob
fastboot -i 0x0B05 flash system "name of the update"
Click to expand...
Click to collapse
please keep your mouth shut off if you don't know what to say.
YOU CAN FLASH UPDATE FILE FROM ASUS WEBSITE WITH TWRP AND THERE IS NOT BRICK IN HERE
******
here is what i just did to update my tab to 4.2.1
-was running cleanrom 3.4.4 with twrp 2.2.2.0
-downloaded twrp 2.4.4.0 and flashed it with fastboot
-download 4.2.1 update file from asus website=> unzip this file to get the real file ( apparently, asus just put the rom.zip file into a folder, then zip this folder again, kind a stupid here ^^)=> put it in my external micro sdcard
- boot into recovery=> flash the updated rom.
avatar_pt said:
Again, I followed the tutorial blindly for the flash
Maybe it was something else, dunno. I just bricked, but I be managed to recover
Click to expand...
Click to collapse
It wouldn't flash for me either. I used your method of flashing the blob, then followed the OP's directions for flashing TWRP using the fastboot/TWRP files he provided.
Re: [Tutorial] Rooting and installing a recovery on Android 4.2.1 (10.6.1.8+)
What i have done
I download the firmware from asus and renamed to xx_epad-user-10.6.1.8.zip
XX is the ww or US you must rename this in the directory what you extract
Example WW_epad-user-10.6.1.8.zip
US_epad-user-10.6.1.8.zip
Then put it in the root of your sd card or on your root on the tablet
Then you can update
And you can root follow this forum.
I am on 4.2.1 and rooted
Thank for all who have this made it
Thanks
Sent from my ASUS Transformer Pad TF300T using xda premium
Flash zip file from asus web site it really works!
avatar_pt said:
Your instructions are wrong... You cannot flash the update using custom recovery, it will result in a brick..
Already happened with me!!! I've followed your tutorial blindly and had to sweat a bit to recover my tablet.
Change it ASAP.
Best solution to unbrick/flash is to go into fastboot and use
fastboot -i 0x0B05 flash system blob
fastboot -i 0x0B05 flash system "name of the update"
Click to expand...
Click to collapse
I did flash my asus with the zip from asus web page with no issues, I used TWRP 2.4.3
I un-zipped the file (just one time and without change the name) and I placed the next zip file to my SD card root folder, then I made a full wipe and intall the zip file from SD card.
Right now my asus belong to my wife, my youngest son and I because I can create users.
I made a backup of my apps with the asus aplication and I could reinstall all them after the update.
AB
Good to go for me. TWRP recovery and rooted. Nice write up man.
You might add in there something about the new bootloader booting directly to fastboot now, no need to select the usb icon. Also maybe mention to make sure that the drivers get installed properly once you are in fastboot. When I booted to fastboot it had to install some drivers, so I waited for those to finish before I ran the fastboot command.
Installed TB and about to uninstall some bloat. Can't wait for roms to get updated.
Thanks again man.
avatar_pt said:
Your instructions are wrong... You cannot flash the update using custom recovery, it will result in a brick..
Already happened with me!!! I've followed your tutorial blindly and had to sweat a bit to recover my tablet.
Change it ASAP.
Best solution to unbrick/flash is to go into fastboot and use
fastboot -i 0x0B05 flash system blob
fastboot -i 0x0B05 flash system "name of the update"
Click to expand...
Click to collapse
Yes , it's true , i was bricked , too
could you help me how to unbrick ????????
thanks
Re: [Tutorial] Rooting and installing a recovery on Android 4.2.1 (10.6.1.8+)
I don't understand what your bricks are. Maybe you didn't wipe your tablet as you should? I updated to 4.1 and 4.2 via recovery and never had a problem.
I updated the topic with more info
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Notice: Rooting your device will break OTAs because they require an unmodified system, so you might want to check for updates before rooting your X. However, there is a workaround:
Boot into TWRP via step 5E below, but DO NOT flash it (step 5D)!!
Do a backup of your completely stock, unrooted ROM
Root the device by flashing SuperSU...zip
When an OTA hits, you can get it by doing this:
Boot into TWRP again without flashing it (same as step 1 above)
Restore your stock, unrooted ROM (from step 2 above)
Apply the update from stock recovery
Backup the unmodified ROM with the update if you want, then re-root as above.
Note: You will lose any changes, mods or app data since you did the backup, but hey, at least the OTA is applied.
If you get stuck with an update that won't flash and you haven't backed-up your unrooted ROM as above, look here:
[Guide] How to Install OTA's with TWRP, and please hit thanks for @SpiritBreak3r :good:
_____________________
Disclaimer: Rooting does not void the OnePlus X’s warranty, though damaging your hardware (i.e., burning up your CPU by overclocking, hardbricking the device) will. You proceed at your own risk! I accept no responsibility for what you do with your phone. Follow the directions closely, and the odds are you will succeed without any trouble. If you are not sure what you are doing, do some more research before you try. If you get confused with terminology, try looking here for answers or Google it. If you get stuck, post a question in the thread—we're here to help you.
Preliminary steps
1. Make sure that your phone is always charged above 50%!!!
Running out of battery in the middle of flashing something could brick your phone.
2. Make sure that your computer can properly communicate with the device:
We will be issuing commands to the phone from your PC via the USB cable using Android’s SDK tools, in particular ADB and fastboot. If you have not done so already, you must install the following on your Windows computer for this to work:
Java runtime
The Universal Android ADB Driver for Windows.
SDK tools for Android (alternately just ADB & fastboot). Remember where this is installed on your harddrive for later!
You can verify the connection between your PC and phone by running the following procedure:
A. With the phone booted normally, connect it to your computer with the USB cable.
B. Enable Android debugging by going to Settings > About phone and tapping on “Build number” 7 times.
C. Go to Settings > Developer options and check “Android debugging”. A dialogue box will appear asking you to authorize your computer’s RSA fingerprint. Click “Always allow...”
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
D. Open a command prompt in Windows and navigate to the folder where you put SDK tools for Android (ADB & fastboot) above.
E. Type the following command:
Code:
adb devices
You should get a return like this:
If you cannot get the connection to work:
1. Check your USB connection, then verify that Android debugging is enabled in settings and that your computer’s RSA fingerprint has been authorized.
2. Still not working? Open Device Manager in Windows and make sure that you don’t have a yellow exclamation point next to something like “Android Device” or “One.” This would indicate a driver problem that must be resolved. Try re-installing the Universal Android ADB Driver for Windows, and make sure to restart your computer. Once you’ve rebooted, if you still have a yellow triangle, right-click on the device and select “Update Driver Software,” then “Search automatically for updated driver software.”
3. If you still have a yellow exclamation point, then try forcing the driver to install:
In Device Manager, right-click on the device and select “Update Driver Software.”
Select “Browse my computer for driver software”
Select “Let me pick from a list of device drivers on my computer”
Select “ADB Interface” from the list
Select manufacturer “Google”
Select “Android Testing Interface Version xxx”
Click “Next.” If you get a warning, select “Yes” to continue and wait for the driver to install properly.
3. Know how to enter “fastboot mode” on the OnePlus X
To root the device, you must be competent at booting it into fastboot mode. There are two ways to accomplish this:
Power off the phone. Then simultaneously hold down the volume up & power buttons until it vibrates. When done correctly, you will see the words “Fastboot Mode” on a black screen. If not, you dumb-thumbed it, and the device will boot normally into Android. Power off the device and try again.
With the phone running Android normally and Android debugging enabled (see above), open a command prompt in Windows, navigate to the folder where you installed SDK tools (ADB & fastboot) and type:
Code:
adb reboot bootloader
Rooting the OnePlus X
There are three essential steps to rooting the device:
Unlock the bootloader
Flash or boot into TWRP custom recovery [For OxygenOS 3.1.3 use TWRP blu_sp★rk r175]
Flash SuperSU...zip from recovery [For OxygenOS 3.1.3 use SuperSU v2.78 SR1 beta]
However, we're going to add a few more to protect your data and device in case something gets borked.
1. Backup your phone’s data
Unlocking the bootloader will involve doing a factory reset resulting in the loss of all accounts, emails, texts, apps and app data, pictures, music, etc. on the device. Move anything you need to keep onto your PC or a cloud service like DropBox.
2. Unlock the bootloader
2A.Go into Developer Options and enable bootloader unlocking
2B. Boot the device into fastboot mode. (Simultaneously hold down the volume up & power buttons until it vibrates.) You should see a black screen with the words “Fastboot Mode”.
2C. Plug in the USB cable.
2D. Verify that your device is connected with this command:
Code:
fastboot devices
You should get a return like the image above under Preliminary Steps
2E. Unlock the bootloader using the following commands:
Code:
fastboot oem unlock
The device will unlock the bootloader, erase all user data and reboot itself into Android. You will have to set up everything from scratch.
3. Re-enable Android debugging
3A. Re-enable Developer options by going to Settings > About phone and tapping on “Build number” 7 times.
3B. Go to Settings > Developer options. Check “Android debugging” and re-authorize your computer’s RSA fingerprint.
4. Download SuperSU zip
4A. Head over to Chainfire’s CF-Root thread and download the SuperSU access management tool from the “CWM / TWRP / MobileODIN installable ZIP” link. It will probably called something like UPDATE-SuperSU-v2.XX.zip. This zip file will root your device and install the SuperSU access management app in one smooth motion. Hit the thanks button for Chainfire or donate to his Paypal account and buy him a Coke.
NOTE: For OxygenOS 3.1.3 use SuperSU v2.78 SR1 beta
4B. Copy UPDATE-SuperSU-v2.XX.zip to your phone’s SD card.
5. Flash TWRP custom recovery
5A. Download TWRP recovery.
NOTE: For OxygenOS 3.1.3 use TWRP blu_sp★rk r175
5B. Place file you downloaded above to the location where you installed SDK tools (ADB & fastboot).
5C. Boot the device into fastboot mode and connect it to your computer with the USB cable.
5D. In this step, we will replace your stock recovery with TWRP recovery.
Note: This step is optional. If you want to root but preserve stock recovery, skip straight ahead to step 5E below. Thanks @rockuppl for the reminder. :good:
Open a command prompt in Windows and navigate to the folder where you installed SDK tools (ADB & fastboot). Type the following commands:
Code:
fastboot flash recovery twrp-3.0.0-0-onyx.img
5E. Reboot into TWRP recovery with the following command.
Code:
fastboot boot twrp-3.0.0-0-onyx.img
You should now see the custom recovery you just flashed, not the stock recovery.
6. Backup your stock ROM before making any changes
In TWRP press “Backup.” <--- See how simple this is???
Don’t be a noob—backup your device!!! Right now we don't have stock boot debuggable image files for the OnePlus X, so borking your device could leave you with a nice paperweight until we do. :crying: Restoring from a backup in recovery is easy, and only works if you've backed-up first
7. Root the device
7A. The device should still be in recovery from step 6 above. Go back to the main menu and press “Install,” find UPDATE-SuperSU-v2.XX.zip on the SD card, then flash it.
7B. Reboot the phone. It is now rooted!
7C. Go to the app drawer and open SuperSU. Update the binary if prompted. Its icon looks like this:
7D. Download and install Root Checker from the Play Store to verify that you have root access.
Yes I already own the phone and I see the bootloader unlock switch in dev options. I also checked the stock recovery which gives options to flash files from phone memory or otg. So it must be fairly easy. But I still don't want to risk it without it being tried and tested. If there were a custom recovery I could have also backed up the factory image. Only choice is to wait and see I guess
I could try today evening... will update here.
@CafeKampuchia
Is it ok to flash supersu.zip with stock recovery.
Before flashing supersu.zip, will unlock bootloader . Will follow the guide from oneplue two procedure to unlock..
Flashing supersu is safe on hundreds of devices, but I don't have the X so I can't say one way or the other.
I tried the OnePlus One tutorial to unlock bootloader and root it thanks to this guide.
When it comes to install TWRP, adb tells me it's ok but when I boot into recovery, it's the "official" one that show up.
Even from this recovery, I tried to install the SuperSU.zip, but it keeps telling me it failed, so I think I'll just wait for someone to do it correctly
Knockys said:
I tried the OnePlus One tutorial to unlock bootloader and root it thanks to this guide.
When it comes to install TWRP, adb tells me it's ok but when I boot into recovery, it's the "official" one that show up.
Even from this recovery, I tried to install the SuperSU.zip, but it keeps telling me it failed, so I think I'll just wait for someone to do it correctly
Click to expand...
Click to collapse
I wouldn't try flashing a recovery for another device, especially if the stock recovery isn't available.
I'm surprised that supersu wouldn't flash from stock, though.
CafeKampuchia said:
I wouldn't try flashing a recovery for another device, especially if the stock recovery isn't available.
I'm surprised that supersu wouldn't flash from stock, though.
Click to expand...
Click to collapse
Well I thought that TWRP was for all devices and I already went to the stock one before installing TWRP without success to flash SuperSU.
But apprently, installing TWRP the way I did wasn't the right way because I still boot to the stock recovery :/
Knockys said:
I tried the OnePlus One tutorial to unlock bootloader and root it thanks to this guide.
When it comes to install TWRP, adb tells me it's ok but when I boot into recovery, it's the "official" one that show up.
Even from this recovery, I tried to install the SuperSU.zip, but it keeps telling me it failed, so I think I'll just wait for someone to do it correctly
Click to expand...
Click to collapse
Hi, after unlocking bootloader, you are not able to update/flash supersu.zip from stock recovery? right?
if it so, then we need to wait for custom recovery to flash root.
Thanks.
Knockys said:
Well I thought that TWRP was for all devices and I already went to the stock one before installing TWRP without success to flash SuperSU.
But apprently, installing TWRP the way I did wasn't the right way because I still boot to the stock recovery :/
Click to expand...
Click to collapse
No, TWRP is definitely not for every device. You have to use the version made for your specific device.
CafeKampuchia said:
No, TWRP is definitely not for every device. You have to use the version made for your specific device.
Click to expand...
Click to collapse
My bad then ahah
mjose said:
Hi, after unlocking bootloader, you are not able to update/flash supersu.zip from stock recovery? right?
if it so, then we need to wait for custom recovery to flash root.
Thanks.
Click to expand...
Click to collapse
Yes it fails on stock recovery, we'll have to wait for a custom one indeed...
Hi, finally its available in oneplus forum
https://forums.oneplus.net/threads/...om-recovery-root-take-efs-backup-more.401713/
Thanks.
mjose said:
Hi, finally its available in oneplus forum
https://forums.oneplus.net/threads/...om-recovery-root-take-efs-backup-more.401713/
Thanks.
Click to expand...
Click to collapse
THIS WORKS! But beware using the recovery imagine provided there as in is in Mandarin, not English. Other than that it works fine! Already rooted
Savya said:
THIS WORKS! But beware using the recovery imagine provided there as in is in Mandarin, not English. Other than that it works fine! Already rooted
Click to expand...
Click to collapse
Hey i need your help, i installed the custom recovery in Mandarin but i don't understand anything! Could you please tell me where i should go in this recovery to wipe dalvik cache and flash super su? Step by step? Thanks!
Works for me too ! I'll try to install Xposed now ahah !
Hope they'll release TWRP in English soon !
EDIT : Xposed installed and working ! For those who don't know how to do, see here
mjose said:
Hi, finally its available in oneplus forum
https://forums.oneplus.net/threads/...om-recovery-root-take-efs-backup-more.401713/
Thanks.
Click to expand...
Click to collapse
I'll update the OP, but I won't make it a noob friendly guide until we have an English TWRP from a known/trusted developer.
Edit: I tried thanking your post, but I'm out of thanks for the day--8 post limit
CafeKampuchia said:
I'll update the OP, but I won't make it a noob friendly guide until we have an English TWRP from a known/trusted developer.
Edit: I tried thanking your post, but I'm out of thanks for the day--8 post limit
Click to expand...
Click to collapse
I've requested the OP for an English version and hopefully he'll post a link soon.
And that's okay you can thank me later xD
Savya said:
I've requested the OP for an English version and hopefully he'll post a link soon.
And that's okay you can thank me later xD
Click to expand...
Click to collapse
I have english version repacked from original source
https://www.dropbox.com/s/zypo7b41lvj0r2h/en-recovery-twrp-onyx-.img?dl=0
ukanth said:
I have english version repacked from original source
https://www.dropbox.com/s/zypo7b41lvj0r2h/en-recovery-twrp-onyx-.img?dl=0
Click to expand...
Click to collapse
Just flashed it now!
Confirmed that its working and its in English!
Thanks a ton mate!
Also do i have your permission to post your link in the oneplus forums? As there are many users there too waiting for an english version.
@ukanth : shared the recovery on my post on the OP forums
https://forums.oneplus.net/threads/...om-recovery-root-take-efs-backup-more.401713/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DISCLAIMER:
I'm not responsible for any damaged watches or other broken things! All of this is still heavily in development and mainly a developer release, not at all recommended for normal usage!
The following tutorial CAN brick your watch if you're not careful enough! Once again I'm not taking any responsibility!
This has only been tested on Android N so far, Android O is not yet fully tested!
---------------------------------------------------------
Please read before doing anything:
This is a port of TWRP for the Ticwatch E. Currently we're not able to boot it via fastboot (well, it technically does but there's an issue with the video driver) and when trying to flash it the watch will instantly flash the stock recovery over it upon reboot.
To avoid this we have to do a little workaround! Once you reboot your watch it'll restore the stock recovery again! After following these steps your watch will be stuck in a bootloop which we'll fix too tho.
Please keep the Changelog below in mind and read what's working and what's not before asking. We may or may not have seen this issue before already.
Files you'll need:
v003 of "TWRP for Ticwatch E" (and most likely S) - OneDrive Mirror
Stock Recovery for Ticwatch E (and most likely S) - OneDrive Mirror
ADB and Fastboot drivers installed (I recommend "15 Seconds ADB Installer")
Changelog:
Updated Instructions:
Slightly updated the instructions so you won't lose any data if you're already on an bootloader unlocked watch!
v003 (OneDrive Mirror):
Managed to make TWRP persistent! Check Instructions on how to.
v002 (OneDrive Mirror):
Now includes systemless root package inside the TWRP image so you're able to root your watch!
v001 (OneDrive Mirror):
Initial release, no ADB so far. Can't be booted from fastboot directly either due to weird fastboot behavior and has to be flashed first. However upon normal reboot Mobvoi decided to flash over the stock recovery again so we have to do a workaround.
Instructions:
The new Instructions by Luxios require a few less steps AND if you've already unlocked your watch before you won't even lose data!
Enable ADB in the Developer Settings
Once done connect your watch to your computer and do "adb reboot bootloader"
THIS WILL RESET YOUR WATCH:*Once in fastboot mode type "fastboot oem unlock" (if you already have an unlocked bootloader you [font=Verdana, Arial, Helvetica, sans-serif]can skip this[/font])
Follow the on-screen instructions on your watch to unlock it (if you already have an unlocked bootloader you can skip this)
Reboot via "fastboot reboot" and wait until Android Wear fully starts up
One started reboot to the bootloader via the same command as above
Once the bootloader shows up again type "fastboot flash recovery TWRP_TicwatchE_v003.img"
After that type "fastboot oem reboot-recovery" to reboot to the TWRP recovery
In order to make TWRP persistent you need to go to "Install" > "Install ZIP" > "supersu" > "TicwatchE_TWRP_keeper.zip" and flash it
Upon rebooting you may notice it'll get stuck in an infinite TWRP bootloop. To fix this boot into TWRP, then choose "Reboot" > "Bootloader", back in fastboot type "fastboot boot StockRecovery_TicwatchE.img" and wait a few seconds, a few reboots later Android Wear should start right up again.
If you want to root your watch reboot it once again with "adb reboot recovery" and go to the same folder as above, tho this time flash "SuperSU-2.79-wear_systemless.zip"
Unroot/Remove TWRP for Android O Update:
Go to this thread to also update directly to the last Android O update and revert all customizations: https://forum.xda-developers.com/sm...es/android-o-super-easy-ticwatch-e-s-t3789835
Have fun!
You're the best! I'm gonna try as soon as I can, and let you know.
Ok, I'm trying to flash it.
Problem is, it flashes, but when I do fastboot reboot, it will boot in android wear instead that TWRP.
If then I reboot in the recovery with adb reboot recovery, it will be already the stock recovery again... Any tip?
Piereligio said:
Ok, I'm trying to flash it.
Problem is, it flashes, but when I do fastboot reboot, it will boot in android wear instead that TWRP.
If then I reboot in the recovery with adb reboot recovery, it will be already the stock recovery again... Any tip?
Click to expand...
Click to collapse
If your bootloader is (or was) already unlocked you have to lock and then unlock it again for it to work.
Yes sorry, I noticed that right after posting, but I've bad network.
Now seems to have gone all fine, I'm booting it, I'm only unsure it flashed SuperSU well, since it shown an error at the end of the script, although the rest of the log seemed to report all to go fine.
Piereligio said:
Yes sorry, I noticed that right after posting, but I've bad network.
Now seems to have gone all fine, I'm booting it, I'm only unsure it flashed SuperSU well, since it shown an error at the end of the script, although the rest of the log seemed to report all to go fine.
Click to expand...
Click to collapse
The guy who made it initially did send me a picture of it successfully rooted. Should work, errors can happen since TWRP can't write to all partitions yet.
Sadly it looks like SuperSU failed to root. It gave a data partition mounting error at the end of the script, don't know if it is normal. TWRP isn't able to mount data either.
EDIT: Looks like I found a way to boot TWRP without having to lock/unlock bootloader.
Doing this, I managed to boot TWRP after setting the watch up, and in this way, it didn't fail to mount /data. Let's see...
EDIT2: now SuperSU still fails, but for a different reason. I'm gonna ensure that it failed though.
EDIT3: su command responded, so seems that root works. I'll do some more tests.
TWRP is now persistent! Check the updated guide
Rooting succeeded!
Seems like I managed to root the smartwatch using the version 2. For the moment I'm happy like this, next times I'll indeed use new procedures.
EDIT: Yes, I rooted it.
My steps (the ones on OP are the recommended ones):
-Bootloader unlock;
-Boot in Android Wear to enable ADB from Settings;
-Reboot in bootloader with "adb reboot bootloader";
-Flashed this TWRP v2;
-"fastboot reboot", then "adb reboot recovery" as soon as adb was detected while booting.
In this way I managed to avoid the system to flash stock recovery over TWRP.
By the way, I don't recommend my way of rooting it, it's less safe, just follow the updated instructions in OP.
Huge thanks to @EpicLPer
Wow, this is excellent. I had TWRP built days ago, I went through hell (long story) finding the kernel code and got help from Mobvoi's CTO. I just couldn't get it to boot to recovery. I tried the supplied TWRP, seemed to basically work except for not being able to mount all the partitions. I tried the one I build and I'm in a bootloop. Power button does nothing, we'll see what happened when it loses it's battery. Oh well, will probably order another one anyway.
Thanks for the recovery. I'll resume testing when I get another working device.
BackCheck said:
Wow, this is excellent. I had TWRP built days ago, I went through hell (long story) finding the kernel code and got help from Mobvoi's CTO. I just couldn't get it to boot to recovery. I tried the supplied TWRP, seemed to basically work except for not being able to mount all the partitions. I tried the one I build and I'm in a bootloop. Power button does nothing, we'll see what happened when it loses it's battery. Oh well, will probably order another one anyway.
Thanks for the recovery. I'll resume testing when I get another working device.
Click to expand...
Click to collapse
If the watch doesn't turn off even after holding the button for a minute then you've damaged something else than just the recovery. Holding down the button normally triggers all the time no matter what, even if you'd have bricked it.
BackCheck said:
Wow, this is excellent. I had TWRP built days ago, I went through hell (long story) finding the kernel code and got help from Mobvoi's CTO. I just couldn't get it to boot to recovery. I tried the supplied TWRP, seemed to basically work except for not being able to mount all the partitions. I tried the one I build and I'm in a bootloop. Power button does nothing, we'll see what happened when it loses it's battery. Oh well, will probably order another one anyway.
Thanks for the recovery. I'll resume testing when I get another working device.
Click to expand...
Click to collapse
You can flash again the stock recovery with spflash tool.
EpicLPer said:
If the watch doesn't turn off even after holding the button for a minute then you've damaged something else than just the recovery. Holding down the button normally triggers all the time no matter what, even if you'd have bricked it.
Click to expand...
Click to collapse
I really wish I knew what. All I did was flash a bad recovery, pretty sure something was was wrong with the ram disk. All I get is the splash logo for 3 seconds and a brief vibrate.
Luxios said:
You can flash again the stock recovery with spflash tool.
Click to expand...
Click to collapse
I think I need a scatter file to even get started. I've never used the tool so any other instructions would be greatly appreciated.
Great to hear someone that it is working on this! What about Android Wear updates? Did you try if it is possible to install them using TWRP?
Edit 1: Just tried to install twrp but inside "supersu" folder there is only "SuperSU-2.79-wear_systemless.zip", where can I find "TicwatchE_TWRP_keeper.zip"?
elios93 said:
Great to hear someone that it is working on this! What about Android Wear updates? Did you try if it is possible to install them using TWRP?
Edit 1: Just tried to install twrp but inside "supersu" folder there is only "SuperSU-2.79-wear_systemless.zip", where can I find "TicwatchE_TWRP_keeper.zip"?
Click to expand...
Click to collapse
I have the same problem...
EDIT: I have a Ticwatch S.
Niktendo said:
I have the same problem...
EDIT: I have a Ticwatch S.
Click to expand...
Click to collapse
I've managed to install it anyway. First check if it is not already installed using command
Code:
adb reboot recovery
If it does not work try this after you are in bootloader:
Code:
fastboot flash recovery TWRP_TicwatchE_v003.img
fastboot reboot
Then, as suggested by @Piereligio send this command as soon as possible while the watch is booting:
Code:
adb reboot recovery
This should work
However it is interesting that you have a S model. By sharing the build.prop of your device should be possible unlock all watchfaces for E model for instance!
elios93 said:
I've managed to install it anyway. First check if it is not already installed using command
Code:
adb reboot recovery
If it does not work try this after you are in bootloader:
Code:
fastboot flash recovery TWRP_TicwatchE_v003.img
fastboot reboot
Then, as suggested by @Piereligio send this command as soon as possible while the watch is booting:
Code:
adb reboot recovery
This should work
However it is interesting that you have a S model. By sharing the build.prop of your device should be possible unlock all watchfaces for E model for instance!
Click to expand...
Click to collapse
This is the best way i found to install the TWRP recovery:
- Unlock the boot loader
- Reboot, wait until android start again
- Reboot again in boot loader mode
- flash the twrp v003 recovery
- type:
Code:
fastboot oem reboot-recovery
- Flash the twrp keeper zip package
- flash the root zip package (if you want root)
EpicLPer said:
The guy who made it initially did send me a picture of it successfully rooted. Should work, errors can happen since TWRP can't write to all partitions yet.
Click to expand...
Click to collapse
Can you get me the device tree or at least BoardConfig.mk used for this? I have a working watch (still working on recovering the old one) and I think I can get the rest of the partitions working but I would really like to avoid any more mistakes.
Luxios said:
This is the best way i found to install the TWRP recovery:
- Unlock the boot loader
- Reboot, wait until android start again
- Reboot again in boot loader mode
- flash the twrp v003 recovery
- type:
Code:
fastboot oem reboot-recovery
- Flash the twrp keeper zip package
- flash the root zip package (if you want root)
Click to expand...
Click to collapse
That 'fastboot oem reboot-recovery' command sure is a nice find!
Hey, bought my ticwatch e used online.
The watch is almost new and everything works as it should, but it has these two developer orriented apps preinstalled and can’t be uninstalled via settings neither with a factory reset.
They dont do anything but i just want to remove them
https://photos.app.goo.gl/gTNg5QCPzBtKgnzy1
And yeah the watch also generates a bug report by itself everyday i also want to stop that lol
hassanabid94 said:
Hey, bought my ticwatch e used online.
The watch is almost new and everything works as it should, but it has these two developer orriented apps preinstalled and can’t be uninstalled via settings neither with a factory reset.
They dont do anything but i just want to remove them
https://photos.app.goo.gl/gTNg5QCPzBtKgnzy1
And yeah the watch also generates a bug report by itself everyday i also want to stop that lol
Click to expand...
Click to collapse
Maybe it's a specific developer unit. Don't do anything with it yet, we could loom further into this if it is something special.
Hello,
I am new to phone rooting/modding, this is my first time trying to install a custom ROM (lineageOS) to my OnePlus 8 Pro.
First, I followed this guide for rooting, installing TWRP and then Magisk. The only different thing that I did was, when flashing TWRP, not usingfastboot flash recovery twrp-image-filename.img, but fastboot flash recovery_a/b twrp-image-filename.img, because I read that the former may lead to a boot loop.
Everything worked. Then I proceeded to Install LineageOS on instantnoodlep, where it said I needed to upgrade my stock OS to Oxygen 11/Android 11 first (it came with O10/A10). I did that successfully.
However, it turned out that O11/A11 had overwritten TWRP with the stock recovery. So I flashed TWRP again. This too was successful.
I decided not to install the LineageOS with the LineageOS recovery, as in the official guide, but through TWRP. I copied the LineageOS image to phone memory, booted to TWRP, selected Wipe and did a Factory Reset - Wipes Data, Cache and Dalvik (DID NOT choose Advanced Wipe, probably this was the problem?)
After the reset, I selected the LineageOS ZIP file and installed it.
After booting to system, LineageOS starts loading, but after 4-5 mins I see
QUALCOMM CrashDump Mode
--------------------------------------------------
Panic requested on external modem boot failure
mdm_force_reset
Any help for getting out of this?
It will be MUCH appreciated.
Hi, This Has Happened To Me Before On My Oneplus 8T, you basically have to download this program called msm download tool right HERE (the link is for the oneplus 8 pro) on the link select your filmware region so either: european, international or indian and download it. once you choose that choose either android 10 or 11 then follow this video (In the video the guy is using the oneplus 8t, but it will be the same for the oneplus 8 pro) This Proccess Will Revert Your Device To Stock And Bootloader Will Be Re-Locked, Good Luck! One more thing - you need to download the qualcomm drivers. if you need any more help regarding the msm download tool, booting your device to edl mode or having some issues with the qualcomm driver you can always ask me.
Anyways if you want to re unlock the bootloader you can always reboot into the bootloader and do fastboot oem unlock. Then to flash twrp you can always do fastboot flash recovery (drag and drop the recovery image here) then sideload magisk.zip! Any errors like always tell me.
MaybeDontAsk said:
Anyways if you want to re unlock the bootloader you can always reboot into the bootloader and do fastboot oem unlock. Then to flash twrp you can always do fastboot flash recovery (drag and drop the recovery image here) then sideload magisk.zip! Any errors like always tell me.
Click to expand...
Click to collapse
The unlock command would be:
Code:
fastboot flashing unlock
Thanks for the suggestions, I will try them when I get to my home PC, I'm at work now.
In the meantime: can someone explain to me what is the exact procedure for installing LineageOS with the latest TWRP image? More specifically, which options in "Advanced Wipe" should be checked, because in all the tutorials I found they were using old versions of TWRP which did not include the "system" option. Mine had it, so I decided not to use Advanced Wipe at all and use the default wipe options (this is also what they did in one of the tutorials). Could this be the cause for the crash dump error?
Also, I am kind of reluctant to re-lock the bootloader and go back to stock OxygenOS. I still have access to the (LineageOS) recovery mode (it overwrote TWRP). Can I try doing something from there, like maybe overwriting it with TWRP again, then wiping everything (the right way) and installing LineageOS again?
Well when ever I get a Qualcomm crash dump error I always like to go back to stock and re do everything fresh just in case something else goes wrong but if you just don't wanna go back to stock you can do this:
If you wanna overwrite lineage os recovery you can reboot into the bootloader, and just do fastboot flash recovery (drag and drop twrp image here)
So it will be something like:
Code:
fastboot flash recovery C:\Users\YourUsername\Desktop\(recovery name).img
Or if you have the twrp image in the same place at platform-tools you can do:
Code:
fastboot flash recovery (recovery.img)
Or a one time twrp boot:
Code:
fastboot boot C:\Users\YourUsername\Desktop\(recovery name).img
Or:
Code:
fastboot boot (recovery name).img
But like I said it's probably better to re-lock the bootloader to start fresh then you can unlock it again and do anything else. Good Luck.
Anyways in TWRP Navigate To:
Wipe>Advanced Wipe> Dalvik/Cache>Data>swipe to wipe
Go back to TWRP home
Advanced>Adb Sideload
Now in PC cmd do:
Code:
adb sideload (drag and drop lineage os zip here)
Hit Enter And Wait Until It Finishes Flashing
Now For The Google Apps (GAPPS):
Download Nik GAPP From:
NikGApps - Custom Google Apps Package!
NikGapps Website
nikgapps.com
Select "Download"
Then look through all packages and read what each one contains, I would go with either core or basic. But you may need another apps so just read and choose.
Once you choose, click "download now"
Navigate To Folder
Releases>NikGAPPS R if lineage is 18.1(Android 11)>Latest Version>then choose from here and download.
Back to TWRP
If the download for gapps Finished:
Navigate to:
Advanced>adb sideload
Back On CMD:
Flash Gapps:
Code:
adb sideload (drag and drop NikGAPPS zip)
once it finishes:
On TWRP go back to home menu and navigate to:
Wipe>Format Data>Type "yes">Hit Enter>Go Back To TWRP Menu>Reboot>System if it says "no rom is installed" just swipe to confirm reboot, Lineage OS Is Actually Already Flashed. Good Luck!
I know this is long but it's really not lol.
@MaybeDontAsk
Thanks a lot! I will try again via TWRP first. I don't want to re-lock the bootloader just yet, because I fear something may go wrong in the process and I may end up with a bricked phone AND a locked bootloader, and that will really be the worst scenario, from what I've read in forums.
As for the GAPPS part - I don't plan to install them. Just a LineageOS image will be fine.
Alright well hope everything goes well and yeah I also feared I may end up bricking my device with the msm download tool but I've already done it multiple times.
It has fixed a lot of issues for me wether it is that the device is booting straight into recovery or fastboot or that it's not even booting up!
Just something about TWRP: when I tried just booting to it, the phone froze on the "Fastboot Mode" splash screen and stopped there. So I had to use the flash option.
Also, about flashing: I should use
Code:
fastboot flash recovery (recovery.img)
and not
Code:
fastboot flash recovery_a (recovery.img)
fastboot flash recovery_b (recovery.img)
right?
Just double checking to make sure.
Unfortunately, Wipe failed. In Advanced Wipe i chose
- Dalvik/ART Cache
- Data
and left Metadata, Internal Storage and USB OTG unchecked. (In my above post, I wrote I had "system", I meant I had Metadata instead of System in the options list).
Anyway, this is what I got:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I forgot to mention I did a full backup before my first wipe. Should I try to restore from it now?
freeride01 said:
Unfortunately, Wipe failed. In Advanced Wipe i chose
- Dalvik/ART Cache
- Data
and left Metadata, Internal Storage and USB OTG unchecked. (In my above post, I wrote I had "system", I meant I had Metadata instead of System in the options list).
Anyway, this is what I got:
View attachment 5543241
I forgot to mention I did a full backup before my first wipe. Should I try to restore from it now?
Click to expand...
Click to collapse
I suggest to do msm download right now. It will fix every error, plus it doesn't even take long to re unlock bootloader you can just skip through the setup without wifi or Google account, no lock screen fingerprint or pin, then just enable oem unlock and reboot to bootloader unlock the bootloader then you don't need to to do setup again since you can just reboot to bootloader when its wiping by pressing volume up and down + power button then flash twrp and flash lineage or any other custom rom for the op8p.
MaybeDontAsk said:
I suggest to do msm download right now. It will fix every error, plus it doesn't even take long to re unlock bootloader you can just skip through the setup without wifi or Google account, no lock screen fingerprint or pin, then just enable oem unlock and reboot to bootloader unlock the bootloader then you don't need to to do setup again since you can just reboot to bootloader when its wiping by pressing volume up and down + power button then flash twrp and flash lineage or any other custom rom for the op8p.
Click to expand...
Click to collapse
Alright.
I gotta find a Windows PC though, I am on Linux/Fedora.
My OxygenOS before the wipe was 11.0.10.10.IN11BA, I guess from the list I should download "OOS 11.0.4.4", because its the latest.
I'll post again when there is some progress.
MaybeDontAsk said:
Hi, This Has Happened To Me Before On My Oneplus 8T, you basically have to download this program called msm download tool right HERE (the link is for the oneplus 8 pro) on the link select your filmware region so either: european, international or indian and download it. once you choose that choose either android 10 or 11 then follow this video (In the video the guy is using the oneplus 8t, but it will be the same for the oneplus 8 pro) This Proccess Will Revert Your Device To Stock And Bootloader Will Be Re-Locked, Good Luck! One more thing - you need to download the qualcomm drivers. if you need any more help regarding the msm download tool, booting your device to edl mode or having some issues with the qualcomm driver you can always ask me.
Click to expand...
Click to collapse
OK, I got my hands on a Windows 10 PC. I downloaded and extracted the MSM tool and watched the video you linked.
There is no Win7 version of the .exe file, so I guess I'll use the "normal" one anyway.
Yes, my phone is unbricked! Thank you VERY much!
Now, I still want to use LineageOS instead of OxygenOS. I will follow the same procedure and then your instructions for installing LineageOS via TWRP (with sideload instead of Install). I'll post about the result.
One thing that's still kind of unclear to me though. Is there any difference if I flash TWRP with the recovery or the recovery_a and recovery_b options?
freeride01 said:
Yes, my phone is unbricked! Thank you VERY much!
Now, I still want to use LineageOS instead of OxygenOS. I will follow the same procedure and then your instructions for installing LineageOS via TWRP (with sideload instead of Install). I'll post about the result.
One thing that's still kind of unclear to me though. Is there any difference if I flash TWRP with the recovery or the recovery_a and recovery_b options?
Click to expand...
Click to collapse
Hello, I am glad I was able to help you anyways I just recommend using recovery since I think if you do _a or _b you need to be on that partition so just do recovery so you can boot into twrp no matter on what partition you are in.
MaybeDontAsk said:
Hello, I am glad I was able to help you anyways I just recommend using recovery since I think if you do _a or _b you need to be on that partition so just do recovery so you can boot into twrp no matter on what partition you are in.
Click to expand...
Click to collapse
Hi again,
I did the whole process again and when I did adb sideload I got this:
Code:
[[email protected] phone root]$ adb sideload lineage-18.1-20220214-nightly-instantnoodlep-signed.zip
adb: sideload connection failed: closed
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: closed
Now what? There's a slide in TWRP that says "Swipe to start sideload", should I swipe it?
EDIT: Maybe Ishould use adb install as described here?
No, you need to reinstall the adb interface drivers, search up on how to do it on Linux.
Tht link you put is for installing apk directly from adb and not roms.
But adb seems to work, adb devices returns my phone ID.
It says something like "(Device ID) | Sideload?
If yes then reboot both the laptop/pc and phone.
Code:
[[email protected] phone_root]$ adb devices
List of devices attached
19356f32 recovery
(changed some digits in serial no. for privacy)