Related
Hi, i had a S4 which got a broken screen and costs too much to fix a the moment so i brought a Telstra HTC ONE XL off a friend for $100.
I do like the phone but was over the 4.2.1 software as used to the 4.3 on the S4 which i rooted and put on CM10.
I tried with this phone to put on the nightly cm 10.3 but i hit a problem ,when install the nightlies it boot loops and when i try install the stable 10.1 it fails with an error which i do belive is to do with my V2 hboot.
I downloaded the RRU which is supposted to update the hboot to v3 then i can install cm10.3 (aparently) but when i run the rru it fails saying not for my phone.
RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed_With_Partial
I have unlocked through htcdev and rooted it ok.
Im stuck now though as i pressed backup current original rom which turns out its not.
The phone details are
CID TELST001
Model: HTC ONE XL TELSTRA
If someone can tell where to either find the newest telstra rru for my phone or how to update my hboot so i can use cm10?
My phone is pretty useless at the moment
stueee said:
I downloaded the RRU which is supposted to update the hboot to v3 then i can install cm10.3 (aparently) but when i run the rru it fails saying not for my phone.
Click to expand...
Click to collapse
Where are you getting CM from (link it) and what is the file named? CM will typically have the phone's code name (EVITA) in the file name. If the code name ENDEAVORU is in the file name, it is in fact for the wrong device, as the ENDEAVORU is for the quad core Tegra3 (non-LTE) version, which is completely different hardware.
Also, I don't know if 10.3 is even released yet for our device, or for the ENDEAVORU for that matter. I think you might be confused about what you are flashing. So again, link what you are trying to install.
The reason you couldn't run that RUU is because the CID check wouldn't allow it, it's looking for an at&t CID which you don't have. Getting s-off disables the security check which would let you run any Evita RUU but you need to get a ROM to boot first before you try that. You also need SuperCID.
Your best bet is probably to flash an older Sense ROM (4.0 or 4.1), then you can at least boot, and get SuperCID and s-off so you can run the 3.18 RUU to meet the requirements for the latest cm ROMs.
Sent from my Evita
timmaaa said:
The reason you couldn't run that RUU is because the CID check wouldn't allow it, it's looking for an at&t CID which you don't have.
Click to expand...
Click to collapse
For some reason, I got confused and thought the OP was saying that the ROM install was failing. But it clearly says the RUU (or "rru" anyway) failed.
But yes, you can only run an RUU for your carrier version. So you will need s-off to run the AT&T RUU (the RUU referenced in the OP).
But still confused about the mention of CM10.3. From what I can see, it doesn't exist for either our EVITA, or the ENDEAVORU.
Maybe he meant cm10.2 and it was a typo?
Sent from my Evita
timmaaa said:
Maybe he meant cm10.2 and it was a typo?
Click to expand...
Click to collapse
Could be. Although if so, its a type that appears twice.
It seems fairly common for folks to try to install the wrong CM (wrong device). So I want to make sure the OP isn't doing that.
redpoint73 - the CM i downloaded and installed was from http://get.cm/?device=evita and i tried
cm-10.2-20131030-NIGHTLY-evita.zip which installed but bootloops
and then i tried the stable - cm-10.1.3-evita.zip which gave me the failed error.
stueee said:
redpoint73 - the CM i downloaded and installed was from http://get.cm/?device=evita and i tried
cm-10.2-20131030-NIGHTLY-evita.zip which installed but bootloops
and then i tried the stable - cm-10.1.3-evita.zip which gave me the failed error.
Click to expand...
Click to collapse
Okay, neither of those are CM10.3, as stated in your first post. Please post accurate information to prevent form confusing those that are trying to help.
What hboot are you currently on? Its listed on the bootloader screen.
What version of TWRP?
You should be able to mount SD in TWRP, put a Sense ROM on the phone, and get back up and running.
Hi Red,
Sorry i typed out that post at almost 1am after pulling my hair out over a few hours and got a little confused.
My hboot is 2.15 and twrp is 2.6.3.0 which I believe is the latest.
What sense rom would work on mine as i really need this working now as i cant find a rom to suit anywhere with my lesser expertees.
I tried changing the cid using the super cid Telstra bat file but it won't recognize the phone as its not loaded, i tried in off state, bootloader, fastboot and twrp but is just keeps saying cant find phone.
I also tried the hex editor method but it didnt seem to update the CID after i completed it without errors.
thanks for you help.
redpoint73 said:
Okay, neither of those are CM10.3, as stated in your first post. Please post accurate information to prevent form confusing those that are trying to help.
What hboot are you currently on? Its listed on the bootloader screen.
What version of TWRP?
You should be able to mount SD in TWRP, put a Sense ROM on the phone, and get back up and running.
Click to expand...
Click to collapse
With 2.15 hboot, you cannot modify the files required for supercid.
You can try the ever so risky jet tool. But this tool deliberately bricks to downgrade your hboot.
Sent from my HTC One XL using xda app-developers app
Any recent Sense ROM will suit your current setup, have a look here and you'll find a whole bunch. Unfortunately for you the 2.15 hboot has write protection enabled so there's no way you can get SuperCID (abd therefore can't get s-off), at least not until an exploit is released.
When you tried to flash CM did you also flash the boot.img via fastboot afterwards? You're s-on so that's necessary to get it to boot. Phones on a higher hboot like yours are unable to flash the boot.img through recovery so it must be done manually.
All you do is retrieve the boot.img from the root of the ROM zip, put it in your fastboot folder on your PC, and after you've flashed the ROM in recovery you reboot to bootloader, connect the phone to the PC, open a command prompt from within your fastboot folder (shift + right click anywhere in the folder then select open command prompt here), then give the following command:
fastboot flash boot boot.img
Once that's done you can reboot the phone and it should boot into the ROM.
Sent from my Evita
stueee said:
My hboot is 2.15
Click to expand...
Click to collapse
That's pretty important. This is the reason why the older CM10.1 failed to install. CM was having issues with older hboots, so a script was added to require hboot 2.14.
Once hboot 2.15 came along, folks found that CM failed to install since the install script explicitly requires 2.14. Later versions include hboot 2.15 in the install script.
As exad and timmaaa mention, SuperCID (and therefore s-off) are not possible on hboot 2.15. So you are stuck with s-on (assuming that is what you are on now). It also means you can't currently run any RUU. Reason being, with s-on you can't run older RUUs, RUUs from another carrier, and there are no RUUs based on hboot 2.15. No "current" RUU exists (for your hboot), you can't run "previous" RUUs with the S-on restriction. So therefore you can't currently run any RUU.
But hboot 2.15 will work with newer versions of CM (and other AOSP ROMs which have been recently updated) as well as any Sense ROMs. But with s-on, you need to extract boot.img and flash manually with fastboot every time you install a ROM (as timmaaa points out). If you did not do this, this is why flashing the recent CM10.2 nightly resulted in a bootloop. Failure to falsh boot.img is the most common reason for bootloop after flashing a ROM.
stuck in bootloop
ive recently have been flashing different roms onto my htc one with no problem..then i decided to try the google play edition and realised i had to be s-off...now i have super cid 11111111 and s-off and was running skydagon 14.1 with no prob...today i did a nand backup and thought i would try the liquid rom then half way through the fresh install (i wiped cache and dalvik first)my phone shut down and boots up into a loop..if i go to recovery (twrp 2.6.3.3) it only stays in recovery a few seconds then goes back to the start of bootloop...i have tried cwmr also...i have otg cable and have used adb a few times however im not highly skilled so any help would be appreciated...apologies on the excessive post..
martin-m7 said:
ive recently have been flashing different roms onto my htc one with no problem..then i decided to try the google play edition and realised i had to be s-off...now i have super cid 11111111 and s-off and was running skydagon 14.1 with no prob...today i did a nand backup and thought i would try the liquid rom then half way through the fresh install (i wiped cache and dalvik first)my phone shut down and boots up into a loop..if i go to recovery (twrp 2.6.3.3) it only stays in recovery a few seconds then goes back to the start of bootloop...i have tried cwmr also...i have otg cable and have used adb a few times however im not highly skilled so any help would be appreciated...apologies on the excessive post..
Click to expand...
Click to collapse
You're in the wrong forum, buddy. This is the HTC One XL forum.
Hi all,
I installed MaximusHD ROM and messed up my partitions so now I have only 2 GB available. I want to fix it by going back to stock ROM.
Currently my phone is superCID, s-off, hboot 2.16, radio 1.20.
From what I've read I should be able to install any RUU but I have not been able to. I tried to do it in fastboot mode and in normal mode when Android is on but without success. Setup starts but some unknown error appears, I think it is error 105... or 150.
I've followed some guides here but the setup won't work because of the unknown error Do I have to look for a specific RUU ?
The only thing that I have not done is to lock my bootloader prior to installing the RUU. However the guides state that I do not have to lock it if my phone is S-OFF.
If I do fastboot getvar all next to "version main" I see nothing, it is empty.
Please help!
I changed my CID to HTC__001 but this did not help Please help me to get back to stock !
mkoev said:
I changed my CID to HTC__001 but this did not help Please help me to get back to stock !
Click to expand...
Click to collapse
I had similar issue what I ended up doing was pulling the recovery image out of the install package and flashing it via fastboot and it restored my sd storage I had to use the modified recovery supplied I would try that- I believe you could change your cid to whatever RUU your trying to flash and it should work also,its seems some have downgraded to hboot 2.1.5 to flash RUU (read,read,read)best of luck
Somehow I fixed my problem yesterday. I was not able to install RUU however I was able to change my hboot back to 1.04 ... afterwards I installed the latest version of TWRP and suddenly I was able to see stuff on my internal memory. Prior to that TWRP 2.3.x.x was not able to detect my whole internal memory. Anyway... my advice to people is not to install MaximusHD via CWM although it says that it works. It does work, but it is easier with TWRP
So this is my situation,
after using MaximusHD 10.0.0, I would like to go back to my stock rom. The problem is that I lost my nandroid back-up because of flashing another update version of twrp. I'm a little bit new to all this android flashing stuff, so I was wondering if anybody could help me?
I was planning of using a guild for this, which i can't post because i'm a new user, who says just to relock bootloader and use a RUU. But instead of using the T-mobile version, I wanted to use a RUU file for Europe.
Before I was going to start with this, I wanted to make a nandroid back-up, but CWM can't mount my SD-card.
So, how do I start going back to the stock rom from MaximusHD 10.0.0 on my HTC One S C4?
Ask for more info if needed!
[Update]: I found a solution for my can't mount SD Problem. So can somebody help me finding a right RUU? (I live in Belgium)
Try to flash TWRP, then you can backup.
And then flash an RUU
AndroGeek974 said:
Try to flash TWRP, then you can backup.
And then flash an RUU
Click to expand...
Click to collapse
So, do I need to first Relock my bootloader before I run the RUU? Or is it not needed because I'm S-OFF?
im also S-Off and on Hboot 2.16, now to get back to 2.15 is this the right way ?
flash my backup of stock 3.16 Jelly Bean in TWRP
relock the bootloader
Flash 3.16 RUU.exe
Thanks
So, last little question!
What happens if the RUU gives an error?
Does your ROM is still the way it was before if you cancel the RUU after error?
Or is your ROM deleted?
FantasyGamer said:
So, last little question!
What happens if the RUU gives an error?
Does your ROM is still the way it was before if you cancel the RUU after error?
Or is your ROM deleted?
Click to expand...
Click to collapse
Nothing happens, the installer stops and you are still the same as you were. So it doesn't hurt to try them.
[Update]: I found a solution for my can't mount SD Problem. So can somebody help me finding a right RUU? (I live in Belgium)[/QUOTE]
what is the solution , I have the exact same problem as you and want my stock rom back ?
beerfly said:
[Update]: I found a solution for my can't mount SD Problem. So can somebody help me finding a right RUU? (I live in Belgium)
Click to expand...
Click to collapse
what is the solution , I have the exact same problem as you and want my stock rom back ?[/QUOTE]
It's really easy, you just have to reflash the modded version of TWRP for MaximusHD 10.0.0. All the other versions of TWRP or cwm won't work.
FantasyGamer said:
what is the solution , I have the exact same problem as you and want my stock rom back ?
Click to expand...
Click to collapse
It's really easy, you just have to reflash the modded version of TWRP for MaximusHD 10.0.0. All the other versions of TWRP or cwm won't work. [/QUOTE]
its the version 2.6.1.0 is it, and have to flash it via fastboot right ?
[QUOTE/]its the version 2.6.1.0 is it, and have to flash it via fastboot right ? [/QUOTE]
Yes, that's the one! But take the file shipped with MaximusHD 10.0.0 because it's a modded version, and not the normal one of 2.6.1
FantasyGamer said:
[QUOTE/]its the version 2.6.1.0 is it, and have to flash it via fastboot right ?
Click to expand...
Click to collapse
Yes, that's the one! But take the file shipped with MaximusHD 10.0.0 because it's a modded version, and not the normal one of 2.6.1 [/QUOTE]
Yes I know its modded version , I tried to push it but it cant be done, Since I have CWM recovery, i cant put this TWRP one from maximus, it says failed: remote not allowed. I think it is because I relocked my bootloader, If I have to unlock it again, i wont be able to do it since cant use sd properly, so its doomed circle i think, need really big help guys . thanks in advance !
This is what i did.
1.oem relock
2. install org RUU, i downloaded one of the exe's and just let it do it's thing.
3. done.
4. rooted
5. flashed twrp
Okay,
So I just want to be sure about this.
Are these the ONLY steps I have to take?
1) Put device in Fastboot USB
2) Run RUU -> in this case http://www.androidruu.com/getdownload.php?file=Ville/RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4.exe
3) I have my old phone back with stock rom.
More info:
ROM: MaximusHD 10.0.0
***TAMPERED***
***UNLOCKED***
VLE PVT SHIP S-OFF RL
CID-11111111
HBOOT-2.16.0000
RADIO-1.20.50.05.16
FantasyGamer said:
Okay,
So I just want to be sure about this.
Are these the ONLY steps I have to take?
1) Put device in Fastboot USB
2) Run RUU -> in this case http://www.androidruu.com/getdownload.php?file=Ville/RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4.exe
3) I have my old phone back with stock rom.
More info:
ROM: MaximusHD 10.0.0
***TAMPERED***
***UNLOCKED***
VLE PVT SHIP S-OFF RL
CID-11111111
HBOOT-2.16.0000
RADIO-1.20.50.05.16
Click to expand...
Click to collapse
Relock the phone first, i don't know why, but i read on the forums that you have too when returning to stock.
1. in cmd "fastboot oem lock" phone now says "relocked"
2. from fastboot run RUU exe and wait.
3. done
In my case the RUU flashed me back to hboot 1.13, so install all updates from htc, then it updated to hboot 2.15.
So now you need to re-unlock the phone, and flash a new recovery.
If you want CM11 hboot 2.15 you need to flash modded recovery from http://forum.xda-developers.com/showthread.php?t=2528113
If you don't CM11 flash will fail.
Go here http://forum.xda-developers.com/showthread.php?t=1583427&highlight=tutorial and follow STEP 1.
That should re-unlock the phone.
STEP 2 flashes new recovery. Skip STEP 3.
After recovery has been flashed, boot into recovery, then press "reboot" and reboot to bootloader, if you flashed twrp it will ask to install superSU.
Now you are ready to flash anything again.
Is it necessary to re unlock?
Because i'm not planning on changing rom soon.
Thanks for the help!
You don't need to flash new rom, if you want to stay on stock you can, stock will still boot fine afterwards.
fusk said:
You don't need to flash new rom, if you want to stay on stock you can, stock will still boot fine afterwards.
Click to expand...
Click to collapse
I know, but is doesn't hurt not to re-unlock, right?
I succesfully went back to Android 4.0.4 :laugh:
I now want to perform an OTA . Do I first need to S-ON?
FantasyGamer said:
I succesfully went back to Android 4.0.4 :laugh:
I now want to perform an OTA . Do I first need to S-ON?
Click to expand...
Click to collapse
Just make sure you aren't SuperCid, or it could brick the phone.
I am currently running on MaximusHD rom. My phone's details are:
ROM: MaximusHD 10.0.0
***TAMPERED***
***UNLOCKED***
VLE PVT SHIP S-OFF RL
CID-11111111
HBOOT-2.16.0000
RADIO-1.20.50.05.16
When i executed RUU, it showed me "incorrect image. Find the correct RUU."
Which RUU i have to download for my phone?
So my problem is the next one, i recently formated my sdcard which had maximushd rom on it and running as it was my daily rom, at te time i was on supercid but then i had started to do stupid things , i had s-on back on, changed the cid to roger001 but the phone is bought from germany unbranded ( i don`t know what was in my head), now i have managed to install a new rom on the phone but
My storage shows only 48mb, and i have tryed the tricks with stock recovery and then twrp 2610 it shows up 12gb but then after i install the rom is back to 48 or even 0mb,
So how the hell i solve this? and how to get back to stock, as i have tried to install a oficial ruu (zip or exe) and it says to get the correct rom.
OTA_Ville_U_JB_45_S_Globalive_WWE_3.16.1500.7_1.11.50.05.28_10.27.50.08L_release_3049068z393w1fez9cc9lt.zip on supercid didnt work, then i had changed it to roger001 it didn`t (obviousely) i have tried to change the cid again but it won`t let me without s-off but the first time it did let me, now my phone frezzes,
RUU_Ville_U_Rogers_WWE_1.84.631.9_Radio_0.17.31501S.10_2_10.27.31501S.10L_release_265373_signed.exe on this one now it says that my usb connection is lost right at the begining running it from windows or if i am flashing it trough fastboot it says remote sygnature fail,
So what i am doing wrong, at the moment i have managed to install magiorom with the storage issue,
my hboot is 2.16.0000
my radio is 1.20.50.05.16
htc one s ville(s4)
can someone help me to sort things out please
i have tried to change the cid trough fastboot comands or with hxd editor with no luck, please someone help me i am on this problem for days now, i have magiorom installed but it has storage problem as i am coming from maximus hd which i understood it caused the storage problem beacause of the firmware
Ok so first wipe your sd card for full storge
The download and use rumrunner if ths t dose not work use moonshine and if that one dise not work use firewater <this is for s-off
Now go back to your original cid and find stock recovery and run the ruu fir your phone
If you got this far then your phone is back to stock with s-off
Sent from my SPH-L710 using Nightmare Rom
Flashalot said:
Ok so first wipe your sd card for full storge
The download and use rumrunner if ths t dose not work use moonshine and if that one dise not work use firewater <this is for s-off
Now go back to your original cid and find stock recovery and run the ruu fir your phone
If you got this far then your phone is back to stock with s-off
Sent from my SPH-L710 using Nightmare Rom
Click to expand...
Click to collapse
thanks for the reply i have managed to sort things out with rumrunner ) now i am back to stock but with s-off )and rooted ) thank you
Hello I have supercid, s-off and previously flashed MAXIMUSHD ROM and that's on hboot 2.16 so I got board and sick of sense 5 and I want to try out one of the kitkat ROMs but I need hboot 2.15 for that and yes I know that there are hboot 2.16 kitkat roms but they are unstable so can someone tell me step by step how to downgrade hboot 2.16 to 2.15 because I'm quite of a dumb person
the_ziom said:
Hello I have supercid, s-off and previously flashed MAXIMUSHD ROM and that's on hboot 2.16 so I got board and sick of sense 5 and I want to try out one of the kitkat ROMs but I need hboot 2.15 for that and yes I know that there are hboot 2.16 kitkat roms but they are unstable so can someone tell me step by step how to downgrade hboot 2.16 to 2.15 because I'm quite of a dumb person
Click to expand...
Click to collapse
This is how I proceed :
1) Downgrade to 2.15 hboot by flashing the old firmware (extract firmware.zip and flash as you did for MaximusHD)
2) Run the latest RUU to get everything clean (I flashed this one)
3) Flash custom recovery with fastboot (TWRP 2.3.X.X)
4) You're done !
benJX said:
This is how I proceed :
1) Downgrade to 2.15 hboot by flashing the old firmware (extract firmware.zip and flash as you did for MaximusHD)
2) Run the latest RUU to get everything clean (I flashed this one)
3) Flash custom recovery with fastboot (TWRP 2.3.X.X)
4) You're done !
Click to expand...
Click to collapse
thank you but i have super cid and from what i have read i have to install the ruu according to my cid
tell me if im right
the_ziom said:
thank you but i have super cid and from what i have read i have to install the ruu according to my cid
tell me if im right
Click to expand...
Click to collapse
In fact, the CID matters if you have one from an operator (have a look here, but not the last one, it's the superCID), in this case, you have to choose a RUU according to your operator.
But being superCID, you can run any RUU, so run the last generic one (see my link) and everything will be ok to start from official clean install. Of course you'll stay S-OFF after running the RUU.
The only thing requested is to be on 2.15 hboot, that's why you have to downgrade to older firmware in order to run this.
Hope it will help.
I have kind of a similar question. After moonshine S-OFF, I'm on modified moonshine HBOOT 2.15.4444. Now I want to go back to the stock HBOOT 2.15.0000. Do I just need to run the RUU to go back? I'm bootloader unlocked, CID T-MOB010, TWRP recovery, and I flashed radio 1.20. Do I need to flash radio back to match the RUU before I run it?
Thanks
dr3amsINdigital said:
I have kind of a similar question. After moonshine S-OFF, I'm on modified moonshine HBOOT 2.15.4444. Now I want to go back to the stock HBOOT 2.15.0000. Do I just need to run the RUU to go back? I'm bootloader unlocked, CID T-MOB010, TWRP recovery, and I flashed radio 1.20. Do I need to flash radio back to match the RUU before I run it?
Thanks
Click to expand...
Click to collapse
Running an RUU is the safest option, although its a bit hit and miss getting the RUU to run correctly. Flashalot recently made a guide (http://forum.xda-developers.com/showthread.php?t=2678700) if you run into any problems. I would try it without changing the radio, if it doesn't work then flash the matching one and go from there.
Now I cannot recommend this, as I have only tried it once myself and the consequences if it went wrong could mean a dead phone, but this post (http://forum.xda-developers.com/showpost.php?p=39216236&postcount=274) details how you can manually flash a hboot version in RUU mode since you are S-OFF. It comes from this thread: http://forum.xda-developers.com/showthread.php?t=1777223. Use it at your own risk, there have been two incidents of bricks but it depends how lucky you are feeling!
rosswhite said:
Running an RUU is the safest option, although its a bit hit and miss getting the RUU to run correctly. Flashalot recently made a guide (http://forum.xda-developers.com/showthread.php?t=2678700) if you run into any problems. I would try it without changing the radio, if it doesn't work then flash the matching one and go from there.
Now I cannot recommend this, as I have only tried it once myself and the consequences if it went wrong could mean a dead phone, but this post (http://forum.xda-developers.com/showpost.php?p=39216236&postcount=274) details how you can manually flash a hboot version in RUU mode since you are S-OFF. It comes from this thread: http://forum.xda-developers.com/showthread.php?t=1777223. Use it at your own risk, there have been two incidents of bricks but it depends how lucky you are feeling!
Click to expand...
Click to collapse
Yeah I heard about that method, but I thought it would be safer to just run the RUU even though it's more work. I think the bricks were from flashing the zips in recovery, not the new ones you flash in fastboot. Either way, I didn't feel like risking it.
Thanks! I'll try the RUU.
dr3amsINdigital said:
Yeah I heard about that method, but I thought it would be safer to just run the RUU even though it's more work. I think the bricks were from flashing the zips in recovery, not the new ones you flash in fastboot. Either way, I didn't feel like risking it.
Thanks! I'll try the RUU.
Click to expand...
Click to collapse
Wise choice, yeah you are right, the bricks were when they were flashing the zips in recovery. Its actually pretty safe in RUU mode but what's the point of risking it.
benJX said:
In fact, the CID matters if you have one from an operator (have a look here, but not the last one, it's the superCID), in this case, you have to choose a RUU according to your operator.
But being superCID, you can run any RUU, so run the last generic one (see my link) and everything will be ok to start from official clean install. Of course you'll stay S-OFF after running the RUU.
The only thing requested is to be on 2.15 hboot, that's why you have to downgrade to older firmware in order to run this.
Hope it will help.
Click to expand...
Click to collapse
dr3amsINdigital said:
I have kind of a similar question. After moonshine S-OFF, I'm on modified moonshine HBOOT 2.15.4444. Now I want to go back to the stock HBOOT 2.15.0000. Do I just need to run the RUU to go back? I'm bootloader unlocked, CID T-MOB010, TWRP recovery, and I flashed radio 1.20. Do I need to flash radio back to match the RUU before I run it?
Thanks
Click to expand...
Click to collapse
rosswhite said:
Running an RUU is the safest option, although its a bit hit and miss getting the RUU to run correctly. Flashalot recently made a guide (http://forum.xda-developers.com/showthread.php?t=2678700) if you run into any problems. I would try it without changing the radio, if it doesn't work then flash the matching one and go from there.
Now I cannot recommend this, as I have only tried it once myself and the consequences if it went wrong could mean a dead phone, but this post (http://forum.xda-developers.com/showpost.php?p=39216236&postcount=274) details how you can manually flash a hboot version in RUU mode since you are S-OFF. It comes from this thread: http://forum.xda-developers.com/showthread.php?t=1777223. Use it at your own risk, there have been two incidents of bricks but it depends how lucky you are feeling!
Click to expand...
Click to collapse
HELP my device does not see any memory and i cant flash any rom hellpp
the_ziom said:
HELP my device does not see any memory and i cant flash any rom hellpp
Click to expand...
Click to collapse
What hboot are you on now? Did you run an RUU to downgrade?
rosswhite said:
What hboot are you on now? Did you run an RUU to downgrade?
Click to expand...
Click to collapse
Hboot 2.15 after running the |RUU.exe|
dont have the memory (does not see device when trying to side load , recovery cant mount sdcard)
help i need my phone
the_ziom said:
Hboot 2.15 after running the |RUU.exe|
dont have the memory (does not see device when trying to side load , recovery cant mount sdcard)
help i need my phone
Click to expand...
Click to collapse
Which recovery did you flash? Try TWRP 2.7.0.0.
the_ziom said:
Hboot 2.15 after running the |RUU.exe|
dont have the memory (does not see device when trying to side load , recovery cant mount sdcard)
help i need my phone
Click to expand...
Click to collapse
Can you boot on stock android rom installed by the ruu ?
rosswhite said:
Which recovery did you flash? Try TWRP 2.7.0.0.
Click to expand...
Click to collapse
i already have twrp 2.7 and i flashed phillz and still nothing
benJX said:
Can you boot on stock android rom installed by the ruu ?
Click to expand...
Click to collapse
yes but i formated my memory to instal a pac man rom
the_ziom said:
yes but i formated my memory to instal a pac man rom
Click to expand...
Click to collapse
So actually you can confirm you are on HBOOT 2.15, Pihllz recovery and no rom installed ?
If yes reboot to bootloader, select clear storage, flash this recovery. Your sdcard should be mountable and let you install your rom.
####
benJX said:
So actually you can confirm you are on HBOOT 2.15, Pihllz recovery and no rom installed ?
If yes reboot to bootloader, select clear storage, flash this recovery. Your sdcard should be mountable and let you install your rom.
Click to expand...
Click to collapse
Another Problem
when ever i try to flash any rom it fails! and i dont know what to do HElp
So many developers and only 2 can help me
Please I'm begging for help
the_ziom said:
Another Problem
when ever i try to flash any rom it fails! and i dont know what to do HElp
Click to expand...
Click to collapse
Flash stock recovery : http://loadbalancing.modaco.com/download.php?file=ville_recovery_signed.img
Then Clear Storage from bootloader and flash TWRP recovery