Related
I was trying to redo Toast's part 1 method for root and when I flashed the PC36IMG.zip, it suddenly stopped, the screen flashed, it showed the status again, but then failed. Now whenever I try to flash a PC36IMG.zip, it loads fine, but then shows "Checking PC36IMG.zip..." After that, it takes me back to the menu, without giving me the option to flash. This is really frustrating, and I can't seem to fix it. I tried running the RUU but got a bootloader incompatible error. Please help!
What version do you have 1.3xxx or 1.47. xxx? If you have 1.47 you wil need the newer ones to root then run toast method.
Sent from my PC36100 using XDA App
Just a little heads up, ask the MOD to move this to Q & A so you don't get flamed.
does it flash the "checking sdcard for PC36...." and then go back to the bootloader? If so, you may want to assure PC36IMG.zip is on your SDCard and that it's formatted as fat32.
Sorry, wasn't sure if this should be a development or Q&A question. Mods please move. Thanks afflaq, that is the problem I'm having. I'll try reformatting the sd card and see if that helps. I just can't figure it out. Its almost like something broke in the bootloader. Anyways, I'll try to reformat and try again.
Tried a different SD card and formatted it. Still has the exact same problem. I think my HBoot is messed up. Does anyone know how I can fix it without using the PC36IMG.zip method?
Is it actually named pc36img.zip or just pc36img? If you have the .zip it won't read it. Not sure if this is your problem but troubleshooting here.
Huoter is a flame
churchwin88 said:
Is it actually named pc36img.zip or just pc36img? If you have the .zip it won't read it. Not sure if this is your problem but troubleshooting here.
Click to expand...
Click to collapse
Its pc36img.zip. I can check and make sure its not zip.zip, but I'm pretty sure it isn't. It loads, so it must have the right name, but then it says checking and after a few seconds just stops. My phone is having some major issues lately, and since I can't seem to use the PC36IMG method, does anyone know where I can pick up the latest RUU? The older one won't work, so I need the newest one even though I'll lose root. This is a freaking nightmare!
Ok, I tried the latest RUU and everything went through. I'll go follow the instructions to root it again and hopefully I'll be able to get everything working again.
Ok, I used quickroot and everything seems fine. Even loads the PC36IMG.zip's correctly now. Thanks for everyone's help. Hopefully this thread will help someone else who gets a bad bootloader.
For about the last 2 days I have been unable to receive text messages on my phone yet I can still send out. Regardless of what rom I use I am still not getting any. I even called sprint and they said it seems like a technical issue. I didn't realize it until someone from work called wondering why I hadn't responded, I just thought no one wanted to talk to me :/ haha
Come on XDA geniuses! Please save me! I don't want to get a new phone
Edit : the only weird thing that has happened in the past few days was I flashed what I thought was a CM kernel but CWM said "Updating boot " I freaked out fearing that I did something wrong (I know on a computer if you mess up boot you're introuble) and quickly restored a NAND knowing that it would restore any boot image
Sent from my PC36100 using XDA App
happened to me as well, u have 2 update ur msid... if ur on a CM ROM, do a nandroid and flash the default evo rom, or any sense rom, i used the fresh rom...
then call sprint, n tell them you cant receive texts and you want to update your msid, and they will tell u 2 go 2 your dial pad, n dial ##2...# <<<--- some numbers, cant remember... jes enter those numbers, n dey'll tell u wat 2 do, its simple... once u update the msid, ur fone will reboot, then try 2 send urself a text from another fone or frm online, it shud work now....
once the texts start working, reboot into ur recovery again n flash ur nandroid backup 2 take ur fone back 2 how it was be4
if ur not on a CM ROM, u dnt have 2 boot into recovery or do nandroid or anything, jes call sprint straight up, n tell em about not receiving texts n need 2 update msid, same stuff as above...
This has been an ongoing issue for me for a few months now. For a time i was also unable to make calls as well. The phone would ring on my side but the other person's phone would not ring at all. I called sprint and they had me update my profile and some other things and that seemed to help initially as i started receiving sms again. But to this day, i still sometimes get messages that were sent hours late. Outgoing seems ok, but the incoming are delayed from an hour to 12 hours. I read this thread and it seems like this is a sprint issue.
http://community.sprint.com/baw/message/219489
Im rooted running netarchy's latest burnt droid rom and kernel
Thanks but I dont live in Chicago.
l8agin said:
This has been an ongoing issue for me for a few months now. For a time i was also unable to make calls as well. The phone would ring on my side but the other person's phone would not ring at all. I called sprint and they had me update my profile and some other things and that seemed to help initially as i started receiving sms again. But to this day, i still sometimes get messages that were sent hours late. Outgoing seems ok, but the incoming are delayed from an hour to 12 hours. I read this thread and it seems like this is a sprint issue.
http://community.sprint.com/baw/message/219489
Click to expand...
Click to collapse
1) "Flashing boot" means "flashing /boot partition" which is where the kernel is stored. No reason to freak out about that.
2) To solve your problem, just Nandroid Backup your ROM, flash over to a stock rooted Sense ROM (You can get 3.70.651.1 from here) and from there, update your PRL and Profile. You should get a slew of texts that you hadn't been receiving, and after that you can just Nandroid Restore back to your previous ROM.
This was a bug that we on the Snap team first found while beta-testing Snap 7.6, and we also found that flashing over to Sense usually cleared it up, but updating PRL and Profile always fixed it.
Really? lol I feel like such a noob (even though i am not really one) most kernels I flash say "Updating Kernel" and etc.
Also I figured that out about an hour ago when I read that on an HTC Hero forum.
and it worked I got like 50 texts hahahaaaa!
But thanks because if I didnt find that out earlier then YOUD BE A LIFESAVER!
I'm curious though, what causes this to happen?
drmacinyasha said:
1) "Flashing boot" means "flashing /boot partition" which is where the kernel is stored. No reason to freak out about that.
2) To solve your problem, just Nandroid Backup your ROM, flash over to a stock rooted Sense ROM (You can get 3.70.651.1 from here) and from there, update your PRL and Profile. You should get a slew of texts that you hadn't been receiving, and after that you can just Nandroid Restore back to your previous ROM.
This was a bug that we on the Snap team first found while beta-testing Snap 7.6, and we also found that flashing over to Sense usually cleared it up, but updating PRL and Profile always fixed it.
Click to expand...
Click to collapse
I understand most of the main input from this thread here, and this is way aside from anything here but does it make a difference if I have a 1.77_003 PRI Version with 60674 PRL Version?
I see that they have 1.90_003 or something now? Is that updateable for my phone? Specs in my signature if that is any useful bit of info
hmsheen10 said:
Really? lol I feel like such a noob (even though i am not really one) most kernels I flash say "Updating Kernel" and etc.
Also I figured that out about an hour ago when I read that on an HTC Hero forum.
and it worked I got like 50 texts hahahaaaa!
But thanks because if I didnt find that out earlier then YOUD BE A LIFESAVER!
I'm curious though, what causes this to happen?
Click to expand...
Click to collapse
We never found out what really "caused" it, but my theory is that EPST (which only Stock-based ROMs have, not CM), "checks-in" with the radio, or keeps it in-check, and sometimes it gets a little messed up, and the EPST has to correct it.
One way to think about it I guess, is a vehicle travelling in a straight line; it won't always be straight, and needs to be corrected every now and then due to slight errors, or outside interference (wind, imperfections in the road, etc.). Random reboots, power-offs, bad updates, screwed up cell towers, and such might have a similar effect on the radio.
This is just speculation though, I have no real proof behind it.
Same problem. need help
Hi. I use this forum for a long time but it's the first time I comment. I have the same problem and it's really annoying. I am noob and I need help to do this:
1) "Flashing boot" means "flashing /boot partition" which is where the kernel is stored. No reason to freak out about that.
2) To solve your problem, just Nandroid Backup your ROM, flash over to a stock rooted Sense ROM (You can get 3.70.651.1 from here) and from there, update your PRL and Profile. You should get a slew of texts that you hadn't been receiving, and after that you can just Nandroid Restore back to your previous ROM.
I have a rooted Samsung Galaxy S Plus with custom rom 4.3.1.
Thank you
I simply have done all i can - and it seems that i cant do it right. Please consider to help me, because im noob.
Before i state my problem i should say that i have googled an crossed xda forum for 4 days and without any improvement.
Problem I have is that, my phone randomly reboots at no particular time or place - but here come the details:
First, for purpose of unlocking phone from SIM lock from carrier, it was S-OFFed and rooted by someone else (previous owner).
Rom was installed - Oxygen 2.3.2. and it worked for few months without bugs.
Then, one day it restarted and stuck in bootloops, but it came up for few seconds, or some time (but not for long), and then again restarted and so on. Eventually it held enough to do a factory reset which generally helped, but with one strange thing - clock couldnt sync and loosed about an hour for 5-6 hours (really strange).
Then i decided to try some other ROM hoping to resolve clock issue.
When I go into HBOOt it says:
--- AlphaRev ---
BRAVO PVT4 SHIP S-OFF
HBOOT-6.93.1002
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.27
Aug 10 2010 17:52:10
Then i went here -> http://forum.xda-developers.com/show...p?t=1315961URL and done REALLY step by step whole procedure.
ROM was installed, along with -> http://forum.xda-developers.com/show....php?t=1408936
It worked flawllessly for about half an hour an then started rebooting on no particular action - sometimes went up for some time few secs to 10-20 mins an then reboot and sometimes it got stuck in endless loop (only pulling the battery helped).
Since it went wrong, i tried to RESTORE previosly made BACKUP of mentioned OXYGEN ROM, but sadly, same thing happened all the time.
I was devasteted, didnt know what to do so I decided to get back to STOCK ROM via RUU. (thought it would solve the problem)
I used RUU_Bravo_Froyo_HTC_WWE_2.29.405.14_Radio_32.49.00 .32U_5.11.05.27_release_224699_signed
Phone stayed S-OFF (obviosly for AlphaRev HBOOT) but have been preety stable comparing what was happening before, in terms: restarted few times for a day and allways rebooted back. Then i inserted other SIM card ant it began again with restarts as soon it went up and been up for 10-20 secs. After few reboots, it stabilised, but had different problem: couldnt add new account, and couldnt remove one I set up at the beginning (message said that i should do FACTORY reset if i want account removed). So I did factory reset - and NOTHING HAPPENED - evrything stayed exactly as it was - with account and everything.
Then i came across BORTAKs Guide ->http://forum.xda-developers.com/showthread.php?t=1275632 and followed step one, although it doesnt exactly match my probs - in terms that my phone boots up most of the time, but restarts randomly...
So I did what I was supposed to do and installed CyanogenMod after following step 10 Amon Ra's Recovery (I have PVT4 device) but same thing continues to happen - reboots, apparently on trying to add account on phone...
SORRY FOR SUCH LONG POST, but Im out of ideas, and new to this so PLEASE< PLEASE HELP me if u somehow can...
Thanks in advice
goxyendzy said:
I simply have done all i can - and it seems that i cant do it right. Please consider to help me, because im noob.
Before i state my problem i should say that i have googled an crossed xda forum for 4 days and without any improvement.
Problem I have is that, my phone randomly reboots at no particular time or place - but here come the details:
First, for purpose of unlocking phone from SIM lock from carrier, it was S-OFFed and rooted by someone else (previous owner).
Rom was installed - Oxygen 2.3.2. and it worked for few months without bugs.
Then, one day it restarted and stuck in bootloops, but it came up for few seconds, or some time (but not for long), and then again restarted and so on. Eventually it held enough to do a factory reset which generally helped, but with one strange thing - clock couldnt sync and loosed about an hour for 5-6 hours (really strange).
Then i decided to try some other ROM hoping to resolve clock issue.
When I go into HBOOt it says:
--- AlphaRev ---
BRAVO PVT4 SHIP S-OFF
HBOOT-6.93.1002
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.27
Aug 10 2010 17:52:10
Then i went here -> http://forum.xda-developers.com/show...p?t=1315961URL and done REALLY step by step whole procedure.
ROM was installed, along with -> http://forum.xda-developers.com/show....php?t=1408936
It worked flawllessly for about half an hour an then started rebooting on no particular action - sometimes went up for some time few secs to 10-20 mins an then reboot and sometimes it got stuck in endless loop (only pulling the battery helped).
Since it went wrong, i tried to RESTORE previosly made BACKUP of mentioned OXYGEN ROM, but sadly, same thing happened all the time.
I was devasteted, didnt know what to do so I decided to get back to STOCK ROM via RUU. (thought it would solve the problem)
I used RUU_Bravo_Froyo_HTC_WWE_2.29.405.14_Radio_32.49.00 .32U_5.11.05.27_release_224699_signed
Phone stayed S-OFF (obviosly for AlphaRev HBOOT) but have been preety stable comparing what was happening before, in terms: restarted few times for a day and allways rebooted back. Then i inserted other SIM card ant it began again with restarts as soon it went up and been up for 10-20 secs. After few reboots, it stabilised, but had different problem: couldnt add new account, and couldnt remove one I set up at the beginning (message said that i should do FACTORY reset if i want account removed). So I did factory reset - and NOTHING HAPPENED - evrything stayed exactly as it was - with account and everything.
Then i came across BORTAKs Guide ->http://forum.xda-developers.com/showthread.php?t=1275632 and followed step one, although it doesnt exactly match my probs - in terms that my phone boots up most of the time, but restarts randomly...
So I did what I was supposed to do and installed CyanogenMod after following step 10 Amon Ra's Recovery (I have PVT4 device) but same thing continues to happen - reboots, apparently on trying to add account on phone...
SORRY FOR SUCH LONG POST, but Im out of ideas, and new to this so PLEASE< PLEASE HELP me if u somehow can...
Thanks in advice
Click to expand...
Click to collapse
Did you try to run RUU after flashing Alpharev downgrade to achieve S-ON gain, or you just ran it over Alpharev stock?
Also did you try to format sd card or to remove it from phone and than to boot it up?
It all seems like it was SIM unlocked by a "fake" code so that are the issues that can happen.
Plus: to gain SIM unlock you don't need S-off and root.
nlooooo said:
Did you try to run RUU after flashing Alpharev downgrade to achieve S-ON gain, or you just ran it over Alpharev stock?
Also did you try to format sd card or to remove it from phone and than to boot it up?
It all seems like it was SIM unlocked by a "fake" code so that are the issues that can happen.
Plus: to gain SIM unlock you don't need S-off and root.
Click to expand...
Click to collapse
I ran it over Alpharev... Im really new to this so i ask for help.
U say that i should:
1) flash AlphaRev downgrade to achieve S-ON gain (HOW exactly? please link to some guide if exists)
2) then run RUU
I tried formatting SD card later, removed it, even change card and latest ROM (Cyanogen) is on other SD card and its all the same...
Thanks for fast reply
goxyendzy said:
I ran it over Alpharev... Im really new to this so i ask for help.
U say that i should:
1) flash AlphaRev downgrade to achieve S-ON gain (HOW exactly? please link to some guide if exists)
2) then run RUU
I tried formatting SD card later, removed it, even change card and latest ROM (Cyanogen) is on other SD card and its all the same...
Thanks for fast reply
Click to expand...
Click to collapse
Yes, both steps. With that you will overwrite both hboot and radio to stock ones, that could be the things that made you problems. You will get S-on after flashing of RUU (I recomend 2.3) when your hboot is overwritten.
This is a good guide how to use ADB and fastboot (you will need fastboot for flashing of hboot):
http://androidforums.com/desire-all...fastboot-windows-updated-1st-june-2011-a.html
But reading your post I think that the problem is with unlocking (SIM). If a guy that sold you the phone said he did it with S-off and root he is laying, as I told you it can't be done with that. The problem can occur when you unlock the phone with a "fake code" that actually removes the part of phone's software used to check for carrier and not replacing critical parts (something like that).
There's a tool:
http://forum.xda-developers.com/showthread.php?t=943726
Try to run it and see what you will get.
nlooooo said:
Yes, both steps. With that you will overwrite both hboot and radio to stock ones, that could be the things that made you problems. You will get S-on after flashing of RUU (I recomend 2.3) when your hboot is overwritten.
This is a good guide how to use ADB and fastboot (you will need fastboot for flashing of hboot):
http://androidforums.com/desire-all...fastboot-windows-updated-1st-june-2011-a.html
But reading your post I think that the problem is with unlocking (SIM). If a guy that sold you the phone said he did it with S-off and root he is laying, as I told you it can't be done with that. The problem can occur when you unlock the phone with a "fake code" that actually removes the part of phone's software used to check for carrier and not replacing critical parts (something like that).
There's a tool:
http://forum.xda-developers.com/showthread.php?t=943726
Try to run it and see what you will get.
Click to expand...
Click to collapse
Thanks in advance, ill try everything when i setup everything properly. Will update on progress! :good:
OK, at fisrt I have removed both SIM and SD cards and then:
1) flashed AlphaRev downgrade to achieve S-ON
2) then run RUU
Inserted only SIM card, and for now without reboots - but this was only 15 mins ago, so ill keep informing about case after testing, in hope not to get another reboot ever.
What I realised is thatr I dont have recovery?
Is this supposed to be? And how will I resolve problem If something unwanted occur?
Thanks a lot for Your help!
goxyendzy said:
OK, at fisrt I have removed both SIM and SD cards and then:
1) flashed AlphaRev downgrade to achieve S-ON
2) then run RUU
Inserted only SIM card, and for now without reboots - but this was only 15 mins ago, so ill keep informing about case after testing, in hope not to get another reboot ever.
What I realised is thatr I dont have recovery?
Is this supposed to be? And how will I resolve problem If something unwanted occur?
Thanks a lot for Your help!
Click to expand...
Click to collapse
You have recovery, but it is stock one (pretty different to custom ones ).
Now after you flashed 2.3 RUU you probably have 1.02 hboot, so go here:
revolutionary.io
Download the tool and follow the process described to achieve s-off and root again (the problem you have have nothing connected with s-off and root but probably with some parts of system software which might be recovered now). During the process you will flash Clockworkmod recovery, from which you will install Superuser.apk. After that reboot the phone and go here:
4ext.net
Download Recovery updater, install it to your phone and flash 4ext recovery. Than from recovery you can restore backup you have from your old rom, but my suggestion is to go here:
http://forum.xda-developers.com/showthread.php?t=809328
and find something for you, cause I think that you have to start from scratch to have a proper software (cause you already had problems with previous one).
If you're up to Oxygen again go here:
http://download.oxygen.im/roms/
but I think that there are a few roms on previous link that are based on Oxygen, but a little bit modified with some extra options.
Well, thanks really, but for now I would like to live things as they are...
I dont mind beeng S-ON and not rooted, if phone doesnt reboot again. I just need it functioning, without advanced options.
Are U suggesting that STOCK ROM is not the way I should go?
goxyendzy said:
Well, thanks really, but for now I would like to live things as they are...
I dont mind beeng S-ON and not rooted, if phone doesnt reboot again. I just need it functioning, without advanced options.
Are U suggesting that STOCK ROM is not the way I should go?
Click to expand...
Click to collapse
It's the way I went for a long time until I started experimenting, mostly because a lack of space. After that I found the thread I posted (All things desire) and wanted to try some advanced roms (Sense 3.0, 3.5) even made some stuff on my own on that way.
http://forum.xda-developers.com/showthread.php?p=23101063#post23101063
My opinion is that stock roms are the best solution foe our device, cause it runs smoothest and I think that Sense is something that brings HTC devices above all other android devices. I've never been a fan of AOSP software but I tried it, just to see how it feels. I even used MIUI rom for some time as the first software option.
Anyway, the story with memory problem stays, but the main point for getting s-off and root again are diagnostic and flashing options cause on s-off device you can flash all crucial partitions that can cause problems (hboot and radio-see attachment) and change partition table layout to gain space (see alpharev.nl)
I hope I helped!
nlooooo said:
It's the way I went for a long time until I started experimenting, mostly because a lack of space. After that I found the thread I posted (All things desire) and wanted to try some advanced roms (Sense 3.0, 3.5) even made some stuff on my own on that way.
http://forum.xda-developers.com/showthread.php?p=23101063#post23101063
My opinion is that stock roms are the best solution foe our device, cause it runs smoothest and I think that Sense is something that brings HTC devices above all other android devices. I've never been a fan of AOSP software but I tried it, just to see how it feels. I even used MIUI rom for some time as the first software option.
Anyway, the story with memory problem stays, but the main point for getting s-off and root again are diagnostic and flashing options cause on s-off device you can flash all crucial partitions that can cause problems (hboot and radio-see attachment) and change partition table layout to gain space (see alpharev.nl)
I hope I helped!
Click to expand...
Click to collapse
Since there are no reboots yet (I really hope its in past) U have been more than helpful! :good:
I still havent inserted sd card, and been consedering of getting a new one (with higher speed).
Also, as I see that U R my countryman (ko ce kome ako ne svoj svome), U have earned a few drinks when U come to my town!
I will be updating how things are regarding of this case.
Cheers :highfive:
goxyendzy said:
Since there are no reboots yet (I really hope its in past) U have been more than helpful! :good:
I still havent inserted sd card, and been consedering of getting a new one (with higher speed).
Also, as I see that U R my countryman (ko ce kome ako ne svoj svome), U have earned a few drinks when U come to my town!
I will be updating how things are regarding of this case.
Cheers :highfive:
Click to expand...
Click to collapse
No problem, I'm holding you for your word!
If you have no reboots try to insert different carriers sim cards and see if it's still unlocked.
reboots again
nlooooo said:
No problem, I'm holding you for your word!
If you have no reboots try to insert different carriers sim cards and see if it's still unlocked.
Click to expand...
Click to collapse
Reboots again...
After half a day of normal usage, I tried inserting another SIM (but from same carrier) and it started again...
Not so often but from time to time it reboots.
So I guess, at the end it seems it is hardware fault.
One strange thing thou (and it makes me wonder): When I try removing account it says I should do Factory Reset if I want to change that basic acc. But afrer performing Factory Reset NOTHING happens? Account is still there, along with other settings and/or installed apps.
Any ideas?
Invitation still holds
Hey guys, this one is interesting.
So I have the newest and latest radio and hboot on my phone (One V CDMA), the hboot version that breaks any kind of downgrading. I've tried different ROMs, and found out that only BeyondExistence's cfx build and awidawad's RhythmicRom work with the new hboot version. while messing around, I also tried to downgrade my hboot using the RUU, extracting the PK76img.zip from it, and loading that on my SD card. That didn't work because apparently my hboot version is too new. After that I installed the RhythmRom and it worked perfectly fine ans stable, with one major problem: I can't receive text messages anymore! I can send them and they get to their destination, but when somebody answers me, I get nothing. Phone calls, 3G, Wifi, everything works, just not receiving a text message. Could it be that my failed attempt at doing the RUU broke something major? or what is going on here?
Thanks for your help!
dennisog said:
Hey guys, this one is interesting.
So I have the newest and latest radio and hboot on my phone (One V CDMA), the hboot version that breaks any kind of downgrading. I've tried different ROMs, and found out that only BeyondExistence's cfx build and awidawad's RhythmicRom work with the new hboot version. while messing around, I also tried to downgrade my hboot using the RUU, extracting the PK76img.zip from it, and loading that on my SD card. That didn't work because apparently my hboot version is too new. After that I installed the RhythmRom and it worked perfectly fine ans stable, with one major problem: I can't receive text messages anymore! I can send them and they get to their destination, but when somebody answers me, I get nothing. Phone calls, 3G, Wifi, everything works, just not receiving a text message. Could it be that my failed attempt at doing the RUU broke something major? or what is going on here?
Thanks for your help!
Click to expand...
Click to collapse
i had tried the same thing with the PK76.img.zip and everything is working for me as far as i can tell. I did go back and use a guide that took me through the steps of putting the old recovery back on it and doing an oem bootlock (i think that is what it was called) it was linked in the other thread you where in.
don't know if that would make a difference or not. did you clear the cache and everything else in the recovery as instructed?
maybe if that doesn't work just try re-installing the rythmic rom again.
don't know if any of that will help you or if you have maybe tried any of those things.
qwerty5554 said:
i had tried the same thing with the PK76.img.zip and everything is working for me as far as i can tell. I did go back and use a guide that took me through the steps of putting the old recovery back on it and doing an oem bootlock (i think that is what it was called) it was linked in the other thread you where in.
don't know if that would make a difference or not. did you clear the cache and everything else in the recovery as instructed?
maybe if that doesn't work just try re-installing the rythmic rom again.
don't know if any of that will help you or if you have maybe tried any of those things.
Click to expand...
Click to collapse
yeah I've tried pretty much everything at this point, and I still can't receive text messages. maybe it's virgin's fault, so I swapped my phone and I'll swap it back in a while to see if that changes anything. If not, I guess I need to wait for a RUU with the 1.57 hboot so that I can go back to stock... this is strange.
long story short, when I switched to Leedroids latest rom (not the RC2) I kept getting this itson app has forced closed error and when I press OK it comes back. I thought about trying it like 3 times and I realized the kernal was giving me problems so I went back to stock. I don't know if that messed it up but now only on stock rooted I have Data bu. I'm unable to text or call on either end. And ive tried to just install the ruu but adb won't even see that its there. So im lost now and the frustration has gone away lol. Please help ?
Baseband: 1.32.651.30
S-on
Thanks in advance guys
dragzer223 said:
long story short, when I switched to Leedroids latest rom (not the RC2) I kept getting this itson app has forced closed error and when I press OK it comes back. I thought about trying it like 3 times and I realized the kernal was giving me problems so I went back to stock. I don't know if that messed it up but now only on stock rooted I have Data bu. I'm unable to text or call on either end. And ive tried to just install the ruu but adb won't even see that its there. So im lost now and the frustration has gone away lol. Please help ?
Baseband: 1.32.651.30
S-on
Thanks in advance guys
Click to expand...
Click to collapse
try this one
http://dl3.htc.com/application/RUU_...IMA_SPCS_1.11_003_release_437681_signed_2.exe
or
rename the 1.32.651.30 RUU.zip to 0PJAIMG.ZIP, place it on a ext sd card formatted in FAT32 (a 16 or 32gig one should work), reboot into DOWNLOAD_MODE, agree and it should flash.
dragzer223 said:
long story short, when I switched to Leedroids latest rom (not the RC2) I kept getting this itson app has forced closed error and when I press OK it comes back. I thought about trying it like 3 times and I realized the kernal was giving me problems so I went back to stock. I don't know if that messed it up but now only on stock rooted I have Data bu. I'm unable to text or call on either end. And ive tried to just install the ruu but adb won't even see that its there. So im lost now and the frustration has gone away lol. Please help ?
Baseband: 1.32.651.30
S-on
Thanks in advance guys
Click to expand...
Click to collapse
try my recommendation in this thread, it may work!
http://forum.xda-developers.com/one-m9/help/data-messed-t3176705