Earlier today I bricked my Padfone 2 by installing 3rd part font. After a reboot to apply the changes, it got to the boot logo but never any further.
I got it up and running again, :victory: and to those out there in same or similar situation, here's a tutorial on what I did:
Before we start, there's a few things you need;
1.1 Latest ADB version (I used 1.0.31) [ATTACHED]
1.2 Latest Fastboot version [ATTACHED]
1.3 CWM Recovery [ATTACHED]
1.4 Latest ASUS USB Drivers (available from ASUS Support site) [ATTACHED]
1.5 Padfone 2 Firmware (available from ASUS Support site)
*** NOTE: For ease of use, place extract and place all of the above to the same folder.
*** NOTE: Inside the Padfone 2 Firmware ZIP file, there's another ZIP file. This is the one we need! The one I used was called "WWE_A68-10.4.15.1-0-ota-user.zip"
*** NOTE: This method does not install CWM Recovery on your phone, it only boots it temporarily.
If you have all of the above, continue to step 2;
2.1 Booting your Padfone 2 into Fastboot mode
2.2 Press and hold Power + Volume up buttons
In Fastboot mode, connect your phone to your computer and launch cmd. Wait for windows to install necessary drivers if needed.
3.1 Navigate your CMD to the folder containing ADB, Fastboot and CWM Recovery (recovery.img)
3.2 In CMD type:
Code:
fastboot boot recovery.img
In the CWM Recovery on your phone, select the option titled "Install ZIP from sideload".
Use the volume keys to navigate and select by pressing the power button.
4.1 In CMD, transfer the Padfone 2 Firmware by typing
Code:
adb sideload [firmware-file-name.zip]
- Example from my case, I wrote:
Code:
adb sideload WWE_A68-10.4.15.1-0-ota-user.zip
4.2 When it is done, you'll be presented with CWM Recovery's screen again, select "Reboot system now".
4.3 CWM Recovery will present you with a warning saying: "ROM may flash stock recovery on boot. Fix?" - Select "NO".
If you are experiencing problems with driver installation, you can fix it manually. If windows installed the drivers correctly, skip this step. To solve this, go to device manager by entering the Start menu, right-click Computer and select “Manage”. Select the Device Manager.
You should see a failed device named A68. Right-click it and select “Update device software”
Select “Browse my computer for driver software”
Select “Let me pick from a list of device drivers on my computer”
Select “Have Disk”
Now browse and navigate to the folder you extracted your ASUS USB Drivers to and select the file named “android_winusb.inf”
Select “ASUS Android ADB Interface” and install.
All done! You should have a working Padfone 2 again!
Please note that you may need to root your phone again.
Please credit if used
/HelmerN
HelmerN said:
Earlier today I bricked my Padfone 2 by installing 3rd part font. After a reboot to apply the changes, it got to the boot logo but never any further.
I got it up and running again, :victory: and to those out there in same or similar situation, here's a tutorial on what I did:
Before we start, there's a few things you need;
1.1 Latest ADB version (I used 1.0.31) [ATTACHED]
1.2 Latest Fastboot version [ATTACHED]
1.3 CWM Recovery [ATTACHED]
1.4 Latest ASUS USB Drivers (available from ASUS Support site) [ATTACHED]
1.5 Padfone 2 Firmware (available from ASUS Support site)
*** NOTE: For ease of use, place extract and place all of the above to the same folder.
*** NOTE: Inside the Padfone 2 Firmware ZIP file, there's another ZIP file. This is the one we need! The one I used was called "WWE_A68-10.4.15.1-0-ota-user.zip"
*** NOTE: This method does not install CWM Recovery on your phone, it only boots it temporarily.
If you have all of the above, continue to step 2;
2.1 Booting your Padfone 2 into Fastboot mode
2.2 Press and hold Power + Volume up buttons
In Fastboot mode, connect your phone to your computer and launch cmd. Wait for windows to install necessary drivers if needed.
3.1 Navigate your CMD to the folder containing ADB, Fastboot and CWM Recovery (recovery.img)
3.2 In CMD type:
Code:
fastboot boot recovery.img
In the CWM Recovery on your phone, select the option titled "Install ZIP from sideload".
Use the volume keys to navigate and select by pressing the power button.
4.1 In CMD, transfer the Padfone 2 Firmware by typing
Code:
adb sideload [firmware-file-name.zip]
- Example from my case, I wrote:
Code:
adb sideload WWE_A68-10.4.15.1-0-ota-user.zip
4.2 When it is done, you'll be presented with CWM Recovery's screen again, select "Reboot system now".
4.3 CWM Recovery will present you with a warning saying: "ROM may flash stock recovery on boot. Fix?" - Select "NO".
If you are experiencing problems with driver installation, you can fix it manually. If windows installed the drivers correctly, skip this step. To solve this, go to device manager by entering the Start menu, right-click Computer and select “Manage”. Select the Device Manager.
You should see a failed device named A68. Right-click it and select “Update device software”
Select “Browse my computer for driver software”
Select “Let me pick from a list of device drivers on my computer”
Select “Have Disk”
Now browse and navigate to the folder you extracted your ASUS USB Drivers to and select the file named “android_winusb.inf”
Select “ASUS Android ADB Interface” and install.
All done! You should have a working Padfone 2 again!
Please note that you may need to root your phone again.
Please credit if used
/HelmerN
Click to expand...
Click to collapse
The f.cking windows not found my phone when try to install drivers windows give my cannot install .....
please tell me what i do to install drivers other drivers or what please help me?
thanks!
I wish I could enter into Fastboot mode.
I have two Padfone 2 bricked (by unknow reason) with QHSUSB_DLOAD error (Qualcomm High Speed USB Download).
the whole case: http://forum.xda-developers.com/showthread.php?t=2220775
Do you have any ideas?
Hi,
I have the same problem like you rafael_mfr .
Is there any solution to unbrick my padfone 2 ?
Bricked?
I have now joined the club
Not sure if it's bricked or not but the phone is stuck on loading (silver Asus with circulating loading) unstopping for more than an hour.
Tried your technique and all other possible ways but no luck any ideas?
charlykayo said:
The f.cking windows not found my phone when try to install drivers windows give my cannot install .....
please tell me what i do to install drivers other drivers or what please help me?
thanks!
Click to expand...
Click to collapse
Have you tried the last step? I mention issues with windows drivers and how to manually install them.
rafael_mfr said:
I wish I could enter into Fastboot mode.
I have two Padfone 2 bricked (by unknow reason) with QHSUSB_DLOAD error (Qualcomm High Speed USB Download).
the whole case: http://forum.xda-developers.com/showthread.php?t=2220775
Do you have any ideas?
Click to expand...
Click to collapse
Tamsabodi said:
Hi,
I have the same problem like you rafael_mfr .
Is there any solution to unbrick my padfone 2 ?
Click to expand...
Click to collapse
As far as I know, the QHSUSB_DLOAD error is hardware related and cannot be fixed by normal means. I believe it requires some special hardware or flash tool or something.
You could try manually installing the Asus USB drivers by following the last step and see if that works?
In any case, the tutorial only fixes software based issues.
Mine got totally bricked some time ago. Somehow the mainboard was fried and needed replacement.
It didn't react in any way when trying to power it on. If i plugged in the charger, it would get pancake-making hot!
Asus dispatched a UPS guy to pick it up and send it for repair. When the mainboard is fried like mine was, they can't tell if it were rooted or not, so they had to repair it.
All in all, I had a great experience with ASUS warranty
droidace said:
I have now joined the club
Not sure if it's bricked or not but the phone is stuck on loading (silver Asus with circulating loading) unstopping for more than an hour.
Tried your technique and all other possible ways but no luck any ideas?
Click to expand...
Click to collapse
Your issue should be fixable!
I'm assuming your bootloader is unlocked?
Was the
Code:
adb sideload WWE_A68-10.4.15.1-0-ota-user.zip
successfull?
HelmerN said:
Your issue should be fixable!
I'm assuming your bootloader is unlocked?
Was the
Code:
adb sideload WWE_A68-10.4.15.1-0-ota-user.zip
successfull?
Click to expand...
Click to collapse
Yes, bootloader is unlocked
Yes, adb sideload is working via CWM but tried it with the latest firmware update (WWE_A68-10.4.17.7-0-ota-user.zip) from asus.com after renaming the file to "WWE.zip" for shorter cmd lines
Anything else needs to be checked?
droidace said:
Yes, bootloader is unlocked
Yes, adb sideload is working via CWM but tried it with the latest firmware update (WWE_A68-10.4.17.7-0-ota-user.zip) from asus.com after renaming the file to "WWE.zip" for shorter cmd lines
Anything else needs to be checked?
Click to expand...
Click to collapse
Did you extract the zip file?
Within the zip file, theres another zip. That's the one you need.
Yo dawg! We heard you like zip's, so we put a zip within your zip, so you can zip while zipping
Click to expand...
Click to collapse
HelmerN said:
Did you extract the zip file?
Within the zip file, theres another zip. That's the one you need.
Click to expand...
Click to collapse
Yeah, I had that covered. it's the final zip level ..
droidace said:
Yeah, I had that covered. it's the final zip level ..
Click to expand...
Click to collapse
Very surprised it didn't work.
Have you tried factory restore through the recovery boot?
HelmerN said:
Very surprised it didn't work.
Have you tried factory restore through the recovery boot?
Click to expand...
Click to collapse
Tried that at the very beginning.
That issue has started after I installed GPS Status - Test and Fix https://play.google.com/store/apps/details?id=com.cochibo.gpsstatus&hl=en as part of getting a better GPS performance I have reset GPS and then Get Xtra data but after restarting, it never loaded the system. I hope this helps identifying the issue
I might try this way as a final try
droidace said:
Tried that at the very beginning.
That issue has started after I installed GPS Status - Test and Fix https://play.google.com/store/apps/details?id=com.cochibo.gpsstatus&hl=en as part of getting a better GPS performance I have reset GPS and then Get Xtra data but after restarting, it never loaded the system. I hope this helps identifying the issue
I might try this way as a final try
Click to expand...
Click to collapse
I wouldn't recommend doing an SKU conversion. There might be (not sure) a slight difference in hardware in the different areas. I know products sold in China sometimes aren't up to spec with the rest of the world in order to keep prices down and sales up, for an example.
So if the voltage settings are a little off in comparison to your hardware, it might get fried.
That being said, your issue is a weird one. It sounds like software malfunction, easily solvable with a reset or sideloading firmware, forcing me to wonder if your device have been flashed with a different SKU or, perhaps, have a hardware malfunction.
For now all I can come up with is; repeat the process. Give it reasonable time to boot up, 10 mins. should be more than enough. If there's still no progress, enter recovery and clear the cache and try booting up again.
Otherwise I'm stumped.
Might be time to consider the RMA option?
A lot of Padfone 2's are born with a eMMC fault - so it could be related?
Fixed, wipe data partition (from stock recovery ONLY) what an intermittent issue
Thanks..... it was wery usefull
There's another way to un-brick.
The first day I received my Padfone 2, after only 6 hours I got it really badly bricked. No button combination would work, all I got was "invalid kernel"
On Modaco there's a thread http://www.modaco.com/topic/365818-padfone-2-invalid-kernel/?p=2191432 that worked very well, even a self-proclaimed noob as myself could finally get it together. It was amazing as I thought I had to send the Phone back to Germany (from Portugal)
For those who prefer the German language: http://www.android-hilfe.de/asus-padfone-2-forum/531509-bricked-invalid-kernel-2.html
credits go to Paul O'brien and manu7irl who posted this solution on MoDaCo and Vakilando on Android-Hilfe who inspired me to give it a second try.
HelmerN said:
Earlier today I bricked my Padfone 2 by installing 3rd part font. After a reboot to apply the changes, it got to the boot logo but never any further.
I got it up and running again, :victory: and to those out there in same or similar situation, here's a tutorial on what I did:
Before we start, there's a few things you need;
1.1 Latest ADB version (I used 1.0.31) [ATTACHED]
1.2 Latest Fastboot version [ATTACHED]
1.3 CWM Recovery [ATTACHED]
1.4 Latest ASUS USB Drivers (available from ASUS Support site) [ATTACHED]
1.5 Padfone 2 Firmware (available from ASUS Support site)
*** NOTE: For ease of use, place extract and place all of the above to the same folder.
*** NOTE: Inside the Padfone 2 Firmware ZIP file, there's another ZIP file. This is the one we need! The one I used was called "WWE_A68-10.4.15.1-0-ota-user.zip"
*** NOTE: This method does not install CWM Recovery on your phone, it only boots it temporarily.
If you have all of the above, continue to step 2;
2.1 Booting your Padfone 2 into Fastboot mode
2.2 Press and hold Power + Volume up buttons
In Fastboot mode, connect your phone to your computer and launch cmd. Wait for windows to install necessary drivers if needed.
3.1 Navigate your CMD to the folder containing ADB, Fastboot and CWM Recovery (recovery.img)
3.2 In CMD type:
Code:
fastboot boot recovery.img
In the CWM Recovery on your phone, select the option titled "Install ZIP from sideload".
Use the volume keys to navigate and select by pressing the power button.
4.1 In CMD, transfer the Padfone 2 Firmware by typing
Code:
adb sideload [firmware-file-name.zip]
- Example from my case, I wrote:
Code:
adb sideload WWE_A68-10.4.15.1-0-ota-user.zip
4.2 When it is done, you'll be presented with CWM Recovery's screen again, select "Reboot system now".
4.3 CWM Recovery will present you with a warning saying: "ROM may flash stock recovery on boot. Fix?" - Select "NO".
If you are experiencing problems with driver installation, you can fix it manually. If windows installed the drivers correctly, skip this step. To solve this, go to device manager by entering the Start menu, right-click Computer and select “Manage”. Select the Device Manager.
You should see a failed device named A68. Right-click it and select “Update device software”
Select “Browse my computer for driver software”
Select “Let me pick from a list of device drivers on my computer”
Select “Have Disk”
Now browse and navigate to the folder you extracted your ASUS USB Drivers to and select the file named “android_winusb.inf”
Select “ASUS Android ADB Interface” and install.
All done! You should have a working Padfone 2 again!
Please note that you may need to root your phone again.
Please credit if used
/HelmerN
Click to expand...
Click to collapse
please helmern , help me!
MY PADFONE 2 is bloked after istalling a rom.
after, I have istalled from sideload (with cwm v.6) the ufficial rom but it ,after rebooting is always bloked on the screen of logo ''asus'' and not rebooting. why ?
this is the log report :
{
"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"
}
help me , please!
agent-06 said:
please helmern , help me!
MY PADFONE 2 is bloked after istalling a rom.
after, I have istalled from sideload (with cwm v.6) the ufficial rom but it ,after rebooting is always bloked on the screen of logo ''asus'' and not rebooting. why ?
this is the log report :
View attachment 2575590
help me , please!
Click to expand...
Click to collapse
hi i have the same problem , only asus logo no rebooting.........helpppppppppppppppppp
i tried your solution all ok but bloked on asus logo
famonaco said:
hi i have the same problem , only asus logo no rebooting.........helpppppppppppppppppp
i tried your solution all ok but bloked on asus logo
Click to expand...
Click to collapse
before installing a firmware you have to do all three wipes For three times.
Inviato dal mio PadFone 2 utilizzando Tapatalk
Related
My tab started giving al kind of errors on internal apps and stuff so i shut it down and now it is in reboot loop.
I can get it into odin download mode or fastboot mode. But i cannot see it with adb or fastboot (it doesent show up when using adb devices or fastboot devices.
i can use odin to do a pda flash but outcome is stil the same.
also did nvflash from Retail 3.1 CWM Recovery, Root & full back up!
al goes fine but after that still no adb reboot recovery or adb devices
iam desperate please help me with this
renedg said:
My tab started giving al kind of errors on internal apps and stuff so i shut it down and now it is in reboot loop.
I can get it into odin download mode or fastboot mode. But i cannot see it with adb or fastboot (it doesent show up when using adb devices or fastboot devices.
i can use odin to do a pda flash but outcome is stil the same.
also did nvflash from Retail 3.1 CWM Recovery, Root & full back up!
al goes fine but after that still no adb reboot recovery or adb devices
iam desperate please help me with this
Click to expand...
Click to collapse
Here's what you do.
Download the file linked below
Download ODIN attached below
Once both are downloaded, extract PDA_SIGNED_P7105.tar
Boot your tablet into ODIN and plug it into your PC
Open the ODIN program on your PC and check the box next to PDA
Click the PDA button and navigate to the file you downloaded earlier
Press Start and let it flash
Once it is done, it will still boot loop.
You need to go into recovery (It will now be the default recovery) and wipe data/factory reset only.
Reboot and it should load up, however you will be on 3.0.1.
You can get back to 3.1 by rooting and installing recovery again or by using the update feature in the tablet's settings.
Good luck!
http://www.mediafire.com/?gcenefqc3khcc0c
renedg said:
My tab started giving al kind of errors on internal apps and stuff so i shut it down and now it is in reboot loop.
I can get it into odin download mode or fastboot mode. But i cannot see it with adb or fastboot (it doesent show up when using adb devices or fastboot devices.
i can use odin to do a pda flash but outcome is stil the same.
also did nvflash from Retail 3.1 CWM Recovery, Root & full back up!
al goes fine but after that still no adb reboot recovery or adb devices
iam desperate please help me with this
Click to expand...
Click to collapse
Please DO NOT ask Questions in the Development forum
Moving to General
When i have done this and go into recovery (power and left volume) i stil get usb icon and download (odin) and still no device found with adb or fastboot (driver i sbeing loaded so somehow my system does regonize it as fastboot or recovery device but with fastboot devices or adb devices still no device in list.
It is alive again. Thanks all who helped out
renedg said:
when i have done this and go into recovery (power and left volume) i stil get usb icon and download (odin) and still no device found with adb or fastboot (driver i sbeing loaded so somehow my system does regonize it as fastboot or recovery device but with fastboot devices or adb devices still no device in list.
Click to expand...
Click to collapse
it is alive again. Thanks all who helped out
You are the man! My IO Galaxy Tab 10.1 is alive again!
Thanks!
Hi All,
I am done the ODIN step, but it still in bootloop mode. I dont know how to do with the Fastboot recover mode. I tried with my Windows 7 and it can't recognized my fastboot driver and stay in the <waiting for device>. Is there any solution for me. Thank you so much.
ericc191 said:
Here's what you do.
Download the file linked below
Download ODIN attached below
Once both are downloaded, extract PDA_SIGNED_P7105.tar
Boot your tablet into ODIN and plug it into your PC
Open the ODIN program on your PC and check the box next to PDA
Click the PDA button and navigate to the file you downloaded earlier
Press Start and let it flash
Once it is done, it will still boot loop.
You need to go into recovery (It will now be the default recovery) and wipe data/factory reset only.
Reboot and it should load up, however you will be on 3.0.1.
You can get back to 3.1 by rooting and installing recovery again or by using the update feature in the tablet's settings.
Good luck!
Click to expand...
Click to collapse
Hello, I have also followed these directions however I am having issues rebooting into recovery using adb.
When I execute adb devices no devices are found.
Any additional help would be appreciated. Thanks
UPDATE:
Success!! I was able to correct the boot loop problem by installing fastboot on a linux machine and running sudo fastboot -w. Also my tablet was in fastboot mode (Power + Volume down, then Select the usb symbol).
Instructions for installing fastboot were found here http://forum.xda-developers.com/showpost.php?p=14675422&postcount=2
boot looping SOLVED! Honeycomb 3.1 google i/o galaxy tab 10.1
[IO TAB] Boot looping? Try this to get your tab back...
I had an issue with my IO 10.1 Tab boot looping. I imagine that this would work for retail as well but have not tried it.
This process will factory reset your device.
You will need fastboot and recovery.img to boot into recovery in order to perform a factory reset.
Fastboot & Stock IO recovery comes from this post as an attachment at the bottom.
You need adb to continue (windows).
1. Extract files to where adb resides (platform-tools folder in android SDk main folder) e.g
C:\Program Files\Android\android-sdk\platform-tools .
2. Plug your tab in to a power source and then hold down the power button until it shuts down. Wait until the tab displays the charging battery.
3. Press and hold the volume down (left button in landscape) and power buttons until the usb and odin icons show up. Volume down to move left and volume up to select the usb logo. Now you should be in fastboot. Plug the usb into your computer.
4. Time to fire up adb!
Start / run / cmd , cd\,
Than, cd to your platform-tools folder or wherever your adb is at. (should be in platform-tools inside of android-sdk-windows)
5. In cmd type "adb start-server" without quotes to start adb. All comands should exclude quotes.
6. Type "fastboot devices" your device serial should appear!If not:
Edit the “<PATH TO ANDROID SDK>\extras\google\usb_driver\android_winusb.inf” file and copy/paste the following lines and add them to the [Google.NTx86] section (for 32bit Windows) and/or [Google.NTamd64] (for 64bit Windows).
NO Empty line above this set, though galaxy tab 10.1v but works for all variants!(tab detected as adb xxx device)
;Galaxy Tab 10.1v
%SingleAdbInterface% = USB_Install, USB\VID_04E8&PID_6860&REV_9999&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_04E8&PID_6860&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_04E8&PID_6601
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
;
Download the fastboot zip attached to this post (includes both Win and Linux version) and extract the files to your “<PATH TO ANDROID SDK>\platform-tools” folder
7. Now, type "fastboot boot recovery.img"
8. Now you should boot into recovery. For "adb command lines" to work boot with clockworkmod recovery img (Command and files here: http://droidbasement.com/db-blog/?p=2032)
If you want to try other stuff like push a system restore, kernel or whatever, now you can. If you fail at it, you can always repeat the steps leading up to this point to get back to recovery.
9. Time to just get the tab back! Select "wipe data/factory reset" and confirm, clear cache.
10. After that is done select "reboot device".
Credits to JASKRU from rootwiki, with some additions and modifications extracted from different sources!
for rooting the tab install the zip file from this post in recovery mode (loading recovery.img from fastboot):
http://droidbasement.com/db-blog/?p=2054
P.S don't reboot into recovery with adb command "adb reboot recovery" as it doesn't work, correct way is with fastboot command as mentioned in step 7!
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
FIRST STEP: add the attached fastboot files into the container folder of adb (in sdk folder)
This is mine:
C:\Program Files\Android\android-sdk\platform-tools
of course I did that and mine is in the same folder as yours
I get to step six and thats when it gives me the error
E:\android-sdk-windows\platform-tools>fast boot devices
'fast' is not recognized as an internal or external command,
operable program or batch file.
also when I go to the left instead of odin this is my pic (in attachment)
NOW if I hit the power button and the right on in landscape mode I do get the android system recovery options says Android System Recovery <3e> (pic attached)
I have tried wiping date clearing cache as far as fastboot goes it still doesnt let me in fastboot eventhough im not sure at this point what fastboot even is
I finally got CWM 4.0.0.4 on it but now what because somehow im on 3.0.1 on my tab it wont charge and idk what to do
These steps were tested on 3.1.can you update your firmware from kies or on device?fastboot is needed to boot into the recovery image as in your pic which you already have managed being in older firmware.
E:\android-sdk-windows\platform-tools>fast boot devices
I believe something is still wrong, did you extract the contents of zip file in the platform-tools or the complete folder?Second, how was your tab once in fastboot recongnized by windows it should be as an adb. Device and not fastboot. Third, try manually installing the driver from extras folder, google, usb in android sdk. Last is your system 64bit or 32bit as the modification in inf file should be made accordingly. The only issue is driver or fastboot exe not being in adb folder.
Adding, once in recovery as in the pic, try command adb devices and let know if your device is detected hence you can push a restore fileto your device and reboot or push original recovery.zip file and apply it from sdcard (internal memory).
Last try odin option and flash firmware as tar file mentioned in this forum, try the bootloop or blank screen threads.
tried this route but it cannot find my device via ADB - used the PDANet driver - note i did not get a driver in the extras folder
ideas?
mughalgxt said:
These steps were tested on 3.1.can you update your firmware from kies or on device?fastboot is needed to boot into the recovery image as in your pic which you already have managed being in older firmware.
E:\android-sdk-windows\platform-tools>fast boot devices
I believe something is still wrong, did you extract the contents of zip file in the platform-tools or the complete folder?Second, how was your tab once in fastboot recongnized by windows it should be as an adb. Device and not fastboot. Third, try manually installing the driver from extras folder, google, usb in android sdk. Last is your system 64bit or 32bit as the modification in inf file should be made accordingly. The only issue is driver or fastboot exe not being in adb folder.
Adding, once in recovery as in the pic, try command adb devices and let know if your device is detected hence you can push a restore fileto your device and reboot or push original recovery.zip file and apply it from sdcard (internal memory).
Last try odin option and flash firmware as tar file mentioned in this forum, try the bootloop or blank screen threads.
Click to expand...
Click to collapse
solved my problem -
first fastboot.exe is located in the android-sdk\tools directory. i copied it to my android-sdk\platform-tools directory
Then i get into the tablet's fastboot mode (holding down power + volume down, then select the USB icon) i plug in the cable to my PC's USB, then go to device manager and you should see a fastboot device with an exclamation mark. right click on this and select update driver then navigate to android-sdk\extras\google\usb_driver directory and select android_winusb.inf - it should now install the driver
open up a cmd window and follow the instructions highlighted above starting at step 7
animatechnica said:
solved my problem -
first fastboot.exe is located in the android-sdk\tools directory. i copied it to my android-sdk\platform-tools directory
Then i get into the tablet's fastboot mode (holding down power + volume down, then select the USB icon) i plug in the cable to my PC's USB, then go to device manager and you should see a fastboot device with an exclamation mark. right click on this and select update driver then navigate to android-sdk\extras\google\usb_driver directory and select android_winusb.inf - it should now install the driver
open up a cmd window and follow the instructions highlighted above starting at step 7
Click to expand...
Click to collapse
IN Short, follow the steps in my previous post from 1st till end! Flashing the bootloader file from my thread in development section, is easiest way. Replacing fastboot with recovery option in bootscreen solves many issues for non-developers!
yes and i should add your method was very effective ! thanks
what threw me off initially was not finding the fastboot.exe which was in a different folder and the usbdriver - which needed to be installed separately and can be found by launching SDK manager, selecting Available packages-Third-party Add ons-Google Inc - Google USB Driver Package revision 4
mughalgxt said:
IN Short, follow the steps in my previous post from 1st till end! Flashing the bootloader file from my thread in development section, is easiest way. Replacing fastboot with recovery option in bootscreen solves many issues for non-developers!
Click to expand...
Click to collapse
Thanks!!!
This totally worked!
vokhoa408 said:
Thanks!!!
This totally worked!
Click to expand...
Click to collapse
Is this thing getting Ice cream sandwich?
that might solve all these problems.
Samsung Galaxy Tab 10.1 boot loop
Edit: *Fixed!* Ok, so here is my advice to all you other noobs who bricked your tablet, be AWARE that your tablet actually is conscious, it chooses when it wants to work. Just do everything it says on here, all the fixes I have listed, reboot a bunch of times, yell at it, and when you cry a true tear of pain and remorse, and it splashes down on the surface, it will recognize this and all of a sudden work. Booted to 3.0.1 and going to update, that all that is holy.
Hi Guys, I am having the same problem and need some expert advice please, I have a Samsung Galaxy Tab 10.1 with Android Honeycomb 3.1, running Windows XP Pro SP3
I've gone over every solution to this problem on xda over two days and none have worked for me, either that or i'm not doing it correctly.
I successfully rooted my Tab a few days ago, then tried to install a 'boosted' theme and everything is messed up now. When I boot it just hangs on the samsung loading screen, and it reboots to the same screen.
I have tried wiping data/factory reset in cwm
I have tried wiping cache partition
I have tried running Odin through downloading mode
I have adb and fastboot installed on my computer
I have Samsung Android adb interface driver in Device Manager
I have PDAnet installed
When I boot holding the volume down and power button to get the two options, the only two options I have are the Odin Downloading green guy on the right, and an icon with a box and an arrow coming out of it that takes me to CWM on the left.
So I cannot choose fastboot mode on the Tab, when I try to run 'fastboot flash system new.img' through cmd.exe it just says < waiting for device >
I"m a total noob to this and should have left well enough alone when I successfully rooted it, i'm sure I must be just missing a small step, if I could get a bit of guidance it would be greatly appreciated, thanks.
I tried to root my me302kl by following the first post described in this thread, but it seems I've bricked my tablet
http://forum.xda-developers.com/showthread.php?t=2601837
I have the LTE version, unlocked the bootloader using the apk from Asus, and followed the fastboot method in the first post, and now I'm stuck at the Asus logo on startup. I'm trying to factory reset by using the update download from the Asus website, but when i try
fastboot erase cache
fastboot erase system
fastboot flash update US_ME302C-V4.7.3-0-ota-user.zip
it fails with this:
writing 'update'...
FAILED (remote: partition table doesn't exist)
Then I tried following perpe's advice but both methods did not work
Download the update zip for your device and sku from ASUS. Unpack it once, there should be a second zip, try to flash it with
fastboot update name-of-your.zip
if this doesn't wotk, then copy the update zip to an external sd card. Your sd card should be formated in far32. Place the card into the tablets sd card. Press Volume UP + Power to boot it into the bootloader, it should flash it automatically, if not look if yor bootloader has a menu entry "sd download..." select it with the volume keys and power.
Click to expand...
Click to collapse
When booting into recovery mode, I get the dead android robot icon, regardless of whether the .zip file is on the SD card or not. I've also tried making a system.img file out of the system folder from the extracted zip file and flashing that with fastboot flash system system.img and fastboot flash boot boot.img, but that didn't work either.
Any kind soul have advice on how to make use of the official Asus OTA .zip file, or perhaps be able to supply some .img backups for me to make use of?
EDIT
Found out that to get the recovery menu to show up, you have to hold the power button and press volume up. I thought that the menu would show up automatically so I got confused. ADB sideloaded the Asus OTA .zip and everything is back to normal
Hello
How to flash oryginal soft on this tablet. Can you help with this ?
I tried SDK and wiped all system but now i cannot flash the system. How should i do it ?
I have firmware fros ASUS page and now what?
I tried fastboot flash update... but i have measege that unknown partition and cannot determinate image file name. What im doing wrong?
Thanks!
Lenino83 said:
Hello
How to flash oryginal soft on this tablet. Can you help with this ?
I tried SDK and wiped all system but now i cannot flash the system. How should i do it ?
I have firmware fros ASUS page and now what?
I tried fastboot flash update... but i have measege that unknown partition and cannot determinate image file name. What im doing wrong?
Thanks!
Click to expand...
Click to collapse
download the OTA zip from the asus website
unzip once, you should have another zip
power on the tablet while holding volume up to boot into recovery mode
after the android robot shows up, hold volume up and press the power button to get the recovery menu to show
install the zip using adb sideload
using adb sideload will differ depending on what OS you're using. you can google to find out more specific instructions for that because it's a little more work to get it for windows. for OSX if you have homebrew, you can just 'brew install android' and it will install all the android tools for you.
once you have adb installed, in the terminal type 'adb sideload pathname_of_zip.zip' and it will restore your device to factory settings
I had the same problem and your trick saved me from sending it back. I am not sure if i would have send it back as I have yet to brick something since I am playing with android back in the days of Viewsonic gtablet. We are stuck with 4.2.
Sent from my T0LTE using Tapatalk
help
tkuichooseyou said:
Found out that to get the recovery menu to show up, you have to hold the power button and press volume up. I thought that the menu would show up automatically so I got confused. ADB sideloaded the Asus OTA .zip and everything is back to normal
Click to expand...
Click to collapse
hello
got like the same problem.. dead robot, no boot, in recovery does not want to update from ota file.
Can u explain please how to ADB sideload ota.zip?
What I need, drivers and step by step?
I tried but I get no device in adb
Thank you:crying:
ionratiu2000 said:
hello
got like the same problem.. dead robot, no boot, in recovery does not want to update from ota file.
Can u explain please how to ADB sideload ota.zip?
What I need, drivers and step by step?
I tried but I get no device in adb
Thank you:crying:
Click to expand...
Click to collapse
You have to download adb or android sdk, or google how to install adb. Once you have installed the adb, hold the power button, and either Volume UP or down to put tablet into bootlfash recovery mode. Once you have it in recovery mode, push volume up or down to get into true recovery mode.
There you would see adb sideload.
Download US or WWW files from Asus website, and unzip the file into ADB directory or whatever path. then type adb sideload name of the file.
Please read the 1st post by OP on this thread twice or three times, and it tells you how to get your tablet back from brink.
back
rob_z11 said:
You have to download adb or android sdk, or google how to install adb. Once you have installed the adb, hold the power button, and either Volume UP or down to put tablet into bootlfash recovery mode. Once you have it in recovery mode, push volume up or down to get into true recovery mode.
There you would see adb sideload.
Download US or WWW files from Asus website, and unzip the file into ADB directory or whatever path. then type adb sideload name of the file.
Please read the 1st post by OP on this thread twice or three times, and it tells you how to get your tablet back from brink.
Click to expand...
Click to collapse
Got it. Done! the tablet is running again, but I encounter another issue
I have no permission to write internal sd.
I cant touch internal, some apps that require writing don't work (play store, camera, etc) I cant root, unlock or do anything that require w permissions.
Any way to fix that?
Or I have to wait for a CWM and rom image ?
ionratiu2000 said:
Got it. Done! the tablet is running again, but I encounter another issue
I have no permission to write internal sd.
I cant touch internal, some apps that require writing don't work (play store, camera, etc) I cant root, unlock or do anything that require w permissions.
Any way to fix that?
Or I have to wait for a CWM and rom image ?
Click to expand...
Click to collapse
You can download king's root or something which is a window app, and it does give your tablet root. I am not exactly sure about the name, but would let you know once I have access to my laptop.
Sent from my T0LTE using Tapatalk
ASUS MEMO PAD FHD10 ME302KL frozen logo screen
I have problem with my asus memo pad 10. It just shows asus logo startup screen and nothing more and it have no reaction with anything I do.
Please help!
I can't boot into recovery mode, but there is no problem to boot into fastboot mode!
Could anyone provide stock recovery file or link? Then I can flash recovery and do the adb sideload.
Thanks!!
Ok, so I attempted to root a Nabi 2 so I could use the SD card to hold apps since the onboard memory is terrible and I bricked the dang thing. I unlocked root supposedly using a one click app method, then I was able to attempt to update using the updater already on the Nabi. During the reboot, thats when it bricked. It is stuck in a constant boot loop mode that eventually ends up on a dead android screen.
My main problem is I know there has got to be a way to restore a stock rom/os on it, but every how to guide out there assumes that I already know what the hell they are talking about. SDK, ADB, HIV, STD, its irritating. Also, I tried TWRP, ADB, etc. but since the Nabi is in a constant boot loop and dead android screen, I can't get my PC to recognize it for more than 5 seconds. Is there a step by step guide to what I need to do for a novice? Like step 1. "since your PC can't recognize the device in the first place this is where you start". Step 2, use "this program, then this, and this is why".
Can anyone out there help me get pointed in the right direction? I am tech savvy but the existing guides assume too much, have broken links, and don't say anything about what to do when you can't even get your device to be recognized.
Thanks
Aaron
I am pretty sure TWRP is the way to go but it isn't able to manipulate the Nabi, and I can't install drivers, etc or do anything else due to the constant reboot.
Higher-Primate said:
I am pretty sure TWRP is the way to go but it isn't able to manipulate the Nabi, and I can't install drivers, etc or do anything else due to the constant reboot.
Click to expand...
Click to collapse
So what version of software was the Nabi running? There are 3 different versions of TWRP depending on if you were on Ice Cream Sandwich, Jellybean, or Kitkat.
First of all to stop the bootloop can you get to the bootloader screen? Power up by holding the power and vol - (or maybe vol + I never pay that much attention). You should see a screen with little lines of text that say "fastboot protocol, recovery kernel, forced recovery, etc). If you can get there then we need to get TWRP on the device. You will need to have tablet plugged in to computer and select fastboot protocol. Now go to windows device manager and see if you see "android device" or only an unknown device. For unknown device you can try these drivers http://forum.xda-developers.com/showpost.php?p=62826514&postcount=2639
See if this will detected the device once you have fastboot running and we can work from there. NablabGUI installer. http://nabtabhacks.com/nabilabgui2015/publish.htm
If the fastboot devices button give you a device number then you can try and install TWRP.
aicjofs said:
So what version of software was the Nabi running? There are 3 different versions of TWRP depending on if you were on Ice Cream Sandwich, Jellybean, or Kitkat.
First of all to stop the bootloop can you get to the bootloader screen? Power up by holding the power and vol - (or maybe vol + I never pay that much attention). You should see a screen with little lines of text that say "fastboot protocol, recovery kernel, forced recovery, etc). If you can get there then we need to get TWRP on the device. You will need to have tablet plugged in to computer and select fastboot protocol. Now go to windows device manager and see if you see "android device" or only an unknown device. For unknown device you can try these drivers http://forum.xda-developers.com/showpost.php?p=62826514&postcount=2639
See if this will detected the device once you have fastboot running and we can work from there. NablabGUI installer. http://nabtabhacks.com/nabilabgui2015/publish.htm
If the fastboot devices button give you a device number then you can try and install TWRP.
Click to expand...
Click to collapse
I want to say it was running 4.1 or 4.2 but I'm not positive. Stupid me should have written it down. Is it possible to load any of the versions now that I have wiped it? I was able to go to the kernal mode using + and pwr, then from there I got the dead android screen. From there I did a - and + and got an option to side load recovery or boot to ADB I think it was. So since I can at least get there, is there anything I can do? Other than that, TWRP won't recognize it and says no drivers are loaded. I'm assuming because I can't get the Nabi to stay stable long enough to actually load anything on to it? The device recognizes for a few seconds then disappears.
Higher-Primate said:
I was able to go to the kernal mode using + and pwr, then from there I got the dead android screen.
Click to expand...
Click to collapse
At the screen where you selected "kernel mode", select "fastboot protocol" instead. With the tablet plugged in go to your computer and open "device manager". Look for the device. You will need to have drivers loader for fastboot before you can do anything. Once you get the drivers loaded you will need to get TWRP on device. Lets just get fastboot working first.
This is something I am working on too that might be helpful
http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119/post63390550
aicjofs said:
At the screen where you selected "kernel mode", select "fastboot protocol" instead. With the tablet plugged in go to your computer and open "device manager". Look for the device. You will need to have drivers loader for fastboot before you can do anything. Once you get the drivers loaded you will need to get TWRP on device. Lets just get fastboot working first.
This is something I am working on too that might be helpful
http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119/post63390550
Click to expand...
Click to collapse
Ok, I tried fastboot, but it doesn't really do anything. Once I go into fastboot, I have more options. Bootloader, continue, reboot bootloader, reboot, and power off. None of the options allows the Nabi to show up as a device in device manager. Everything just takes me to the dead android unfortunately.
So I guess my next question would be, how do I get drivers loaded for a device that can't show up?
Higher-Primate said:
So I guess my next question would be, how do I get drivers loaded for a device that can't show up?
Click to expand...
Click to collapse
Have you installed these drivers yet? Nabilab driver for 32 or 64 windows? http://forum.xda-developers.com/showpost.php?p=62826514&postcount=2639
The part you did where it just had bootloader, continue, etc is the correct screen you want to be in. Install the drivers and then go back to the fast boot protocol again.
aicjofs said:
Have you installed these drivers yet? Nabilab driver for 32 or 64 windows? http://forum.xda-developers.com/showpost.php?p=62826514&postcount=2639
The part you did where it just had bootloader, continue, etc is the correct screen you want to be in. Install the drivers and then go back to the fast boot protocol again.
Click to expand...
Click to collapse
Geeze, my bad! Sorry about that. I must have not seen that part. Ok, with the fastboot menu sitting there and the 64 bit drivers installed, I am able to see "android device" in the device manager, and it shows up as a fastboot device in NabiLab GUI and Tools. Now I'm excited! Whats next?
Higher-Primate said:
Geeze, my bad! Sorry about that. I must have not seen that part. Ok, with the fastboot menu sitting there and the 64 bit drivers installed, I am able to see "android device" in the device manager, and it shows up as a fastboot device in NabiLab GUI and Tools. Now I'm excited! Whats next?
Click to expand...
Click to collapse
If you are in NabiLab2015. Go in to the Nabi2 screen. There should be an option to select which version you are using(ICS, JB, KK, etc) You can cycle though install the 3 different TWRP's until you find the one that boots. Normally it needs to be in Android or TWRP not in the fastboot bootloader but I think it will still install.
If not you can go back to main screen open a command window and type.
fastboot flash recovery 2/new/recvoery/recovery.img
fastboot flash recovery 2/JB/recovery/recovery.img
fastboot flash recovery 2/ICS/recovery/recovery.img
Each line you type is a separate attempt, meaning you will have to get back to the fastboot screen each time.
Or if you are feeling frisky it should have an option to return to stock. You will lose your data doing it that way, there might be another way where you can save it.
aicjofs said:
If you are in NabiLab2015. Go in to the Nabi2 screen. There should be an option to select which version you are using(ICS, JB, KK, etc) You can cycle though install the 3 different TWRP's until you find the one that boots. Normally it needs to be in Android or TWRP not in the fastboot bootloader but I think it will still install.
If not you can go back to main screen open a command window and type.
fastboot flash recovery 2/new/recvoery/recovery.img
fastboot flash recovery 2/JB/recovery/recovery.img
fastboot flash recovery 2/ICS/recovery/recovery.img
Each line you type is a separate attempt, meaning you will have to get back to the fastboot screen each time.
Or if you are feeling frisky it should have an option to return to stock. You will lose your data doing it that way, there might be another way where you can save it.
Click to expand...
Click to collapse
It recognizes the Nabi in the device manager, and when I click Fastboot - bootloader - Devices on the Tools section of NabiLab2015, but when I go under NV7A Disney/Nick (which I think this one is) or NV7A - US, it won't show the device under either Nabi Product Tab. Also, from the command prompt for all 3 commands, I get "C:\Users\aaronf\AppData\Local\Apps\2.0\R81BWYH1.9HO\2X87EK1X.KEM\nabi..tion_0000000000000000_0001.0000_ecfca16b310dc7a8>fastboot flash recovery 2/ICS/recovery/recovery.img
error: cannot load '2/ICS/recovery/recovery.img'"
Not sure what to do next. I feel we are really close though, but the program still can't truly "see" my device I don't think.
Higher-Primate said:
It recognizes the Nabi in the device manager, and when I click Fastboot - bootloader - Devices on the Tools section of NabiLab2015, but when I go under NV7A Disney/Nick (which I think this one is) or NV7A - US, it won't show the device under either Nabi Product Tab. Also, from the command prompt for all 3 commands, I get "C:\Users\aaronf\AppData\Local\Apps\2.0\R81BWYH1.9HO\2X87EK1X.KEM\nabi..tion_0000000000000000_0001.0000_ecfca16b310dc7a8>fastboot flash recovery 2/ICS/recovery/recovery.img
error: cannot load '2/ICS/recovery/recovery.img'"
Not sure what to do next. I feel we are really close though, but the program still can't truly "see" my device I don't think.
Click to expand...
Click to collapse
Oh. I'm an idiot. I was doing this from memory. I swapped it around should be
Fastboot flash recovery 2\recovery\ICS\recovery.img
Change the other 2 accordingly
aicjofs said:
Oh. I'm an idiot. I was doing this from memory. I swapped it around should be
Fastboot flash recovery 2\recovery\ICS\recovery.img
Change the other 2 accordingly
Click to expand...
Click to collapse
No problem at all. Ok, that seemed to have done something. I put in the exact one you just changed above, and I rebooted normally, now I have a TWRP screen on the Nabi display. Now, what instructions do I need to follow? Do I still use NabiLab2015, if so the Disney/Nick or NV7A - US? Both now say "TWRP +mount:mounting /system on ext4 failed: no such file or directory.
Also, here is this if it helps. This now shows up under ADB - Android/TWRP - devices:
List of devices attached
0123456789ABCDEF recovery
NABI INFORMATION
-----------------------------------------------------------------------------
Device=[Full
Android Version= [4.1.2]
Build Date=[Dec 28 2013]
Bootloader=[unknown]
Nabi Serial=[]
Higher-Primate said:
Also, here is this if it helps. This now shows up under ADB - Android/TWRP - devices:
List of devices attached
0123456789ABCDEF recovery
NABI INFORMATION
-----------------------------------------------------------------------------
Device=[Full
Android Version= [4.1.2]
Build Date=[Dec 28 2013]
Bootloader=[unknown]
Nabi Serial=[]
Click to expand...
Click to collapse
Good. Progress.
Let's try the other TWRP's. The /system not mounted sounds like a wrong TWRP version.
In TWRP go to the reboot tab, and select reboot bootloader.
In NabiLab command prompt try
fastboot flash recovery 2\recovery\JB\recovery.img
EDIT: Also let me know, do you want to try and save your data or just start fresh with latest Nabi software.
aicjofs said:
Good. Progress.
Let's try the other TWRP's. The /system not mounted sounds like a wrong TWRP version.
In TWRP go to the reboot tab, and select reboot bootloader.
In NabiLab command prompt try
fastboot flash recovery 2\recovery\JB\recovery.img
EDIT: Also let me know, do you want to try and save your data or just start fresh with latest Nabi software.
Click to expand...
Click to collapse
Ugh, it seems the only one that will do anything is the first one: Fastboot flash recovery 2\recovery\ICS\recovery.img. That one at least gave me something under devices. The other two android versions JB and KK didn't show up as a device at all. Also, when trying to open the NabiGUI program now, it crashes out. So maybe its the program causing the issue of not seeing the other two versions of Android? I dunno. Also, a fresh start with the latest Nabi software would be just fine. This whole thing started out with me wanting to utilize expandable SD card storage for apps so if that can actually be done, awesome! But bottom line, if this thing just works again I am cool with that too.
Higher-Primate said:
Ugh, it seems the only one that will do anything is the first one: Fastboot flash recovery 2\recovery\ICS\recovery.img. That one at least gave me something under devices. The other two android versions JB and KK didn't show up as a device at all. Also, when trying to open the NabiGUI program now, it crashes out. So maybe its the program causing the issue of not seeing the other two versions of Android? I dunno. Also, a fresh start with the latest Nabi software would be just fine. This whole thing started out with me wanting to utilize expandable SD card storage for apps so if that can actually be done, awesome! But bottom line, if this thing just works again I am cool with that too.
Click to expand...
Click to collapse
If the program is crashing open windows task manager and see if any ads.exe are running or try rebooting the computer.
So let's get back to what worked. Use the same commands as you did to get it working the first time.
In TWRP on tablet. Try going to wipe tab and do a factory reset. Just to see if it will wipe the system.
aicjofs said:
If the program is crashing open windows task manager and see if any ads.exe are running or try rebooting the computer.
So let's get back to what worked. Use the same commands as you did to get it working the first time.
In TWRP on tablet. Try going to wipe tab and do a factory reset. Just to see if it will wipe the system.
Click to expand...
Click to collapse
Ok, I tried the Fastboot flash recovery 2\recovery\ICS\recovery.img command again, it worked, then I went into the TWRP on the tablet, did a complete wipe, and now it is stuck on the Nabi logo screen. About all I can do to it now is reboot it into fastboot and nothing else.
Higher-Primate said:
Ok, I tried the Fastboot flash recovery 2\recovery\ICS\recovery.img command again, it worked, then I went into the TWRP on the tablet, did a complete wipe, and now it is stuck on the Nabi logo screen. About all I can do to it now is reboot it into fastboot and nothing else.
Click to expand...
Click to collapse
-Best done with external SD card.
-Boot to TWRP by booting tablet to bootloader menu. (With tablet powered down press and hold both Vol- and power)
-Select recovery kernel with vol keys
-Do a back up of just the boot partition in TWRP. Just check "boot" and nothing else. Make sure you are backing up to external storage(MicroSD card)
Install 3.0.13 ROM and bootloader.
- Download 3013 stock ROM https://drive.google.com/file/d/0B08qqrSbn4djOFQ1a0cwQjVEV2M/view?usp=sharing
- Put SD card in computer. Navigate to the folder TWRP/BACKUPS/XXXX. XXX is a serial number unique to your Nabi.
- Make a new folder and call in whatever you want. So it should now look like TWRP/BACKUPS/XXX/yourfolder
- Unzip the 3013stock.zip file you downloaded in to the "yourfolder" you created above. The files should look like ext4.system.win, emmc.boot.win, ext.addon.win, etc. This should set you up for the 3.0.13 ROM.
- Download the KK3013bootloader zip https://drive.google.com/file/d/0B08qqrSbn4djcnVTYjI0dTJSQjA/view?usp=sharing.
- Copy it to the SDcard. This will be for the bootloader update.
- Put sdcard in Nabi
- Boot to TWRP
- Go to restore tab, and find the backup under the "yourfolder" you made on the external SD card and unzipped the files to.
- You should be able to select boot, system, and addon and skip the others.
- If everything restores then go to TWRP "install tab", find the KK3013bootloader.zip you downloaded and install it.
- Reboot
aicjofs said:
-Best done with external SD card.
-Boot to TWRP by booting tablet to bootloader menu. (With tablet powered down press and hold both Vol- and power)
-Select recovery kernel with vol keys
-Do a back up of just the boot partition in TWRP. Just check "boot" and nothing else. Make sure you are backing up to external storage(MicroSD card)
Install 3.0.13 ROM and bootloader.
- Download 3013 stock ROM https://drive.google.com/file/d/0B08qqrSbn4djOFQ1a0cwQjVEV2M/view?usp=sharing
- Put SD card in computer. Navigate to the folder TWRP/BACKUPS/XXXX. XXX is a serial number unique to your Nabi.
- Make a new folder and call in whatever you want. So it should now look like TWRP/BACKUPS/XXX/yourfolder
- Unzip the 3013stock.zip file you downloaded in to the "yourfolder" you created above. The files should look like ext4.system.win, emmc.boot.win, ext.addon.win, etc. This should set you up for the 3.0.13 ROM.
- Download the KK3013bootloader zip https://drive.google.com/file/d/0B08qqrSbn4djcnVTYjI0dTJSQjA/view?usp=sharing.
- Copy it to the SDcard. This will be for the bootloader update.
- Put sdcard in Nabi
- Boot to TWRP
- Go to restore tab, and find the backup under the "yourfolder" you made on the external SD card and unzipped the files to.
- You should be able to select boot, system, and addon and skip the others.
- If everything restores then go to TWRP "install tab", find the KK3013bootloader.zip you downloaded and install it.
- Reboot
Click to expand...
Click to collapse
What happens if it won't let me create the backup folder? It errors out and says it can't create one.
Hello there,my Wave 8 HD+ stuck in android boot logo. I downloaded the wave8hd_20151105_v1.8 update thru wireless update and install, it says error in installing:
E:error in /mnt/internal_sd/adupsfota/update.zip
(Status 7)
Installation aborted.
My tablet is now in recovery mode and cant move highlight due to no volume buttons available,i can only select the "reboot system now" option.
Any other alternative for volume button so that i could just do the factory reset??
I also followed the detailed instruction on bluewave website on how to update the said Tablet thru PC but to no avail.
i emailed both the Telecom Company from where i get my Bluewave Tablet and the Bluewave Customer support but until now they stiil haven't replied yet.
thank you very much for your immediate reply.
-Jovi
jovirex said:
Hello there,my Wave 8 HD+ stuck in android boot logo. I downloaded the wave8hd_20151105_v1.8 update thru wireless update and install, it says error in installing:
E:error in /mnt/internal_sd/adupsfota/update.zip
(Status 7)
Installation aborted.
My tablet is now in recovery mode and cant move highlight due to no volume buttons available,i can only select the "reboot system now" option.
Any other alternative for volume button so that i could just do the factory reset??
I also followed the detailed instruction on bluewave website on how to update the said Tablet thru PC but to no avail.
i emailed both the Telecom Company from where i get my Bluewave Tablet and the Bluewave Customer support but until now they stiil haven't replied yet.
thank you very much for your immediate reply.
-Jovi
Click to expand...
Click to collapse
maybe try to use adb and try to push the firmware manually.. if they have a firmware download available
toolhas4degrees said:
maybe try to use adb and try to push the firmware manually.. if they have a firmware download available
Click to expand...
Click to collapse
I did use the software Rockchip Batch Tool v1.7 provided by Bluewave in their website,install the 33GT driver for my tab(Tab can now be seen by my PC and download the correct firmware update(using my serial number at the back of said tablet) still provided by Bluewave,but still error in upgrade..
i just want to know how to change the highlighted option in recovery mode so i can wipe/factory reset my Tablet disregarding the said update..
there is an option in recovery mode "recover system from back up" but i could not choose to highlight and select the option..
any alternatives for the volume button??Btw,the firmware provided by Bluewave is in ".img" format,not "zip"..
thank you so much for your reply..
-Jovi
i have the same problem, got an error after wireless update.. please help!
to fix this... use your otg cable and connect a usb mouse then reboot it once its reboot use the mouse to move into the recovery mode... wipe data and cache then select update adb sideload once inside the sideload press the power button until it reboot.. once you see the bluewave and its start to have a loading in the lower right corner.. voila... your tablet is fix ... hope it help u
ohgnevets said:
i have the same problem, got an error after wireless update.. please help!
Click to expand...
Click to collapse
wave 8hd+
jho_zep said:
to fix this... use your otg cable and connect a usb mouse then reboot it once its reboot use the mouse to move into the recovery mode... wipe data and cache then select update adb sideload once inside the sideload press the power button until it reboot.. once you see the bluewave and its start to have a loading in the lower right corner.. voila... your tablet is fix ... hope it help u
Click to expand...
Click to collapse
hello, jho_zep, thank you so much for your reply, i am now able to move the highlight to select using my mouse, but still when i try to update from ADB, it tells me to send package to the device etc.. and i also tried to press the power button, it wont reboot the system, it would only shutdown the system.. another thing, i still cant get rid of the system update. " installing system update" then error comes in, my android is down.. i tried wipe date/ factory reset, still nothing.
Thanks in advance
Do you already solve your problem? because I have now the same problem as this.
I have pressed the wireless update then it restarted and it says an Error status 7.
I don't know what to do and how to deal with this problem.
can you help me?
My nextbook tablet rk3026 has a partition named metadata that holds the recovery boot commands. You could possibly try to wipe it and do a factory reset. I don't think it actually gets mounted so you would need to find a file the same size as the partition and dd to it. Or back up your system with rockchip flash tool then using a hex editor replace all data in metadata image with zeros. Obviously be careful. Here is a tool download with included guide credits to finless at freaktab(not sure if he is here at xda) for posting it.
http://freaktab.com/forum/developme...p-your-rk-device-rom-with-the-new-rk-2-1-tool
as always BACKUP and know if you don't do it correctly you may get a brick.
thank you for the response Destructos. but that solution won't help for my freakin weird tab 33gt HD+.
I get frustrated now
Problem solved
first thing to do is make sure that you have already installed the rkchip_usb driver in your computer.
What are the requirements?
1st of course your Tablet and Cable Connector
2nd Finless ROM Flash Tool v1.37
3rd Rokchip BatchTool v1.7
4th the update image/firmware for your Bluewave 8 HD+ that is downloadable from their official website
Steps:
1. off your tablet and connect it to the computer
2. open the Finless Rom Flash, uncheck all the boxes
3. turn ON your Tablet (be attentive) and while the blue screen is starting you may NOTICE that the ROM FLASH TOOL detected your device, it says "RKAndroid Mass Storage USB". when you have read that, press immediately the "Reboot Flash mode" and your device will in black screen. but ROM Flash tool still detected your device as "RKAndroid Mass Storage USB "
4. Open the Batch Tool, (you must know how to use it) find your image, then you will notice that the CONNECTED DEVICES below have color green, in that case you may now Click UPGRADE. wait for a minute and booooom, you device is functionable again.
have a feedback if it is helpful.
P.S.
before I go to that steps, when I am stuck in RECOVERY MODE of my device, I Click the Recover from BACKUP then my tablet restarts and it turns to BOOTLOOP and repeatedly saying NO COMMAND.
PLDC said:
first thing to do is make sure that you have already installed the rkchip_usb driver in your computer.
What are the requirements?
1st of course your Tablet and Cable Connector
2nd Finless ROM Flash Tool v1.37
3rd Rokchip BatchTool v1.7
4th the update image/firmware for your Bluewave 8 HD+ that is downloadable from their official website
Steps:
1. off your tablet and connect it to the computer
2. open the Finless Rom Flash, uncheck all the boxes
3. turn ON your Tablet (be attentive) and while the blue screen is starting you may NOTICE that the ROM FLASH TOOL detected your device, it says "RKAndroid Mass Storage USB". when you have read that, press immediately the "Reboot Flash mode" and your device will in black screen. but ROM Flash tool still detected your device as "RKAndroid Mass Storage USB "
4. Open the Batch Tool, (you must know how to use it) find your image, then you will notice that the CONNECTED DEVICES below have color green, in that case you may now Click UPGRADE. wait for a minute and booooom, you device is functionable again.
have a feedback if it is helpful.
P.S.
before I go to that steps, when I am stuck in RECOVERY MODE of my device, I Click the Recover from BACKUP then my tablet restarts and it turns to BOOTLOOP and repeatedly saying NO COMMAND.
Click to expand...
Click to collapse
Why is it, when I do this, my tablet can't be detected by the software? I'm stuck on recovery mode. When it's on the blue logo, still does nothing.
I can only see my device when I look for it on Device Manager under Android Phone. Why is that? It doesn't show the "Other Devices". I've installed the driver but to no avail, still fails me. Please help. Thanks!
Hi all!!
This is for all the people who managed to softbrick (or hardbrick) their Lenovo Tab 3 8' (TB3-850F) tablets!
All you will need link, at the end of the post. I don't know for how long it will be up, but you can use it for now.
By the way.... Should you find something useful here... please hit the thanks button in the end
A. Unbrick
This requires flashing a clean stock rom. You will need:
a. stock rom for the TB3-850F (Google is you friend )
b. Sp Flashtool (you can download from their official site). From there, also download the MediaTek USB VCOM drivers and Driver Auto Installer v1.1236.00 (or any latest version).
Steps:
1. Install the windows drivers you downloaded
Note : If you encounter problems installing Windows drivers in Windows 10, google how to install unsigned drivers in Win10
2. Open the folder you extracted SP Flashtool and run it as administrator.
3. Unzip the rom file you downloaded.
4. Inside the folder of your unzipped rom file, look for a file similar to XXXXXXXXXX_scatter_file.txt
5. Load this in the SP Flashtool (click downlad tab, then scatter loading, load this file in there. It should load your rom you will see some colours, etc...
The tricky part:
Assuming you have correctly installed the drivers:
1. turn off the device (well if bricked it is turned off all ready) just make sure, and in SP Flashtool click options and 'with battery'.
2. Click the green download button on SP Flashtool.
3. Hold down the Vol down key on your device and connect it to a usb port.
4. If you see a red line and continue to yellow, all is probably good! Don't let go of the vol - button until yellow line reaches 100%
B. Root and TWRP recovery
This requires that you have or download:
a. platform tools (adb and fastboot)
b. a twrp.img (image file) for the lenovo TB3-850F copied to external SD Card and platform tools folder (google is... useful )
c. latest supersu.zip (flashable) copied to an external SD CARD
d. busybox.apk
Steps:
1. Grab tablet, go to settings ---> about tablet ---> click version number 7 times to enable developer options
2. From settings again click developer options and enable OEM Unlocking and usb debugging
3. Navigate in the platform tools folder. While holding SHIFT right click and select open commandline here (or similar)
4. Connect tablet to PC and in the command line issue: adb devices
If a weird number shows up and says device on the left you are all good to continue.
5. Now on the command prompt again issue: adb reboot bootloader
Your tablet should now reboot to fastboot (big Android, laying down)
6. Issue command: fastboot oem unlock (also check tablet screen for confirmation)
Wait a little bit and reboot your tablet. (should work with holding the power key down for a little longer than 10 seconds. If not hold down volume key and power button for the same amount of time - tested and working)
**At this point it is ESSENTIAL to leave the tablet to fully boot. The bootloader unlock triggers a FACTORY RESET which you must leave to complete and set up your tablet from the beginning.
** It is also ESSENTIAL to complete the boot and set up cycle because, after the automatic factory reset you will need to RE-ENABLE developer options and usb debugging. Once you are done continue to 7.
7. In the platform tools folder copy the twrp.img (you should have downloaded earlier, check upwards... )
8. Open the command line again and type:
a. adb reboot bootloader
b. fastboot boot twrp.img
** This will load up TWRP recovery only for this boot time.
****BE EXTRA CAUTIUS TO -NOT- ALLOW twrp to make modifications. Essential! Should you do otherwise go back to how to unbrick your tablet.
9. Choose install, and install supersu.zip.
10. Choose reboot to system and allow complete boot cycle! Essential!
11. Your tablet should now be rooted. However to succesfully flash the twrp recovery you need to have Busybox installed. Download as .apk and install it (at the time of writing this I believe Busybox 54 is the latest version).
12. Once installed back to the windows terminal and issue:
a. adb reboot bootloader
b. fastboot boot twrp.img
ONCE AGAIN - DO -NOT- ALLOW twrp to make modifications!!!!!
13. From you external SD Card install twrp.img, select recovery when prompted.
14. Reboot to system and enjoy!!!!
Note : Install an app that makes it easy to boot to recovery. (I personally use root essentials - Trying the combination keys did nothing for me, or just poped up the chinese options menu. That does not mean the recovery has not been installed correctly. Booting to recovery from rootessential menu, boots straight to twrp)
All you will need and credits:
https://drive.google.com/drive/fold...ourcekey=0-SDvJaXtWWk-TY9B53ct8dw&usp=sharing (thanks button, thanks button, thanks button!!! )
Results:
(it is in Greek, but you get the idea )
Hope I have helped! Happy playing with the commands and whole process! :good:
Lastly, if you get stuck at any point, you can either use this thread or PM me for further advice, explanation and/or any kind of assistance.
Note: Special thanks to @MotoJunkie01 for actually taking the time to further help people on this thread, as unfortunately I do not currently have the time to do so myself. It is worth checking out @MotoJunkie01 's threads also. There, you can find very useful and updated information.
r&xp said:
Hi all!!
This is for all the people who managed to softbrick (or hardbrick) their Lenovo Tab 3 8' (TB3-850F) tablets!
If you find it useful, just hit thanks in the end
A. Unbrick
This requires flashing a clean stock rom. You will need:
a. stock rom for the TB3-850F (Google is you friend )
b. Sp Flashtool (you can download from their official site). From there, also download the MediaTek USB VCOM drivers and Driver Auto Installer v1.1236.00
Steps:
1. Install the windows drivers you downloaded
2. Open the folder you extracted SP Flashtool and run it as administrator.
4. Unzip the rom file you downloaded.
4. Inside the folder of your unzipped rom file, look for a file similar to XXXXXXXXXX_scatter_file.txt
5. Load this in the SP Flashtool (click downlad tab, then scatter loading, load this file in there. It should load your rom you will see some colours, etc...
The tricky part:
Assuming you have correctly installed the drivers:
1. turn off the device (well if bricked it is turned off all ready) just make sure, and in SP Flashtool click options and 'with battery'.
2. Click the green download button on SP Flashtool.
3. Hold down the Vol down key on your device and connect it to a usb port.
4. If you see a red line and continue to yellow, all is probably good! Don't let go of the vol - button until yellow line reaches 100%
B. Root and TWRP recovery
This requires that you have or download:
a. platform tools (adb and fastboot)
b. a twrp.img (image file) for the lenovo TB3-850F copied to external SD Card and platform tools folder (google is... useful )
c. latest supersu.zip (flashable) copied to an external SD CARD
d. busybox.apk
Steps:
1. Grab tablet, go to settings ---> about tablet ---> click version number 7 times to enable developer options
2. From settings again click developer options and enable OEM Unlocking and usb debugging
3. Navigate in the platform tools folder. While holding SHIFT right click and select open commandline here (or similar)
4. Connect tablet to PC and in the command line issue: adb devices
If a weird number shows up and says device on the left you are all good to continue.
5. Now on the command prompt again issue: adb reboot bootloader
Your tablet should now reboot to fastboot (big Android, laying down)
6. Issue command: fastboot oem unlock (also check tablet screen for confirmation)
Wait a little bit and reboot your tablet.
**At this point it is ESSENTIAL to leave the tablet to fully boot. The bootloader unlock triggers a FACTORY RESET which you must leave to complete and set up your tablet from the beginning.
** It is also ESSENTIAL to complete the boot and set up cycle because, after the automatic factory reset you will need to RE-ENABLE developer options and usb debugging. Once you are done continue to 7.
7. In the platform tools folder copy the twrp.img (you should have downloaded earlier, check upwards... )
8. Open the command line again and type:
a.adb reboot bootloader
b.fastboot boot twrp.img
** This will load up TWRP recovery only for this boot time.
****BE EXTRA CAUTIUS TO -NOT- ALLOW twrp to make modifications. Essential! Should you do otherwise go back to how to unbrick your tablet.
9. Choose install, and install supersu.zip.
10.Choose reboot to system and allow complete boot cycle! Essential!
11.Your tablet should now be rooted. However to succesfully flash the twrp recovery you need to have Busybox installed. Download as .apk and install it (at the time of writing this I believe Busybox 54 is the latest version.
12.Once installed back to the windows terminal and issue:
a.adb reboot bootloader
b.fastboot boot twrp.img
ONCE AGAIN - DO -NOT- ALLOW twrp to make modifications!!!!!
13. From you external SD Card install twrp.img, select recovery when prompted.
14. Reboot to system and enjoy!!!!
Note 1: Install an app that makes it easy to boot to recovery. (I personally use root essentials - Trying the combination keys did nothing for me, or just poped up the chinese options menu. That does not mean the recovery has not been installed correctly. Booting to recovery from rootessential menu, boots straight to twrp)
Note 2: If you encounter problems installing Windows drivers in Windows 10, google how to install unsigned drivers in Win10
I apologize for not being able to post links, but I believe the required software is not particularly hard to find.
Hope I have helped! Happy playing with the commands and whole process! I will continue to help as much as I can :good:
Click to expand...
Click to collapse
Good guide. This tablet has temperamental steps involved with custom recovery and root. This guide gives a good outline of those steps. Here is a link to my thread for Stock Android 6.0 firmware for this tablet for members who need a stock ROM.
https://forum.xda-developers.com/android/general/rom-lenovo-tab-3-8-tb3-850f-android-6-0-t3593043
---------- Post added at 09:08 PM ---------- Previous post was at 09:06 PM ----------
Sorry, didn't mean to quote the entire OP....
MotoJunkie01 said:
Good guide. This tablet has temperamental steps involved with custom recovery and root. This guide gives a good outline of those steps. Here is a link to my thread for Stock Android 6.0 firmware for this tablet for members who need a stock ROM.
https://forum.xda-developers.com/android/general/rom-lenovo-tab-3-8-tb3-850f-android-6-0-t3593043
---------- Post added at 09:08 PM ---------- Previous post was at 09:06 PM ----------
Sorry, didn't mean to quote the entire OP....
Click to expand...
Click to collapse
Thank you, I appreciate your comment. I was really enthusiastic to read that you are working on a pure Stock Android 6.0 ROM for this device! Will definitely be waiting for that!
Thank you again!
r&xp said:
Thank you, I appreciate your comment. I was really enthusiastic to read that you are working on a pure Stock Android 6.0 ROM for this device! Will definitely be waiting for that!
Thank you again!
Click to expand...
Click to collapse
Thank you for the encouragement. I am in hopes that we can eventually get a dedicated device forum for the tb3-850f. I truly believe this tablet has the potential for plenty of future development.
@r&xp I love you so much, I was in the same predicament as you and you helped get my tablet running again. Just wanted to mention, I had to hold volume down when plugging in the USB for the SPFT step instead of volume up. THANK YOU AGAAAAAAAAAAIN <3
Rimmir said:
@r&xp I love you so much, I was in the same predicament as you and you helped get my tablet running again. Just wanted to mention, I had to hold volume down when plugging in the USB for the SPFT step instead of volume up. THANK YOU AGAAAAAAAAAAIN <3
Click to expand...
Click to collapse
Thanks for the comment!!! :silly:
Glad it worked for you. Isn' t it like a really good feeling when you actually see your bricked device boot correctly for the first time after you had almost deemed it unusable???
(also... a... small request... could you please click on that thingy... you know... that ehhh... thanks button??? :angel::angel:)
Just an update, since damaging my TB3-850F, I have since ordered another unit from Office Depot which is due to be delivered Monday or Tuesday. Once it arrives, I'll finish my TWRP flashable stock 6.0 ROM for this device and start back on the modified stock ROM.
r&xp said:
Thanks for the comment!!! :silly:
Glad it worked for you. Isn' t it like a really good feeling when you actually see your bricked device boot correctly for the first time after you had almost deemed it unusable???
(also... a... small request... could you please click on that thingy... you know... that ehhh... thanks button??? :angel::angel:)
Click to expand...
Click to collapse
Lol yessir, thanked!
MotoJunkie01 said:
Just an update, since damaging my TB3-850F, I have since ordered another unit from Office Depot which is due to be delivered Monday or Tuesday. Once it arrives, I'll finish my TWRP flashable stock 6.0 ROM for this device and start back on the modified stock ROM.
Click to expand...
Click to collapse
Looking forward to it. I picked mine up from walmart just yesterday for using as a google maps/car media center
My Lenovo Tab 3 replacement finally arrived in the mail. I'll be picking up where I left off on compiling both unmodified stock and custom stock-based ROMs for this tablet.
On my modified stock based ROM, I'm considering the implementation of Substratum (Root Ver) for theming, but I would like to get the input of other device owners first. So far, I have debloated, deodexed and zipaligned the OS. I am including the modified/patched boot image with SuperSU v2.79 SR3 binaries installed for systemless root, Nova Launcher, Pixel Icon Pack, BusyBox v1.26.2 binaries pre-injected in /su/xbin/, and Kernel Adiutor-Mod installed in /system/apps/ for user defined adjustments to the stock kernel and governors.
You guys please give me input on what you would like included in the ROM. Thanks
r&xp said:
Hi all!!
This is for all the people who managed to softbrick (or hardbrick) their Lenovo Tab 3 8' (TB3-850F) tablets!
Click to expand...
Click to collapse
I had a Lenovo Tab3 that bricked during the initial set up and this saved me for having an expensive paperweight! The process worked like a charm. You ROCK!
chienfou said:
I had a Lenovo Tab3 that bricked during the initial set up and this saved me for having an expensive paperweight! The process worked like a charm. You ROCK!
Click to expand...
Click to collapse
Really glad it worked for you!!!
Thumbs up! :good::good:
load the scatter file .txt in SP Flashrom is OK ... it show me purple color until finish loading the file.
but how come when I hit the green button Download, it seems like nothing downloading,
thanks God, and thank you so muchhh muchhh muchhh for saving my tablet... after 2 days struggling with this brick
thank you the topic thread and MotoJunkie01 led me here :crying::fingers-crossed:
yiukiang said:
thanks God, and thank you so muchhh muchhh muchhh for saving my tablet... after 2 days struggling with this brick
thank you the topic thread and MotoJunkie01 led me here :crying::fingers-crossed:
Click to expand...
Click to collapse
Try again to get TWRP installed to your /recovery partition or, alternatively, try to simply boot into TWRP from fastboot with the fastboot boot twrp.img command. It is common for members to experience some difficulty in installing custom recovery on this device. It has been my experience that most members are successful the second time around.
Thanks MotorJunkie!! But mine after was saved from brick from this thread, i was rooted it also by your instructions from other thread.. Now the gps from GoogleMap doesn't determine the location (even the location already turned on ) ... Plus i couldn't check the systemupdate ( it says connection network failed even i was connecting to wifi already) ...
What should i do, or do you know how to fix it?
yiukiang said:
Thanks MotorJunkie!! But mine after was saved from brick from this thread, i was rooted it also by your instructions from other thread.. Now the gps from GoogleMap doesn't determine the location (even the location already turned on ) ... Plus i couldn't check the systemupdate ( it says connection network failed even i was connecting to wifi already) ...
What should i do, or do you know how to fix it?
Click to expand...
Click to collapse
System updates (OTAs) won't install on rooted operating systems. To install an OTA, you must have unmodified stock /boot, /system, and /recovery partitions installed. On the GPS issue, go to Settings, Apps, and ensure Google Maps has been granted location access permission.
Hi ...
I followed this guide but during the unbricking' I unplugged the device from USB (since I could not see any input on device or indication in SP Flash Tool).
Now the device will not turn on at all (previously I would see the Lenovo Logo splash screen but then it would just stay at this screen. Now i do not see anything).
When I plug into computer by USB, it causes my computer to freeze up (Windows 10).
Any ideas or is this now completely bricked? (hard bricked).
xavier234 said:
Hi ...
I followed this guide but during the unbricking' I unplugged the device from USB (since I could not see any input on device or indication in SP Flash Tool).
Now the device will not turn on at all (previously I would see the Lenovo Logo splash screen but then it would just stay at this screen. Now i do not see anything).
When I plug into computer by USB, it causes my computer to freeze up (Windows 10).
Any ideas or is this now completely bricked? (hard bricked).
Click to expand...
Click to collapse
It sounds like a hard brick. I can't speak for the OP, @r&xp on this, so you may want to get his advice. Have you tried the OP's methods of using your hardware buttons for forcing the device into adb/fastboot recognition? I think this is your only chance of recovering it. By it not powering on, from my experience, a bootloader or bootloader dependent partition has been corrupted, thus hard bricking the tablet.
MotoJunkie01 said:
It sounds like a hard brick. I can't speak for the OP, @r&xp on this, so you may want to get his advice. Have you tried the OP's methods of using your hardware buttons for forcing the device into adb/fastboot recognition? I think this is your only chance of recovering it. By it not powering on, from my experience, a bootloader or bootloader dependent partition has been corrupted, thus hard bricking the tablet.
Click to expand...
Click to collapse
Hello, I'll weigh in on this one. There are multiple threads above the TB3-850F on this forum and also another forum.
I initially followed a different thread and instructions which caused my problem. Notably do not allow TWRP write access !!! This mistake caused the soft-brick.
Anyone following any other advice about TB3-850F or downloading any other image BEWARe. Only follow the advice in this thread by r&xp:
https://forum.xda-developers.com/android/help/lenovo-tab-3-8-tb3-850f-unbrick-root-t3598727
Following this advice I now restored original image and then rooted in just a few hours.. Thank you r&xp for the good advice. :laugh: