Related
Ok I am in dire need of help! I just flashed my G2x and have no connection to tmob ile whatsoever. Ive tried three different roms no including eagles blood, hell fire phoenix and now bionix. each time ive got no tmobile connection and no battery data also. dont know if ive done something wrong any help?
Have you tried CM7? Did you do a full wipe prior to installing? Have you tried to flash back to stock? We need a little more info, please.
yes ive tried cm7. i just recently reverted completely back to stock and still no connection or battery data. when i originally flashed rom yes i did full wipe cache wipe and dalvik wipe. well when i had flashed clockwork mod recovery i did it through rom manager and my first custom rom flash resulted in a boot loop and i wasnt able to get back into recovery.. after hours of searching i figured out how to flash recovery through apx and was able to get into clockwork recovery and there i flashed my rom.. since then ive tried everything to get a connection to the network with no success. even reverting to full stock.. now before it was stock gingerbread and now its back to froyo.. have tried over and over to use lg update tool with no success.. thanks for all and any help
So im still searching.. With no luck.. Turns out it is a baseband problem says unknown.. Im literally seconds from throwing this phone at the wall!! Aaagh...
If you have no baseband, you may not have a radio installed... no radio/unknown = no data. Try flashing your desired ROM and then flashing a radio. I don't much about the G2X... you might want to check this thread out: http://forum.xda-developers.com/showthread.php?t=1332350
Also, I just read that you can go to LG's website and use their official updater. Some users have said they had to return to stock to get it to work, while another claims they had CWM Recovery and CM installed and it worked perfectly. Bottom line is that is sounds like you need a radio.
Yea ez stuff. Downlosd radio and flash it
Sent from my HTC Sensation Z710e using XDA App
vabeachfc3s said:
Yea ez stuff. Downlosd radio and flash it
Sent from my HTC Sensation Z710e using XDA App
Click to expand...
Click to collapse
Not "ez stuff" but can be done. Follow the instructions from this link.
http://forum.xda-developers.com/showthread.php?t=1332350
Ment like ez to fix
Sent From Space Using My ICS Flavored Sensation
I had this once just pulled battery and sim let it sit for a few minutes and rebooted problem solved. It was a weird thing but it worked lol.
Sent from my LG-P999 using xda premium
Thats awesome
Sent From Space Using My ICS Flavored Sensation
GTWalling said:
Not "ez stuff" but can be done. Follow the instructions from this link.
http://forum.xda-developers.com/showthread.php?t=1332350
Click to expand...
Click to collapse
gonna try this but the sim card thing first haha seems easier.. ive tried the lg update tool and it always gets stuck at 30%.. i appreciate everyones help i will keep you posted.. oh and the sim card battery
trick didnt work .. =p lucky dog
ok this has gotten depressing .. i have tried almost every forum searching for ways to fix this.. but now i have one LAST ?..Does anyone think that getting a stock rom from another g2x will fix my situation?
roymontante77 said:
ok this has gotten depressing .. i have tried almost every forum searching for ways to fix this.. but now i have one LAST ?..Does anyone think that getting a stock rom from another g2x will fix my situation?
Click to expand...
Click to collapse
Have you tried the Ge Ril app in the market? https://market.android.com/details?...t=W251bGwsMSwxLDEsImNvbS5zaWJib3IuZ2V0cmlsIl0.
My first question is: is it possible to get the OTA update on a rooted phone?
The 2nd question is there something I can do to get the Software Update check work?
I realise that my first question may answer this one as well, it's only just that all of the other ROM's I've tried did at least seem to contact a checking service and come back with a response that No Updates have been found. This one just keeps waiting for a response and never gets one.
Want to at least try the official OTA ICS update from Vodafone UK if possible, without having to load a stock ROM and locking my phone again.
Thanks
Sent from my HTC Sensation Z710e running Extreme Sensation Dream 2 using xda premium
It has always been traditionally said not to apply an OTA on a rooted phone as, historically, it's caused nothing but problems. Whether the same is true now I can't say BUT I would not recommend it personally
do i need to uninstall only SU, or su and clockwork to install ota?
sorry for my bad english
thanks
CWM needs to go as well - you need the stock recovery
Thanks for the advice. I'll have to go stock if CM9 is a long way off. Or try 7.x again, although I'll really miss ICS.
Sent from my HTC Sensation Z710e using xda premium
I think as long as you have stock recovery but are S-OFF; it shouldn't be an issue. I looked at some previous posts , albeit from the Evo forum and it seems to be fine. I could be wrong, though.
I keep seeing people post about being rooted and flashing the OTA update. Now someone please, please, please correct me if I am wrong, but when you flash as new ROM, unless you just flash a new system via ADB fastboot commands, you flash a new kernel and all every time you flash a new ROM. So therefor it does not matter if you are rooted cause the rooted kernel will be replaced with a new ROM. For those out there that do not know the kernel is contained in the boot.img of a ROM. Now in a s tock ROM it is. Of always named boot.img but it is still pretty much the same thing with maybe a little more than a custom TOM's would be. So please people stop wording about being rooted, it does not matter. If you are on the correct stock ROM and have the stock recovery you are good to go to flash and run the OTA. It does not matter if you are S-off or S-on either.
It does 100% matter as otherwise the SU app/binary will still be present and potentially cause issue to the 'stock' ROM. Go look at the Desire forums all over the net for examples as to why you shouldn't flash an OTA onto a rooted handset
EddyOS said:
It does 100% matter as otherwise the SU app/binary will still be present and potentially cause issue to the 'stock' ROM. Go look at the Desire forums all over the net for examples as to why you shouldn't flash an OTA onto a rooted handset
Click to expand...
Click to collapse
So as long as you're stock recovery, and stock ROM, but s-off, it shouldn't have any bearing whether or not you upgrade ota... Right?
Sent from my HTC Sensation XE with Beats Audio Z715e using XDA
EddyOS said:
It does 100% matter as otherwise the SU app/binary will still be present and potentially cause issue to the 'stock' ROM. Go look at the Desire forums all over the net for examples as to why you shouldn't flash an OTA onto a rooted handset
Click to expand...
Click to collapse
Ok I well look into this further when I get home from work. I have not looked at the Desire forums yet, bit I will later today. My question is though are the Desire users having to use the stock recovery, or has someone made a flashable .zip file for them of the OTA? If so this could have something to do with the troubles. Like I said I will check into this further this evening. I still say it should not as the kernel is replaced when you flash the OTA update, bit I could very well be wrong.
It's not that you can't do it, you can, it's just not recommended. By all means try it but should it go wrong flashing an RUU is all that would work
Sent from my Galaxy Nexus using xda premium
EddyOS said:
It's not that you can't do it, you can, it's just not recommended. By all means try it but should it go wrong flashing an RUU is all that would work
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I totally understand what you are saying, but flashing stock is not the only way to fix it, it is just the easiest and most user friendly way to fix it. It is pretty much a one click fix, and that is because of the RUU it self. When you flash via a RUU the utility runs a Task 28 on the NAND memory first meaning the NAND is totally wipped, meaning all partitions, before the ROM is flashed. Now you can also use ADB to remove and reflash all partitions,Splash 1(mtdblock0), recovery(mtdblock1), boot(mtdblock2), system(mtdblock3). cache(mtdblock4), userdata(mtdblock5).
Now back to the question about being rooted, I still have not got home yet to get on my computer to look at the desire forums. Now from what I know root is acheived on the kernel level cause that is what root is. It allows for direct communication with the kernel, again correct me if I am wrong. Now I understand that Superuser app binaries would still be present if you flashed just the system. But if you flash a whole new ROM wich is what the OTA update does, then the kernel is replaced with the kerneel in the OTA update, which by is either a completely new kernel or a modified kernel that HTC has made to work with ICS. I have not had time to look into wich one it is, but from my experience of trying to help port the SDK of ICS to the Sensation it is probably a completely new kernel.
Anyway I will have to do some research on the differences between stock recoveries and custom recoveries. Specifically the processes the recoveries run when flashing a ROM from SD card, and just what all is in the OTA update files. Once I get to do this I will be more able to give a hard core answer to this question. Oh and thinks to the EddyOS for helping to get me back into digging around in ROM files and learning more about how Android works.
Edit: I totally forgot to mention JTAG, this is another way that you could fix the problem, all be it sort of a major over kill for the problem, but still a fix.
Hi all,
I just tried flashing miui 2.4.20 to an HTC DESIRE S.
1)Before doing so, I unlocked the bootloader using HTC Dev tool
2)Rooted using superclick tool
3)Installed CWM Recovery using fastboot
and then flashed the rom....it won't go any further than the white HTC screen on reboot even though it looks like the flash is successful. I tried reflashing several times with no luck can someone please help?
EDIT:Just realised that I had to flash the boot.img using fastboot...problem solved.
Is there a way to make the Desire S completely unlocked so that I can flash using cwm without the need of fastboot?
lowrider82 said:
Hi all,
I just tried flashing miui 2.4.20 to an HTC DESIRE S.
1)Before doing so, I unlocked the bootloader using HTC Dev tool
2)Rooted using superclick tool
3)Installed CWM Recovery using fastboot
and then flashed the rom....it won't go any further than the white HTC screen on reboot even though it looks like the flash is successful. I tried reflashing several times with no luck can someone please help?
EDIT:Just realised that I had to flash the boot.img using fastboot...problem solved.
Is there a way to make the Desire S completely unlocked so that I can flash using cwm without the need of fastboot?
Click to expand...
Click to collapse
Yes. You need to downgrade your hboot, there are guides for this in the general section, you'll need to find a compatible ruu, get back to stock rom and then use revolutionary to S-Off
Sent from Purgatory - Still stuck between the One X and the SGS3.
How do i do the boot.img
Did it all on the exact same way you did
got the exact same problem at the moment.
Were do i find the boot.img and how do i go about getting it onto the phone
Im new to flashing
slugger7 said:
Did it all on the exact same way you did
got the exact same problem at the moment.
Were do i find the boot.img and how do i go about getting it onto the phone
Im new to flashing
Click to expand...
Click to collapse
I got a solution, but its a bit tricky: use the forum search
Sent from my HTC Desire S using xda app-developers app
Feel like an idiot lol
c.m.b said:
I got a solution, but its a bit tricky: use the forum search
Sent from my HTC Desire S using xda app-developers app
Click to expand...
Click to collapse
Yep found out like now and it is working now. Thanx for teaching me the ways of the force
slugger7 said:
Yep found out like now and it is working now. Thanx for teaching me the ways of the force
Click to expand...
Click to collapse
No problem, but use it with caution
Sent from my HTC Desire S using xda app-developers app
help needed.
c.m.b said:
No problem, but use it with caution
Sent from my HTC Desire S using xda app-developers app
Click to expand...
Click to collapse
hey.
please help me..
i flashed the pacman rom using clockmod recovery..
i downloaded it ,copied into my sd and then installed it..
i am still stuck on htc screen..
please help..
i dont know what to do!
jigi1993 said:
hey.
please help me..
i flashed the pacman rom using clockmod recovery..
i downloaded it ,copied into my sd and then installed it..
i am still stuck on htc screen..
please help..
i dont know what to do!
Click to expand...
Click to collapse
Are you htcdev unlocked?
lowrider82 said:
Hi all,
I just tried flashing miui 2.4.20 to an HTC DESIRE S.
1)Before doing so, I unlocked the bootloader using HTC Dev tool
2)Rooted using superclick tool
3)Installed CWM Recovery using fastboot
and then flashed the rom....it won't go any further than the white HTC screen on reboot even though it looks like the flash is successful. I tried reflashing several times with no luck can someone please help?
EDIT:Just realised that I had to flash the boot.img using fastboot...problem solved.
Click to expand...
Click to collapse
I have flashed many devices(Desire, Desire S, HD2, HD and One X) a hundred of times because I am a beta tester. So I know the ins and outs of flashing. But this time I need your help guys.
I have unlocked my Desire S (Hboot is 2.00.0002, S-ON, Radio 3822.10.50.24_M)
flashed TWRP recovery
flashed Viper Saga 2.1.3 JB
flashed boot.img
And the Rom booted and installed. All fine so far.
Now I want to install a different ROM.
Flashed the new PACman JB_2.2_v22 ROM, and boot.img. But this time I got stuck at white screen. So I tried CWM recovery and even 4EXT. Flashed Rom and its boot.img again. No luck. Stuck at white screen every time.
But now the weirdest. At the end I flashed TWRP recovery, Viper Rom and its boot.img again. And damn, I'm stuck at the white screen again.
Also weird is that I am not able to flash an official RUU after unlocking the bootloader again. When plugging in the device I can start the RUU installation proces. But during the sending firmware proces, the phone screen remains black with HTC on it for hours. So I had to remove the cable and boot the phone into bootloader again.
It looks like something is blocking these two processes.
Any ideas? I searched through XDA and on the internet. The only thing I can find to solve the white screen with green HTC is flashing boot.img. But that is not the issue.
The problem and sollution with the RUU installation, I haven't seen at all yet.
Hope somebody could point me in the right direction.
wanahave said:
I have flashed many devices(Desire, Desire S, HD2, HD and One X) a hundred of times because I am a beta tester. So I know the ins and outs of flashing. But this time I need your help guys.
I have unlocked my Desire S (Hboot is 2.00.0002, S-ON, Radio 3822.10.50.24_M)
flashed TWRP recovery
flashed Viper Saga 2.1.3 JB
flashed boot.img
And the Rom booted and installed. All fine so far.
Now I want to install a different ROM.
Flashed the new PACman JB_2.2_v22 ROM, and boot.img. But this time I got stuck at white screen. So I tried CWM recovery and even 4EXT. Flashed Rom and its boot.img again. No luck. Stuck at white screen every time.
But now the weirdest. At the end I flashed TWRP recovery, Viper Rom and its boot.img again. And damn, I'm stuck at the white screen again.
Also weird is that I am not able to flash an official RUU after unlocking the bootloader again. When plugging in the device I can start the RUU installation proces. But during the sending firmware proces, the phone screen remains black with HTC on it for hours. So I had to remove the cable and boot the phone into bootloader again.
It looks like something is blocking these two processes.
Any ideas? I searched through XDA and on the internet. The only thing I can find to solve the white screen with green HTC is flashing boot.img. But that is not the issue.
The problem and sollution with the RUU installation, I haven't seen at all yet.
Hope somebody could point me in the right direction.
Click to expand...
Click to collapse
To flash an ruu you need to lock your bootloader. As for the other issue do you know what panel your phone has, it's not an issue on sense roms and only becomes apparent in jb roms. Check http://forum.xda-developers.com/showthread.php?t=1943524
[OFF-TOPIC] Non-Sony screen panel DS users lounge I'd your not sure
The person who reads too much and uses his brain too little will fall into lazy habits of thinking.
—Albert Einstein
AW: HTC DESIRE S stuck at HTC White screen after flash Plese help!
And the problem with flashing ViperSAGA from TWRP is a different issue, TWRP is known to be problematic, I would recommend 4ext.
jugg1es said:
To flash an ruu you need to lock your bootloader. As for the other issue do you know what panel your phone has, it's not an issue on sense roms and only becomes apparent in jb roms. Check http://forum.xda-developers.com/showthread.php?t=1943524
[OFF-TOPIC] Non-Sony screen panel DS users lounge I'd your not sure
The person who reads too much and uses his brain too little will fall into lazy habits of thinking.
—Albert Einstein
Click to expand...
Click to collapse
Thanks for your reply.
Yes I've locked my phone again before installing the RUU. Made no sense. I've tried 2 WWE RUUs both with the same issue.
What panel I have I really don't know. Viper is sense. Worked om first flash. But after flashing PACman, the boot issues started. Now even Viper is not booting anymore.
I check the thread you posted. Will try the kernels. See what is happening.
EDIT: flashing these kernels do not work, because I'm S-ON. Need boot.image.
---------- Post added at 08:32 PM ---------- Previous post was at 08:31 PM ----------
teadrinker said:
And the problem with flashing ViperSAGA from TWRP is a different issue, TWRP is known to be problematic, I would recommend 4ext.
Click to expand...
Click to collapse
As I wrote. I've tried all of them. Am now on 4EXT. But still facing same issues. White screen with green logo.
I'd start fresh, make sure your unlocked, check the drivers are installed correctly (are you on win 8, if so check post two of link in my sig) format all but sd in 4ext, flash rom (sense rom to start) flash kernel. Your obviously no noob but sometimes we miss the obvious. I'm around for a bit so report back
"We don't like their sound, and guitar music is on the way out."
- Decca Recording Co. rejecting the Beatles, 1962
Hi tried to flash AOKP_saga_unofficial using goomanager twrp recovery downloaded then flashed Rom in goomanager but on reboot got white screen HTC logo stuck scenario any ideas what went wrong
Desire s
Unlocked and rooted using all in one tool
S-on still
Hboot 2xxxx not downgraded
Sent from my HTC Desire S using xda app-developers app
gazzy21uk said:
Hi tried to flash AOKP_saga_unofficial using goomanager twrp recovery downloaded then flashed Rom in goomanager but on reboot got white screen HTC logo stuck scenario any ideas what went wrong
Desire s
Unlocked and rooted using all in one tool
S-on still
Hboot 2xxxx not downgraded
Sent from my HTC Desire S using xda app-developers app
Click to expand...
Click to collapse
Did you flash boot.img?
"We don't like their sound, and guitar music is on the way out."
- Decca Recording Co. rejecting the Beatles, 1962
Hi first time have done it thru goomanager I don't remember ticking or seeing option to flash boot image would it be safe to do so and be necessary thanks
have to research a bit more I was a bit lax flashing rom
Sent from my HTC Desire S using xda app-developers app
Sorry my bad
Should have read up a bit more didn't flash bootloader sorry for wasting your time also wondering if I should flash ext4 recovery instead of using twrp seems every body using ext4 now
Sent from my HTC Desire S using xda app-developers app
gazzy21uk said:
Sorry my bad
Should have read up a bit more didn't flash bootloader sorry for wasting your time also wondering if I should flash ext4 recovery instead of using twrp seems every body using ext4 now
Sent from my HTC Desire S using xda app-developers app
Click to expand...
Click to collapse
Don't worry about it, 4ext is the best recovery for our device. There seems to be a few issues with the other two.
"We don't like their sound, and guitar music is on the way out."
- Decca Recording Co. rejecting the Beatles, 1962
having a look round revolutionary Rom looks better prospect see you using it atlas this stock gb is running near perfect only trying to improve battery drain 18-20MA in sleep at mo revolutionary has under clock facility which is only way I can see but at what cost
This may I say is a really excellent thread filled by people like me not reading up enough before we tinker to our cost and thanks to you xda this is a casualty department for noobs
Sent from my HTC Desire S using xda app-developers app
gazzy21uk said:
having a look round revolutionary Rom looks better prospect see you using it atlas this stock gb is running near perfect only trying to improve battery drain 18-20MA in sleep at mo revolutionary has under clock facility which is only way I can see but at what cost
This may I say is a really excellent thread filled by people like me not reading up enough before we tinker to our cost and thanks to you xda this is a casualty department for noobs
Sent from my HTC Desire S using xda app-developers app
Click to expand...
Click to collapse
The casualty department is located in the help Thread (follow link in my sig)
"We don't like their sound, and guitar music is on the way out."
- Decca Recording Co. rejecting the Beatles, 1962
Here is what I did....
HTC One X (ATT). Unlocked and rooted yesterday. (TWRP)
Today tried to install CM10 and GApps, got stuck on CM bootscreen, then I flashed the boot.img and it still did not work....then my immediate next step (probably stupidly) was to flash modded boot...still did not work....I just got to HTC screen with the red writing on the bottom and nothing else....
So I got into TWRP and restored to my backup (which I was able to do before the above) and just got to the same HTC screen with red type on the bottom......now I started to panic.
I tried to relock the phone...and I did but now I cant go anywhere but the fastboot screen!!!!
Please Help!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
If you relocked already just run the ruu in fastboot and restore to stock.
davezaff said:
If you relocked already just run the ruu in fastboot and restore to stock.
Click to expand...
Click to collapse
I am downloading the RUU....we'll see
Many Thanks
davezaff said:
If you relocked already just run the ruu in fastboot and restore to stock.
Click to expand...
Click to collapse
Many thanks....it worked!!!!!
Now the question is...do I try again? (Not today anyway)
trevorb21 said:
Many thanks....it worked!!!!!
Now the question is...do I try again? (Not today anyway)
Click to expand...
Click to collapse
Just read read and read more..be comfortable first than you'll be fine and know how to get out of any situation
Just read up and give it another go.....like anything else, sometimes you need certain thing to happen to learn....good luck.
Just saying, you flashed the boot.img after flashing the rom and gapps? The boot.img is flashed before flashing the rom
It can be done either way.
ive been seeing alot of new members soft bricking this way should read though this post http://forum.xda-developers.com/showthread.php?t=1957193 it explains every thing for ppl on hboot 1.14 and higher.
trevorb21 said:
I tried to relock the phone...and I did but now I cant go anywhere but the fastboot screen!!!!
Click to expand...
Click to collapse
That is what is supposed to happen. Once you relock, you need to run the RUU. It won't boot otherwise.
I am unlocked and rooted again.....ready to try again...
I want to leave the phone alone but I cant help myself.......Anyone else have this issue???
I know what you mean, when i first got my one x and learned of rooting, i felt i was claustrophobic with normal stock. I Read and read and read some more, before I even thought about flashing roms. But I Recommenced flashing Viper JB 3.1.0 As it basically installs the boot img in the boot-loader for you. I also recommend Cm 10.1, except it does not have camera working as of yet. If you dont mind not having a camera, cm 10.1 is a very smooth rom. Also remember if flashing certain roms like cm 10. dalvik, cache and factory reset, as well as flashing the boot img are required for the rom to work. Good luck
trevorb21 said:
I am unlocked and rooted again.....ready to try again...
I want to leave the phone alone but I cant help myself.......Anyone else have this issue???
Click to expand...
Click to collapse
I've had this problem since may 6th, 2012 lol.. good god you should here my wife when I tell her I didn't get her messages or calls because I was in recovery lol!
Sent from my HTC One XL using Tapatalk 2
InflatedTitan said:
I've had this problem since may 6th, 2012 lol.. good god you should here my wife when I tell her I didn't get her messages or calls because I was in recovery lol!
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
I'm livin in the same life man been though 4 android phone and a tablet in a year o and rooted all my friends phones
Thanks a ton this thread helped me save my phone
I looked around and didn't see a solution to my problem. I might have missed it because I'm kind of panicked right now.
My HOXL was dying really fast. Within a few hours, it falls from 80% to 0%. I wanted to factory reset because I heard that it helps the battery life.
So I followed the process I always have (I'm unlocked, rooted, and had pacman's evita ROM installed) and did a factory reset, wiped cache and dalvik cache. Then I re-flashed pacman's ROM and the gapps. When I rebooted though, it went to the HTC screen and in a few seconds it just went black. I think it might have still been on or something, but nothing was happening for like 30 minutes. I tried it over and over again, flashing new ROMs and kernels, but now all that's happening is that it's stuck on that very first HTC screen.
I downloaded the latest JB RUU for evita to try it out. But if I can't get past that first screen, is there a way to connect it? I can still get into TWRP's recovery. My HBoot is 1.09. I'm really starting to feel nervous about having to buy a new phone, yet I feel like there should be a way to fix this. Could flashing the stock kernel be all I need? I tried to download from Viper's hub, but the download just stops at 99% and doesn't finish.
Please, I would really, really appreciate any help!
I would run the 3.18 RUU (which you can do in fastboot).
Try a complete wipe: Factory reset, system, cache and dalvik cache in twrp or if it is not wiping correctly due to twrp version " 2.3......" is best fro our phones, try downloading and installing twrp again or use adb commands to wipe and flash rom again.
I've tried a complete wipe, but I just noticed that my TWRP version is 2.2.0. I tried the wipe like five or more times and it didn't work. My PC isn't reading the HOXL in the adb command window. I rooted a Sero Pro 7 this way, so I think I should have the drivers installed for it... I'm going to try installing the HTC Sync drivers and seeing if I can send adb commands to my HOXL. If this doesn't work, I'm going to try the 3.18 RUU. I heard that some people have bricked their HOXL completely doing this, but I didn't change my SuperCID and s-on (?), so would I be fine? Or would it be safer to just use the latest ICS one (RUU_EVITA_UL_ICS_40_S_Cingular_US_2.20.502.7_Radio _0.19as.32.09.11_2_10.105.32.25L_release_271865_si gned.exe)?
So you have no way to flash boot image separately? I would definitely try to get device recognition so adb can be used before running ruu.
Sent from my HTC One X using xda premium
Yeah, I went through the noob way of unlocking and rooting this phone, so there was no need to use adb commands. I would have liked to try that first before running RUU, but I just want to have a working phone again, even if I have to go through the whole process of unlocking and rooting.
Sent from my Nexus 7 using XDA Premium HD app
I would still try to get a good adb environment. Sometimes panic is not a good thing. Just be careful and make sure you get the proper ruu and do not let the battery die while running it. Let me know if it works.
Sent from my HTC One X using xda premium
Venomtester said:
I would still try to get a good adb environment. Sometimes panic is not a good thing. Just be careful and make sure you get the proper ruu and do not let the battery die while running it. Let me know if it works.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
This is what I'm worried about:
SERooted wrote: Note to OP: You really should add to the 1st post that it is not wise to flash the 3.18 firmware over super cid and s-on.. its not a good thing for most people to have a qhsb_dload turn their phone into a paper weight before finding out that they shouldn't have used that file to begin with. i had to find out the hard way. i would have flashed the ics firmware on my phone but decided to go with the big JB only to find out that it turns it into a paperweight. I understand this is no fault but my own, however this would greatly help people when choosing which ruu to run.
http://forum.xda-developers.com/showthread.php?t=2191477
I know what you mean lol. I would only do that as a last resort. I would try and get adb working since the phone is not bricked. It just seems to have no Rom or boot image. Have you tried one with an aroma installer?
Sent from my HTC One X using xda premium
Venomtester said:
I know what you mean lol. I would only do that as a last resort. I would try and get adb working since the phone is not bricked. It just seems to have no Rom or boot image. Have you tried one with an aroma installer?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Huh...I just tried flashing the UrDroid ROM because of its aroma installer, but it didn't happen in recovery, like I thought it would. It said it was successful, so I rebooted the system. It got past the initial screen with an AT&T boot img and htc one img. Now I'll have to see if it actually loads past this.
EDIT: It worked! I'm going to have to try to see if I can load boot img some other way than just an aroma installer.
You can use Flash GUI from the market to install boot images or get Goo Manager to install a 2.3..... Version of twrp. That may solve your problems.
Sent from my HTC One X using xda premium
Venomtester said:
You can use Flash GUI from the market to install boot images or get Goo Manager to install a 2.3..... Version of twrp. That may solve your problems.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Second Flash GUI....works like a charm