Database Info

[Q] Rooting the 3G Xoom (Stock 3.2) with CWM - error 0x120000

Hi folks,
atm I feel like a complete newb because I cant manage to root my xoom according to http://forum.xda-developers.com/showthread.php?t=1074979 with fastboot. (Can't flash through cwm since the device is stock 3.2)
What I have:
Motorola Xoom EU 3G (MZ601)
Android Version 3.2
Kernel 2.6.36.3
Firmware GAS_EMEA_USAEVRSTUTMDE_P016
What doesn't work:
As soon as I try to flash recovery my almighty command line says:
Code:
>fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
sending 'recovery' (3998 KB)...
OKAY [ 0.490s]
writing 'recovery'...
FAILED (command write failed (Unknown error))
finished. total time: 1.103s
My xoom shows "Starting Fastboot protocol support" as if nothing happened.
When I try to issue the command again immediatly, the error changes to:
Code:
>fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
sending 'recovery' (3998 KB)...
FAILED (remote: (00120000))
finished. total time: 0.274s
The xoom is showing "Failed to process command error(0x120000)".
Here is what I've done so far, aside from following the post mentioned above including all tipps in that thread.
tried three different cables for connecting the xoom to my PC, including the original one.
tried two different computers with three different OSs (x64 only so far)
tried to flash the image immediatly after the oem unlock without booting into system
tried everey single usb port on every system
tried updating chipset drivers as well as the usb drivers
I don't know what to try next. Could someone please give me a hint what to try next? I'm stuck here.
Thanks in advance & thanks for reading, Jan

jan_goose said:
Here is what I've done so far, aside from following the post mentioned above including all tipps in that thread.
tried three different cables for connecting the xoom to my PC, including the original one.
tried two different computers with three different OSs (x64 only so far)
tried to flash the image immediatly after the oem unlock without booting into system
tried everey single usb port on every system
tried updating chipset drivers as well as the usb drivers
I don't know what to try next. Could someone please give me a hint what to try next? I'm stuck here.
Thanks in advance & thanks for reading, Jan
Click to expand...
Click to collapse
Have you tried to check the md5-checksum of the image file?

llama-power said:
Have you tried to check the md5-checksum of the image file?
Click to expand...
Click to collapse
Hi, indeed, I forgot that. I've checked it and they are matching, so no luck here.
Does someone know if maybe 64bit systems could cause problems? (And what to do aside from buying a new PC ^^)

