Hay guys,
for my Desire HD i use the custom rom Jellytime. I used the r6.2, then i flashed an update.zip to r7.
But then i realized, bluetooth is not working and i'm not connected to my google account. So i decided to downgrade to r6.2, so i flashed the .zip as an update.zip. now my phone freezed after the jellytime bootlogo :/
I tried to get to the recovery but when i press power+ volume down, it vibrates 3 times and nothing happens.
does anybody knows what to do? I have a backup, so are there any possibilities, to restore the backup?
slixx
Ouch, did you flash the ROM as an update.zip or the backup?? And what recovery do you got?
hay,
i flashed the r7 as an update.zip, to update my custom rom from r6.2 to r7. and i also flashed the r6.2 as an update.zip to downgrade
I think this was my fault.
i have the lastes version i think - something like 5.0.1.20.
okay,
i used the adb to boot into the bootloader. with the bootloader i booted into the recovery, know i try to restore my backup.
hope it works!
Report back with your progress.
EDIT: and save yourself some trouble next time by using recovery instead of bootloader for installing ROMs
It worked!
i restored the backup, after this i installed an older version of jellytime, flashed gapps, and restored my personal stuff with google
i didn't flashed the rom with the bootloader. i just forgot to flash gapps, after installing the jellytime update ._.
this was the reason why i was not connected to my google account. and the bluetooth function...hmm i dont care cause i don't use it.
but now everything is okay again.
BTW, if you feel like getting back to jelly time, I recommend using v30, or the last 4.1.2 version of jelly time. I think it was only until v9 that jellytime started getting stable, and v30 should be almost bug free.
Sent from my Inspire 4G using xda app-developers app
black screen after update of Jellytime was installed
I flashed in recovery , formatted and all that and picked up the zip of jellytime all installation steps worked fine and once finsihed and the phone was going to finally reboot it just turned black and didn't continue.
HOw do I resolve this? How can I do my backup ? Right now my phone is useless so appreciate a fast answer
Regards
Toby
ektob said:
I flashed in recovery , formatted and all that and picked up the zip of jellytime all installation steps worked fine and once finsihed and the phone was going to finally reboot it just turned black and didn't continue.
HOw do I resolve this? How can I do my backup ? Right now my phone is useless so appreciate a fast answer
Regards
Toby
Click to expand...
Click to collapse
Do you have an unlock bootloader? If so, have you flashed the boot.img in fastboot?
glevitan said:
Do you have an unlock bootloader? If so, have you flashed the boot.img in fastboot?
Click to expand...
Click to collapse
If you mean I am rooted - yes I am. I had the IceColdSandwich before I tried to flash this CM10 JellyTime. I'm not sure I did the fastboot. I did a clean wipe and selected the update rom zip and then followed the steps, inlcuding selecting Desire S and flash (normal?) . It ran through all the installation steps without problems, but when finsihed and during the reboot it hanged (black screen).
ektob said:
If you mean I am rooted - yes I am. I had the IceColdSandwich before I tried to flash this CM10 JellyTime. I'm not sure I did the fastboot. I did a clean wipe and selected the update rom zip and then followed the steps, inlcuding selecting Desire S and flash (normal?) . It ran through all the installation steps without problems, but when finsihed and during the reboot it hanged (black screen).
Click to expand...
Click to collapse
I didn't ask about root, did I? I made 2 simple questions that have not been answered
glevitan said:
I didn't ask about root, did I? I made 2 simple questions that have not been answered
Click to expand...
Click to collapse
So responding a bit more politely;
Do you have an unlock bootloader? To unlock a bootloader is mlostly resolved by doing a root. That I have done so yes in that case I do have a unlocked bootloader. Please correct me if I am wrong in conclusion.
If so, have you flashed the boot.img in fastboot? I am not sure in this. I think I was give two choices - fast boot and normal boot. I selected normal boot.
ektob said:
So responding a bit more politely;
Do you have an unlock bootloader? To unlock a bootloader is mlostly resolved by doing a root. That I have done so yes in that case I do have a unlocked bootloader. Please correct me if I am wrong in conclusion.
Click to expand...
Click to collapse
You are wrong in your conclusion.
bananagranola said:
You are wrong in your conclusion.
Click to expand...
Click to collapse
OK..fine. Still I'm sure I'm unlocked. Now I acctally got the bootloader working - ACE PVT ENG S-OFF RL . So I read your link - thanks it seemed valuable but I didn't get why I needed to open a terminal window (dos window I assume) secondly it didn't work at all since the usb connection didn't connect properly.. I'm sorry for being such a hassle.. . I did before though un zip the folders so if needed - where should the boot image be in order for it to load from the sd card ?
Thanks for the patience
EDIT: I tried to follow the flashboot steps as best I could, but failed to load the image.
ektob said:
ACE PVT ENG S-OFF RL
Click to expand...
Click to collapse
Then you are not unlocked!! I give up.
bananagranola said:
Then you are not unlocked!! I give up.
Click to expand...
Click to collapse
Whatever - I didn't stop me from installing other ROMs. This case is now closed - I changed ROM to CodefireX - worked fine. But sure I will look into it if its necessary - for sure for Jellytime..
I must say you guys really tried to help but any reasons to why I have to unlock bootloader - is that something that have become necessary over time? Maybe its also bad instructions on the ROMS main pages? Why do I need to search 50 different forums to get a simple answer?
Anyway you can give up on me now because I resolved it on my own. Thanks
Because there are additional steps if you are unlocked...
Related
Hello peeps,
I've just come from an iphone so please forgive my stupidity. I've been looking around XDA and various other places for 2 days trying to sort my One X, but don't seem to be making any progress.
I currently only have access to the bootloader
I managed to unlock and root the phone, but then got stuck on a boot loop which I haven't been able to get out of. I was able to get into the OS, but had no cell or wifi, but now I'm just stuck in the bootloader after a failed flash of probably an incorrect RUU. The phone has been relocked.
I ran Vtool from post 7 here http://forum.xda-developers.com/showthread.php?t=1989358, and my main version is 2.17.206.2
I'm in the UK on the o2 network.
Can someone please help??
slixter said:
Hello peeps,
I've just come from an iphone so please forgive my stupidity. I've been looking around XDA and various other places for 2 days trying to sort my One X, but don't seem to be making any progress.
I currently only have access to the bootloader
I managed to unlock and root the phone, but then got stuck on a boot loop which I haven't been able to get out of. I was able to get into the OS, but had no cell or wifi, but now I'm just stuck in the bootloader after a failed flash of probably an incorrect RUU. The phone has been relocked.
I ran Vtool from post 7 here http://forum.xda-developers.com/showthread.php?t=1989358, and my main version is 2.17.206.2
I'm in the UK on the o2 network.
Can someone please help??
Click to expand...
Click to collapse
ok but what do you want to do now? keep it unlocked or not?
matt95 said:
ok but what do you want to do now? keep it unlocked or not?
Click to expand...
Click to collapse
I'd like to unlock it with a custom rom, but I'm quite happy just to have a working phone again.
Additional info, I also have access to CWM
slixter said:
I'd like to unlock it with a custom rom, but I'm quite happy just to have a working phone again.
Additional info, I also have access to CWM
Click to expand...
Click to collapse
Phone is also unlocked again using Hasoons all in one kit.
Happy to hear of a fellow iphone convert :thumbup:
Is there something in particular you did that caused the boot loop?
Do you by chance have a nandroid backup?
jonnyboiii said:
Is there something in particular you did that caused the boot loop?
Click to expand...
Click to collapse
I've got no idea to be honest.
I've got no back ups.
If you have access to cwm then you're not totally out of luck, I think your best option would be to flash a stock rom for your particular phone.
jonnyboiii said:
If you have access to cwm then you're not totally out of luck, I think your best option would be to flash a stock rom for your particular phone.
Click to expand...
Click to collapse
Can you direct me to a stock rom?
did you flash the boot.img when you got bootloops?
matt95 said:
did you flash the boot.img when you got bootloops?
Click to expand...
Click to collapse
Pretty sure i didn't
slixter said:
Pretty sure i didn't
Click to expand...
Click to collapse
that's why you got bootloops... when you flash a rom you need to flash its boot.img too
matt95 said:
that's why you got bootloops... when you flash a rom you need to flash its boot.img too
Click to expand...
Click to collapse
So do i need to flash the boot.img and the rom from CWM and I should be ok?
Just look around in the One-X forum, do some searching, see if you can find a stock rom to download to your computer then move to your phone.
CWM has this handy feature I think in the "mount" tab, where you can mount your phone as a usb device, from which your computer will pick it up and you'll be able to move the roms file to your phone for flashing.
jonnyboiii said:
Just look around in the One-X forum, do some searching, see if you can find a stock rom to download to your computer then move to your phone.
CWM has this handy feature I think in the "mount" tab, where you can mount your phone as a usb device, from which your computer will pick it up and you'll be able to move the roms file to your phone for flashing.
Click to expand...
Click to collapse
Thanks for the info - think I have a rom I can use.
1 more question before i continue, how do i flash the boot.img file? I have a zip with the rom / boot.img
I have mounted as usb storage and copied the zip file across
I've installed CM, after wiping cache, dalvik, system etc, but seem to be stuck on the JB animation screen.
Wondering if this means the OS is installing, or if I'm still stuffed....
I don't know if I need to do something with the boot.img file as the onlyl thing i did was load the zip file for CM
slixter said:
I've installed CM, after wiping cache, dalvik, system etc, but seem to be stuck on the JB animation screen.
Wondering if this means the OS is installing, or if I'm still stuffed....
I don't know if I need to do something with the boot.img file as the onlyl thing i did was load the zip file for CM
Click to expand...
Click to collapse
Personally I've flashed a total of three roms which isn't many, but in all my time spent reading threads of the latest and greatest roms I've never heard anything about a separate boot.img that you needed to flash... (perhaps a One-X specific thing?).
Just be patient with it when it's booting, the first boot after an install always takes longer.
jonnyboiii said:
Personally I've flashed a total of three roms which isn't many, but in all my time spent reading threads of the latest and greatest roms I've never heard anything about a separate boot.img that you needed to flash... (perhaps a One-X specific thing?).
Just be patient with it when it's booting, the first boot after an install always takes longer.
Click to expand...
Click to collapse
I do need to flash the boot.img first.
I'll do that once my battery gets some more charge.
How much charge does it have right now? It's important to always go into using CWM on a substantial amount of battery life. Upwards of %50 is recommended, but but you should do just fine with around 30, that is assuming you're able to tell.
slixter said:
I do need to flash the boot.img first.
I'll do that once my battery gets some more charge.
Click to expand...
Click to collapse
download the rom's boot.img and type with the phone in fastboot mode:
Code:
fastboot flash boot path/to/boot.img
after that your phone will boot up correctly
jonnyboiii said:
How much charge does it have right now? It's important to always go into using CWM on a substantial amount of battery life. Upwards of %50 is recommended, but but you should do just fine with around 30, that is assuming you're able to tell.
Click to expand...
Click to collapse
How do you tell how much charge it has?
matt95 said:
download the rom's boot.img and type with the phone in fastboot mode:
Code:
fastboot flash boot path/to/boot.img
after that your phone will boot up correctly
Click to expand...
Click to collapse
Fastboot won't let me flash cos of the low battery, so will let the phone charge for a bit then try again. Thanks.
ok im truely frustrated after trying to figure this out in past 2 days and reading more than 60 threads/websites.
Problem:
my one x was running 4.0.4 rooted +supre user+CWM, till i got the notification for 4.1 update. i pressed install now and downloaded around 380 MB, during the update phase a red exclamation icon appeared and phone rebooted into 4.0.4.
relocked bootloader, flashed stock recovery and downloaded it again and this time copied the OTA file before pressing install. so i installed and same issue.
uninstalled Avast AV (android) and ran through the same process again, same thing, started up into 4.0.4 again.
unlocked the bootloader, flashed CWM 5.8.4, copied ota file into phone and renamed it to update.zip. ran it from recovery menu and got status 7 error.
downloaded and ran JBFWTOOL21 and followed the instructions, during one of the steps i encountered an error and after restarting the phone i was stock at "HTC One x" with "beatsound" logo at bottom.
NOW NOTHING WORKS
what ive tried so far:
relocked loader and flashed stock recovery and tried Factory Reset, no luck.
unlocked loader and flash CWM and tried wiping cache and wiping disk. nothing.
relocked loader,flashed recovery and ran stock RUU "RUU_ENDEAVOR_U_ICS_40_HTC_ARA_1.28.415.9_Radio_1.1204.103.14_release_25679_signed" but it doesnt work, give an error related to version numbers or something.
extracted system.img, boot.img from RUU temp folder ROM.zip and tried to flash but cant flash system.img (918mb). something about not enough HEAP i think.
from the OTA JB zip extracted recovery.img, boot.img and recovery.img and flashed them. nothing.
downloaded "One_X_All-In-One_Kit_v2.1" and tried kernel flash, nothing.
clearing cache via fastboot command also doesnt work
really appreciate any helpful input guys, im really frustrated. thanks
Oh my.. First, stop unlock and relock of bootloader. Do you have a cwm backup from before all this started? Flashing cwm and restoring that backup will get you far.
The first ota attempt failed due to cwm, always return to stock recovery (recovery.img from your cwm backup image) before applying ota update!
Kind Regards
TwinAdk
unfortunately, no. no backup.
since it all started from the official update i didnt make any backups.
Stop trying flash randomly. Run the following command:
fastboot getvar version-main
it wasnt just random flashing, i starting reading different posts and so tried them all one-by-one to see which works, anyway the output:
version-main: 3.16.415.4
woomera said:
it wasnt just random flashing, i starting reading different posts and so tried them all one-by-one to see which works, anyway the output:
version-main: 3.16.415.4
Click to expand...
Click to collapse
Well that's why the older RUU wouldn't work. You have the latest.
You'll need to go to the ROM backups thread and see if you can get a backup and flash its boot.img and restore it from CWM.
Actually, reboot your PC and try to flash system.img and boot.img again. You will probably need to be locked.
but isnt that the boot.img from "OTA_ENDEAVOR_U_JB_45_S_HTC_ARA_3.16.415.4-2.17.415.2_release_304331jrfus698taf4vm1x"?
cause i have already tried it, didnt work. i have the OTA file.
Modified my post. Look up.
i have boot.img from firmware with hboot 3.16 and 3.19, which one to use?
and the system.img is from stock RUU which is "RUU_ENDEAVOR_U_ICS_40_HTC_ARA_1.28.415.9_Radio_1.1204.103.14_release_25679_signed", will that work?
the OTA JB is a zip file and doesnt have system.img.
Err.. 1.39?
yes
the firmware included in "JBFWTOOL21" is 1.36 which is used by many to manually upgrade to JB but the firmware inside the OTA file itself is 3.19 which is also the version i updated to since i thought its the reason the update doesnt work.
the Hboot version on my phone is 1.39 at the moment.
Hmmm. Looks like you'll have to find a backup in the backups thread and flash it.
BenPope said:
Hmmm. Looks like you'll have to find a backup in the backups thread and flash it.
Click to expand...
Click to collapse
i dont understand, a backup of what? the system.img?
Something similar happened to me....my phone was bootlooping. I flashed a custom rom and it booted up fine... did u try flashing a custom rom?
sridheepan said:
Something similar happened to me....my phone was bootlooping. I flashed a custom rom and it booted up fine... did u try flashing a custom rom?
Click to expand...
Click to collapse
I thought about suggesting that too, but I'm new to flashing so I didn't feel confident enough to do it..
But off the top of my head, a custom rom, complete with boot.img and everything should work..
I'm using http://forum.xda-developers.com/showthread.php?t=2013506, it's super great and support all hboot versions.
No guarantees it will work though.
Kind Regards
TwinAdk
sridheepan said:
Something similar happened to me....my phone was bootlooping. I flashed a custom rom and it booted up fine... did u try flashing a custom rom?
Click to expand...
Click to collapse
guess it worth a try even though i'd rather fix the problem in hand in another fashion.
gonna give it a try and post the results.
k so i downloaded the Blade rom and it worked, thanks "TwinAdk".
so now about JB. should i just use "JBFWTOOL21" or better if i do it manually?
and is this the right order to do it manually: ?
-unlock bootloader
-flash CWM
-flash boot.img
-install from zip in CWM
woomera said:
i dont understand, a backup of what? the system.img?
Click to expand...
Click to collapse
A nandroid backup, like what Clockworkmod recovery makes.
woomera said:
k so i downloaded the Blade rom and it worked, thanks "TwinAdk".
so now about JB. should i just use "JBFWTOOL21" or better if i do it manually?
and is this the right order to do it manually: ?
-unlock bootloader
-flash CWM
-flash boot.img
-install from zip in CWM
Click to expand...
Click to collapse
NP, glad it worked! So now you have a phone that can actually boot up and make phone calls.. Not on the stock rom you wanted, but it's better than when you started this thread
From this point on, you can use a "return to stock" thread for the HOX.
1. Make a NANDROID backup via CWM (so you can get back to what you have now!)
2. Move the backup to your computer, to avoid anything happening to it
3. See this tutorial ([TUT] Getting back to stock after flashing custom roms [Noob friendly])
NOTE: The thread says the following in the top:
NOTE: These instructions require that you have one of the ICS hboot versions in order to work (1.12.0000 or lower). If you have one of the new JB hboots 1.28, 1.31 or 1.33 there is currently no way to return to stock until a JB ruu is released for your device.
Click to expand...
Click to collapse
The "new jb hboots" also refers to 1.39.
I have the 1.39 myself, and i believe i am able to return to stock via my CWM backup of my stock phone, from before i flashed a custom rom the first time.. Is that assumption wrong? Someone more experienced than me to the rescue, please
Kind Regards
TwinAdk
BenPope said:
A nandroid backup, like what Clockworkmod recovery makes.
Click to expand...
Click to collapse
thanks for the clarification
TwinAdk said:
NP, glad it worked! So now you have a phone that can actually boot up and make phone calls.. Not on the stock rom you wanted, but it's better than when you started this thread
From this point on, you can use a "return to stock" thread for the HOX.
1. Make a NANDROID backup via CWM (so you can get back to what you have now!)
2. Move the backup to your computer, to avoid anything happening to it
3. See this tutorial ([TUT] Getting back to stock after flashing custom roms [Noob friendly])
NOTE: The thread says the following in the top:
The "new jb hboots" also refers to 1.39.
I have the 1.39 myself, and i believe i am able to return to stock via my CWM backup of my stock phone, from before i flashed a custom rom the first time.. Is that assumption wrong? Someone more experienced than me to the rescue, please
Kind Regards
TwinAdk
Click to expand...
Click to collapse
i have read the same thing, also "BenPope" mentioned it. so with this version of Hboot (1.39) i cant restore unless its a nandroid backup.
but i dont wanna go back to stock ICS! i wanna finish what i was trying to do in first place, Upgrade to JB.
but no matter what i do i get the "status 7 error". i have tried it with the OTA my phone downloaded and also downloaded it again directly from HTC website via a link from one of the threads in forum.
so status 7 apparently is related to CRC error but how can that be? and what is my option right now to do the upgrade? also bear in mind that before all these happened the normal upgrade process via the "system update" also failed with a red icon error.
Hey guys!
My Xperia Arc S is kinda new - 1 month old.
I was on Xperia Ultimade HD Rom for a while and wanted to install another rom, so i did via CWM Recovery.
All fine.
I wanted to restart my phone but it got stock in Sony Logo.
Because my bootloader cant be unlocked i rooted with kernel downgrade and CWM is not there after flashing due to the wipe.
So i flashed stock .tft with Flashtool and phone booted again.
Now when I'm trying to flash anything my phone gets always stuck in Sony Logo (even when i try Eagleboy's mode without wiping!).
Anyway: I'd like to install a custom rom.
Does anyone how to fix this?
Bootloader: Locked
Phone: LT18i
Rooted: yes
... and I have the 4.0.1.B.0.587 firmware installed right now.
Thanks in advance!
Phone Flashing problem
That's the only problem with locked bootloader's:crying:When you install some stock custom roms you have to wipe system to do a clean install which by default wipes cwm because it is installed in system for locked bootloader's.So if you have a problem with a install you have to flash another .ftf because you wiped cwm recovery.
When I first had arc I had a locked bootloader and it was a pain if something went wrong while flashinghaving to flash again etc! etc! It just got to stage where I had enough and took the plunge and unlocked the bootloader.:good:
I'm afraid it's one of those things you have to live with unless you unlock your bootloader:crying: ( I know you said you can't )there are quite a few stock roms that work but like I said if anything goes wrong you have to flash .ftf again.Probably a case of just trying each one Jader's rom alway's seemed to boot nice:good:
tallman43 said:
That's the only problem with locked bootloader's:crying:When you install some stock custom roms you have to wipe system to do a clean install which by default wipes cwm because it is installed in system for locked bootloader's.So if you have a problem with a install you have to flash another .ftf because you wiped cwm recovery.
When I first had arc I had a locked bootloader and it was a pain if something went wrong while flashinghaving to flash again etc! etc! It just got to stage where I had enough and took the plunge and unlocked the bootloader.:good:
I'm afraid it's one of those things you have to live with unless you unlock your bootloader:crying: ( I know you said you can't )there are quite a few stock roms that work but like I said if anything goes wrong you have to flash .ftf again.Probably a case of just trying each one Jader's rom alway's seemed to boot nice:good:
Click to expand...
Click to collapse
Hi, thanks for your answer
I tried to install 3 different roms till now - i wiped everything.
Then: Boot till sony-logo - I have to flash another tft with flashtool, Root again, and this takes time and is quite annoying.
I came from Samsung Galaxy S there wasn't the problem with the "bootloader" which is really annoying.
So: What should i do now?
I mean my CWM is not persistent and till now no rom worked.
Galaxy3User said:
Hi, thanks for your answer
I tried to install 3 different roms till now - i wiped everything.
Then: Boot till sony-logo - I have to flash another tft with flashtool, Root again, and this takes time and is quite annoying.
I came from Samsung Galaxy S there wasn't the problem with the "bootloader" which is really annoying.
So: What should i do now?
I mean my CWM is not persistent and till now no rom worked.
Click to expand...
Click to collapse
Hi totally agree it is frustrating!:crying: When you install some of these custom rom's they use Aroma installer are you unticking the reboot option in aroma installer and rebooting from cwm?Because you need to reboot that way (you seem to be doing everything right )
(1) Boot to cwm
(2) Wipe cache/Data/Advanced Dalvik cache
(3) Mounts & Storage format data/cache/system (NOTHING ELSE!)
(4) Install .zip on Sd card
(5) Choose options Aroma Installer
(6) Untick reboot option
(7) Reboot from cwm
tallman43 said:
Hi totally agree it is frustrating!:crying: When you install some of these custom rom's they use Aroma installer are you unticking the reboot option in aroma installer and rebooting from cwm?Because you need to reboot that way (you seem to be doing everything right )
(1) Boot to cwm
(2) Wipe cache/Data/Advanced Dalvik cache
(3) Mounts & Storage format data/cache/system (NOTHING ELSE!)
(4) Install .zip on Sd card
(5) Choose options Aroma Installer
(6) Untick reboot option
(7) Reboot from cwm
Click to expand...
Click to collapse
Yes i know , but thats what i did !
Wiped & formatting these settings and unticking reboot in aroma.
But it still doesn't work
Galaxy3User said:
Yes i know , but thats what i did !
Wiped & formatting these settings and unticking reboot in aroma.
But it still doesn't work
Click to expand...
Click to collapse
:crying:Like I said you seem to be doing everything rightHave you tried this rom http://forum.xda-developers.com/showthread.php?t=1994135 it's a two part installation but if I remember right this one seemed to install ok:good:
tallman43 said:
:crying:Like I said you seem to be doing everything rightHave you tried this rom http://forum.xda-developers.com/showthread.php?t=1994135 it's a two part installation but if I remember right this one seemed to install ok:good:
Click to expand...
Click to collapse
Haha i know. Thats why it seems strange for me too. But i need a custom rom and normally i would need a different kernel too.
But thats not possible. Sadly.
So nobody knows what i could change?
Galaxy3User said:
Haha i know. Thats why it seems strange for me too. But i need a custom rom and normally i would need a different kernel too.
But thats not possible. Sadly.
So nobody knows what i could change?
Click to expand...
Click to collapse
Only other thing you could try is changing your base firmware/ftf I notice you are using .587 base ftf try changing to another one, although Some of the custom roms recommend that firmware
Maybe someone else as any ideas
Απ: Flashing problem
If you accidentally formatted system then you removed the cwm. Try flashing the official ftf, install x-parts and redo everything without wiping system partition.
The other choice is to unlock your bootloader and you'll never face this problem again. I voided my warranty less a month after taking my phone, I knew that any problem will come up I could fix it myself
Sent from my Xperia Arc
Retrosid said:
If you accidentally formatted system then you removed the cwm. Try flashing the official ftf, install x-parts and redo everything without wiping system partition.
The other choice is to unlock your bootloader and you'll never face this problem again. I voided my warranty less a month after taking my phone, I knew that any problem will come up I could fix it myself
Sent from my Xperia Arc
Click to expand...
Click to collapse
Yep sure - but my CWM is gone when i wipe data. And I tried this: I flashed stock .ftf and installed xparts, then flashed a ROM without wipe - but doesn't boot and I cant access CWM again :/
And as I said i can't unlock my bootloader.
.. But the strange thing is just:
I even get bootloop when I install EAGLEBOYYS MOD (!) without WIPING anything! (just the recommended for sure)
That should not happen.
Why can't you unlock bootloader? Doing that would solve most of the problems you are facing. You don't have to downgrade to re root. Flash the stock kernel, install a new recovery then try again.
Sent from my Xperia Arc S using xda premium
If I go in service menu it says: Bootloader Unlock Allowed: No !
If I flash stock .ftf root is gone (?) -- RootChecker says that root is gone too.
Galaxy3User said:
Yep sure - but my CWM is gone when i wipe data. And I tried this: I flashed stock .ftf and installed xparts, then flashed a ROM without wipe - but doesn't boot and I cant access CWM again :/
And as I said i can't unlock my bootloader.
Click to expand...
Click to collapse
Galaxy3User said:
If I go in service menu it says: Bootloader Unlock Allowed: No !
If I flash stock .ftf root is gone (?) -- RootChecker says that root is gone too.
Click to expand...
Click to collapse
First of all - this thread: http://forum.xda-developers.com/showthread.php?t=1683957
I advice you to take step by step STRICTLY.
Or you can try to root with the FlashTool but I'm not sure if it will work with locked BL.
After that: http://forum.xda-developers.com/showthread.php?t=1955248
And for additional info: http://forum.xda-developers.com/showthread.php?t=1955248
TopperBG said:
First of all - this thread: http://forum.xda-developers.com/showthread.php?t=1683957
I advice you to take step by step STRICTLY.
Or you can try to root with the FlashTool but I'm not sure if it will work with locked BL.
After that: http://forum.xda-developers.com/showthread.php?t=1955248
And for additional info: http://forum.xda-developers.com/showthread.php?t=1955248
Click to expand...
Click to collapse
Thats how i rooted my Arc S!
Thats the only method that is working with locked BL.
And well, i took all the steps mentioned in the second topic you posted..
If you can't get it to work (stuck on Sony logo), then flash this in flash tool and then root again and do it one more time.
It´s ICS and kernel for Arc S but works fine on regular Arc. I use it myself on my Arc.
http://www.mediafire.com/?r0anos8emtx4iiy password is MMAS (If asked for)
Good luck and have fun with your superfast Arc with Ultimate HD™ ROM 2.0.
Click to expand...
Click to collapse
And this download link doesnt work :/
Galaxy3User said:
Thats how i rooted my Arc S!
Thats the only method that is working with locked BL.
And well, i took all the steps mentioned in the second topic you posted..
And this download link doesnt work :/
Click to expand...
Click to collapse
Here it is:
https://www.box.com/s/yu3dbp760kkyw7osoo41
https://www.box.com/s/9prbhnvkmyrglyoyl20j
TopperBG said:
Here it is:
https://www.box.com/s/yu3dbp760kkyw7osoo41
https://www.box.com/s/9prbhnvkmyrglyoyl20j
Click to expand...
Click to collapse
I flashed these files already after i got stuck at SONY logo but doesnt help..
Galaxy3User said:
I flashed these files already after i got stuck at SONY logo but doesnt help..
Click to expand...
Click to collapse
What does mean "doesnt help" ?
What are you trying to do and dont work, what is messages, what happens, did you have newest version of FlashTool, did you have installed ADB drivers, what's the error ?
TopperBG said:
What does mean "doesnt help" ?
What are you trying to do and dont work, what is messages, what happens,
did you have newest version of FlashTool, did you have installed ADB drivers,
what's the error ?
Click to expand...
Click to collapse
I mean when i flash this .ftf and reroot and install CWM all works fine.
But when I try to flash any ROM and doing all wipes etc. correctly it still gets stuck at SONY logo!
I have newest version of flashtool and ADB drivers installed. In flashtool there is no error.
Galaxy3User said:
I mean when i flash this .ftf and reroot and install CWM all works fine.
But when I try to flash any ROM and doing all wipes etc. correctly it still gets stuck at SONY logo!
I have newest version of flashtool and ADB drivers installed. In flashtool there is no error.
Click to expand...
Click to collapse
Which ROM are you trying to flash?
Is that ROM for locked BL ?
I've been following xda for a while now, but this is my first post so please take it easy on me, if I posted this in the wrong thread.
I am not new to rooting and costom roms. I have successfully rooted one phone before and I used it for a more than a year, didn't have any problems at all. Yesterday I got myself HTC One X and today I tried to root it and somehow got myself stucked/bricked.
The phone is stuck on HTC Quietly brilliant screen. I can get into bootloader, but thats it. What can I do? I already tried to flash back the original ROM, but couldn't get device to connect to PC. I looked all over the forum and googled it and still can't seem to find the solution. Any help would be highly apprechiated.
*** UNLOCKED ***
ENDEAVOUR PVT SHIP S-ON RL
HBOOT-1. 39. 0000
CPLD-None
MICROP-None
RADIO-5. 1204. 162A. 29
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW Secure boot: enabled
MODEM PATH : OFF
Which rom did you flash? You have to flash the boot.img from within the .zip file.
Sent from my HTC One X using XDA Premium App
Desaf said:
Which rom did you flash? You have to flash the boot.img from within the .zip file.
Sent from my HTC One X using XDA Premium App
Click to expand...
Click to collapse
Something went wrong when I tried to root it. It probably didn't go through with it. I tried to flash a stock rom back, after I got stuck but it won't go, because I can't connect with PC.
Straxer said:
Something went wrong when I tried to root it. It probably didn't go through with it. I tried to flash a stock rom back, after I got stuck but it won't go, because I can't connect with PC.
Click to expand...
Click to collapse
Which recovery have you installed? If it's twrp you can mount SD from there put a custom ROM on it with superuser (root) flash that ROM from recovery and you have root. It's by far the easiest way to flash a custom ROM to get root instead of getting root on a stock ROM.
And BTW, the hox is not easy to brick of you ask me so don't panic (yet)
Sent from my HTC One X using xda app-developers app
Straxer said:
Something went wrong when I tried to root it. It probably didn't go through with it. I tried to flash a stock rom back, after I got stuck but it won't go, because I can't connect with PC.
Click to expand...
Click to collapse
need to be more specific. did it happend just after you tried rooting? or did you try to install/flash rom/kernel/(recovery etc)
try to root again . use this tool. its the easiest. http://forum.xda-developers.com/showthread.php?t=1604439
i m no expert but from my experience your problem occurs when you flash incampatable kernel..also, we cannot s-off our one x so you have to flash the kernel (named as boot.img, if not , you rename it) manually via fastboot. (download sdk tools) when flashing new rom.
dragonflame8712 said:
need to be more specific. did it happend just after you tried rooting? or did you try to install/flash rom/kernel/(recovery etc)
try to root again . use this tool. its the easiest. http://forum.xda-developers.com/showthread.php?t=1604439
i m no expert but from my experience your problem occurs when you flash incampatable kernel..also, we cannot s-off our one x so you have to flash the kernel (named as boot.img, if not , you rename it) manually via fastboot. (download sdk tools) when flashing new rom.
Click to expand...
Click to collapse
As you said, I used that tool. I installed HTC Drivers, registered at HTCDev, got TokenID, submitted it and unlocked Bootloader. Everything went ok, the only thing that was wrong was with the MTP device driver, which failed to install every time. (I think that was the reason why it disconnected with PC). I then procceded to Perm Root where it got stuck on the phone with red explanation point screen. From there I could still reset phone to a normal state like there was no changes.
Then I tried InsecureBootAndRoot, followed the steps and shortly after it started rooting, the program closed and it was stuck here. I tried to do it again, but I got the message: Waiting for a device.
Can you explain in more detail, how to flash kernel manually, if my computer doesn't recognize device?
dragonflame8712 said:
need to be more specific. did it happend just after you tried rooting? or did you try to install/flash rom/kernel/(recovery etc)
try to root again . use this tool. its the easiest. http://forum.xda-developers.com/showthread.php?t=1604439
i m no expert but from my experience your problem occurs when you flash incampatable kernel..also, we cannot s-off our one x so you have to flash the kernel (named as boot.img, if not , you rename it) manually via fastboot. (download sdk tools) when flashing new rom.
Click to expand...
Click to collapse
Ok, I think I know how to flash kernel. Can you tell me which one to chose or give me a link to it please.
Straxer said:
Ok, I think I know how to flash kernel. Can you tell me which one to chose or give me a link to it please.
Click to expand...
Click to collapse
Have you flashed a rom yet or are you still on stock? Do you prefer sense roms or AOSP/cyanogen?
gffmac said:
Have you flashed a rom yet or are you still on stock? Do you prefer sense roms or AOSP/cyanogen?
Click to expand...
Click to collapse
No, I haven't. I am now practically without a rom (I think). I would prefer custom rom (like cyanogen).
The problem is that everytime I try to do anything for example, flash back factory RUU, I get the message: device not found. Is this because of problem with drivers. Someone please help me out
Straxer said:
The problem is that everytime I try to do anything for example, flash back factory RUU, I get the message: device not found. Is this because of problem with drivers. Someone please help me out
Click to expand...
Click to collapse
If you want cyanogen you need a custom recovery like TWRP. That recovery you can flash through fastboot but like you said there is something wrong with your drivers. Did you install HTC sync on your PC. And did you enable USB debugging in your current ROM?
Sent from my HTC One X using xda app-developers app
J_Dutch said:
If you want cyanogen you need a custom recovery like TWRP. That recovery you can flash through fastboot but like you said there is something wrong with your drivers. Did you install HTC sync on your PC. And did you enable USB debugging in your current ROM?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Yes, I got CWM recovery. I just discovered that. I installed and uninstalled all the latest htc drivers and htc sync many times. It enabled debugging mode, the last time I was on stock rom (don't know if you can check that now in bootloader?) If my phone is not rooted, than I can't install custom rom right, because I think it isn't. how can I check that?
Straxer said:
Yes, I got CWM recovery. I just discovered that. I installed and uninstalled all the latest htc drivers and htc sync many times. It enabled debugging mode, the last time I was on stock rom (don't know if you can check that now in bootloader?) If my phone is not rooted, than I can't install custom rom right, because I think it isn't. how can I check that?
Click to expand...
Click to collapse
No you don't need root to flash a custom ROM. Flashing a custom ROM will give you root. So you are doing things the wrong way. If you can get into cwm then make sure you have cyanogen.zip and gapps.zip on your phone. Extract(copy) the boot.IMG file from cyanogen. Then from cwm do a nandroid backup, full wipe except SD card, flash cyanogen, flash gapps. Then from cwm boot into boot loader, make sure you place the extracted boot.IMG in your fastboot folder on PC and in command line give commands: fastboot flash boot boot.img then: fastboot erase cache then: fastboot reboot Then you can unplug USB and it will start cyanogen and you have root.
Sent from my HTC One X using xda app-developers app
J_Dutch said:
No you don't need root to flash a custom ROM. Flashing a custom ROM will give you root. So you are doing things the wrong way. If you can get into cwm then make sure you have cyanogen.zip and gapps.zip on your phone. Extract(copy) the boot.IMG file from cyanogen. Then from cwm do a nandroid backup, full wipe except SD card, flash cyanogen, flash gapps. Then from cwm boot into boot loader, make sure you place the extracted boot.IMG in your fastboot folder on PC and in command line give commands: fastboot flash boot boot.img then: fastboot erase cache then: fastboot reboot Then you can unplug USB and it will start cyanogen and you have root.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Okay, so I installed latest CM10 and gapps. How to extract boot.IMG form cyanogen?
I extracted boot.img from Cyanogenmod zip file (that is the same for everybody, right?). I did a Nandroid backup like you said But now all I can do is wipe data/factory reset (CWM Recovery v5.8.4.0). I can't find an option to wipe only selected things.
I was blind, but now I see! I got it running. Everything works great. Thanks to all of you, especially to J_Dutch :victory:
Straxer said:
I was blind, but now I see! I got it running. Everything works great. Thanks to all of you, especially to J_Dutch :victory:
Click to expand...
Click to collapse
Glad you got it up and running! Hope you enjoy the custom ROM, with every other ROM you flash you will need that boot.img to be flashed separately.
Ps. Please hit the thanks button if somebody helps you. It's designed for that.
Sent from my HTC One X using xda app-developers app
J_Dutch said:
Glad you got it up and running! Hope you enjoy the custom ROM, with every other ROM you flash you will need that boot.img to be flashed separately.
Ps. Please hit the thanks button if somebody helps you. It's designed for that.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Just came back to do that. Much appreciated!
Hi XDA,
I decided to install CM 11 on my HTC, and so I unlocked the bootloader, and I then rooted it. I also updated my HBOOT to 1.39. After this I installed CWM and backed up, and attempted to flash the latest CM for the One X. Firstly I had an issue with the status 7 error, but managed to overcome that by updating my CWM (Now running 6.0.4.7 Touch Recovery). At the moment I do not have an OS, and all attempts to flash a new ROM are successful, however when I reboot I am still stuck at a frozen boot screen. ("HTC. Quietly Brilliant"). Even restoring my backup doesn't work.
Any help would be much appreciated.
Apologies if this is in the wrong section.
Thank you
JamesNZ7 said:
Hi XDA,
I decided to install CM 11 on my HTC, and so I unlocked the bootloader, and I then rooted it. I also updated my HBOOT to 1.39. After this I installed CWM and backed up, and attempted to flash the latest CM for the One X. Firstly I had an issue with the status 7 error, but managed to overcome that by updating my CWM (Now running 6.0.4.7 Touch Recovery). At the moment I do not have an OS, and all attempts to flash a new ROM are successful, however when I reboot I am still stuck at a frozen boot screen. ("HTC. Quietly Brilliant"). Even restoring my backup doesn't work.
Any help would be much appreciated.
Apologies if this is in the wrong section.
Thank you
Click to expand...
Click to collapse
Have you flashed boot.img?
mr93 said:
Have you flashed boot.img?
Click to expand...
Click to collapse
I haven't, no. Is this unzipping the rom and then flashing the .img?
Yeah take out the boot.img indeed and flash it via fastboot
Mr Hofs said:
Yeah take out the boot.img indeed and flash it via fastboot
Click to expand...
Click to collapse
Aaaahhh THANK YOU SO MUCH !!! Working beautifully!!
Such a simple solution.
mr93 said:
Have you flashed boot.img?
Click to expand...
Click to collapse
Thanks a billion !!