ROM update freezez on either 45% or 53% - MDA, XDA, 1010 Software Upgrading

I am trying to flash my XDA with the Radio_Stack_Upgrade_v421.exe, the flashing freezez on either 45% complete, or 53% complete. After being frozen for several minutes the XDA just announces "Flashing failed! press OK to restart you device", if I do press OK it just boots and the same thing happens all over again.
the XDA is connected to a Compaq laptop running WinXP. With no other programs running besides active sync (as requested in the installation guide)
After the Radio Stack Upgrade (if I ever get this to work), I would be installing the much larger Radio_Unit_Upgrade_v31703.exe, so I might in for even more trouble than this...
Any help from you guys? what am I obivously doing wrong here?

More trouble:
Since the ROM flashing didn't go through I deleted the files autorunning the flash from the XDAs startup directory: now it boots as normal without tyring to do the ROM flash after each boot.
I noticed that I was supposed to flash the radio unit upgrade first, and after that the radio stack upgrade (not the other way around as I was tyring).. However now I cannot do the radio unit flash either: since a strange new feature has appeared. The XDA device does not recognize connecting the power cord at all. The radio unit flash requires that the AC power is attached: and even thou it IS attached, the damn machine doesnt recognize that and refuses to start the flashing.
Iv trying reseting the XDA several times by pressing that hidden button on the left-down side of the machine. Doesn't help: in all occasions, connected to the PC or not, It fails to recognize the AC connection. It also gives zero informaiton on battery life: just says that it is "unknown"
What I can I do to restore the XDA to a factory default state? or make it recognize the AC power connection?
Any help apprechiated, thanks!

Tried hard reset now the XDA won't boot this time. its gets to the opening screen where reads 3.12 and a tad later the letters G and U appear. After a rather long wait, about 2 minutes or so, it says "beep" and a plain white pocket windows style window appears - after which the XDA seems to be completely frozen. When I place it in the cradle, the PC cannot connect to it, and just nothing at all happens. How do I recover from this?
Sorry for the multiple posts..

I too have the same problem. After trying the new ROM upgrade the unit hangs. Nothing is possible. Only a white screen flashes after hard reset. How to fix this to come to it's original state?. Now when booting can see only 3.17.03 and G and R is blank. Then the white screen keeps on flashing. Pls. help.
Thanks
Palitha

Is the screen totally white or are there blocks in the screen. This sort of problem has been linked to an stk.lnk in the startup folder. Delete it see what happens.

valheru said:
Is the screen totally white or are there blocks in the screen. This sort of problem has been linked to an stk.lnk in the startup folder. Delete it see what happens.
Click to expand...
Click to collapse
The screen is not totally white: it has a blue bar on top of the screen. Also when this screen first appears there is a brief loud "beep" sound. After which it frozez.
How do you propose I delete the file? Since the device is unconnectable through USB, and does not boot into normal mode, what can I do?
I have already tried a hard reset with no luck: it just seems to get the XDA to the state its already in (no change in situation)

SNAFU
Still the same "SNAFU" situation here. Any toughts before I use the XDA device to warm up my fire place?

Related

Red Led of Death

