Related
Hello & yes, yet ANOTHER person with this issue. This is what I've done:
It all started by going out to unlockr's page & following their rooting how-to. When I did this it put it in the never ending dell screen flashing lights loop. I've researched quite a few hrs on this. This is what I tried:
1) Doing factory restore (holding volume buttons & pwr buttons down) & choosing restore.
2) Borrowed a buddies SD card & tried a restore (did nothing)
3) Followed a couple of guys instructions on doing a restore one of them being here: http://forum.xda-developers.com/showthread.php?t=776883
After following the directions I did see it look like it was updating back to the 1.6 OS, but after it rebooted it was still stuck in the Dell flashing loop cycle.
SO I did probably the dumbest thing I could do & took it back to Best Buy who is shipping it off... most likely to get my warranty canceled, but I didn't know what else to do. I had purchased their protection plan, so I'm not sure how it's gonna go. They would have replaced it in the store, but I had already returned my 1st one as it wouldn't boot right out of the box (not my fault).
So I figure if they don't flash it at Dell & get it back to working, I'll have to keep working on it myself to correct the issue....
So I guess my question is, any advise on why mine is being so difficult or is this just the way it is & it takes several attempts to flash these things sometimes? Or has Dell implemented a security feature in the new releases & that's what is causing my headache?
Those of you who feel the need to rain down the "Dumb thing to do returning it" please save those comments as I've already stated "I know".... I just need some positive input on getting this thing back on "it's feet" IF Dell doesn't fix it for me.
I will keep you posted on the Best Buy/Dell Drama that I'm sure will start up... I will say that if it's not fixed, I can't say that I'll continue with paying Best Buy $10 a month for a protection plan, as they supposedly will replace the phone if it was damaged in any way. If anyone has info or a story on that part of it I'd like to hear it as well.
Thanks in advance!
Look for the upgrading downgrading guide in xda. Nornally starting from 4399 build is a good start to get you back up and running.
http://android.modaco.com/content/dell-streak-streak-modaco-com/317549/how-to-go-back-from-21-to-00-builds/&source=android-home&ved=0CBoQFjAB&usg=AFQjCNH7W3lUKYibzBQg4qVNxKs955Q0LQ
Sent from my Dell Streak using XDA App
DON'T USE THE UPGRADING/DOWNGRADING GUIDE!! IT WILL BRICK YOUR WHITE STREAK!!
The white Dell Streak is known to have something different going on with it. There is a special tool (QDLTool) that is needed to upgrade it/unbrick it. It takes you directly to stock 2.2 and you can do what you want from there. See this thread here for more information and a fix.
http://android.modaco.com/content/d...24010/warning-white-dell-streak-is-different/
Thanks for the knowledge! Didn't know there was a difference, although I suspected something was amiss when I was doing what I was instructed to do but not getting results....
Any more info is appreciated so keep it coming!!!
erm not that im saying this BUT you got protection(inshureance)accidently drop it in a sink full of water or some such like acident pay your excess and get a new one.
but i dint say that.There norm pritty good at replaceing your phone after such an acident
We'll see what happens when I get the phone back... the post from TopShelf95 may just have saved it from a fate similar to that! HA!
FOR WHITE DELL STREAKS
You'll need the QDLTools for this... so please search/google the links or posts for that.
Typed instructions from these posted from videos that I can't link to yet as I'm a noobe here...
(Hope I didn't fat finger & mistyped anything so be on the safe side & don't cut and paste command line stuff)
1) Start, type CMD in the “programs search area”, CTL, SHIFT & Enter to start command window in Admin mode.
2) Type “bcdedit –set loadoptions DISABLE_INTEGRITY_CHECKS & press “enter”
3) Type “bcdedit -set testsigning on” & press “enter”
4) Reboot
5) Go to the directory where you’ve stored the QDLTools (ex. C:\Streak\RepairTool) , then into the subfolders until you find the driver folder, open the subfolder “Driver_2.067”, Then “Test Certificate” .
6) Right click on qcusbtest & install cert
7) Choose “place all certificates in the following store” & browse
8) Install cert in the “Trusted Publishers” store, when done click “Ok”
9) Right Click on the qcusbtest cert again & select “Install Certificate” again
10) Choose “place all certificates in the following store” & browse
11) Now install cert in the “Trusted Root Certification Authorites” store
12) Click “Ok” when done
13) Remove & replace battery in Streak.
14) Hold down the Volume Up button & plug in USB cable
15) PC should detect connection & install drivers (which will fail)
16) Open control panel & go to device manager
17) Locate the “Qualcomm HS-USB Diagnostics 9002” (if it doesn’t have a yellow exclamation mark by it, you have the driver & can skip forward to
18) Right click & select “Update Driver Software”
19) Select “Browse my computer for driver software”
20) Select “Let me pick from a list of…”
21) Choose “Show All Devices” & click “Next”
22) Click on “Have Disk” & browse to the repair folder, drivers are in the Driver_2.067 folder, if you are using 64bit OS go to WIN64 (Win32 for 32bit)
23) Select WNET unless there is a folder for your version of Windows (for 64bit choose AMD64 unless you have an Intel Itanium CPU)
24) Select “qcser.inf”, click Open, then “Ok”
25) Choose “Qualcomm Incorporated” & choose “Qualcomm HS-USB Diagnostics 9002”, then click “Next”.
26) Click “Yes” if you get an Update Driver Warning dialogue box, then “close” once installed.
27) Now go back to QDLTool folder
28) DISCONNECT USB CABLE FROM STREAK
29) Start the QDLTool utility
30) On the QDLTool Upgrade Build screen the area “Device” with “Port:” in it should say “Not Connected”.
31) Make sure USB cable is UNPLUGGED & remove batter from the Streak.
32) LEAVE BATTERY OUT FOR AT LEAST ONE MINUTE
33) Replace battery & install back cover on Streak
34) Hold down Volume Up button & connect USB cable to go back into diagnostics mode
35) “Port” in the Device window will change to ”Qalcomm HS-USB Diagnostics 9002 (COM4)” once the Streak has been identified.
36) Click “Run” to start the update. Takes from 3 to 4 minutes typically.
37) IF YOU GET A FAILURE AT THIS POINT go back to steps 31 thru 34. Wait for step 35 & follow 36.
38) When it says “Waiting for Reboot” your Streak should reboot itself, ready to go into Fastboot mode
39) IF IT FAILS AT THIS POINT: your ADB drivers for fastboot are not installed correctly, so fastboot may be erroring, install drivers & restart steps 28 thru 36.
40) At this point your device should have been updated & should soon finish booting into the updated Android release.
41) Take your PC out of Test mode by going to “Start”, type CMD in the “programs search area”, CTL, SHIFT & Enter to start command window in Admin mode
42) Type in “bcdedit /deletevalue loadoptions
43) Type in “bcdedit –set testsigning off
44) Reboot
other solution
Solution # 2
Take the phone back to where you bought it and get the black one.
As some of you may know my white one met similar fate and after hours of getting no where i just took it back and got the black one.
after 20 minutes of getting it home i had froyo 2.2 running on it.
besides..do you really want a white phone? lol
i didn't. they were supposed to give me a black one to begin with..
I told the returns lady i wanted a black one and they gave me a white one. when they booted up the phone it didnt boot and they did not say one word. they just went and got me a black one.
Frankly this was the only reason i bought one from bestbuy..
it certainly wasnt because of their pricing
Good luck.
Bigfoot, if you'll reread my original post you'll see that I've already returned one & tried to return the white one, but they would only allow one instore return. I don't care if it's white or black (I'm not racist HA!) it's gonna be in a Otterbox Defender anyway. I just want a phone/tablet that works at this point.
We'll see how the above mentioned "fix" works if I have to install it when I get my phone back.
I have the white streak too and I can tell you that the QDLTool works like a dream. Just follow the instructions to the letter and you will have 2.2 on it in no time. The Streak is virtually impossible to perma-brick. Since QDLTool works on a lower level than fastboot, it will work even when all else fails.
Awesome again good to know!
Does the qdltool work for the black streak?
Sent from the Dell streak
FINALLY (update)
So after 42 days I FINALLY got my phone back from Best Buy... WORST customer experience... I would tell the whole experience, but I'll just make it short... they couldn't find it at one point, they shipped it back 42 days later, my 16 gig sd card is missing from it & when I got it back, they'd not reflashed the phone. So they did nothing but basically steal my sd card & gave it back to me....
ANYWAY.... After I went back to BB to find out what they were gonna do about my phone not working (which I'll have to call mgr tomorrow) I got home & followed the instructions given in this thread to flash my white dell streak & IT WORKED!!!! No issue 1st time around... Perfect, almost as easy as jailbreaking an iPhone... THANK YOU VERY MUCH FOR THE HELP!!! You guys are awesome...
Now... I have a friend who is also asking will this process work for the Black Dell Streaks... so will it?
also
this puts your system into an unlocked status which enables you to download the official Dell 2.2 ver. One downside to it is it shuts off your wi-fi hotspot...
Good thing about the Dell ver. it fixes the buttons sensitivity for one thing that seems to be an issue on the QDAtools ver... I'm sure later builds that is fixed though (would think it would be)
WRONG
I was wrong (looked in the wrong spot) wi fi hotspot is there... my bad
so by using the tool method on my white streak, does it mean my phone is rooted? or is there more i need to do to root my white streak?
Raikoue said:
so by using the tool method on my white streak, does it mean my phone is rooted? or is there more i need to do to root my white streak?
Click to expand...
Click to collapse
No, it won't be rooted. But that's easy to do. You can stay with Dell stock ROMs (download from their website) or go with DJ_Steve's ROM which is rooted and has lots of other features. Rooting isn't hard, though, if you stay with stock. Just use Super One Click and you'll be good. I'm not sure if either method is supposed to work, but my wife's only was rooted by the second method (rage against the cage or something like that).
Also, QDL Tool works for both black and white streaks.
I have the same situation as the OP. However when I try the instructions I make it all the way to the part of running the QDL tool. There I get an error message at about 12 seconds, during the section just after Run HEX success. The error says:
ERROR[D14]:streaming hello Failed!
ERROR: Download fail!
It then says to remove battery and try again, which I do and get another failure.
Any thoughts besides taking a hammer to this thing?
after the first time it went through the fastboot (Downloading AMSS) it rebooted and I had to manually put it back into the fastboot mode (hold camera) for it to fishing writing everything else.
It Worked Perfect!
I've moved on to the Samsung Galaxy Note... My Streak did it's year or so service as well as it could (it's still working without issue) but I wanted a phone that had actual support, I am an IT tech by day & just don't wanna have to mess with yet another system that I have to do go thru a few hundred pages of forums to figure out the true method of getting something to work or install. iPhone hackers have Android beat in that area for sure... 1 click root/jailbreak is the way it should be.... but iPhone doesn't have a 5.3" screen!!!!!!
Welcome to the comprehensive guide on rooting and unbricking your precious TF103C!
Some words of wisdom and truth
You will most likely be here because, you know, your device is bricked.
First of all, I would like to say that none of the downloadable links are made by me. I happened to find them laying around XDA after looking for a solution for a long time.
Skip this if you don't want to know the reason behind this thread
I got this device a while back (my guess is 4 months), and loved it from the start. Rooted it, of course, and soon after, it didn't want to boot anymore.
As there isn't much development going on (due to the locked bootloader), it's hard to find a solution for bricking. While scrolling, I came upon a post from member gouster3, which came to the solution below. I myself have used this successfully, and have my tablet back. In my opinion, also on rooting, there was no dedicated thread available that really explained the steps to root the device, so as a thank you to the guys who got my tablet fixed, here it is!
The rooting process
The rooting of this tablet is quite easy, really! I'll explain in a few simple steps.
Head into settings > security > then turn on unknown sources
Download the Rootzenfone .apk file. get it here
Install the app (if it is still in your notification bar you can just press the downloaded file, or you can navigate to it's location to install from there)
Turn on airplane mode before you open the app
Open the app, and hit "OK, I know, please root!" (when you press this, a number of screens and a popup will show, ignore those)
5 seconds after pressing, restart your tablet.
Hooray! You are now rooted!
Unbricking your device
Luckily, unbricking is almost as easy as rooting the phone, if you know the steps you have to follow. Here's what you could do (it worked for me) if you still have acces to DROIDboot.
As always, install the adb drivers first! get it here
# You can also make sure the correct driver is installed when plugging in the device in DROIDboot mode. In you device manager it should show up as Android Debug Bridge#
Download these files, containing a clean system. get it here
Make sure the device is turned off, and the battery is at least 50% (just to ensure a complete flash before your battery runs out)
Hold volume+ and power untill the asus screen pops up, then release the power button.
Plug in the tablet to your pc (usb cable) when DROIDboot has been loaded.
Open the downloaded folder, and find 'update_image.bat'
Right click the .bat file, and choose 'run as administrator'
A CMD screen should open on your PC indicating the flashing status. All you have to do now (assuming that it works as intended) is wait untill the process is completed.
Your tablet will reboot automatically when the process is done.
That's it! the 2 things that keep this tablet alive. I would like to send a thanks to the members who were so kind to help me out on this.
gouster3, for providing the link to the unbrick solution
Eclipse00, for giving the link to the rootzenfone apk
Monki, for giving me a clean system.img and putting effort into getting my tablet running again
To all of you, thanks!
It works on my TF103CX too. (it is same hardware).
When i bricked my TF103CX, i had around 80% of battery, but i was not able to charge,
so be careful when bricking. Always do interventions to system with full battery.
//I think, we need add our TF103C to xda device list. it will be nice.
I heared that using Intel Manufacting Tool we can get UEFI instead of Droidboot, and boot Ubuntu/Windows on IntelBay tablets. I found guide for Teclast: http://forum.xda-developers.com/android/general/teclast-x98-air-3g-tablet-9-7-2048x1536-t2913035 But i cannot find any UEFI fot TF103C. I dont want to full brick m device with trying flash it.
Here is original thread in russian language.
Thanks
Thanks for helping me rescue my tablet. Much appreciated
Could anyone please confirm if the rooting method may be used on the TF103CG (K018) model? Or in general is the app able to root any device that is anyhow Zen-related?
this don´t work if you have lillipop on tf103c, the droidboot don´t load, You only get Fasboot starting and nothing more...
i want the raw lollipop image ( system.img ) for tf103c
will this essentially work as a factory reset? mine touch isn't working; and i just want to nuke all my data off the device
Hello all, I just ordered a TF0310C (Best Buy exclusive) from woot.com which will be here tomorrow and the closest thing I can find information on is the TF103C (both are Intel processors), and just trying to find as much info on it as I can. I was unable to find any roms or anything for the TF0310c, will things from the TF103C work on the TF0310C such as rooting or custom recovery at least?
http://computers.woot.com/offers/asus-transformer-pad-10-1-android-tablet-1
Unbrick not working on tf103c running KK. It looked like it was doing something, but no luck. Any common troubleshooting tips?
m374llic4 said:
Will things from the TF103C work on the TF0310C such as rooting or custom recovery at least?
http://computers.woot.com/offers/asus-transformer-pad-10-1-android-tablet-1
Click to expand...
Click to collapse
I know its a bit late, but perhaps better than never. I'd say those devices are identical, but somehow there is a weird naming mixup. Here are the official ASUS pages for them:
http://www.asus.com/supportonly/ASUS Transformer Pad TF0310C/HelpDesk/
https://www.asus.com/Tablets/ASUS_Transformer_Pad_TF103C/specifications/
Whatever you do on the first link, it will be eventually redirected to somewhere that belongs to the second. Their specifications are also basically the same. This is still a guessing game tough, so the best would be to compare 2 build properties, partition tables etc. of those devices to know more.
Rooting will most likely work, Zenroot should do it regardless of device type.
hello,
i have tried different way to unbrick my tf103c, but none is working
i have access to fastboot
i successfully run your bat file to copy the image, but after it reboot and stays on the "asus" logo
if i launch the command after modified the name of the "AS-TF103C-v67.43-capsule.bin" into "capsule.bin", it reboot then a blue progress bar is showing, when the bar is complete the tab reboots, but again it stays on the "asus" logo :'(
do you have any advise ?
Same issue
Hello,
I have the same issue with my tf103c ; i was trying to apply a new update from asus support (to get android 5).
It didn't work and in addition to that, my device results to be bricked.
I have successfully run the bat file, but then i get stuck at Asus logo and device never boot...
Icarolo did you manage to solve your issue ? Is someone really succeed in unbrick tf103c device ?
Thank you in advance
Dead
Hi! I have an asus tf103c and i rooted it with the rootzenfone.apk but now it doesn't turn on at all. after i pressed okay, waited about 15 sec and then i restarted it, but it just turned off. And now it's dead. What should i do?
ASUS K010 (TF103C). I forgot how to enter Recovery
Hello everyone, I have an ASUS K010 (TF103C). The complete model is TF103C-MB1-BLK-DK.
I forgot how to enter Recovery. My Asus is bricked. I know it is possible to enter the recovery because a few months ago I entered and also enter droidboot mode. On that occasion I discovered pressing the buttons energy, volume +, volume - somehow, because I did not work the methods that were in different sites websites, but now I do not remember the exact way of pressing the buttons. I tried many methods but they do not work, only the "Asus looking for incredible" logo appears. The battery has a charge (I charge it manually).
If someone has this same model and knows how to enter the recovery would greatly appreciate it.:good:
I think you can enter the droidboot menu by pressing Volume Up + Power for several secondes.
i dont have acces to DROIDboot.
How can unbrick my tf103c.. thanks
i dont have acces to DROIDboot.
How can unbrick my tf103c.. thanks
Brick3d said:
Welcome to the comprehensive guide on rooting and unbricking your precious TF103C!
Some words of wisdom and truth
You will most likely be here because, you know, your device is bricked.
First of all, I would like to say that none of the downloadable links are made by me. I happened to find them laying around XDA after looking for a solution for a long time.
Skip this if you don't want to know the reason behind this thread
I got this device a while back (my guess is 4 months), and loved it from the start. Rooted it, of course, and soon after, it didn't want to boot anymore.
As there isn't much development going on (due to the locked bootloader), it's hard to find a solution for bricking. While scrolling, I came upon a post from member gouster3, which came to the solution below. I myself have used this successfully, and have my tablet back. In my opinion, also on rooting, there was no dedicated thread available that really explained the steps to root the device, so as a thank you to the guys who got my tablet fixed, here it is!
The rooting process
The rooting of this tablet is quite easy, really! I'll explain in a few simple steps.
Head into settings > security > then turn on unknown sources
Download the Rootzenfone .apk file. get it here
Install the app (if it is still in your notification bar you can just press the downloaded file, or you can navigate to it's location to install from there)
Turn on airplane mode before you open the app
Open the app, and hit "OK, I know, please root!" (when you press this, a number of screens and a popup will show, ignore those)
5 seconds after pressing, restart your tablet.
Hooray! You are now rooted!
Unbricking your device
Luckily, unbricking is almost as easy as rooting the phone, if you know the steps you have to follow. Here's what you could do (it worked for me) if you still have acces to DROIDboot.
As always, install the adb drivers first! get it here
# You can also make sure the correct driver is installed when plugging in the device in DROIDboot mode. In you device manager it should show up as Android Debug Bridge#
Download these files, containing a clean system. get it here
Make sure the device is turned off, and the battery is at least 50% (just to ensure a complete flash before your battery runs out)
Hold volume+ and power untill the asus screen pops up, then release the power button.
Plug in the tablet to your pc (usb cable) when DROIDboot has been loaded.
Open the downloaded folder, and find 'update_image.bat'
Right click the .bat file, and choose 'run as administrator'
A CMD screen should open on your PC indicating the flashing status. All you have to do now (assuming that it works as intended) is wait untill the process is completed.
Your tablet will reboot automatically when the process is done.
That's it! the 2 things that keep this tablet alive. I would like to send a thanks to the members who were so kind to help me out on this.
gouster3, for providing the link to the unbrick solution
Eclipse00, for giving the link to the rootzenfone apk
Monki, for giving me a clean system.img and putting effort into getting my tablet running again
To all of you, thanks!
Click to expand...
Click to collapse
Hi, I see that the thread is old, but I need to fix my old pad. I can do all the steps, but the problem is that I can not find a clean system I can install. I will really appreciate if someone could give me a link to one.
Unbricking tf103c
Hello,
Is it possible to unbrick somehow a device like mine. I dont have either bootloader or recovery or anything (I have two same tablets) and I mess one up. After new update touch screen stopped working so I installed something (I dont remember) i installed new recovery and then tried to install new rom...Every time I power it on (doesnt matter standar od with combos it just show asus logo in search of incredible and that's it. I managed if I press both VOL - and VOL + AND PWRBTN I get something in device manager "Unknown USB Device (Device Descriptor Request Failed)"! Is there anything I can do?
After one of my at twice weekly full nandroid backups to microSD I attempted to revert to an earlier release of the custom Marshmallow ROM I had updated from. A failed TWRP 3.x dirty flash, gave me an error message that it was unsuccessful and I could not turn my phone on or (obviously) get to Fastboot. My phone would not respond to the power button or anything else. While steps later I discovered that my power button is malfunctioning (more on that later) it did not change my QHSUSB_BULK, Qualcomm HS-USB QDLoader 9008 mode issue.
When I plugged my phone into my laptop running Windows 7 there was always an acknowledgment sound and Device Manager showed a device QHSUSB_BULK with a driver issue. This matched the numerous "Hard Brick" posts on numerous sites referring to the LG Nexus 4 (E960), our E970 and Optimus G Pro (E980) which largely share the same chipset in addition to numerous other newer phone models from LG and others with Qualcomm chipsets.
Numerous old posts stated that a JTAG repair was my only hope of reviving the late 2012 model phone that I have had for 3 years. Finding no one in driving distance with JTAG equipment, the prospect of paying $50 + two way shipping (likely approximately $70 total) seemed like an unwise investment for old hardware regardless of how much I still like it. This was reinforced after perusing eBay and my local Craigslist for suitable, somewhat newer, replacement models. While I had successfully replaced my battery months ago, I am not inclined to connect wires to anything on the motherboard to short and possibly reset anything.
== Bottom Line ==
What ended up getting my phone back to Download Mode was following a portion of the instructions here ==> http://open-freax.fr/guide-unbrick-your-lg-g3/ with a couple of changes.
You have to get the Qualcomm HS-USB QDLoader 9008 mode without any Window driver error, BoardDiag by willcracker, and an E970 TOT file ( LGE970AT-01-V20j-310-410-MAR-08-2013+0.tot or similar) before you can do anything. I ended up using an old laptop of mine (Netbook actually) since I still got a driver error after installing the 64-bit Qualcomm 9008 driver on my primary machine. I never connect my OG to that old laptop and it is running 32-bit Windows 7.
Due to my power button issue I ended up taking the back off my phone, disconnecting the battery, and putting it back in my Diztronic rubber case since LG stuck us with a non-removable battery.
E970 variation from what is detailed under "Now , let's get the party started" are in the "AP Chipset" (ours is MSM8960). The Com Port is specific to what is in your Device Manager where the QLoader 9008 shows up. As detailed, if the EMMC TEST shows a problem you are wasting your time proceeding since you have a hardware problem.
Another E970 variation is in the paragraph starting with "Now untick EMMC Test select" which is the 3rd paragraph before "Step 3: back to stock"
- There are no files with the name dbi or laf generated in our TOT extraction so skip those but proceed in the order stated.
- In the following paragraph, after flashing Sbl1 go ahead and flash Sbl2 & Sbl3. I have no idea what they do and someone more knowledgeable may say they are not necessary but it worked for me.
After that I was able unplug (remember my pwr button is not working) hold down both volume buttons, plug back in and I was in Download mode. From there I could use LGNPST which means I was no longer "Hard Bricked" but Soft Bricked, which is not that big a deal. You will not need "Step 3: back to stock" if you follow posts in XDA about Soft Brick recovery methods like Teenybin or other.
Wow, sounds like quite the process. I'm happy to know you got it working again!
Boiled down...
Once the Windows drivers are loaded and properly recognizing the phone it should not take more than 15 minutes (not counting TOT file download if needed) and not involve phone disassembly to get it into Download mode.
After my overly long post I realized that my replacement battery (in use for months) despite being identical to my OEM battery other than the date stamp, had been malfunctioning and my power button is fine. I am back to using my original battery. The process took a bit of trial and error and days for me to figure out.
The G2 (AT&T version) I snagged on eBay was delivered today but battery is discharged so I will fiddle with it after charging. Physically it appears in excellent shape but until I am able to fiddle with it I will withhold judgement.
My lg e970 is hard bricked and i need adb dump/backup to revive that . if someone can provide that it will be of great help . the procedure to create adb backup is mentioned below. i hope some noble soul will help me smile
step 1: root your device.
step 2: go to setting > about > software info > build info > tap 5-6 times until message getting to enable developer mode.
step 3: go to setting > developer option > usb debugging >Turn ON
step 4: open your PC and run adb t from cmd.exe
step 5: run this command then check your mobile screen for grant su permission.
adb shell
su
dd if=/dev/block/mmcblk0 of=/sdcard/Alive_Dump.bin bs=1024 count=1048576
step 6: AFTER THAT create 1GB dump in your phone internal main storage.
find name “Alive_Dump.bin”
note : command are case sensitive so try to direct copy paste better for no error.
Where to begin? Logic would dictate, the beginning.
I'll do my best to be brief with the backstory.
Months ago I ordered a Jide Ultratablet to use as my portable workhorse. At first things were peachy until a rather monumental lag began to manifest every 15-45 seconds. It made the device impossible to utilize in any productive fashion, so I contacted Jide and opened up a support ticket. After months (in no way an exaggeration) of barely responsive correspondence, during which I sent them a video to demonstrate the problem, they finally came back to me with an email containing a link to a compressed folder containing the Remix 2.0 images, and also a link to a rather vague and complicated tutorial on how to flash Remix 1.5 manually to a device. (In fact, I tried to include a link to the tutorial, but I am unable to since I haven't posted to the forum enough. I am happy to PM it or email it to anyone who might like to help) I can only assume I am meant to apply the same logic to the Remix 2.0 files they sent me. Seemed a bit dicey at first glance, but while I'm by no means an expert, I'm no slouch in this arena and I'm a very quick study.
Now, on to the proverbial meat and potatoes:
If you were able to contact me for a link to the tutorial in question, you will have undoubtedly seen that they indicate one should use ADB-Fastboot as a means to flash the recovery image. No real surprises there. I have ADB and Fastboot installed on my PC (Windows 10). I also have the ADB drivers installed and have confirmed the addition to my PATH. (eg: ;C:\ADB) I can also confirm that it is working fine since I am able to pull up a terminal and issue the ADB command and it gives me the usual wall of commands. The problem is that my device (Ultratablet) is not being seen by ADB. I have checked my USB drivers and they are all up to date and installed properly. My PC sees the device no problem and there is no indication of any sort of connection error. I've also tried different cables and ports. Yet, I can't access it via ADB and thus am unable to issue commands to my device such as "adb reboot bootloader" or "fastboot reboot-bootloader".
My next logical approach was to attempt forcing the device into fastboot mode using the hardware button combination, which is not listed specifically for the Ultratablet anywhere, I might add. (Power key + Volume up) It brings me to a boot options menu with the selections "Continue/Fastboot Protocol/Recovery Kernel/Reboot/Poweroff/Forced Recovery". Ateempting to select Fastboot Protocol causes the display to shut off for a moment, the device to vibrate once, and then the display to turn back on back at the same menu full of selections.
So, in summary, I am expected to flash the device using fastboot and yet I can't even get the device into fastboot mode, let alone issue commands from my PC terminal. As I highlighted near the beginning, teh Jide support team is incredibly unresponsive and not overly helpful. I have notified them of this same set of issues, but I don't expect to hear back in any expedient fashion and I thought one of the mighty members here on XDA might be able to help me come up with a next step in the meantime. I'd cerainly love to be able to use my shiny new tablet.
In any case, thank you for your time.
Kind regards.
Shaiden
Bump? Anyone? Still swinging in the breeze on this one. No word back from the manufacturer, as expected. =/
I have the same problem
Shaiden said:
Bump? Anyone? Still swinging in the breeze on this one. No word back from the manufacturer, as expected. =/
Click to expand...
Click to collapse
I know it's been 4 years but did you find any solution to this? I'm asking because I have the same problem. I decided to downgrade to Remix OS 1.5 in order to root (I have tried 5 rooting apps with no success) but my device refuses to enter fastboot protocol. The whole idea was since I can't find a way to root the damn thing in its current state maybe I can manage it with its older OS version. All this just to turn it to android root apps "testing ground" device. Oof.
First of all, I know that I am the one who is to be blamed, but may be, I can be a help to others or to development. I want to thank the developers for their achievements and do encourage them to continue, even though Microsoft seems to do the same to Windows Phone which IBM did to OS/2.
What did I do?
I have a Lumia 920 with broken digitizer and brownish display, so that was the best device for some testing. With WPInternals I succeeded in routing an unlocked the boot loader.
Switched to MSM, I started to discover the partitions. Unfortunately, I touched the mouse and dragged and dropped "somewhat" in, I think, in the EFIESP partition.
Please don't ask me, why I did not continue with undoing or at least reflash the partitions extracted from an original ffu image.
Well, I rebooted the device and I lost. Damage is about 10 Euro, which I payed for the phone, nothing to be complained about.
With WDRT, I have the well known "device not supported" comments, the same with thor2, WPInternals and Chimera.
If someone has a suggestion, how to force the device to mass storage mode or the cog wheel/flash mode (vol+ and power does not work), you are welcome.
Log files can be provided, if you are interested.
Best regards,
Joachim
At least I solved it by swapping the good display to a device with broken display. I will reassemble the broken device with the broken display (which is still working) and give it away as spare parts.