Related
Tuesday night I loaded CM7, and then the Market wouldn't update my apps so I decided I would restore BAMF 1.5. After doing so, the Market just gave me "Fails" trying to update, and I could not access recovery, as I was going to do a complete wipe and reflash. Most of Wednesday, an extremely helpful & knowledgable member, Mattgyver83, tried diligently to help me rectify the situation, but to no avail. We tried to Fastboot, tried flash_image, tried fix permissions...shoot, I practically wore out adb..anyway, I ended up reverting back to stock and unrooted. I used jcase's method to revert back to stock, and that was painless, and successful. I decided last night to try rooting again, thinking a fresh root would solve my issue of not being able to access recovery. Root was successful, but I still cannot access recovery, through rom manager, or through bootloader. When I attempt it my Tbolt goes to white HTC screen, and stays there. All functions of my phone now work, and all aspects of root work, except I cannot flash anything. Rom manager shows I have clockwork recovery, but I just can't get to it.
Sorry for the long ramble. If anyone has had this issue, or if anyone knows a fix, I would appreciate it. Otherwise, I wait for Gingerbread.
Thanks
Happened to me with CM7 builds. For some reason they were erasing the recovery. Just have to reflash the recovery in Rom Manager and you'll be all set in the future.
do what i do pull batt leave out for a min, then put the batt back in and connect usb right away.
travishamockery said:
Happened to me with CM7 builds. For some reason they were erasing the recovery. Just have to reflash the recovery in Rom Manager and you'll be all set in the future.
Click to expand...
Click to collapse
Tried that, but thanks. Still just goes to white HTC screen, and stays there until I do battery pull.
jr4000watts said:
do what i do pull batt leave out for a min, then put the batt back in and connect usb right away.
Click to expand...
Click to collapse
I can get to bootloader, just not able to get into recovery.
I'm stabbing in the dark at this, but this did work for me with my Droid...
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Ie. Flash recovery and wait until the confirmation pop-up/message only takes a few seconds to pop up. If the message takes longer than 5 seconds or so, re-flash recovery and repeat until the confirmation comes up quickly.
This sounded retarded to me, but I was at the end of my rope so I tried it. It worked like a charm.
M.
monolithic said:
I'm stabbing in the dark at this, but this did work for me with my Droid...
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Ie. Flash recovery and wait until the confirmation pop-up/message only takes a few seconds to pop up. If the message takes longer than 5 seconds or so, re-flash recovery and repeat until the confirmation comes up quickly.
This sounded retarded to me, but I was at the end of my rope so I tried it. It worked like a charm.
M.
Click to expand...
Click to collapse
Thanks, but that didn't work. I think something in my os got lost when I restored BAMF from CM7.
Yea I spent a good few hours yesterday trying to help Orio out and we attempted a ton of things to try and fix the recovery issue, this post should offer a bit more insight to the methods used, this is running off memory;
adb reboot recovery failed
Reinstall latest Rom Manager apk and Flash CWM
flash latest rom manager via fastboot (CWM only)
(fastboot flash recovery /sdcard/recovery-clockwork-3.0.2.5.img)
**did not do fastboot erase recovery first**
"return to stock safely and properly" XDAthread by jcase
return to stock image [RUU], reroot, try again
try to boot into recovery via hboot
manually installed fix_permissions.sh script and busybox on rooted stock, ran.. didnt fix
tried to see if flash_image method would work, didn't
All of the above have failed and we basically tried almost all combinations. Not once would this phone get back into recovery, even after flashing the appropriate RUUs which include either stock android or CWM recovery. The only thing we have not currently attempted which might be the last thing left is to do is manually install the nandroid.sh script and do an advanced restore of the recovery image only from a nandroid backup on SD. I would rather not go down this method as it could have an undesired result, I have done it to restore a G1 back in the day but not 100% if its gonna work on a tbolt. Thankfully his phone boots, and we can get into hboot, but yea.. pretend recovery just doesnt exist at all...
Curious if anyone has any knowledge above what we have already tried.
monolithic said:
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Click to expand...
Click to collapse
I recall the same thing and its a good thought however that was mostly a generic error due to a CWM update and CM6 (I think) but either way flashing an RUU should override this shortcoming and im pretty sure that issue was worked out in CWM as well.
Not to be rude, but I don't think this question belongs in the development section.
Orio56 said:
I can get to bootloader, just not able to get into recovery.
Click to expand...
Click to collapse
do you still have the P zip file for the radio (baseband) on your SD card? if you do....try to delete it...then hold power and volume down button down....then see if you can get into recovery....
probably not going to work...but it is worth a try......
hogowner said:
do you still have the P zip file for the radio (baseband) on your SD card? if you do....try to delete it...then hold power and volume down button down....then see if you can get into recovery....
probably not going to work...but it is worth a try......
Click to expand...
Click to collapse
Thanks, but no, I deleted that after loading it. I actually reverted back to stock/unrooted last night and rerooted and the problem still remains. It's quite strange.
maybe i missed it if someone suggested this but what about flashing an older version of CWM?
shelooga said:
maybe i missed it if someone suggested this but what about flashing an older version of CWM?
Click to expand...
Click to collapse
That is what I was going to suggest. In ROM Manager at the very bottom try and flash an older version.
Sent from my ADR6400L using XDA Premium App
SUCCESS !!!
I fixed it !
Apparently, when I loaded up cm7, files showed up about the same time on my sdcard in clockworkmod download file. I deleted those files, and reflashed clockworkmod in rom manager, (which this time took like 3 - 4 minutes), and rebooted into recovery and it worked...did it again, just in case it was a fluke and it worked.
All is well now...the planets are realigned !!!
Thanks everyone for your ideas and especially thanks to mattgyver83 who helped me for something like 4 hours yesterday. Exceptional kindness !!
mods...you can close this thread.
GREAT NEWS!!!! CONGRATULATIONS!!
THANKS FOR REPORTING BACK!
This may help out other members with the same problem!!
now go ahead and start playing with your T-BOLT again!
That's a very odd solution. My first two things to try would have been:
1) fastboot:
fastboot erase recovery
fastboot flash recovery C:\some\local\path\recovery.img
You can't, well, probably shouldn't, flash a recovery from the /sdcard. When in fastboot mode I don't think the sdcard is even mounted. Either way, I think fastboot needs the img file on the local file system.
2) Create a PG05IMG.zip file with the recovery.img file in it, and flash that through HBOOT. Although this should have been done in some form or fashion when you downgraded or re-rooted, so YMMV.
I apologize in advance if this has been posted elsewhere. I've been looking everywhere I can possibly imagine for the past 3 hours trying to find a solution to no avail.
I'll get right to it. Whenever I try to turn on WI-FI or 4G, I get "Error". No description as to why, or what could be causing it, but heres what I've done.
I'm no noob when it comes to rooting. I had my original Evo rooted most of the time I had it with little to no problems. I've had the 3D since the day it came out, and I haven't felt the need to root. But I got to talking with my buddy earlier and decided I'm going to do it for the OC (and I gotta admit, Synergy looks pretty legit). I'm at hboot 1.5, so I went through the HTC unlock process, and the TWRP recovery process. Then I flashed Synergy, and I set it up, and I get this error.
So I try reflashing it, and that doesnt work. I'm thinking it could be the kernal. So i try 2-3 different kernals (listed on the Synergy thread), and I get the same error. I try a combination of different things for what seems like the next 10 hours (reality, it was about 2) and no matter what I try, I can not seem to get rid of this message. I clear all the cache/dalvik. Wipe back to factory. Hell, I even tried loading the stock ROM and this problem will not go away.
I have the PC86IMG ready to go about to flash back to stock and be done with this root process. The damage is done as far as warranties go, but I would really like to have something to show for it. Does anyone know a way to resolve this without reverting back to locked?
Did you flash the kernel via fastboot? If not the kernels don't flash with the 1.50 hboot, you need to grab the boot.img out of the rom zip and flash via fastboot. Check post 2 in the Synergy thread I believe there are detailed instructions there.
EDIT: Instructions are actually on post 2 of the Eternity thread.
Transformer Sent
Is it not possible to just flash using TWRP?
Edit: I did read that you would need to flash via Fastboot, but I thought that was just initially. So everytime I flash a ROM, I need to adb through fastboot?
That did it. Thanks so much! That was driving me crazy!
(made sure to click "thanks" too)
Ok, this is my first post so be gentle. I tried to root my sons phone and now it's useless. I went thru HTC's website to unlock bootloader due to having HBOOT 1.5. I'm unlocked and thinking life is good but, I loaded several different ROM's and get the same result. It starts to load the ROM and reboots, sometimes it goes into a safemode with the Viper Rom. I've been jacking with this for 2 days and need some help. I can't find a good link for the RUU or PG86...bla bla bla, I would take it back to stock and surrender but, can't even do that. I've installed TWRP and CWM, just to try different stuff, but get all the same reults.
I think you need to flash the boot.img separately. I'm not sure though. There's a thread for flashing with 1.50 somewhere in the development section
We're comin from a pure power source.
I am having the same issue here, I installed several ROMS, it works for a day, but then the reboot attack starts. Constant lockups and random restarts, sometimes 3 reboots in a row.
ROMs I tried to flash:
1. Xperia XE
2. Titan Trinity 3 HD
3. Nocturnal Adrenaline 1.0.2
Maybe it's the kernel, is there a list of kernels that I can flash?
This worked for me
My phone kept rebooting after root before, but I managed to fix it. This will only work if you can get into fastboot. Download the ruu file located here and run it while in fastboot. This will unroot your phone if you have S-On. After that is done, if it still loops, take out the battery and count to five, then put the battery in and hold the power button on the phone until the phone starts to turn on normally. That fixed my problem, hope it fixes yours. You may have to update after you get your phone started and you will lose all your data. Sorry about the link, I updated to one that has a working download.
armydude13090 said:
My phone kept rebooting after root before, but I managed to fix it. This will only work if you can get into fastboot. Download the ruu file located here and run it while in fastboot. This will unroot your phone if you have S-On. After that is done, if it still loops, take out the battery and count to five, then put the battery in and hold the power button on the phone until the phone starts to turn on normally. That fixed my problem, hope it fixes yours. You may have to update after you get your phone started and you will lose all your data. Sorry about the link, I updated to one that has a working download.
Click to expand...
Click to collapse
Unroot my phone?
Is it possible to re-root it?
Thanks all for the posts. I will give some of this a shot and see what happens. I can get to fastboot, and have loaded a couple of things thru the cmd prompt to try and help, but nothing so far. I'm not really sure if the kernel thing is what's stopping the roms for loading. I can't get the S-OFF, I'm unlocked. I can send anything I want thru the cmd prompt, and also flash zips thru twrp or cwm. Would like to start over but ca't even find a way to do that. Thanks again for the posts.
Cardmastr, we're on the same boat, pg86 takes forever to download, so as I'm waiting patiently, keep me in on the loop with what you're doing.
RUU didn't cut it, kept failing. have not found an image file to flash thru the cmd prompt. Still no luck. What can I throw into fast boot that might help me?????!!!!!!
When I started flashing after using HTC Unlock, I ran "fastboot boot recovery.img" - which booted TWRP with the necessary permissions. Then I wiped everything and flashed the ROM. Haven't had any issues with the ROMs I've tried.
Which recovery did you install? Twrp 1.1.1 is your best bet.
The 2.x version twrp or cwm do not okay nice with some phones.
S3nt from my 3D wond3rland
I used the TWRP 1.1.1. Might of messed up with some of the cmd prompt stuff I'm going back thru.
thefsfempire said:
When I started flashing after using HTC Unlock, I ran "fastboot boot recovery.img" - which booted TWRP with the necessary permissions. Then I wiped everything and flashed the ROM. Haven't had any issues with the ROMs I've tried.
Click to expand...
Click to collapse
Everyday is Halloween for u dude!! UR a Monster! This little tidbit hooked me up. Thanks to you we are back in game.
When installing a ROM, doesn't it wipe /data, /system, etc for us?
Hello all,
I have a question that has not been answered after many hours of searching. Hopefully I'm just dumb, and my buddy's stock firmware and data isn't hosed. I'm trying to get his stock firmware running again so I can back it up safely.
What I've done:
Tried to flash CWM's update.zip via stock recovery (signature verification failed on the three different zip's I could find in the forums and various links)
Used Heimdall to push "cmenard-T959-CWM" zImage (this worked, and I get a different screen at boot)
The phone boots to the point of the T-Mobile splash screen with the annoying shriek sound, but goes to a black screen after. If i touch any of the soft buttons, they light up and remain lit. It'll stay like that for at least 20 minutes.
Is it possible to re-flash the system partition and not the data partitions using ODIN? Is that even feasible? Like I mentioned above, I'd like to get the stock firmware running such that I can make a good backup of it with all the user data intact. I haven't been able to because the CWM+root wouldn't flash.
Any suggestions or insight would be greatly appreciated.
thanks in advance!
Well as long as you don't format the internal SD, any pictures and videos and things should remain intact.
Here is a similar thread. See if it resembles your issue.
http://forum.xda-developers.com/archive/index.php/t-794869.html
Toast6977 said:
Well as long as you don't format the internal SD, any pictures and videos and things should remain intact.
Here is a similar thread. See if it resembles your issue.
http://forum.xda-developers.com/archive/index.php/t-794869.html
Click to expand...
Click to collapse
Thanks for the suggestion, Toast. I don't believe the internal SD has been messed with, and I don't plan to mess with it either. The thread you linked is not quite related to my issue, as far as I can tell.
I am able to get into Download Mode, and the Stock Recovery mode as well. However every time I try to flash an 'update.zip' with the Stock Recovery, I get an error about Signature Verification Failure.
After stepping back from it for a day, I think I've gained some clarity. Since all I've done is flash a different Kernel with Heimdall, I'm going to try to flash a stock kernel then see what happens.
Is this phone on stock Froyo or have you got it back to JFD (eclair)?
If Froyo, that's the problem. Using Odin back to Eclair and run update.zip. It won't work from stock Froyo.
*-*- I made some assumptions in my previous post. The shrieking sound. Black screen. Lights stay lit. Sounded like a poltergeist.
Glad you can get in download mode and recovery.
The old 2E vs 3E problem. Nice catch Toast
Give this a whirl: recovery 3e modified to work like recovery 2e
Might have to ABD push it to your internal SD card though.
Toast6977 said:
Is this phone on stock Froyo or have you got it back to JFD (eclair)?
If Froyo, that's the problem. Using Odin back to Eclair and run update.zip. It won't work from stock Froyo.
*-*- I made some assumptions in my previous post. The shrieking sound. Black screen. Lights stay lit. Sounded like a poltergeist.
Glad you can get in download mode and recovery.
Click to expand...
Click to collapse
Woodrube said:
The old 2E vs 3E problem. Nice catch Toast
Give this a whirl: recovery 3e modified to work like recovery 2e
Might have to ABD push it to your internal SD card though.
Click to expand...
Click to collapse
hahaha poltergeist!
Wow, so I'm glad I asked. I wouldn't have known about this issue, as I do not have any history with this device.
I know that the ROM is currently 2.2, and the Android System Recovery is showing "3e".
If I understand correctly, once I'm ready to flash up to ICS, I'll need to ODIN back to 2.1 to get Android System Recovery "2e", which will let me flash 'update.zip' packages freely. Then I flash an 'update.zip' to get CWM, then flash CM7, then CM9 (and CM9 is my intended destination).
The things mentioned in the thread you linked do appear to apply to my situation.
However I still want to get the stock OS booted and working, then do a Nandroid backup of it. (it's the computer tech/security pro in me. Since I'm new to this device, I -tried- to read up on everything first, and didn't want to make a change without being sure it would work.)
Does anyone happen to know if flashing a stock kernel over the 'cmenard' kernel will harm anything, and hopefully get a successful boot? Again, I'm trying to get the stock ROM booting again in order to verify I have everything I need off of it, then do a nandroid backup. Flashing to CM9 will come afterwards.
Ok, here are some things for you.
Here is a kernel pack that you can use. Read the OP because there are Froyo AND Gingerbread kernels in there.
[KERNELS] Moped_Ryder SGS Kernel Pack v2 [20+ Froyo/GB Kernels]
I really suggest using something like BaliX 1.2 or BaliUV kernels to make your back up. They are smooth, fast and OC/UV-able. To flash just Wipe /cache, /dalvik -> flash kernel -> Wipe /cache, /dalvik (I also fix permissions too bc that is the way that I learned and I just do it that way all the time). Reboot and Bam!! you should be able to get to the point that you can make a backup.
Look in my signature, there are downloads and flashables that are direct download linked. There is also an ICS install guide that can help your journey. Once you have your backup, then use Odin from the Toolbox in my signature and flash back to stock JFD. From there you will be able to follow my guide.
If you need any files, just let me know and I will upload them when I get home (won't be until late though, i have plans right after work).
Using HB, can I choose any theme? I am not so acquainted with the Theme chooser and boot animation of my phone. I flashed a boot animation zip yesterday and it was stuck in "ANDROID" screen. So I have to flash again. I never used any boot animation and themes in my phone yet. I want to know about them.
Sent from my SGH-T959 using xda app-developers app
Wrong thread. Put that question in the Jelly Bean Banter thread. No need to hijack this thread until we get OP up and running.
Ugh, so I've been on vacation for a while, and since being back I've been super freaking busy =(
Finally spent some time with the phone tonight. Took some fiddling to get the right drivers working for the phone on my Win7x64 laptop.
In any case, I checked out that Kernel thread, and extracted the Bali kernel. Since I had flashed successfully(?) with Heimdall at first, and I'm becoming more familiar with it, I used it to flash the Bali_1.8.8-zImage. That appeared to work, as I get a new boot screen/animation with the Bali logo.
However, after the Bali logo disappears, the T-Mobile animation+sound plays, and then gives me a black screen. The screen is on (backlight is on) but all black. Also, if I touch a soft-button, they'll light up and the phone will remain in that state for as long as I can stand to wait. (one episode of Archer)
So, it's doing the same thing as before, but with a new boot logo/animation.
I wonder if something else in the ROM has been messed up? Should I forget trying to save it, and just use ODIN to flash a whole new rom/kernel package? I'll talk to the owner tomorrow and see if he's now willing to do that.
I also wonder if I was wrong to use Heimdall again, instead of using the CWM method. Please correct me if I'm wrong, but I think those two methods end up doing the exact same thing. Is one method more reliable than the other?
Bah, this sucks; I have more questions than answers at this point =( Any ideas, Woodrube, Toast?
maxpeet said:
Ugh, so I've been on vacation for a while, and since being back I've been super freaking busy =(
Finally spent some time with the phone tonight. Took some fiddling to get the right drivers working for the phone on my Win7x64 laptop.
In any case, I checked out that Kernel thread, and extracted the Bali kernel. Since I had flashed successfully(?) with Heimdall at first, and I'm becoming more familiar with it, I used it to flash the Bali_1.8.8-zImage. That appeared to work, as I get a new boot screen/animation with the Bali logo.
However, after the Bali logo disappears, the T-Mobile animation+sound plays, and then gives me a black screen. The screen is on (backlight is on) but all black. Also, if I touch a soft-button, they'll light up and the phone will remain in that state for as long as I can stand to wait. (one episode of Archer)
So, it's doing the same thing as before, but with a new boot logo/animation.
I wonder if something else in the ROM has been messed up? Should I forget trying to save it, and just use ODIN to flash a whole new rom/kernel package? I'll talk to the owner tomorrow and see if he's now willing to do that.
I also wonder if I was wrong to use Heimdall again, instead of using the CWM method. Please correct me if I'm wrong, but I think those two methods end up doing the exact same thing. Is one method more reliable than the other?
Bah, this sucks; I have more questions than answers at this point =( Any ideas, Woodrube, Toast?
Click to expand...
Click to collapse
Wrong they are not the same. cwm can do the work without a PC beside you can erase, back up , restore and flash, which make our life easier, heimdall or Odin ," I prefer odin "are the last option when you can't fix it with cwm
To fix your phone use Odin or heimdall and go back to stock don't worry all your files, photo, music, will be safe. Then
1 get root on you , if you don't how ask
2 get cWm
3 do a nandroid back up
4 have fun flashing all roms you want lol
Sent from my SGH-T989 using xda app-developers app
Yeah, I would just Odin back to stock JFD w/ repartition checked...
Then I'd flash something real stable for him. There are lots of stable ROMs to choose from. I used Bionix V for a long time before moving onto Jelly Bean.
Since the phone belongs to someone else, I'd stick with something lower than JB though. 911 can have/has issues.
Toast6977 said:
Yeah, I would just Odin back to stock JFD w/ repartition checked...
Then I'd flash something real stable for him. There are lots of stable ROMs to choose from. I used Bionix V for a long time before moving onto Jelly Bean.
Since the phone belongs to someone else, I'd stick with something lower than JB though. 911 can have/has issues.
Click to expand...
Click to collapse
do no check de re-partition button and use a .pit file follow this tutorial and you will be fine
http://forum.xda-developers.com/showthread.php?t=848737
Ok so here's the deal...
I was running ViperRez ROM and decided it was time for a change and found a few ROMs I wanted to check out. Tried EclipticRez, kept force closing and rebooting before or just after I could finish the phone set up. Tried Nils Business, no luck. So finally tried to load MIUI for ICS and ran into trouble.
Each time before loading these ROMs I used Clean Wipe to wipe before loading the ROM. I am S-on. Unlocked. HBOOT- 2.11
So here's where my trouble is... Normally when a ROM fails to work, I'd simply reboot into recovery, wipe, and load a different rom via zip from SD card. The problem I'm having, besides the ROM not loading and getting stuck on the HTC flash screen is, I cant get into recovery. I can reboot into the bootloader screen, get to fastboot. When I try to select recovery the phone goes black, flashes something quickly on the lower part of the screen with CWM recovery looking logo, then reboots and sticks on the HTC white screen. Another issue, my battery will no longer charge via phone charger, so I had to go out and buy a battery charger today to even get my phone running again since all this drained the battery.
I've flashed the PH98IMG, removed it since it was causing me to constantly reflash it and reboot. Removed the boot img from the MIUI ROM and placed it in the root of my SD card, seemed to do nothing. I've also tried to use abd, although I'm not really sure how to use it, basically tried to follow a few different threads, but when I typed adb devices, the list was always blank.
Can anyone help me to either get this MIUI ROM working or at least get me back into recovery so I can re-load ViperRez that I know was working? I am no expert, so please give detailed instructions if you can. Thanks in advance.
ronin_rone said:
Ok so here's the deal...
I was running ViperRez ROM and decided it was time for a change and found a few ROMs I wanted to check out. Tried EclipticRez, kept force closing and rebooting before or just after I could finish the phone set up. Tried Nils Business, no luck. So finally tried to load MIUI for ICS and ran into trouble.
Each time before loading these ROMs I used Clean Wipe to wipe before loading the ROM. I am S-on. Unlocked. HBOOT- 2.11
So here's where my trouble is... Normally when a ROM fails to work, I'd simply reboot into recovery, wipe, and load a different rom via zip from SD card. The problem I'm having, besides the ROM not loading and getting stuck on the HTC flash screen is, I cant get into recovery. I can reboot into the bootloader screen, get to fastboot. When I try to select recovery the phone goes black, flashes something quickly on the lower part of the screen with CWM recovery looking logo, then reboots and sticks on the HTC white screen. Another issue, my battery will no longer charge via phone charger, so I had to go out and buy a battery charger today to even get my phone running again since all this drained the battery.
I've flashed the PH98IMG, removed it since it was causing me to constantly reflash it and reboot. Removed the boot img from the MIUI ROM and placed it in the root of my SD card, seemed to do nothing. I've also tried to use abd, although I'm not really sure how to use it, basically tried to follow a few different threads, but when I typed adb devices, the list was always blank.
Can anyone help me to either get this MIUI ROM working or at least get me back into recovery so I can re-load ViperRez that I know was working? I am no expert, so please give detailed instructions if you can. Thanks in advance.
Click to expand...
Click to collapse
Have you tried fastboot flashing the boot.img?
gleggie said:
Have you tried fastboot flashing the boot.img?
Click to expand...
Click to collapse
I have tried. Although Im not sure it worked right, or if I even did it right. Just an update. I tried flashing another PH98IMG and it said it was older. Still stuck
ronin_rone said:
I have tried. Although Im not sure it worked right, or if I even did it right. Just an update. I tried flashing another PH98IMG and it said it was older. Still stuck
Click to expand...
Click to collapse
your are s-on you need to extract the boot.img from the zip. go to fastboot and make sure it says fastboot usb
fastboot flash boot boot.img
that will flash the kernel that you need. the ph98img you only need if you are trying to make firmware changes. everything else can be run from the computer.
Also, make sure you are flashing 3.04 roms. Viperrez i think never updated to the global . If you are flashing global roms, you HAVE to do the firmware update.
dragonstalker said:
your are s-on you need to extract the boot.img from the zip. go to fastboot and make sure it says fastboot usb
fastboot flash boot boot.img
that will flash the kernel that you need. the ph98img you only need if you are trying to make firmware changes. everything else can be run from the computer.
Also, make sure you are flashing 3.04 roms. Viperrez i think never updated to the global . If you are flashing global roms, you HAVE to do the firmware update.
Click to expand...
Click to collapse
I kinda understand what you are saying, but the other problem I have is.... When running adb my phone is not listed in the adb devices, although it is listed in the usb devices. Not sure what to do about that.
Are you in charge only mode on the phone?
Is usb debugging enabled?
USB debugging was selected prior to this incident and it was on charge only as well. It was not connected as a usb drive. I cannot get into the settings of the phone to find out what it is now or if its changed.
I would suggest going S-Off, it will make flashing a whole lot easier. As for getting back to a usable state, you should be able to flash a PH98IMG in bootloader. If anything, flash an RUU and go from there.