Flashed my device with BuildOS software - everything went smoothly, but when I reset it at the end it became stuck on the boot screen (where it shows you your radio R 1.32.00 etc.).
Now I cannot sync and reflash it and the phone just gets stuck on this screen with hard & soft resets.
Any ideas?
BuildOS keeps giving me the Error101 No Connection message.
Are there any programs out there that will flash my internal memory and get this unstuck?
Related
i got myself a jasjar couple days ago.
but the device keeps rebooting/reseting every 15min. or whatever.
so i tried to update the rom version with a more recent one.
however ... now my device doesn't do anything at all.
it's frozen at the bootloader if i'm correct.
only thing it displays is 'serial' at top of the screen and 'version 1.00' at the bottom.
i tried a hard reset, soft reset.... always ends up back at this screen.
could anyone plz help me?
Sounds like you just need to reflash your device. Use this ROM: http://forum.xda-developers.com/showthread.php?t=319838
Unpack the zip file and run the MaUpgradeNoID file.
---
i've done that. but the phone keeps rebooting.
just after spash screen the screen goes black.
is there a way to backup my current radio/ext rom etc.?? so i can restor?
i have the WM ultimate as suggested, but keeps rebooting.
i tried a hard reset, which sometimes helps.
but when i disconnect my charger/usb cable the phone goes off within a few secs.
i tried with 3 batteries, all result the same so can't be that i think.
As my understanding your device doesnt boot as long you are pluged to power isnt it? if I am right try this:
clean the contact point of your battery and contact clips on your device (golden clips) use a pcb board cleaner
lets say the power is at 90% but wouldn't boot.
but when connected with usb/power it does load, and needs to stay connected till the 'enter pin'-screen prompts.
i think this issue is related to an unstable mix of rom/ram/radio information.
after i tried some custom cooked images everything seems fine
Hey guys,
I have the Bootloader all happy and running but after flashing the Radio (I did this because I thought it would fix random crashes and GPRS crashing) the OS just hangs in boot even after hard resetting.
How do I go about flashing when in Bootloader mode?
Cheers,
Callum
EDIT: I tried with the TTY app (mtty) but it fails to show a USB port. I noticed that Windows XP just sits on acquiring network address.
Hey.
You must deactivate AcitveSync --> "Allow USB Connections" and kill all ActiveSync Processes.
If you have Vista you need other Drivers. Search in google 'VistaRUU'.
You could Flash VIA SD Card from Bootloader, just try to search a little bit in google.
cu
pOpY
If you have installed in the past Hard SPL, you should be able to flash a new ROM from the bootloader screen. Simply choose Hard SPL on the installer.
I have a SIMILAR ISSUE I I have issues with an old Hermes not gonna get into it, but I gotta outta what I thought was my WORST mess ever. Now my 8525 boots (I have the Official AT&T WM6 ROM) see all the opening screens and BOOM it JUST HANGS on the TOUCHSCREEN CALIBRATION screen!!! Touchscreen is completely UNRESPONSIVE so are 90% of the rest of the buttons I can power off and use the side scroll Blackberry dial, and I think the Right SOFT KEY brings UP a USELESS menu, BUT I AM STUCK AT THE CALIBRATION screen no touchscreen I have done A Hard Reset 1000 times, I can connect via ActiveSync with my PC, cant Flash Anything though I get ERROR 260 So I just have a booting 8525 stuck on th4e calibration screen
ANY IDEAS??????????/
nicknowsky said:
I have a SIMILAR ISSUE I I have issues with an old Hermes not gonna get into it, but I gotta outta what I thought was my WORST mess ever. Now my 8525 boots (I have the Official AT&T WM6 ROM) see all the opening screens and BOOM it JUST HANGS on the TOUCHSCREEN CALIBRATION screen!!! Touchscreen is completely UNRESPONSIVE so are 90% of the rest of the buttons I can power off and use the side scroll Blackberry dial, and I think the Right SOFT KEY brings UP a USELESS menu, BUT I AM STUCK AT THE CALIBRATION screen no touchscreen I have done A Hard Reset 1000 times, I can connect via ActiveSync with my PC, cant Flash Anything though I get ERROR 260 So I just have a booting 8525 stuck on th4e calibration screen
ANY IDEAS??????????/
Click to expand...
Click to collapse
check out this link
http://forum.xda-developers.com/showthread.php?t=382578
If you've Hard SPLed your hermes, try the sd card method. 1st, you need to back up your card, format it fat 32 then copy the .nbh file onto from the rom of your choice. rename the nbh file to "Hermimg.nbh" then insert into phone. put hermes into bootloader and follow the prompts. this will reflash another os. Hope this gets you out of your pickle... cheers
Hi,
I cannot flash anything on my Rhodium TMo.
Everytime I flash with any Rom or radio, I got error 302 and stuck in the middle of proccess.
I cannot go in the windows phone, it stucks on 3 colors RGB.
What should I do?
I've this situation for almost a day, and I feel panic now..
I've tried task29, but it stucks on 71%.
I've tried flashing NRG roms, and always stuck in 1%.
I've tried flashing radio, and always stuck in 41%.
It's already HardSPLed.
Really, I don't know what to do...
Please help..
I'm guessing you are flashing true the active sync method. If not please tell.
1. Go into the bootlaoder, plugin your usb (you should see USB on your phone) and flash like you normal would (this way you don't use active sync)
2. Flash true your SD card. Place RHODIMG.nbh in the root of your storage card.
I think my phone may have had a catastrophic hardware failure but I am hoping not and maybe some of you clever people can help me resurrect it.
I have been running KK ParanoidAndroid without any problems for a few months. Yesterday I tried to boot it up and after showing the Google screen the screen went black then a single horizontal white line appeared 3/4 way down the screen. It stalled there forever so I pulled the battery and booted into TWRP recovery. It seemed to take a lot longer than normal but did boot into TWRP OK.
Once there however TWRP reported no backups, no OS and no storage space (0 MB). I couldn't mount any partitions,. I tried factory reset but it appeared to fail and just made the phone vibrate for a while. The log shows:
Unable to mount - /system, /cache, /data etc and something about no valid partition for MTP
Then the screen greyed out, faded to black and the phone powered off. Now it seems pretty much non responsive.
Any thoughts, other than bin it and get a new phone?
EDIT: It seems it hadn't powered off, just gone blank whilst attempting to wipe. I am now back in TWRP but the factory reset has failed. So. It seems I still have a functional recovery but not much else. Any help much appreciated.
In the absence of any responses I've searched a bit more and decided in the end to try to install a factory image using fastboot. I was holding out to see if there was any way I could save any user data but in the end that seems unlikely anyway.
So, I followed this guide: http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/
It all seemed to go smoothly until the final commend - after flashing the zip containing the system, boot and recovery images I got the error message "FAILED (remote: Write Fail)"
Hmmm...
Regardless I tried to finish off with fastboot reboot. As I hit enter the device screen faded slowly to a kind of washed out grey and the horizontal white line appeared on the display again (as before - see my first post). No further progress, and the device became unresponsive. I pulled the battery and tried to boot, and it bootlooped once to the Google screen before the screen faded to a washed out grey again and it became once more unresponsive.
After pulling the battery once more I can still get to fastboot, and I can now get to stock recovery, but otherwise I can't seem to get any further.
Is it toast??
My daughter has been using this phone, but never backed her photos up. Now it won't boot and she is worried they are lost forever. I've been trying to help, but only seem to make things worse.
1. She never enabled USB debugging, or rooted it
2. She could not tell me whether she had allowed the OTA upgrades.
3. It got into a reboot loop a few days ago. It would start to boot, then say it was optimising a random number of apps (anything between 90 and 158) and then start over. Wileyfox tech support told me that this was due to an incompatibility between Cyanogen and the latest Facebook Update.
4. They sent me a link to the FOTA files with instructions how to progressively upgrade to Android 7 (TOS111B)
5. They couldn't tell me how to determine whether it was running CM12 or CM13 (I now realise that I could have looked at the log files in the recovery partition)
6. I therefore assumed that it was running CM12. I used their instructions to go into recovery and manually update from SD card to ZNH0EAS2NH from there to ZNH2KAS7EB and then to TOS111B
7. Fatally I did not reboot between updates. At the end I had the Wileyfox splash screen black on white, and then got an animation with it red on white. It then got stuck.
8. I then tried using fastboot to go back to the original version of the OS so I could start over. I found the fastboot image and I flashed the boot and system partitions.
9. Now on boot it either gets stuck on the black on white boot screen, or it displays it for a second and then turns off.
Can anyone help me? - I think my daughter will have a nervous breakdown if I don't find a way of recovering her photos. Recovering the photos is more important than unbricking the phone.
jerrytaff said:
My daughter has been using this phone, but never backed her photos up. Now it won't boot and she is worried they are lost forever. I've been trying to help, but only seem to make things worse.
1. She never enabled USB debugging, or rooted it
2. She could not tell me whether she had allowed the OTA upgrades.
3. It got into a reboot loop a few days ago. It would start to boot, then say it was optimising a random number of apps (anything between 90 and 158) and then start over. Wileyfox tech support told me that this was due to an incompatibility between Cyanogen and the latest Facebook Update.
4. They sent me a link to the FOTA files with instructions how to progressively upgrade to Android 7 (TOS111B)
5. They couldn't tell me how to determine whether it was running CM12 or CM13 (I now realise that I could have looked at the log files in the recovery partition)
6. I therefore assumed that it was running CM12. I used their instructions to go into recovery and manually update from SD card to ZNH0EAS2NH from there to ZNH2KAS7EB and then to TOS111B
7. Fatally I did not reboot between updates. At the end I had the Wileyfox splash screen black on white, and then got an animation with it red on white. It then got stuck.
8. I then tried using fastboot to go back to the original version of the OS so I could start over. I found the fastboot image and I flashed the boot and system partitions.
9. Now on boot it either gets stuck on the black on white boot screen, or it displays it for a second and then turns off.
Can anyone help me? - I think my daughter will have a nervous breakdown if I don't find a way of recovering her photos. Recovering the photos is more important than unbricking the phone.
Click to expand...
Click to collapse
Since posting this I have had a partial success. A more complete set of fastboot flashing using the TOS111B fastboot images has got me to a phone that boots. Many of the apps work. However...
a) I get an "unfortunately the process com.android.phone has stopped" appearing almost as fast as I can close the app making it very difficult to get anything off the phone. However, I did manage to set up a google sync to upload the photos.
b) my daughter now tells me that her SMS's are vital.... and the messaging app says " getting message" then closes down
c) I cannot enable developer setting to enable usb debug mode. I can get into the phone status page under settings. Repeated tapping on the android version brings up the nougat splash screen, but the 7 taps (or 700 for that matter) on build number does nothing whatsoever.
Does anyone have any ideas how to recover to a fully working system without doing a factory reset?
I suspect that the sms database would have gone when the cache was cleared. Can anyone confirm that to be the case before I spend any more time trying to recover them?
Hi Jerry ,
Exactly the same problem here. Could you tell me where you've found the TOS111B fastboot images?
Thx!
Have you tried booting into safe mode?
I think you do that by pressing and holding the volume down down button during reboot.
If you can manage that you may be able to dissable the apps that are causing the crash.