Database Users

Odin screwed me over

Hey everyone,
so first let me tell you that I am not a newb so I tried every possible solution I could come up with, so this is just a last attempt.
So I wanted to tests some ROMs around since I had a free friday night and Odin screwed me over. I tried to flash JM9 with 512, some other Froyo ROMs and even gave a shot to Darky's resurrection. But no matter what I try, Odin always does one of these things:
It gets stuck at Initializing...
It gets stuck at SET PARTITION...
It gets stuck at Kernel flashing...
It turns my screen into a random colour and gets stuck (green, gray, blue, red so far..)
Tried flashing with/without PIT/Partition, 1 package ROMs, 3 package ROMs, etc.. To no avail. Tried to have the battery out for half an hour, etc..
All I can do with my phone atm is acces Download mode, so that kinda keeps me hoping, however it won't boot or go to recovery..
So any ideas anyone? Thanks for any help..

Download a known working copy of Odin and try that. also download new firmware from samfirmwares too just in case your current firmwares have become corrupted.

used odin 1.0 with pit 512
this was a guide i made for a not so savvy mate. so folder links and other bits you wont have but im sure it will help.
STAGE ONE
You will see in the stage one folder two items one is ODIN the other is a PIT file.
Lets plug your phone cable into a usb port ( on the main board is best not extensions)
Open up ODIN
On the left hand side make sure “Re-Partition” is ticked.
Now click on the words “PIT”
This should bring you up a selection window locate it to the “PIT” file in the same folder as ODIN.
Now put your phone in that downloader mode VOL DOWN+HOME+POWER
Plug the phone into the USB port.
You will now see the first box has a yellow com port under it (top left hand corner)
Now click start.
You will see some text in the bottom left message box.
This may take about 5mins.
But once it is done you will see a big green PASS!! In the top left box.
If its been to long say 10mins take battery out and start again.
If it doesn’t work second time Gtalk.
Once you see PASS!!!! Unplug the phone and take battery out.
STAGE TWO
On the right hand side click RESET ( its next to start)
Now un-tick RE-Partition.
Now in the stage two folder there is three files.
In ODIN click “PDA” this will bring up the selection window
Match it to this file
I9000XXJPY-REV03-PDA-low-CL757011.tar.md5
Phone matches with this file.
MODEM_I9000XXJPY.tar.md5
CSC matches with this file.
GT-I9000-CSC-MULTI-OXAJPY.tar.md5
Now that you have selected the files put the battery back in your phone.
Go back to downloader mode.
Plug phone it when you see the Yellow com port like in stage one click start.
This may take a while but you will see some text in messages box bottom left.
Once this is done we will again get the green PASS!!!!
The phone will proceed to the home screen.
You have successfully updated your phone to the latest version.
Pat on back.

Also make sure kies isnt running and try as many different usb ports as you can.
windows sucks at com port control.

Thanks everyone for the input but as I've mentioned I've tried all possible methods that came to mind. Even the one described above..
Any other ideas? :x

Could it be that your USB driver is screwing things up? Try flashing from a different port or better yet a different computer.
If all else fails maybe you could try to flash with Heimdall instead of Odin.

dakine said:
Could it be that your USB driver is screwing things up? Try flashing from a different port or better yet a different computer.
If all else fails maybe you could try to flash with Heimdall instead of Odin.
Click to expand...
Click to collapse
Different USB ports is always worth trying.
Sent from my GT-I9000 using XDA App

I always use Odin 1.0 but you could try 1.3 or 1.7.
Sent from my GT-I9000 using XDA App

Just throwing ideas around really.
can you get into upload mode? Try clearing SD card. Clearing cashe. All thy kind of thing.
Try flashing a different kernal disable all lax fix stuff.
What was your set up before you tried flashing?
Sent from my GT-I9000 using XDA App

Install (or re-install, whatever) USB drivers. http://forum.xda-developers.com/showthread.php?t=728929
Uninstall Kies (iff installed), it's horrible anyway
Like others said, use a different USB port. Reboot PC (lol, I know).
I like Odin 1.7 best so far...
And I agree, please describe your initial setup. Any fancy kernels? Lagfix/ext4?

