Hi all, Does anyone know of an “unbrick” solution for a B70 Transformer on SBK2? I gave my tablet to my brother to try out as he was thinking of getting one and he decided to see how hard it would be to un-root it in case he ever needed to. Well I guess he answered that question as now it won’t boot past the EeePad/Asus logo screen. The loading bar gets about half way across and then it just sits there. I can get into APX mode, but cannot access recovery and it’s not recognized by my PC anymore for use with ADB.
I’ve searched around a lot and found several options if it wasn’t an SBK2 device, but it is, and I haven’t found anything yet.
Any advice, thoughts or ideas would be appreciated.
**Update - When trying to boot into recovery (Vol - and power) the status at the top of the screen reads:
Android US_epad-user bootloader , e. release by "US_epad-8.2.3.9-20110423".
Checking for android ota recovery
Related
Never like to have to resort to posting myself but I've had a decent look around the web and can't seem to find a solid solution to my problem so I'm hoping to get some specific help
So I have a UK MZ601 3G Motorola Xoom which was happily running Moray 2.2.1 and had been rooted using the universal root method. Decided to update to 2.2.2 and now my Xoom is stuck in a boot-loop on the custom rippling water boot animation.
The tablet hangs on the first line when trying to boot into recovery so for all my efforts cannot access CWM and perform a hard reset and fresh rom install.
I've tried - and I'm assuming I'm correct in thinking this means I cannot get the Xoom to any stage where I can use adb to attempt to get in to recovery or push files to the system etc. this way.
From what I've read on other forum posts - booting holding volume up and power puts the device into an 'RSD' state which is another method of reflashing the device? I've read this requires an 'SBF' file - which I have seen for download - but believe it only works for the US models?
I've left the boot screen looping overnight - so its not an issue of it just being slow. Because of the custom boot screen I obviously can't return it to the shop as I presume its an obvious warranty void?
Would massively appreciate any help in bringing whats looking increasingly like a £500 paper weight back to life.
Thanks
crozuk said:
Never like to have to resort to posting myself but I've had a decent look around the web and can't seem to find a solid solution to my problem so I'm hoping to get some specific help
So I have a UK MZ601 3G Motorola Xoom which was happily running Moray 2.2.1 and had been rooted using the universal root method. Decided to update to 2.2.2 and now my Xoom is stuck in a boot-loop on the custom rippling water boot animation.
The tablet hangs on the first line when trying to boot into recovery so for all my efforts cannot access CWM and perform a hard reset and fresh rom install.
I've tried - and I'm assuming I'm correct in thinking this means I cannot get the Xoom to any stage where I can use adb to attempt to get in to recovery or push files to the system etc. this way.
From what I've read on other forum posts - booting holding volume up and power puts the device into an 'RSD' state which is another method of reflashing the device? I've read this requires an 'SBF' file - which I have seen for download - but believe it only works for the US models?
I've left the boot screen looping overnight - so its not an issue of it just being slow. Because of the custom boot screen I obviously can't return it to the shop as I presume its an obvious warranty void?
Would massively appreciate any help in bringing whats looking increasingly like a £500 paper weight back to life.
Thanks
Click to expand...
Click to collapse
When you press volume up and power, and hold it, it reboots, yeah? Then you wait about three seconds on dual core screen and tap volume down...what happens then? Do you see android recovery in upper left? Or starting fastboot protocol? Where does it hang? Just trying to see where things are going wrong. If you can get into starting fastboot protocol you are in good shape. If you can get into cwm recovery you should be in great shape. Check out the Xoom Heaven thread in General for some info on recovery.
You are most likely far from bricked...almost all of us have recovered from worse situations than you are in now so just keep cool.
okantomi said:
When you press volume up and power, and hold it, it reboots, yeah? Then you wait about three seconds on dual core screen and tap volume down...what happens then? Do you see android recovery in upper left? Or starting fastboot protocol? Where does it hang? Just trying to see where things are going wrong. If you can get into starting fastboot protocol you are in good shape. If you can get into cwm recovery you should be in great shape. Check out the Xoom Heaven thread in General for some info on recovery.
You are most likely far from bricked...almost all of us have recovered from worse situations than you are in now so just keep cool.
Click to expand...
Click to collapse
Thanks for your reply - tried numerous times getting into recovery - get stuck with one line of 'starting fastboot protocol' and seems to hang there.
Have experience rooting and flash etc. and have obviously used adb in the past.
If I could just get to recovery - or a state where I could use adb I would be fine. But as I said in my first post - looks like I can only access an 'RSD' state.
Is there any other way of getting adb access from my PC? All the help for bricked xooms seems to concern US models - and don't want to try anything that will completely write it off!
Thanks again for your help.
Quick update -
Have retried Fastboot - stuck on 'Starting Fastboot protocol support'
Tried Android Recovery - got stuck on a black screen for a long long time but finally booted!
Wiped and re-installed what I know to be a kosher ROM! Was a scary moment there but thanks for your help and reassurance!
crozuk said:
Quick update -
Have retried Fastboot - stuck on 'Starting Fastboot protocol support'
Tried Android Recovery - got stuck on a black screen for a long long time but finally booted!
Wiped and re-installed what I know to be a kosher ROM! Was a scary moment there but thanks for your help and reassurance!
Click to expand...
Click to collapse
If you are still rooted and all, just for safety's sake, make sure to do another nandroid backup and save it to your micro sdcard. Backup, backup, backup. Then also make sure that you have a compatible cwm recovery installed, that will let you access your microsd card. It sounds like you're alright, so, cool.
Hi all, I have an Android tablet (Diablotek D2-721, very cheap I know, but it serves its purpose) that is stuck in a boot loop. The real problem here is that this device apparently does not have any sort of recovery mode and being in a boot loop means it does not get recognized by ADB or any firmware flashing software.
I researched all day yesterday perusing forum after forum but almost every single solution requires booting into recovery. Is anyone able to shed any light and tell me what my options might be at this point?
Thanks in advance.
S1lent Echoes said:
Hi all, I have an Android tablet (Diablotek D2-721, very cheap I know, but it serves its purpose) that is stuck in a boot loop. The real problem here is that this device apparently does not have any sort of recovery mode and being in a boot loop means it does not get recognized by ADB or any firmware flashing software.
I researched all day yesterday perusing forum after forum but almost every single solution requires booting into recovery. Is anyone able to shed any light and tell me what my options might be at this point?
Thanks in advance.
Click to expand...
Click to collapse
Maybe you can try to flash a recovery like CWM via ODIN.
Just my 2 cents!!
No, I cannot flash anything because the tablet refuses to talk to my computer while in this boot loop. I tried ADB, Odin, and the manufacturer's flashing tool but nothing would register the device as being connected. Plus I set up a second operating system and tried doing all of the same things on Windows 7 because Windows 8 has been problematic with drivers but it still made no difference. Still, thanks for the suggestion. x.O
The matter is null now. I just took it back and got another tablet, one with a recovery mode.
For anyone searching on this D2-721 tablet, be wary because with no recovery mode available it is very hard if nigh impossible to recover from a lot of things normally recoverable from any Android device. I tried for two days and spent hours pouring through forums but in the end my computer just could not talk to the tablet while in a boot loop. And trust me, I tried everything.
Thanks for the responses and help, it was appreciated.
Well I was gonna install omnrom 4.4.2 on my tf300 so I went in recover mode and fully wiped the data but it was taking very long time and I tought that it has jammed so I hold down the power button and it switches off then it kept boot on Asus logo then it go on the teamwin logo (recovery) and it stay on the teamwin and sometime the screen blinks but stays there then I read to do APX I downloaed the drivers from this site and install them and I hold power + volume up and I end up in a black screen and there where I installed the drivers the windows managed to fidn my tablet than I tried to do nvflash.exe but cant get it to work pls help me. also I cant turn off my tablet cos when I do it keep boot up get past the Asus logo and freezes at teamwin recovery logo. help pls
ConsoleFreak said:
Well I was gonna install omnrom 4.4.2 on my tf300 so I went in recover mode and fully wiped the data but it was taking very long time and I tought that it has jammed so I hold down the power button and it switches off then it kept boot on Asus logo then it go on the teamwin logo (recovery) and it stay on the teamwin and sometime the screen blinks but stays there then I read to do APX I downloaed the drivers from this site and install them and I hold power + volume up and I end up in a black screen and there where I installed the drivers the windows managed to fidn my tablet than I tried to do nvflash.exe but cant get it to work pls help me. also I cant turn off my tablet cos when I do it keep boot up get past the Asus logo and freezes at teamwin recovery logo. help pls
Click to expand...
Click to collapse
Also after I did this I was on latest TF300 stock rom 4.2.1 JB
Please help me
nvflash procedure to fallback on
This guide I collected from somewhere on these great XDA forums and I always, always made sure I created the nvflash backup and stored those files away somewhere safe FIRST before I started tinkering around with my device...usually multiple locations, locally and in cloud...I have those copies but can't share them here because they are locked to my device, are unique and just won't work for any other different device...
Look in the GENERAL section and in the troubleshooting where you have posted...there seems to be quite a few people with similar brick issues in varying degrees...there's a solution somewhere for your unique issue. Download both a 4.2 and a 4.4.2 blob/firmware as a start and learn how to unblob/extract them into their different components...you're gonna need them to get back to stock...all the best
Moe5508 said:
This guide I collected from somewhere on these great XDA forums and I always, always made sure I created the nvflash backup and stored those files away somewhere safe FIRST before I started tinkering around with my device...usually multiple locations, locally and in cloud...I have those copies but can't share them here because they are locked to my device, are unique and just won't work for any other different device...
Look in the GENERAL section and in the troubleshooting where you have posted...there seems to be quite a few people with similar brick issues in varying degrees...there's a solution somewhere for your unique issue. Download both a 4.2 and a 4.4.2 blob/firmware as a start and learn how to unblob/extract them into their different components...you're gonna need them to get back to stock...all the best
Click to expand...
Click to collapse
but its alreayd bricked i heard you need to be on ICS for nvflash to work and fastboot is keeping on waiting for device
ConsoleFreak said:
but its alreayd bricked i heard you need to be on ICS for nvflash to work and fastboot is keeping on waiting for device
Click to expand...
Click to collapse
You cannot use NvFlash unless you have already made the NvFlash Backups prior to bricking.
Hi everyone. I am new to Andriod and to XDA. Like most, I am trying to root my Android device. I have a Digiland DL721-RB that I am trying to root and it will not let me. This is a 6.0.1 Marshmallow device and it will not work with Kingo ROOT (multiple failed attempts with both ADK and PC version.) I have since factory reset the device and made it into Recovery Mode. The recovery mode shows a build MMB29M.dzr11251051.
Can this help to locate a ROM or method of accessing and unlocking the bootloader? Any assistance would be appreciated.
UPDATE: It appears that fastboot or bootloader is inaccessible via normal means. There is a pin-hole Reset button on the rear of the device that only seems to disconnect power to the entire tablet and just shuts it down. I have attempted multiple combinations of button presses to get into this area but can only access the Recovery Mode. I am using an Ubuntu shell to access the tablet and can get into the
Code:
adb shell
but most areas are "Permission denied." I also attemted
Code:
adb reboot fastboot
which reboots the tablet but gets stuck with a backlit black screen.
I see that 50 people have looked at this post since I created it so I know there is at least a minimal interest in this topic. I have been using this table for about two weeks and it is not a bad device for $40, especially if you just want something that's disposable.
Anyway, I am not looking for someone to unlock it for me. I am looking for suggestions on how to approach this as there is something I am undoubtedly overlooking. Any suggestions (besides getting a new tablet) would be appreciated. This is a challenge and I want to learn more about the process, not just unlocking it. I enjoy the application method of learning.
Thanks in advance for any assistance.
I bought the device 2 hours ago, here in Las Vegas, NV, for $19.00 USD.
I am interested in this thread getting answered.
Thanks.
phoebos
Blank screen
That blank screen IS Fastboot, oddly enough. If you dumped your ROM I can hook y'all up.
osirisale786 said:
Blank screen
That blank screen IS Fastboot, oddly enough. If you dumped your ROM I can hook y'all up.
Click to expand...
Click to collapse
I'm looking for ROM. Hook it up!
I’m desperate and frustrated at this point. I’ve been working on this for days. I will do my best to explain my situation although there is some info I don’t have.
Here is what’s happening.:
When I try booting to recovery it just says booting recovery kernel image. It sits there frozen. Does not advance.
When I boot normally it freezes on the Eee Pad screen.
When I boot while holding the volume up button, it freezes at the Eee pad screen.
When I boot to APX mode the screen goes black and my Windows 10 computer chimes. Device manager shows drivers installed for the device (no exclamation mark)
The situation:
My buddy have this to me after he bricked it trying to flash a custom rom. I don’t know what he did and he can’t seem to give me any additional information aside from he had twrp 2.8 at some point. He doesn’t remember the rom or anything. Serial number starts with BCOKAS. I’m running windows 10.
What I’ve tried:
I feel like I’ve tried everything. I tried different drivers, I’ve tried Peri, easy flasher, one click recover, and a couple other programs. I’ve tried tried all options and configurations In Easy Flasher. When I go to cmd and type adb devices (or whatever it is) it does not show any devices. Nothing I have done seems to do anything.
I’m sure I’m leaving some things out and I’m sorry if I am. Please. Please help. I get way too frustrated doing things like this and I’m close to just throwing it as high as I can to watch it break. Any insight would be much appreciated. Thanks.