jan_goose said:
Hi, indeed, I forgot that. I've checked it and they are matching, so no luck here.
Does someone know if maybe 64bit systems could cause problems? (And what to do aside from buying a new PC ^^)
Click to expand...
Click to collapse
well, they could but on my 64bit system everything worked out fine. You could try installing a 32 bit OS, as your computer is likely compatible to that. I don't, however, believe that would do any good as it looks like your computer is doing what it should, only your xoom isn't... (to me, it looks like your computer is sending the file just fine but the xoom just doesn't want to flash that file to memory)...
what does fastboot getvar all return?

llama-power said:
what does fastboot getvar all return?
Click to expand...
Click to collapse
A command I wasn't aware of, thanks.
While charging, it says:
Code:
(bootloader) version-bootloader: 1049
(bootloader) product: xoom-cdma
(bootloader) secure: yes
(bootloader) model: MZ600
(bootloader) memory-info: 0x101:0x5454:0
(bootloader) mid: 001
(bootloader) version: 0.4
(bootloader) serialno: 037C710041XXXX
(bootloader) version-baseband: N_01.100.05P
(bootloader) version-baseband-2:
(bootloader) battery-status: 45%:7.847V:0.869A:21.37C
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
I'm a bit confused because it says "MZ600", but according to the tablet info when android has booted it is a MZ601.
I'm living in germany, where I've also bought the device and it's got a 3g module which i'm actually using.

jan_goose said:
While charging, it says:
Click to expand...
Click to collapse
did you just omit the (bootloader) iswarrantyvoid: yes or did that really not appear? Apart from that, everything looks just like on my device... Thus, I am officially out of ideas... I'd offer to have a look at your device next week as I'll be in your location then but I currently don't see how that would do any good...
jan_goose said:
I'm a bit confused because it says "MZ600", but according to the tablet info when android has booted it is a MZ601.
Click to expand...
Click to collapse
yeah, that distracted me at first too, but a friends MZ601 which is neither rooted nor unlocked, says the same, so I think thats fine...
Anyhow... sorry, no clue what's wrong with your device...:-(
can you flash a the recovery image from Motorola?

llama-power said:
can you flash a the recovery image from Motorola?
Click to expand...
Click to collapse
Actually, I couldn't.
I didn't even try before. This simple question of yours emerged something like a nerdrage from deep inside.
I looked sternly at my xoom and decided that I won't go down first.
Well, the rest was luck, but since I've tried it multiple times and it worked, here are the steps:
Start slowly with these lines (I know them by heart by now)
Code:
adb reboot bootloader
fastboot flash recovery recovery-solarnz-XXXXXX-XXXX.img
It will fail. Do the last line again, it will show error 0x120000.
Now you have to be quick as soon as you submitted the next line:
Code:
fastboot reboot
Unplug your device from the PC and start hitting the Volume down button immediatly (this means: do not tap and hold, press it multiple times) until the display says fastboot is ready .
Now re-plug the xoom to the PC again and re-do this:
Code:
fastboot flash recovery recovery-solarnz-XXXXXX-XXXX.img
This time, everything goes well.
If, like me, you are coming from stock, don't forget you must not reboot to system again, but directly to recovery and install something like Team EOS ROM.
I have no clue why it worked, but since I was so fascinated that I've tried it three times I guess one could say it's reproducable.
Good night and thanks to llama-power for being inspirational.

wow
jan_goose said:
Actually, I couldn't.
I didn't even try before. This simple question of yours emerged something like a nerdrage from deep inside.
I looked sternly at my xoom and decided that I won't go down first.
Well, the rest was luck, but since I've tried it multiple times and it worked, here are the steps:
Start slowly with these lines (I know them by heart by now)
Code:
adb reboot bootloader
fastboot flash recovery recovery-solarnz-XXXXXX-XXXX.img
It will fail. Do the last line again, it will show error 0x120000.
Now you have to be quick as soon as you submitted the next line:
Code:
fastboot reboot
Unplug your device from the PC and start hitting the Volume down button immediatly (this means: do not tap and hold, press it multiple times) until the display says fastboot is ready .
Now re-plug the xoom to the PC again and re-do this:
Code:
fastboot flash recovery recovery-solarnz-XXXXXX-XXXX.img
This time, everything goes well.
If, like me, you are coming from stock, don't forget you must not reboot to system again, but directly to recovery and install something like Team EOS ROM.
I have no clue why it worked, but since I was so fascinated that I've tried it three times I guess one could say it's reproducable.
Good night and thanks to llama-power for being inspirational.
Click to expand...
Click to collapse
i tried your method did not work i was also getting the error code what worked was using [Recovery] EOS recovery (R6) CWM Based and it pushed thru fastboot no problem just a heads up

Just to confirm...
jan_goose said:
A command I wasn't aware of, thanks.
While charging, it says:
Code:
(bootloader) version-bootloader: 1049
(bootloader) product: xoom-cdma
(bootloader) secure: yes
(bootloader) model: MZ600
(bootloader) memory-info: 0x101:0x5454:0
(bootloader) mid: 001
(bootloader) version: 0.4
(bootloader) serialno: 037C710041XXXX
(bootloader) version-baseband: N_01.100.05P
(bootloader) version-baseband-2:
(bootloader) battery-status: 45%:7.847V:0.869A:21.37C
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
I'm a bit confused because it says "MZ600", but according to the tablet info when android has booted it is a MZ601.
I'm living in germany, where I've also bought the device and it's got a 3g module which i'm actually using.
Click to expand...
Click to collapse
Did you verify if that information is correct? I get the same info from fastboot

Onedroidev said:
Did you verify if that information is correct? I get the same info from fastboot
Click to expand...
Click to collapse
I have no idea why the information seems to be wrong, but obviously it can be ignored, at least in my case.
As long as you've got a 3G module, it is not a MZ600, regardless what fastboot is saying.

[Q] No bootloader + relocked device [SOLVED]

Hello, first excuse me for my english , i'll try to be clear as possible.
I get a tf700t with bootloader trouble, i tought that it be easy to repair.
On the screen with asus logo there's write ''the device is unlocked'' then the owner told me CWM was installed on.
But when i try to go to recovery section (RCK) i have
Booting Recovery kernel image
Booting failed
Unrecovarable bootloader error (0x00000000)
Cannot go to cold boot too, it load nothing (bootloop).
I have fastboot but i cannot flash anything on it:
C:\adt-bundle-windows-x86_64-20130729\sdk\platform-tools>fastboot getvar all(bootloader) version-bootloader: 1.0 (bootloader) version-baseband: 2.0
(bootloader) version: 0.4
(bootloader) serialno: 015d29955e67ec09
(bootloader) mid: 001
(bootloader) product: Cardhu
(bootloader) secure: yes
(bootloader) unlocked: no
(bootloader) partition-size:bootloader: 0x0000000000800000
(bootloader) partition-type:bootloader: emmc
(bootloader) partition-size:recovery: 0x0000000000800000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:boot: 0x0000000000800000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:system: 0x0000000030000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 0x000000001ac00000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:userdata: 0x00000006e5680000
(bootloader) partition-type:userdata: ext4
all:
finished. total time: 0.082s
Click to expand...
Click to collapse
And tying to wipe give me the same error message than the RCK.
And so my question is, will i be able to use fastboot or something else to flash recovery, boot,etc...
Thanks

Can you tell us your bootloader version (you can see it when booting with Volume Down + Power)?

Pretoriano80 said:
Can you tell us your bootloader version (you can see it when booting with Volume Down + Power)?
Click to expand...
Click to collapse
cardhu-user bootloader 1.00 e released by ww_epad-10.4.4.25

Acem31 said:
cardhu-user bootloader 1.00 e released by ww_epad-10.4.4.25
Click to expand...
Click to collapse
Have a look here - - > http://forum.xda-developers.com/showthread.php?t=2179759 <-- some users were able to recover from similar issue.
Be aware that the thread is for the TF300T so make sure you download the firmware for the TF700T if you decide to try that procedure.

Pretoriano80 said:
Have a look here - - > http://forum.xda-developers.com/showthread.php?t=2179759 <-- some users were able to recover from similar issue.
Be aware that the thread is for the TF300T so make sure you download the firmware for the TF700T if you decide to try that procedure.
Click to expand...
Click to collapse
Yup, i have all .img/.blob made for the tf700t.
I'll look the thread, and reply to give results, hope it will work.

Well, it work fine, indeed i think i'll soon make a tuto for those ho have the same problem, it should be usefull.
So, i recovered my bootloader, my recovery, then now i'll ty to install the stock rom, but my external SD i not recognize by the tf700t.
It should be easy to fix it. When it's done, i'll mark the thread like solved.
Your help was really usefull @Pretoriano80 !!

Acem31 said:
Well, it work fine, indeed i think i'll soon make a tuto for those ho have the same problem, it should be usefull.
So, i recovered my bootloader, my recovery, then now i'll ty to install the stock rom, but my external SD i not recognize by the tf700t.
It should be easy to fix it. When it's done, i'll mark the thread like solved.
Your help was really usefull @Pretoriano80 !!
Click to expand...
Click to collapse
Glad you managed to recover it.

Well it's harder to fix it. TWRP is unable to mount /System /Sdcard etc
Then i cannot use adb sideload with TWRP & CWM, so i'm still unable to put the rom on the devices.
An idea? I googled it, i didn't find any issue. I probably missed something :/

Well, i know what i miss.
When i turn on the device, i can see "this device is unlocked" or somethin like that.
But with:
fastboot getvar all
I have "unlocked: no" , that's why i'm unable to write any ROM on the system part.
The only way i know to re unlock, is using the ASUS unlock apk, but without any system installed...
Will i be able to unlock, or do something else to get the STOCK back?

It's impossibile that you locked the bootloader, so far there's no way to do it, not for end-users at least.
Edit: Have you tried to push the stock recovery via fastboot?
---------- Post added at 06:58 PM ---------- Previous post was at 06:51 PM ----------
You could try this:
1) Dowload the latest firmware from Asus site and extract the blob file to the same location where fastboot.exe is located
2) Boot device in fastboot mode then...
3) fastboot -i 0x0B05 flash staging blob
4) after sending and writing process is done restart with " fastboot -i 0x0B05 reboot"
If everything goes as expected you should have a full Asus firmware installed (and stock recovery)

