Hey,
I followed this guide: http://forum.xda-developers.com/showthread.php?t=1285894 However, after doing the steps fully, I launched ROMManager, becasue I didn't know it wasn't working correctly. So in order to fix it, I tried to restore my phone to the stock rom, by following this guide: http://forum.xda-developers.com/showthread.php?t=1286432
I used both the rooted pda and the modem files with Odin. That didn't fix anything either. So then I decided to search a bit more, and figured out that I shouldn't have installed or used RomManager. No big deal, I redid the first guide again. Now that I'm correctly into CWM (the 3 button press way, not RomManager > Boot into CWM) I tried flashing CM7. I can't. I get a pretty long error. It starts with the following:
Assert failed: getprop ("ro.product.device")
I googled that. Turns out CM doesn't support the radio/modem I flashed. (atleast, that's what the problem was with a different phone). How can I go about solving this? I basically just want CM7 running on the S2.
Edit: I was using the wrong CM7 rom. I was able to flash it, but now it just gets stuck at the Galaxy S2 screen with the yellow triangle. Left it there for about 5 minutes with nothing else poping up. Right now I'm going to try a nandroid restore.
Alright. I was able to restore it. I was also able to install the Cognition X2 Mod. I'm still having issues with Cyanogen, but I'll keep trying and looking around the forums.
Fixed. Reflashed the mod twice and it's working.
Which ROM did you flash? Because i was having the same problem. i was able to restore and i'm back to stock rooted.
I installed both cognition and cm7 lastnight.
I'd backup everything first though in CWM Backup
Both times, all I did was copy the .zip to the INTERNAL sd storage, then boot into recovery via (VOL UP + VOL DOWN + POWER), did data/cache wipe, then install from SD and voila.
I got it working. At first I was flashing the International S2 rom. then I downloaded the rom off the thread in this forum. So it should be all good now.
I am just getting the cyanogen mod 7 logo on loop after flashing.
How do i get back to where i am able to do a restore? Volume up and Power is no longer working. Thanks
justininhifi said:
I am just getting the cyanogen mod 7 logo on loop after flashing.
How do i get back to where i am able to do a restore? Volume up and Power is no longer working. Thanks
Click to expand...
Click to collapse
VolUp + Power never worked.
VolUp + VolDn + Power... This is documented in MANY places.
Yeah, I got this issue when I tried to flash google apps, then installed cyanogen. To get out of the loop, I cleared everything (wipe) then flashed CM7 twice (there is a new nightly, just got released a few hours ago, fixed bluetooth audio) and then flashed the google apps package. Took a min or two to boot upto the setup screen after that, it took just a few seconds to boot up.
Entropy512 said:
VolUp + Power never worked.
VolUp + VolDn + Power... This is documented in MANY places.
Click to expand...
Click to collapse
Ah, that it what i meant. I was finally able to get back into recovery mode after trying about 4-5 times and have everything working great. Just couldn't get the ROM manager to work to get google apps so i had to flash that. Am i correct that it should be the old style market and not the one that comes stock?
justininhifi said:
Ah, that it what i meant. I was finally able to get back into recovery mode after trying about 4-5 times and have everything working great. Just couldn't get the ROM manager to work to get google apps so i had to flash that. Am i correct that it should be the old style market and not the one that comes stock?
Click to expand...
Click to collapse
The g apps file I flashed only had "talk" on it. Once I loaded talk it asked me what other apps I wanted to download from the market. It downloaded and installed those apps.. But once I went to the market place it was the same one as the stock rom.
weird, i still have the old market style. I wonder if there is anyway to update without reflashing.
Related
I can't post in the VEGAn-TAB GingerEdition STABLE RC1 thread, so I have to post here, sorry.
I am trying to install VEGAn on my new G Tablet, and I keep getting into endless cycles.
First I rooted, then loaded CWM fine. Cleared data, cache, and dalvic. When I installed the ROM, it would hang on the Viewsonic boot screen. Tried several times, even tried fixing permissions, nothing.
So now I have tried the nvflash full restore, which made me lose CWM. Now I am not able to install CWM (.8) it just gives a loading bar and then reboots. Then when I use push power+volume up and release, which should boot into CWM, it just does the same thing (tries to install update.zip) then reboots.
I also can't boot into APX mode: when I hold down Power+Volume up, the screen is supposed to go black, but it never does. Just tries to load an 'update.zip' file that isn't there, and then reboots. This means that I can't use the nvflash method to install CWM.
Here is the current info from my about tablet:
Model UPC300-2.2
Tap UI version: 1.1-3389
Kernel version: 2.6.32.9.00000.10.8.2-dirty
Build Number FRF91
Any help would be extremely and much appreciated. Thanks!!
G
To go into APX mode, you have to hold Power plus Volume down. Get NVFlash, restore to stock rom, and then install CWM again and the flash your Rom. And don't forget to partition with NVFlash.
http://forum.xda-developers.com/showthread.php?t=861950
EDIT: I had the same issue. Installed CWM, then flashed CM7 and I wanted to change roms but I couldn't until I set up NVFlash and restored to stock and flashed VEGAn-TAB.
fp99 said:
To go into APX mode, you have to hold Power plus Volume down. Get NVFlash, restore to stock rom, and then install CWM again and the flash your Rom. And don't forget to partition with NVFlash.
http://forum.xda-developers.com/showthread.php?t=861950
EDIT: I had the same issue. Installed CWM, then flashed CM7 and I wanted to change roms but I couldn't until I set up NVFlash and restored to stock and flashed VEGAn-TAB.
Click to expand...
Click to collapse
Thanks! If I follow the steps here for nvflash http://forum.xda-developers.com/showthread.php?t=861950, won't that automatically repartition, or do I need to do something else beyond that?
generosity21 said:
Thanks! If I follow the steps here for nvflash http://forum.xda-developers.com/showthread.php?t=861950, won't that automatically repartition, or do I need to do something else beyond that?
Click to expand...
Click to collapse
You actually have to do that in CWM. Under the advance option -> partition SD card.
Check out step 7. http://forum.xda-developers.com/showthread.php?t=865245
EDIT: This will erase everything on the tablet. Rom files and all. After the partition. Mount the USB and copy the rom file onto the tablet via the usb cable.
Thanks for the help, one last question.
I applied the fix to Market, but now I'm not sure if it needed it, and I am not able to download any apps from the market. I can browse fine, just not download. Did applying the fix mess things up, and is there an easy way to fix? I tried rebooting, but maybe fix permissions is necessary?
Thanks
g
generosity21 said:
I can browse fine, just not download. Did applying the fix mess things up
Click to expand...
Click to collapse
No, you didn't mess things up. Do the fix again: delete the cache for the Market app, delete the data for the Google services app, reboot, and you should be able to download. Worked for me.
By reboot, I mean powering completely off, then manually turning it back on.
Working great now! I think it may have been the Wifi network I was using. I have read several posts where switching to a different wifi fixed the download issue.
Thanks for the help
-BoneZ- said:
No, you didn't mess things up. Do the fix again: delete the cache for the Market app, delete the data for the Google services app, reboot, and you should be able to download. Worked for me.
By reboot, I mean powering completely off, then manually turning it back on.
Click to expand...
Click to collapse
You guys hit it out the park with this rom. I have a question what browser is this? Also I like to save articles as I cruise the web and the stock browser let me create custom folders. What would be a good way to do it with this rom and browser?
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.
ok so yesterday i rooted my telus fascinate and i was going to isntall the MIUI rom. Following a guides instructions i installed rom manager and did a clockwork mod recovery, i then put the rom on my root file of my sd card and tried to install it through the "install rom from sd card option" on the app. Problem was i only got into the stock recovery mode and not the clockwork one it aslo gave me signature failures. I then followed the guide of this video:
http://http://www.youtube.com/watch?v=Q7xV0yE9ZcA
when i installed the kernel everything went fine but then after i got into CW recovery and installed the rom my phone booted and it just kept repeating the normal splash screen (it said galaxy I9000 instead) followed by a screen that said something like cryogenic mod. I got freaked out from here and tried to install stock kernels to get my phone running. As of right now my phone will boot but only stay on the splash screen. I can not access recovery mode. I really need some help, thanks.
these are some of the files i used:
the rom i used,
http://http://forum.xda-developers.com/showthread.php?t=1150045
the kernel i used,
http://http://forum.xda-developers.com/showthread.php?t=822756
thanks
the links are broken. Did you install a rom / kernal specifically for the telus fascinate?
i believe it could have been for the galaxy I9000,
ill try to fix the links btw
update*
i managed to get it into clockwork recovery mode by holding the dam buttons for a solid 5 minutes, after doing this i pressed factory reset, now my phone is stuck saying:
-- wiping data...
Formatting DATA
0_0' im not having a great day
http://forum.xda-developers.com/showthread.php?t=1227807Until I know what version miui and kernal you are trying to flash, it's hard to help. It definately sounds like your phone is soft bricked tho.
Edit* Here are some links you should read up on.
http://forum.xda-developers.com/showthread.php?t=923712
http://forum.xda-developers.com/showthread.php?t=1227807
try to type this inot your browser:
http://forum.xda-developers.com/showthread.php?t=1150045
aswell as this:
http://forum.xda-developers.com/showthread.php?t=822756
it takes a little longer but i cant fix the links sorry.
So as of now i got i managed to wipe all of the data on my phone and i am in recovery mode, if i click reboot it does the same thing and stays on the boot screen. If i click the mod from the sd card it flashes from the normal model number screen to one saying cryogen mod. It then keeps going back and forth with a flash of a screen that has a bunch of commands on it for about 2 seconds
brodydj said:
try to type this inot your browser:
http://forum.xda-developers.com/showthread.php?t=1150045
aswell as this:
http://forum.xda-developers.com/showthread.php?t=822756
it takes a little longer but i cant fix the links sorry.
So as of now i got i managed to wipe all of the data on my phone and i am in recovery mode, if i click reboot it does the same thing and stays on the boot screen. If i click the mod from the sd card it flashes from the normal model number screen to one saying cryogen mod. It then keeps going back and forth with a flash of a screen that has a bunch of commands on it for about 2 seconds
Click to expand...
Click to collapse
The rom you are trying to flash is for a i500 fascinate. I suggest taking the time to do alot of research before you turn the phone into an expensive paperweight. Read this link!!
http://forum.xda-developers.com/showthread.php?t=921285
K well i ran that rom and it works now but he only problem is i dont have any cell service, do you know how to fix that. I know that you are probably laughing at my mild retardism at this subject but i am a big noob. As for what you said in your previous reply is their an MIUI version for the fascinate from telus because i basically rooted my phone so i could get this rom.
thanks
Update*
i followed the instructions on the link you posted and chose the rom for MIUI I9000 as the one i was going to install but when i istall zip from sd it only says installed correctly and then when i reboot it keeps changing from the sgh-t959d to the galaxy s cyanogen screen
yea your boot looped now. I would run the rom that worked just install the compatible radio and kernal for it and you should get cell service back.
ok thanks i got all my cell service back and i got the MIUI rom to work. Now to just ry to remember all the apps i had
Your welcome...glad you got everything working!
Before doing my flash, I did my research, and it seemed that in order to update from CM7 to CM10, I had to flash a different version of CWM. So I booted into recovery, flashed the version 6.xxx CWM, and then rebooted (I assumed that in order to flash CM10, I had to be in a CM10-compliant recovery). After getting back to my regular desktop, I rebooted into recovery as normal... only it didn't go into recovery. Instead, it paused for a moment like it would go into recovery, then booted to my normal desktop.
I've tried about a billion ways to boot into recovery, to include SD based recoveries, but it either goes to a larger sized N screen, then hangs up on a black screen, or it boots me to my normal CM7. I "can" continue to operate on CM7, but until I can boot into recovery, I can neither update to CM10 nor address any problems I come across in my current build.
Suggestions?
nashdude said:
Before doing my flash, I did my research, and it seemed that in order to update from CM7 to CM10, I had to flash a different version of CWM. So I booted into recovery, flashed the version 6.xxx CWM, and then rebooted (I assumed that in order to flash CM10, I had to be in a CM10-compliant recovery). After getting back to my regular desktop, I rebooted into recovery as normal... only it didn't go into recovery. Instead, it paused for a moment like it would go into recovery, then booted to my normal desktop.
I've tried about a billion ways to boot into recovery, to include SD based recoveries, but it either goes to a larger sized N screen, then hangs up on a black screen, or it boots me to my normal CM7. I "can" continue to operate on CM7, but until I can boot into recovery, I can neither update to CM10 nor address any problems I come across in my current build.
Suggestions?
Click to expand...
Click to collapse
Have you tried holding on the power button and the "n" button as you boot? I recall running into a similar issue as yours and that was the only way I could get to recovery. If you're able to get into recovery that way I would consider maybe getting a different version fo CWM. I had trouble with the 6.0.1.5 version. You might try the 6.0.1.2 version here: http://forum.xda-developers.com/showthread.php?t=1640958&page=5
I ran into something similar when I tried installing CWM 6.x.x. I chickened out and decided to run CM10 from SD instead, and I'm so happy on the performance now that I do!
I did the "unbrick" thing with "repart.img" to get the Tablet back to "out of the box" state and sighed of relief when it worked!
Yeah, I was afraid of that. I really didn't wanna go through the process of unbricking, but I guess there's no help for it.
troy9829 said:
Have you tried holding on the power button and the "n" button as you boot? I recall running into a similar issue as yours and that was the only way I could get to recovery. If you're able to get into recovery that way I would consider maybe getting a different version fo CWM. I had trouble with the 6.0.1.5 version. You might try the 6.0.1.2 version here: http://forum.xda-developers.com/showthread.php?t=1640958&page=5
Click to expand...
Click to collapse
Power + 'n' doesn't work on my NT either, I have to turn the device off, insert the SD with CWM, then plug in the (still turned-off) NT to a wall charger and allow it to boot up that way - then (and only then) do I boot into recovery, and without touching any buttons. Hopefully that helps
Dang, whoever thought this would be such a booger of a deal?!?
Okay, first off, let me apologize for coming off like a noob, but it seems there's so much information out there that everything's kinda bleeding together, so let me tell you where I'm at.
I've unbricked and restored the NT to stock 1.4.2
I tried rooting, but the only root I can find that is flashable from SD is the 5.5 CWM which is older than the CWM 6.xxx that every CM10 version calls for. So I went ahead and did the root, so now I have a stock NT with root access. This is where I'm getting stuck...
I'm at this point...
http://forum.xda-developers.com/showthread.php?t=1640958&highlight=cwm+1+4+2
...and it apparently requires you to reboot into CWM in order to install CWM?!?
I've found the CWM 6+ files I think I need, but when I try to follow the instructions, my NT won't kick over into recovery---it keeps booting straight to the rooted 1.4.2 stock rom. I've found guides that take you from stock 1.4.3 to CM10, some that take you from 1.4.2 to root, and I even found Indirect's CM7 (without the instructions on how to get CWM on there in the first place!). I even downloaded Rom Manager and tried to boot into recovery that way, but it said there was my device wasn't supported.
I've been staring at this dang screen for three hours, trying to find a step by step, and I'm coming up empty. Maybe I'm just too frustrated at this point and need a breather.
What I need to know is how to install CWM 6+ on a NT that's either rooted or stock 1.4.2 (I still have the unbrick SD card) so that I can boot into CWM. From there, I can make my way through installing CM10. Help. Please. Am about to chew the lining out of my cheek.
I don't know if this might be helpful? http://forum.xda-developers.com/showthread.php?t=2037368
Sent from my NookColor using Tapatalk 2
Not yet. I was expecting OTA to kick in, updating my current 1.4.2 to 1.4.3, but it hasn't. Honestly starting to think my NT doesn't want to be rehacked LOL
Okay, so here's what I'm doing at the moment...
I'm at rooted stock. I moved CWM 6.0.1.2, CM10, and gapps over to internal SD.
I booted into recovery with an older version CWM SD card (SD card image with Win32 > turned off NT > insert SD > plug in USB to autoboot)
While in recovery (from SD), I flashed CWM 6.0.1.2 , CM10 (meghd00t), and gapps-jb-20121011.
I reboot...
WE HAVE JOY!
Now to check to see if the thing's gonna run right (got a whole lotta "XYZ has stopped" error messages upon boot up)
Dangit, keep getting those error messages about Gapps stopping and Google Play, and other stuff. Not allowing me to do hardly anything I need to. I can't even boot into recovery from the home page---it still loads straight to the Rom. In order to get into recovery, I need to use the SD that I made to get into recovery in the first place. Going to wipe dalvik and the other caches to see if that helps...
After wiping the caches, I boot into CM10 with no error messages. I DL'd a game from my Gmail account, and it appears to be working properly. Thanks for the suggestions and for letting me vent
I just went thru this similar ordeal too. It took me over 3 weeks to finally find a recovery & cm10 combo. What I found is that I couldn't get ANY version of twrp to act right. Indirect's flashing tool was invaluable. I finally used it to flash a cwm 6.x from Laverne's thread. It seems that not all versions of cwm 6.x are compatible with certain cm10 roms too & by chance I hit a combo that finally worked! I'm staying with what I got for a while!
Sent from my Nexus 7 using Tapatalk 2
Hey guys,
as HTC doesn't deliver an officiall KitKat ROM, I just decided not to wait any longer and to flash a custom ROM. While I have flashed custom recoveries and (because of root) installed OTA updates manually, this is the first time I installed a custom ROM.
I chose the AOKP ROM offered by PippoX3 here http://forum.xda-developers.com/showthread.php?t=2516863 as it seemed to be stable.
I followed the instructions: downloaded and flashed Lloir's CWM version from here: http://forum.xda-developers.com/showthread.php?t=2074244 - worked, and I was able to boot the stock rom afterwards. Made a Nandroid backup, did a full wipe, copied AOKP and PA GAPPS (modular full) zip files to /data/media (=the internal sdcard), flashed ROM, flashed GAPPS. Afterwards, I rebooted.
That's where I'm stuck. All I'm seeing is the HTC Logo, so it might be either a bootloop (but backgroudn is solid white, no pulsing or anything), or it's frozen. Normally, this wouldn't be a problem - just reboot. But: Pressing Power or Power+VolumeDown doesn't do ****. (Well, actually the Hardware Button LED starts to flash as they should, but no reboot).
As the HOX+ unfortunately has a build-in battery, it's no option to just remove it... So all I'm hoping for is either some hints from you, guys, or for the battery to run out and, I'f I'm lucky, the phone to charge afterwards (if it doesn't charge it's officielly bricked I guess).
So: What do do now?
PS: Studying infomratics, so get as technical as you like. I'm not an expert in android OS structure, but I'll get most things. I'm not afraid of the console, nor Linux, nor anything. But: I won't follow "I dunno why and it seems strage but do it although I don't know why it sometimes work"-instructions that seem just weird... so please, if you don't know what do do either, just skip it.
snehonja said:
Hey guys,
as HTC doesn't deliver an officiall KitKat ROM, I just decided not to wait any longer and to flash a custom ROM. While I have flashed custom recoveries and (because of root) installed OTA updates manually, this is the first time I installed a custom ROM.
I chose the AOKP ROM offered by PippoX3 here http://forum.xda-developers.com/showthread.php?t=2516863 as it seemed to be stable.
I followed the instructions: downloaded and flashed Lloir's CWM version from here: http://forum.xda-developers.com/showthread.php?t=2074244 - worked, and I was able to boot the stock rom afterwards. Made a Nandroid backup, did a full wipe, copied AOKP and PA GAPPS (modular full) zip files to /data/media (=the internal sdcard), flashed ROM, flashed GAPPS. Afterwards, I rebooted.
That's where I'm stuck. All I'm seeing is the HTC Logo, so it might be either a bootloop (but backgroudn is solid white, no pulsing or anything), or it's frozen. Normally, this wouldn't be a problem - just reboot. But: Pressing Power or Power+VolumeDown doesn't do ****. (Well, actually the Hardware Button LED starts to flash as they should, but no reboot).
As the HOX+ unfortunately has a build-in battery, it's no option to just remove it... So all I'm hoping for is either some hints from you, guys, or for the battery to run out and, I'f I'm lucky, the phone to charge afterwards (if it doesn't charge it's officielly bricked I guess).
So: What do do now?
PS: Studying infomratics, so get as technical as you like. I'm not an expert in android OS structure, but I'll get most things. I'm not afraid of the console, nor Linux, nor anything. But: I won't follow "I dunno why and it seems strage but do it although I don't know why it sometimes work"-instructions that seem just weird... so please, if you don't know what do do either, just skip it.
Click to expand...
Click to collapse
Just flash mannually the boot img that came with the rom. Look in the specific thread of the custom rom or google it .
Sent from my HTC One X+ using Tapatalk
grigoriisi said:
Just flash mannually the boot img that came with the rom.
Click to expand...
Click to collapse
I would if I came out of the bootloop/freeze/whatever it is I'm in right now But thanks for the hint, I'll make sure I flash the rom first before installing the zip via CWM when I'm trying again.
If u keep power plus volume down pressed with the capacitive buttons flashing it will reboot to bootloader . Sometimes u have to keep it pressed for a pretty long time and it will eventually restart . Happened to me not only once
Sent from my HTC One X+ using Tapatalk
grigoriisi said:
If u keep power plus volume down pressed with the capacitive buttons flashing it will reboot to bootloader . Sometimes u have to keep it pressed for a pretty long time and it will eventually restart . Happened to me not only once
Sent from my HTC One X+ using Tapatalk
Click to expand...
Click to collapse
just hold down the power button until the buttons light flash and go off, then let go of power(the phone will reboot). Then quickly press vol down and power and hold until Bootloader shows up. Flash boot.img (fastboot flash boot <name of bootimg>.img
Well, I tried pressing for over two minutes, phone didn'T restart. It's solved after all, the phone ran out of battery and I charged fine afterwards, that way I was able to get into recovery again. Flashed boot.img (thanks for the advice!) manually before installing the zip - everything fine now. Consider this solved.