Well finally. I did everything on my PC and nothing worked, but managed to try on friend's PC and it worked.
Anyone has an idea on what could have caused this? Hope future flashing will work on my PC
Also thanks to everyone trying to help, limited to 5 thanks only tho

I'm guessing it a driver issue. Assuming you have Windows, whenever you plug a USB device a driver is installed. You can see what these are if you enable the hidden devices: http://www.techrepublic.com/blog/window-on-windows/get-rid-of-old-device-drivers-hidden-in-vista/867 for Vista for example, but it works just like that for others.
Wipe every trace of the Samsung/Android drivers, uninstall Kies, run a registry cleaner, rebbot (obviously), and just reinstall the Samsung/Android drivers. Get the newest Odin. If that doesn't help, I have no idea what the cause might be.

[Solved] Mystery bricked tablet. Black "android systems" screen

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

SOD and no root and unable to connect to a pc!

Ok so I was running taboonay 3.0d and I thought I'd have a go at Thor's rom. Flashed it wasn't really into it few things missing that I like in taboonay. So I then restored my back up. All hunky dory.
I then flashed a zip for scrillax v8 bootloader. It seemed to work fine, tablet boots up and rom running fine. I then tried to get to recovery and it's just not happening. Acer recovery says it cannot get root access. When I reboot I can get into the bootloader menu but none of the commands work. I can't get into the recovery menu at all no matter what I do. So then I figured I'd give Blackthund3r's root tool a go. Got everything ready on the pc including latest acer drivers. Now the tab isn't showing up on the pc either. I know some others have had similar problems but no solution was found in the other threads and considering that I probably screwed up badly somewhere along the way I thought I'd start this thread where you can all point out my ignorance and stupidity without bothering anyone else :silly:
Any help?

Any advice at all would be great, I have reinstalled drivers for tab but still no go! I'm on a old xp pro laptop. Everything else connects to the usb port and the cable is working fine

If you can't get to Recovery, you will need to reflash that.
But first thing is first. And that's the driver issue.
With the tab plugged into the PC, go to Device Manager, and see if it reflects there. If not, you will probably have to reload the drivers. You have a choice, which is the Acer Driver installation, or you can try the Google USB Android drivers. Generally I have had not much luck letting windows search the PC, so I usually install them manually. You can either;
a. Direct device manager to look in a specific folder for the google drivers, or;
b. In Device Manager, when you choose update drive, use "select from list" and see if the acer drivers show up there.
Generally, when you install the acer drivers, you should "right" mouse click the install file and select "run as administrator".
MD

Thanks md will give it another go
My device manager has no option for select from list or update drive, just scan for new hardware. Nothing shows up for acer.

irishmoe said:
Thanks md will give it another go
My device manager has no option for select from list or update drive, just scan for new hardware. Nothing shows up for acer.
Click to expand...
Click to collapse
Ok, now I run Win 7. But XP should be similar.
Are you saying in device manager, you do not have a device with an exclamation mark when you plug the tab in???
If you do, then right click the exclamation mark, select properties. Then the Tab "driver". Next, select "update driver". Then, "browse my computer for drivers". You should get the option to "select from a list".
If your PC does not detect the tablet at all when you plug it in, then it';s a different issue. It's what we call a USB Brick. At first guess. Usually easy to fix on the 500.
Can you start your tablet in APX mode? hold the pin reset, press and hold pwr. Count to 3, and release pwr, then 1 second later, release the pin reset. You should have a black screen with the pwr lite on.
I'm thinking you might want to do the manual flashing of the bootloader + 1.7.3 recovery. Obviously the bootloader V8 flashed, or it wouldn't work at all. Civato has instructions for manual flashing of the bootloader and recovery. Note that I HOPE you wrote down your UID number somewhere. As you will need to convert it to the SBK.
MD
EDIT. One more note. When you boot to the bootloader menu, in your case, probably the only option that will work is "fastboot mode". When you select it, the menu should go away, and it should say "fastboot mode". Then plug into PC and see if windows detects it in device manager. If so, you can fastboot a recovery image to it. Note, that for fastboot to work, you must have the Android SDK installed on your PC. Because you will have to run the fastboot commands from a command window. But for now, check to see if you get to fastboot mode on the tablet.
Sorry I can't spend a lot of time, as it';s late in moscow. Job tomorrow. But Skirlaz_CZ can give you the commands to fastboot a recovery in his bootloader thread.

