Related
I am running Windows 7 x64 I have no idea if following this guide on another operating system will work, this is just a step by step of EXACTLY how I did this, Not to say this is the only way. I have tested other methods and I have put in different variables and I have successfully gotten it to work several times in a row doing it this way while following jp4756's guide. I am sure this is not the only way to accomplish root, however this worked for me perfectly. PLEASE don't skimp out on any step. There is no shortcut here just follow the steps and jp4756's guide to the TEE!!!
Step 1.
Uninstall pdanet/htc sync/ any other thing you installed to get all this to work before
Unplug phone from computer usb cables and have phone powered on and in settings menu
Step 2.
download USBDeview(install it) easy to google it
download HTC SYNC(do NOT install it yet) for mytouch slide easy to google it
Step 3.
While in settings menu go to Application
go to Development
and check the box USB debugging
Step 4.
In settings go to Connect to PC
touch Default connection type and choose Sync
At this point you have the phone not plugged in, you have the setting on the phone changed, you have dowloaded usbdeview and installed it, and have htc sync dowloaded
Step 5.
Start USBDeview(some may have to right click the exe and run as administrator) and delete all android drivers and mytouch drivers, anything relating to android
Install HTC SYNC and let it completely install
Step 6.
Plug phone into computer and let the computer auto install drivers etc...
Step 7.
turn the phone off. Power on the Slide into the bootloader by Holding Down ( Volume Down + Power Button ) After it does its little thing your computer will beep and start auto installing drivers and stuff
Step 8.
If everything has gone according to plan in Device Manager it will show Android 1.0 or w/e with a exclamation point. Right click on that and choose Update Driver Software
2 options pop up choose Browse my Computer
then choose Let me Pick from list...
a list will appear giving lots of choices
choose Android Phone should be the first choice that says android....
then 3 options will appear, choose the 3rd one that has Composite in it and choose okay.
Step 9.
Now select Recovery from the bootloader menu
after it is done doing its thing completely 2 things will happen
1) In device manager you will now have something under disk drives
2) USBDeview a new driver will pop up at the end of the list, something like this:
Port_#0004.Hub_#0004 T-Mobile myTouch 3G Slide USB Device Mass Storage Yes No No No E: HT05RPS05696 6/16/2010 4:00:58 PM 6/16/2010 4:07:35 PM 0bb4 0ff9 08 06 50 USBSTOR USB Mass Storage Driver USBSTOR.SYS USB @usbstor.inf,%generic.mfg%;Compatible USB storage device
Step 10.
This new driver to appear shows Yes under the Connection column. This needs to be disabled. Right click on it and choose Disable Selected Device
after about 10 seconds it should no longer say Yes under connection column, if this does not happen then you are not running it under Admin.
Okay so now you are literally almost freaking there.
Step 11.
Now basically all you have to do is follow jp4756's guide starting with step 5. Im going to assume you already understand steps 1-4 in his guide. And you already have the package listed in his guide as well. You have already put those files where they belong
Step 12.
Okay so we are basically following his guide now. first things first
5. run the update.zip it will fail(MUST DO)
6. now in cmd type adb reboot recovery (don’t press enter)
7. in the recovery hit reboot system now( once it starts rebooting run that command rapidly untill back into recovery) <--- Basically while the phone is rebooting you are just hitting up arrow enter up arrow enter up arrow enter up arrow enter in CMD. You will know when you can stop when the CMD freezes for a sex, computer makes beeping noises and the phone reboots basically. It is headed for recovery and we must switch our command now
8.type adb devices(if it says nothing repeat the steps, if it says offline unplug it and then plug it back in, if it says recovery your fine) <---- Basically after you know its headed for recovery you change command to adb devices and you repeat previous procedure, up arrow enter up arrow enter up arrow enter etc.... I did not use loop, i did this all manually.
This may take a few tries, if it does not show offline then go back to step 6 rinse and repeat. You go back and forth just a few times and you will have it. Literally within about 3 tries you should accomplish the annoying goal of having offline stay there.
My job is done, follow guide and continue on your quest for root
There is no guarantee this will work for everyone. I am not claiming that this is 100% Im just giving an explanation as to how i got it and what might have been causing everyones trouble. Results may vary
Thank you to all the devs who made this possible and jp4756 for his wonderful guide
Wow that is just way to much stuff there...
I've ran loop on 2 totally different Computers running 2 totally different OS's and running 2 totally different Drivers, I have no problems with either one..
1st: XP sp3 32bit w/ PDANet Drivers <--- Only ones that I could get to load, Forcing drivers wouldn't work in XP... also like I said before, make sure to close the PDANet Program in the Toolbar.. Also make sure to read the directions when installing PDANet...
2nd: Windows 7 64bit w/ Htc Drivers <---PDANet Drivers also work... You have to force the HTC Drivers in Devices Manager..
I think most people are having this problem because they aren't doing the USB Debug thing. But could be Wrong.
Also a side note my phone is running the USB Drive and not SYNC works just fine...
Also It just might be your computer so I would try and use a different one if you can.
jnight666 said:
Wow that is just way to much stuff there... I don't see how anyone has a problem with loop.
I've ran loop on 2 totally different Computers running 2 totally different OS's and running 2 totally different Drivers, I have no problems with either one..
Also It just might be your computer so I would try and use a different one if you can.
Click to expand...
Click to collapse
Sorry that we all can't be as cool as you jnight666, but some of us are having real problems with no apparent explanation. I am an IT professional with access to every kind of computer used in the modern world, and trust me, I've tried all the ones that apply. Rubbing it in our faces that it was just so easy for you is just rude.
THE DRIVER MAKES NO DIFFERENCE FOLKS. IF YOU CHANGES DRIVERS AND THEN IT WORKED, IT'S PURELY A COINCIDENCE. PEOPLE HAVE GOTTEN THIS TO WORK ON MANY DIFFERENT DRIVERS.
THE CONNECT TO PC SETTING ON THE PHONE DOES NOT MAKE A DIFFERENCE IN FASTBOOT/RECOVRY FOLKS. IF YOU CHANGED THIS SETTING AND IT WORKED, IT'S PURELY A COINCIDENCE. PEOPLE HAVE GOTTEN THIS TO WORK ON VARIOUS DIFFERENT SETTINGS.
That being said, this didn't solve mine. I still cannot root.
And Yes, my cap locks was on purpose.
Okay, please dont come in here and start telling me how my method is wrong. I already stated there are other ways to accomplish it. I had already stated that this isnt 100%. I am merely offering an exact procedure that i duplicated SEVERAL times, with it working for me every time. If this isnt how you accomplished it then pls, theres no reason for you to be in this thread posting negative comments.
With that said fermunky, did you follow the procedure to the tee? - btw im not assuming anything so please dont take it personal. Im just trying to help ppl : )
My caps wasn't to be negative. There are too many people claiming the drivers were a key. And I am not saying yours said this, but it also doesn't clearly say it doesn't. That is all.
Completely understandable, and definitely no disrespect to you or anyone here
When I disable the Mass Storage I see other items in USBDeview that reference the Slide. I end up in a loop after rebooting and rapidly entering adb reboot recovery. I was seeing everything as your instructions explained.
Do you think it is worth a shot to disable all but one item for the Slide? Any suggestions would be greatly appreciated. I work in an IT Escalation Group and this has to be one of the toughest nuts I have tried to crack! LOL
Thanks,
jnight666 said:
Wow that is just way to much stuff there... I don't see how anyone has a problem with loop.
I've ran loop on 2 totally different Computers running 2 totally different OS's and running 2 totally different Drivers, I have no problems with either one..
1st: XP sp3 32bit w/ PDANet Drivers <--- Only ones that I could get to load, Forcing drivers wouldn't work in XP... also like I said before, make sure to close the PDANet Program in the Toolbar.. Also make sure to read the directions when installing PDANet...
2nd: Windows 7 64bit w/ Htc Drivers <---PDANet Drivers also work... You have to force the HTC Drivers in Devices Manager..
I think most people are having this problem because they aren't doing the USB Debug thing. But could be Wrong.
Also a side note my phone is running the USB Drive and not SYNC works just fine...
And if anyone want to say anything about this I'll go load up my Pentium III machine and see if it works on that...
Also It just might be your computer so I would try and use a different one if you can.
Click to expand...
Click to collapse
3 different computers 3 different op systems installed uninstalled drivers different programs etc...some phones are hard to root its a ambiguous situation
Yeah sorry I wasn't trying to be rude.
I was just trying to be helpful, sorry if it came out that way...
I also have the loop not working issue but i usually only happens once or twice..
I feel your pain I had trouble with the push Update.zip part of this thing and I was trying it for hours...
I was just trying to tell you what worked for me...
If you tried different computer and still no luck then im guessing its the Phone that is the issue or the USB Cable...
gofizzle said:
When I disable the Mass Storage I see other items in USBDeview that reference the Slide. I end up in a loop after rebooting and rapidly entering adb reboot recovery. I was seeing everything as your instructions explained.
Do you think it is worth a shot to disable all but one item for the Slide? Any suggestions would be greatly appreciated. I work in an IT Escalation Group and this has to be one of the toughest nuts I have tried to crack! LOL
Thanks,
Click to expand...
Click to collapse
You definitely don't want to do that, as one of them is one that you need to be connected once you finally get to see offline stay. Are you rebooting using the method described in jp4756's guide? meaning your rebooting using the recovery option reboot, then in command doing the adb reboot recovery, then once you no the phone is gonna boot into recovery you switch to spamming adb devices? When you say your in a loop it sounds to me maybe your not doing the adb devices after the phone listened to your adb reboot recovery command
Followed your instructions...
No ! next to anything in device manager. Right clicked on Android Phone > Android ADB Device and went to properties to update the driver. Nothing in the HTC folder would work, they both said that they weren't applicable for the device...(this was in C:\Program Files (x86)\HTC\HTC Driver\Driver Files\Win7_x64)
before plugging your phone into your computer a single time, can you confirm that you started up USBDeview and uninstalled every single driver related to android, or mytouch or htc etc... Also before ever plugging your phone in a single time did you install htc completely?
Code3VW said:
Followed your instructions...
No ! next to anything in device manager. Right clicked on Android Phone > Android ADB Device and went to properties to update the driver. Nothing in the HTC folder would work, they both said that they weren't applicable for the device...(this was in C:\Program Files (x86)\HTC\HTC Driver\Driver Files\Win7_x64)
Click to expand...
Click to collapse
Right Click Android Phone - Properties - Driver - Update Driver - Browse My Computer - Let me pick from a list of device drivers (click this, don't give it the path in the upper box) - Have Disk - Browse to yours C:\Program Files (x86)\HTC\HTC Driver\Driver Files\Win7_x64 - click androidusb.inf and select Open - OK - Unclick Show compatible hardware - Select "T-Mobile myTouch 3G Slide" - Next - All Done.
after getting some sleep and starting fresh, i tried this method again this morning. on the fourth or fifth try i got my slide to stick in offline mode. so then i unplugged it and plugged it back in to get into recovery. lost it, and now im on my 50th or so try to get it back to offline mode.
i need a stiff drink lol
it seems partially a driver issue and also an adb issue i thinks. it connects 'when it feels like it'
i'll report back if i make any progress.
btw im doing this on XP Pro SP3 fully updated
edit: I also noticed when adb does catch the slide, 2 instances of adb are running, then one closes and loses the phone. maybe this will help solve some of the problems
You've misunderstood that post. Only one instance of ADB will show when the loop is not running. Once you start the loop, another instance of ADB will show up and disappear many times. This is normal. As long as only one instance is showing before loop, you are fine.
fermunky said:
My caps wasn't to be negative. There are too many people claiming the drivers were a key. And I am not saying yours said this, but it also doesn't clearly say it doesn't. That is all.
Click to expand...
Click to collapse
I would just like to say that I have followed every method listed in these forums, achieved root the first try (using the updated update.zip). My problem occured when flashing the eng rom, I lost clockwork,root and now the phone runs like sh!t. Yes, superuser was installed and yes my pc no longer recognizes the phone when searching for adb devices after pushing the first 2 files from the eng flash walkthrough.
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
mtjnkee said:
I would just like to say that I have followed every method listed in these forums, achieved root the first try (using the updated update.zip). My problem occured when flashing the eng rom, I lost clockwork,root and now the phone runs like sh!t. Yes, superuser was installed and yes my pc no longer recognizes the phone when searching for adb devices after pushing the first 2 files from the eng flash walkthrough.
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
Click to expand...
Click to collapse
maybe your downloads were corrupted. that's really strange...
man, that really sucks! I am truely sorry...
after spending 20 hours or so on rooting, I really feel your pain.
After I reboot into recovery mode and then use adb to check for my device I never get it to show up. Just so I am clear when you say 'spamming your device' you mean after reboot and rapidly entering the reboot recovery command, then looking for device with adb devices command. I never get it to show.
Thanks for the reply!
No devices in adb?
So I had this same problem with my MT3G. Type in "adb devices" kills the last device and it lists connected devices and NONE were listed. Not sure exactly what I did, but did eventually get it working. (I was trying to use the emulator)
Now though I'm having the same problem with my wife's MTS. Any ideas?
I bought an Acer a500 tablet a few days ago not knowing how broken it is.
After loads of research and attempting different techniques I still haven't had any progress.
The software issue:
When booting up the tablet, it goes to the black screen with "android system" at the top and power off/ shutting down in the middle of the screen.
Fixes I've tried:
1.
Since I don't know anything about what operating system is on this tablet, I have been blindly flashing different "stock" (from Vache) versions of HC.
--The android logo with gears shows up, the green bar loads but freezes when it gets 1 cm away from finishing.
--After turning off the tablet and booting it up again, "updating bootloader shows up on the upper left hand corner of the screen. Then a message pops up saying "apk installer: all pre processes complete". Then it returns to the black screen.
2.
The tablet will not go into apx mode (using the reset botton at the bottom).---Fixed. I didn't execute the steps properly. Apx mode works fine.
3.
I plugged the tablet into an older windows laptop and the computer could not install the correct drivers to sync with the tablet. Again also my lack of knowledge. I installed drivers from Acer.com
4.
These two guides seem to be exactly what my problem is but I can't seem to make sense of them:
http://forum.xda-developers.com/showthread.php?p=24531880#post24531880
http://forum.xda-developers.com/showthread.php?t=1572622
This is as far as I've gotten.
Other complications:
--The battery is dead. I have to use it while plugged in by the charger.
--Most of the thread that I have looked at use Megaupload as the source of downloading their files.
--The original owner of the tablet will not help me out. As I stated before, I don't know what version android OS was on here before it was bricked and on top of that the original owner won't answer my questions. As far as I know though, this tablet is not rooted or has anything "non-OEM" installed in it. The story goes that this tablet was bricked when the owner tried to "update" it. Before that, it was functioning perfectly.
-----It looks like Darvis is having the same issue and frustrations I'm having but reading his threads makes me think that this tablet is a dead end.
http://forum.xda-developers.com/showthread.php?t=1427983&page=4
http://www.androidtablets.net/forum...32467-please-help-me-unbrick-my-iconia-5.html
If someone could point me in the right direction toward fixing this tablet, I would appreciate it very much.
Thank you for reading my Thread.
KiwiN said:
http://forum.xda-developers.com/showthread.php?t=1572622
Click to expand...
Click to collapse
First off......I hope u didn't pay much for the tablet.
Secondly the guide above looks pretty straight forward but maybe this is one of the ones that has files at megaupload?
I know that the ra recovery and timmydean's files are accessible as I have downloaded both of them.
Maybe someone who has done this previously will chime in and get you the other file if it is indeed unreachable.
Sent from my A500 using xda premium
I would suggest trying to connect the tab to a Windows 7 PC after installing the USB drivers from ACER. Then check if your device appears in the device manager. As long as you have its UID you can flash the tab from the PC with one of the EUU tools - check my signature on "how to revert to 3.0.1" or TimmyDean's thread which offers an EUU with rooted HC 3.2.1 (it's linked in my thread as well).
How exactly did you try to get into APX mode?
p.s. I have the EUU files if you can't access them from the threads links. I can send them to you.
getting into apx mode
When I perform the steps (hold reset + power for 3 secs then release power); the tablet turns on as it usually does. It goes to the Acer screen, then android and back to the black home screen. My computer responds by saying that it is "installing drivers" but it "fails to install drivers". At the same time I have the DND.exe open and it does not recognize my tablet.
I'm trying to follow the instructions from the root 3.2.1 v4 file.
I can't perform the first step where it instructs me to turn on Usb debugging. The problem is that I can't open the settings by clicking the clock. Nothing happens.
I realize that one complication of my tab is that it will not charge. The battery power is below 15% so none of these fixes might not be effective for me. That might be the ultimate problem?
CyaN1de-
I paid $100 for the tablet. As of this moment I feel like I paid too much.
Thank you both for you quick replies. I have to say that most of the problems that I'm having is because of my lack of experience but I'm learning. I hope I fix this tab soon.
if this dont fix it, i'll give you what you paid for it;0
someone posted a while back that a hard reset fixed the android systems screen error
not sure where you're at now but no harm in trying it
Try using hard reset:
1) Turn off your tablet,
2) Rotation lock s to your left;
3) Press Vol+ (which is next to rotation lock) and power on simultaneously
4) As soon as the tablet vibrates you can release the power on button and you
should start to switch rotation lock left and right till you see
Erasing Userdata...
Erasing Cache...
Vol+ is still pressed;
5) The tablet starts to format
6) Your tablet will be as clean as it can be.
Thanks for the suggestion but I didn't accomplish anything by hard resetting it. I've done this many times and nothing has changed.
I haven't given up on unbricking this tablet yet and even though it's frustrating I'm learning from the process. If I decide to sell it, I'll contact you Dibb.
KiwiN said:
.....
When I perform the steps (hold reset + power for 3 secs then release power); the tablet turns on as it usually does. It goes to the Acer screen, then android and back to the black home screen. My computer responds by saying that it is "installing drivers" but it "fails to install drivers". At the same time I have the DND.exe open and it does not recognize my tablet.
Click to expand...
Click to collapse
i've seen the 2 methods u described but i've not seen anyone else have success with it apart from the OP'ers - seems OTT to me but hey if it works for ya...
I've used timmydeans method ALOT on HC it never failed to work and that includes reverting back to HC from ICS - if it doesnt work for your issue then id be tempted to use blackthund3rs APXFlash Tool and civato's HC_ICS_Bootloader zip to flash a new bootloader and rom package on yr tab - but for the moment we'll run with td'sv4 - if drivers fail to install then believe me, its a good sign
try this:
I know you-ve probly done it but u need to do it again:
reboot everything, then reinstall acer drivers (yeh i know)
fire up ya tab but dont connect to yr pc just yet -as you said you
doubt usb debugging in enabled so we'll try another way around it
run the prgb20.exe it will scan for the new image but not find it becos youre disconnected...thats good....
after maybe 5 -7 minutes of scanning for the new image - it will show a
window "cannot detect yr iconia tab"
and instructions for getting into apx mode - go ahead connect usb put the tab into apx BUT don't click next until....
the drivers will try to install, dont let windows search but let me choose
(off memory) choose device and adb or android ph should show up here
the acer boot/recovery drivers should install...maybe even under USB Controllers
once they do and only when they do click next to put tab into:
acer download mode.......
as i said this is worth a go,,,,how about the update.zip have u tried that.....
else the only other way i know is apx flash....ya still need to get into apx
mode and if u cant then ???? sometimes youll try something over and over
and then out of the blue it will work...you'll swear you never did anything different , it jsut worked this time.....
hope you find some joy
Thanks Dibb for your words of wisdom. I've put it aside for now but I'm going to pick it up in the morning.
As addition to what dibb_nz said - Windows 7 would do the trick - I'm almost 100% sure you'll be able to connect in APX mode with the drivers properly installed. Then use one of the EUUs.
Drained battery really looks like the ultimate problem now because as far as I know you cannot charge the tab in APX mode - haven't tried that. Eventually I would suggest to crack the tab open, remove the battery and charge it somewhere - I don't know alternative ways but...may be another tab or you own charger with proper connector ...
http://www.youtube.com/watch?v=xvXihNIdQ1M
p.s. 15% power ... seems enough to flash through the PC...but who knows - don't waste them and get everything you need before starting the procedure.
no probs m8 hope u have better luck tomorrow
if u wanted to try the EC method i have those files if you want them
good luck m8
dibb_nz said:
if drivers fail to install then believe me, its a good sign
try this:
I know you-ve probly done it but u need to do it again:
reboot everything, then reinstall acer drivers (yeh i know)
fire up ya tab but dont connect to yr pc just yet -as you said you
doubt usb debugging in enabled so we'll try another way around it
run the prgb20.exe it will scan for the new image but not find it becos youre disconnected...thats good....
after maybe 5 -7 minutes of scanning for the new image - it will show a
window "cannot detect yr iconia tab"
and instructions for getting into apx mode - go ahead connect usb put the tab into apx BUT don't click next until....
the drivers will try to install, dont let windows search but let me choose
(off memory) choose device and adb or android ph should show up here
the acer boot/recovery drivers should install...maybe even under USB Controllers
once they do and only when they do click next to put tab into:
acer download mode.......
hope you find some joy
Click to expand...
Click to collapse
So I went through all these steps and the TD's V4 tool finishes updating the tab. But then it continues to the same black, android systems screen. And afterwards the tablet won't connect with the computer.
I am currently downloading the update.zip so i'm going to see if that will work.
KiwiN said:
So I went through all these steps and the TD's V4 tool finishes updating the tab. But then it continues to the same black, android systems screen. And afterwards the tablet won't connect with the computer.
I am currently downloading the update.zip so i'm going to see if that will work.
Click to expand...
Click to collapse
do u get on yr tab the big 'PASS' in white leetters or "entering download mode" at all???
think we're beyond update.zip if EUU failed but you can try it -
you can get to apx which is a start - getting a new boot/recovery image on there is the main priority I think...as i posted earlier i've only ever seen a fix for this problem work for 2 people, so on new ground here....
But anyway check out the APXFlash method/walkthru in my sig....all the info is in there and the links to the required files ....do we know if you're on HC or ICS B/L????
I got the word pass; now using recovery mode to flash a rom.
not sure which bootloader I have.
I am using:
Acer_A500_7.006.01_COM_GEN2: http://vacheandroid.com/files/Acer_...1_COM_GEN2.zip
But after it says install from sdcard complete it also give me the message:
E: Can't mount/ dev/block/mm....
E: Can't mount Cache: recovery/log
E: can't mount open cache: recovery/log
E: Can't mount /dev/block/mm...
found this:
dibb_nz said:
yes if you're talking about the stock roms from vaches thread, you need the full rom package - you cant just use an 'update' package as they need a full rom to work properly....
for instance my original HC3.2.1 Stock build is 7.014.15_COM_GEN1
and theres no FULL Rom for 3.2.1, so i have to use the HC 3.2 FULL instead
.....Acer_A500_7.006.03_COM_GEN1.zip
Once flashed, thankfully I recieve the 2 small OTA Updates to get up to 3.2.1 again
Another couple of days the ICS OTA d/l'ed and installed with no probs....
is that clearer or am i making things worse????
Click to expand...
Click to collapse
What I've learned from this whole process is that all of the obstacles I'm facing are due to my lack of knowledge. Thanks for sticking with me Dibb. I can't thank you enough.
KiwiN said:
When I perform the steps (hold reset + power for 3 secs then release power); the tablet turns on as it usually does. It goes to the Acer screen, then android and back to the black home screen.
Click to expand...
Click to collapse
I could never get mine into apx mode with the usb cable plugged in. So try that if you haven't. And it is literally hold reset, then press power, without letting up on the reset, release the power button after 3 seconds (use a watch or timer!) then one more second before you release the reset... It does work, but the timing has to be close. It must have a tenth of seconds or less tolerance. Very picky... I've done it on 2 different a500s so far and I am heading to do another tonight. If it doesn't work I'll be right back!!!
KiwiN said:
I got the word pass; now using recovery mode to flash a rom.
not sure which bootloader I have.
I am using:
Acer_A500_7.006.01_COM_GEN2: http://vacheandroid.com/files/Acer_...1_COM_GEN2.zip
But after it says install from sdcard complete it also give me the message:
E: Can't mount/ dev/block/mm....
E: Can't mount Cache: recovery/log
E: can't mount open cache: recovery/log
E: Can't mount /dev/block/mm...
found this:
What I've learned from this whole process is that all of the obstacles I'm facing are due to my lack of knowledge. Thanks for sticking with me Dibb. I can't thank you enough.
Click to expand...
Click to collapse
Hi m8 Hwya goin - just got home - what's the lay of the land???
Holey motley we just had a good shake....thort was gonna carry on thank fk it stooped, phew, just been awhile since we had one like that, scary
Crikey just as I finished typing "....land"
Back to more important matters..... whr u at m8????
None of the roms I've tried to flash go to completion. I'm stuck at trying to flash different roms from recovery mode. Not much luck with what I've tried but I'm going to try more before I give up.
Are there any particular roms I should try more than once?
Or why am I getting the "error" messages stated earlier?
KiwiN said:
None of the roms I've tried to flash go to completion. I'm stuck at trying to flash different roms from recovery mode. Not much luck with what I've tried but I'm going to try more before I give up.
Are there any particular roms I should try more than once?
Or why am I getting the "error" messages stated earlier?
Click to expand...
Click to collapse
recovery mode???
u need a new boot and recovery image on that thing
the HC EUU based flash arent working even tho u got a PASS on screen after TDv4
So HC based methods arent up to it. You need nvflash/fastboot.
We need ICS with the unlocked bootloader it has access to another level below where HC worked because HC b/l is and always has been locked down.
If ICS cant fix it, I have no idea what will and my offer to buy is off the table!!!!
check out civatos guide and ready yourself for nvflash via zip files in that post or blackthund3rs APXflash tool, with a complete tutorial for using it, all links in my sig.
good luck
Just to chime in with a tip on getting google drivers to work.
When getting any device not recognized, or driver error, generally I go into windows device manager, select the unknown or offending device, update driver, only I choose which driver to use, and ignore the error message where it says "may not be compatible with your device", and use it anyhow.
I get that occassionally when swapping back and forth between devices.
Also, battery not charging and display errors, are usually a sign of EC Power control. So you were on the right track about that. Once you get a rom up and running, if the batt don't charge, then there are some EC flash's you can do from CWM.
Back at it again using BT's nvflash tool. And tablet is still bricked.
I've tried a few different bundles and none allow me to operate the tablet. Everything goes smoothly and I get "pass" at the end of the process. When I go to reboot the tablet, it gets stuck at the black start up screen.
Found another lead: http://forum.xda-developers.com/showthread.php?t=1579490
Sounds like he was in the same situation as I am but has a bit more skills and knowledge dealing with problem solving.
You say you were able to flash roms. So apparently recovery is working OK. Have you tried flashing civato's flexreaper? It has code that will detect whether you bootloader is HC or ICS. You may just be flashing a rom that doesn't match your bootloader... I know I'm jumping into the middle of this, but it's just a thought.
Also, when you did the hardware reset with the rotation lock switch did you get the confirmation that it was, in fact, being wiped?
Failing all that, I'd be willing to take it off your hands for spare parts...
Sent from my A500 using Tapatalk 2
A bit of an SOS situation if anyone knows the right steps please
Well, I restored a Titanium Backup and mistakenly toggled the "restore system apk". It ran fine, all restored and then when I rebooted got stuck.
By "stuck", it re-boots constantly. It shows the LG animation, then all I can see is two messages before it starts booting again:
1) "Unfortunately, Google Play Services Has Stopped"
2) "Unfortunately, System UI has stopped
... and then it does the entire boot sequence, animation, again, and again.
Here is what I can do:
* It is in USB debug mode.
* I have drivers on laptop
* I am able to connect with adb and also shell into phone.
* With adb, I have output to the file an "adb bugreport" as well as an "adb logcat".
* I have several backups:
a) The modemsst1.img and modemsst2.img created by Titanium Backup
b) Titanium backups (full apps and data)
c) an "adb backup - all" backup
* I managed to get it into firmware update mode by pressing the volume up button and the power button and then when it flashed red a few times, just the up button. So, I can get it into Firmware update mode.
Of course, I have never really used adb before, except to dabble a bit. So, I am encouraged that I can somehow get into with shell.
I am not unplugging it until I know what to do!
Since then I have been able to turn the phone off and also put it into charging on USB.
This is what worked:
* Hold down power and volume down button until booting stops and phone turns off completely.
When it does shut down, I kept buttons down until it flashes logo again and then shuts down again. Then I let go. Phone is off and when I plugged in the charger it shows charging animation.
Now, after inspecting the bugreport, I noticed a lot of these messages for all the system apps like this one:
"I/PackageManager(21318): Expecting better updatd system app for com.lge.sizech"
I think the cause of all this shralp is this, I did a LG Mobile Support Tool "Upgrade Recovery" and then in Titanium Backup I restored an older backup (incl system apks). At least that makes sense seeing all the "Expecting better apdat system app" messages in the bugreport.
Still not sure what to do next
I tried the very good instructions here:
[Guide] Unroot/Unbrick - flash official factory firmware with LG Launche
http://forum.xda-developers.com/showthread.php?t=2471370
The update succeeded. However, when I rebooted the phone it is in the same boot-loop with message that it was before.
I used the BELL D803B10D_00.kdz file. Now I will try with the earlier version BELL D803BA_00.kdz file.
We will see what happens ...
do you have nandroid backup from previous rom?
I have three backups:
1) Titanium Backup (full)
* This was my first backup performed right after rooting device and installing Titanium Backup.
2) Titanium Backup (full)
* Did this 2 days ago. Device was working OK and did as precaution.
3) ADB BACKUP. I did this one before my Titanium restore.
I restored the first titanium backup and that (ooooppps!) was after I did an LG Firmware update.
ALSO:
I am on Windows 7 64 and although adb works fine, fastboot does not. I understand that might be a problem with windows 7 64.
So, unless anyone objects, I am going to redo on my windows 32 machine and also "fastbook oem unlock".
Since firmware is OK, if I do the fastboot oem unlock, that will wipe everything. But I can still boot and re-setip the phone, right?
Just checking before I fudge everything up here ..
ALSO ALSO:
I had antivirus/theft security installed and I disabled it partway through last restore.
Maybe that has somethng to do with this all .
But I am still cool because I can ADB and also firmware install seems ok.
ADB works and that is the one good sign.
or you can follow ADB Sideload method
http://forum.xda-developers.com/showthread.php?t=2318497
zekurosu said:
or you can follow ADB Sideload method
http://forum.xda-developers.com/showthread.php?t=2318497
Click to expand...
Click to collapse
I don't (didn't) have TWRP installed. How can I sideload without it?
Also, should I adb oem unlock to get it wiped at this point?
I'm having a similar problem on a Bell D803. Just happened very randomly today. I turned my phone off for an exam, then turned it back on after.. initially had no signal and a black background. Settings for factory reset wouldn't work. My phone is rooted and has TWRP. I went into recovery and formatted.
Bootloop.
Bootloop.
Bootloop x 20.
I however, don't get the same two messages. I just keep bootlooping.
Got home, tried to go through download mode to unbrick it, but for some reason my computer isn't picking it up. I have all the drivers, and before this incident, it was recognized.
Any solutions?
I'm thinking of buying an OTG USB and then just flashing a stock zip from recovery. Would that be a possible viable solution?
asdfvtn said:
I'm having a similar problem on a Bell D803. Just happened very randomly today. I turned my phone off for an exam, then turned it back on after.. initially had no signal and a black background. Settings for factory reset wouldn't work. My phone is rooted and has TWRP. I went into recovery and formatted.
Bootloop.
Bootloop.
Bootloop x 20.
I however, don't get the same two messages. I just keep bootlooping.
Got home, tried to go through download mode to unbrick it, but for some reason my computer isn't picking it up. I have all the drivers, and before this incident, it was recognized.
Any solutions?
I'm thinking of buying an OTG USB and then just flashing a stock zip from recovery. Would that be a possible viable solution?
Click to expand...
Click to collapse
Well, I am able to connect with adb fine on my laptop (Win 7 64) but not on my desktop (Win 7 32)
But on my Win 7 64 I cannot get into fastboot.
I am wondering if the driver install on my desktop went foo-bar and needs reinstall. Also, I noticed that the website drivers are more recent USB drivers than some of the ones linked on this site.
I used adb uninstall package for many user packages and it was success. But I still see the packages listed in the bugreport?
For example: I already uninstalled "com.benhirashima.skiplock" and also "com.lookout".
Why? What to do to really zap them for good?
Sorry, I posted the wrong link earlier.
This was the guide I used which succeeded but made no difference to the boot-loop.
LG G2 Stock Firmware (Go Back to Stock)
http://forum.xda-developers.com/showthread.php?t=2432476&highlight=d803
Just figured out how to do a factory reset.
http://www.youtube.com/watch?v=3ogBvzbPikc
The hard reset worked and now I am configuring the phone settings!
So, again, this is what I did:
1) http://forum.xda-developers.com/showthread.php?p=45293512
2) http://www.youtube.com/watch?v=3ogBvzbPikc
Not sure if it all worked but I am setting the phone up as we speak (or as I type)
natureburger said:
Well, I am able to connect with adb fine on my laptop (Win 7 64) but not on my desktop (Win 7 32)
But on my Win 7 64 I cannot get into fastboot.
I am wondering if the driver install on my desktop went foo-bar and needs reinstall. Also, I noticed that the website drivers are more recent USB drivers than some of the ones linked on this site.
Click to expand...
Click to collapse
Hmm that's strange. Unfortunately for me, I'm already on 64-bit and it still isn't picking it up.
ALL FIXED UP
WORKING 110%
:good:
natureburger said:
ALL FIXED UP
WORKING 110%
:good:
Click to expand...
Click to collapse
I have followed this to a t.
Succesfully flashed the stock firmware that came with the phone when sold.
Did hard reset using the the power button and volume down
= phone rebooting every 10 seconds, no wifi, imei = null
adb devices = offline.
Really depressed right now. If anybody can help me I would appreciate it.
zprovo said:
I have followed this to a t.
Succesfully flashed the stock firmware that came with the phone when sold.
Did hard reset using the the power button and volume down
= phone rebooting every 10 seconds, no wifi, imei = null
adb devices = offline.
Really depressed right now. If anybody can help me I would appreciate it.
Click to expand...
Click to collapse
Press the power button down and hold it.
It should turn off, then look like it is turning on, (flash logo very briefly) and then turn off.
Let go of power button and it should stay off.
Do that. Now, does it work to turn off completely?
Let's see if you can do that first.
Then .. do hard reset, exactly like this:
http://www.youtube.com/watch?v=3ogBvzbPikc
Does the hard reset screen show and give you hard reset options?
natureburger said:
Press the power button down and hold it.
It should turn off, then look like it is turning on, (flash logo very briefly) and then turn off.
Let go of power button and it should stay off.
Do that. Now, does it work to turn off completely?
Let's see if you can do that first.
Click to expand...
Click to collapse
Yup. I totally understand what you are saying and have done it many times. I had to use that method to get into download mode and also had to use it to do hard reset.
I just reflashed the phone all over again a second time succesfully.
Reboots every 5 seconds. Keyboard came up for a few seconds for the first time in 48 hours during the initial setup phase. 5 seconds later as I was trying to input a wifi code it would not appear. then it rebooted as usual.
I really appreciate any input right now. :cyclops::crying:
zprovo said:
Yup. I totally understand what you are saying and have done it many times. I had to use that method to get into download mode and also had to use it to do hard reset.
I just reflashed the phone all over again a second time succesfully.
Reboots every 5 seconds. Keyboard came up for a few seconds for the first time in 48 hours during the initial setup phase. 5 seconds later as I was trying to input a wifi code it would not appear. then it rebooted as usual.
I really appreciate any input right now. :cyclops::crying:
Click to expand...
Click to collapse
1) Are you able to completely turn it off using my instructions?
2) When you hard reset (2nd half of this video), http://www.youtube.com/watch?v=3ogBvzbPikc
a) Does the hard reset screen show?
b) Does it give you the hard reset options?
3) Before it was bricked, was it in 'usb debug mode' in developer options?
4) Which kpz version did you restore to?
5) Did your "adb devices" ever work? Did your "adb shell" ever work?
natureburger said:
1) Are you able to completely turn it off using my instructions?
2) When you hard reset (2nd half of this video), http://www.youtube.com/watch?v=3ogBvzbPikc
a) Does the hard reset screen show?
b) Does it give you the hard reset options?
3) Before it was bricked, was it in 'usb debug mode' in developer options?
Click to expand...
Click to collapse
1) Yes absolutely. It is sitting next to me right now doing nothing at all because I turn it off when I am not trying to fix it, otherwise it keeps rebooting relentlessly.
2) a) Yes, same as the video. b) Yes it says the same exact thing as the video. I press power key twice and it begins. The stock recovery android appears with a loading bar on the bottom for ~1 minute then it goes to the boot "lg animation".
3) Yes it was. Before it was bricked I essentially always had it in debug mode because I successfully rooted it and simply left it on debugging mode after having to activate it to root.
4) D801V11B_00.kdz The EXACT same as the original. This is a Videotron (canadian) phone. I can clearly remember without a doubt going into about phone and this is what it was running before all of this happened.
5) I am having a bit of memory strain here, but I do believe it also said adb devices before any of the issues came. It is a good point I will try "adb device" from another trusted computer.
Other notes: I can browse the android os for a few seconds. Sometimes sound does not work, wifi is non functional (even though the keyboard never appears, I managed to have a security free wifi in my proximity and it would not connect (was saying: temporarily avoiding bad signal)) and also I do have modemstat1.img and modemstat2.img backups for EFS.
adb devices consistently shows "offline" but it is definitely recognizing the phone. I have also tried using usb debugging activated and still "offline". Drivers are up to date and all.
The upper drawer in the usual g2 user interface is strange now. it doesnt have anything except for the date (1970 something...) and a "gear" icon for system settings. I am talking the drawer you drag down from the top of the screen.
This phone was working with absolutely no problems 2 days ago.
Thank you so much for looking into this. I have certainly exhausted my repairing capacities. I am entirely dependent upon the knowledgeable individuals in here from here on out.
zprovo said:
1) Yes absolutely. It is sitting next to me right now doing nothing at all because I turn it off when I am not trying to fix it, otherwise it keeps rebooting relentlessly.
2) a) Yes, same as the video. b) Yes it says the same exact thing as the video. I press power key twice and it begins. The stock recovery android appears with a loading bar on the bottom for ~1 minute then it goes to the boot "lg animation".
3) Yes it was. Before it was bricked I essentially always had it in debug mode because I successfully rooted it and simply left it on debugging mode after having to activate it to root.
4) D801V11B_00.kdz The EXACT same as the original. This is a Videotron (canadian) phone. I can clearly remember without a doubt going into about phone and this is what it was running before all of this happened.
5) I am having a bit of memory strain here, but I do believe it also said adb devices before any of the issues came. It is a good point I will try "adb device" from another trusted computer.
Other notes: I can browse the android os for a few seconds. Sometimes sound does not work, wifi is non functional (even though the keyboard never appears, I managed to have a security free wifi in my proximity and it would not connect (was saying: temporarily avoiding bad signal)) and also I do have modemstat1.img and modemstat2.img backups for EFS.
adb devices consistently shows "offline" but it is definitely recognizing the phone. I have also tried using usb debugging activated and still "offline". Drivers are up to date and all.
The upper drawer in the usual g2 user interface is strange now. it doesnt have anything except for the date (1970 something...) and a "gear" icon for system settings. I am talking the drawer you drag down from the top of the screen.
This phone was working with absolutely no problems 2 days ago.
Thank you so much for looking into this. I have certainly exhausted my repairing capacities. I am entirely dependent upon the knowledgeable individuals in here from here on out.
Click to expand...
Click to collapse
Hmmmm..... why your adb devices is not working? But the re-pair works and you can then do hard reset.
But that is good information you shared.
Maybe someone else can chime in.
From my experience:
1) adb usb access seems spotty. My win 7 64 connected fine and it even kept the shell through the reboot cycle. But on my win 7 32 machine it was only detecting device and then not able to shell.
2) I was also able to use from the LG website LG MOBILE SUPPORT TOOLS.
Download the LG MOBILE SUPPORT TOOL
I downloaded the most recent one from the LG website and make sure to select your options >> country and then the correct phone model at the upper right hand corner of the tool.
Then install USB driver for correct phone model.
Then see if USB works, "adb device" should return the device code.
"adb shell" should show the shell prompt.
3) There is always fastboot. But I an noob and know 0% about how to properly connect and use it.
Some others please chime in and help this droid bro!
I could with some help please. I expect that the answer is already on the forum somewhere, so if someone could post a link, that would be great.
My Nexus - unlocked and rooted - 5.1 with Wugfresh several months ago, today decided not to boot up.
I get "Google" then it goes to a black/glowing screen and stays there.
With some fiddling around I can get the dead Android and "no command". I can get into the power off/recover/reboot bootloader etc screen.
I have wiped the cache - no change.
I have done a factory reset - wiped all data - no change.
Using Wugfresh, I get - no ADB
I am not able to check usb debugging because I can't get into the device.
The thing is obviously alive (although not as we know it) because windows install a driver for it when it is plugged in to the USB post. However it installs an MTP driver and I am not able to change this.
Any ideas anyone?
Thanks
lejars1 said:
I could with some help please. I expect that the answer is already on the forum somewhere, so if someone could post a link, that would be great.
My Nexus - unlocked and rooted - 5.1 with Wugfresh several months ago, today decided not to boot up.
I get "Google" then it goes to a black/glowing screen and stays there.
With some fiddling around I can get the dead Android and "no command". I can get into the power off/recover/reboot bootloader etc screen.
I have wiped the cache - no change.
I have done a factory reset - wiped all data - no change.
Using Wugfresh, I get - no ADB
I am not able to check usb debugging because I can't get into the device.
The thing is obviously alive (although not as we know it) because windows install a driver for it when it is plugged in to the USB post. However it installs an MTP driver and I am not able to change this.
Any ideas anyone?
Thanks
Click to expand...
Click to collapse
It is possible that your system and/or boot partitions have become corrupted.
If that is the case, you'll need to reinstall the ROM. The best way to do this is to install a custom recovery like twrp or clockworkmod, reformat your partitions, and proceed from there.
Hi - thanks for this.
I got it sorted in the end.
Here's a link to what happened.
http://forum.xda-developers.com/showpost.php?p=60970017&postcount=1597
Ok, so to start off I'm very familiar with Nexus Root Toolkit an its many graceful features & its ablity to bring the N7 from the brink of destruction (Soft -Brick) "AS LONG AS YOUR PC CAN DETECT THE DEVICE".
Here's the issue.. I was in TWRP (Multi-ROM) just renaming 1 of the Secondary ROMs to more friendly names, I hadn't done any flashing of any zips or roms for a few boots, I just booted into Recovery to do some renaming of Secondary ROMs that I had installed a few nights before but I had been in an out of several different one's just making sure they were all working so anyway.. after I was done renaming, I reboot the system & it just went F'ing blank.. now nothing.. there's no back light, no bootlogo, nothing happens at all when I plug in the charging or hold the power button with or w/out the vol-+ keys, I've checked the battery connection, it was snug but I removed it over night.. still nothing, I'm just clueless.. Before we jump on the NRT do a factory wipe & restore, when I plug it into Windows it instantly pops up with the "Device has Malfunctioned" not the "installing adb drivers" or anything like it has so many times before.. either Im over thinking this an the answer is so simple Im blinded by rage over how much this p1sses me off that it was working fine one moment an then just reboots to blank nothingness.. even if I take the battery out an try plugging it directing into the pc via the OEM usb cable it gives the same error with or w/o the battery in .. the toolkit cant even see it cause windows cant establish what the hell it is.. And yes I've tried installing every android driver possible.. the N7 was primarily for my wife to read e-books on.. so i rarely played with it.. an it was new sealed in the box just bought last year around this time so i can't believe the Flash Memory is shot already, if anyone could throw me their 2 cents it would be greatly appreciated , this is so frustrating but I think its BRICKED.. or at least some tiny flash chip is toast..
its the - N7 2012 Grouper WIFI Only model -
p.s. I apologize for the slight harsh tone, I'm just upset with this issue.. I got this particular tablet with the knowledge an understanding that it was the (almost) un-brickable tablet, yet I managed to do it.. If by some chance I get it to fire up, I will definitely let ya know.. But I have read alot of posts an my guess is somehow I managed to mess up the nvflash an now the memory chip or something is corrupt beyond a NRT Factory reset.. but again it was at almost full battery when i rebooted from within the TWRP Menus & I wasn't flashing anything previous to me being in my Main Rom which was stock rooted 4.4.4 de-bloated, playing a game called Empire 4 Kingdoms for like a 1/2 (just getting my daily's) before i decided to check out my Secondary Roms an rename a few because I wanted to started playing around with them to test how the same game played on different flavors or Android..
phnxnvrdies said:
Ok, so to start off I'm very familiar with Nexus Root Toolkit an its many graceful features & its ablity to bring the N7 from the brink of destruction (Soft -Brick) "AS LONG AS YOUR PC CAN DETECT THE DEVICE".
Here's the issue.. I was in TWRP (Multi-ROM) just renaming 1 of the Secondary ROMs to more friendly names, I hadn't done any flashing of any zips or roms for a few boots, I just booted into Recovery to do some renaming of Secondary ROMs that I had installed a few nights before but I had been in an out of several different one's just making sure they were all working so anyway.. after I was done renaming, I reboot the system & it just went F'ing blank.. now nothing.. there's no back light, no bootlogo, nothing happens at all when I plug in the charging or hold the power button with or w/out the vol-+ keys, I've checked the battery connection, it was snug but I removed it over night.. still nothing, I'm just clueless.. Before we jump on the NRT do a factory wipe & restore, when I plug it into Windows it instantly pops up with the "Device has Malfunctioned" not the "installing adb drivers" or anything like it has so many times before.. either Im over thinking this an the answer is so simple Im blinded by rage over how much this p1sses me off that it was working fine one moment an then just reboots to blank nothingness.. even if I take the battery out an try plugging it directing into the pc via the OEM usb cable it gives the same error with or w/o the battery in .. the toolkit cant even see it cause windows cant establish what the hell it is.. And yes I've tried installing every android driver possible.. the N7 was primarily for my wife to read e-books on.. so i rarely played with it.. an it was new sealed in the box just bought last year around this time so i can't believe the Flash Memory is shot already, if anyone could throw me their 2 cents it would be greatly appreciated , this is so frustrating but I think its BRICKED.. or at least some tiny flash chip is toast..
its the - N7 2012 Grouper WIFI Only model -
p.s. I apologize for the slight harsh tone, I'm just upset with this issue.. I got this particular tablet with the knowledge an understanding that it was the (almost) un-brickable tablet, yet I managed to do it.. If by some chance I get it to fire up, I will definitely let ya know.. But I have read alot of posts an my guess is somehow I managed to mess up the nvflash an now the memory chip or something is corrupt beyond a NRT Factory reset.. but again it was at almost full battery when i rebooted from within the TWRP Menus & I wasn't flashing anything previous to me being in my Main Rom which was stock rooted 4.4.4 de-bloated, playing a game called Empire 4 Kingdoms for like a 1/2 (just getting my daily's) before i decided to check out my Secondary Roms an rename a few because I wanted to started playing around with them to test how the same game played on different flavors or Android..
Click to expand...
Click to collapse
UPDATE STATUS - If I plug it into the pc without the battery i get a windows driver install box that says "Installing APX..." does this indicate the NVFlash is corrupt or is there a way to get out of apx mode.. im not familiar with that mode .. only ADB & fastboot..
Update 2 - After reading lots, I've come to conclude its hardbricked, must have had an error in memory or whatever.. its stuck in APX mode so im going to replace the whole MB with a working 32GB [model me370t] & start over .. maybe ill not install so many ROMS via multirom.. just a few - THREAD BE CLOSED - I'm done here, good luck to anyone with similar results