Hi,
After upgrading to new ROM I performed hard reset on my vx6900. At the last screen during hard reset pocedure I press Send button as requested and it was a last time I ever saw something on my screen. Device is not waking up anymore when I plug power it always the red led is switching on (with or withoout batery). I took a 100% charged batery from another device, but it's not helping. I'm out of options I think I tried evrething: Hard reset combination, bootloader combination, keep it on charge for hours, then without battery for hours - no luck.
Could anybody help me?
fofan said:
Hi,
After upgrading to new ROM I performed hard reset on my vx6900. At the last screen during hard reset pocedure I press Send button as requested and it was a last time I ever saw something on my screen. Device is not waking up anymore when I plug power it always the red led is switching on (with or withoout batery). I took a 100% charged batery from another device, but it's not helping. I'm out of options I think I tried evrething: Hard reset combination, bootloader combination, keep it on charge for hours, then without battery for hours - no luck.
Could anybody help me?
Click to expand...
Click to collapse
Had you been switching to Android (NAND Flash)?
No, I performed hard reset after succefully loading NFSFAN's WM6.5 1.00 FINAL ROM.
Before NFSFAN's WM6.5 1.00 I loaded Vogue_unlocker_MFG-2.31 (initial attempt to load NFSFAN's WM6.5 without unlocker didn't work).
Is there any way to revive it after Red Led?
If you cannot put your device in bootloader, then you are toast
How are you trying to put the device in bootloader?
I guess it dead then Not waking up into boot mode after Pwr-snd-reset.
Also I tried any combination of buttons with reset. It is not waking up. And it is strange to me because I was just performing hard reset and following the screen prompt. Now I don't see any activities except this stupid red led. I though there is some sort of reincarnation procedure some "hard hard" reset?
To enter the Boot Loader mode....
Press and hold the following buttons:
Power (on top left of device) + Camera (on right of device, near the bottom) + Reset (small hole on bottom right of device, just right of the USB port. You can press this with the tip of your device's stylus).
It can be tricky to press all 3 of thes buttons at the same time, and you will probably need to use both hands.
You should see an odd rainbow on screen, indicating that you are in the Boot Loader mode. The device does not need to be connected to a computer of charger in order to enter Boot Loader mode.
If this does not work you may actually have the 1st bricked vogue I've ever seen...
(It didn't get wet, did it...?)
antinerd said:
Press and hold the following buttons:
Power (on top left of device) + Camera (on right of device, near the bottom) + Reset (small hole on bottom right of device, just right of the USB port. You can press this with the tip of your device's stylus).
It can be tricky to press all 3 of thes buttons at the same time, and you will probably need to use both hands.
You should see an odd rainbow on screen, indicating that you are in the Boot Loader mode. The device does not need to be connected to a computer of charger in order to enter Boot Loader mode.
If this does not work you may actually have the 1st bricked vogue I've ever seen...
(It didn't get wet, did it...?)
Click to expand...
Click to collapse
That is exactly why I was asking. What you are doing with power +vol keys is for the TP and not for the Vogue.
I used boot loader sequence already (pwr + camera + reset) between all other sequences it doesn't help, device is no show any vital signs the only thing that works is a red led.
I also noticed that when I power it up without batery and then insert the battery the red led is going away. Then Red led is blinking every time I press the reset.
It sounds that you may have fried your NAND...
Just to be sure, you didn't bump it, throw it, or sent it for a swim... have you?
Have you tried this?
http://forum.xda-developers.com/showthread.php?t=694798
May not work, but it is worth a shot.
Guys, when you get a red LED, it means your battery is fried. It's near summer so are you sure you didn't charge it in the car or something? Replace your battery and you'll be fine.
atoz350 said:
Guys, when you get a red LED, it means your battery is fried. It's near summer so are you sure you didn't charge it in the car or something? Replace your battery and you'll be fine.
Click to expand...
Click to collapse
The OP already stated that he tried a 100% charged battery from another Vogue and nothing.
No, I didn't do anything brutal to that device, as i said it was absolutely responsive when I started the hard reset sequence and it had not history of stuck buttons, anyways I'm going to doublecheck all buttons to make sure nothing stuck and preventing it from boot (looks like it my last hope )
If that doesn't work. open it up and clean the dust and debris out of there with a can of spray air. There might be a spec of dust that is causing a short circuit. That actually happened to me during the 80386 days when I was putting together a computer and it wouldn't get past the post screen. Turned out, there was a spec of dust lying across 2 pins on the CPU.
I keep my phone in my pocket and every now and again I take the back cover off and there is a ton of dust in there.
Good luck.
So? Any news? Could you revive it?
Use this it will be fine as i have used it once!!!
Edited *This will help those that are stuck at the HTC welcome screen and cannot get past it to load IMCokeMan's Unlocker.**
Edit by ImCoKeMaN: If you are stuck in bootloader (3 color screen) use titanexitbl or mtty (set 16 0 then task first and try these steps only if that doesn't work.
Apparently you can not use SDHC cards with this method, please use the 512mb card that came with your phone.
I have successfully unbricked my phone due to updating the Alltel rom to a non Alltel Vogue, before IMCokeman had released his unlocker an also have downgraded to the previous SPL version. I will shortly update this post with the How to instructions. I just need to retrace my steps.
I would first like to thank IMCokeMan for his help and unlocker.
I currently have a Sprint Vogue but I assume this will work for all versions
For those that had loaded the Alltel rom without the unlocker and have bricked there phone try this procedure to unbrick your phone.
1. First download IMCokeMaN's 2.31 Unlocker. http://rapidshare.com/files/11019074...r_MFG_2.31.exe
2. Extract IMCokeMan's unlocker
Previous SPL version was 2.31 current SPL version is 0.36
Edit by ImCoKeMaN:
Note: Steps 3, 4 and 5 should not be necessary, but step 6 is critical that it is a signed rom from your carrier
3. Navigate to the extracted folder and within the folder you will find the following file called VOGUIMAG2.nbh and rename it to VOGUIMG.nbh
4. Copy the file to a fat32 memory card, and insert it back into your phone, and place it into bootloader mode.
5. The phone should display Loading... let it sit there for a minute or so. It will not go past this screen, now reboot the phone.
6. Extract your official rom (Must be a signed EXE from your carrier, check here)
7. Navigate to the extracted folder and within the folder you will find the following file called ruu_signed.nbh and rename it to VOGUIMG.nbh
8. Copy the file to your memory card (less than 2gb and formated fat32) and insert it back into the phone and place it back into bootloader mode, and install the your Carrier's Official ROM.
patelaquib said:
Edited *This will help those that are stuck at the HTC welcome screen and cannot get past it to load IMCokeMan's Unlocker.**
Edit by ImCoKeMaN: If you are stuck in bootloader (3 color screen) use titanexitbl or mtty (set 16 0 then task first and try these steps only if that doesn't work.
Apparently you can not use SDHC cards with this method, please use the 512mb card that came with your phone.
I have successfully unbricked my phone due to updating the Alltel rom to a non Alltel Vogue, before IMCokeman had released his unlocker an also have downgraded to the previous SPL version. I will shortly update this post with the How to instructions. I just need to retrace my steps.
I would first like to thank IMCokeMan for his help and unlocker.
I currently have a Sprint Vogue but I assume this will work for all versions
For those that had loaded the Alltel rom without the unlocker and have bricked there phone try this procedure to unbrick your phone.
1. First download IMCokeMaN's 2.31 Unlocker. http://rapidshare.com/files/11019074...r_MFG_2.31.exe
2. Extract IMCokeMan's unlocker
Previous SPL version was 2.31 current SPL version is 0.36
Edit by ImCoKeMaN:
Note: Steps 3, 4 and 5 should not be necessary, but step 6 is critical that it is a signed rom from your carrier
3. Navigate to the extracted folder and within the folder you will find the following file called VOGUIMAG2.nbh and rename it to VOGUIMG.nbh
4. Copy the file to a fat32 memory card, and insert it back into your phone, and place it into bootloader mode.
5. The phone should display Loading... let it sit there for a minute or so. It will not go past this screen, now reboot the phone.
6. Extract your official rom (Must be a signed EXE from your carrier, check here)
7. Navigate to the extracted folder and within the folder you will find the following file called ruu_signed.nbh and rename it to VOGUIMG.nbh
8. Copy the file to your memory card (less than 2gb and formated fat32) and insert it back into the phone and place it back into bootloader mode, and install the your Carrier's Official ROM.
Click to expand...
Click to collapse
The OP is not stuck in bootloader. His device simply doesn't turn on.
Unfortunatelly nothing helps. I opened it up, even unscrewed completely and sprayed with dust remover. It's the same.
What I noticed is when I plug device to power without battery the red led goes on (it's normal behavior for all devices). Then I insert the battery while device is still plugged in (in my case to Laptop's USB). The red led goes away (also normal behavior for devices). Then I can hear USB connect sound from laptop and in few seccond message: "USB device not recognized".
Click on reset button causes device's Red Led to blink and I can hear USB re-connect sound from Laptop again. Any other buttons or combination of buttons on device don't do any diffrence.
You are only trying to charge via USB? You should have said this earlier. Get a charger (output of 1 A). I had the same thing happen to a Wizard once and I used a high output charger and it worked again (battery was brand new too).
USB cable was one of my desperate try-outs, before I was keeping it on stock HTC (1A) charger for days, with empty and full battery in and no luck

[Q] First blue screen, now boot loop.

Hello XDA-devs forums,
I'm having an issue since yesterday.
I have rooted my Huawei Ideos X5, and it ran fine for a day or so.
However, when my battery ran out it shut down into a completely blue screen.
When I tried booting it again, this just showed me a blue screen as well.
Now, I fixed this issue by connecting the phone to my PC after booting it with the Vol+ and Vol- pressed.
(So you get the pink/purple screen)
However, when I opened the phone on my PC, all I saw was a "239 MB" "empty" space, and it should have ~2GB..
I placed a backup copy I saved of my "image" folder in that 239 MB storage, and it booted.
However, today I hooked it up to my PC again to see if it magically changed..
And I couldn't access the 239 MB space anymore.
When I tried fixing the issue with a reboot of the phone, that just caused it to get stuck in a booting loop.
So now I'm stuck with a phone that keeps trying to boot itself,
and I can't access it on my windows PC.
I can, however, access 4 different folders of the phone on my linux notebook.
Now, my question is: can someone with a good understanding of problems like these please help me out?
I'm getting kind of fed up with it, as I've only got the phone for 2 days now.
Thank you in advance, and thank you for taking the time to read this.
Have you tried removing the battery for 5 minutes and then putting it back in?
After this, what happens when you press VOL+ and Power?
How about if you press VOL+, VOL- and Power, without the USB cable?
Hello Katu, thank you for posting.
Regarding your questions:
Yes, I have tried to take out the battery for 5+ minutes- it didn't change anything to the situation unfortunately..
If I press VOL+ and Power at the same time, the device boots into recovery mode.
In this I have tried to format the device in order to reset it to factory defaults, but this did not help either.
When I press VOL+, VOL- and Power, the phone boots into the pink/purple screen.
Can you try a custom recovery and a custom rom? I want to see if your onboard flash is borked.
u8800,cm7,[email protected]
I had the same when my phone got f*ucked up. Put the image folder, than download official rom, like b138 and install it. then check your imei. There is a change that it will be 0.
PlanDreaM said:
Can you try a custom recovery and a custom rom? I want to see if your onboard flash is borked.
u8800,cm7,[email protected]
Click to expand...
Click to collapse
Well, I used an original ROM:
U8800 V100R001C00B136(Overseas General version)
And that resulted in the boot.img being corrupted, so I can't even overwrite that anymore.
Also, this is what I see when I hit VOL+, VOL- and Power at the same time to boot into safe mode, and connect it to my PC.
img69 [dot] imageshack [dot] us/img69/244/10101191548pm.png
julle131 said:
I had the same when my phone got f*ucked up. Put the image folder, than download official rom, like b138 and install it. then check your imei. There is a change that it will be 0.
Click to expand...
Click to collapse
I installed the official B136 rom, and after it rebooted, it would just hang on a black screen.
(it used to show the IDEOS or Android logo when it booted)
Hmm mine came with this Rom
U8800 V100R001C00B135SP01 ( general )
Looking at your name you're from the Netherlands ( so am I )
where did you get this 136 version from ?
I would try to put this one on it
You have to put the 'dload' folder into the root of your SD Card,
then boot into boot-loader, after that it'll automatically flash back to the stock Rom.
1 Format SD card
2 On the SD card, create "dload" folder
3 Put the unzipped Rom into "dload" folder
4 Then boot to bootloader (pink screen)
Yes, mine came with that version as well.
However, I couldn't find it anymore and thus downloaded the version I said earlier.
Also, I did everything as you described, except step 4.
You have to boot to recovery instead of bootloader. (VOL+ and Power)
Anyways, I managed to get ClockworkMod's recovery.img on my phone,
and from there on install a custom ROM on the phone, which magically got it working again - even though it didn't work earlier.
Thank you for reading my thread and taking the time to reply to it.
My issue has been resolved.
just for the record, flashing a stock rom is different from flashing a custom rom..
the 4 steps described by Gman2oo6 is the correct way to flash a stock rom (and it is written clearly in the document that is in the stock rom zip file)
[edit]
step (1) is not a necessary step though..
Yeah, I noticed that.
What I did was format my SDcard with FAT32,
and put a custom rom (update.zip) on the SDcard.
I then booted ClockworksMod Recovery and installed the custom rom from the SDcard.
When I tried installing the stock rom, I just followed the PDF file's instructions that came with the stock rom.
hey i udated to GB 2.3.4 (official)and i didnt like the it cuz the wifif ddnt work and the bluetooth also the DATA so itryed to downgrade to 2.2.2 original official and it did the 2/2 steps intalled and when it restarted it did not want to turn on all that happened was it vibrated and thats all so i left it on like that and when the battery died i plugged it in to the AC and the LED turned on red and the touch kkeys also but not the screen so i really NEED help!
Try to turn it on with lead connected but no battery and see if you can start it.
My battery also went dead flat this morning and I couldn't get it started at all till I tried this. Once I got it started the only thing I could do was quickly pop in the batery and let it charge. Just leave off the cover till you get it going.
I have to add that I did not have the problem of a failed update to deal with but it may at least get you started
i tryed it
nope nothin good happened all that happens is a blank screen with nothin on ,LED is off and the touch keys are off. it justz vibrates and when i put the battery it turn the LED on to red and the touch keys turn on but then like 5 min later the LED and keys turn off
astewart said:
Try to turn it on with lead connected but no battery and see if you can start it.
My battery also went dead flat this morning and I couldn't get it started at all till I tried this. Once I got it started the only thing I could do was quickly pop in the batery and let it charge. Just leave off the cover till you get it going.
I have to add that I did not have the problem of a failed update to deal with but it may at least get you started
Click to expand...
Click to collapse
ok heres what i did i wanted to upgrade my phone to the newest version GB 2.3.4.So what i did was download the update and i followed the installation steps i successfully updated to Gb 2.3.4. so like i was checking how it look and the new feature but when i wanted to go on the android market i went to setting and turn on the wifi and it said Error and then i tried the Bluetooth and it said Error also so then i put my SIMs card in and i was like imma use DATA then and when i restarted my phone it had service but no HSPA+ or Edge or GPRS so like i just hatted my phone from their so then i was trying to root it but iddnt know how to do that so like i read this website and i got the UPDATE.APP or 2.2.2 AT&T did the same steps of the installation of BG 2.3.4 and it went to the process and 1/2 stepp good it passed and then 2/2 also passed it installed it and when it said Successively Installed it said Restarting and the scrren turn of and it vibrated and thats all that happened and i left it like that for the whole days and nothing happened
Do u got any idea?
When i connect it to my laptop it says installing drivers .then its says sucesfully installed drivers ready to use. so then i got to Device Manger and i check what has been installed and their it said USB Human interface device and HID-compliant device WHAT DOES THAT MEAN??
Not sure about the HID (human interface device) probably just the way windows sees the device for interfacing with it. With regards to the not booting I have read a lot of people saying that you need to factory reset and clear cache after the upgrade/downgrade. With the phone off, turn it on by long pressing volume+ and power on button till you get the blue recovery screen and from there you can reset factory/ data and also clear the cache. from what I see this should clear up the problem and start up. Please read this thread, it may help you somehow..... http://forum.xda-developers.com/showthread.php?t=1420728
Hope this helps a little
U mean Boot recovery and imma try it and thanks ill check it out
Sent from my MB300 using XDA App
all that i know is that if u customized your partition, it'll bootloop,
so go back to stock-partition ^^
How do I do that got like the steps or video?
Sent from my MB300 using XDA App
when i downgraded to 2.2.2 i installed this V100R001C00B138SP04CUSTC185D002
http://forum.xda-developers.com/showthread.php?t=1251250 got it from that link
Looks like you are not having much luck. Did you try to factory reset?
astewart said:
Looks like you are not having much luck. Did you try to factory reset?
Click to expand...
Click to collapse
well how do i do that do i need to got to the purple/pink screen or bot recovery cuz i cannot access that my phone doesn't do anything pretty much

Defy-semi bricked

Was running an ICS rom for about 2-3 weeks. Can't remember which 1 but I do remember that it was a Defy+ (port ?, 4.0.3). It changed my phone description to (MB526). Ran pretty good but would randomly freeze and not move. Decided to re-flash. Went to clockwork to run a backup, not sure/don't remember what I did after that as it's been a week since I'm trying to get Defy back up and running. got stuck in a boot loop. Now it's not even looping, just freezes on google splash screen.
My problem: I can get into boot loader fine but phone is not recognized/won't connect with RSD Lite. Tried a couple different versions including v4.9. If I could connect I'd just re-flash an sbf. Drivers are fine. I have other Motorola Apps such as Flash&Backup3, P2K, Motorola Phone Tools for a couple other phones I have so I should have any drivers I need, Also phone was flashed prior to this with these drivers installed.
I cannot get into fastboot, stock or CWM recovery. I did notice "all" of the zip files on the SD card were gone. Roms, Apps, etc. Everything else was still there. When phone is off and I plug into the computer, the white led lights for a bit, then the blue, then the google splash screen and that's it. Won't move after that. So I'm guessing my recovery is still there but I can't access it. Tried connecting with/without SD in the phone. No luck.
I cannot connect with ADB either. Says no device found.
I've downloaded and re installed everything I could but still no luck.
I am at a loss as to what to try next. This is not my 1st flash so I like to think I know what I'm doing. Flashed 11 different phones, 5 different OS's. So I'm not a noob. But now I need some help from you guys/gals.
Anyone with any suggestions would be welcome.
From my limited knowledge I understand that if you can get into the boot loader your not bricked ?
So what do I do next ? HELP. Questions ? Ask away. This is starting to piss me off.
Bootloader 09.10
Battery OK
OK to Program
Connect USB Data Cable
After pluging in usb, phones says:
Transfer Mode: USB
Did all this on Vista Desktop. Should I try my Windows 7 Ultimite laptop ?
Mods: apologize if it's been covered but I didn't see my problem in the threads, not that I looked at all of them.
Thanks
crz6662 said:
When phone is off and I plug into the computer, the white led lights for a bit, then the blue, then the google splash screen and that's it.
Click to expand...
Click to collapse
When the indicator is lit in blue, press the volume down. It should boot recovery.
crz6662 said:
Should I try my Windows 7 Ultimite laptop ?
Click to expand...
Click to collapse
Yes.
Also you could try to connect your phone to another USB port.
Try that when I get home from work. Let you know if either worked.
Ant-ON said:
When the indicator is lit in blue, press the volume down. It should boot recovery.
Solved. Ya know, I thought I there was something I was missing. That's what happens when you own 9 different phones and play with them all. I had just finished flashing an old Motorola RAZR V3re.
Appreciate the heads up.
Up and running in 5 minutes. Thanks
Click to expand...
Click to collapse

Secure booting Error!

Hello, about a weekago I've installed dorimanx kernel for my D802 and today I realized that it made my 3g connection unstable
I decided to flash back to the stock kernel which I backed up before flashing dorimanx, but something went wrong. I really don't know what.
The phone won't turn on, it keeps showing LG logo and showing Secure booting error. Cause: boot certification verify. (1001)
I tried pretty much everything in the past 6 hours and i'm losing my mind.
LG PC suite or any LG pc software won't recognize the phone when plugged with USB, and everytime I plug in the phone to my PC windows opens 15 boxes of "new hard drive detected, format needed to use" (here's a picture)
Also tried following this post: http://forum.xda-developers.com/showthread.php?t=2582142, but no luck. It seems like my dev folder is missing alot of sub-folders for some reason.
Anyway I'm really lost. Can you guys please help me to solve this? I would really appreciate it.
Thanks.
To be sure, have you already tried to get into TWRP through the factory reset key combination?
I tried almost every combination possible. the phone simply resets itself to the same situation, screen is on but black and nothing else happens
After holding power+down buttons the LG logo comes up and disappears in a snap, like something is wrong.
Nightbeat said:
I tried almost every combination possible. the phone simply resets itself to the same situation, screen is on but black and nothing else happens
After holding power+down buttons the LG logo comes up and disappears in a snap, like something is wrong.
Click to expand...
Click to collapse
Your device is unplugged while you do this right? It has to be completely turned off before doing the combination, and while plugged in, it just doesn't turn off completely.
Yes, it is unplugged while I do it
You'll need to hold the volume down + power key as you turn the phone on, then re-press them when the LG logo shows up to get to the factory reset page. Just verifying the simplest solution before I go in depth with this.
If your phone still won't get into TWRP, try this: plug the phone in to your computer, and open device manager (right click computer > manage) and under portable devices, locate your phone. Once you find it, right click it, click uninstall, and once that's done, unplug your G2 and reboot the PC. Once it boots up, plug your G2 back in and let it reinstall the drivers and try to do the guide again. Best of luck!
EDIT: I just realized the guide you are looking at requires Ubuntu. Are you aware of this?
double edit: http://forum.xda-developers.com/showthread.php?t=2432476
Let me know if you've tried this guide yet.
I believe you're using vistual machine for ubuntu.
Well, if you keep getting 15 messages about formating drives (in windows) when you plug your phone to ubuntu you will not get your patitions in ubuntu.
So you should close the messages asking you to format drives, then open vmware in full screen mode, then plug your phone to computer and follow the guide http://forum.xda-developers.com/showthread.php?t=2582142. I'm sure in this case you will get your phone partitions showing is dev/sdb.
Even if you don't get those partitions keep trying several times untill you succeed.
Good luck.
Thank you!
Apparently I was using the key combination wrong.
And yes I was using ubuntu on a VM.
Nightbeat said:
Thank you!
Apparently I was using the key combination wrong.
And yes I was using ubuntu on a VM.
Click to expand...
Click to collapse
Had a feeling! Glad you fixed it!

Blackberry priv keeps on restarting

Hello, i have a blackberry Priv that is stuck on logo and just keeps on restarting and doesnt go to the main screen....how to solve this problem? CAn i solve it by flashing with autoloader
Also, i cant turn on the phone to main screen,
How do i know if it is version:
STV100-1,
STV100-2,
STV100-3,
STV100-4 OR
STV100-5
I downloaded autoloader for STV100-1 and installed drivers too. Now i put phone in fastboot mode by pressing power key and vol - key. I connect phone to pc and run autoloader but window appears and disappears. How to flash this phone and repair this phone....someone pls help
thanks
andrew21 said:
Hello, i have a blackberry Priv that is stuck on logo and just keeps on restarting and doesnt go to the main screen....how to solve this problem? CAn i solve it by flashing with autoloader
Also, i cant turn on the phone to main screen,
How do i know if it is version:
STV100-1,
STV100-2,
STV100-3,
STV100-4 OR
STV100-5
I downloaded autoloader for STV100-1 and installed drivers too. Now i put phone in fastboot mode by pressing power key and vol - key. I connect phone to pc and run autoloader but window appears and disappears. How to flash this phone and repair this phone....someone pls help
thanks
Click to expand...
Click to collapse
Hi,
If you don't know the model #, then don't flash...
I read that Hard Reset of the device is needed, by pressing and holding the volume up and down keys simultaneously for at least 10 seconds, when you reach the error screen
Charkatak said:
Hi,
If you don't know the model #, then don't flash...
I read that Hard Reset of the device is needed, by pressing and holding the volume up and down keys simultaneously for at least 10 seconds, when you reach the error screen
Click to expand...
Click to collapse
I tried to hard reset, enter bootloader mode, enter recovery mode but its all in vain. Moment phone goes to bootloader mode for enter into fastboot it restarts.
By pressing Volume up + Power it takes me to recovery mode there it shows error and again restarts.
Even its not getting connected to pc cause it restarts continuously and in this situation how can I know which model it is and how can I flash new version.
All this happened after Marshmallow update.
Please come up with some solution else this is just a paper weight.
I have the same issue, after Marshmellow update my Priv keep restarting and continuous doing that until the batTrey drain. The phone also heats up and can't find a solution. Tried all kind of reboots but nothing works.
Hoping for a solution before the phone dies completely.
Same issue since 2 days ago
Hello,
I also have the same issue with the PRIV. I spoke with BB Support. They told they will contact me by after 24 hours. I don't know if there won't be any valid warranty since it is an unlocked phone.
Have you find any solution for this?
Please someone help!!
this is because of a wrong flash, you need to use the autoloader appropiate for your unit, with device in fastboot mode run the autoloader, if you do not know your version download all available and flash them, if it is not valid for your unit it wont flash or it wont work, if you swap files to try to bypass and install mm on ll device like att it wont work neither, i have tested this and it works no matter if you swapped files from other autoloaders or not as long you use the correct one your device will be back to life
Same error here...
But if I try to enter fastboot mode (vol-), it reboots after 2-3 seconds...tried also 32 seconds of power on button....any idea?
Thank you,
Chuck26
nicromant said:
this is because of a wrong flash, you need to use the autoloader appropiate for your unit, with device in fastboot mode run the autoloader, if you do not know your version download all available and flash them, if it is not valid for your unit it wont flash or it wont work, if you swap files to try to bypass and install mm on ll device like att it wont work neither, i have tested this and it works no matter if you swapped files from other autoloaders or not as long you use the correct one your device will be back to life
Click to expand...
Click to collapse
Thanks for the tip,
I tried to flash it with one autoloader days ago. It just didn't succeed. The screen went black with unceasing blinking green light.
I kept the contact wit BB Support. They just washed their hands. They told me to go to the Rogers Store where I just bought the PRIV to ask them for a replacement. This is kind of impossible, since I live in Mexico and when the device was bought was on a trip to Vancouver. Yesterday I just plugged in my laptop the phone with the autoloader running hoping something happens. So I left it at home for several hours. When I came back, it was just as before, restarting over and over and over until fastboot menu. So I just gave another try to the autoloader, but it just happened again. Now it remains in black screen and with the green led light blinking. I tried several button combinations over and over just to get to the fastboot menu with no success.
I can't make it to bring up the loading screen and neither fastboot menu.
I guess it was because picking a wrong autoloader for flashing the PRIV. I downloaded another autoloader for trying.
Please help with this.
My PRIV is the STV100-3.
The first autoloader I tried is the Rogers Canada or Orange Slovakia – STV100-3 & STV100-4 - AAF057 Software Version
The second I want to try is the BlackBerry common SW for generic STV100-1, STV100-3 & STV100-4 devices - AAF518 Software Version
This is the link where I got them:
http ://ca.blackberry.com/content/blackberry-com/en_ca/support/smartphones/blackberry-PRIV/reload.html
Thanks in advance!!
nicromant said:
this is because of a wrong flash, you need to use the autoloader appropiate for your unit, with device in fastboot mode run the autoloader, if you do not know your version download all available and flash them, if it is not valid for your unit it wont flash or it wont work, if you swap files to try to bypass and install mm on ll device like att it wont work neither, i have tested this and it works no matter if you swapped files from other autoloaders or not as long you use the correct one your device will be back to life
Click to expand...
Click to collapse
Thanks for the tip,
I tried to flash it with one autoloader days ago. It just didn't succeed. The screen went black with unceasing blinking green light.
I kept the contact wit BB Support. They just washed their hands. They told me to go to the Rogers Store where I just bought the PRIV to ask them for a replacement. This is kind of impossible, since I live in Mexico and when the device was bought was on a trip to Vancouver. Yesterday I just plugged in my laptop the phone with the autoloader running hoping something happens. So I left it at home for several hours. When I came back, it was just as before, restarting over and over and over until fastboot menu. So I just gave another try to the autoloader, but it just happened again. Now it remains in black screen and with the green led light blinking. I tried several button combinations over and over just to get to the fastboot menu with no success.
I can't make it to bring up the loading screen and neither fastboot menu.
I guess it was because picking a wrong autoloader for flashing the PRIV. I downloade n¿another autoloader for trying.
Please help with this.
My PRIV is the STV100-3.
The first autoloader I tried is the Rogers Canada or Orange Slovakia – STV100-3 & STV100-4 - AAF057 Software Version
The second I want to try is the BlackBerry common SW for generic STV100-1, STV100-3 & STV100-4 devices - AAF518 Software Version
This is the link where I got them:
http ://ca.blackberry.com/content/blackberry-com/en_ca/support/smartphones/blackberry-PRIV/reload.html
Thanks in advance!!
leo_ackzion
if the autoloader solution does not work then you need to force manually the unit into flashboot (google how to force fastboot)
then try to flash each content from the img into the device manually same as the nexus devices
the autoloader should be able to recover your device
this is the reload instruction website
http://support.blackberry.com/kb/articleDetail?articleNumber=000038083
this is where the autoloaders reside
http://ca.blackberry.com/content/bl...pport/smartphones/blackberry-PRIV/reload.html
make sure your device is physically an STV100-3 or 4 it is basic to have the proper version
nicromant said:
leo_ackzion
if the autoloader solution does not work then you need to force manually the unit into flashboot (google how to force fastboot)
then try to flash each content from the img into the device manually same as the nexus devices
the autoloader should be able to recover your device
this is the reload instruction website
http://support.blackberry.com/kb/articleDetail?articleNumber=000038083
this is where the autoloaders reside
http://ca.blackberry.com/content/bl...pport/smartphones/blackberry-PRIV/reload.html
make sure your device is physically an STV100-3 or 4 it is basic to have the proper version
Click to expand...
Click to collapse
Hi nicromant.
After several hours I wrote my last comment, the phone showed the fastboot mode, restarting over and over without showing the BB Logo, but only the fastboot menu, constantly rebooting.
Next, I tried to reload the OS via autoloader again. But then my phone again was in black screen with green and white blinking light.
Then I tried to manually force it into fastboot with the Android SDK Tools, but nothing happens.
When I introduce "adb devices" command, it won't show any connected device in the PC.
So I don't know what else I can do.
Please help!
Thanks in advance.
I just had this problem. Took it to the tmobile store i bought it from and they told me it was fried hardware. The phone keeps trying to reboot and fix itself but obviously it can't happen. Their solution? Get a new phone. I had a 2 year warranty and apparently the priv has been having so many problems that the store was offering a trade up deal to a samsung. Hopefully a store near you is doing the same, because thats probably your only option at this point if it's the same problem as mine.
leo_ackzion said:
Hi nicromant.
After several hours I wrote my last comment, the phone showed the fastboot mode, restarting over and over without showing the BB Logo, but only the fastboot menu, constantly rebooting.
Next, I tried to reload the OS via autoloader again. But then my phone again was in black screen with green and white blinking light.
Then I tried to manually force it into fastboot with the Android SDK Tools, but nothing happens.
When I introduce "adb devices" command, it won't show any connected device in the PC.
So I don't know what else I can do.
Please help!
Thanks in advance.
Click to expand...
Click to collapse
Try to install the appropiate ADB and fastboot drivers it is why your pc is unable to see the device, check on device manager if you have it setup properly, unfortunately i do not have a priv anymore (i change devices every 1 or 2 month)
I have same problem with my Priv from AT&T (100-1). It failed to boot after autoloader. it does not turn on. Just LED flashes: White one flash, then Green 3 flashes. and again. I can not force it into fastboot menu anymore holding Power plus Vol down or any other combination.
Need help! Thanks
after updating with this loader
https://bbapps.download.blackberry.com/Priv/bbry_qc8992_autoloader_user-common-AAG191.zip
i also cant boot the phone it just show me 4 options on screen but keep on coming back to it no matter what i select
Hold power & vol down both for 32 seconds for a real HARD reboot...
Charkatak said:
Hi,
If you don't know the model #, then don't flash...
I read that Hard Reset of the device is needed, by pressing and holding the volume up and down keys simultaneously for at least 10 seconds, when you reach the error screen
Click to expand...
Click to collapse
I had the same issue quite suddently with no warning. Phone just shut itself off (in a manner similar to what happens when you long press the powre button) Spent hours wondering what to do. Finally Thought the power button was stuck. I slipped a long finger nail into the gap where the power button contacts the phone electronics (dont know how to be clearer than this) to try and separate the power button and whatever it touches when you press it. After a couple of tries, The phone started up successfully. It appears to be a design issue
I FIXED IT!
Same issue as described, bootloop after 10 seconds.
I used electrical tape under and over the flat cable of the power button, also covered the "inner" power button with this.
Now it works for already 1,5 hours and is loading updates.
Also posted this as nes3Ah in crackberry forums, but it has to be released by a mod.
Good luck!

Categories

Resources