Thanks MD I can get into fastboot mode so I'll try that one first. I didn't write and numbers down unfortunately. I was following a thread on tegraowners to install the bootloader which made no mention of making records( I'm a simpleton that needs to be led by the nose)
I appreciate your input

irishmoe said:
Thanks MD I can get into fastboot mode so I'll try that one first. I didn't write and numbers down unfortunately. I was following a thread on tegraowners to install the bootloader which made no mention of making records( I'm a simpleton that needs to be led by the nose)
I appreciate your input
Click to expand...
Click to collapse
Ouch! No UID numbers. That hurts. Look in your old CWM recovery backups (if you have) on your EXT SD Card. If you were at one time running a more recent version of CWM, You might have them in the recovery folders. The more recent recovery programs in the backup folders, it's called UID.txt. You have to have this if you use NVFlash. No way around that.
With Fastboot, you don't need it, as you will fastboot the recovery image. If successful, that should allow you to boot to recovery, and flash one of the custom roms. Make sure you do your wipes as in the Rom install instructions. I use CWM 1.7.3 (I've been too busy to try EZTerry's or the TWRP versions. But CWM works good so far.
If not, well, there;s always the update.zips to get a stock ICS on your tab.
Either way, we'll get you running, so don't worry. Just takes a little time between time zones, work, and family
MD

Moscow Desire said:
Either way, we'll get you running, so don't worry. Just takes a little time between time zones, work, and family
MD
Click to expand...
Click to collapse
You're not wrong there! I'm doing the whole ikea/home improvement thing with the family today. I'll try the fastboot later
Again I really appreciate the help.

Ok MD so the fastboot doesn't work at all. I installed adb using knives and forks and that couldn't pick up the tab for drivers installation. My head is wrecked! checking backups for numbers now
0x037c62074 and a few more got it
Edit: farkin idiot I just noticed the sdk requirement! Will install sdk and give fastboot another whirl

irishmoe said:
Ok MD so the fastboot doesn't work at all. I installed adb using knives and forks and that couldn't pick up the tab for drivers installation. My head is wrecked! checking backups for numbers now
0x037c62074 and a few more got it
Edit: farkin idiot I just noticed the sdk requirement! Will install sdk and give fastboot another whirl
Click to expand...
Click to collapse
HA HA! Yep, gotta have the SDK for ADB and Fastboot. I posted some instructions yesterday about flashing recovery via fastboot.
http://forum.xda-developers.com/showpost.php?p=29294671&postcount=6
You should be able to do it if you already have V8 Bootloader.
MD

Nice one MD going to try it out.

irishmoe said:
Thanks MD I can get into fastboot mode so I'll try that one first. I didn't write and numbers down unfortunately. I was following a thread on tegraowners to install the bootloader which made no mention of making records( I'm a simpleton that needs to be led by the nose)
I appreciate your input
Click to expand...
Click to collapse
I'll add that then - good idea
EDIT: It is done. And it is now foolproof. If you read that forum post now and STILL don't save your UID then I worry about you http://forum.tegraowners.com/viewtopic.php?f=30&t=388

irishmoe said:
Nice one MD going to try it out.
Click to expand...
Click to collapse
Waiting for an update

blackthund3r said:
I'll add that then - good idea
EDIT: It is done. And it is now foolproof. If you read that forum post now and STILL don't save your UID then I worry about you http://forum.tegraowners.com/viewtopic.php?f=30&t=388
Click to expand...
Click to collapse
Ha ha cheers mate! Like I said I'm a simpleton but not quite that bad.
Thanks for all the good work. I was actually following another thread stupidly when I should have been following yours.
MD - was away for a few days, just back but have had a few beers so not doing anything stupid tonight. Got sdk installed.

MD - Have you a link to download cwm 1.7.3 img? The download link in tegra won't work for me.
edit - nevermind I usedthe recovery skrillax suggested in his thread. Problem is the pc is not picking up the tab at all. Just says waiting for device

irishmoe said:
MD - Have you a link to download cwm 1.7.3 img? The download link in tegra won't work for me.
edit - nevermind I usedthe recovery skrillax suggested in his thread. Problem is the pc is not picking up the tab at all. Just says waiting for device
Click to expand...
Click to collapse
Sorry I was away. Did everything work ok for you? All running? (been trying to chase down my rom issue)
If it says "waiting for device", then you need to check your device manager, and make sure the correct driver is recognized. (APX, Fastboot, Recovery, Download, etc). Usually, I can change drivers while this is happening, and the process will complete.
MD

ok I don't mind admitting that I'm totally lost here. Nothing resembling the tab is showing up device manager so how can I check the drivers?I've been playing around with device manager for a while now and I can't find any way to do what you suggested
I've uninstalled and reinstalled the drivers again and again. Nothing! Could it have anything to do with me having a gateway? I wouldn't think so because they're the same inside.

Righto, no matter what I do the tab won't show up. Obviously can't check the drivers without the device showing up so I really am at a loss.
Even if I try the manual flash from civatos thread I will still come up with the same problem. No device no can do

irishmoe said:
Righto, no matter what I do the tab won't show up. Obviously can't check the drivers without the device showing up so I really am at a loss.
Even if I try the manual flash from civatos thread I will still come up with the same problem. No device no can do
Click to expand...
Click to collapse
be worth checking you still have usb debugging enabled m8
EDIT: The only other thing i can think of is to put yr tab in apx mode manually (press and hold reset button then press and hold power button, when the pwr lite comes on count 3 seconds and then release it, hold reset another second and then let that go) - you should have a black screen and power lite is on) now connect yr cable and see if the pc picks up the acer boot/recovery driver under usb controllers .
If these drivers install then I'd attempt a rollback to HC using an EUU, at least this method depends on yr pc not seeing yr tab. I'd only attempt this tho if the boot/recovery driver is installed and listed in dev. manager.

dibb_nz said:
be worth checking you still have usb debugging enabled m8
EDIT: The only other thing i can think of is to put yr tab in apx mode manually (press and hold reset button then press and hold power button, when the pwr lite comes on count 3 seconds and then release it, hold reset another second and then let that go) - you should have a black screen and power lite is on) now connect yr cable and see if the pc picks up the acer boot/recovery driver under usb controllers .
If these drivers install then I'd attempt a rollback to HC using an EUU, at least this method depends on yr pc not seeing yr tab. I'd only attempt this tho if the boot/recovery driver is installed and listed in dev. manager.
Click to expand...
Click to collapse
Ok ok boot/recovery driver? You've lost me there chap! Xp device manager is showing nothing tab related. Tell me what to do and I'll give it a blast.
I'm using the regular usb slot as opposed to the mini cause I've no mini cable. That should be ok right?

S7 Edge is completely Unresponsive after tried Unroot

Last night I tried to unroot my phone as the title says. Everything was going fine, and I installed the stock files on Odin. The video I found on it said to select re.Partition and T.Flash on Odin. I did, and now the phone is unresponsive and my phone doesn't show up on my computer. I can't turn it on or use any button combination to turn it on. If I hold the power button my computer makes a connection sound but doesn't show up. Please help.

Go to device manager and check if it finds it at any name. Sometimes bootloader devices are even found as "bacon sandwich" . Well.. most of the time they will be hidden under like "marshall bootloader" or something totally weird that You would not plug into Your computer (bacon sandwich).
As long as it makes sound it's good. It means that the device isn't 100% dead.
Try holding Odin button combination(5-10 seconds) with the phone being plugged in and see if odin detects it or if Your device manager shows something.
The good thing? Just in case if You really killed Your phone, take it back to Samsung and tell them that You left Your phone to charge over night and in the morning it was dead. They should replace it. (Note 7 battery affair might be helpful)
And future advice. Don't use t.flash nor repartition. Although I think that repartition is safe as long as You use pit file. But t.flash NOPE. Unless I know what certain thing does, I don't touch it.
Just to sum it up.
1. See if Your phone is detected in Device manager
1b. See if You can get it to be detected by using Odin button combination.
2. If not take it to Samsung. They should replace it, because it's completely dead. And there's no way for them to check the knox.
3. Never use t.flash or repartition again.
4. If You need any further help just tell me
Good luck.

What video did you watch? Options only need to be changed when you flash TWRP - you need to untick the Auto Reboot to make TWRP stick, even with auto reboot it flashes ok. So basically OPTIONS of Odin is just when you are in deep... Now your phone is definitely hard bricked and I would recommend just go to your seller and ask for a warranty fix... if they cant boot to dl mode they might not even be able to see if your knox is 0x1.

ProtoDeVNan0 said:
Go to device manager and check if it finds it at any name. Sometimes bootloader devices are even found as "bacon sandwich" . Well.. most of the time they will be hidden under like "marshall bootloader" or something totally weird that You would not plug into Your computer (bacon sandwich).
As long as it makes sound it's good. It means that the device isn't 100% dead.
Try holding Odin button combination(5-10 seconds) with the phone being plugged in and see if odin detects it or if Your device manager shows something.
The good thing? Just in case if You really killed Your phone, take it back to Samsung and tell them that You left Your phone to charge over night and in the morning it was dead. They should replace it. (Note 7 battery affair might be helpful)
And future advice. Don't use t.flash nor repartition. Although I think that repartition is safe as long as You use pit file. But t.flash NOPE. Unless I know what certain thing does, I don't touch it.
Just to sum it up.
1. See if Your phone is detected in Device manager
1b. See if You can get it to be detected by using Odin button combination.
2. If not take it to Samsung. They should replace it, because it's completely dead. And there's no way for them to check the knox.
3. Never use t.flash or repartition again.
4. If You need any further help just tell me
Good luck.
Click to expand...
Click to collapse
I found a UMBus Root Bus Enumerator. I don't know if that's something

Bus enumerators are the USB controllers in Your computer so I don't think it is it. Maybe You could find something like "unknown device" or "unknown descriptor" something like that..
Btw. Did You install Samsung drivers? Sometimes devices aren't visible in device manager until You install proper drivers.
If nothing really works then download Smart Switch and then plug Your phone in. It should find it in like a emergency mode hopefully. And if smart switch doesn't detect anything either then just go to the place where You got the phone and they will replace it.

Did I hard brick my h990DS

In trying to root it, I downgraded to H990DS10b_00_open_ame_ds_op_1103 via Uppercut. From there I followed carefully the "dirty Santa comes for the H990" thread. I got through to the "untrusted app" message, but I did not get the bat.2 on the cmd window. So I had to restart the phone, and the screen was weird and unreadable. By coincidence Uppercut was not working, giving "error reading from file" on my Windows machine. So from here I did the mistake and got too impatient. At that time I could still see the phone via ADB. Then I thought it might be helpful to do a hard reset - which obviously was a big mistake. Now it powers up showing the LG logo, gives the sound and turns into a weird screen. I can make sound from it by pressing the screen, but after some time it reboots into is a black screen saying kernel crash. It says that I can restart by pressing vol down. When I do that, the same happens again. It also says that I can do ram drop using QPST configuration, whatever that means?
Do I have to say goodbye to it, of do I have any hope?

Doesn't sound like a hard brick to me. I would completely restart the rooting process.
What I would do however, is make sure that all the programs (LG UP etc) and DirtySanta files are correct and working.
Things to try:
• Make sure the drivers are installed correctly. You can google for LG USB drivers. Install and restart.
• Make sure LG UP is run as administrator (as a precaution to access devices)
• Hold Vol Up while the device is off and the plug in the usb cable (while the other end is plugged into the machine) - this should get you into Download mode
• Make sure that you are running the "Run Me First" files in Dirty Santa. This is a common mistake that I have made before even when re-rooting for the tenth time.
• Run all the Dirty Santa CMD files as administrator (it can't hurt).
As far as the screen, does it look like white noise? if so, it is a known kernel incompatibility (the stock kernel) with root. Best thing to do, is that when you get to the step that requires you to install TWRP and then reboot using the reboot command in fastboot, is that you actually pull the batter out after installing TWRP and then reboot into recovery using the hardware keys (Vol Down and Power Button, then let go of Power Button and repress it whilest holding Vol Down but ONLY when the LG logo first appears.).
This is just some general troubleshooting, and not in any particular order. Hopefully it is of some help.

Thank you very much. I appreciate Some observations before I move on. Yes, the screen looks like white noise. In download mode - it only shows download mode shortly in an box, and then goes to white noise again. I mave manages to get in touch with it from Windows in fastboot mode, here it gives me a serial number from LGUS996, definitely not my h990DS? Is that normal?
Another thing, right now Uppercut is teasing me. I think I started it from the zip file, so now it is looking for the program in a temp file that I cannot find. I need to find out how to remove that link in windows to move on with LGUP.

henrylar said:
Thank you very much. I appreciate Some observations before I move on. Yes, the screen looks like white noise. In download mode - it only shows download mode shortly in an box, and then goes to white noise again. I mave manages to get in touch with it from Windows in fastboot mode, here it gives me a serial number from LGUS996, definitely not my h990DS? Is that normal?
Another thing, right now Uppercut is teasing me. I think I started it from the zip file, so now it is looking for the program in a temp file that I cannot find. I need to find out how to remove that link in windows to move on with LGUP.
Click to expand...
Click to collapse
Even though there is white noise in download mode, download mode will still function.
I'm not sure about the serial number thing though. Is it a refurb?
Rather copy Uppercut to its own file outside of the .zip and also disable your antivirus just incase while you are running it. Run it as administrator.
Honestly, I would go into Download mode and user Uppercut to flash a completely stock KDZ. Then try the process over again from the start.
I've had this exact issue and it is totally recoverable.

Thank you so much for the help. Because of that I am now back to a working phone. Have installed the old KDZ file, and now it correctly says that I have a H990DS phone again. You were right about antivirus - even if I thought I had disabled it, I had not, and that made the strange message in uppercut. I will try rooting once more - this time I know how more about what to do if it goes wrong.

I have now re-installed the santa files again, and everything goes fine according to the description until the message about installing step 2, that message never comes to the first cmd window, unfortunately. And I have not (yet) dared to start the step 2 bat from a new cmd window. As I read the description, it should give me a message in the first started cmd window, right?

henrylar said:
I have now re-installed the santa files again, and everything goes fine according to the description until the message about installing step 2, that message never comes to the first cmd window, unfortunately. And I have not (yet) dared to start the step 2 bat from a new cmd window. As I read the description, it should give me a message in the first started cmd window, right?
Click to expand...
Click to collapse
Did you do the terminal thing on the phone?Also have you installed and drivers the right way?you definitely skip something

I think you are right, I can just not understand what. I did the terminal thing, yes and no failure messages of any kind, just no messages at the first cmd screen. . The drivers works fine for everything else, so I cannot imagine any problem there.

I have now tried several times to do the procedure. It all goes very well until the point where there should come a message in the runmefirst command window. No message comes, and for this reason I have not dared to go on. It gives all the right messages on the terminal window on the phone until the point where I have to run step2.bat. I have become pretty good at recovering via LGUP, but do any of you have a hint for me? I have disables antivirus, and I run the windows as administrator?
edit: I succeeded, by simply moving on without any messages from the runmefirst. Worked fine. So now I am rooted Thank you very much JL and Mike for the help.