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
Related
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.
Hey guys i have read hundreds of posts and just want to know if i am missing anything before i count this as a total loss.
I was about to upgrade from Hairy Bean 3.5 to 4.2 I am rooted and unlocked.
First i have done many roms on many devices.
What i did was tried to get into clockwork, 2 times i shutdown and did the vol down and power and then hit vol up and it would say loading recovery kernel but never made it anywhere, so i held power down until it reboot into android, the i did the reboot into recovery from android and it did the same them, next i opened rom manager did the latest clockwork recovery and then rebooted into recovery from rom manager, it shut off and made it back to the Asus logo with the "the device is unlocked" in upper left corner and the Nvidi Tegra in lower right corner. Thats as far as i can get. i have tried the vol down and power again and nothing. it always gets back to that screen.
I can hold both power buttons and connect the usb and computer will see a APX and Unknown device in windows manager, but no drivers, i have tried the universal drivers but they dont work. i also download the asus stuff from asus and nothing helped either.
Any help would be great. Thanks to this great forum and great people as i have used it for years.
soloblazer said:
Hey guys i have read hundreds of posts and just want to know if i am missing anything before i count this as a total loss.
I was about to upgrade from Hairy Bean 3.5 to 4.2 I am rooted and unlocked.
First i have done many roms on many devices.
What i did was tried to get into clockwork, 2 times i shutdown and did the vol down and power and then hit vol up and it would say loading recovery kernel but never made it anywhere, so i held power down until it reboot into android, the i did the reboot into recovery from android and it did the same them, next i opened rom manager did the latest clockwork recovery and then rebooted into recovery from rom manager, it shut off and made it back to the Asus logo with the "the device is unlocked" in upper left corner and the Nvidi Tegra in lower right corner. Thats as far as i can get. i have tried the vol down and power again and nothing. it always gets back to that screen.
I can hold both power buttons and connect the usb and computer will see a APX and Unknown device in windows manager, but no drivers, i have tried the universal drivers but they dont work. i also download the asus stuff from asus and nothing helped either.
Any help would be great. Thanks to this great forum and great people as i have used it for years.
Click to expand...
Click to collapse
You have bricked your device.
You have installed an ics recovery onto the jellybean bootloader. There are warnings everywhere on xda saying not to use cwm on the prime.
If you cannot get back to the bootloader menu where the icons are or you cannot boot back into android it is game over I'm afraid.
flumpster said:
You have bricked your device.
You have installed an ics recovery onto the jellybean bootloader. There are warnings everywhere on xda saying not to use cwm on the prime.
If you cannot get back to the bootloader menu where the icons are or you cannot boot back into android it is game over I'm afraid.
Click to expand...
Click to collapse
So am i stuck? i didnt know it was a ICS recovery? i have used CW on the unit for almost a year and half, and never had a issue until today. Is there somewhere i can send the prime to, to get it fixed? or is it back to ASUS and pay them big bucks to fix it? Is there anything at all i could try before giving up on it?
thanks
soloblazer said:
So am i stuck? i didnt know it was a ICS recovery? i have used CW on the unit for almost a year and half, and never had a issue until today. Is there somewhere i can send the prime to, to get it fixed? or is it back to ASUS and pay them big bucks to fix it? Is there anything at all i could try before giving up on it?
thanks
Click to expand...
Click to collapse
You have not used cwm on that device since that nvidia logo has been bottom right. You updated the bootloader with a ROM at some point to jellybean and that is why you had no recovery there. You then tried putting cwm back on which was not for jellybean and you killed it sorry.
Only hope now Is Asus who could charge you up to 200 dollars to fix it.
Edit. there was a custom cwm at one point made by Wookie for his port of the tf300 ROM to the prime originally. This was never given out for long but the versions you say of hairybean in your first post never existed. We are only on 2.2 now and you are talking about 3.5 and 4.2.
flumpster said:
You have not used cwm on that device since that nvidia logo has been bottom right. You updated the bootloader with a ROM at some point to jellybean and that is why you had no recovery there. You then tried putting cwm back on which was not for jellybean and you killed it sorry.
Only hope now Is Asus who could charge you up to 200 dollars to fix it.
Edit. there was a custom cwm at one point made by Wookie for his port of the tf300 ROM to the prime originally. This was never given out for long but the versions you say of hairybean in your first post never existed. We are only on 2.2 now and you are talking about 3.5 and 4.2.
Click to expand...
Click to collapse
Sorry i was on 1.5 and was going to go to 2.11. Not sure were i got the other numbers. I guess i will try to send it back to ASUS and see what happens if there is nothing else to do.
So is it a software or hardware isssue? I am assuming is software issue and there is just not a way to reflash it?
thanks again for the help.
soloblazer said:
Sorry i was on 1.5 and was going to go to 2.11. Not sure were i got the other numbers. I guess i will try to send it back to ASUS and see what happens if there is nothing else to do.
So is it a software or hardware isssue? I am assuming is software issue and there is just not a way to reflash it?
thanks again for the help.
Click to expand...
Click to collapse
Most times Asus will try to replace the motherboard which is not needed.
If you be straight with them and tell them you messed up the recovery partition when flashing it and that there is nothing wrong with the hardware and could they please reflash it you might get lucky and have less of a bill.
flumpster said:
Most times Asus will try to replace the motherboard which is not needed.
If you be straight with them and tell them you messed up the recovery partition when flashing it and that there is nothing wrong with the hardware and could they please reflash it you might get lucky and have less of a bill.
Click to expand...
Click to collapse
Ok i will see what happens, so is it just a flash they have to do? I am assuming you need a special machine to flash it or is it done from a computer to flash it?
Update:
So i sent my prime back to Asus, after a week they said it was customer induced damaged and was not covered under warranty. They said it need to have the motherboard replaced at a cost of almost $300.
I told them what i did, as someone here told me to, and said i mess up the recovery partition and it just needed to be flashed and didnt need a new motherboard.
This is there response:
There are limitations to what we can do on the service side and the service dept does not have the capability to flash the unit so all we can offer is hardware replacement. Please advise.
Not sure what to do next, am i just out of luck? i can buy another one for less then $300?
Thanks for the help again.
buy a motherboard on eBay - $80 - $100, I just did, I replaced
I just did the same thing to mine; installed CMW on my TF201 latest stock JellyBean. Unlocked and rooted. Only had the thing for about a week. Can you tell me if the "mainboard" they are selling on ebay will work? Also did you find a tutorial to follow with replacing the board - if so where? Thanks - Bill
Yes does anyone know of, or have a video tutorial on how to take these apart and replace, i changed the digitize on my TF101, not a big deal.
as
surenzxx said:
I recently installed CyanogenMod with the Unlock Bootloader for noobs and I noticed the internal SD wasn't mounted. So I tried to flash an ICS ROM to see if it would work but it didn't. I was stuck at the boot screen. I tried restoring an ICS CWM backup and a JB backup but it didn't work. Currently, I have a flashed JB backup with a messed up touchscreen (because of the way I unlocked the boot-loader). It won't boot and I don't know how I can install the stock ROM. I really just want my phone to work at this point. I don't know if there's any way to use the offline method to flash a .kdz since I can't access android. I tried hard resetting, but when I do it starts up Clock Work Mod which I believe happens because of the way I unlocked boot-loader.
I'm trying to use this guide to fix it using SW upgrade. I did find a .bin and .fls which i'm downloading right now.
If anyone could help or give some advice that would be great. I really just want to use my phone, I don't care about flashing a custom ROM right now. As long as my phone works, I'll be happy.
Click to expand...
Click to collapse
Let me know if this works for you! Also you can do the offline fix just as long as you can get into S/W Upgrade mode. But I am curious to see if you can use the bin/fls files tool that you mentioned to get your phone working again.
as
surenzxx said:
Thanks for the reply! I'm planning on trying this method out tomorrow and ,if you don't mind, could you please elaborate on how I can do the offline fix with S/W Upgrade mode? I'll check back on the forum tomorrow!
Click to expand...
Click to collapse
Well just get your phone into S/W Upgrade mode and follow this tutorial. Getting into S/W Upgrade:
1. Get stock ROM here.
2. Turn off your phone
3. Press and hold the vol + button while inserting USB to computer
4. Keep holding the vol + until you see the S/W upgrade mode
5. Flash ROM with tutorial mentioned above.
Good Luck!
as
surenzxx said:
Isn't that just an infobank of all the KDZs? I'm pretty new, but can you flash a kdz with the offline method? To clarify, I was asking how to flash the kdz with the offline method in S/W upgrade mode. So ROMs/KDZs are essentially the same, right?
Edit: I read everything over again and realized what KDZs really are. I'm just wondering now if I could just hard reset in some other way because the LG Update Tool doesn't recognize my phone even though I see all the drivers. It's stuck at 15%.
Edit 2: I tried the method I suggested and it resulted with "Magic number does not concide".
So I'm stuck here with a phone that is stuck in bootloop, and has CWM installed. Can anyone help?
Click to expand...
Click to collapse
alright, this is all from memory but the offline flash didnt work as well for me when stuck in weird bootloops.
Step one-going back to online flash---->
A---
the easiest way i found was to go to C:/windows/system32/drivers/ect/hosts
right click>open with notepad
there should be two lines at the bottom
"127.0.0.1 csmg.lgmobile.com
127.0.0.1 csmgdl.lgmobile.com"
i would cut them out and paste them in a text doc in the same folder for reference later...
but either way you should remove them from the hosts file and save
B----
Make sure your small server is closed! once you minimize it it should go down to your status bar (shttps)
Step two-LGMS---->
make sure you have LG mobile support installed or install it.
open lg mobile support
install needed drivers for your phone
power your phone off/remove the battery
put battery back in
connect it to your computer holding down the volume up button
S/W UPDATE mode should pop up, if it doesn't preform and hardreset and try again til it works (it will)
then in the top right corner there should be a button or two click them both until you see
"restore update" or Update restore or something to that effect
select that
and let it ride man
i got my phone ****ed many times and just had to keep redoing this until it worked. if your bootloader is truely unlocked you can probably go through all that again and get CM10 working, i did but im still working through kinks.....
GOOD LUCK feel free to ask any more Q's about this process if you run into any problems
as
surenzxx said:
Hello! Sorry for the late reply. Before I start, do you mean LG Mobile Support form when I unlocked the boot-loader, if not could you provide a link to it? And by the way, when I tried hard resetting, the phone sent me back to CWM, any ideas why?
I was reading the CM10.2 notes yesterday and I realized there isn't supposed to be an internal SD card showing up when you plug in your phone to your PC. So I did tried fixing what wasn't broke.
Anyway, thanks for the info!
Click to expand...
Click to collapse
that could work, but i just downloaded the LG Mobile Support that i found from a google search. im pretty sure it was just from lg's website
GOOD LUCK
was your phone off before you hit the vol up and home, then clicked power for three-five seconds?
CROSSFREEZE said:
that could work, but i just downloaded the LG Mobile Support that i found from a google search. im pretty sure it was just from lg's website
GOOD LUCK
was your phone off before you hit the vol up and home, then clicked power for three-five seconds?
Click to expand...
Click to collapse
Such a late reply, sorry! I did nothing. Before you replied I flashed CM10.2 but never bothered to boot up my phone. Preparing to connect my phone to my comp, I couldn't start CWM so I figured " I'll just leave my phone plugged in for a few hours." Two hours later, my phone has a blank screen, i'm thinking "This shouldn't be blank? What the hell?." I pressed the power button and was greeted with Cid. I screamed out loud: "**** yeah!"
If people have the same problem as me all I did was: Reflash my my phone with 10.1, stock, 10.1 again, and then 10.2. I did that, only that.
What's funny is that I never checked to see if my phone was working after I flashed CM10.2. :silly:
Can't wait for Kit-Kat. Thank you for keeping up with my post, CROSSFREEZE I appreciate it!
Edit: I might submit a really specific and simplified version of the "Unlock Bootloader for Noobs P769" for the take of contributing.
surenzxx said:
Edit: I might submit a really specific and simplified version of the "Unlock Bootloader for Noobs P769" for the take of contributing.
Click to expand...
Click to collapse
love that idea, theres al;ot of reading i skimmed it and watched the video and after skippiing half the steps it worked for me but there was alot of messed up stuff to fix
Dear All,
Before I start, please forgive the repetition, as I know this issue comes up a lot but I've searched all over and can't find a solution for my circumstance. If there's a post I've missed, please direct me there...:fingers-crossed:
I recently received a Lumia 800 with a Qualcomm bootloader, sim-locked to a UK network. The first thing I did was use NSSPro to remove the simlock, which was successful, but I also wanted to debrand and try a custom ROM..
I read round the issue a fair bit and was going to go down the Linux 'dd' route when I spotted the Windows flashing utilties. Ever keen for an easy life, I went ahead and flashed my handset with FunkyRom, apparently making two fatal errors; not backing up my partitions in Linux and not using Linux to do the flash. Laziness stopped me backing up and I'm aware I deserve what I get for that, but the warnings about flashing in Windows were a little harder to spot and I only found those after the event.
ANYWAY....
Unsurpisingly it turns out, the Windows flash bricked the 'phone. I can get it into Qualcomm bootloader mode in Windows and Linux, I can read the partition map (attached), flash it in NSSPro, 'dd' it in Linux and flash it with the Windows tools, but it won't boot past the Nokia logo. After initial flashing the battery went haywire as well and wouldn't hold it's charge much beyond ten minutes. The battery is fine, I have swapped it out for a new one and it works fine in another 'phone, so I'm not sure what that was about. One other thing to note is I've never been able to hard reset it after flashing, the combination of button presses does nothing, no matter how long I hold them down, all that happens is the 'phone reboots if I release the power button.
I've tried many reflashes, replacing the third partition etc but I think I'm just laying s**t on top of s**t now and would appreciate some guidance. I don't think it's terminally bricked because I can still read/write from/to it in Linux, NSSPro etc, but I'm normally a Nokia N9 man, so this partition structure is unknown, I don't know what I'm looking for.
Any help much appreciated, with the note that I realise I ballsed up not making a backup, so you can skip telling me I'm a fool, I'm getting that enough from the missus..!
Sorry for the looong first post,
Squid
Not sure about fixing it as I have the 710, but Im pretty sure you could RMA to the place you bought it, and they would be too lazy to do full checks on what you did to it, send it back to Nokia and send you a replacement
I've bricked tablets and GPUs and phones and RMA'd, and not once have they ever questioned what I did
One phone I RMA'd I'd flashed a German ROM to and everything was stuck in German, UK company just walked me through factory resetting it on the phone, didn't work obviously, so they gave me a new one
Just an idea if you can't fix it yourself
Other options would be taking it to a local phone repair store who have tools to flash bricked phones, there have been a few here who didn't read the "DO NOT FORMAT" posts, and hit the format button bricking their phones, took it to a repair store who flashed it back to a working state for them
Good luck
Hi and thanks for the reply.
I'll be honest, I'm a Nokia N9 man myself, I was hoping to unlock this one as a spare's spare (it looks and feels familiar), so I'm unlikely to be taking it for repair if I can't get it going myself, but it's interesting to hear you've never been questioned about any DIY work you may have done, I've always thought they'd be hot on that...?
I am holding out for a technical hint or two on something I may have borked during the flash itself, and whether that might be recoverable, after all I can get to the bootloader, just whatever I flash on top (FunkyRom, Rainbow Mod etc) just don't load. Also, why doesn't hard reset work on this 'phone? I have questions but I've run out of brains for answers.
Are there generic full partition dumps available to dd in Linux that would be like a vanilla image? Are there specific partitions that may be the problem? If it gets to the Nokia logo but no further, how far in the booting process has it come?
Squid
Hi John,
Maybe you can try this: http://forum.xda-developers.com/showpost.php?p=47076870&postcount=2
Otherwise I can download an original rom for you, maybe you can flash that with nss, just let me/us know.
Greetz,
Rataplan said:
Hi John,
Maybe you can try this: http://forum.xda-developers.com/showpost.php?p=47076870&postcount=2
Otherwise I can download an original rom for you, maybe you can flash that with nss, just let me/us know.
Greetz,
Click to expand...
Click to collapse
Brilliant, I'll take a look at the NSU first, thanks!
Rataplan,
No joy with the NSU Retail I'm afraid. Do you think you could let me have an original ROM please as mentioned? After that, I guess it goes to the bin..
John
Ok, gonna download and upload this evening, keep you informed.
Greetz,
Rataplan said:
Ok, gonna download and upload this evening, keep you informed.
Greetz,
Click to expand...
Click to collapse
Great, thanks!
john smash said:
Great, thanks!
Click to expand...
Click to collapse
Ok John, you can download the rom here: https://dl.dropboxusercontent.com/u/9417919/rm-801.7z , the rom is based on RM801_059L8M3_1750.0805.8773.12220, I also suggest to read this: http://forum.xda-developers.com/showthread.php?t=1457341 and
this: http://forum.dailymobile.net/index.php?topic=77419.0
Greetz,
Many thanks, I'll try it later. I have actually tried those threads you linked previously but I'll take another look.
Cheers,
John
Hey there Rataplan,
No dice I'm afraid. I can't get the phone connected in anything other than Qualcomm mode, so I can't use NCS to flash. I can use NSSPro to flash a file with .nb extension but not the files you uploaded. NSU Retail asks me to connect in Qualcomm mode then doesn't recognise the phone once I do that.
I just don't understand how if I can get to the Qualcomm bootloader, why flashing RainbowMod or FunkyRom/FunkyRom lite doesn't work, do you have any suggestions? Is there a way to check if any of my partitions are corrupted?
JS
EDIT - Just read this post - http://forum.xda-developers.com/showpost.php?p=29583840&postcount=2 and renamed the boot.img of the ROM you uploaded. Now my 'phone shows a 'Three UK' splash screen, then the nokia logo, but still doesn't load. Is there a way to know what stage of the boot the 'phone is getting to before it hangs?
Ha! Got it!
Using the extract and rename method I flashed the 11412 firmware (oldest one in Navifirm) for product code 059M062 and bingo! It boots and there's no simlock...
Thanks for all your help Rataplan, 'phone revived!
:victory:
Great, I know it had to work, that's why I gave you an copy of an older rom, I'm glad you solved it yourself , take care next time.
Greetz,
Rataplan said:
Great, I know it had to work, that's why I gave you an copy of an older rom, I'm glad you solved it yourself , take care next time.
Greetz,
Click to expand...
Click to collapse
Will do..
I've changed my product code with NSSPro but if I try to flash any later ROMS then it goes back to being borked. I can always recover to this ROM now but I'm wondering why I can't upgrade?
john smash said:
Will do..
I've changed my product code with NSSPro but if I try to flash any later ROMS then it goes back to being borked. I can always recover to this ROM now but I'm wondering why I can't upgrade?
Click to expand...
Click to collapse
I have to take a look at your product code, did you try Nokia Update Retrailer.
The original product code was 059L7C6, I've successfully flashed it with a ROM for product code 059M062 and confusingly, I've written the product code 059L7C2 with NSSPro..
Does it bork it if you try to update it through Zune ?
*Detection* said:
Does it bork it if you try to update it through Zune ?
Click to expand...
Click to collapse
Hey,
Just plugged it into Zune now and it's offering me 7.10.7740.16. Question: Does using Zune overwrite the Qualcomm bootloader? Once that's gone I know I can't get any custom ROMS loaded on here..
Thanks,
JS
For those who may be interested:
I've got a working Lumia now, flashed with a 12220 firmware on a UK product code but that's it, I can't get anything more up to date on there. Every time I flash something more recent I get stuck at the Nokia screen. In addition, I get the same result with any of the custom ROMs, they just won't load. Could my hardware version be preventing the upgrade? Any ideas..?
JS
john smash said:
Hey,
Just plugged it into Zune now and it's offering me 7.10.7740.16. Question: Does using Zune overwrite the Qualcomm bootloader? Once that's gone I know I can't get any custom ROMS loaded on here..
Thanks,
JS
Click to expand...
Click to collapse
No the update doesn't overwrite the bootloader, I flashed the unlocked bootloader to mine and have flashed custom & stock & custom & stock in that order and everything stayed unlocked
So I got an Asus Transformer Prime from a friend of my who had botched this thing something awful!
What I know of it so far:
-- He used Asus unlock tool to unlock it
-- He rooted it and added TWRP (not sure which version)
-- He changed the file system to f2fs and flashed CROMBI-KK to it
If you power on the tablet, it goes straight to TWRP screen and freezes. - no functionality at all. I can not at this time get it to go to fastboot.
I was able to get it to boot into APX mode (you know the one with the black screen and you'd think it turned off unless you plug it in and notice in device manage that it isn't?)
I can not communicate with the tablet via cmd. Not sure if I'm using the correct commands.
If I restart the tablet, it boots with the ASUS screen and says the device is unlocked and then goes straight into TWRP and freezes.
I'm working on it with Win7 64-bit so any and all advice or help you and send my way would be much appreciated.
If you help me fix it...well, then! Stop by KCMO sometime and I'll buy you a pint or four! Thanks in advance!
UPDATE!!!
Just to Update, still stuck with the same issue. Nothing new I have found but then, I haven't had time to really work on it. Please let me know if you've run into this problem too and how I could fix it.
Thank everyone!
st.pickle said:
Just to Update, still stuck with the same issue. Nothing new I have found but then, I haven't had time to really work on it. Please let me know if you've run into this problem too and how I could fix it.
Thank everyone!
Click to expand...
Click to collapse
I hope you have more luck than I do. Mine was given to me by my bro and I dont know really much about this tablet since its not mine. It's a huge learning curve when its not your own device. I cant get it to boot into download mode or any of the recovery options. But again, I am somewhat of a noob in terms of this tablet. What's APX mode?
squall458 said:
I hope you have more luck than I do. Mine was given to me by my bro and I dont know really much about this tablet since its not mine. It's a huge learning curve when its not your own device. I cant get it to boot into download mode or any of the recovery options. But again, I am somewhat of a noob in terms of this tablet. What's APX mode?
Click to expand...
Click to collapse
here is a link on xda that should hel pexplain APX. Good Luck!
http://forum.xda-developers.com/wiki/APX_mode