Acem31 said:
fastboot getvar all
I have "unlocked: no" , that's why i'm unable to write any ROM on the system part.
Click to expand...
Click to collapse
Sounds reasonable, but mine also says "unlocked: no" and I have no problems flashing stuff.

Pretoriano80 said:
It's impossibile that you locked the bootloader, so far there's no way to do it, not for end-users at least.
Edit: Have you tried to push the stock recovery via fastboot?
---------- Post added at 06:58 PM ---------- Previous post was at 06:51 PM ----------
You could try this:
1) Dowload the latest firmware from Asus site and extract the blob file to the same location where fastboot.exe is located
2) Boot device in fastboot mode then...
3) fastboot -i 0x0B05 flash staging blob
4) after sending and writing process is done restart with " fastboot -i 0x0B05 reboot"
If everything goes as expected you should have a full Asus firmware installed (and stock recovery)
Click to expand...
Click to collapse
Huumm unexpected issue? When it restart, first it stay on the asus logo, so i press power + vol down to go fastboot and there, no more fastboot icon, but fastboot start directly(i still can choose RCK , Cold boot & wipe data)
Also, i have
"Key driver not found..booting OS"
I will retry as long as i have fastboot

Acem31 said:
Huumm unexpected issue? When it restart, first it stay on the asus logo, so i press power + vol down to go fastboot and there, no more fastboot icon, but fastboot start directly(i still can choose RCK , Cold boot & wipe data)
Also, i have
"Key driver not found..booting OS"
I will retry as long as i have fastboot
Click to expand...
Click to collapse
That's normal, it means that fastboot mode it's ON. No more USB icon in bootloader menu.
Inviato dal mio ASUS Transformer Pad TF700T con Tapatalk 4
---------- Post added at 07:20 PM ---------- Previous post was at 07:19 PM ----------
What happens when you choose RCK? You end-up with a dead Android?
Inviato dal mio ASUS Transformer Pad TF700T con Tapatalk 4
---------- Post added at 07:27 PM ---------- Previous post was at 07:20 PM ----------
And btw mate, give us more info... did you followed my advice, flash went good, wich bootloader version it shows now. This details could save your device and wrong info could brick it.
So far mh understanding is that the flash went fine but for some odd reason it doesn't boot the OS. I guess one of the reasons is because you switched from 4.1 to 4.2.1 so some old data is stopping the device from booting...just my wild guess.
Inviato dal mio ASUS Transformer Pad TF700T con Tapatalk 4

OFF TOPIC: where are you come from in italia?
The command running, as soon as it finish i'll tell you the result.

Acem31 said:
OFF TOPIC: where are you come from in italia?
The command running, as soon as it finish i'll tell you the result.
Click to expand...
Click to collapse
Yes,Rome-Italy.If the command is running at some point you should see a blu bar filling slowly.

Pretoriano80 said:
Yes,Rome-Italy.If the command is running at some point you should see a blu bar filling slowly.
Click to expand...
Click to collapse
Well, next time i'll go to calabria to see my cousin, i'll stop in Roma to make you a huge kiss! It works!
BIG BIG BIG BIG thanks! I'll mark the topic as resolved!
Grazie!

Acem31 said:
Well, next time i'll go to calabria to see my cousin, i'll stop in Roma to make you a huge kiss! It works!
BIG BIG BIG BIG thanks! I'll mark the topic as resolved!
Grazie!
Click to expand...
Click to collapse
No problem mate,i'm glad it's up and running again.
Edit: And you could use the "thanks" button too

[Q&A] [MOD] OnePlus One Unlocker: Reset Unlock & Tamper Bit

Q&A for [MOD] OnePlus One Unlocker: Reset Unlock & Tamper Bit
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:

Thank you so much!!!!!!!
This solved my problem like a charm!

bootloader
bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.005s]

bootloader locked twrp recovery specific problem
Hello. I did post my problem on OPO forum but didnt found my answer. Iwil try here now
As answer for your questions in 1st post:
1) yes i did unlock by bootloader before.
2) I am running twrp recovery now (and thats the only thing left on my OnePlus One no Os)
3) (bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.016s]
finished. total time: 0.016s
4) E:\One plus one\2222\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (5560 KB)...
OKAY [ 0.168s]
writing 'boot'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.186s
5) well basicly i tried everything including your method... i am trying to fix this for 2 days now. Ill just describe whats happening when i try to do your method in different ways because seems like your method is the solution for my phone the only thing is how to make it to work...
first off all when i tried to push that file thru adb push command nothing was apppering on my phone...
than i bought my usb otg cable and connected usb stick with that file... it helped because my phone saw that file and i could instal it... but when i tried to instal it thru TWRP it was saying that
MD5 check sum is wrong and instalation failed...
Today i tried siedeload that file thru "adb sideload ..." command and
E:\One plus one\2222\adt-bundle-windows-x86_64-2014702\sdk\platform-tools>adb sideload OnePlusOne-Bootunlocker.zip
error:closed
error:closed
Hope this is clear enough plzzzz help i want my OPO back tho i bought it like 3 weeks
Thx for any answers ...
OKi downloaded difeerent file and MD5 sum was alright this time... sorry for trouble and thx for fixing my problem

Thx guys for restoring my OPO all is working fine i have back to stock phone and 38r thru automatic update 1 more time thx and cheers. Good job

