Related
Hello,
I ran the radio OTA, followed the instructions, and after it rebooted itself it is just stuck on the htc incredible splash screen. If I hold power down and power I do get in to the boot loader, but rebooting still hangs on that splash screen. I read through the OTA thread and I didnt see any mention of this problem, any ideas?
Also, if I put PB31IMG.zip back on and let it do its thing, it tells me the version is too old. Any ideas?
did u wipe?
did u wipe?
Click to expand...
Click to collapse
LOL. I ask my son that sometimes. Just sayin'...
Warning!
Do not start a new thread with problems/questions in Development sub-forum. If you have to start a new thread, please do so in General. Else, post in the appropriate thread to which your problem/question relates. 2nd offense results in 3 day vacation. Thanks!
I'm having the same problem, and I just ran the 2.15.00.07.28 radio zip. To be honest I didn't wipe first as I thought I didn't need to. I did run unrevoked forever prior to attempting this install. I was going to right before installing CM6.. but obviously I didn't get that far. I did run a nandroid backup before hand.
So right now I'm still staring at this htc incredible splash screen. Holding power or volume down or both doesn't change anything and I'm afraid to take out the battery. Any suggestions?!
Thanks
edit: ok so I read on the 2.15 release thread that some others were having the same problem.. Am I safe to pull out the battery and try a reflash?
Reliant said:
Also, if I put PB31IMG.zip back on and let it do its thing, it tells me the version is too old. Any ideas?
Click to expand...
Click to collapse
OK, what are you trying to do? Sounds like you are trying to install the leaked OTA from early July (the one that gives 720P video recording)?
If that IS what you are attempting, it sounds like you already have it otherwise you wouldn't be getting that main version is older message. Check your hboot version, if it is .77 that is stock, .79 is the newer one I think
Are you sure you are using the correct PB31IMG.zip? The one you want is here: http://forum.xda-developers.com/showthread.php?t=726791
If you are trying to unroot and downgrade to an earlier version then you want to follow directions per this step-by-step video:
http://www.youtube.com/watch?v=eeuiURZZZds&feature=player_embedded
htc_woe_is_me said:
Are you sure you are using the correct PB31IMG.zip? The one you want is here: http://forum.xda-developers.com/showthread.php?t=726791
Click to expand...
Click to collapse
No, I was trying to update to the most recent radio from stock radio. Or do I have to update another radio inbetween? I got the zip from http://forum.xda-developers.com/showthread.php?t=752436&highlight=stuck+splash+screen, for 2.15 radio
or were you talking to the guy before me
msmith0957 said:
No, I was trying to update to the most recent radio from stock radio. Or do I have to update another radio inbetween? I got the zip from http://forum.xda-developers.com/showthread.php?t=752436&highlight=stuck+splash+screen, for 2.15 radio
or were you talking to the guy before me
Click to expand...
Click to collapse
My fault, I misunderstood.
No you can flash any radio, just dont flash the same one twice, or step on any cracks, and never walk under a ladder!
I just went from 1.03.04... to 2.05, and now just installed 2.15.. I didn't have any problems at all.
My fix
I had this exact issue, where it hangs on the HTC Incredible boot screen after trying to update the radio. I could boot into HBOOT (voldown+power) after a battery pull, and when it tried to update my PB31IMG.zip file, it would give some type of error, and when I would try and go into recovery it would jump back to the HTC Incredible boot screen and hang again.
I determined that my problem was caused either by a bad radio or bad recovery flash from the PB31IMG.zip file I had downloaded. I pulled my SD card and plugged it into my laptop using the MicroSD-to-SD adapter, deleted the PB31IMG.zip file, REDOWNLOADED the file from my laptop and stuck it back in the root of my SD card, the put the SD card back in the phone and rebooted into HBOOT and reflashed the radio/recovery. Problem solved.
I don't know if that will work for everyone, but it is exactly what happened to me.
Hope it helps,
jakewill
jakewill said:
I had this exact issue, where it hangs on the HTC Incredible boot screen after trying to update the radio. I could boot into HBOOT (voldown+power) after a battery pull, and when it tried to update my PB31IMG.zip file, it would give some type of error, and when I would try and go into recovery it would jump back to the HTC Incredible boot screen and hang again.
I determined that my problem was caused either by a bad radio or bad recovery flash from the PB31IMG.zip file I had downloaded. I pulled my SD card and plugged it into my laptop using the MicroSD-to-SD adapter, deleted the PB31IMG.zip file, REDOWNLOADED the file from my laptop and stuck it back in the root of my SD card, the put the SD card back in the phone and rebooted into HBOOT and reflashed the radio/recovery. Problem solved.
I don't know if that will work for everyone, but it is exactly what happened to me.
Hope it helps,
jakewill
Click to expand...
Click to collapse
Yeah, unfortunately this is not going to work for everyone. I was permanently disabled after trying this method. I'm still lurking around for a sure fix to avoid the same issue on my new phone.
bagery77 said:
Yeah, unfortunately this is not going to work for everyone. I was permanently disabled after trying this method. I'm still lurking around for a sure fix to avoid the same issue on my new phone.
Click to expand...
Click to collapse
Bricked?
Sent from my HTC Incredible «•» Rooted/S-off/Skyraider v2.5.2 Vanilla «•» http://www.unrevoked.com/forever
htc_woe_is_me said:
Bricked?
Sent from my HTC Incredible «•» Rooted/S-off/Skyraider v2.5.2 Vanilla «•» http://www.unrevoked.com/forever
Click to expand...
Click to collapse
Yes my phone was bricked using that method. I'm trying not to overuse the term "bricked."
Thanks for all the help.. but once I pulled the battery and turned the phone back on, apparently it booted up just fine. I guess it just needed a little push in the right direction. Once I checked the settings, the radio was indeed flashed. I got really worried over nothing I installed CM6 and everything is just fine.
First of all, sorry if this is posted in the wrong place. Im pretty new to all this and don't really know how things work here.
I think im pretty buggered, and im pretty far out of my depth now. Im just posting to see if anything can be done or if it's already too late. Sorry if im missing something obvious that can fix this, however after 3 days of messing with this stuff my brain is starting to blur lol. Ok so here it is:
Tried updating to froyo via the OTA update pushed out recently. That failed and ive tried various ways of getting froyo to install over the last few days using Clockworkmod recovery. I ended up pushing a load of system files onto my phone via adb just to let the updater-script get past assert's. The point is, this was obviously a bad idea as I now have some kind of messed up copy of froyo installed which will not boot up past the HTC splash screen. Problem: the half-cocked update replaced the Clockworkmod recovery with the stock recovery so I now cannot use nandroid to push a backup back onto the phone
To make things worse when I boot into the stock recovery I also can't get into adb/shell, it detects the device but just says offline. Tried a lot of things to get round this but nothing has worked. So as ive got stock recovery and can't seem to get into adb anymore it would appear ive pretty much run out of options unless something can be done with fastboot... I don't know what im doing with that though so any help would be appreciated.
HTC Wildfire T-Mobile UK
S-ON
HBoot - 1.01.0001
Radio - 3.35.20.10
Recovery - Stock
Im at the end of the road here. If anyone has any ideas to try I would be very very grateful, otherwise il have to go see how much T-Mobile wants to repair it
Thanks in advance !
Undeadllama said:
First of all, sorry if this is posted in the wrong place. Im pretty new to all this and don't really know how things work here.
I think im pretty buggered, and im pretty far out of my depth now. Im just posting to see if anything can be done or if it's already too late. Sorry if im missing something obvious that can fix this, however after 3 days of messing with this stuff my brain is starting to blur lol. Ok so here it is:
Tried updating to froyo via the OTA update pushed out recently. That failed and ive tried various ways of getting froyo to install over the last few days using Clockworkmod recovery. I ended up pushing a load of system files onto my phone via adb just to let the updater-script get past assert's. The point is, this was obviously a bad idea as I now have some kind of messed up copy of froyo installed which will not boot up past the HTC splash screen. Problem: the half-cocked update replaced the Clockworkmod recovery with the stock recovery so I now cannot use nandroid to push a backup back onto the phone
To make things worse when I boot into the stock recovery I also can't get into adb/shell, it detects the device but just says offline. Tried a lot of things to get round this but nothing has worked. So as ive got stock recovery and can't seem to get into adb anymore it would appear ive pretty much run out of options unless something can be done with fastboot... I don't know what im doing with that though so any help would be appreciated.
HTC Wildfire T-Mobile UK
S-ON
HBoot - 1.01.0001
Radio - 3.35.20.10
Recovery - Stock
Im at the end of the road here. If anyone has any ideas to try I would be very very grateful, otherwise il have to go see how much T-Mobile wants to repair it
Thanks in advance !
Click to expand...
Click to collapse
You'll need a goldcard and an RUU. Look up how to make a goldcard and let me know when you have one
Wow, thanks for the quick reply
I did try creating a goldcard yesterday (using android.modaco.com/content/software/308798/pc-application-goldcardtool/). So assume I DO have one for the time being...
however if it doesn't work and I need to create a new goldcard:
Since I can't get into adb or boot up android and therefore can't access my sd card through my phone I presume il have to go out and buy a cheap card reader tomorrow.
Also, I have to run this command again:
adb shell cat /sys/class/mmc_host/mmc1/mmc1:*/cid
But if I can't get into adb how would I go about doing this, can I get the CID of the sd card from a card reader?
As for the RUU, there's many to choose from on shipped-roms.com, does this sound about right?
RUU_Buzz_TMO_UK_1.14.110.1_Radio_13.45.55.24_3.35.15.19_release_130442_signed.exe
Thank you so much for your help.
This this a decent guide from Paul over at MoDaCo.
Ok disregard my last post about a card reader... I managed to borrow a friends android phone since it appears goldcard's are specific to the sd card, not the phone. So after following the instructions I now definitely have a goldcard.
Also have the RUU mentioned in the previous post.
RUU_Buzz_TMO_UK_1.14.110.1_Radio_13.45.55.24_3.35. 15.19_release_130442_signed.exe
Is this right, and what do I do with these now to get them on my phone? Ive tried running the RUU whilst in Hboot and in recovery but it wont recognise my phone, presumably because adb isn't working.
Thanks again for the help.
There is another way to do it when it can only get into hboot. I'll look today for the method and let you know.
Sent from my HTC Wildfire using XDA App
Ah I did manage to get round it in the end. Using the PC49IMG.zip hboot method. Tried pulling the rom.zip from the temporary files that are made when running the 1.14.110.1 RUU. But obviously as I had a newer hboot or bootloader or whatever it was and it wouldn't let me downgrade back to this version. So I went for the newest one, 2.22.405.1 I think it was. With that in the root of the sdcard everything was up and running again after it had finished installing over the top of the messed up system.
Only worked because T-Mobile's OTA was a slightly older version 2.21.110.2, thank god there was a newer version available on the interwebs.
Probably not the best way of doing it but im just glad ive got a working phone again.
Thanks for replying though.
Just on a side note... its bloody ridiculous that its so hard to downgrade android!!! It causes people like me, who don't really know what they're doing, large quantities of banging-head-against-wall sessions
Undeadllama said:
Ah I did manage to get round it in the end. Using the PC49IMG.zip hboot method. Tried pulling the rom.zip from the temporary files that are made when running the 1.14.110.1 RUU. But obviously as I had a newer hboot or bootloader or whatever it was and it wouldn't let me downgrade back to this version. So I went for the newest one, 2.22.405.1 I think it was. With that in the root of the sdcard everything was up and running again after it had finished installing over the top of the messed up system.
Only worked because T-Mobile's OTA was a slightly older version 2.21.110.2, thank god there was a newer version available on the interwebs.
Probably not the best way of doing it but im just glad ive got a working phone again.
Thanks for replying though.
Just on a side note... its bloody ridiculous that its so hard to downgrade android!!! It causes people like me, who don't really know what they're doing, large quantities of banging-head-against-wall sessions
Click to expand...
Click to collapse
Yeah that's the method I was going to suggest, glad you sorted it out.
It's the fact that they lock out fastboot and stuff. If we had S-OFF from the factory, fixing these things would be so much easier
Hi,
how were you able to do this?
"Ah I did manage to get round it in the end. Using the PC49IMG.zip hboot method. Tried pulling the rom.zip from the temporary files that are made when running the 1.14.110.1 RUU. But obviously as I had a newer hboot or bootloader or whatever it was and it wouldn't let me downgrade back to this version. So I went for the newest one, 2.22.405.1 I think it was. With that in the root of the sdcard everything was up and running again after it had finished installing over the top of the messed up system. "
Thanks
Hey guys,
I have the original myTouch 3g (no 3.5mm jack).
I decided to unroot and go back to T-Mobile's original Froyo version (i know stupid idea). I attempted to use SAPPIMG.nbh file to go back to factory. Unfortunately, it didn't work so I tried using SAPPIMG.zip. Now I have a Vodaphone splash screen instead of the T-Mobile one. no access to recovery, or anything. I can access fastboot. Where did I go wrong?? (aside from wanting to un-root myself)
Any help would be appreciated!
Fastboot Screen reads:
SAPPHIRE PVT 32B SHIP S-ON H
HBOOT-1.33.0009 (SAPP30000)
CPLD-10
RADIO-3.22.20.17
May 8, 2009 21:02:32
well if u can access fast boot you can probably flash recovery again
fastboot flash recovery "recovery file.img"
or try to boot recovery
fastboot boot "recovery file.img"
I attempted to do that but I get a signature failed error and booting recovery file just leaves me stuck at the red Vodafone splash image. Nothing else comes on.
try finding the proper sapping.nbh file for your area / carrier.
place it in the root of your memory stick by its self. turn on your phone while holding vol down and let it flash the file. you should end up back on stock 1.5 i think just root again after. i had a similar problem like this like last week and had to start over =/
Ndokami said:
try finding the proper sapping.nbh file for your area / carrier.
place it in the root of your memory stick by its self. turn on your phone while holding vol down and let it flash the file. you should end up back on stock 1.5 i think just root again after. i had a similar problem like this like last week and had to start over =/
Click to expand...
Click to collapse
I have tried multiple different sappimg.nbh files. But the problem is that now it somehow has Vodafone files on it. So i'm not sure how to get it back to T-mobile.
Every time I try the SAPPIMG.nbh it gives me the following error: Main version is older.
If I try to use a SAPPIMG.zip I get the following error: Model ID incorrect. Everything sort of fails when it checks for the signature.
Also, when I try to upload amon ra recovery to recovery partition with fastboot I get remote: signature verify fail.
Wrong section!!!!
@crazy
You're new here... so let me warn you here and now. The Development section is for the members that want to post their work such as roms, scripts, hacks, etc. When I'm in a bad mood and I see posts in the development section that are not development related I normally just delete them. However, I'm in a good mood and decided to move it to GENERAL where it belongs. HOWEVER... next time it will dissappear. Please take a few minutes and carefully read over the forum rules and stickies before posting. We also have a search feature that works quite well (most of the time).
If I see that you posted a new thread about something that is found in a sticky, already been answered and can be found by using the search feature or against forum rules you're post will be deleted and you may even be subject to losing your membership.
Besides all of that... enjoy and welcome!
Thanks for your help @Binary.
I searched all through the forums and tried to flash a recovery through fastboot. NO go.
Next I tried the gold card method and with that I continue to get either Model ID incorrect or Main version is older. So here I am seeking guidance from everyone else who may know what I can try next.
Thanks in advance for all your help guys.
It seems like your Mytouch 3g haven't flashed recovery.img just choose a suitable image to flash. XD
Pal_Hwang said:
It seems like your Mytouch 3g haven't flashed recovery.img just choose a suitable image to flash. XD
Click to expand...
Click to collapse
How do I force flash the recovery image? Any time I try flashing any recovery image via fastboot the signature check fails. Is there an official recovery image that would work?
Any help guys? Still not running.
can you boot into system or not?
if yes,root your device and flash recovery.That's what I did yesterday.
if not,use SAPPIMG.nbh again,and then flash rec,radio/spl through fastboot.
i don't know if it helps,just try it.
edward0119 said:
can you boot into system or not?
if yes,root your device and flash recovery.That's what I did yesterday.
if not,use SAPPIMG.nbh again,and then flash rec,radio/spl through fastboot.
i don't know if it helps,just try it.
Click to expand...
Click to collapse
Thanks for your reply. I just attempted to boot into system and I can't. This is the error I get:
Code:
cannot load 'system'
I have tried multiple different versions of SAPPIMG.nbh and here is the error I get:
Code:
Main Version is older!
Update Fail!
crazydeo said:
Thanks for your reply. I just attempted to boot into system and I can't. This is the error I get:
Code:
cannot load 'system'
I have tried multiple different versions of SAPPIMG.nbh and here is the error I get:
Code:
Main Version is older!
Update Fail!
Click to expand...
Click to collapse
download this one and try it
http://www.mediafire.com/?jlm5hzzhmhk
i fixed mine with it.
edward0119 said:
download this one and try it
http://www.mediafire.com/?jlm5hzzhmhk
i fixed mine with it.
Click to expand...
Click to collapse
Woah woah woah dude. You can't just have someone flash a sappimg just because it worked for your device. He needs a specific one. That one may work, but there's the same percentage chance that it could also brick his phone.
Sent from my HTC Glacier using Tapatalk
crazydeo said:
Thanks for your reply. I just attempted to boot into system and I can't. This is the error I get:
Code:
cannot load 'system'
I have tried multiple different versions of SAPPIMG.nbh and here is the error I get:
Code:
Main Version is older!
Update Fail!
Click to expand...
Click to collapse
I tried your version and I still get the following error:
Code:
Main Version is older!
Update Fail!
DonJuan692006 said:
Woah woah woah dude. You can't just have someone flash a sappimg just because it worked for your device. He needs a specific one. That one may work, but there's the same percentage chance that it could also brick his phone.
Sent from my HTC Glacier using Tapatalk
Click to expand...
Click to collapse
Thanks Don Juan for the heads up and looking out, but i'm getting desperate at this point. I have read through almost all the threads on the forum regarding my issue. The only thing I haven't tried is the GoldCard method at this point. Unfortunately and quite bad on my part, I never made one. Now, attempting to make one without Android is almost impossible. I can't read the SD card CID on anything. I've tried a mac, windows XP, windows 7, I even tried Linux but nothing.
Any insights and words of wisdom are greatly appreciated.
crazydeo said:
Thanks Don Juan for the heads up and looking out, but i'm getting desperate at this point. I have read through almost all the threads on the forum regarding my issue. The only thing I haven't tried is the GoldCard method at this point. Unfortunately and quite bad on my part, I never made one. Now, attempting to make one without Android is almost impossible. I can't read the SD card CID on anything. I've tried a mac, windows XP, windows 7, I even tried Linux but nothing.
Any insights and words of wisdom are greatly appreciated.
Click to expand...
Click to collapse
Can you give me till tomorrow when I'll be able to sit down at a computer and give some proper guidance? One thing is for sure, if we have to make a goldcard you'll have to see if you can borrow an Android phone from a friend. What you can do in the meantime is get ANDROIDSDK installed, turn the phone on in fastboot mode plugged into the computer and run the folksingers commands from the ANDROIDSDK Tools folder
Code:
fastboot getvar version-main
Sent from my HTC Glacier using Tapatalk
DonJuan692006 said:
Woah woah woah dude. You can't just have someone flash a sappimg just because it worked for your device. He needs a specific one. That one may work, but there's the same percentage chance that it could also brick his phone.
Sent from my HTC Glacier using Tapatalk
Click to expand...
Click to collapse
I know that dude,it's just my suggestion.
crazydeo said:
I tried your version and I still get the following error:
Code:
Main Version is older!
Update Fail!
Click to expand...
Click to collapse
sorry then,I can't help anything.
DonJuan692006 said:
Can you give me till tomorrow when I'll be able to sit down at a computer and give some proper guidance? One thing is for sure, if we have to make a goldcard you'll have to see if you can borrow an Android phone from a friend. What you can do in the meantime is get ANDROIDSDK installed, turn the phone on in fastboot mode plugged into the computer and run the folksingers commands from the ANDROIDSDK Tools folder
Code:
fastboot getvar version-main
Sent from my HTC Glacier using Tapatalk
Click to expand...
Click to collapse
Thank you for helping me out Don Juan. I cannot thank you enough!
In the meantime I will ask around and see who has an Android I could borrow.
Here is the info you requested:
Code:
version-main: 2.16.151.1
So I have a MyTouch 3g w/ the 3.5mm... I'm no noob but obviously I'm farrr from expert because I've effectively softbricked my phone.
Can't get past splash screen (stuck in a boot loop @ the HTC logo). I can bring up hboot and I have fastboot access.. but that's about it. No ADB drivers, no goldcard, no recovery, nada.
When trying to push anything useful (like a recovery image) through fastboot, I get "failed: remote not allowed."
As for how I got into this mess, it started when I mixed up two SD's and ran an update.zip meant for a different phone. Ouchies Instead of immediately coming for help, I thought I could fix it by just unrooting back to cupcake. Ugh.. I seriously don't know what I was thinking.
Is there any hope left for me?
Info.....
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.0013 (SAPP31000)
CPLD-13
RADIO-2.22.23.03
Thanks so much in advance for any advice. Love this forum btw, long-time lurker & first time poster here
Update: I have recovery. I've tried factory reset, wiping cache, loading several different update.zip files.
When trying to load a recovery image through update.zip I get a verification error. Still can't load a rom.
I can get past the HTC logo now, but only the menu bar loads.. the rest of the UI doesn't, and I get a repeating "The process andriod.process.acore has stopped unexpectedly" error, along with a few other errors.... then it will shut down and go to HTC logo again, and bootloop. I have to factory reset to get past the bootloop again.
How can I load a custom recovery through recovery? I'm guessing that's my only solution right now.
Just flash 2.10.531.4 T-Mobile USA DRD35 RUU. It is official ROM (sure, your data will be deleted)
UPDATE 2: Okay, I think I know what my problem is, but I'm stuck once again.
This phone was originally rooted and running cyanogen. i mixed up two sd cards accidentally flashed a motorola rom when i was trying to reset, which was the big dumb mistake that led to me trying to fix it by unrooting, which may have been an even dumber decision lol... i know i know
i think ive got a radio/spl mismatch going on? and i still cant fix anything with no adb or debugging. and fastboot's not flashing anything... i'm about to take downtown and have someone look at it, but i really don't want to spend the $.. but the work im missing over this is $$ too haha. >_<
5[Strogino] said:
Just flash 2.10.531.4 T-Mobile USA DRD35 RUU. It is official ROM (sure, your data will be deleted)
Click to expand...
Click to collapse
Thanks.. I just tried that last night, fastboot won't pick it up, recovery is giving me errors. the exe won't do it either (but i'm not sure if that's related to the lack of adb drivers?) seems to be a permissions problem.. do i need s-off?
shortcat87 said:
i think ive got a radio/spl mismatch going on?
Click to expand...
Click to collapse
If you still have same hboot / radio as in your first post - you DON'T have mismatch
shortcat87 said:
I just tried that last night, fastboot won't pick it up
Click to expand...
Click to collapse
What error did you get?
You can run ruu but navigate into temporary directory and search for rom.nbh, copy to folder with fastboot.exe and close RUU
Then go into fastboot-mode and run
Code:
fastboot flash nbh rom.nbh
shortcat87 said:
do i need s-off?
Click to expand...
Click to collapse
NO
5[Strogino] said:
If you still have same hboot / radio as in your first post - you DON'T have mismatch
Click to expand...
Click to collapse
Thanks, that's good to know
What error did you get?
Click to expand...
Click to collapse
When flashing in hboot (goldcard and otherwise) - No error, just goes through initial loading of SAPPIMG.zip and then goes back to hboot screen like nothing happened
...in recovery - Displays E: can't open cache/recovery/command, allows to apply update.zip but then gives a failed verification error
...in fastboot - Remote: not allowed error, aborts installation
You can run ruu but navigate into temporary directory and search for rom.nbh, copy to folder with fastboot.exe and close RUU
Then go into fastboot-mode and run
Code:
fastboot flash nbh rom.nbh
Click to expand...
Click to collapse
Thanks, will try, though i haven't had success in fastboot yet
Found this post and will try that first & let you know how it goes. If nothing works, I'm looking to sell a MT3G 1.2 for someone to play with, because I can't afford to spend any more time messing with it myself
Hello, I have been having loads of problems with reception (staying in 2g mode, staying completely offline all day until I notice and toggle airplane mode, etc.), so I really wanted to try a new radio.
I started in this thread: http://forum.xda-developers.com/showthread.php?t=2115197 which was really encouraging. I got all the way up to setting up ADB and having the phone verified to be attached while in bootloader fastboot. However, every time i try to send the command: "fastboot flash radio radio.img" i get this error: failed <remote not allowed>
I have researched that error and came across multiple forums. There weren't many answers, other than that the bootloader might be locked, or isn't in s-off mode. I can confirm that my bootloader reads:"S-OFF" on the top line. So, I am thinking it is locked then?
I will update the bootloader if i absolutely need to, but I was hoping to get some last words of advice before I do. It seems like that should be the very last resort. Especially after reading that I might have to use the bootloader to flash every kernel if I use a new rom with a different kernel than the one i am currently on. I am also worried about bricking the device, although, I am pretty careful. Oh, and I don't care at all about the warranty. This phone is years past that by now.
Also, I have tried renaming the file to PD15img.zip and dropping it in the root of the SD card to attempt flashing it with HBOOT in the bootloader; but it says: "wrong zipped image". I already double and triple checked that the md5 code matched, even after renaming it.
So, any advice? is it possible that there is another way to do this besides using the bootloader? Like using CWM? I am on CWM
touch v5.8.1.0 BTW
Or, could i maybe upgrade the bootloader, use adb fastboot to change the radio, then switch back to the bootloader i am currently on to avoid complications in the future? Or, since I am still a total n00b, is there any chance I am just doing something wrong with ADB?
In case it helps for reference, this is all of the info about my bootloader that I can read while in that mode:
GLACIER PVT SHIP S-OFF
HBOOT-0.86.0000
MICROP-0429
RADIO-26.03.02.26_M
eMMC-boot
Sep 27 2010
Thank you so much for anyone who is willing to help me tackle this. This old phone has been all I can afford lately, and it has been my sole source of internet at home via tethering. Having even a marginally better radio reception would make a world of difference.
Cheers!
S off equals unlocked boot loader.
All good there.
Grab the 4ext app from
4ext.net
And install 4ext recovery, much better. Then try flashing whatever you want. Gotta be careful, Some radios can brick if you mess up.
Sent from my iPhone using Tapatalk
Thanks so much for the help. I really did like cwm touch, but I'll switch if 4ext will allow me to do this. Do you think I could mess anything up if I just tried flashing it in cwm? Also, (super n00b question here) should I rename the file to be .zip? I would assume so I just want to be certain.
kinsaturated said:
Thanks so much for the help. I really did like cwm touch, but I'll switch if 4ext will allow me to do this. Do you think I could mess anything up if I just tried flashing it in cwm? Also, (super n00b question here) should I rename the file to be .zip? I would assume so I just want to be certain.
Click to expand...
Click to collapse
Nahh Just install the app and let it do it's work.
The recovery is also touch.