Hello all, Let me start this off first by saying I am in no way shape or form a developer. I am just providing the Guide/Steps to install only the new radio without needing the Engineering Hboot. It also skips the steps of reflashing your boot.img and recovery image that get over written if you flash the firmware.zip
Items you will need before installing radio
-ADB and Fastboot connectivity
-S-OFF
-Radio.zip in file location that you will be executing the fastboot commands (ie. c/DNA/DNA Unclock/)
Thanks to lazarus2297 for compiling the radio zip into a fashable form to eliminate the need to reflash BOOT/Recovery
Radio ZIp- http://dl.dropbox.com/u/30538029/radio.zip
STEP 1- Verify ADB connectivity with your PC
C:\android\DNA Unlock>adb devices
List of devices attached
FA2B9S503169 device
STEP 2- Rebot Bootloader
C:\android\DNA Unlock>adb reboot bootloader
STEP 3- execute Fastboot OEM RebootRUU command
C:\android\DNA Unlock>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.159s]
finished. total time: 0.160s
STEP 4- Fastboot Flash radio.zip
C:\android\DNA Unlock>fastboot flash zip radio.zip
sending 'zip' (18514 KB)...
OKAY [ 1.989s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[radio] unzipping & flushing...
(bootloader) [RUU]UZ,radio,0
(bootloader) [RUU]UZ,radio,9
(bootloader) [RUU]UZ,radio,18
(bootloader) [RUU]UZ,radio,27
(bootloader) [RUU]UZ,radio,36
(bootloader) [RUU]UZ,radio,41
(bootloader) [RUU]UZ,radio,50
(bootloader) [RUU]UZ,radio,59
(bootloader) [RUU]UZ,radio,68
(bootloader) [RUU]UZ,radio,73
(bootloader) [RUU]UZ,radio,82
(bootloader) [RUU]UZ,radio,87
(bootloader) [RUU]UZ,radio,95
(bootloader) [RUU]UZ,radio,100
(bootloader) [RUU]WP,radio,0
(bootloader) [RUU]WP,radio,36
(bootloader) [RUU]WP,radio,73
(bootloader) [RUU]WP,radio,100
(bootloader) ...... Successful
OKAY [ 6.913s]
finished. total time: 8.904s
STEP 5- Reboot
C:\android\DNA Unlock>fastboot reboot
rebooting...
finished. total time: 0.047s
STEP 6 VERIFY BASEBAND
Thanks to JCase, DSB, Beaups and all the real developers who made S-OFF possible on the DNA
Thanks for the guide. Now we've got to try out some other radios too. The one that came with the OTA seems to have better connectivity, but that doesn't mean there are no others that are better. Any idea which ones would work?
orangechoochoo said:
Thanks for the guide. Now we've got to try out some other radios too. The one that came with the OTA seems to have better connectivity, but that doesn't mean there are no others that are better. Any idea which ones would work?
Click to expand...
Click to collapse
no clue noone else has a similar phone until the M7 comes out... the TBOLT/Evo used to have interchangeable radios but we had to flash CDMA and LTE radios separate because they are different bands...
I"m just sticking with Official radios
I took the OTA, and now have S-Off, can I still use this?
EchoX860 said:
I took the OTA, and now have S-Off, can I still use this?
Click to expand...
Click to collapse
Since you have the OTA you have the new radio.
Was told these steps would eliminate my Wifi issues.
EchoX860 said:
Was told these steps would eliminate my Wifi issues.
Click to expand...
Click to collapse
Do you still have the wifi issues?
EchoX860 said:
Was told these steps would eliminate my Wifi issues.
Click to expand...
Click to collapse
If you took the OTA, then you already have these radios.
Your WiFi issues are likely related to improper flashing of kernel/modules. When you flashed your last ROM, what kernel did you use? The 2 most popular around here are DSB's Cubed kernel, and Elkay's kernel.
You must unzip the kernel files into their own dedicated folder so you can access them.
These kernels come with a 'modules' zip file that must be flashed separately in recovery before everything will function correctly. If you're only flashing the boot.img, then there is your problem.
To flash the boot.img, you should use the IMG Flash GUI app (in Android), or via fastboot, and then immediately reboot to recovery and flash the modules.
I always also wipe cache and Dalvik cache too.
Sent from my HTC DNA
i used the eng hboot and flashed the radio fine. the wifi improved alot and i no longer need to wait for youtube to buffer lol
Sent from my HTC6435LVW using xda app-developers app
Since you took the OTA, I don't think custom kernels are compatible with it. In the development forum someone posted the new kernel and modules, flash those to fixyour WiFi issues.
Does anyone know if this radio will help GSM ?
maxtcee said:
Does anyone know if this radio will help GSM ?
Click to expand...
Click to collapse
I'm testing that now on tmo , signal is a little stronger but I haven't visited the areas I usually run into major problems. As long as it stops dropping completely I'm happy. Mostly.
Tapatalked from my HTC DNA
You can't flash this radios in hboot?
Sent from my HTC6435LVW using Tapatalk 2
You were right, I flashed the Dice Kernel, but stock modules. Stupid mistake, but it works great now.
So will i be able to run the old kernels with the new radio.img without any problems? i know, flash the boot.img in fastboot and the modules in recovery afterwards
Thank you very much for this! Any chance to post the original radios this way, too (or if someone has a link) in case reception and data speeds are actually worse with the newer radios? That way we can flash back if need be
ML417 said:
So will i be able to run the old kernels with the new radio.img without any problems? i know, flash the boot.img in fastboot and the modules in recovery afterwards
Click to expand...
Click to collapse
Yes, I'm running my phone like that right now. The radio seems better but I didn't do a before and after speed test.
orangechoochoo said:
Yes, I'm running my phone like that right now. The radio seems better but I didn't do a before and after speed test.
Click to expand...
Click to collapse
The updated radio seems to have helped my wifi speeds. Not sure about 4g though since my speeds vary from 15 to 50 depending on the time of day
Sent from my HTC6435LVW using xda app-developers app
I love the fact that we can now pick and choose which things to install.
Does anyone have the md5 of the radio . zip?
Sent from my HTC6435LVW using Tapatalk 2
Related
The basic problem I have is that the software won't apply to my phone correctly.
Software number: 1.02.605.6. Should show 2.01.605.11
Any help would be awesome.
Here is more information that I think could be useful. Please request any additional information or clarification.
I delocked, then I ran the new RUU, then unlocked it back up. I got to the point of basically having everything stock, and it showed the new 2.01.605.11 software number, but obviously I wanted everything back, so I flashed my nand backup using amon ra. I must have missed something because I'm basically back to the same spot I used to be which was that the update would randomly shut my phone down and end on this error "E:Error in /cache/fumo/OTAPkg.zip" in the recovery screen and i'd have to battery pull to make things restart..
I'm not sure if it's different now, but my baseband version shows:
0.95.00.1118r, 0.95.00.1223r
i know the first one is the new baseband. I do not have the 5 signal bars though, although I did when everything was stock for a minute before i started messing with things again.
ON the bootloader screen it shows hboot v2.11
So I think i'm really close just missing something. Is it not cool to just flash my old recovery file that i made before starting this stuff? Did I include too much information when I created it(check too many boxes).. I'm not even sure how to ask this question to be honest.
When I try to do the update itself at this point, it will download and start to apply, and then give me the same error like this one.
'E:Error in /cache/fumo/OTAPkg.zip'
Since doing everything I currently cannot use wifi, it shows "error" in the settings menu which I know is similiar to other errors people have gotten.
I would greatly appreciate any help and explanation!
Have you tried relocking your phone and doing a factory reset via the bootloader? The OTA will pop up once factory reset. This is how to applied the OTA with ease, hope this helps!
I actually did a factory reset before any of this. I should have included that in the OP. Honestly I think it was still locked when I factory reset, but I know it worked in some form because I no longer had amon-ra recovery. I'm like right on the verge of understanding all this kernal stuff on another level but obviously not there yet since I can't figure this OTA out.
So you were rooted debloated but otherwise stock, and you just relocked *which means its still rooted right?* and then factory reset, then the update will apply.. then you unlock it again.. and then you can flash back to your debloated nand backup?
Maybe i'm not understanding flash and recover.. can i not use those interchangeably?
Could my problem be that I did the factory reset before locking it back up? I thought with some methods factory reset wasn't necessary (RUU resets things regardless)..
I believe I relocked, did a factory reset, then once stock rom loaded up I downloaded and installed update. After installing the OTA was when I unlocked again, thats odd I believe once re-locked you lose root access and doing a factory reset will grant you stock unrooted rom. Try deleting the OTA zip from the sd card and redownload. The wifi not working means you had a kernel installed, reinstall stock kernel from NilsP thread and make sure to use Scott's flash tool to flash the boot.img from the kernel. You can get the boot.img from kernel in the PH98IMG.zip which resides in the kernel folder.
You might as well run the RUU for 2.01.605.11. It is the update and will probably fix everything for you. It will get you back to stock, you will just have to unlock the phone after you run the RUU and then reinstall Amon Ra to get root back.
thurst0n said:
I delocked, then I ran the new RUU
Click to expand...
Click to collapse
I've already run the new RUU.
And then you did a restore of a nandroid. Your mainver is now updated and your are trying to run an older mainver, probably why you are having so many issues. Rerun the RUU and act like it is a brand new phone that you just picked up. if you want to run a rom, install from scratch.
richii0207 said:
I believe I relocked, did a factory reset, then once stock rom loaded up I downloaded and installed update. After installing the OTA was when I unlocked again, thats odd I believe once re-locked you lose root access and doing a factory reset will grant you stock unrooted rom. Try deleting the OTA zip from the sd card and redownload. The wifi not working means you had a kernel installed, reinstall stock kernel from NilsP thread and make sure to use Scott's flash tool to flash the boot.img from the kernel. You can get the boot.img from kernel in the PH98IMG.zip which resides in the kernel folder.
Click to expand...
Click to collapse
Ok Im going to sort of "Start over soon" if I can't finnegal a way here shortly.
But I swear it showed 'relocked' in bootloader, and i was still rooted. Relocking it forces everything back to stock, but it sitll shows the updated radio, and hboot2.11
I really don't think I ever flashed a kernal unless you count amon-ra as being a kernal. Again i'm new to this and some of the terminology confuses, me so explanation to the steps helps too.
EmerikL said:
And then you did a restore of a nandroid. Your mainver is now updated and your are trying to run an older mainver, probably why you are having so many issues. Rerun the RUU and act like it is a brand new phone that you just picked up. if you want to run a rom, install from scratch.
Click to expand...
Click to collapse
Ok so basically you're saying I can't have my cake and eat it too? I will have to reset my phone up with apps and settings etc.. I don't use a ROM, I just froze and uninstalled many many things, and installed other things etc..
Is the 'E:Error in /cache/fumo/OTAPkg.zip' caused by the mainver discrepency?
I was trying to prevent starting from scratch, but I suppose backing up from my nandroid is essentially flashing a rom.. right?
Would it possible to achieve my old setup using TI as opposed to amon-ra recovery?
thurst0n said:
Ok so basically you're saying I can't have my cake and eat it too? I will have to reset my phone up with apps and settings etc.. I don't use a ROM, I just froze and uninstalled many many things, and installed other things etc..
Is the 'E:Error in /cache/fumo/OTAPkg.zip' caused by the mainver discrepency?
I was trying to prevent starting from scratch, but I suppose backing up from my nandroid is essentially flashing a rom.. right?
Would it possible to achieve my old setup using TI as opposed to amon-ra recovery?
Click to expand...
Click to collapse
I restored a nand I made before the OTA after I accepted the OTA so it can be done. I wasn't having any issues, certainly not the one you are having. My software says 1.02.605.6 since flashing the older ROM but I still show the new radios listed in baseband, and I'm not getting that error. My mainver is at 2.x. You can check what mainver your phone is on in fastboot using the following command:
fastboot getvar all
But that error is not really a mainver error, at least not like the ones that have been happening. That file you mentioned the error about is the OTA update and your phone seems to be trying to run it or something. I think what is happening is that you are restoring your nand cache and there's a trace of the OTA in there so your phone wants to run the OTA. I would bet that if you delete the OTAPkg.zip file you'll be fine. Either it's there and your phone is trying to run it or your phone thinks it's there and it's not. You might want to look in settings and see what it says about having an update.
Also, wipe your cache and dalvik cache in recovery and see if that fixes it. Especially if that OTA file isn't there, then it must be something else in your cache that wants to run the update.
If that doesn't work, then RUU again and then try restoring your nand without the cache checked. Or if you made a nand right after the RUU restore that. If you didn't, make one after you get RUU and rooted in case you need to revert back. I'm kicking myself cuz I was so excited to get my phone back how I wanted it I forgot to make one myself after I RUU'd today and of course I didn't realize it until right after I confirmed I wanted to flash the custom ROM.
feralicious said:
I restored a nand I made before the OTA after I accepted the OTA so it can be done. I wasn't having any issues, certainly not the one you are having. My software says 1.02.605.6 since flashing the older ROM but I still show the new radios listed in baseband, and I'm not getting that error. My mainver is at 2.x. You can check what mainver your phone is on in fastboot using the following command:
fastboot getvar all
But that error is not really a mainver error, at least not like the ones that have been happening. That file you mentioned the error about is the OTA update and your phone seems to be trying to run it or something. I think what is happening is that you are restoring your nand cache and there's a trace of the OTA in there so your phone wants to run the OTA. I would bet that if you delete the OTAPkg.zip file you'll be fine. Either it's there and your phone is trying to run it or your phone thinks it's there and it's not. You might want to look in settings and see what it says about having an update.
Also, wipe your cache and dalvik cache in recovery and see if that fixes it. Especially if that OTA file isn't there, then it must be something else in your cache that wants to run the update.
If that doesn't work, then RUU again and then try restoring your nand without the cache checked. Or if you made a nand right after the RUU restore that. If you didn't, make one after you get RUU and rooted in case you need to revert back. I'm kicking myself cuz I was so excited to get my phone back how I wanted it I forgot to make one myself after I RUU'd today and of course I didn't realize it until right after I confirmed I wanted to flash the custom ROM.
Click to expand...
Click to collapse
Getvar All shows this
Code:
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.11.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.01.605.11
(bootloader) serialno: 000000
(bootloader) imei: 000000000
(bootloader) product: vigor
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PH9810000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4184mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bc948b45
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
I need to go to work now, but I appreciate everyones help in this! I must be looking in the wrong spot or it's not there, cuse the OTApkg.zip i cannot find at the moment, i swear i've downloaded it like 20 times over the past 2 weeks haha
feralicious said:
I restored a nand I made before the OTA after I accepted the OTA so it can be done.
Click to expand...
Click to collapse
Same here.
thurst0n said:
Getvar All shows this
Code:
< waiting for device >
(bootloader) version-bootloader: 2.11.0000
(bootloader) version-main: 2.01.605.11
I need to go to work now, but I appreciate everyones help in this! I must be looking in the wrong spot or it's not there, cuse the OTApkg.zip i cannot find at the moment, i swear i've downloaded it like 20 times over the past 2 weeks haha
Click to expand...
Click to collapse
First of all, I would edit your post and delete your serial number and imei as I believe that is sensitive info.
So you are updated based on what you posted, did you check your baseband in settings? That will confirm your radio update. I would try wiping your cache and dalvik cache in recovery. I do think there's some trace of that update and your phone is trying to update but that file isn't there so it errors out.
After you wipe power down, pull battery and then reboot. Hopefully that fixes it.
Then go into settings and see if it shows any updates available for you.
Sent from my ADR6425LVW using Tapatalk
So, i tried to do the WireTrick and it f-ed up my phone. i lost recovery + rom and can't flash anything cuz i'm on HBOOT 1.58 S-ON. (UNLOCK HTCdev).
I wanna relock it and run the Sprint RUU.exe but i'm getting the follow error;
_____________________________________________________
C:\rootevo3dnew>fastboot oem lock
...
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [PG_ERROR] htc_pg_hdr_get(114):
(bootloader) sd_read_sector error
(bootloader) [PG_ERROR] htc_pg_part_hdr_get(166):
(bootloader) htc_pg_hdr_get failed
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 134086008 (0x7FDFD78)
FAILED (status read failed (Too many links))
finished. total time: 1.014s
________________________________________________________
Is there any other way to get Lock/Relock?
MANY THX
Sorry I may be wrong and hopefully someone will correct me if I am because I cant remember for sure but since your unlocked, you could install recovery thru bootloader with PG86100.zip. Once you get recovery then you could at least get your phone will working again...
Sent from my Rooted S-OFF EVO 3D
Hit that thanks button if I helped.
scottypeterson said:
Sorry I may be wrong and hopefully someone will correct me if I am because I cant remember for sure but since your unlocked, you could install recovery thru bootloader with PG86100.zip. Once you get recovery then you could at least get your phone will working again...
Sent from my Rooted S-OFF EVO 3D
Hit that thanks button if I helped.
Click to expand...
Click to collapse
No, I can't cuz I still s-on...
Axhole said:
So, i tried to do the WireTrick and it f-ed up my phone. i lost recovery + rom and can't flash anything cuz i'm on HBOOT 1.58 S-ON. (UNLOCK HTCdev).
I wanna relock it and run the Sprint RUU.exe but i'm getting the follow error;
_____________________________________________________
C:\rootevo3dnew>fastboot oem lock
...
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [PG_ERROR] htc_pg_hdr_get(114):
(bootloader) sd_read_sector error
(bootloader) [PG_ERROR] htc_pg_part_hdr_get(166):
(bootloader) htc_pg_hdr_get failed
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 134086008 (0x7FDFD78)
FAILED (status read failed (Too many links))
finished. total time: 1.014s
________________________________________________________
Is there any other way to get Lock/Relock?
MANY THX
Click to expand...
Click to collapse
Is there some reason you can't reinstall a recovery using adb? If you boot to bootloader, I would think you could flash your recovery image using adb commands. Then you should be able to reinstall your rom. I installed my recovery with s-on this way with no issues.
Barring that, I am not sure if the wire trick works on 1.58, I did it before I allowed my hboot to upgrade, but what happens if you try it again? Do you have anything to lose?
Just boot into bootloader, enter fastboot then in fastboot connect usb cable.
In PC you can flash downloaded recovery using "fastboot flash recovery recovery_name.img" command, just make sure that recovery image is in the same dir as fastboot.exe.
Guys, come on. I can't flash/boot recovery. that's the why i wanna relock it. when i try to boot an img, i get the msg "FAILED (remote: reproduce boot image with on-flash ramdisk error)", as far as i know it's cuz the ramdisk is empty. HELP PLEASE. lol.
Helppp!!!
Damn it! Nobody? Any one? I'm phoneless...
http://forum.xda-developers.com/showthread.php?t=1677053
read this thread. there is a command that will restore the backups in the folder with the exe file.
"(bootloader) Lock successfully..."
That line is there, more likely than not you're locked successfully. Run the RUU and see what happens
Axhole said:
Damn it! Nobody? Any one? I'm phoneless...
Click to expand...
Click to collapse
U can flash a zip ruu u just need to dl a signed ruu that u were currently on and run it then extract the zip from the .exe if ur on Windows search in the start menu %temp% delete everything and if it leaves some files that's fine then run the ruu .exe then look in the newest of the 2 folders it creates then find a file in the folder with another folder in it open that folder and find rom.zip move it to desktop and rename PG86IMG.zip place on sd and boot in bootloader and press vol + and u can try the wire trick again if u want
Sent from my PG86100 using xda premium
rockerdudelive said:
http://forum.xda-developers.com/showthread.php?t=1677053
read this thread. there is a command that will restore the backups in the folder with the exe file.
Click to expand...
Click to collapse
i tried that... no good ;-/
beneath-a-burning-turtle said:
"(bootloader) Lock successfully..."
That line is there, more likely than not you're locked successfully. Run the RUU and see what happens
Click to expand...
Click to collapse
NO my friend... it's like, "ok, you got it", then next line you have "NO WAIT, you can't get it" lol. STILL a big "UNLuCKy" ;0)
kickyoace said:
U can flash a zip ruu u just need to dl a signed ruu that u were currently on and run it then extract the zip from the .exe if ur on Windows search in the start menu %temp% delete everything and if it leaves some files that's fine then run the ruu .exe then look in the newest of the 2 folders it creates then find a file in the folder with another folder in it open that folder and find rom.zip move it to desktop and rename PG86IMG.zip place on sd and boot in bootloader and press vol + and u can try the wire trick again if u want
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
i did that and it just reboot with no changes... no errors. darn it!
Axhole said:
NO my friend... it's like, "ok, you got it", then next line you have "NO WAIT, you can't get it" lol. STILL a big "UNLuCKy" ;0)
Click to expand...
Click to collapse
Trust me, I think you got it. When I had a stroke of stupidity and relocked to take ota (which you should NEVER do), it gave me that EXACT line after it said locked successfully and I was locked just fine. Ran the ruu and was back to stock
Sent from my PG86100 using xda app-developers app
I went through similar issues but never got full update to New hboot I had to reunlock my phone flash stock rooted Rom then do wire trick but as previously stated I was still on 1.5 hboot and not sure if wire trick works on 1.58
Sent from my PG86100 using xda app-developers app
I just wanna said to y'all that I really appreciate all the help. I went to a sprint store and the technician told me that my cellphone has a "hardware failure". New cellphone, end of story. Thanks y'all.
Hey guys. I rooted my thunderbolt, and put the Liquid-ICS-v1.5-MR3-Mecha rom and the clockworkmod with touch recovery on it. All was great for the first day, second day while listening to music my music stopped and my phone could no longer see my 32gb sd card. I powered off, and reseated the sd card. Booted back up and i was able to listen to music again, for about 5 minutes, then same thing. I blew out the port with air duster and tried it again, it worked for a bit longer, but alas, it happened again. After the 4th try it could no longer read my sd card. I have an upgrade in march so i figured ill deal with it. About a week later my phone started rebooting alot. I never installed anything other than angry birds and Google play music so i could listen to my backed up music once my sd card stopped working. After about a day of rebooting randomly, it finally went into a bootloop, not getting passed the white screen. I could sometimes pull the battery and turn it back on and it would boot normally. After a while i wasn't even able to do that, so i booted into recovery, which also couldnt mount my sdcard, and wiped data, cache and dalvick. My phone booted up into liquid and I had to re set everything back up. After rebooting it, it went back to the bootloop problems. I then wiped everything again, this time wiping system as well. Nothing booted up after that past the white htc screen. I could still get into hboot and recovery though. hboot also couldnt load the sdcard when i put nothing but PG05img.zip for some reason. never found it, always came up with an error. But it would say it was trying to load pg05diag.zip instead. tried naming the zips as that too, but that didnt work either. Tried using adb to push a new rom but it would error out. Used fastboot to flash different recoveries hoping one would be able to read my sd card and i could flash a new rom. None worked, tried amon ra, twrp, and the non touch cwm. so I tried following a return to stock guide, using the tbolt.zip. that seemed promising, but I couldnt flash a new rom. My phone seemed unable to work with it. I managed to get rid of revolutionary, was still s-off, and still had amon ra. So i tried returning to stock using some .exe ruu's. but all get stuck at 56% updating the system. but I am now left with this screen:
MECHA XD SHIP S-ON
HBOOT-1.03.0000
MICROP-/
RADIO-1.49.00.0406w_1
eMMC-boot
Jan 22 2011.0.1: 10:43
RUU
I can also get the black htc screen with the 4 white triangles in the corners.
I have searched and searched and followed every guide I believed would fix it.
But at this point I believe it is bricked. Those 2 screens are all I can get to. Any help would be greatly appreciated
EDIT. I can re-lock and unlock via the HTC dev tool, but thats about it. I have used to the most up to date ruu I can find and even the oldest, when I run the ruu the wizard shows no previous version. They all get stuck at Updating system at 56%. The only way I can get to the ruu/hboot screen is to turn my phone on, plug it into the computer and then un plug it. I cant flash an zips, cant ADB, fastboot is very slim on what I can do. I have tried everything I can find. I will probably be using my insurance to get a new phone this weekend til I can upgrade, just wondering if There was any last ditch option I could try.
So you can no longer boot into recovery?
Sent from my ADR6400L using xda premium
Correct, those 2 screens are the only I can see, Hboot, which is really just the RUU screen i guess, and a black screen with htc in the center and a white triangle with exclamation points in the corners
I could do fastboot getvar all,
the only thing i can wipe is cache
Im not sure what all i can do with fastboot, but i tried flashing a new recovery and that failed, I can copy and paste the results of the recovery flash attempt once the phone charges a little.
heres the wipe results
C:\XXXXXXXXXXX\adt-bundle-win
k\platform-tools>fastboot erase userdata
erasing 'userdata'...
FAILED (remote: not allowed)
finished. total time: 0.019s
C:\XXXXXXXXXXX\adt-bundle-win
k\platform-tools>fastboot erase cache
erasing 'cache'...
OKAY [ 0.470s]
finished. total time: 0.473s
C:\XXXXXXXXXXX\adt-bundle-win
k\platform-tools>fastboot erase data
erasing 'data'...
FAILED (remote: not allowed)
finished. total time: 0.006s
C:\XXXXXXXXXXX\adt-bundle-win
k\platform-tools>fastboot erase system
erasing 'system'...
FAILED (remote: not allowed)
finished. total time: 0.006s
here is my results of getvar all
\\C:\XXXXXXXXXX\adt-bundle-windows-x86
k\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.03.0000
(bootloader) version-baseband: 1.49.00.0406w_1
(bootloader) version-cpld: None
(bootloader) version-microp: /
(bootloader) version-main:
(bootloader) serialno: XXXXXXXXXXXXXX
(bootloader) imei: 355195000000017
(bootloader) product: mecha
(bootloader) platform: HBOOT-7630
(bootloader) modelid: PG0510000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3669mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-1abb52a0
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
(bootloader) region-id: not support
all: Done!
finished. total time: 0.035s
The version main comes up blank.
this is my results when trying to flash a new recovery with fastboot
\platform-tools>fastboot flash recovery recovery-ra-mecha-3.06-gnm.img
sending 'recovery' <5776 KB>...
OKAY [ 0.959s ]
writing 'recovery' ...
<bootloader> signature checking...
FAILED <remote: 12 signature verify fail>
finished. total time: 1.959s
Your phone looks like it switched itself back to s on. I think your h boot may be corrupted.
Sent from my ADR6400L using Tapatalk 2
so are you confirming that is bricked?
I have a couple hboot PG05IMG.zip files you can flash. Hopefully this will restore your hboot to get your phone up and running again. Uploading it now... will post when they are finished.
If your phone is bricked, then trying this definitely won't hurt. Who knows... it may unbrick you.
Sent from my ADR6400L using xda premium
**Note: This will return your phone back to stock unrooted, but should hopefully get you running again**
I'm sure you know that these files must be renamed to PG05IMG.zip and be located on the root of your SD card in order to be flashed in hboot. Please check MD5 before flashing these files... it's VERY important.
FIRST FILE: http://db.tt/lBPkS4Jy
MD5: c64b4367086fff4f51ec3d5d766a0456
Rename this file to PG05IMG.zip and flash in hboot.
If your phone won't mount the SD card, pull it out of your phone and use your computers SD port or get a USB SD card reader (like $10 at Walmart) to put this file on the root of your SD card.
**You may have one update (update number 8?) that is bypassed, which is fine**
After this is finished, reboot and your phone SHOULD boot up looking fully stock with its dreadful bloat. Once it looks "good", get back to the root of your SD card and delete the file named PG05IMG.zip that you just used or rename it to anything except other than PG05IMG.zip
SECOND FILE: http://db.tt/Jy7jk9gZ
MD5: abda920f3e159fb05c00d8c54a5b8768
Put this next file on the root of the SD and rename it to PG05IMG.zip
Flash in hboot. Once finished, reboot your phone and you are done. Don't forget to take this PG05IMG.zip file off of your SD or rename it to something else.
Let me know if this worked for you.
Sent from my ADR6400L using xda premium
yeah its a no go. The only way I can turn my phone on is to plug it into either the computer or the wall, and when i do that it shows the black ruu error screen. (black with htc in middle and 4 white triangles in corners, then if i unplug my phone it will show the hboot screen, but all that shows is Ruu highlighted in orange, and the hboot version and stuff. buttons do nothing and it doesnt try to load anything from sdcard. I verified the sd card works on a different phone.
muddydog4 said:
yeah its a no go. The only way I can turn my phone on is to plug it into either the computer or the wall, and when i do that it shows the black ruu error screen. (black with htc in middle and 4 white triangles in corners, then if i unplug my phone it will show the hboot screen, but all that shows is Ruu highlighted in orange, and the hboot version and stuff. buttons do nothing and it doesnt try to load anything from sdcard. I verified the sd card works on a different phone.
Click to expand...
Click to collapse
Dang, yeah, I'm sure it's bricked then. I'm sorry man.
Sent from my ADR6400L using xda premium
RBarnett09 said:
Dang, yeah, I'm sure it's bricked then. I'm sorry man.
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
Thanks for the suggestions though
Flash the RUU in my signature with the command
fastboot flash zip PG05IMG.zip
should fix you right up
trter10 said:
Flash the RUU in my signature with the command
fastboot flash zip PG05IMG.zip
should fix you right up
Click to expand...
Click to collapse
I don't think he is able to see his device in adb. That would be the best way if he could.
Sent from my ADR6400L using Tapatalk 2
Alright thanks, I download it and give it a try when i get home. I can do some fastboot commands btw. Definately not adb though. And ive been having trouble keeping my phone charged, it doent quite charge right now that it's in this state.
Alright thank you so much man. It worked! I'm back to stock and setting it up. Ill report any problems. I'll probably go back to custom roms eventually but give me a couple days to get bored of stock first.Thank you again.
Update. The entire left side of my screen (1/4 in) didnt respond to touches, made hitting "q" annoying in portait and space in landscape really annoying. It stopped working a few months ago when I was still on stock the first time. And it didnt work on Liquid. But now it works? Weird but you seemed to have solved every problem I had, even if that one was unintentional ;P
Update** It stopped working again as soon as I updated that it was working lol
Trter10 works miracles again! Its good to see you lurking still! We miss you over here in the TB forums.
Sent from my ADR6400L using xda premium
Update**
There are a lot bugs. Have to reboot a couple times to get service, and some times it does go into a boot loop. Still beats having a brick lying around though thats for sure. Sd card still doesnt work though which was kind of dissapointing but what evs. It says its got a unrecognizable file system but won't format it, and says it was removed. Plus the all in one tool doesnt see my phone either.
It's doing an awful lot of boot looping and random restarts, haven't had service in about an hour when it does get through though. But htc sync still cant see my phone along with any other program like revolutionary or your tool. I think im just going to avoid the head ache and just send it back. I used my phone while i was bored at work a lot and since it's just being frustrating it hardly seems worth the effort. Thanks though guys.
**You may have one update (update number 8?) that is bypassed, which is fine**
Along that idea. I'm stuck rolling back from ICS to 2.3.4 +/-. I've tried a couple MUUs they seem to be only different in the last couple decimal places.
But in both instances, they both "bypassed" 1. bootloader, as well as item 8. They unpack fine, they seem to install fine, I'm prompted to press the power key upon completion. I do so. The phone starts to reboot up for normal use, but it hangs at the first sceen, which is white with green letters in the middle htc and it just stays there. I'm trying your two files in this post to see if they will get me moving. What do you think about bypassing 1. bootloader?
Thanks
Mike
I purchased a EVO 4G LTE for my sister a little while back and recently she had her boyfriend attempt to root it for her, and since I'm here it obviously didn't go over all too well. All he said he did was follow a video (which he gave me) on how to root for the newer software version. "Something happened and it didn't work so I watched another video and tried that" The phone is currently unlocked with S-ON and he flashed a working version of TWRP and cm10 couldn't figure it out and here we are. help please. Rooted using Linux. i did some reading and found out i had to flash the boot.img through fastboot. it just hangs at <waiting for device> in the terminal. Apologies if this has been answered, if so please point me in the right direction.
http://forum.xda-developers.com/showthread.php?t=1917106
Scroll down to see how to replace the files with the files from the cm10 rom that he flashed to the phone.
I forgot to mention I too am running linux, i tried to open this in wine and it wont save the files to my system. i will try this at a friends house asap and report back, thanks
BusstopBill44 said:
I forgot to mention I too am running linux, i tried to open this in wine and it wont save the files to my system. i will try this at a friends house asap and report back, thanks
Click to expand...
Click to collapse
Is adb configured right?
I use Linux and when I was son I was able to flash boot.img without problems
Sent from my EVO using xda app-developers app
jesuscash said:
Is adb configured right?
I use Linux and when I was son I was able to flash boot.img without problems
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
I'm not really sure what he did or why he even tried. How can I check adb to see if that was done correctly?
tilltheend714 said:
http://forum.xda-developers.com/showthread.php?t=1917106
Scroll down to see how to replace the files with the files from the cm10 rom that he flashed to the phone.
Click to expand...
Click to collapse
Alright, we have made some progress, I went to a buddys house and flashed the boot.img using said method flashed gapps as well.Now, i have no touch function but it does boot to the homescreen, any advice?
BusstopBill44 said:
Alright, we have made some progress, I went to a buddys house and flashed the boot.img using said method flashed gapps as well.Now, i have no touch function but it does boot to the homescreen, any advice?
Click to expand...
Click to collapse
I'm guessing it's on the latest firmware (3.16)? That update breaks the touch panel on all non-3.16 roms (which would include cm)...the only way to downgrade is to flash the tp.img from the previous firmware (3.15), which requires s-off. I would recommend going that route as it makes things a lot easier. For example, once you're s-off you won't have to fastboot flash kernels anymore. Check out the dirty racun thread in Original Development for more info. If you decide to s-off, you can flash the old tp.img zip from the 3.15 firmware to get the touch panel working for cm:
http://themikmik.com/showthread.php...dio-Collection&p=220556&viewfull=1#post220556
Otherwise, if you don't want to go s-off then you'll need to flash a sense Rom that's using the 3.16 base (which I think most if not all are now). I recommend Viper4g, runs great and has tons of tweaks like cm.
Sent from my EVO LTE
BusstopBill44 said:
Alright, we have made some progress, I went to a buddys house and flashed the boot.img using said method flashed gapps as well.Now, i have no touch function but it does boot to the homescreen, any advice?
Click to expand...
Click to collapse
Boot into bootloader and check the radio. If its 1.12.11.1210 then he took the 3.16 OTA and your only choices are what premo15 said.
premo15 said:
I'm guessing it's on the latest firmware (3.16)? That update breaks the touch panel on all non-3.16 roms (which would include cm)...the only way to downgrade is to flash the tp.img from the previous firmware (3.15), which requires s-off. I would recommend going that route as it makes things a lot easier. For example, once you're s-off you won't have to fastboot flash kernels anymore. Check out the dirty racun thread in Original Development for more info. If you decide to s-off, you can flash the old tp.img zip from the 3.15 firmware to get the touch panel working for cm: (Had to remove link)
Otherwise, if you don't want to go s-off then you'll need to flash a sense Rom that's using the 3.16 base (which I think most if not all are now). I recommend Viper4g, runs great and has tons of tweaks like cm.
Sent from my EVO LTE
Click to expand...
Click to collapse
Thanks, i decided to try and go S-OFF. I flashed the correct RUU for 3.16 and I get an error message after I flash the RUU,zip
/RabiesShot_LINUX$ sudo ./fastboot flash zip RUU.zip
< waiting for device >
sending 'zip' (659905 KB)...
OKAY [ 45.943s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
FAILED (remote: 43 main version check fail)
finished. total time: 122.961s
BusstopBill44 said:
Thanks, i decided to try and go S-OFF. I flashed the correct RUU for 3.16 and I get an error message after I flash the RUU,zip
/RabiesShot_LINUX$ sudo ./fastboot flash zip RUU.zip
< waiting for device >
sending 'zip' (659905 KB)...
OKAY [ 45.943s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
FAILED (remote: 43 main version check fail)
finished. total time: 122.961s
Click to expand...
Click to collapse
Did you run babyracun before relocking and running the ruu?
tilltheend714 said:
Did you run babyracun before relocking and running the ruu?
Click to expand...
Click to collapse
Wow, I completely looked past that, thought I read that whole page thoroughly. It looks like after I failed at that RUU it no longer has TWRP installed, I really hate asking but what can I possibly do now?
BusstopBill44 said:
Wow, I completely looked past that, thought I read that whole page thoroughly. It looks like after I failed at that RUU it no longer has TWRP installed, I really hate asking but what can I possibly do now?
Click to expand...
Click to collapse
re-flash twrp
bigdaddy619 said:
re-flash twrp
Click to expand...
Click to collapse
another error, $ sudo ./fastboot flash recovery openrecovery-twrp-2.4.2.0-jewel.img
sending 'recovery' (8032 KB)...
OKAY [ 1.277s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.107s
and tried it with 2.4.1.0, which i had before, as well.
BusstopBill44 said:
Wow, I completely looked past that, thought I read that whole page thoroughly. It looks like after I failed at that RUU it no longer has TWRP installed, I really hate asking but what can I possibly do now?
Click to expand...
Click to collapse
I don't know if you can just install TWRP again or if you'll have to go through the HTCdev unlock again. You'll need the Unlock_code.bin for the Dirtyracun process anyway so you might as well get it again.
tilltheend714 said:
I don't know if you can just install TWRP again or if you'll have to go through the HTCdev unlock again.
Click to expand...
Click to collapse
^^^^ true
I don't know if this will work since you've already tried dirtyracun; but I just used this method to achieve s off. It's ridiculously easy, and took me 5 minutes..
http://forum.xda-developers.com/showthread.php?t=2163013
tilltheend714 said:
I don't know if you can just install TWRP again or if you'll have to go through the HTCdev unlock again. You'll need the Unlock_code.bin for the Dirtyracun process anyway so you might as well get it again.
Click to expand...
Click to collapse
alright, some progress, got my unlock from HTCDEV got the unlock token, restarted the whole S-OFF process over,got through the ruu.zip. it installed, It rebooted itself instead of allowing me to "sudo ./fastboot reboot bootloader." It booted to a stock rom (which is now 3.15), I was in shock that I had her phone working again. restarted to bootloader, noticed it was locked and s-on went back to the directions and had me unlock through the unlock_token and finall had me run "sudo ./RabiesShot...which is giving me errors.
Starting up...
Testing connection...
Test 1: Rebooting into bootloader
Waiting fastboot (18/60)
Waiting...
Test 2: Booting device...
Waiting ADB... (60/60)
Test 2: Booting FAILED
Reboot device manually
Connection test failed!
After this error I rebooted into bootloader and im S-ON with unlocked. can i jump right into s-off'ing it
BusstopBill44 said:
alright, some progress, got my unlock from HTCDEV got the unlock token, restarted the whole S-OFF process over,got through the ruu.zip. it installed, It rebooted itself instead of allowing me to "sudo ./fastboot reboot bootloader." It booted to a stock rom (which is now 3.15), I was in shock that I had her phone working again. restarted to bootloader, noticed it was locked and s-on went back to the directions and had me unlock through the unlock_token and finall had me run "sudo ./RabiesShot...which is giving me errors.
Starting up...
Testing connection...
Test 1: Rebooting into bootloader
Waiting fastboot (18/60)
Waiting...
Test 2: Booting device...
Waiting ADB... (60/60)
Test 2: Booting FAILED
Reboot device manually
Connection test failed!
After this error I rebooted into bootloader and im S-ON with unlocked. can i jump right into s-off'ing it
Click to expand...
Click to collapse
Yeah, you should be able to run rabies shot again. Did you enable USB Debugging befor trying to run rabies shot? And are you running linux 32-bit?
tilltheend714 said:
Yeah, you should be able to run rabies shot again. Did you enable USB Debugging befor trying to run rabies shot? And are you running linux 32-bit?
Click to expand...
Click to collapse
thanks, and after all that s-off/on nonsense I cant s-off with a 32 gb microsd....grrrr
BusstopBill44 said:
thanks, and after all that s-off/on nonsense I cant s-off with a 32 gb microsd....grrrr
Click to expand...
Click to collapse
You can try this
http://forum.xda-developers.com/showthread.php?t=2163013
But that requires root. You don't have a 2gb card laying around anywhere?
hi lol guys
i have htc amaze x715e inst
i need custom rom like viper rom
rom
nokia alkng said:
hi lol guys
i have htc amaze x715e inst
i need custom rom like viper rom
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2167596
pbergonzi said:
http://forum.xda-developers.com/showthread.php?t=2167596
Click to expand...
Click to collapse
dear sir
s -off not slove with me
no prob
after flash viper rom
wifi not work
please help
viper?
nokia alkng said:
dear sir
s -off not slove with me
no prob
after flash viper rom
wifi not work
please help
Click to expand...
Click to collapse
What is "not slove?"
Which viper rom did you flash?
What happens with wifi?
pbergonzi said:
What is "not slove?"
Which viper rom did you flash?
What happens with wifi?
Click to expand...
Click to collapse
i use this [ROM] Viper Amaze 2.0.2 [Aroma][ Android 4.0.4 | ICS | Sense 4.1][4/15/2014]
but wifi not working
wifi not working
nokia alkng said:
i use this [ROM] Viper Amaze 2.0.2 [Aroma][ Android 4.0.4 | ICS | Sense 4.1][4/15/2014]
but wifi not working
Click to expand...
Click to collapse
Do proper wipe (data/factory reset and "format all partitions except sdcard") to re-flash rom and then re-flash. After launch again, check wifi settings to see if there are available networks.
You already upgraded phone to ICS I think, or rom wouldn't have flashed.
pbergonzi said:
Do proper wipe (data/factory reset and "format all partitions except sdcard") to re-flash rom and then re-flash. After launch again, check wifi settings to see if there are available networks.
You already upgraded phone to ICS I think, or rom wouldn't have flashed.
Click to expand...
Click to collapse
mmmmmmm
in fact befor install wip data and no available wifi networks
pbergonzi said:
Do proper wipe (data/factory reset and "format all partitions except sdcard") to re-flash rom and then re-flash. After launch again, check wifi settings to see if there are available networks.
You already upgraded phone to ICS I think, or rom wouldn't have flashed.
Click to expand...
Click to collapse
could u gave me correct rom
pbergonzi said:
Do proper wipe (data/factory reset and "format all partitions except sdcard") to re-flash rom and then re-flash. After launch again, check wifi settings to see if there are available networks.
You already upgraded phone to ICS I think, or rom wouldn't have flashed.
Click to expand...
Click to collapse
after flash viper rom
wifi error
wifi error
nokia alkng said:
after flash viper rom
wifi error
Click to expand...
Click to collapse
Go in your About Phone and give the kernel and Android Version and software, etc.
Did you upgrade the phone from GB to ICS?
pbergonzi said:
Go in your About Phone and give the kernel and Android Version and software, etc.
Did you upgrade the phone from GB to ICS?
Click to expand...
Click to collapse
good day bro
thanx
is these enugh
C:\android>cd c:\Android
C:\android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.92.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) serialno: SH289VF00271
(bootloader) imei: 357265045299516
(bootloader) product: ruby
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PH8510000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 3747mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-b411d064
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.502s
C:\android>fastboot oem readcid
...
(bootloader) cid: HTC__044
OKAY [ 0.006s]
finished. total time: 0.008s
C:\android>
please help thanx
phone
nokia alkng said:
good day bro
thanx
is these enugh
please help thanx
Click to expand...
Click to collapse
Can you still launch android into any rom at all?
pbergonzi said:
Can you still launch android into any rom at all?
Click to expand...
Click to collapse
yap viper rom
but now make auto fast restart
pbergonzi said:
Can you still launch android into any rom at all?
Click to expand...
Click to collapse
I think I bricked my phone...
now make auto restart
rom for you
nokia alkng said:
yap viper rom
but now make auto fast restart
Click to expand...
Click to collapse
If it bootloops, it's not bricked--brick does nothing at all, not even bootloop.
Go into recovery, perform "wipe data/factory reset" and "format all partitions except scared." Download this rom and copy to sdcard, then flash this rom the same way you flashed the viper rom:
http://d-h.st/His
Let me know what happens.
pbergonzi said:
If it bootloops, it's not bricked--brick does nothing at all, not even bootloop.
Go into recovery, perform "wipe data/factory reset" and "format all partitions except scared." Download this rom and copy to sdcard, then flash this rom the same way you flashed the viper rom:
http://d-h.st/His
Let me know what happens.
Click to expand...
Click to collapse
oky
this rom ruu.exe u mean flash it using twrp recovery ??
and after that flash viper rom
exe
nokia alkng said:
oky
this rom ruu.exe u mean flash it using twrp recovery ??
and after that flash viper rom
Click to expand...
Click to collapse
Just run the exe on your windows computer and see if asks you to connect the phone or if you have to connect the phone first with adb or whatever it asks. Just run the exe and see what happens. Search the forum for more information on it--I don't have time right now. DON'T flash viper after using this--just use this to get your phone stable and then see if you want to do something else with the phone, but FIRST at least get the phone stable. Maybe you will want to keep it that way and not flash anything until you become more familiar the process by reading the threads. The important thing right now is to get your phone back to stable working phone, NOT experimentation.
pbergonzi said:
Just run the exe on your windows computer and see if asks you to connect the phone or if you have to connect the phone first with adb or whatever it asks. Just run the exe and see what happens. Search the forum for more information on it--I don't have time right now. DON'T flash viper after using this--just use this to get your phone stable and then see if you want to do something else with the phone, but FIRST at least get the phone stable. Maybe you will want to keep it that way and not flash anything until you become more familiar the process by reading the threads. The important thing right now is to get your phone back to stable working phone, NOT experimentation.
Click to expand...
Click to collapse
again aloot thanx
in fact i need arabic rom
next
is this rom ruu.exe correct with s-on phone ??
pbergonzi said:
Just run the exe on your windows computer and see if asks you to connect the phone or if you have to connect the phone first with adb or whatever it asks. Just run the exe and see what happens. Search the forum for more information on it--I don't have time right now. DON'T flash viper after using this--just use this to get your phone stable and then see if you want to do something else with the phone, but FIRST at least get the phone stable. Maybe you will want to keep it that way and not flash anything until you become more familiar the process by reading the threads. The important thing right now is to get your phone back to stable working phone, NOT experimentation.
Click to expand...
Click to collapse
ERROR (156): IMAGE ERROR :crying::crying::crying::crying:
nokia alkng said:
again aloot thanx
in fact i need arabic rom
next
is this rom ruu.exe correct with s-on phone ??
Click to expand...
Click to collapse
are you there