Fastboot flash
If I want to flash via fastboot, in which state the Unlock Bit and Tamper Bit have to be?
Im trying to flash stock 38r, and im getting the error that device not unlocked. Tried to unlock with fastboot oem unlock, but when i flash the stock rom, im getting that error.
Thanks.

I got this question too!

The script does not work, I have tested on XNPH22R and XNPH33R it always remains
Device tampered: true
Device unlocked: false
probably the tamper go to true when you lock the bootloader
it might work a script that lock the bootloader and reset the tampe at the same time

Can't UNlock boot loader
I have a locked bootloader and nothing i try is unlocking it.
background, i rooted and tried to go back to start. Now when my phone turns on i get the system ui error non stop. So i'm hoping to unlock bootloader and reflash stock rom.
Device Tampered: true
device unlocked: false
from here, i don't have a clue what to do.

Can't unlocked boot loader
Hi there, I believe I messed my phone while trying to root and install twrp recovery. Now I can't run "oem unlock" to unlock my phone, I can't go to recovery, the only thing I can get into is FASTBOOT mode. Here is my screen shoot , please take a look and let me know what should I do . I downloaded Boot Unlocker from your post, but don't know how to flash it since I can't run "boot recovery twrp.img"
Please take a look at my attachment .
Thanks

pablikowskipablik said:
Hello. I did post my problem on OPO forum but didnt found my answer. Iwil try here now
As answer for your questions in 1st post:
1) yes i did unlock by bootloader before.
2) I am running twrp recovery now (and thats the only thing left on my OnePlus One no Os)
3) (bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.016s]
finished. total time: 0.016s
4) E:\One plus one\2222\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (5560 KB)...
OKAY [ 0.168s]
writing 'boot'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.186s
5) well basicly i tried everything including your method... i am trying to fix this for 2 days now. Ill just describe whats happening when i try to do your method in different ways because seems like your method is the solution for my phone the only thing is how to make it to work...
first off all when i tried to push that file thru adb push command nothing was apppering on my phone...
than i bought my usb otg cable and connected usb stick with that file... it helped because my phone saw that file and i could instal it... but when i tried to instal it thru TWRP it was saying that
MD5 check sum is wrong and instalation failed...
Today i tried siedeload that file thru "adb sideload ..." command and
E:\One plus one\2222\adt-bundle-windows-x86_64-2014702\sdk\platform-tools>adb sideload OnePlusOne-Bootunlocker.zip
error:closed
error:closed
Hope this is clear enough plzzzz help i want my OPO back tho i bought it like 3 weeks
Thx for any answers ...
OKi downloaded difeerent file and MD5 sum was alright this time... sorry for trouble and thx for fixing my problem
Click to expand...
Click to collapse
--------------------------------
HI , my problem is exactly like your, can you tell me how did you solve it please ?

Oneplus tamper flag
I am trying to set my tamper flag on my Oneplus to false, but I can't seem to get both to stay false. I am on 38R and following the instructions from here to flash back stock rom and recovery. And here to reset tamper flags. I can't seem to get the device tampered flag to false. Instead I get this
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
What am I doing wrong. Thanks

paralaxx said:
I am trying to set my tamper flag on my Oneplus to false, but I can't seem to get both to stay false. I am on 38R and following the instructions from here to flash back stock rom and recovery. And here to reset tamper flags. I can't seem to get the device tampered flag to false. Instead I get this
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
What am I doing wrong. Thanks
Click to expand...
Click to collapse
Why does it matter? It doesn't affect your warranty or anything.
Transmitted via Bacon

timmaaa said:
Why does it matter? It doesn't affect your warranty or anything.
Transmitted via Bacon
Click to expand...
Click to collapse
I thought have the tamper flag as True voids warranty no? Plus, I am trying to contact customer service for a problem I have and knowing OnePlus I don't want to give them any excuses for fixing my phone.

paralaxx said:
I thought have the tamper flag as True voids warranty no? Plus, I am trying to contact customer service for a problem I have and knowing OnePlus I don't want to give them any excuses for fixing my phone.
Click to expand...
Click to collapse
Not sure where you got that information but it's incorrect. Unlocking the bootloader trips the tamper but neither void your warranty.
Transmitted via Bacon

Tampered - TRUE
--------------

Hello guys! I'm wondering why my brand new, out of box OPO had tamper flag set to TRUE?? I was just updated to 38R through OTA and went to fastboot and checked with device-info... It was the first command I ever used in fastboot so how is that possible?

THANK YOU!
That really worked, same happened to me and I have been over a day reading and trying to put this to work! thank you

Locked Bootloader
Hi Mate's !!
I am facing same problem. my boot loader is locked i tried
Fastboot oem device-info (It give)
(bootloader) Device tempered:true
(bootloader) Device Unlock:false
(bootloader)Charger screen enable: false
Okey[0,005s]
Then i try
Fastboot oem unlock (It restart the phone in recovery mode) but device gives same info
(bootloader) Device tempered:true
(bootloader) Device Unlock:false
I also tried to bootloaderunlocker.zip by sideload but result is installation failed due to signature verification
Help me
Thanks in advance

Oneplus one Tamper bit
Hi,
Just got a quick question I was looking into flash android lollipop onto my opo deceive but wanted to do a little research before starting. I saw this post on the tamper bit and unlock script. I thought I would see what my "fastboot oem device-info" was as I have not unlock this device before. To my surprise the tamper bit came back true and the unlock bit came back false. I'm curious how this could be if I have never unlocked the device? If anyone could shed some light on this that would be great. Thanks in advance.

[help] oneplus dead randomly?

Hey guys,
before i finally give up on this phone and throw it in the bin, my oneplus phone randomly rebooted while i was using it, while it rebooted it just froze on the cyanogen screen, i powered it off and powered it back on and it still boots up to cyanogen screen.
now here is the weird part, i have tried every fix available on xda, reddit, and the official oneplus forums. i have tried to factory reset, wipe cache+ media, tried to fastboot oem unlock but it doesn't seem to do anything.
iv installed every thing to the tee ( drivers etc) tried different cables. i just think this phone has randomly died outta the blue for no reason(3months), RMA is not an option as i voided the warranty after replacing the oneplus screen my self when it cracked.
i didn't have root and had the CM stock recovery.
i had encryption enabled,
the last thing i did was transfer files to my phone approx 15 mins later it just died.

