Related
I've got a new A500 and I intend to root it soon, but I would like advice on whether to take the current update 7.014.1 being pushed before I go through the rooting process? It currently shows having 3.2 OS version.
Zoandroid said:
I've got a new A500 and I intend to root it soon, but I would like advice on whether to take the current update 7.014.1 being pushed before I go through the rooting process? It currently shows having 3.2 OS version.
Click to expand...
Click to collapse
Doesn't matter, the only way to root it is by flashing it which wipes it totally clean
timmyDean said:
Doesn't matter, the only way to root it is by flashing it which wipes it totally clean
Click to expand...
Click to collapse
My concern, being still in the middle of researching just how to root the A500, was whether the update would have a similar effect as, for example, the more major update from 3.0 to 3.2, which, as I understand it totally changes the procedure used to achieve root. But if it won't matter one way or the other, I might as well take the update in the interim. I keep hoping to see a more simple 'one-click' style of root made available before I tackle this task. So far I've found something like 3 different ways to root the tablet between this forum and another. But each is a rather involved process.
Thanks!
timmyDean said:
Doesn't matter, the only way to root it is by flashing it which wipes it totally clean
Click to expand...
Click to collapse
I downgraded, rooted, and then flashed the stock ROM without wiping. If going to any other rom, you might need to wipe.
There currently is no way to root a stock 3.2 or later tablet with a simple one click. In the past GingerBreak gave us that ability but since has been plugged. The other thing causing issues is ACER locked the boot loader making it difficult to flash in a new boot image to get to root.
=== 411 on rooting ===
So, if you have a tablet and want to root it then you have to start looking at security holes. This is what the GingerBreak exploit did along with others. But, ACER plugged those holes and as of today, nobody has found anymore.
So, you might look at exploiting an update.zip. These are OTA's that run but they are signed by ACER. So you can take it apart (unzip) and modify it, but you cannot resign it with an ACER Key. Therefore, you have to sign it with your key. Since it is NOT signed by ACER, the ACER recovery will not install it. So, you have to replace the ACER recovery with CWM which will install any update.zip regardless of who signed it. You just need to change the built in recovery by flashing in CWM recovery.
Lastly, you can just change the boot image and add root. This is easy and straight forward to do. This is just like making your own custom update.zip. Once you have your custom boot, you can then just use Nvflash to flash in your custom boot.
Now, fast forward. ACER (can someone please explain to me why?) decided to lock the bootloader thereby not allowing you to replace the recovery, boot, or any other area. Meaning, you cannot use Nvflash anymore without a key.
With the bootloader locked, you can only load new images if you know the key used to lock it. Of course, they use a public and private key combination, and they appear to use the serial number of the USB device as part of the public key making the keys on my tablet unique compared to yours.
With all this said, this ends all the easy simple rooting methods because first, they've plugged all the security holes (which they should do). Secondly, they locked the boot loader making it very difficult for people to just flash in a rooted boot image.
Armed with this, how do you root a 3.2? One way to do it is to get to a version prior to 3.2 loaded that has a security hole or does not have the bootloader locked. You now exploit it and get root. Now, with root access you make a 'backdoor' that only you know about which allows you to get into your tablet as root. With this done, now roll your tablet forward apply all updates. Since you have a 'backdoor' you can always gain root access.
Unfortunately, this gets to be messy or can be more difficult to do than just clicking on a GingerBreak application. However, if you follow the steps posted here in the forum, it's straight forward and easy enough to do. If not, you are going to have to wait for someone to find a hole and build a oneclick application. I wouldn't hold my breath on this, it probably will never happen because everyone is working on ICS.
Lastly, everyone should write to ACER, refuse to buy ACER (or any tablet) that doesn't allow you (AS THE OWNER) to change it. How would you like to buy a Ford to just have Ford lock the lug nuts on the rims so you could NOT put on your custom wheels.
I believe failure to allow owners to unlock these devices will be the downfall to Android. Windows 8 does NOT have such restrictions and businesses are not going to use devices that are locked and cannot be customized for business. Because developers write software they can sell, they'll move to Windows 8 and drop supporting Android and all these goofy flavors and restrictions. Android might be great and everyone hates Microsoft, but software vendors are going to NOT want to support all these devices.
my 2¢
timmyDean said:
There currently is no way to root a stock 3.2 or later tablet with a simple one click. In the past GingerBreak gave us that ability but since has been plugged. The other thing causing issues is ACER locked the boot loader making it difficult to flash in a new boot image to get to root.
=== 411 on rooting ===
So, if you have a tablet and want to root it then you have to start looking at security holes. This is what the GingerBreak exploit did along with others. But, ACER plugged those holes and as of today, nobody has found anymore.
So, you might look at exploiting an update.zip. These are OTA's that run but they are signed by ACER. So you can take it apart (unzip) and modify it, but you cannot resign it with an ACER Key. Therefore, you have to sign it with your key. Since it is NOT signed by ACER, the ACER recovery will not install it. So, you have to replace the ACER recovery with CWM which will install any update.zip regardless of who signed it. You just need to change the built in recovery by flashing in CWM recovery.
Lastly, you can just change the boot image and add root. This is easy and straight forward to do. This is just like making your own custom update.zip. Once you have your custom boot, you can then just use Nvflash to flash in your custom boot.
Now, fast forward. ACER (can someone please explain to me why?) decided to lock the bootloader thereby not allowing you to replace the recovery, boot, or any other area. Meaning, you cannot use Nvflash anymore without a key.
With the bootloader locked, you can only load new images if you know the key used to lock it. Of course, they use a public and private key combination, and they appear to use the serial number of the USB device as part of the public key making the keys on my tablet unique compared to yours.
With all this said, this ends all the easy simple rooting methods because first, they've plugged all the security holes (which they should do). Secondly, they locked the boot loader making it very difficult for people to just flash in a rooted boot image.
Armed with this, how do you root a 3.2? One way to do it is to get to a version prior to 3.2 loaded that has a security hole or does not have the bootloader locked. You now exploit it and get root. Now, with root access you make a 'backdoor' that only you know about which allows you to get into your tablet as root. With this done, now roll your tablet forward apply all updates. Since you have a 'backdoor' you can always gain root access.
Unfortunately, this gets to be messy or can be more difficult to do than just clicking on a GingerBreak application. However, if you follow the steps posted here in the forum, it's straight forward and easy enough to do. If not, you are going to have to wait for someone to find a hole and build a oneclick application. I wouldn't hold my breath on this, it probably will never happen because everyone is working on ICS.
Lastly, everyone should write to ACER, refuse to buy ACER (or any tablet) that doesn't allow you (AS THE OWNER) to change it. How would you like to buy a Ford to just have Ford lock the lug nuts on the rims so you could NOT put on your custom wheels.
I believe failure to allow owners to unlock these devices will be the downfall to Android. Windows 8 does NOT have such restrictions and businesses are not going to use devices that are locked and cannot be customized for business. Because developers write software they can sell, they'll move to Windows 8 and drop supporting Android and all these goofy flavors and restrictions. Android might be great and everyone hates Microsoft, but software vendors are going to NOT want to support all these devices.
my 2¢
Click to expand...
Click to collapse
Hi, and thank you VERY much for posting such a nice explanation, especially in addition to all the work you have done posting your thread rooting 3.2. I understand, and completely agree with your explanation, as well as your position on taking control of what we bought and paid for. I take even stronger offense with this tablet's bootloader being locked than I do on my phones. This is not a discounted phone with a service plan tied to a cell provider. It has WiFi, but " I " am the only one providing its data (it never leaves my home). There is no justification here that I am 'leasing' a provider's technology . It was a gift, so I can't speak to choosing the vendor. But I like your wheel lug analogy.
I've been reading the threads on rooting, and both my Android phones are rooted and ROMed, so I've been around the block a couple times from the rooting aspect. But thus far I have been rather confused as to which route to take with the tablet. I don't want to be limited to using terminal for su access, so I want to 'fully root' the tablet. My goal is to allow apps like Titanium Backup, Root Explorer, and others I use on the phones, as well as having Clockworkmod Recovery, or similar recovery capable of working with nandroid backups. But for now I don't have plans to use a custom ROM. So having rooted stock 3.2 would suffice.
Although I do fully understand the need to research these kinds of things before jumping in, I also know that often times information evolves, and lengthy threads which were once considered current info end up not getting updated during that evolution. This can lead to wasted time reading information which can no longer actually be used . So in the spirit of pursuing the most current info, could you recommend which thread I can use to get the best results while rooting this 3.2.1 OS Tablet with the above goals in mind?
Used Timmydean's method, it is pretty easy as long as you follow his instructions with in the zip file he has made with all the tools you need inside of hat zip file. You root, install super user and busybox then download Acer recover installer and that will install cwm...
http://forum.xda-developers.com/showpost.php?p=20654298&postcount=129
Good luck and thanks again timmydean for this method.
Sent from my A500 using xda premium
Thanks, that sounds like the way to go. I'll head over to the link you provided.
I've got a couple of questions about the zip file at that post. I want to download that to my PC, and will be using ADB from there, right? I have the choice of doing so from either Windows XP SP3, or Windows 7 Home Premium. I read in older threads that many of the problems people had were only when they used XP, but were avoided by using Windows 7 (which was exactly opposite of what people experienced rooting the LG Ally), so it seems that in this case it is desirable to use Win7?
I presume I'll need to install a driver so the PC can 'see' the tablet. Is one provided in the tools, or do I need to download that somewhere?
I used windows 7. Yes the driver is in the zip file. I unzipped the file to a folder on my desktop and went from there.
In the zip there is a folder called usbpcdriver. Run the set up from within the fooder to get your driver... please read the instructions that say read me..
Sent from my A500 using xda premium
Thanks. I intend to read everything I can get my hands on before I actually start this. I definitely don't want any trouble or, heaven forbid, to brick the tablet.
pretty easy i think... good luck and let us know when you get rooted
I'm not finding any actual instructions on the steps to take for this procedure. The readme file in version 3 zip file only talks about "changes" from whatever the original procedure was.
Where can I get the actual instructions for the entire procedure?
Edit: I just downloaded version 2 of the zip file. In that one there is an additional PDF called "Steps". It is a little more detailed, and says at step 20 that "you should now have 3.2 with a SU shell installed". Does the DotNetDetector step actually ROOT the device? That seems simple enough, but it still has no mention of things like installing ADB and the PC driver. I located the actual thread from which the single post was derived (the target of the URL above, where it is suggested I use TimmyDean's procedure). I am now looking through that entire thread to try to sort out where the instructions are.
AHA! Post 119 of that main thread says "Also the instructions and everything you need are in earlier posts.".
It appears this procedure needs an instruction manual written to consolidate all the gathered information. Having a link to only the download zip files isn't telling me the whole picture. I'll try gleaning the thread and see if I can put together all the steps needed from start to finish to make this work. Looks like ROOT ain't happening tonight.
http://www.multiupload.com/SLR6XSV841
---------- Post added at 05:14 AM ---------- Previous post was at 05:11 AM ----------
thats the link to read me file.. I about to jail break an Iphone 4... Wish me luck
I edited the above post while you were replying. I'll check out that link, thanks.
Good luck on jailbreaking the DemonSpawn 4.
http://forum.xda-developers.com/showpost.php?p=20680452&postcount=137
he has updated it again. looks like a few steps where taken out to make it more simpler
good luck man. Iphone is jail broken
OK, so it looks like the file you just sent me a link to is the same one as the "Steps.PDF" file that was released in Version 2. It appears to me that what I need to do is blend the changes (detailed in version 3's readme file) into that original Steps file, to make a single contiguous set of instructions, and then start at the top. I notice it does mention installing the PC driver and ADB.
Do I have this right so far?
rdnkchevy said:
http://forum.xda-developers.com/showpost.php?p=20680452&postcount=137
he has updated it again. looks like a few steps where taken out to make it more simpler
good luck man. Iphone is jail broken
Click to expand...
Click to collapse
That was fast! Wanna do my tablet?
The link you sent just now is to the version 3 zip file posted on 12/25, which is what I had initially downloaded. It does appear he streamlined the procedure, but it is that readme file which leaves out the part about installing the PC driver and ADB in the beginning, and also leaves out the part at the end telling you that you should now have 3.2 with a SU shell installed.
Please understand that I want to be "fully" rooted, not just have the ability to gain an SU prompt in terminal. Will this procedure "fully root" the tablet? I'm confused by what he means saying "SU shell installed".
Yes if you use his v3 file you will be.. you will need to down load acer recovery from the market after you are rooted and then flash clockworkmod.. this should all take you about 30 min if that...
rdnkchevy said:
Yes if you use his v3 file you will be.. you will need to down load acer recovery from the market after you are rooted and then flash clockworkmod.. this should all take you about 30 min if that...
Click to expand...
Click to collapse
OK, thanks!! Rooting went well without incident. I just installed Root Explorer and Titanium Backup, and made a backup to SD of my apps and data. Then installed Acer Recovery Installer, and let it install CWM Recovery. But what is considered the "home" button on the tablet?? Is it the reset button? The only buttons on this thing are the Volume rocker and the Power button. ( I got brave and found out it is the POWER button ).
Edit: To clarify, I meant to ask which button serves as the Home button while you are IN the CWM Recovery environment, not while in the Android OS home screen.
The touchscreen on my Fire stopped working today. I already talked to Amazon and am getting a replacement, but I want to revert back to stock before sending it in. I've seen ways to do this with TWRP, but I don't have a touchscreen to use TWRP, or any recovery for that matter, with.
Is there any way to do this?
I do have full ADB and Fastboot access, with FireFireFire working, but do not have a currently working rom installed (I was on CM9, and it won't go past the boot screen).
drk.hd said:
The touchscreen on my Fire stopped working today. I already talked to Amazon and am getting a replacement, but I want to revert back to stock before sending it in. I've seen ways to do this with TWRP, but I don't have a touchscreen to use TWRP, or any recovery for that matter, with.
Is there any way to do this?
I do have full ADB and Fastboot access, with FireFireFire working, but do not have a currently working rom installed (I was on CM9, and it won't go past the boot screen).
Click to expand...
Click to collapse
There is a way to do this with adb... I just do not know the proper commands. Sorry
Does installing a custom rom void the warranty? Seems like it would be BS for Amazon not to honor it when it's apparently a hardware related issue.
sengwall said:
Does installing a custom rom void the warranty? Seems like it would be BS for Amazon not to honor it when it's apparently a hardware related issue.
Click to expand...
Click to collapse
No, I don't think it does, but I'd rather not take the chance.
drk.hd said:
No, I don't think it does, but I'd rather not take the chance.
Click to expand...
Click to collapse
YES! It absolutely does. The second the device was rooted it broke warranty.
Sent from my myTouch_4G_Slide using XDA App
The same thing actually happened to me earlier today. I was just browsing some sites on the ICS rom when it just stopped responding. I couldn't get it to recognize any touches even after a bunch of reboots, so I just figured it to be some bug that hadn't been squashed yet. When I dropped down to recovery and saw the same issue, I knew I had a real problem.
Hoping against hope, I tried both CWMR and TWRP on it and got no results. Like you, I figured it would have to go back to Amazon, so I started searching for a way to get it back to stock... nothing obvious jumped out at me because everything is written with access to recovery in mind... which doesn't help.
So, I started reading about adb and going through the built-in help. As I was familiarizing myself with some basic adb commands and options, I left TWRP open in front of me. I don't know how long I had it that way when I mindlessly tapped on the screen and thought I saw it flicker. Yes! I had pressed the Wipe button and it had taken me to that section. It's been working fine ever since.
I'm not claiming I did anything and I don't have a how-to on how to fix it, but it couldn't hurt to just leave the thing running in recovery for a while and see if the touchscreen comes back to life for you too.
Still, I'd love to see someone with more adb knowledge provide a simple tutorial on how to get it back to stock without access to recovery. I'm sure it would be helpful to someone in the future... maybe even me if the same problem comes up again.
Best of luck to you.
Just ignore my comment
Sent from my Amazon Kindle Fire using Tapatalk
If your on the rooted stock rom you could always wait until Amazon pushing the next OTA
You will have to make a fastboot image and flash that with fastboot. But before you create the image, you will have to create all the appropriate symlinks. Then you run...
Code:
make_ext4fs -l 512m -a system -s /path/to/fastboot_system.img /path/to/system_folder
That will create the fastboot image. Then when FFF gives you fastboot access, you run...
Code:
fastboot flash system fastboot_system.img
You will also need a fastboot image for recovery and the bootloader.
Isn't there any easy way like with my desire, simple ruu.
Or hasn't anyone created these images to flash. I also need to get back to stock everything and send it to amazon, my wifi gets error after some period of time and some times when screen goes off, try'd 3 roms and stock.
There is a way to tell the device to install /sdcard/update.zip via shell commands. I forget what they are tho. Something about the extendedcommands. If I have time tomorrow I'll look it up.
here it is:
http://www.theandroidsoul.com/kindle-fire-stock-rom-installation-guide/
b63 said:
here it is:
http://www.theandroidsoul.com/kindle-fire-stock-rom-installation-guide/
Click to expand...
Click to collapse
Thanks for the link. I'm back on this thread because I think my Kindle Fire touchscreen is now dead for good. However, those instructions do not work as-is because you need to press a button on the screen to tell the Kindle Fire to allow the host to mount it as a USB Mass Storage device. Although those instructions don't get you all the way there, I was able to use the core idea to get my Kindle Fire back to stock. So, many thanks for pointing me in the right direction.
On top of the touchscreen not working, I ended up partially bricking the device trying to find a way to flash it back to stock, so I had also posted in the Unbricking thread. I posted my solution there....
http://forum.xda-developers.com/showpost.php?p=23226260&postcount=701
Odds are, if you have a device that is booting correctly, you will be able to ignore steps 3 and 4 and get it booting back to stock. I do have a couple of other suggestions... Leave your USB cable hooked up to the Kindle Fire as it boots into stock for the first time. This is the only time that it will automatically mount the /sdcard to your computer and you will have a chance to reclaim (and delete) all the files stored there. You can also do something like 'adb pull /sdcard C:\sdcard' before you flash. Also, depending on what ROM and apps you were using before starting the process, you might want to delete your user data and reset the device to factory defaults. You can do this with 'fastboot erase userdata' and the next time you start the device, you'll get a warning that it's about to reset. Hit the power button and you should have a clean, fresh from the factory Kindle fire... albeit with a broken touchscreen. Good luck!
After several failed attempts to follow this guide (no offense to posters; I appreciate your contributions), I found this to be the simplest method.
http://stackoverflow.com/questions/10817721/wipe-data-factory-reset-through-adb
Download stock update, then it's basic procedure in adb:
adb push C:/update.zip /sdcard/update.zip
adb shell
recovery --wipe_data
After reboot, go back into to adb shell and do "recovery--update_package=/sdcard/update.zip"
Factory reset, etc. and you're good to go.
I deleted a folder in /data that had some installed software in it. Once I deleted it, the N7 immediately began spitting FCs at me, Aldiko keystore, the WinnIME app, some .pngs, all FCs.
I rebooted and it hangs on the Google screen. I can get into the bootloader by holding volume down, but the menu usually navigated by volume buttons stays on Start and the power/enter button does nothing. No recovery, obviously.
Most depressing, fastboot and adb do NOT work. The closest analogs to this problem I have found through this search is people who accidentally erased their bootloader. It looks like mine may be corrupted, which could end up being no better.
I am out of town and away from my primary Android computer. The one I have with me is Windows, with an Ubuntu VM that has the SDK and confirmed working ADB and fastboot usually. No dice now, like I said.
When I plug in the tablet through USB, the Windows host attempts to install MTP drivers and fails. I would try and install the Windows SDK and try to get a connection through some of the Windows drivers, but the internet where I am cannot take it.
Any ideas? I am thinking the device is toast, but since I would be the first I have heard of to be able to get into the bootloader and still brick, I thought I would open it up to the community.
Details: I HAD CWM, no more. Stock, rooted only.
is there no nv flash for this device.. this is what you need. to boot into nv flash and flash the boot-loader.. .. I think this is the only way. There is another thread that talks about this.. Not sure if they managed it or not but they were very close i think..
erica_renee said:
is there no nv flash for this device.. this is what you need. to boot into nv flash and flash the boot-loader.. .. I think this is the only way. There is another thread that talks about this.. Not sure if they managed it or not but they were very close i think..
Click to expand...
Click to collapse
Yeah. I used NVflash on the wife's transformer 101. I saw that thread, but i think the resolution was that they finally got close enough to find out they didn't know what they were talking about.
That sounds worse than I intended it. I mean that they simply weren't very experienced NVflash users and so they didn't know what they were missing until they worked at it. Seems a while away, if ever.
I have a second Nexus 7, i am wondering if i can do something with the hardware, maybe. Is all of the storage in one chip? I have the 16 gig, i seem to remember the 8 gig has n actual emmc.
I am going to try and stay away from devices with virtual sdcards from now on. This was just a folder in storage, WTF? I am not even sure how this is possible. Hardlink mayhem, presumably. The device had only ran stock.
mateorod said:
Yeah. I used NVflash on the wife's transformer 101. I saw that thread, but i think the resolution was that they finally got close enough to find out they didn't know what they were talking about.
That sounds worse than I intended it. I mean that they simply weren't very experienced NVflash users and so they didn't know what they were missing until they worked at it. Seems a while away, if ever.
I have a second Nexus 7, i am wondering if i can do something with the hardware, maybe. Is all of the storage in one chip? I have the 16 gig, i seem to remember the 8 gig has n actual emmc.
I am going to try and stay away from devices with virtual sdcards from now on. This was just a folder in storage, WTF? I am not even sure how this is possible. Hardlink mayhem, presumably. The device had only ran stock.
Click to expand...
Click to collapse
yea there is only one storage device inside the nexus.. its all symlinked
If you could get the driver going, send a adb reboot-bootloader command, the bootloader should work then.
Will the next nexus have a longer screen?
Same problem here.
mateorod said:
I deleted a folder in /data that had some installed software in it. Once I deleted it, the N7 immediately began spitting FCs at me, Aldiko keystore, the WinnIME app, some .pngs, all FCs.
I rebooted and it hangs on the Google screen. I can get into the bootloader by holding volume down, but the menu usually navigated by volume buttons stays on Start and the power/enter button does nothing. No recovery, obviously.
Most depressing, fastboot and adb do NOT work. The closest analogs to this problem I have found through this search is people who accidentally erased their bootloader. It looks like mine may be corrupted, which could end up being no better.
I am out of town and away from my primary Android computer. The one I have with me is Windows, with an Ubuntu VM that has the SDK and confirmed working ADB and fastboot usually. No dice now, like I said.
When I plug in the tablet through USB, the Windows host attempts to install MTP drivers and fails. I would try and install the Windows SDK and try to get a connection through some of the Windows drivers, but the internet where I am cannot take it.
Any ideas? I am thinking the device is toast, but since I would be the first I have heard of to be able to get into the bootloader and still brick, I thought I would open it up to the community.
Details: I HAD CWM, no more. Stock, rooted only.
Click to expand...
Click to collapse
Hi, everyone!
I've got the same problem with my Motorola Razr D3 (XT920). After a system update, something bad happen while the system tried to install the last patch realeased by Motorola. I still can access the bootloader but nothing is working.
So I wonder if any of you guys have figured out how to reinstall the bootloader.
Hi,
I broke my Nexus 4 screen so I can't do anything, the touchscreen is completely down. But the display is working.
I have bought a new Nexus 4 and I want to get my photos from the broken device. The problem is that I can't unlock the phone (pattern), so I can't access to these. USB debugging is off and the device isn't rooted.
I hope someone have a solution for me. Does any virtual touchscreen exist ?
Ghuillaume said:
Hi,
I broke my Nexus 4 screen so I can't do anything, the touchscreen is completely down. But the display is working.
I have bought a new Nexus 4 and I want to get my photos from the broken device. The problem is that I can't unlock the phone (pattern), so I can't access to these. USB debugging is off and the device isn't rooted.
I hope someone have a solution for me. Does any virtual touchscreen exist ?
Click to expand...
Click to collapse
Don't know if there is a simpler option, but this might help you:
http://forum.xda-developers.com/showthread.php?t=2433307
Not sure if adb works with usb debugging disabled though...
That has to be the Worst case scenario. Another reason I use Google drive and keep pics synced via cloud
Sent from my Nexus 4 using xda app-developers app
It's really annoying, I just need to unlock my phone but I can't !
I'm not comfortable with the idea having my pics on Google's servers, but I will find something to backup data now..
Maybe the only way is to wait the nexus to be obsolete and find a screen for a low price
Oh wait !
USB debugging is ON ! I didn't see the bean icon because there are a lot of notifications.
But I can't use adb :
$ adb shell
error: device unauthorized. Please check the confirmation dialog on your device.
Click to expand...
Click to collapse
Ghuillaume said:
Oh wait !
USB debugging is ON ! I didn't see the bean icon because there are a lot of notifications.
But I can't use adb :
Click to expand...
Click to collapse
I'm assuming that because your phone isn't rooted you don't have a custom recovery or an unlocked bootloader. Is this correct?
i know with my HTC desire i run adb, when the device is turned off and connected to PC .
i think you can try it with your N4 , there are tools to do it google it .
good luck
You can try some combination of Airdroid (older version) and adb/shell command. So you'll need your device connected and older version of Airdroid - not two, because it asks for user action to accept the connection, and the older one just gives random generated password for the user to input in their browsers.
Now, you'll need to push the apk on your phone, and then just start it from your adb shell with the following command:
am start -a android.intent.action.MAIN -n com.sand.airdroid/.Splash - this should work on the old version
am start -a android.intent.action.MAIN -n com.sand.airdroid/.SplashActivity_ this works on last airdroid
At least you can try with other app that doesn't need user interaction on their display to get into the phone memory from their browsers. You can just install them from play store.
The first time that I'm writing here in Nexus forum though I am here with my 2 old DHD for about 2 years and I hope my answer could be helpful. And now I am here because of my soon to come Nexus 4
You could try to unlock, flash CWM then "adb pull" the files from there. No need for the digitizer to get it done. Fully charge the battery before starting.
You don't need root access, just adb debugging.
For everything off your phone: adb pull /sdcard/
Done.
EDIT: If you just want your pics from your camera the command would be adb pull /sdcard/DCIM/Camera/
lopezk38 said:
I'm assuming that because your phone isn't rooted you don't have a custom recovery or an unlocked bootloader. Is this correct?
Click to expand...
Click to collapse
You don't need root to use adb.
You only need to for adb to access anything beyond the sdcard.
When you first use adb there is a pop up on the device that asks if you want to allow the pc access.
He can't use the touchscreen to confirm its ok. This is the reason after I flash a Rom hook up to my pc ASAP and have it remember my computer to allow me access if this were to happen to me.
illru said:
You could try to unlock, flash CWM then "adb pull" the files from there. No need for the digitizer to get it done. Fully charge the battery before starting.
Click to expand...
Click to collapse
HUGE reason why this won't work:
unlocking the bootloader wipes the entire device.
Which... is pointless if you're trying to recover data.
studacris said:
HUGE reason why this won't work:
unlocking the bootloader wipes the entire device.
Which... is pointless if you're trying to recover data.
Click to expand...
Click to collapse
If you flash the custom recovery immediately after unlocking (without rebooting into android in between) your data should not get wiped.
Well then... I sit here humbly corrected.
studacris said:
Well then... I sit here humbly corrected.
Click to expand...
Click to collapse
Dont worry, its not really an officially documented thing...more of just a bug with the bootloader.
Also if flashing your phone makes you nervous you could try to pull from in stock recovery but I don't know if it will work. Never played with stock recovery, it dose not last on my phone for very long.
illru said:
Also if flashing your phone makes you nervous you could try to pull from in stock recovery but I don't know if it will work. Never played with stock recovery, it dose not last on my phone for very long.
Click to expand...
Click to collapse
I dont think adb works in stock recovery. Only custom ones afaik.
hi all and thanks for your help in advance...
i have been assigned an a500 which is bricked and only shows the acer logo and nothing goes on from there
i have tried multiple roms along with custom roms as an update.zip into an SD card but it stops at the same position which is about 30% everytime on every rom
ive tried fastboot, says the BL is locked and when i tell it to unlock it it just says OKAY and stays locked
now blackthund3r with his apx flashing tool presented some hope as it detected the apx mode but after the flashing starts it wont go into bootloader mode the screen is just black
i have attached a screenshot of my pc trying to identify the tablet with apx not installed for no driver is found
i have installed every driver i can put my hands on starting with the latest from Acer drivers and none of them seems to give me the apx driver.
i think the only problem i have is the apx driver, can anyone point me in the right direction? ive got my SBK from afterota only one time and it never worked after that time. can anyone help with the drivers?
#edit:
i forgot to mention that even though it says apx is not installed, when i connect it in apx mode i have a little usb icon which says "eject APX" call me crazy but that just says apx IS installed right?
ssvNormandy said:
hi all and thanks for your help in advance...
i have been assigned an a500 which is bricked and only shows the acer logo and nothing goes on from there
i have tried multiple roms along with custom roms as an update.zip into an SD card but it stops at the same position which is about 30% everytime on every rom
ive tried fastboot, says the BL is locked and when i tell it to unlock it it just says OKAY and stays locked
now blackthund3r with his apx flashing tool presented some hope as it detected the apx mode but after the flashing starts it wont go into bootloader mode the screen is just black
i have attached a screenshot of my pc trying to identify the tablet with apx not installed for no driver is found
i have installed every driver i can put my hands on starting with the latest from Acer drivers and none of them seems to give me the apx driver.
i think the only problem i have is the apx driver, can anyone point me in the right direction? ive got my SBK from afterota only one time and it never worked after that time. can anyone help with the drivers?
#edit:
i forgot to mention that even though it says apx is not installed, when i connect it in apx mode i have a little usb icon which says "eject APX" call me crazy but that just says apx IS installed right?
Click to expand...
Click to collapse
Generally, the APX (boot recovery download) driver should be installed with just the normal Acer drivers from the web site. On a Win8 pc, it can be a real pain, so if you have a Win7 pc, I would advise it. I suppose you are looking in Windows "Device Manager"?
Not sure about the "eject APX" message. Sounds strange to me, but maybe it says that on an XP PC, been to long to remember.
Stock Acer bootloader has no "Fastboot" capability. This was added after ICS with a patched bootloader.
Either way, you will need your CPUID number to use any of the NVFlash tools. There are stickies on how to get this, but more than likely you will need a Linux set-up, not sure if there's a windows method.
If the tab had been rooted, and a custom recovery added, there's a possibility there was a backup done, and it would be in the Clockwork Mod folder on externalSD card.
9918
Moscow Desire said:
Generally, the APX (boot recovery download) driver should be installed with just the normal Acer drivers from the web site. On a Win8 pc, it can be a real pain, so if you have a Win7 pc, I would advise it. I suppose you are looking in Windows "Device Manager"?
Not sure about the "eject APX" message. Sounds strange to me, but maybe it says that on an XP PC, been to long to remember.
Stock Acer bootloader has no "Fastboot" capability. This was added after ICS with a patched bootloader.
Either way, you will need your CPUID number to use any of the NVFlash tools. There are stickies on how to get this, but more than likely you will need a Linux set-up, not sure if there's a windows method.
If the tab had been rooted, and a custom recovery added, there's a possibility there was a backup done, and it would be in the Clockwork Mod folder on externalSD card.
Click to expand...
Click to collapse
I am running win7 x64 and the apx drivers seem to be installed as blackthund3r recognizes it, its just that in blackthund3r apx tool it never seems to want to get into the bootloader mode i have no idea why.
also regarding my CPUID when i used afterota it showed me :
Tablet Serial : 485FEFA483118011
Tablet Cpuid : EMULATOR-5554
Tablet Sbk : 0xF5030000 0x00000000 0xF0D1E302 0xF0D1E302
Android Build : GT-N7000-user
Bootloader : 0.03.01-HC
now isnt the CPUID a 15-16 digit hex number?
and if my CPUID is wrong in this case above it should mean my SBK is wrong aswell right?
the build number is of a galaxy Note device which is also strange.
also, the device came with no SD card and it has not been rooted or a custom recovery installed on it, the owner says "it just died"
I had the Linux idea in mind as a last resort i suppose its time.
thank you for your help
ssvNormandy said:
I am running win7 x64 and the apx drivers seem to be installed as blackthund3r recognizes it, its just that in blackthund3r apx tool it never seems to want to get into the bootloader mode i have no idea why.
also regarding my CPUID when i used afterota it showed me :
Tablet Serial : 485FEFA483118011
Tablet Cpuid : EMULATOR-5554
Tablet Sbk : 0xF5030000 0x00000000 0xF0D1E302 0xF0D1E302
Android Build : GT-N7000-user
Bootloader : 0.03.01-HC
now isnt the CPUID a 15-16 digit hex number?
and if my CPUID is wrong in this case above it should mean my SBK is wrong aswell right?
the build number is of a galaxy Note device which is also strange.
also, the device came with no SD card and it has not been rooted or a custom recovery installed on it, the owner says "it just died"
I had the Linux idea in mind as a last resort i suppose its time.
thank you for your help
Click to expand...
Click to collapse
Oh man, Somebody must have tried installing a Galaxy Note Rom? Got me a little confused on just exactly what you have there mate.
The CPUID as you stated, should be an alpha numeric sequence such as for example (mine)038061c7409fa617.
Why it's telling you it's Emulator-5554 is quite strange. Tell me, how exactly did you get this CPUID? As if the tablet won't boot past the bootloader (Acer screen), then the usual discovery tools we have, can't get it, and this I can promise. I'm guessing it's just spitting out some programming error.
And, I can also say your SBK number is suspect also. Looks weird. Here is mine (no, won't work on yours) 0x79531F00 0xBB680C01 0xFB22E803 0x8ADE2003
I would suggest the following;
There's a user here, dibb_nz, and he has some links on unbricking. Currently he is abroad, so won't answer PM. Also, there is a thread "Why CPUID is Important (might be the same things). In there, are some steps on how to get the number from a dead tablet. No, I've never personally had to do this, but other folks have. I know there's steps from Linux, but believe there may also be windows steps as well.
Another good link from Linux (you can run I dual boot, as I do) http://forum.xda-developers.com/showthread.php?t=1751978 This should be easy to follow, and probably best chance at getting it.
Another good thread from Dibb_nz http://forum.xda-developers.com/showthread.php?t=2049778 Has several unbrick procedures.
I have several factory Roms here on my server. I try getting one whenever I come across them. Acer in all of their infinate wisdom, have shut down their OTA servers for quite some time, and also, they add and delete factory Roms from their official support site all the time.
If I can help you, I will. Some things may be out of my control, but will help as much as possible. We have some pretty good folks here in the 500 forums, but the tablet is getting a bit old, and most have moved on to somehing newer.
MD
Moscow Desire said:
Oh man, Somebody must have tried installing a Galaxy Note Rom? Got me a little confused on just exactly what you have there mate.
The CPUID as you stated, should be an alpha numeric sequence such as for example (mine)038061c7409fa617.
Why it's telling you it's Emulator-5554 is quite strange. Tell me, how exactly did you get this CPUID? As if the tablet won't boot past the bootloader (Acer screen), then the usual discovery tools we have, can't get it, and this I can promise. I'm guessing it's just spitting out some programming error.
And, I can also say your SBK number is suspect also. Looks weird. Here is mine (no, won't work on yours) 0x79531F00 0xBB680C01 0xFB22E803 0x8ADE2003
I would suggest the following;
There's a user here, dibb_nz, and he has some links on unbricking. Currently he is abroad, so won't answer PM. Also, there is a thread "Why CPUID is Important (might be the same things). In there, are some steps on how to get the number from a dead tablet. No, I've never personally had to do this, but other folks have. I know there's steps from Linux, but believe there may also be windows steps as well.
Another good link from Linux (you can run I dual boot, as I do) http://forum.xda-developers.com/showthread.php?t=1751978 This should be easy to follow, and probably best chance at getting it.
Another good thread from Dibb_nz http://forum.xda-developers.com/showthread.php?t=2049778 Has several unbrick procedures.
I have several factory Roms here on my server. I try getting one whenever I come across them. Acer in all of their infinate wisdom, have shut down their OTA servers for quite some time, and also, they add and delete factory Roms from their official support site all the time.
If I can help you, I will. Some things may be out of my control, but will help as much as possible. We have some pretty good folks here in the 500 forums, but the tablet is getting a bit old, and most have moved on to somehing newer.
MD
Click to expand...
Click to collapse
I got my CPUID from afterota "no idea how but it just worked for one time, and later yesterday worked again".
when i try "adb devices" it just shows nothing, while yesterday also i tried the same command and it returned with EMULATOR-5554 as a device connected and i could get in the shell but could do nothing from there...
i have seen those posts before they have been helpful but as far as using "a500 manager tool" to recover my CPUID, the tool hasent worked.
anyways i suspect the only way of getting my CPUID is through a linux distribution,and from there i can stumble around with nvflash from there or go back to windows. As I dont have any linux expertise it would be a good experience.
ssvNormandy said:
I got my CPUID from afterota "no idea how but it just worked for one time, and later yesterday worked again".
when i try "adb devices" it just shows nothing, while yesterday also i tried the same command and it returned with EMULATOR-5554 as a device connected and i could get in the shell but could do nothing from there...
i have seen those posts before they have been helpful but as far as using "a500 manager tool" to recover my CPUID, the tool hasent worked.
anyways i suspect the only way of getting my CPUID is through a linux distribution,and from there i can stumble around with nvflash from there or go back to windows. As I dont have any linux expertise it would be a good experience.
Click to expand...
Click to collapse
Use Ubuntu for the linux distro. It's by far the most common. Basically you can install it 2 ways.
1) As a dual boot (might have to disable a BIOS setting if your PC is pretty new. Usually only if it was a Win8 new system) Benefit is that the Linux OS will get 100% system resources. Downside is that it'll partition your HDD.
2) Run it under cygwin. Basically an emulator which runs within windows, and you create a virtual drive for the Linux install. The benefit is that you can uninstall it rather easily when finished. Downside is it shares Windows resources.
If you're only after the UID, then probably the cygwin method is better for you.
MD
Moscow Desire said:
Use Ubuntu for the linux distro. It's by far the most common. Basically you can install it 2 ways.
1) As a dual boot (might have to disable a BIOS setting if your PC is pretty new. Usually only if it was a Win8 new system) Benefit is that the Linux OS will get 100% system resources. Downside is that it'll partition your HDD.
2) Run it under cygwin. Basically an emulator which runs within windows, and you create a virtual drive for the Linux install. The benefit is that you can uninstall it rather easily when finished. Downside is it shares Windows resources.
If you're only after the UID, then probably the cygwin method is better for you.
MD
Click to expand...
Click to collapse
i've never heard of cygwin, i was thinking virtual machine but i was slacking due to the work it needs doing and my impatience... i must ask if afterota is showing EMULATOR-5554 and i managed to get it in adb mode and it still showed EMULATOR-5554 do you think its even recoverable in ubuntu?
ssvNormandy said:
i've never heard of cygwin, i was thinking virtual machine but i was slacking due to the work it needs doing and my impatience... i must ask if afterota is showing EMULATOR-5554 and i managed to get it in adb mode and it still showed EMULATOR-5554 do you think its even recoverable in ubuntu?
Click to expand...
Click to collapse
Well, being in the 500 forums, and owning a 501, I can say these tablets are pretty much bulletproof. I've never known one that can't be unbricked. Basically, if it has some life, it can be brought back. Mine blew away the bootloader, hard bricked. Took out the mainboard, slapped it in the oven, reseated some nand chips, and it updated the blob file when I booted it. :good: imagine that!
It's still a little flakey running EUUS files, but it's on 3.2.1 and rooted, so I will leave it on that rather than press the issue any further. Besides, it's only used for You Tube and Browser anyhow.
I would say the Linux method will probably reveal the true CPUID. Afterota seems like it's generating some development code. Like I said, none of those tools will work properly unless the tablet OS is running, so who knows what strange things will happen.
I've never used VM, but it should also boot ubuntu.
This chap just got his CPUID today using a Linux distro.
http://forum.xda-developers.com/iconia-a500/help/a500-brick-firmware-install-t2865167
Moscow Desire said:
Well, being in the 500 forums, and owning a 501, I can say these tablets are pretty much bulletproof. I've never known one that can't be unbricked. Basically, if it has some life, it can be brought back. Mine blew away the bootloader, hard bricked. Took out the mainboard, slapped it in the oven, reseated some nand chips, and it updated the blob file when I booted it. :good: imagine that!
It's still a little flakey running EUUS files, but it's on 3.2.1 and rooted, so I will leave it on that rather than press the issue any further. Besides, it's only used for You Tube and Browser anyhow.
I would say the Linux method will probably reveal the true CPUID. Afterota seems like it's generating some development code. Like I said, none of those tools will work properly unless the tablet OS is running, so who knows what strange things will happen.
I've never used VM, but it should also boot ubuntu.
This chap just got his CPUID today using a Linux distro.
http://forum.xda-developers.com/iconia-a500/help/a500-brick-firmware-install-t2865167
Click to expand...
Click to collapse
the oven? im confused what reflowing the solder has to do with anything lol and i hope im not going to that stage haha
im downloading ubuntu now as we speak, im hoping it will work but im confused about the libraries that i need to download, GCC and the other ones, are they something special and special installation required? or sniffing around google would do the trick?
ssvNormandy said:
the oven? im confused what reflowing the solder has to do with anything lol and i hope im not going to that stage haha
im downloading ubuntu now as we speak, im hoping it will work but im confused about the libraries that i need to download, GCC and the other ones, are they something special and special installation required? or sniffing around google would do the trick?
Click to expand...
Click to collapse
Well, normally after you get an ubuntu install, you can download extra packages. Terminal for one. I'm sure the Ubuntu help center tells you how to get certain packages (lib's and such). Basically you do it via a terminal window. Like I said, I've never used that particular procedure myself, but seems some others got it figured out.
Ha Ha... the oven. Yes, I was skeptical to say the least, but thinking back on rice to dry out a phone, putting a dead HDD in the freezer, well, it seemed plausible. And for me, the oven trick worked. Pressed all the nands back into place, and was able to clear the "Blob update failed" error (was stuck with no working bootloader, hence a hard brick). I attribute it to my 2.5yrs old girl dropping the tab once too often (although was in a good cover).
Moscow Desire said:
Well, normally after you get an ubuntu install, you can download extra packages. Terminal for one. I'm sure the Ubuntu help center tells you how to get certain packages (lib's and such). Basically you do it via a terminal window. Like I said, I've never used that particular procedure myself, but seems some others got it figured out.
Ha Ha... the oven. Yes, I was skeptical to say the least, but thinking back on rice to dry out a phone, putting a dead HDD in the freezer, well, it seemed plausible. And for me, the oven trick worked. Pressed all the nands back into place, and was able to clear the "Blob update failed" error (was stuck with no working bootloader, hence a hard brick). I attribute it to my 2.5yrs old girl dropping the tab once too often (although was in a good cover).
Click to expand...
Click to collapse
well i have good news and bad news...
i got Ubuntu and i was succeful in retrieving my CPUID and after that my SBK, blackthund3r a500 tool worked and it got into " entering acer download mode" as in it booted in bootloader mode which is very good, but now when i flash something it is stuck at "stage two-uploading image" and the nvflash command screen is stuck at "resume mode".... well great, now what? lol
ssvNormandy said:
well i have good news and bad news...
i got Ubuntu and i was succeful in retrieving my CPUID and after that my SBK, blackthund3r a500 tool worked and it got into " entering acer download mode" as in it booted in bootloader mode which is very good, but now when i flash something it is stuck at "stage two-uploading image" and the nvflash command screen is stuck at "resume mode".... well great, now what? lol
Click to expand...
Click to collapse
Eh, ok, you got the CPUID. Hang on and I'll give you a link for Timmy Deans 3.2.1 rollback.... Sounds like you got a corrupt partition.
OK, download and unzip the contents.
http://www.mediafire.com/download/fo4wqjeald4s3rj/tdv4_rollback_rom.7z
Now, in the contents, you will see the file pbj20upgrage.exe
Run it as "administrator" (right mouse click it and select run as administrator)
Now, don't plug in the tab. After it does a couple things, (installs drivers, starts looking for current build it will eventually prompt you to start your tab in APX mode. Do it. Then connect, enter your CPUID when asked, and it will NVFlash a complete pre-rooted 3.2.1 with CWM Recovery.
Moscow Desire said:
Eh, ok, you got the CPUID. Hang on and I'll give you a link for Timmy Deans 3.2.1 rollback.... Sounds like you got a corrupt partition.
OK, download and unzip the contents.
http://www.mediafire.com/download/fo4wqjeald4s3rj/tdv4_rollback_rom.7z
Now, in the contents, you will see the file pbj20upgrage.exe
Run it as "administrator" (right mouse click it and select run as administrator)
Now, don't plug in the tab. After it does a couple things, (installs drivers, starts looking for current build it will eventually prompt you to start your tab in APX mode. Do it. Then connect, enter your CPUID when asked, and it will NVFlash a complete pre-rooted 3.2.1 with CWM Recovery.
Click to expand...
Click to collapse
well well well, it worked and its perfect now. thank you very much for your help MD pbj20upgrade was the answer, now off to install ICS
thank you again
ssvNormandy said:
well well well, it worked and its perfect now. thank you very much for your help MD pbj20upgrade was the answer, now off to install ICS
thank you again
Click to expand...
Click to collapse
Great!
Now, just remember, when you install one of the full ICS Update files (I have a thread stickied in one of these forums), it will change the bootloader, and also do away with the CWM custom recovery. A custom ICS ROM will not run on an HC 3.2.1 bootloader. This is why we had the Blackthunder tool and patched V8 bootloader. Just so you are aware.
Good luck!
MD
Moscow Desire said:
Great!
Now, just remember, when you install one of the full ICS Update files (I have a thread stickied in one of these forums), it will change the bootloader, and also do away with the CWM custom recovery. A custom ICS ROM will not run on an HC 3.2.1 bootloader. This is why we had the Blackthunder tool and patched V8 bootloader. Just so you are aware.
Good luck!
MD
Click to expand...
Click to collapse
blackthunder's tool just WILL NOT RUN on the tab its always stuck on nvflash resume mode, and uploading image, even after i got the tab back to life i have no idea why, and everytime i try to flash the v8 or even v9 BL it just freezes and i get the acer splash screen again, and then i have to rollback again.
is there any detailed tut on installing ics with the correct steps ? it would be much appreciated, HC wont run any recent app and its ticking me
ssvNormandy said:
blackthunder's tool just WILL NOT RUN on my tab its always stuck on nvflash resume mode, and uploading image, even after i got the tab back to life i have no idea why, and everytime i try to flash the v8 or even v9 BL it just freezes and i get the acer splash screen again, and then i have to rollback again.
is there any detailed tut on installing ics with the correct steps ? it would be much appreciated, HC wont run any recent app and its ticking me
Click to expand...
Click to collapse
Welcome to the world of corrupted nand memory.
You can try running "babsector" and see if it will NVFLASH repaired partitions.
http://forum.xda-developers.com/showthread.php?t=2049778 and go to the second post.
Not saying it will fix it, but it might.
Have you tried running an ICS Update file?
Moscow Desire said:
Welcome to the world of corrupted nand memory.
You can try running "babsector" and see if it will NVFLASH repaired partitions.
http://forum.xda-developers.com/showthread.php?t=2049778 and go to the second post.
Not saying it will fix it, but it might.
Have you tried running an ICS Update file?
Click to expand...
Click to collapse
i have basically tried every ROM available and got nothing in return, running babsector gave me an error about formatting partition failed, although when i booted i had a green screen with v8 bootloader on it but it wont boot not will it install any rom and it says, kernel failed or something i dont remember. I have decided to abandon the project and just give it back to the owner with HC 3.2.1 and get it over with
edit: i added a picture of the error
ssvNormandy said:
i have basically tried every ROM available and got nothing in return, running babsector gave me an error about formatting partition failed, although when i booted i had a green screen with v8 bootloader on it but it wont boot not will it install any rom and it says, kernel failed or something i dont remember. I have decided to abandon the project and just give it back to the owner with HC 3.2.1 and get it over with
edit: i added a picture of the error
Click to expand...
Click to collapse
Yep, same issue with me. I'm stuck on 3.2 HC
Well, it's a secondary tablet anyhow.
Yep well i figured it was unrecoverable and not worth the effort and time put into it, thanks for the rollback method i couldnt have done it without you MD atleast its working now
ssvNormandy said:
Yep well i figured it was unrecoverable and not worth the effort and time put into it, thanks for the rollback method i couldnt have done it without you MD atleast its working now
Click to expand...
Click to collapse
Yeah, and a little bit of knowledge :laugh::laugh::laugh: (maybe too much)
Am glad I could help out!! :good: