Hi there!
i have a htc one s phone, originally with a "HTC__K18" cid which i've changed to "HTC__001".
i've read a lot about debranding it, switching its rom to a european one and get OTAs, and i understand that i can only switch to Super-CID in order to get the RUU to work. however - i won't be able to install the JB OTA.
my question is - can i install the RUU with Super-CID, then change it back to "HTC__001" and install the OTA?
thanks,
Yossi
Doea anyone know where I can find the answer?
Sent from my HTC One S using xda app-developers app
The unbranded RUU should work if your CID is HTC__001
Sent from my One S using Tapatalk 2
Which one should I choose from the ruu link on the sticky post?
I tried the European ones and it failed..
Sent from my HTC One S using xda app-developers app
yossif89 said:
Which one should I choose from the ruu link on the sticky post?
I tried the European ones and it failed..
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
What error message did it give?
Sent from my One S using Tapatalk 2
Now I've tried the JB European ruin, and got Error 132 signature/validation error..
Sent from my HTC One S using xda app-developers app
You might want to redownload the RUU. Is the latency on your connection good?
hmm..
i don't think this is the problem.. it said that i should find another rom which suits my device.
yossif89 said:
i don't think this is the problem.. it said that i should find another rom which suits my device.
Click to expand...
Click to collapse
Whats the mid of the device? Is it correct for the ruu? Tried it in fastboot USB mode?
You can even try it without a simcard inserted.
And is this on a relocked device or still unlocked?
And whats your current boot version?
Verstuurd van mijn HTC One S met Tapatalk
real187 said:
Whats the mid of the device? Is it correct for the ruu? Tried it in fastboot USB mode?
You can even try it without a simcard inserted.
And is this on a relocked device or still unlocked?
And whats your current boot version?
Verstuurd van mijn HTC One S met Tapatalk
Click to expand...
Click to collapse
my mid is PJ4010000.
I don't know if it's the right RUU for my device - i don't know which is the right one, since i've changed the cid and my old cid doesn't have any RUU available.
i've locked, rooted, changed cid and then relocked the device, so there's should be no problem with that.
should i do something with the mid? is it safe to change it?
yossif89 said:
my mid is PJ4010000.
I don't know if it's the right RUU for my device - i don't know which is the right one, since i've changed the cid and my old cid doesn't have any RUU available.
i've locked, rooted, changed cid and then relocked the device, so there's should be no problem with that.
should i do something with the mid? is it safe to change it?
Click to expand...
Click to collapse
oke your mid is fine for the ruu.
this cannot be changed yet (as far as i know)
and what is your current hboot version?
if your still on 2.xx you can also try ro run a older ruu and then do the ota (do not do it on supercid!!)
remember an ruu with a older hboot than your original cannot be flashed (downgrade) if your not s-off
as usaff22 said have you tried downloading another source of the ruu.
have you restored the stock recovery before relocking and running the ruu?
if you are not s-off you have to restore the stock recovery before running the ruu.
tried it without a inserted simcard?
tried the ruu with phone in fastboot usb mode? (heard of people geting error on 1st try but when starting the ruu again it went tru the whole process).
Thanks for your reply!
I'll try everything and let you know if it went fine.
Do you have another source for the OTA?
Sent from my HTC One S using xda app-developers app
Related
I've been going through some Rom/Flashing issues with my HTC One S and having the RUU for my device to start all over again flashing back to stock recovery, relocking the phone and using the RUU to get myself back to stock.
To give you a run down. I just got my phone and I've spent the last month figuring this whole thing out due to this amazing online community on here.
I use TWRP 2.2 as my recovery, unfortunately I dived in, and failed to back up my original non-rooted stock Rom but that's still ok.
[I know nooby but bearing in mind this has all taken place within like, two weeks.] I used to switch effortlessly between MIUI v4 and the stock rooted HTC Sense 4.0.4 android just by backing up and restoring the roms but then I flashed to Paranoid Android and I think I fiddled with something during that flashing process which is why I'm probably getting some arbitrary technical issues now and I'd like to start over!
So anyways, any of you fine gentlemen and possibly ladies out there who could point me in the direction of a Uk HTC One S T-mobile RUU?
Thanks
Unfortunately none. I need one, too.
Sent from my locked, tampered ville
What do you need yours for exactly? Maybe I can help you out
Sent from my HTC One S using xda app-developers app
I have a tampered bootloader, and the flag needs to be reset. That's why I need one. And I have a T-Mobile CID.
I know there are ways to tamper and/or change the CID but I don't particularly want to do that myself.
Sent from my HTC One S using xda app-developers app
I can't change CID, because I don't have an unlocked bootloader.
Sent from my locked, tampered ville
You can use hassoon's HTC one s all in one kit to unlock the bootloader can't you?
Sent from my HTC One S using xda app-developers app
Do a full wipe, flash something like ARHD, change the CID, flash HTC Europe RUUs.
Yes, but I don't want to root... I need to restore from an RUU because that will remove my tampered flag.
Sent from my locked, tampered ville
usaff22 said:
Yes, but I don't want to root... I need to restore from an RUU because that will remove my tampered flag.
Sent from my locked, tampered ville
Click to expand...
Click to collapse
I had a similar issue with my orange uk branded one s but after installing twrp i was able to change my cid from orange to a generic htc cid. I then re installed stock recovery, relocked the bootloader and then was able to install the european ruu. This worked fine and bootloader no longer says tampered although it does say relocked. I believe this is the best you can get if the bootloader has been unlocked at some stage.
norniron said:
I had a similar issue with my orange uk branded one s but after installing twrp i was able to change my cid from orange to a generic htc cid. I then re installed stock recovery, relocked the bootloader and then was able to install the european ruu. This worked fine and bootloader no longer says tampered although it does say relocked. I believe this is the best you can get if the bootloader has been unlocked at some stage.
Click to expand...
Click to collapse
How do you change the CID using twrp? What rom do you flash?
Sent from my HTC One S using xda app-developers app
fastboot oem writecid HTC__001
I have never unlocked though. Only tampered. So it's still locked but tampered.
Sent from my locked, tampered ville
Amilka said:
How do you change the CID using twrp? What rom do you flash?
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
I just started the phone in twrp recovery and followed this guide to change cid :
http://forum.xda-developers.com/showthread.php?p=26516911#post26516911
i then installed this ruu after relocking bootloader :
http://forum.xda-developers.com/showthread.php?t=1861981
I can't seem to be able to get the Viper One S ROM running on my phone, but I could when I came from stock.
My One S is 4.2.2 root box
TWRP 2.4.4
HBOOT 1.14
S-OFF SuperCID 11111111
And I know what RUU to use
But I was wondering if I had to do anything besides lock the bootloader.
Do I just run the RUU?
No writing secure flags, changing CID or having to S-On?
Because I don't want to mess up and brick my device.
Sent from my HTC One S using xda app-developers app
You didn't search good enough.
In every get back to stock topic the minimal requirement are asked and given several times.
Verstuurd van mijn HTC One S met Tapatalk
lmfaohd2 said:
I can't seem to be able to get the Viper One S ROM running on my phone, but I could when I came from stock.
My One S is 4.2.2 root box
TWRP 2.4.4
HBOOT 1.14
S-OFF SuperCID 11111111
And I know what RUU to use
But I was wondering if I had to do anything besides lock the bootloader.
Do I just run the RUU?
No writing secure flags, changing CID or having to S-On?
Because I don't want to mess up and brick my device.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Try the OTA and the Ruu need to lock your bootloader vie cmd fastboot oem lock and unlock vie the same unlock_code
That's all I know
I've been running AOSP ROM's on my evita for a while now, but apparently with the 3.4 kernel you now need hboot 2.14 or higher and mine's at 1.09. My phone was unlocked with S-ON, but I did "fastboot oem lock" this morning because I read that it's necessary for an RUU. I downloaded the 2.20 RUU and tried to run the installer but I always get an Error [170] USB Connection Error. I have the HTC and adb drivers installed successfully and have tried to run the RUU as admin in both Sense and fastboot (bootloader). I'm a bit stumped and would really like to get AOSP back on my phone.
You need to S-off first.
Sent from my HTC One X using xda premium
tlazarus said:
You need to S-off first.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Should I use facepalm for that then?
EDIT
I got s-off, but still no go. Still the error 170.
I know on my old Incredible I was able to rename the rom.zip from the RUU as PB99IMG.zip and put it on the root of my sdcard. Then in hboot it would detect it and ask to flash it. This isn't happening on my evita though. Is there a way to do that, or is that only for older htc devices?
Put phone into fastboot and try again. Check error log to see if it fails to identify your phone.
Open command prompt and type adb devices, if it does not see it then try installing new drivers. If it does see it then enter " adb shell reboot oem-78" that will reboot your phone in to RUU ready fastboot. Open ruu and try running it again.
Sent from my HTC One X using xda premium
Venomtester said:
Put phone into fastboot and try again. Check error log to see if it fails to identify your phone.
Open command prompt and type adb devices, if it does not see it then try installing new drivers. If it does see it then enter " adb shell reboot oem-78" that will reboot your phone in to RUU ready fastboot. Open ruu and try running it again.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Where can I find this error log? It did see my device, I did that command (which ended at the black htc screen) and I ran the RUU again but I still get the error 170. I'm also using this RUU http://bugsylawson.com/index.php/fi...320911-2-101053225l-release-271865-signedexe/
Sounds like a bad download. Is it 568.22 mbs? Try roomyshare.com/ruu-evita-ul-cingular.html
You can find it in the list.
Sent from my HTC One X using xda premium
Venomtester said:
Sounds like a bad download. Is it 568.22 mbs? Try roomyshare.com/ruu-evita-ul-cingular.html
You can find it in the list.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
It is that size, though I may try the link you gave.
EDIT
Okay, I think I found out what I've been doing wrong. I found this link http://forum.xda-developers.com/showthread.php?t=2119610 and it turns out that the file I've been trying does NOT include the 2.14 hboot that I need. The one I need is the latest JB release, but someone said that if you flash it with superCID and S-ON that it will brick your device. I have superCID but S-OFF, does anyone think that will brick my device? Should I flash the RUU with the 1.09 hboot (which I'm running) first, and then flash the newest RUU? Also, it looks like the link I provided offers flashable OTA's of each update. Would those work/be recommended for TWRP?
Change cid to cingular "cws_001" I think. Super cid can cause brick.
Sent from my HTC One X using xda premium
Venomtester said:
Change cid to cingular "cws_001" I think. Super cid can cause brick.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Well I didn't do that...haha. I read on another forum that TWRP doesn't support that cid check function or something and to just remove it from the updater-script so I tried that and flashed the latest OTA zip in TWRP and it failed after a few steps. I tried booting and it didn't get to the boot animation so I rebooted to recovery and restored my backup. I'm going to try a stock zip without the modified updater-script and restore my CID to normal and try again.
EDIT
Well, I restored the CID to CWS__001 and I still get that check_cid error
dshoe said:
Well I didn't do that...haha. I read on another forum that TWRP doesn't support that cid check function or something and to just remove it from the updater-script so I tried that and flashed the latest OTA zip in TWRP and it failed after a few steps. I tried booting and it didn't get to the boot animation so I rebooted to recovery and restored my backup. I'm going to try a stock zip without the modified updater-script and restore my CID to normal and try again.
EDIT
Well, I restored the CID to CWS__001 and I still get that check_cid error
Click to expand...
Click to collapse
To run a ota you need to flash stock recovery image.. and bootloader needs to be unlocked for that
Sent from my HTC One XL using xda premium
31ken31 said:
To run a ota you need to flash stock recovery image.. and bootloader needs to be unlocked for that
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Hm, okay then, let me ask another question. I'm on hboot 1.09 and I need 2.14 to run AOSP ROM's now. What's the best way to get there if I already have ROM's installed. Is it what I'm doing right now or should it be something else?
EDIT
The latest JB RUU is picking up my device now and offering the update, 2 seconds away from doing it....
dshoe said:
Hm, okay then, let me ask another question. I'm on hboot 1.09 and I need 2.14 to run AOSP ROM's now. What's the best way to get there if I already have ROM's installed. Is it what I'm doing right now or should it be something else?
EDIT
The latest JB RUU is picking up my device now and offering the update, 2 seconds away from doing it....
Click to expand...
Click to collapse
Just make sure you are s-off before running ruu or risk a brick..
Sent from my HTC One XL using xda premium
Hi. I am looking my update my hboot from 1.09 to 2.14. I am S-OFF now, also running the Sense 5 rom now(TWRP recovery).
I have downloaded the Latest JB 3.18 RUU from instructions here http://forum.xda-developers.com/showthread.php?t=2064621.
What else do I need to do before flashing the RUU to the device?
For what it's worth, I was on stock 2.20, got s-off and unlocked bootloader with superCID, and ran the 3.18 RUU with no problems. I didn't need to relock or anything.
knanda said:
Hi. I am looking my update my hboot from 1.09 to 2.14. I am S-OFF now, also running the Sense 5 rom now(TWRP recovery).
I have downloaded the Latest JB 3.18 RUU from instructions here http://forum.xda-developers.com/showthread.php?t=2064621.
What else do I need to do before flashing the RUU to the device?
Click to expand...
Click to collapse
You can go ahead and run the RUU. No real risk because you're s-off. Maybe make a backup though.
Sent from my Evita
I am looking for a Stock T-Mobile Jelly Bean image that won't brick my phone. I tried searching for one, but I couldn't find anything or I found RUUs for outdated versions of HBoot. I am trying to revert back to stock, but I am sorta scared to do so with an outdated RUU. I have HBoot version 2.15 and Radio version 1.13.50.05.31. Thanks in advance.
Would this be the RUU I have to download? http://bugsylawson.com/files/file/1...531-10305008l-release-309489-signed-ics-2exe/
I would just prefer a nandroid backup of the stock image that I can just flash with CWM.
I downloaded the RUU, I just need to know if that is the correct one for my phone before I use it. I really don't want a bricked phone. I checked the MD5sum already and it matches, that is the only thing holding me back.
Sent from my One S using xda premium
I have ran that RUU with the same hboot and radio as you. Why do you think it would brick your phone? you haven't supercid and have locked your bootloader right?
(didn't download from that site though)
http://forum.xda-developers.com/showthread.php?t=2094414
Okay, thank you for the reassurance. I just am pretty paranoid about bricking my phone. I have been looking up how to use RUUs for the last day or so, I just couldn't find anything on how to select the right one. Thanks again.
I just checked out your link and I am downloading now. I do not have SuperCID and I will be looking my boot loader.
Sent from my One S using xda premium
OccupyDemonoid said:
Okay, thank you for the reassurance. I just am pretty paranoid about bricking my phone. I have been looking up how to use RUUs for the last day or so, I just couldn't find anything on how to select the right one. Thanks again.
I just checked out your link and I am downloading now. I do not have SuperCID and I will be looking my boot loader.
Sent from my One S using xda premium
Click to expand...
Click to collapse
If you are on TMOB US then it's for you. Furthermore, you can match thr CID of your phone to that in the RUU.exe --> Firmware.zip --> android-info.txt.
You'll have to extract firmware.zip from temporary files when you run RUU without connecting phone.
Sent from my Nexus 7 using Tapatalk HD
I ended up using that RUU that was linked earlier in this thread and everything went fine. I just don't have the stock recovery. I guess that isn't that much of a problem though.
Sent from my HTC VLE_U using xda premium
OccupyDemonoid said:
I ended up using that RUU that was linked earlier in this thread and everything went fine. I just don't have the stock recovery. I guess that isn't that much of a problem though.
Sent from my HTC VLE_U using xda premium
Click to expand...
Click to collapse
The RUU installs the Stock Recovery automatically. You don't have to do anything extra.
You can find stock recovery (if you want to keep it for any purpose) inside the RUU (extraction would require you to run the RUU and then extract the recovery from Temporary Files)
OR
you can find it in the forums.
Hmmm, that's strange. Oh well I guess. When I tried to go into the recovery it just showed a red exclamation mark with a phone under it. I don't really need a recovery right now. Thanks for letting me know where I can find it.
Sent from my HTC VLE_U using xda premium
OccupyDemonoid said:
Hmmm, that's strange. Oh well I guess. When I tried to go into the recovery it just showed a red exclamation mark with a phone under it. I don't really need a recovery right now. Thanks for letting me know where I can find it.
Sent from my HTC VLE_U using xda premium
Click to expand...
Click to collapse
I believe that is the stock recovery. The red exclamation mark is telling you that you don't have access to it. Perfectly normal.
tivofool said:
I have ran that RUU with the same hboot and radio as you. Why do you think it would brick your phone? you haven't supercid and have locked your bootloader right?
(didn't download from that site though)
http://forum.xda-developers.com/showthread.php?t=2094414
Click to expand...
Click to collapse
Can I also run this same RUU as quoted in this thread ?
I have the same radio but different hboot ...
SuperCID = HTC__001 <---- I got this right now, I will have to put in TMO CID before I run RUU, is that true?
VLE PVT SHIP S-ON RL
HBOOT-1.13.0000
RADIO-1-13.50.05.31
I would like to go back to Stock becuase after rooting and putting custom ROM (AOKP, I lost 4g, it was working before)
DroidLuvver said:
Can I also run this same RUU as quoted in this thread ?
I have the same radio but different hboot ...
SuperCID = HTC__001 <---- I got this right now, I will have to put in TMO CID before I run RUU, is that true?
VLE PVT SHIP S-ON RL
HBOOT-1.13.0000
RADIO-1-13.50.05.31
I would like to go back to Stock becuase after rooting and putting custom ROM (AOKP, I lost 4g, it was working before)
Click to expand...
Click to collapse
Yes, I think it will give you an error with that cid. Someone could correct me, but with s-off you can run whatever ruu you want.
tivofool said:
Yes, I think it will give you an error with that cid. Someone could correct me, but with s-off you can run whatever ruu you want.
Click to expand...
Click to collapse
I am planning on changing the CID to match what's in the firmware and then running this RUU but... what about my hboot.. it's different than what you guys have. Its 1.13
DroidLuvver said:
I am planning on changing the CID to match what's in the firmware and then running this RUU but... what about my hboot.. it's different than what you guys have. Its 1.13
Click to expand...
Click to collapse
It will install the newer hboot to 2.15
tivofool said:
It will install the newer hboot to 2.15
Click to expand...
Click to collapse
So I should be able to run the RUU with lower boot like mine and it will upgrade the boot to 2.15 -
Is it true that with 2.15 hboot, modifying the CID is not allowed ?
Any reason why I should stay with 1.13 HBOOT and not go to 2.15 Hboot? Meaning any disadvantages of upgrading to HBOOT 2.15 ?
Well, say you updated your phone via ota & your cid is European or something. And all of the ruus for that CID are lower hboots. If u are s-on and and needed to ruu you wouldn't be able to.
But there is a guide to run a ota.zip for those people, so it isn't hopeless.
So not too many disadvantages.
In fact I just installed the newest Rom and firmware today. So my hboot is 2.16.
And the gossip is that update will be officially put out by HTC in a few weeks.
Sent from my HTC One S using Tapatalk 2
Remember this.
if you want to go stock again in future (warranty purpose)
some providers have only provided an ota (only ruu with lower hboots) when upgrading to jb. So downgrading gets hard
It's not that easy to flash an ota as is a ruu.
If your s-off downgrading is no issue.
Verstuurd van mijn HTC One S met Tapatalk
Hello Guys,
I am trying to update my RUU, but always get the same error while running (Image Error:159). My Phone is T-Mobile Germany, but i have changed the CID to HTC__001 in order to install the HTC Europe RUU. Also tried the T-Mobile Germany RUU with the T-MOB101 cid, but i still get the same Error. My Hboot is 1.09 and my Rom is CM10, but it won't boot for now.
Really need my phone, so it would be awesome, if someone help me.
Mark.oh said:
Hello Guys,
I am trying to update my RUU, but always get the same error while running (Image Error:159). My Phone is T-Mobile Germany, but i have changed the CID to HTC__001 in order to install the HTC Europe RUU. Also tried the T-Mobile Germany RUU with the T-MOB101 cid, but i still get the same Error. My Hboot is 1.09 and my Rom is CM10, but it won't boot for now.
Really need my phone, so it would be awesome, if someone help me.
Click to expand...
Click to collapse
You mean T-MOB010, right?
Why not switch to 11111111 super CID?
Sent from my Nexus 4 using Tapatalk
nicknc said:
You mean T-MOB010, right?
Why not switch to 11111111 super CID?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
No T-Mob101 is the CID for T-Mobile Germany and T-Mob010 for T-Mobile US. I'm not leaving it to 11111111, because i have to change it matching the RUU i want to update.
Mark.oh said:
No T-Mob101 is the CID for T-Mobile Germany and T-Mob010 for T-Mobile US. I'm not leaving it to 11111111, because i have to change it matching the RUU i want to update.
Click to expand...
Click to collapse
If you go to 11111111, then you can install any RUU.
The error you are getting indicates the RUU you want to install does not match your CID.
So 11111111 will let you install the RUU you want. Then switch your CID back to whatever.
Sent from my Nexus 4 using Tapatalk
nicknc said:
If you go to 11111111, then you can install any RUU.
The error you are getting indicates the RUU you want to install does not match your CID.
So 11111111 will let you install the RUU you want. Then switch your CID back to whatever.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Thanks for your answer. Tried to do it with CID 11111111 but i still get the same error. My phone won't even boot anymore tried to un- and reinstall my rom again, but i'm in a bootloop for now. Really don't know what to do for now tried nearly everything but i cant get the RUU to work.
Mark.oh said:
Thanks for your answer. Tried to do it with CID 11111111 but i still get the same error. My phone won't even boot anymore tried to un- and reinstall my rom again, but i'm in a bootloop for now. Really don't know what to do for now tried nearly everything but i cant get the RUU to work.
Click to expand...
Click to collapse
RUU_Ville_U_JB_45_S_TMOUS_3.14.531.11_Radio_1.13.5 0.05.31_10.30.50.08L_release_309489_signed_ICS_2
Try this RUU.
Sent from my Nexus 4 using Tapatalk
nicknc said:
RUU_Ville_U_JB_45_S_TMOUS_3.14.531.11_Radio_1.13.5 0.05.31_10.30.50.08L_release_309489_signed_ICS_2
Try this RUU.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
I'm downloading it right now, but i don't think it'll work as this is for T-Mobile USA and they have a different Baseband Version then Europe
Mark.oh said:
I'm downloading it right now, but i don't think it'll work as this is for T-Mobile USA and they have a different Baseband Version then Europe
Click to expand...
Click to collapse
Yeah, you can flash whatever radio, ROM, etc after the fact.
This is just to get your phone booting again.
Don't forget to lock your boot loader before running the RUU.
Sent from my Nexus 4 using Tapatalk
nicknc said:
Yeah, you can flash whatever radio, ROM, etc after the fact.
This is just to get your phone booting again.
Don't forget to lock your boot loader before running the RUU.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Mhhh didn't work neither, really dont know what else i could try. Tried to flash back to my old cm 10, but i still get a bootloop and while flashing it said unable to mount cache don't know if it means something.
Mark.oh said:
Mhhh didn't work neither, really dont know what i else i could try. Tried to flash back to my old cm 10, but i still get a bootloop and while flashing it said unable to mount cache don't know if it means something.
Click to expand...
Click to collapse
I have read in another forum that i have to update my hboot first, but couldn't find any instrcution on how to update hboot.
I've only read that i could update it via the RUU, but that not possible for me.
Mark.oh said:
I have read in another forum that i have to update my hboot first, but couldn't find any instrcution on how to update hboot.
I've only read that i could update it via the RUU, but that not possible for me.
Click to expand...
Click to collapse
There is a firmware.zip file you can flash from recovery to update/downgrade to hboot 2.15
Sent from my Nexus 4 using Tapatalk
---------- Post added at 04:45 PM ---------- Previous post was at 04:44 PM ----------
You getting the same error with that tmobile RUU?
Sent from my Nexus 4 using Tapatalk
Same Problem Here
Am Having the same problem
Htc one s
««Relocked»»
Hboot 1.14.0002
CID 11111111
S-off
I cant install any ruu file and whn i try to install
the previous ruu it get stuck after erasing user data
Sending.............. For more than 10mins
am runing out of pataince already
pls help
internal sdcard cant mount in recovery