What do you get when giving this fastboot command?
Code:
fastboot oem device-info
XDA Moderator
Transmitted via Bacon

Heisenberg said:
What do you get when giving this fastboot command?
Code:
fastboot oem device-info
XDA Moderator
Transmitted via Bacon
Click to expand...
Click to collapse
C:\adb>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.006s]
finished. total time: 0.006s

21gunSALUTE said:
C:\adb>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.006s]
finished. total time: 0.006s
Click to expand...
Click to collapse
Ok, have you tried this yet?
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732

Heisenberg said:
Ok, have you tried this yet?
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
Click to expand...
Click to collapse
yes i have, what happens is it shows up as COM then
when i click start the green bar starts then half way it goes off then my device reboots with the sound of windows going dun dun it doesn't show up in device manager after.

21gunSALUTE said:
yes i have, what happens is it shows up as COM then
when i click start the green bar starts then half way it goes off then my device reboots with the sound of windows going dun dun it doesn't show up in device manager after.
Click to expand...
Click to collapse
What build of CM were you running?

Heisenberg said:
What build of CM were you running?
Click to expand...
Click to collapse
CM12.
the thing is i cant seem to factory wipe the phone as well, when i clear/wipe it would go to the android man but it would be flashing few times before it goes back to menu.

21gunSALUTE said:
CM12.
the thing is i cant seem to factory wipe the phone as well, when i clear/wipe it would go to the android man but it would be flashing few times before it goes back to menu.
Click to expand...
Click to collapse
I'm stumped unfortunately. My thought is that you potentially have a spontaneously corrupt persist partition (it's more common than you might want to believe), but you can't fix that with a locked bootloader, and you don't seem to be able to unlock your bootloader. Check this automated tool, it might have success in unlocking your bootloader (probably not but it's worth a try):
http://forum.xda-developers.com/showthread.php?t=2970390

Heisenberg said:
I'm stumped unfortunately. My thought is that you potentially have a spontaneously corrupt persist partition (it's more common than you might want to believe), but you can't fix that with a locked bootloader, and you don't seem to be able to unlock your bootloader. Check this automated tool, it might have success in unlocking your bootloader (probably not but it's worth a try):
http://forum.xda-developers.com/showthread.php?t=2970390
Click to expand...
Click to collapse
its ok thanks for trying to help, i have done this before but ill do it again.

installing TWRP and rooting Asus Zenpad 10 (Z300m)

THIS THREAD IS NO LONGER UNDER DEVELOPMENT, FOR FUTURE UPDATES PLEASE HEAD HERE.
Flashing TWRP and Rooting the Asus Zenpad 10 (Z300M)
CREDIT: Diplomatic, JustShaun, and Flukester69 all made this possible. But really if anybody needs an applause, it's Diplomatic. If you wish to thank him you can do so here.
IMPORTANT! READ BEFORE CONTINUING!
Nobody here is responsible if you mess up your tablet! This is your decision and yours alone! Yes, this will void your Warranty! The below is based on the success of our own testing. We suggest reading this multiple times if necessary, before attempting. Ask questions if you are unsure, I'm sure someone will try and help.
Things you'll need:
- Windows computer / possibly Linux if you are savvy enough.
- Z300m with Android 7 (check if there's updates, if so, reboot tablet when done.)
- USB Cable (the one that came with it, or one you are sure works)
- MediaTek VCOM Preloader Drivers (I will explain further below) (Win10 installed drivers work too)
- Z300m Scatter File
- TWRP 3.1.1 image
- SP Flash Tool 5.1532
- SP Flash Tool 5.1548 or later (latest is 5.1720 at the time of this writing)
- Magisk Manager (Beta 13 works)
or
- TWRP 3.1.1 Recoveryasboot
Create a temp folder on your desktop and throw all the above downloads in there.
MTK Driver Install - Pre-Flashing Procedure:
Turn your tablet OFF and plug it in to your computer, Windows should recognize the device and download the drivers. You should be able to manually search through device manager (Turn on Hidden devices might be necessary). When the drivers have been downloaded feel free to unplug the tablet again.
You'll want to make sure the drivers are installed properly. A quick way to test,
Open Device Manager by either searching for it or running 'devmgmt.msc'
Turn on hidden devices.
Expand the 'Ports (COM & LPT) section
If the drivers are installed properly you should see 'MediaTek PreLoader USB VCOM Port (COM*)'
Good enough, if that worked. If not, check your device manager and figure out your driver issue.
Backing Up:
Open the SPFL (latest) dir and open option.ini in any text editor, you'll want to change "[ReadBack] ShowByScatter=false" from false to true and save your changes.
Load into flash_tool.exe.
Change the download-agent from MTK_AllInOne_DA.bin to DA_PL.bin - This is located under the SPFL dir.
Add the Scatter-loading file which should have been downloaded previously.
Head into the Readback tab and you should see 'Preloader, pgpt, proinfo ect...'. Check all of these boxes and click Read Back
Make sure the tablet is turned off and then plug it into your computer. Bar goes red, yellow and then done. Green Checkmark.
It's safe to unplug the USB from the tablet now and you can close the Flash Tool
Flashing TWRP:
It's up to you to backup your tablet. You should, but the tablet technically should reset if anything fails. Another choice that is up to you alone.
Again, Make sure your tablet is powered off and NO USB plugged in. This is basically the same procedure as backing up, except you're using the Download tab instead of Readback.
Extract SP-Flash-Tool-v5.1532.00 and Launch flash_tool.exe.
Change the download-agent from MTK_AllInOne_DA.bin to DA_PL.bin - This is located under the SP-Flash-Tool-v5.1532.00 dir.
Add the Scatter-loading file which should have been downloaded previously.
Look down the list you see Recovery line, click on the right side, point it to the TWRP.img you downloaded. (Make sure this line is only checked.)
Click the Download button and THEN plug in the USB cable to your tablet. Bar goes red, yellow and then done. Green Checkmark.
It's safe to unplug the USB from the tablet now and you can close the Flash Tool
Alternative method that does not require SP Flash Tool, scatter file, etc.
Unlock the bootloader: Download the Asus unlock tool for your tablet here and run it. (It's an APK from ASUS. When done you reboot tablet, you will see a message Your Device Cannot be Trusted..., you're unlocked.)
Download twrp-recoveryasboot-3.1.1-0-z300m.img.
Make sure you have fastboot/adb installed on your PC. Put your tablet in fastboot mode by holding Volume Up and Power, then selecting Fastboot Mode from the menu, and connect to PC.
Run this command to do a tethered boot of TWRP
fastboot boot twrp-recoveryasboot-3.1.1-0-z300m.img​
This will boot but will not install TWRP. You may be able to do whatever you need in this environment. But it is recommended to install TWRP to your flash ROM, and proceed from there.
To flash TWRP from TWRP, go to Install -> Install Image. Select the twrp-3.1.1-0-z300m.img file you downloaded earlier (not the twrp-recoveryasboot*.img file). Select Recovery, then swipe to flash.
Reboot to Recovery
[TWRP first launch]
Now press and hold both the Volume Up and Power button at the same time. Tablet will show a list so let go of the buttons.
Use the Up volume now to select Recovery and press Down volume to select. Tablet should reboot into TWRP. (takes 10-15 seconds)
A dialogue will show in TWRP stating that there is a chance Recovery will be restored (the Asus one) so slide across to keep TWRP.
Mounting /system in read/write mode could be potentially hazardous, this is patched at your own risk.
***NOTE: You will need to boot into the recovery immediately after flashing, failing to do so will result in the Android OS reflashing its stock recovery. If you are concerned about which recovery is installed I would suggest using 'adb reboot recovery' to minimize risk.
[ROOTING]
Put the Magisk flash file on a working micro sdcard and pop it in your device. (this won't get deleted and can be accessed by TWRP)
Don't reboot yet, we need to flash Root (you should have Magisk img/zip on your micro sd inserted in tablet)
Assuming you are familiar with TWRP, Install the Magisk Manager.
When this is done, reboot your tablet to System with TWRP.
We've tried to make this guide as helpful as possible, read this thread and the Z380 thread as there may be new things learned, past experiences of others that could help you.
Enjoy your Rooted Tablet!

Thanks! Any chance of instructions for us using Linux?
Maybe we'll get LineageOS for this soon!

New TWRP Image March 4, 2018
Up to date precompiled kernel from firmware WW-5.3.19
Up to date TWRP/AOSP sources, including TWRP 3.2.1-0
Unified image that may be flashed to recovery or boot partitions, or be used for tethered boot
Guide and downloads on my new TWRP thread
Upgrade Installation
Copy the new image file to your tablet, then use your existing TWRP to Install->Install Image the .img file to Recovery. Then reboot to recovery.
Mandatory step: after trying this release out, you must come back here and post whether it works or not.
(Source code on my Z380M thread.)

Good job ! It's more than anyone else has managed to do so far

justshaun said:
In order to navigate through TWRP you will need to attach the OTG cable and mouse to your tablet, it doesn't currently have any touchscreen functionality. Reboot into the system and make sure to patch your OS.
Click to expand...
Click to collapse
After looking at kernel logs and old source code, it seems like the touchscreen driver is intentionally disabled from working in recovery mode. If we had updated kernel sources, this could be fixed easily.
QwertyChouskie said:
Thanks! Any chance of instructions for us using Linux?
Click to expand...
Click to collapse
Try the Linux flavor of SP Flash Tool?

Wow this is quite the process and twrp with no touch screen? Plz post your success to raise confidence of others like me. Last f'ng tablet I ever buy from Asus. Let's also not forget you will be stuck on this release forever afterwards.
Sent from my P00C using Tapatalk

how do you unroot tablet after this process?

Flukester69 said:
Wow this is quite the process and twrp with no touch screen? Plz post your success to raise confidence of others like me. Last f'ng tablet I ever buy from Asus. Let's also not forget you will be stuck on this release forever afterwards.
Click to expand...
Click to collapse
You can try the Asus unlock tool to be able to flash with fastboot and not worry about SP Flash Tool. At least one person got it work on the Z380M. And you can always unroot/restore original boot & system images to be able to upgrade the firmware. Also, it's kind of unfair to rate a company poorly for not supporting your hacks, especially since this tablet is basically unbrickable AFAIK.
MihaiA7X said:
how do you unroot tablet after this process?
Click to expand...
Click to collapse
Restore the original boot image if you only have systemless root. And also the system image if you've modified it.

diplomatic said:
You can try the Asus unlock tool to be able to flash with fastboot and not worry about SP Flash Tool. At least one person got it work on the Z380M. And you can always unroot/restore original boot & system images to be able to upgrade the firmware. Also, it's kind of unfair to rate a company poorly for not supporting your hacks, especially since this tablet is basically unbrickable AFAIK.
Click to expand...
Click to collapse
I'll give it a try at some point man, not sure about the unbrickable part, $hit happens. Do you have a reference for the guy with the 380 that flashed via fastboot? that would be the preferable method for me really.
---------- Post added at 10:20 PM ---------- Previous post was at 10:01 PM ----------
What is Magisk? Is it really needed? If TWRP is installed with the Flashtools can I not just flash SuperSU with TWRP? If you could clarify?
When I tried the command to flash recovery I got the following...
Code:
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 134217728 bytes
sending 'recovery' (13958 KB)...
OKAY [ 0.445s]
writing 'recovery'...
FAILED (remote: download for partition 'recovery' is not allowed
)
finished. total time: 0.452s

What I meant by unbrickable was that you can use SP Flash Tool to talk directly with the SoC. That gives you low-level access to the flash ROM without depending on any software on it. So for example, if your bootloader or partition table is messed up, something that would brick most devices, you can flash those in without needing to get into the bootloader. I'm not 100% sure this is possible, but I'm pretty confident it is.
This is the post where the guy unlocked the bootloader. But I'm not sure he used fastboot to flash. TBH, FlashTool is not that complicated. Most of that stuff in the guide has to do with backing up your flash memory. If you wanna skip that part, that's up to you. You can just go ahead and use Flash Tool 5.1532 with the scatter file and the right download-agent to flash the recovery. BTW, you can follow that thread as well. Whatever applies to the Zenpad Z380M usually applies to the Z300M too.
Magisk is another root manager like SuperSU. SuperSU seems to have compatibility problems with this tablet. (I have not tried either.)

diplomatic said:
What I meant by unbrickable was that you can use SP Flash Tool to talk directly with the SoC. That gives you low-level access to the flash ROM without depending on any software on it. So for example, if your bootloader or partition table is messed up, something that would brick most devices, you can flash those in without needing to get into the bootloader. I'm not 100% sure this is possible, but I'm pretty confident it is.
This is the post where the guy unlocked the bootloader. But I'm not sure he used fastboot to flash. TBH, FlashTool is not that complicated. Most of that stuff in the guide has to do with backing up your flash memory. If you wanna skip that part, that's up to you. You can just go ahead and use Flash Tool 5.1532 with the scatter file and the right download-agent to flash the recovery. BTW, you can follow that thread as well. Whatever applies to the Zenpad Z380M usually applies to the Z300M too.
Magisk is another root manager like SuperSU. SuperSU seems to have compatibility problems with this tablet. (I have not tried either.)
Click to expand...
Click to collapse
Thanks for clearing that up... Ok I can use the 5.1532, I get that part but I don't get this part...
6. Make sure the tablet is turned off and then plug it into your computer
Click to expand...
Click to collapse
then
Click download at the top and plug in your tablet while it's still off. Assuming all goes well, the 'Download Flash' section at the bottom should be sitting on 100% and you should have a lovely green tick on your screen.
Click to expand...
Click to collapse
So when I press Download button in flash tool, the tablet needs to be OFF? Like powered off completely? Because nothing happens other than seeing the untrusted device (cuz it's unlocked) and the battery charging display.

Flukester69 said:
So when I press Download button in flash tool, the tablet needs to be OFF? Like powered off completely? Because nothing happens other than seeing the untrusted device (cuz it's unlocked) and the battery charging display.
Click to expand...
Click to collapse
Yeah, completely off. Have you installed the Mediatek USB port drivers? Where does it say untrusted device?
So after you unlocked it, have you tried fastboot flash? And you also don't need to use the 5.1532 version. I think the latest one will work too. The 1532 is just the NSA courtesy version.

diplomatic said:
Yeah, completely off. Have you installed the Mediatek USB port drivers? Where does it say untrusted device?
So after you unlocked it, have you tried fastboot flash? And you also don't need to use the 5.1532 version. I think the latest one will work too. The 1532 is just the NSA courtesy version.
Click to expand...
Click to collapse
Installed is whatever Win10 installed. I didn't try other drivers because adb / fastboot appear to work but I can try some other drivers.
Whenever I boot the tablet, it says untrusted device because the bootloader is unlocked. It says, booting in 5 seconds.
I do a fastboot reboot bootloader and I see it says fastboot ready at the bottom of the screen. When I type fastboot devices, it says my device in the list.
I tried fastboot flash recovery recovery.img if that's what you're asking (didn't work, so that's why I went with the software)

So just to be clear, you were getting 'FAILED (remote: download for partition 'recovery' is not allowed)' AFTER you've unlocked the bootloader?
If it's not being detected by SP Flash Tool, then something's wrong with your driver installation. Remember, those Mediatek USB drivers are not the same ones your ADB and/or Fastboot drivers. Check your Device Manger, under Ports, for a device called "MediaTek PreLoader USB VCOM (Android)". You have to check View->Show Hidden Devices to see it when your device is disconnected. You might have to right click and Update Driver Software to fix it.

diplomatic said:
So just to be clear, you were getting 'FAILED (remote: download for partition 'recovery' is not allowed)' AFTER you've unlocked the bootloader?
If it's not being detected by SP Flash Tool, then something's wrong with your driver installation. Remember, those Mediatek USB drivers are not the same ones your ADB and/or Fastboot drivers. Check your Device Manger, under Ports, for a device called "MediaTek PreLoader USB VCOM (Android)". You have to check View->Show Hidden Devices to see it when your device is disconnected. You might have to right click and Update Driver Software to fix it.
Click to expand...
Click to collapse
I got the failed with the fastboot command not the flash tool. I'll try and install the mediatek special drivers you are most likely right that they differ from the sdk provided ones. Reading other threads I understand the flash tool a bit more too. I'll do a bit more work on it and provide feedback. Thanks for your help diplomatic.
Sent from my P00C using Tapatalk

No, I know the message is from fastboot... I'm asking if you have tried fastboot flash with your bootloader UNLOCKED. Because that message indicates that your bootloader was locked when you ran it.

diplomatic said:
No, I know the message is from fastboot... I'm asking if you have tried fastboot flash with your bootloader UNLOCKED. Because that message indicates that your bootloader was locked when you ran it.
Click to expand...
Click to collapse
Well I ran the bootloader unlock tool I downloaded from Asus and ran it so I assumed it's unlocked. I tried to install drivers (latest I could find) but Windows 10 (64-bit) says I have latest installed. I checked device manager and when my tablet is off and I connect it I see the drivers(3) become active for a few seconds and then they turn off. Seems to me something is not working with this process. If you look below it seems to indicate to me the bootloader is unlocked.
Here is info
Code:
C:\adb>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
G7NPCV038358ANK device
C:\adb>fastboot devices
G7NPCV038358ANK fastboot
C:\adb>fastboot flash recovery c:\adb\twrp.img
target reported max download size of 134217728 bytes
sending 'recovery' (13958 KB)...
OKAY [ 0.444s]
writing 'recovery'...
FAILED (remote: download for partition 'recovery' is not allowed
)
finished. total time: 0.453s
C:\adb>fastboot getvar all
(bootloader) max-block-size: 0x80
(bootloader) check-fastboot-version: 1
(bootloader) sofia_support: 1
(bootloader) continuous: 1
(bootloader) flash-all-depart: 1
(bootloader) max-download-size: 0x8000000
(bootloader) partition-size:ADF: 2000000
(bootloader) partition-type:ADF: ext4
(bootloader) partition-size:APD: 6400000
(bootloader) partition-type:APD: ext4
(bootloader) partition-size:flashinfo: 1000000
(bootloader) partition-type:flashinfo: raw data
(bootloader) partition-size:asus_nvm: 100000
(bootloader) partition-type:asus_nvm: raw data
(bootloader) partition-size:frp: 100000
(bootloader) partition-type:frp: raw data
(bootloader) partition-size:userdata: 32000000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:cache: c800000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:system: dfc00000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:metadata: 2000000
(bootloader) partition-type:metadata: raw data
(bootloader) partition-size:tee2: 500000
(bootloader) partition-type:tee2: raw data
(bootloader) partition-size:tee1: 500000
(bootloader) partition-type:tee1: raw data
(bootloader) partition-size:expdb: a00000
(bootloader) partition-type:expdb: raw data
(bootloader) partition-size:logo: 800000
(bootloader) partition-type:logo: raw data
(bootloader) partition-size:para: 80000
(bootloader) partition-type:para: raw data
(bootloader) partition-size:secro: ff7000
(bootloader) partition-type:secro: ext4
(bootloader) partition-size:recovery: ff7000
(bootloader) partition-type:recovery: raw data
(bootloader) partition-size:boot: ff7000
(bootloader) partition-type:boot: raw data
(bootloader) partition-size:lk: 80000
(bootloader) partition-type:lk: raw data
(bootloader) partition-size:seccfg: 40000
(bootloader) partition-type:seccfg: raw data
(bootloader) partition-size:persist: 2000000
(bootloader) partition-type:persist: ext4
(bootloader) partition-size:protect2: a00000
(bootloader) partition-type:protect2: ext4
(bootloader) partition-size:protect1: a00000
(bootloader) partition-type:protect1: ext4
(bootloader) partition-size:nvram: 500000
(bootloader) partition-type:nvram: raw data
(bootloader) partition-size:proinfo: 300000
(bootloader) partition-type:proinfo: raw data
(bootloader) partition-size:preloader: 40000
(bootloader) partition-type:preloader: raw data
(bootloader) off-mode-charge: 1
(bootloader) warranty: no
(bootloader) unlocked: yes
(bootloader) secure: no
(bootloader) kernel: lk
(bootloader) product: ASUS8163_EW_380
(bootloader) version-preloader: 0.1.00
(bootloader) version: 0.5
all: Done!!
finished. total time: 0.112s
C:\adb>
---------- Post added at 11:21 PM ---------- Previous post was at 10:33 PM ----------
diplomatic said:
No, I know the message is from fastboot... I'm asking if you have tried fastboot flash with your bootloader UNLOCKED. Because that message indicates that your bootloader was locked when you ran it.
Click to expand...
Click to collapse
LOL! OK. I figured $h.. out... The problem was this...
The device must be OFF and DISCONNECTED and ONLY connected when you hit the download button. The reason is, the driver shuts off if there is no data transferring. Very important detail. I am guessing this is what the issue was and why the flash tool was not working. Now I probably got old crap drivers by forcing them through Windows Troubleshooter to override signature verification. So anyway I tried flashing anyway and it failed. I suspect because I overrided good drivers with old ones. You can see what I got here.
https://ibb.co/mwkHFv

Whoa, that's kind of unexpected that fastboot would not let you flash even though it's unlocked. And the latest SPFT is not letting you download either. It says it's unlocked but it's acting like it's locked. But you're really close....
That S_SECURITY_SECURE... (6045) message is just the Flashtool's version of fastboot not allowed error (locked bootloader). So you still have to use 5.1532 to flash it. That's all.
I will post a signed image of TWRP to see if that will work for you.

diplomatic said:
Whoa, that's kind of unexpected that fastboot would not let you flash even though it's unlocked. And the latest SPFT is not letting you download either. It says it's unlocked but it's acting like it's locked. But you're really close....
That S_SECURITY_SECURE... (6045) message is just the Flashtool's version of fastboot not allowed error (locked bootloader). So you still have to use 5.1532 to flash it. That's all.
I will post a signed image of TWRP to see if that will work for you.
Click to expand...
Click to collapse
OK That worked with the 5.1532 and I booted to recovery and TWRP is there. Woohoo! Thanks for the continued help! I was getting frustrated. Not like the first device I flashed/rooted etc...
Disconnecting of the tablet until after Download button was one, the next the version of SP Flash.. cool. Making progress.
So you say SuperSU don't work... Magick one works though but installs crap, then you could use sysuninstaller to remove the crap...? Think I read that somewhere. Ok I'll read up anyway, kinda curious why SuperSU
wont work or has problems.
Also know that I removed all the MTK (older) drivers using USBDeview and then rebooting my tablet and going through all the modes, fastboot etc.. the drivers eventually all the Windows certified re-installed (the MS ones). So no need to download drivers either I guess.
Edit: this is a 1 time deal apparently. I had twrp installed but as I didn't have supersu 2.82 downloaded I rebooted out of recovery. Next attempt to go to recovery resulted in "Erasing" so I lost all my apps and had to setup my tablet all over again. Oh well, guess I know what to do now. Try again tomorrow.

All right, good job, man! :good: I'm sure our discussion will clarify the process for others...
As for root, someone else should help you out. I have not put root on my tablet. All my hacks and mods are done through TWRP.
I'm still surprised that the unlocked bootloader did not let you flash it.
---------- Post added at 12:02 AM ---------- Previous post was at 12:00 AM ----------
Flukester69 said:
Edit: this is a 1 time deal apparently. I had twrp installed but as I didn't have supersu 2.82 downloaded I rebooted out of recovery. Next attempt to go to recovery resulted in "Erasing" so I lost all my apps and had to setup my tablet all over again. Oh well, guess I know what to do now. Try again tomorrow.
Click to expand...
Click to collapse
Oh come on, how could you miss that big red text in the OP?