Related
Good evening, kind forum readers.
Per the subject line, I find myself in possession of one misbehaving iMate-branded Blue Angel. Everything was working perfectly until a day and a half ago. Now the device is acting as though there is no SIM card inserted whatsoever.
As you might expect, there is no signal detected whatsoever. The 'Device Information' system applicaton reports no information for the Radio or Protocol version. There is no IMEI number listed on the Identity tab. Launching the 'SIM Manager' tool does nothing - the application never launches. When I do a soft reboot, it correctly lists the ROM verion on the startup screen, but says directly above it "No GSM". I've tried a hard boot and restore from a backup from about a week ago, no luck. I have tried with two SIM cards from two different providers, neither one produces any different results. Both cards work perfectly when inserted into another phone.
I am using the official 1.40.00 WWE ROM from iMate. When I try to reapply the ROM, I receive the "COUNTRY ID ERROR". I tried with an older third-party ROM that I had been using a while back, but that also aborts with the same error message.
Speaking with iMate support netted me the typical "Send it in to a service center" answer.
Hoping that someone else out there might have gone through something similar? Any thoughts/suggestions on how I might recover from this?
Regards,
Shawn.
http://wiki.xda-developers.com/index.php?pagename=BA_1.40.00_Upgrade
Try following the description on the link, go for the MaUpgradeUt_noID option.
Use this on your Original Rom, and try one upgrade at a time, Radio first, then OS, Don't see any reason to flash the Extended Rom
bosjo said:
Try following the description on the link, go for the MaUpgradeUt_noID option.
Use this on your Original Rom, and try one upgrade at a time, Radio first, then OS, Don't see any reason to flash the Extended Rom
Click to expand...
Click to collapse
I just tried this option, and it did progress further this time, but it produced the following error:
Device Software Update Utility - R2500 D1001 - CB2.07 -1
ERROR 114: RADIO ROM UPDATE ERROR
There has been a problem while updating your device software.
To continue the update, please:
1 Disconnect your device and the USB cradle.
2 Perfrom a normal reset by pressing the reset button (as left picture show).
3 Reconnect your device and the USB cradle and run this device software update program again.
Click Exit to quit.
Click to expand...
Click to collapse
Being something of a newbie in such matters, I didn't realize that I had to run GetDeviceData.exe first, so I didn't have a copy of DeviceData.txt. In that the device was not in a bootable state, I wasn't sure how to run the OS upgrade without the Radio upgrade. I ended up going with the decidedly unscientific but seemingly effective solution of just renaming the 'radio_.nbf' file. The OS and extended ROM both upgraded successfully. So now I'm back where I started - the radio is still not functioning.
Run the same upgrade this time with the radio.nbf and remove the other 2 nbfs.
Else ron the radio upgrade only of wiki using those files.
And if what MDAIIIuser says don't work.
Download the latest Rom upgrade from your wendor website,
extract the .exe file with a zip program,
delete the nk, ms, radio files,
Copy the 1.13 radio in there,
Run the BaUpgradeUt.exe
Or try to only delete the ms and nk files leaving what ever radio is in there, and run the BaUpgradeUt.exe
This is based on my experience with two UNis..one Exec and other JASJAR..both had same problem...this is how I solved :
-Put yr device in bootloader Mode
-Disable USB in Active Sync
-Now connect woth USB cable and open mtty utility
-Select the "WESUSB... " port
-You shall see a blank white screen..press Enter to get "USB>"
-Then type ( as BUzz has informed) set 14 0
(here I wud like to inform that after doing the above I did not get success so I typed set 14 10,then set 14 9 for two three times)
-Then I ran the ROM Upgrade directly(After enbabling the USB)
-I then followed the procedure as informed on the COngratulations Screen that is hold the two "-" buttons and soft reset and then pressed 0
-I got them back to normal..
I hope this helps to all my friends...Pls feel free..pls do not trouble our Buzz..he might be busy in inventing something more to our devices
could you please clarify this statement
(here I wud like to inform that after doing the above I did not get success so I typed set 14 10,then set 14 9 for two three times)
in particular the bit "for two three times"
ta
I meant that after typing set 14 0 did not help so in frsutration I thoight of typing something more like set 14 10, set 14 9 set 14 20 also...then I did the flashing again...I got the success...
my msn : [email protected] pls add me...I am normally on line 07.30 to 09.30 IST and 22.00 onwards IST(Indian Std Time).I can help u out
great info. I suggest the following as well:
- If after upgrading and reset, still see Serial 1.0, UpGRADE THE RADIO, and reset again (for mor info search for "MDA PRO is alive"). It will work.
- And, as Dherrero said to me, Dont' worry! there is almost always a solution for your problem (99%).
Same problem, still can't get Jasjar working
Hi -
My Jasjar is now sitting endlessly at the blue imate boot screen, showing the new ROM version numbers. Help!
I've tried "hdubli"s suggestions, but to no avail (although i still have no idea what "set 14 0" was meant to do, or what i was meant to see on screen afterwards!) I also tried "set 14 10", "set 14 9", "set 14 20"...
I've tried reflashing down to the older ROM version, then back to the latest ROM(several times now).
I've tried the following update: http://forum.xda-developers.com/viewtopic.php?t=42992&highlight=bootloader
I'm re-applying the imate official rom now, as i don't know what the above version one is.
But it's still hanging at the blue startup screen...
- It seems to be ROM version independent
- what else is there that i can flash? could the bootloader be corrupt or something?
- iMate online support walked me through reapplying from bootloader, and removing the battery, but that was all they could offer. THen referred me to a 'local service agent'.... but that could take days...
Can anyone help?
/Mark
Re: Same problem, still can't get Jasjar working
mcackay said:
Hi -
My Jasjar is now sitting endlessly at the blue imate boot screen, showing the new ROM version numbers. Help!
I've tried "hdubli"s suggestions, but to no avail (although i still have no idea what "set 14 0" was meant to do, or what i was meant to see on screen afterwards!) I also tried "set 14 10", "set 14 9", "set 14 20"...
I've tried reflashing down to the older ROM version, then back to the latest ROM(several times now).
I've tried the following update: http://forum.xda-developers.com/viewtopic.php?t=42992&highlight=bootloader
I'm re-applying the imate official rom now, as i don't know what the above version one is.
But it's still hanging at the blue startup screen...
- It seems to be ROM version independent
- what else is there that i can flash? could the bootloader be corrupt or something?
- iMate online support walked me through reapplying from bootloader, and removing the battery, but that was all they could offer. THen referred me to a 'local service agent'.... but that could take days...
Can anyone help?
/Mark
Click to expand...
Click to collapse
Hi all,
I have been following almost every thread of this forum for the past week or so, && this is the first time i have come across another person who is suffering from the same problem... Hi Mcackay... I have the EXACT same problem... I have been given some suggestions which i shall try soon... If anything atall works i shall let you know bro... && please inform me if you find any solution...
mOrph
May be this will help further
If one has tried to update Atom/Wizard ROm...will certainly notice that the upgrade process doesn't start unless the battery is >50%..so this is the biggest clue.
Those who want to upgrade make sure that their battery is more than 50%..no one will face the problem.
So those huys who are already in problems...shd try to get their friend's battery which is fully charged and then do the ROM Update..
This will certainly solve their problems.
I installed the new ROM but every time it just said 'congratulations all done etc.....' and I could not get out of bootloader mode.
I did a hard reset to get the white screen and then had the choice of X or 0, but both put me back at the grey screen (where it is just possible to read USB and serial 1.0).
After doing this 5 or 6 times, I found the old radio 1.06 upgrade and ran that, and on completion it allowed the universal to start up AND the ROM files that I had sucessfully installed (see above) were there.
Only problem is I now have 1.06 radio and not 1.09, but i can do an upgrade for just that later.
steve
i cannot make it start i have tried to write in mtty set 14 0 , set 14 9, set 14 20 but nothing.also i ave triedto install almost all rom but everytime stucks in the blue i mate image,any ideas please???
angeln20 said:
i cannot make it start i have tried to write in mtty set 14 0 , set 14 9, set 14 20 but nothing.also i ave triedto install almost all rom but everytime stucks in the blue i mate image,any ideas please???
Click to expand...
Click to collapse
Hi buddy... Am facing the same problem for the past 15 days... My JASJAR has been stuck on the blue imate splashscreen mode... I too have tried flashing the device with all possible ROMS but to no use... One thing that we can conclude is that the problem is ROM independent... Lets work on this together.. There are other 2-3 people on this forum who are facing this same problem... Lets put our heads together && work out a solution... If there is any success at my end, i will update you asap.. PLEASE do the same...
Regards,
mOrph
Almost the same problem I have
Almost the same problem I have with MDA Compact II Now the device is dead the screen blinks. somebody told me that there is a software that works on dos mode and reset all to bring it boot loader & and so there is a bottun inside the device to to clear every thing. But I don't know how???
I also have the same problem stuck on 2nd splash screen
This all started when I used the official imate Jasjar ROM upgrade from the clubimate site (since I have an imate Jasjar). I've come a long way in understanding how to manually upgrade the ROM and have tried numerous ROMs, radios, etc. and still won't go past the splash screen. I'm hoping I we can figure it out today.
no luck yet.i cannot to something and i am afraid that the battery will empty.....
I'm hopefull - I'm online with imate support
I keep on getting disonnected from their support, but so far they said "its just and error but i will help you to fix it so please me the IMEI number" so I gave him my IMEI number and he's supposed to email me the fix. We'll see ..... I'm keeping my fingers crossed.
morphosin said:
angeln20 said:
i cannot make it start i have tried to write in mtty set 14 0 , set 14 9, set 14 20 but nothing.also i ave triedto install almost all rom but everytime stucks in the blue i mate image,any ideas please???
Click to expand...
Click to collapse
Hi buddy... Am facing the same problem for the past 15 days... My JASJAR has been stuck on the blue imate splashscreen mode... I too have tried flashing the device with all possible ROMS but to no use... One thing that we can conclude is that the problem is ROM independent... Lets work on this together.. There are other 2-3 people on this forum who are facing this same problem... Lets put our heads together && work out a solution... If there is any success at my end, i will update you asap.. PLEASE do the same...
Regards,
mOrph
Click to expand...
Click to collapse
i agree this, i also got problem with my exec,
some of thread told us use mtty set 14 0, or just falsh single rom such llike radio rom or nk.nbf, tied many time, tried may ways of reset, boot options, other version and kinds of roms, still no work for me,
I did solve the problem with 3 Unis by what I hv explained above...I think it is Flash Chip related issue...after upgrade it is just not getting a kind of trigger to load the OS..This time I am really struggling with morphosin's JASJAR...it is lying at my place for past 2 days...but no luck so far.
I hv also tried following mtty commands and the results are as explained
task 28
DOC_format failed
task 0
task 7 0/1
made the Uni hang...it did not lock/unlock the ROM
rtask 0/1/3/4
In all these cases it did reset the radio...also had the Radio ROM run but still no effect on booting
May be buzz can help now as increasing number of people are getting this
problem..
I also think of some kind of Super CID in new ROMs which need to be unlocked before doing the upgrade..
@hdubli
thanks but many of my friends are helped by your post,too.
Also one of my friend, receovered by useing command with PlatformBuilder from PC, he reported me like that.
Asukal said:
@hdubli
thanks but many of my friends are helped by your post,too.
Also one of my friend, receovered by useing command with PlatformBuilder from PC, he reported me like that.
Click to expand...
Click to collapse
Hi Asukal...
Can you please elaborate the "platform builder recovery method"... I think thats the only thing left to do now...
Thanks...
FYI ... still working with imate technical support
I've made some progress with imate technical support, but still no solution. So far it's the standard bootloader - USB - Load the ROM response. I'm hoping they'll email me back today with a real answer. I'll keep you all posted.
hdubli said:
This is based on my experience with two UNis..one Exec and other JASJAR..both had same problem...this is how I solved :
-Put yr device in bootloader Mode
-Disable USB in Active Sync
-Now connect woth USB cable and open mtty utility
-Select the "WESUSB... " port
-You shall see a blank white screen..press Enter to get "USB>"
-Then type ( as BUzz has informed) set 14 0
(here I wud like to inform that after doing the above I did not get success so I typed set 14 10,then set 14 9 for two three times)
-Then I ran the ROM Upgrade directly(After enbabling the USB)
-I then followed the procedure as informed on the COngratulations Screen that is hold the two "-" buttons and soft reset and then pressed 0
-I got them back to normal..
I hope this helps to all my friends...Pls feel free..pls do not trouble our Buzz..he might be busy in inventing something more to our devices
Click to expand...
Click to collapse
I also have been stuck in bootloader mode for days, but by following the above it sorts it every time.
I am using mtty v1.42 and simply select USB get the USB> prompt then type SET 14 0 then return. I then see HTCUSB> and close the program
I then cold boot and I am back in business. This is 100% repaeatable
Hope this helps
Stu
Broken Radio ROM blocks official O2 rom, MaUpgradeUt_noID.exe fails "error 114"....
Hello
I hope someone here is able to help me.
I have spent the whole of the last 48 hours (no sleep) trying to fix my O2 XDA Exec. I *believe* that I have tried everything suggested on this forum and on Buzz's site but there is just so much on here now that I may well have missed something.
History:
Over the last few months, my phone has gradually got more inconsistent - dropping calls, refusing to answer calls, losing signal and so on. On Jan 1st, I turned it on and it had lost all my settings - Opera reg code, Wifi encryption, O2 net settings, etc.
I spent the last week with sometimes having network, sometimes not. Finally it just gave up altogether. In Settings>System>Device Info, "Radio Version", "Protocol version" and "IMEI" are all completely blank. When booting, the red text states "No GSM".
Reading around this site it appeared that I should be able to reinstall the radio ROM from the official O2 download however this errored with the Incorrect Country Code error. I have carried out full hard resets and still cannot get any Radio ROM visible. I assume that the lack of IMEI is affecting the official O2 downloads?
Since then, I have tried most variations on this site of ROM installs using MaUpgradeUt_noID.exe suggested in the wiki (with and without entering mtty code: "set 14 0").
Full three-part ROM and radio-only ROM install attempts all fail with the Error 114 "Radio Rom Update Error" (the radio ROM is always attempted first).
The only success I have seen was an update of Bootloader from 1.00 to 1.01 which worked completely perfectly and proved that the PC can indeed connect to the XDA when it feels like it.
After two days of earning no money ( I am self-employed) and no money to spend on support, I wonder if anybody has another suggestion for me?
In case it helps: ROM version: 1.30.107 WWE, ROM date: 04/11/06, ExtROM version: 1.30.162 WWE
All advice welcome
Thanks
Leapy
extract everything from the exe and do an upgrade without the radio.nbf
did you read what he said? its the radio that's bad and needs replacing
i don't know, sorry
poussin69 said:
extract everything from the exe and do an upgrade without the radio.nbf
Click to expand...
Click to collapse
I am now totally confused.
I know there was a smiley at the end of your comment, I just can't work out if you are being funny or astute (or both?). Can you explain how reinstalling the non-radio ROMs will help? Would that restore the IMEI?
TIA
Leapy
Midget_1990 said:
i don't know, sorry
Click to expand...
Click to collapse
Thanks for responding anyway. At least I am not crying alone in the wilderness.
It would be terrific to find a fix, though.
Try to flash the radio from Buzz's unlocker with MaUpgrade_NoID.exe
http://www.buzzdev.net/index.php?option=com_content&task=view&id=78&Itemid=1
pof said:
Try to flash the radio from Buzz's unlocker with MaUpgrade_NoID.exe
Click to expand...
Click to collapse
Thank you for the suggestion, I just tried as you proposed. "Error 114 - Radio ROM Update Error" *sob*!
It's a real shame. It's actually the ideal phone for my needs.
Leapy
1. Disable Activesync (connection settings -> uncheck "allow USB connections").
2. Put universal in bootloader mode
3. Connect device to computer using USB cable.
4. Start HHD Usb monitor (trial version is OK).
5. File -> New session -> USB Monitor -> Select USB device where your phone is connected -> Check "request view" -> Finish
6. In the upper part there are two tabs: basic and complete. Click on "Complete".
7. Click on MaUpgrade_NoID.exe and start the radio flashing process, if everything went fine you should see all the USB traffic output on USB monitor window.
8. When radio upgrade fails, click on Edit -> Export and Save as type "ANSI Text files".
9. Save the text file and zip it.
10. Attach the output here or upload it to ftp if it's too big.
Only with this we can see exactly why it fails
Good luck!
http://forum.xda-developers.com/showthread.php?p=994444#post994444
first as recomended i disabled usb from activesync
then downloaded mtty 1.42
connected the usb and started mtty
chose usb
white screen.....
typed set 14 0...
some gibrish on the screen....
ran the rom update....but it informed me that the rom is not for my device...
typed task 0 in mtty (not sure bout the command but its on page 2 of the forum)
ran the update....nothing same error....
now i saw that my universals screen was blank....
removed the battery....and then restarted my universal....
this might help you...
rtask 0/1/3/4
pof said:
1. Disable Activesync (connection settings -> uncheck "allow USB connections").
2. Put universal in bootloader mode
3. Connect device to computer using USB cable.
4. Start HHD Usb monitor (trial version is OK).
5. File -> New session -> USB Monitor -> Select USB device where your phone is connected -> Check "request view" -> Finish
6. In the upper part there are two tabs: basic and complete. Click on "Complete".
7. Click on MaUpgrade_NoID.exe and start the radio flashing process, if everything went fine you should see all the USB traffic output on USB monitor window.
8. When radio upgrade fails, click on Edit -> Export and Save as type "ANSI Text files".
9. Save the text file and zip it.
10. Attach the output here or upload it to ftp if it's too big.
Only with this we can see exactly why it fails
Good luck!
Click to expand...
Click to collapse
Thank you. I think I did everything exactly as you instructed.
Please find attached the zipped log file.
I would welcome your advice.
Leapy
Radio is corrupted, and device cannot check SecLevel (wait interpreter timeout), it returns default seclevel=FF (unprivileged) and correct CID (O2___001), however when switching to radio bootloader to upgrade the radio, device doesn't answer to any 'rerase' command, that's why the utility gives out flashing after receiving no response to 3 "rerase 0 10000" commands.
Probably this is a bit "crazy", but if it is your last chance... try the following commands in mtty, and try to upgrade the radio again after this:
Code:
USB> password 0000000000000000
USB> set 1e 1
USB> erase a0040000 c80000
USB> erase a0cc0000 c80000
USB> erase a1940000 640000
USB> set 1e 0
Don't do it if you can fix your device by any other means (warranty, service centre, etc...) because I'm not sure if it will work or not
Error 114: Radio Rom Update Error
WOW I have the same problem.....
but this commands for mtty...did nothing to my problem.
ERROR 114: RADIO ROM UPDATE ERROR
I don't know if that helps you....on my PDA it says Upgrade Radio Stack Please Wait...
I have the perfect phone....but it is not a phone anymore...and I go crazy.
Is there any way to update the radio rom from SD card??
Please Help
posted reply to incorrect post - cannot delete post - ignore. Please see next post.
pof said:
Radio is corrupted, and device cannot check SecLevel (wait interpreter timeout), it returns default seclevel=FF (unprivileged) and correct CID (O2___001), however when switching to radio bootloader to upgrade the radio, device doesn't answer to any 'rerase' command, that's why the utility gives out flashing after receiving no response to 3 "rerase 0 10000" commands.
Probably this is a bit "crazy", but if it is your last chance... try the following commands in mtty, and try to upgrade the radio again after this:
Code:
USB> password 0000000000000000
USB> set 1e 1
USB> erase a0040000 c80000
USB> erase a0cc0000 c80000
USB> erase a1940000 640000
USB> set 1e 0
Don't do it if you can fix your device by any other means (warranty, service centre, etc...) because I'm not sure if it will work or not
Click to expand...
Click to collapse
Well, I too am a little "crazy" so I did as you suggest.
I tried to put Buzz's "unlock" radio v 0.0.0.0 ROM on using MaUpgradeUt_noID.exe. And guess what, it fails again but with a different error!
Error 150: ROM UPGRADE UTILITY ERROR. "This rom upgrade utility is not designed for your device. Please get proper ROM Upgrade Utility and try again!"
I attach the USB Monitor log if it proves any use?
I will try and use the official O2 ROMs and see how that goes.
Thanks again for your assistance, I truly appreciate it.
Leapy
To Leapy...
How did this problem started to you??
I have been using this phone for 1 week, after that I changed my SIM card with another one called MAGIC-SIM card, (programmable) with 8 SIM numbers.
After that day ALL the **** started!!!!!
I had problems during my dialing the number on phonepad...
when I was trying to make a call... it hang up.
After some soft reset...it didn't ask me for PIN.
After a hard reset.... on boot screen it said NO GSM
and then on antenna icon on the top of the screen the antenna had a little x on the right side.
Then the known problem ERROR 114: RADIO ROM UPDATE ERROR
I can update any rom I want but not the Radio ROM
leapy said:
I will try and use the official O2 ROMs and see how that goes.
Click to expand...
Click to collapse
well, I tried the O2 update and just got the generic "CID" error - twice. So I guess I am no nearer fixing this issue...
All advice welcome.
Leapy
leapy said:
Well, I too am a little "crazy" so I did as you suggest.
[...]
I attach the USB Monitor log if it proves any use?
Click to expand...
Click to collapse
Sorry but the capture was from the erase commands... not from the failed radio flash... please try to flash 0.0.0.0 radio again and attach the right capture... also make sure activesync is not running when starting the radio upgrade, and if it fails once, run MaUpgradeUtility twice without disconnecting the device from USB.
my friend got the exact same problem with his EXEC, and send it back to O2, they charge him apprx USD500 for mainboard replacement.....(fiuhh.....)
pof said:
Sorry but the capture was from the erase commands... not from the failed radio flash... please try to flash 0.0.0.0 radio again and attach the right capture... also make sure activesync is not running when starting the radio upgrade, and if it fails once, run MaUpgradeUtility twice without disconnecting the device from USB.
Click to expand...
Click to collapse
Thanks for your continued assistance.
I tried twice with the 0.0.0.0 radio ROM and this time the error has reverted to Error 114 again. With both these attempts, I noticed that the displayed "currently installed" ROM versions were blank - previously I saw the actual on-board version numbers. Not sure if that indicates anything?
Capture logs attached:
leapy said:
Not sure if that indicates anything?
Click to expand...
Click to collapse
That indicates you previously had activesync enabled and now don't.
Exactly same error as before, radio bootloader is not responding when the RUU sends 'rinfo' and 'rerase' commands to it, then the RUU gives up trying.
You can backup the radio ROM from another device with "d2s 60000000 00800000", and theoretically you should be able to load it into yours by using "L" command... but I'm not experienced with universal bootloader and can't say for sure if this will work and the right commands to do it... so please wait until someone reads this and can help you more than me, or research by yourself if you have the time to do it
Would appreciate your help on the following issue (amoled display):
- phone doesnt boot up, it is stuck to a screen showing htc in the middle and 4 small triangles in the corners; if I unplug the pc cable it goes to a RUU menu
- no access to recovery or bootloader menus (by holding power + vol down/back)
- installing stock RUUs dont work; there is a 110 error saying that the RUU is not complete (tried 5-6 RUUs, both 2.1 and 2.2). there is a progress bar on the phone's screen that is normally green, but turns red when the radio is being written (as per the install wizard on the pc) and there is another triangle showing up at the end of the progress bar
- fastboot oem boot restarts the phone, but then it gets stuck to the white screen having htc in the middle (like when you start up the phone and after this quietly brilliant shows under htc, for me it doesnt go beyond this initial point)
- fastboot reboot-bootloader restarts the phone into the same 4triangles screen with htc in the middle
- adb doesnt work as it doesnt show my device
- any power + vol down/back combination brings the phone to the 4triangles screen
- if I run the stock RUU after fastboot oem boot (white screen with htc in the middle) there is a menu showing up on top of the white screen showing up the progress (1-bootloader, 2-radio_v2, 3-radio, then system, recovery, user data, etc.); bootloader is updated ok but then it gets stuck when updating radio_v2 and doesnt move further from that point)
- after the RUU install fails, I plug out the pc cable and see the RUU menu; depending on the RUU that I try to flash the hboot version changes up and even goes down after, but the firmware (what the RUU installer "sees" on the phone) and radio (seen on the RUU menu) remains the same: 1.21.405.1 and 4.06xx; the date on the RUU menu also changes depending on the RUU that I try to flash
Any suggestions to get my desire unbricked?
Bit of a background to the problem:
- rooted (unlockr) and was having Paul's r3 rom (2.1)
- updated the radio to 5.10xx
- got into silly restarts when using gps and thought to reflash a new rom and went for Paul's r8
- restarts were there also when using the phone normally
- thought to re-do all the rooting, wiping out everything from the phone, etc; so having r8 as the rom (pre-baked version) I started the rooting process with creating again the goldcard, etc etc
- error message at some point saying partition update fail (following the steps from theunlockr as I did the first time when rooting) and then the phone got to this triangles screen with htc in the middle
- strange though that this screen is different than the one when I first rooted when there was just one big triangle in the middle
Thanks a ton guys!
I've seen a few posts about this screen with the 4 triangles, but never seen the result of any potential fixes, or if it was ever actually fixed.
Just an idea, but it was maybe a bad radio flash if you are saying it started playing up after that? Unfortunately a bad radio flash is fairly terminal so I hope that's not your problem.
Good luck with this one and if you get it fixed then post the result here if you don't mind!
Will definitely post the solution when found; so far though nobody has any thoughts around what might be the reason behind this problem and how to get around it. I dropped a few PMs to the people that had this problem in the past and contacted Paul at Modaco, but so far no replies...
You can fix this with an RUU, I've had the same issue when I unplugged too early after flashing, but you are asking for help in the wrong section.
thought that the dev's section is where the best knowledge exists...
about the RUU process, I am trying to flash stock RUU.exe files, but there is a problem when the radio is being written and then I get a 110 error from the RUU install wizard saying that the RUU is incomplete.
for you the RUU install worked smoothly?
If you get a write error during an RUU flash (i.e. while the flashing is taking place, not before) it probably means there's a hardware fault.
Could be hardware, but I find it hard to believe as the phone is new and it is network locked, hence I didnt even use it for real, apart from some wifi and gps activities. Besides, the phone worked very well when I first rooted with Paul's r3 and the whole mess with restarts when using gps started after I upgraded the radio to 5.10xx having a 2.1 OS.
I feel that the problem started when I tried to root the phone being on Paul's r8 2.2 OS (tried to root with a 2.1 system and then it got messed up in the process).
I am not saying that it is not hardware as it is a possibility, but still think that it might be a messy software aspect, as if the radio is messed up from a hardware perspective, then at least the system should boot up and then wifi, gps, gsm and the things that are controlled by the radio shouldnt work...but somehow the OS should start-up.
Basically I dont get a write error, it's just that the error comes up when the radio is being written, hence I think that there is something wrong with the radio set-up that I have now on the phone...
Maybe somebody knows how to flash the system from scratch using only fastboot in cmd (having the right zip or img files properly signed), or maybe just the radio to start with.
This is not a Development question and thus should not be posted in the Development forum.
Thread reported.
have a look here. i do not know if it helps though. and i know it is not a Desire
http://forum.ppcgeeks.com/htc-hero/118035-error-110-ruu.html
i also found this. sounds familiar? not for desire but might do the trick http://forum.androidcentral.com/htc-hero-roms-hacks/13171-110-error-ruu-1-56-fix-100-unroot-too.html
sorry if i wasted your time.
acolwill said:
This is not a Development question and thus should not be posted in the Development forum.
Thread reported.
Click to expand...
Click to collapse
Well, I thought that as various solutions to root the phone, to get past different restrictions in the OS, etc. were discussed here, it might be a good thing to develop a way to bring back to life a OS being in this situation like mine...come on...
mariosraptor said:
have a look here. i do not know if it helps though. and i know it is not a Desire
http://forum.ppcgeeks.com/htc-hero/118035-error-110-ruu.html
i also found this. sounds familiar? not for desire but might do the trick http://forum.androidcentral.com/htc-hero-roms-hacks/13171-110-error-ruu-1-56-fix-100-unroot-too.html
sorry if i wasted your time.
Click to expand...
Click to collapse
Thanks anyways man, I looked at that already, but cant get it done as I dont have adb commands available in cmd, only fastboot. Dont worry about waisting my time, I really want that these days
I had the same problem. Passed the device in service center. Changed the motherboard under warranty. It took one month's time.
but to get adb you need to download and install android sdk. look here http://developer.android.com/sdk/index.html system dependands download.
install it here are instructions on how to use if you aren't familiar with.
http://www.londatiga.net/it/how-to-use-android-adb-command-line-tool/
for anything else just use google.
i'm pretty sure that your device is fixable and you can fix it without any service center. cheers and post what ever happens.
popepope said:
Thanks anyways man, I looked at that already, but cant get it done as I dont have adb commands available in cmd, only fastboot. Dont worry about waisting my time, I really want that these days
Click to expand...
Click to collapse
I know how to use adb commands...pretty new to android and everything, but lately I roamed a lot through various things about it and learned a lot.
The problem is that adb doesnt list my phone when I run adb devices, it shows only when I run fastboot devices, I am sure you know what I mean...hence I cannot push any files to the phone, etc., at least not using adb in cmd.
That's actually the problem, that I cannot get adb to work, I only have fastboot commands. At least the way I see it now the question is how can I work with the phone to fix it just by having fastboot access in cmd.
I searched quite a lot various forums, etc, but I never came across a solution that will get things going just by having fastboot in cmd (without adb working). Maybe somebody here will come up with some magic trick...
Nerten said:
I had the same problem. Passed the device in service center. Changed the motherboard under warranty. It took one month's time.
Click to expand...
Click to collapse
How did you end up having this problem, just like that or after some update, flash, etc?
Thanks!
have a look here mate http://forum.androidcentral.com/htc...9-bricked-my-evo-but-there-away-un-brick.html
same story unfortunately, doesnt apply to my problem. in the link they use a terminal emulator, but I cant use that as it doesnt work...it's basically an alternative to using adb directly in cmd, and this doesnt work for me.
if I am to get adb functionality back, then I'm done with the problem in 5 mins probably...
thanks anyways, keeping the hope alive!
sorry idf i don't underdstand, but if you have fastboot working in your device and sdcard also then you should be able to push files to device via fastboot making as clean installs as possible.so if your device is picked up by command line type fastboot to see command list. i'am a bit comfused. pretty sure you should fix it through fastboot though.
popepope said:
same story unfortunately, doesnt apply to my problem. in the link they use a terminal emulator, but I cant use that as it doesnt work...it's basically an alternative to using adb directly in cmd, and this doesnt work for me.
if I am to get adb functionality back, then I'm done with the problem in 5 mins probably...
thanks anyways, keeping the hope alive!
Click to expand...
Click to collapse
right, I can run 2 things with fastboot in cmd: (name of the files just an example)
1. fastboot update update.zip
here I get that the archive doesnt contain android-info.txt or android-product.txt
2. fastboot flash update.img
here i get signature verify fail
for example, fastboot erase radio says FAILED, remote: not allowed
there are some fastboot commands related to the kernel and some others, but dont know how to make use of them for my problem.
sd card is accesible for sure and it is a goldcard.
I saw some linux/ubuntu methods to simulate adb usage in cmd, but I dont think it will work...will try to find an ubuntu image and mount it under windows, but dont have time now...
anyways, thanks to everybody for the suggestions and interest, maybe we'll crack it some day
You need to use an official RUU zip image - i.e. a PB99IMG.zip. Not an update.zip.
Hi guys,
i am trying to rescue my P10 lite after some bobo happened. I am hoping for getting some experts on leading me to the right path, delivering as much as possible background in the following lines.
Setup of my device:
- Huawei P10 Lite
-WAS-LX1A
-Firmware: WAS-LX1AC652B101 (DC Unlocker Information)
What (i guess) went wrong:
-I tried to SD-software upgrade my phone but obviously i used wrong firmware -or- some other issue during the update occured. I realized during update process that the phone restarted without it was finished (somewhere at ~50%)
-Now i can't boot, ending up with all same loops as further described
-Immediately after start of phone, i see Huawei logo and then following error message: ERROR MODE: Attention! Please update system again. Error Error NO: 11 (recovery image) & Error NO: 2 (load failed), each start ends up here.
-Recovery can't be entered, hard-reset didnt work
-Fastboot entering and sending commands is possible but with (Phone Locked, FRP Lock message) this somehow keeps me limited to what i can do?
What did i try so far to rescue:
-Apart from above obvious (fastboot/hard-reset/let battery go empty and try recharging again)
-Tried using DC-Unlocker to access some more info, didnt spend credits as i read to many bad experiences not leading to success
Desired outcome:
-I want to bring life back to the phone, no matter in what way either as stock ROM (best case) or certain custom ROMs i dont mind, as long as it usable again. In best case scenario not paying for it without guarantee to success (like DC unlocker etc.)
Do you guys can please shed some lights with a complete sad moron as i am
PS. i must say that i can do a lot of technical stuff on PC, but with android and especially with Huawei i am a complete noob, so if you refer me to some software or firmware please share link if possible? Otherwise i will of course try to find the appropiate with the hints coming from here.