I was Trying to go back to the stock rom, and the way I understood it was to reloack the Tiatan. So I did. Next Ran RUU with stock Rom and now is stuck in Bootloader. Tried to run Unlocker and has to be connected to Activesync first. Can some one help ??????
When you said bootloader screen. Do you mean the tri-color display (where you see the SPL version)?
If so, you need to get Titan_ExitBl.exe.
Before you launch that file, make sure you disable the USB connection in ActiveSync.
If you are stuck at the logo splash screen, press POWER, CAMERA and RESET buttons together.
It will take you back to the tri-color display (bootloader), where you can update your Radio and OS ROMs.
Yes I am stuck at the tri color screen
It is stuck at the tri color screen, tried to load same rom as was running and it stick at loading with 0%. On my computer it goes to recovery mode. also tried to unlock again, but this is where I have to be connected to Activesync.
If anyone has link to this file I am looking but havent found it yet. searching for these theads can be pretty complex. All the info is all spread out.
Thanks for any help
Titan_ExitBl.exe mirror
Could someone post a thread for Titan_ExitBl.exe? PPC geeks has been down and several people could use this. I don't need it now but would like to have it just in case.
Thanks!
Gubber22 said:
If anyone has link to this file I am looking but havent found it yet. searching for these theads can be pretty complex. All the info is all spread out.
Thanks for any help
Click to expand...
Click to collapse
serfboreds said:
Could someone post a thread for Titan_ExitBl.exe? PPC geeks has been down and several people could use this. I don't need it now but would like to have it just in case.
Thanks!
Click to expand...
Click to collapse
Here, I just uploaded the copy I had.
http://rapidshare.com/files/92944471/titan_exitbl.rar.html
Solved
THANK, THANK YOU.
Now what did Titan-exibl.exe. do?
Would like to know as for future references,
And Thanks all for the fast replies, I had been looking for the answer for some time now and I know with in the last week I had run across post the said they were stuck in simular problems like I was but for the life of me I could not find the answer
Thanks
Allen
00000000000hhhh
Exit Bootloader I would bet..
Feed me peanuts and call me Dumbo
Pasukun said:
Here, I just uploaded the copy I had.
http://rapidshare.com/files/92944471/titan_exitbl.rar.html
Click to expand...
Click to collapse
Thanks for the upload. I appreciate it.
Related
I've been going through many posts and the wiki for the past 4 hours...
My friend bought an Imate JASJAM and hes travelling in five hours..I thought it would be nice of me to update to the latest WWE rom from imates website
I've done this many times before on various imates ive owned in the past, but this time during the upgrade process I get an error and the phone reboots into the bootloader screen
Naturally activesync doesnt recognize the device now...
When I run the update again I go through all the steps, the progress bar shows for a few seconds and I get a "vender id" error and "0% upgrade image completed" shows up on the jasjam...Rebooting gets me back to bootloader with
IPL 1.01
SPL 1.06
Its 5am here and im not getting any sleep until I fix this for him!! I've scoured the net, xda-devs wiki and forum, tried many things, to no avail!
Any help would be greatly appreciated!
Put the phone into bootloader mode THEN run the update... do this by holding the camera button down for a while then hit the power button.
Already tried that countless times same "vender id" error...
Madcap180 said:
Put the phone into bootloader mode THEN run the update... do this by holding the camera button down for a while then hit the power button.
Click to expand...
Click to collapse
To put the Hermes in bootloader, you have to press down both the POWER button and SIDE OK button together and use the stylus at the same time to press the RESET button at the bottom.
http://wiki.xda-developers.com/index.php?pagename=Hermes_BootLoader
Have you tried a hard RESET yet?
URPREY said:
To put the Hermes in bootloader, you have to press down both the POWER button and SIDE OK button together and use the stylus at the same time to press the RESET button at the bottom.
http://wiki.xda-developers.com/index.php?pagename=Hermes_BootLoader
Click to expand...
Click to collapse
Sorry didnt correct madcap myself..But thats exactly what I did originally to get to the bootloader menu..Side OK+power+reset...
Still same vender ID error during update...
Yup tried the hard reset too...Just got back to his bricked jasjam
It's not bricked.. hmn.. sheesh, I dont know too much about Hermes... does he have a SD card?
MicroSD...
hmn... is it in when you are trying to flash? if it is, take it out and try again... I dunno, trying to throw everything at ya .. lol
Even though you don't really deserve this, as you didn't bother to read the directions carefully the first time.. Here's the way to fix it:
See this: http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems#problem4
Once you get back into Windows, the first thing you need to install is HardSPLv7..
Let me know if it works.
LOL hadnt tried that actually...
Didn't work though
jayleb said:
LOL hadnt tried that actually...
Didn't work though
Click to expand...
Click to collapse
WHAT didn't work? I don't read minds...
Did it not boot into Windows? Where did it stop? etc.etc.etc..
I will not ask for clarification again.. I'll get too annoyed with it, and you'll be buying your friend a new phone.
Legolas, no need to be a ****.. The guy tried what you told him to try and it didn't work.. not everyone is as 'smart' as u. give the guy a break.
LegolasTheElf said:
Even though you don't really deserve this, as you didn't bother to read the directions carefully the first time.. Here's the way to fix it:
See this: http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems#problem4
Once you get back into Windows, the first thing you need to install is HardSPLv7..
Let me know if it works.
Click to expand...
Click to collapse
With all due respect, I DID read the directions and I DID try that. That was actually the first thing I tried! And when I followed the directions it got stuck on "Windows Mobile" screen...After which I followed the directions for that (problem 2) and yet again still stuck on windows mobile screen! After trying to update again I was back to bootloader-only mode..
Tried HardSPLv7 but it gave me a connection error multiple times...
LegolasTheElf said:
WHAT didn't work? I don't read minds...
Did it not boot into Windows? Where did it stop? etc.etc.etc..
I will not ask for clarification again.. I'll get too annoyed with it, and you'll be buying your friend a new phone.
Click to expand...
Click to collapse
The "didnt work" was meant for the SD-removal idea...
And dude, seriously...Chill
Madcap180 said:
Legolas, no need to be a ****.. The guy tried what you told him to try and it didn't work.. not everyone is as 'smart' as u. give the guy a break.
Click to expand...
Click to collapse
I am being kind and gentle. I am telling him what I am willing and not willing to do in nice terms. It's true: I really do get annoyed when people aren't being clear.
I am offering *my* Friday evening to help him fix *his* phone. I shouldn't need to be bothered by the lack of communication.
jayleb said:
The "didnt work" was meant for the SD-removal idea...
And dude, seriously...Chill
Click to expand...
Click to collapse
Ok, I'm done.. Have fun..
You'll want to read the WIKI and SEARCH using Google..
Sorry, I just don't want to get annoyed over this--especially since I'm trying to help you out.
jayleb said:
With all due respect, I DID read the directions and I DID try that. That was actually the first thing I tried! And when I followed the directions it got stuck on "Windows Mobile" screen...After which I followed the directions for that (problem 2) and yet again still stuck on windows mobile screen! After trying to update again I was back to bootloader-only mode..
Tried HardSPLv7 but it gave me a connection error multiple times...
Click to expand...
Click to collapse
Do you get a No GSM error?
LegolasTheElf said:
Do you get a No GSM error?
Click to expand...
Click to collapse
Nope......
I have searched and searched these forums and have seen several other people with this problem but no solution. I have also looked through the wiki to no avail, so if someone can give me an answer I would really appreciate it.
I have been able to get into the bootloader screen (the r-g-b white stripes) however there is NO text (no serial, no usb) on the screen and it is not recognized by any pc. Can't get any response from mtty.exe because it can't see the USB port. Have tried on multiple PC's...
Is there another way to resurrect this athena or is it DOA?
Thanks,
-Alex-
Some pics of problem...
Blank bootloader...
Please help!
Did you try reflash by SDcard?
http://wiki.xda-developers.com/index.php?pagename=Athena_SD_Card_Flashing
jas_pik said:
Did you try reflash by SDcard?
http://wiki.xda-developers.com/index.php?pagename=Athena_SD_Card_Flashing
Click to expand...
Click to collapse
Yes...no joy.
Just stays on the tri-color screen with no indication that it is reading the card.
Thanks for the advice though!
Did you try resetting - camera button and reset button on the back (I think...) pressed together.
Forum search will tell you exactly...
ssutherland said:
Did you try resetting - camera button and reset button on the back (I think...) pressed together.
Forum search will tell you exactly...
Click to expand...
Click to collapse
Yes, tried the hard reset (camera + reset) the alternate reset (comm + camera + reset) and even the other reset (volume slider + camera + reset). And yes, I was pushing down firmly on the camera button.
Each reset brings me to the tri-color bootloader screen with NO text. No model number, no OS version, no "USB" / "Serial"....just the red-gree-blue-white stripes.
I have looked extensively at all the forums, used the google search for the site and combed the wiki with no luck.
So do you think it is a lost case?
-Alex-
Hello,
sorry for what's happening to you. Can you tell what led to this situation ? Were you trying to unlock your phone or just flashing a new rom ?
luthor_70 said:
Hello,
sorry for what's happening to you. Can you tell what led to this situation ? Were you trying to unlock your phone or just flashing a new rom ?
Click to expand...
Click to collapse
I was trying to load a new ROM but I assumed that I had to use the OliPro unlock first.
Got to the radio flash and that is where it crapped out.
Now that I have read a little more carefully it looks like I don't need to use the OliPro beyond the first step for the stateside unlocked 7501.
Thanks,
-Alex-
when your on bootloader ? does windows detect a usb generic device ?
Nope. Tried 3 different PCs. Shut down all the activesync processes. No luck. No detection that anything is cabled to the advantage.
I am thinking that it is warranty time.
Damn, I hate this....its just the principle of the thing...
-Alex-
bairda said:
Nope. Tried 3 different PCs. Shut down all the activesync processes. No luck. No detection that anything is cabled to the advantage.
I am thinking that it is warranty time.
Damn, I hate this....its just the principle of the thing...
-Alex-
Click to expand...
Click to collapse
Key rule to remember is to always make sure the Advantage is Fully charged. Try charinging it and reflashing it with the factory rom, located here. http://www.america.htc.com/download/RUU_Athena_HTC_US_2.19.453.4_105_1.47.51.00_Ship.exe. Keep us posted and let us know how it went
have you removed the sim and memory card
just checking basics
try that with a full charge and then enter bootloader and connect to usb
Thanks for all the help! I gave up and warrantied a new unit where I WAS successful in loading a new ROM.
I have learned several valuable lessons in the ROM upgrade process. This was on an advantage 7501, unlocked, USA version. I did the upgrade the process with the OliPro 3.0 unlocker, the PK Rom 3.0 and vista pro (32bit):
- Make sure that you have NOT customized your athena/advantage beyond the basic calibration and cut/paste walkthrough.
-Download ONLY THE MOST RECENT VERSION OF THE OLIPRO UNLOCKER. CHECK TWICE TO MAKE SURE THAT YOU HAVE THE LATEST.
-You MUST let step one of the Unlock complete. With the latest version this will make a bricked Advantage practically impossible.
-Go through step 2 & 3 even if you don't think you need this. It will upgrade the radio and give you peace of mind if you are updating to the PK rom.
-Don't panic if you complete step 1 and goof step 2/3. You can recover. But if you screw up the initial SPL unlock in step1...it is not going to be pretty.
Hope this helps!
Thanks for everyones advice!
-Alex-
Hey guys!
I know this topic really dosn't belong here, but i know that the guys in this forum has much knowlegde so i am trying here!
I have this HTC Hurricane phone, and yes i have asked there but no one seems to be able to help, and then i wanted to flash WM6 on it. For that i needed another SPL, which i got from there and flashed it. The flash it self went fine
But for some reason now, the Hurricane can't do anything at all. I can't turn it on normally i just get a white screen after about 10 seconds after i press the power button. The same happens when i try to get to the bootloader (!), all i get is a white screen after about 10 seconds of nothing. When the device shows me this white screen i also can't get it to connect with my PC! The computer dosn't see it at all, not just active sync, but i do not get that windows xp sound when i plug in a usb device.
So, what can i do? Is this a really good example of a bricked device or what?
I hope you guys will accept that i write here. The Hurricane forum is as good as dead, and i know you guys here for your expertise!
~D
I think JTAG or similar or replacing hardware (DOC Module) might save it, but I don't think there is anyway to flash through USB without the bootloader working...
l3v5y said:
I think JTAG or similar or replacing hardware (DOC Module) might save it, but I don't think there is anyway to flash through USB without the bootloader working...
Click to expand...
Click to collapse
okay that was what i thinking too.. well since i got it very cheap i don't think i will spend any money on such operation.. i guess its quite many money?
Just seen this: http://wiki.xda-developers.com/index.php?pagename=Prophet_Rom_Dump
Note that the prompt only comes up for a few seconds and then it will continue to enter the bootloader.
Click to expand...
Click to collapse
The end of it implies that you can load a ROM from the storage card BEFORE bootloader kicks in.
Not sure if this will work on a Hurricane but it might with some modification and a working device :s
l3v5y said:
Just seen this: http://wiki.xda-developers.com/index.php?pagename=Prophet_Rom_Dump
The end of it implies that you can load a ROM from the storage card BEFORE bootloader kicks in.
Not sure if this will work on a Hurricane but it might with some modification and a working device :s
Click to expand...
Click to collapse
Iam lucky for that couse i actually have another hurricane that works! Thank you i will try this on friday or saturday and write back the status.. I hope you will check back..
Iam glad i can allways count on the people in here!
unbrick it
http://forum.xda-developers.com/showthread.php?t=292667
try the alphazero solution =) !!!!
l3v5y said:
Just seen this: http://wiki.xda-developers.com/index.php?pagename=Prophet_Rom_Dump
The end of it implies that you can load a ROM from the storage card BEFORE bootloader kicks in.
Not sure if this will work on a Hurricane but it might with some modification and a working device :s
Click to expand...
Click to collapse
I have just tried the method. But still i do not get anything, but i white screen. I checked that my ROM dump worked by the other phone. It does ask me if i want to install the rom, but on the bricked one, i do not get anything just that white screen
Guess thats it?
Then I think it is a good example of a bricked phone...
G4 rom dump?
Hi xda-members,
I wanted to know if it's possible to backup and restore a G4 device. On the wiki, it says i need a CID unlocked device.
I think if you hardSPL your device, it should be fine (HardSPL circumvents the CID checking procedure).
l3v5y said:
I think if you hardSPL your device, it should be fine (HardSPL circumvents the CID checking procedure).
Click to expand...
Click to collapse
Ok, on another tread. They said if you got an error while backing up you have a CID locked device. And i already have created a backup. So i think it should be fine.
Hi all,
I have been following xda for a while now, but this is my first post. I'm a complete newbie when it comes to WinMo devices so apologies for sounding stupid.
I'm trying to upgrade a ROM on Atom Life and I'm unsure how to get the bootloader onto an SD card. I've searched for hours and have not found anything besides the wiki on xda, but as I'm not an experienced WinMo user, I need it in a little more detail.
It'd be very grateful if anyone could enlighten me!
Press Record + Reset, leave Reset first => ***MiniSD Detected*** => waiting 100%
Read here:
http://forum.xda-developers.com/showthread.php?t=460145
pls search before you open a new thread just for ask a simple question.
Thanks! I did have a good search around, tried the "record + reset" method but nothing happens, it just reboots. I'll give it another go and have another search around.
Thanks for your time.
Try this, my friend success with it:
Power+Record+Reset, and release reset first.
BesFen said:
Try this, my friend success with it:
Power+Record+Reset, and release reset first.
Click to expand...
Click to collapse
i make this but no resalt ples my frind my devis not work screen is blak not work
emam55 said:
i make this but no resalt ples my frind my devis not work screen is blak not work
Click to expand...
Click to collapse
If it is not work, nothing will happend to your device, why did your device screen black? did you flash it with others ROM before?
I've manage to do it now. It takes a bit of finesse to get it right, but i got there in the end. Flashed a stable 6.1 ROM onto device and it's pretty good.
I'm getting a X1 soon this is only a device to start me off in the world of WM. Plus, it's my mates Atom, so I shouldn't really messing about with it. Lol!
Thanks for all the help!
OK so I might have screwed up my prime. I've done command line stuff and had custom ROMs on everything I own. But I am by no means an expert so please bear with me. I will explain my series of events to the best of my ability.
Starts off with a buggy ROM, i loaded it some time ago and have been dealing with it since. It was cm10 dated sometime in the middle of 2012. Did some searching and found that all the new ROMs were saying something about needing to nvflash to get blobs or something. No prob. Right?
Got everything prepared based off of these instructions:
androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/
Downloaded recovery_tf201.img, fastboot, nvflash, and the drivers. The very first step went ok. It showed moving the .img and then flashing the file. When done the little blue bar went across the screen like it should have.
Here's were it all went bad. I ran the reboot command in fastboot, device rebooted, loaded android. I held power a sec and chose "reboot recovery". I can now get the device to do one of three things:
1. Asus splash screen showing device unlocked when powered normally. That's it.
2. Hold vol down gets asus screen with 4 lines: this device is unlocked, android cardhu-user bootloader 2.10 e, checking for ota recovery, and booting recovery kernal image. Stops there.
3. Volume up gets black screen apx mode
Also tried running battery dead. Still same thing.
Is there any hope for my prime?
Where did I go wrong? Was it by pressing "reboot recovery" from the os?
Arggg please help. Otherwise a guide to replace the main board would be great.
Anything else please ask.
Thanks all,
Nick
Username5.2 said:
OK so I might have screwed up my prime. I've done command line stuff and had custom ROMs on everything I own. But I am by no means an expert so please bear with me. I will explain my series of events to the best of my ability.
Starts off with a buggy ROM, i loaded it some time ago and have been dealing with it since. It was cm10 dated sometime in the middle of 2012. Did some searching and found that all the new ROMs were saying something about needing to nvflash to get blobs or something. No prob. Right?
Got everything prepared based off of these instructions:
androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/
Downloaded recovery_tf201.img, fastboot, nvflash, and the drivers. The very first step went ok. It showed moving the .img and then flashing the file. When done the little blue bar went across the screen like it should have.
Here's were it all went bad. I ran the reboot command in fastboot, device rebooted, loaded android. I held power a sec and chose "reboot recovery". I can now get the device to do one of three things:
1. Asus splash screen showing device unlocked when powered normally. That's it.
2. Hold vol down gets asus screen with 4 lines: this device is unlocked, android cardhu-user bootloader 2.10 e, checking for ota recovery, and booting recovery kernal image. Stops there.
3. Volume up gets black screen apx mode
Also tried running battery dead. Still same thing.
Is there any hope for my prime?
Where did I go wrong? Was it by pressing "reboot recovery" from the os?
Arggg please help. Otherwise a guide to replace the main board would be great.
Anything else please ask.
Thanks all,
Nick
Click to expand...
Click to collapse
2. Hold vol down gets asus screen with 4 lines: this device is unlocked, android cardhu-user bootloader 2.10 e, checking for ota recovery, and booting recovery kernal image. Stops there.
Can you post a screen-shot of this ?
Thx Josh
See if this works.
Username5.2 said:
See if this works.
Click to expand...
Click to collapse
When on that screen does the PC see it as anything in device manager ?
So you do have your nvflash files backed up ?
Thx Josh
No it is not picked up by the PC at all.
And no I had just flashed the custom recovery with fastboot. Had not done anything else. Next step was to run wheelie. Didn't get that far.
Username5.2 said:
No it is not picked up by the PC at all.
And no I had just flashed the custom recovery with fastboot. Had not done anything else. Next step was to run wheelie. Didn't get that far.
Click to expand...
Click to collapse
Well, with no fastboot or adb an no nvflash a motherboard is the only way ...
Sorry for the crappy news ....
Thx Josh
lj50036 said:
Well, with no fastboot or adb an no nvflash a motherboard is the only way ...
Sorry for the crappy news ....
Thx Josh
Click to expand...
Click to collapse
Probably; but: screenshots show, that it is a tf101 (Eee Pad Transformer). I thought that I read in the forums some workaround, because it has no encrypted bootloader. Can be wrong, I'm no expert. Search!
edit:
Found it:
lilstevie said:
There is no concept of locked or unlocked in the tf101 bootloader, in the most general sense it is unlocked as it allows booting of unsigned kernels, and flashing of unsigned blobs.
the leaked key allows lower level communication (bootrom) with the device and can recover from bootloader errors.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=22408864&postcount=3
Josh, thanks. And no problem on the crappy news. I kinda figured this was the case.
OK well after searching eBay and forums, I'm going to just get another prime. $80 for the logic board or $100 for a whole working tablet. So I will let this one sit awaiting a fix or a cheap logic board.
In the mean time can someone tell me where I screwed up?
I hate stock ROMs, and the sound of an "unbrickable tablet" by flashing new recovery is appealing. For that I will be attempting to back up these nvflash files on my new prime but I don't want another expensive paperweight.
So 2 questions.
Where did it all go wrong?
Am I following the set of instructions you all would recommend? I did get the link from this forum.
Thanks again.
das chaos said:
Probably; but: screenshots show, that it is a tf101 (Eee Pad Transformer). I thought that I read in the forums some workaround, because it has no encrypted bootloader. Can be wrong, I'm no expert. Search!
Click to expand...
Click to collapse
It is def. A tf201. All that writing in the screenshot is new except "the device is unlocked" since I flashed the recovery image from the link.
das chaos said:
Probably; but: screenshots show, that it is a tf101 (Eee Pad Transformer). I thought that I read in the forums some workaround, because it has no encrypted bootloader. Can be wrong, I'm no expert. Search!
edit:
Found it:
http://forum.xda-developers.com/showpost.php?p=22408864&postcount=3
Click to expand...
Click to collapse
Its a really old bootloader, that is the way they use to look....
Thx Josh
Username5.2 said:
Josh, thanks. And no problem on the crappy news. I kinda figured this was the case.
OK well after searching eBay and forums, I'm going to just get another prime. $80 for the logic board or $100 for a whole working tablet. So I will let this one sit awaiting a fix or a cheap logic board.
In the mean time can someone tell me where I screwed up?
I hate stock ROMs, and the sound of an "unbrickable tablet" by flashing new recovery is appealing. For that I will be attempting to back up these nvflash files on my new prime but I don't want another expensive paperweight.
So 2 questions.
Where did it all go wrong?
Am I following the set of instructions you all would recommend? I did get the link from this forum.
Thanks again.
Click to expand...
Click to collapse
The bootloader is to old to flash that recovery, that is where you went wrong ....
Thx Josh
Username5.2 said:
OK so I might have screwed up my prime. I've done command line stuff and had custom ROMs on everything I own. But I am by no means an expert so please bear with me. I will explain my series of events to the best of my ability.
Starts off with a buggy ROM, i loaded it some time ago and have been dealing with it since. It was cm10 dated sometime in the middle of 2012. Did some searching and found that all the new ROMs were saying something about needing to nvflash to get blobs or something. No prob. Right?
Got everything prepared based off of these instructions:
androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/
Downloaded recovery_tf201.img, fastboot, nvflash, and the drivers. The very first step went ok. It showed moving the .img and then flashing the file. When done the little blue bar went across the screen like it should have.
Here's were it all went bad. I ran the reboot command in fastboot, device rebooted, loaded android. I held power a sec and chose "reboot recovery". I can now get the device to do one of three things:
1. Asus splash screen showing device unlocked when powered normally. That's it.
2. Hold vol down gets asus screen with 4 lines: this device is unlocked, android cardhu-user bootloader 2.10 e, checking for ota recovery, and booting recovery kernal image. Stops there.
3. Volume up gets black screen apx mode
Also tried running battery dead. Still same thing.
Is there any hope for my prime?
Where did I go wrong? Was it by pressing "reboot recovery" from the os?
Arggg please help. Otherwise a guide to replace the main board would be great.
Anything else please ask.
Thanks all,
Nick
Click to expand...
Click to collapse
Username5.2 - We are sorry to hear about this issue you are having and we are more than happy to assist you. Please email us at [email protected] with your serial number and this post attached for assistance.
If you have any further questions, comments, or concerns please do not hesitate to let us know. We will be more than happy to assist you. Once again, thank you for choosing ASUS products and services.
Thank you,
-In Search of Incredible-
Technical Support Department
http://www.asus.com :: http://service.asus.com/
lj50036 said:
Its a really old bootloader, that is the way they use to look....
Thx Josh
The bootloader is to old to flash that recovery, that is where you went wrong ....
Thx Josh
Click to expand...
Click to collapse
Dang. I followed a link from this forum @
http://forum.xda-developers.com/showthread.php?t=1774352
That led me to this link I posted above:
androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/
So that guide had me download an incorrect file? The files were downloaded right from that page. Check it out.
Username5.2 said:
Dang. I followed a link from this forum @
http://forum.xda-developers.com/showthread.php?t=1774352
That led me to this link I posted above:
androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/
So that guide had me download an incorrect file? The files were downloaded right from that page. Check it out.
Click to expand...
Click to collapse
Your firmware version is 9.4.2.21 which is Android version 4.0.3 'ICE CREAM SANDWICH'
The guide is for 'JELLYBEAN' bootloaders....
That is why flashing said file was the wrong thing to do...
Sorry for the bad new... :crying:
Thx Josh