Related
Hi all,
I m still a noob to android and I was trying to flash viperx jellybean rom on my htc one x international tegra 3 version. But after the flashing I noticed that my IMEI and baseband have been erased. The stupid thing I did was not to take a backup before proceeding. So now my phone cant connect to the network.
Can you please let me know if there is a way to fix this phone?
Reflash the rom and in aroma choise: "venom kernel".
After or before, you have to flash the boot.img that you can found in zip rom...
Guich said:
Reflash the rom and in aroma choise: "venom kernel".
After or before, you have to flash the boot.img that you can found in zip rom...
Click to expand...
Click to collapse
Just to confirm reflash the viperx jellybean rom, after after reflashing in aroma choose venom kernal
after that flash the boot.img ?
thanks much for help.
Now, you have wifi signal and network signal?
If no, this is the problem.
So:
1) Extract boot.img from zip folder and put it (boot.img) into your fastboot folder
2) Make an erase cache: "fastboot erase cache"
3) Flash the boot.img: "fastboot flash boot boot.img"
4) Make another erase cache: "fastboot erase cache"
5) Reboot into recovery
6) Flash the rom with a full wipe and at kernel voice, choise Venom kernel
You can resolve with this procedure
Thanks. I have wifi signal but no cell phone signal since my IMEI is erased. Its unable to connect to network.
I will give it a try right now.
thanks.
Unfortunately this didnt work for me. It still doesnt show the IMEI and baseband info on my phone. Both are unknown.
My kernal version is 3.1.10 if that matters.
Please help.
Which version of rom you've flashed?
And what's you hboot?
i think that one way to retrieve it back is with a ruu, going back to full stock ! can you give the out come of :
fastboot getvar version-main
Mr Hofs said:
i think that one way to retrieve it back is with a ruu, going back to full stock ! can you give the out come of :
fastboot getvar version-main
Click to expand...
Click to collapse
I had the same issue...
And I resolved with a reflash of rom, its' strange that for him didn't work...
Mr Hofs said:
i think that one way to retrieve it back is with a ruu, going back to full stock ! can you give the out come of :
fastboot getvar version-main
Click to expand...
Click to collapse
version-main: 3.14.401.31
Also could you please point me on how to go back to stock ? Can I go to ICS or should I go to JB stock?
well if this does not work....i have no other option....this will bring the phone back to factory state
download this file
http://androidfiles.org/ruu/securek...Radio_5.1204.162.29_release_302015_signed.exe
steps :
1: charge the battery full
2: backup all content you need to keep
3: boot the phone in the bootloader and relock the bootloader
fastboot oem lock (the bootloader reboots with a warning in the bootloader, thats fine. keep the phone there)
4: execute the RUU on the pc with admin rights (right mousebutton -> select : run as administrator)
5: sit back and follow the steps on screen. it takes about 7-10 minutes and your phone is back to factory settings
6: hopefully it works
Guich said:
Which version of rom you've flashed?
And what's you hboot?
Click to expand...
Click to collapse
I flashed venom 3.3.7
hboot is 1.39
my cid is htc__001 is that matters
R: [Q] HTC one x corrupted my IMEI and baseband
spacemango80 said:
I flashed venom 3.3.7
hboot is 1.39
my cid is htc__001 is that matters
Click to expand...
Click to collapse
We have only the cid different, but for me worked my steps
Try with the steps by Mr Hofs
Sent from HOX
thats all good....but the IMEI thing is not ......i say try the above and report back !
Just a question on this process:
Dont I have to flash the boot.img and recovery.img too?
Nope.....all is done by the ruu
Mr Hofs said:
Nope.....all is done by the ruu
Click to expand...
Click to collapse
I belive there is something wrong with my windows box (may be a driver issue)
After I run the RUU it goes as far as "waiting for rebooting the bootloader.."
then it gives up saying the phone is not connected.
Is there any way to run this from MAC?
Mr Hofs said:
Nope.....all is done by the ruu
Click to expand...
Click to collapse
Everything went through fine with RUU and now am back to stock.
However the problem persists. IMEI is still not there and baseband is still unknown. This is really killing me.
Any help is highly appreciated
thanks
Then i can't give you the answer....
R: [Q] HTC one x corrupted my IMEI and baseband
spacemango80 said:
Everything went through fine with RUU and now am back to stock.
However the problem persists. IMEI is still not there and baseband is still unknown. This is really killing me.
Any help is highly appreciated
thanks
Click to expand...
Click to collapse
Before the first flash of viper, did you have unlocked your phone or this was unlocked?
And, this problem appears after the flash of Viper Rom??
Sent from HOX
I've tried to update my phone HBOOT from 1.28 to 1.39 and I've used JBFWflasher to do it so I can try using Viper ROM. To cut a long story short I've tried several methods and resorted to flashing it with back to stock but now if looks like it has Viper on it. The phone has gone to being very slow and glichy and I'm stuck with what should I do? .
Can I flash it back to stock again?
What are the steps you have been taken ?
You need to flash the boot.img from the viper rom.zip with fastboot, then make a FULL wipe in the recovery .... not the sdcard ofcourse.
Then install the viper x rom zip.....
Your hboot is updated successfully ?
Give some (or all) info of the steps you did. Including what recovery you are using. Its easier to give proper help
isptim elizabeth
Mr Hofs said:
What are the steps you have been taken ?
You need to flash the boot.img from the viper rom.zip with fastboot, then make a FULL wipe in the recovery .... not the sdcard ofcourse.
Then install the viper x rom zip.....
Your hboot is updated successfully ?
Give some (or all) info of the steps you did. Including what recovery you are using. Its easier to give proper help
Click to expand...
Click to collapse
I've tried Android Revolution HD 20.1 the last few hours still not any better. I've flashed the boot img using jbfwtool21 and then flashed the rom and did a full wipe. Does it have anything to do with the hboot? How do I check?
Check your hboot number in the bootloader. Its number is in there. And what recovery are you on ???
Mr Hofs said:
Check your hboot number in the bootloader. Its number is in there. And what recovery are you on ???
Click to expand...
Click to collapse
hboot is 1.39.0000 recovery is twrp
All should be oke then. Did you try another rom....or maybe its a bad download.
Phone still appears to be acting up even after flashing with another rom. Is there anyway to flash back to stock?
Can you do
Fastboot getvar version-main
Sorry how do i do this? I'm a bit of a noob:laugh:
Ah think I got it, its 3.14.401.31
Oke download this file
http://bugsylawson.com/files/file/1...-r-radio-5120416229-release-302015-signedexe/
Then relock the bootloader
Fastboot oem lock
Then run the ruu with administrator rights....it will flash the phone back to full stock
Or try flashing the rom without the jbfwflasher and just use cmd
A
Viper 3.5.4 xm296
Thank you Mr Hofs followed your instructions and I'm so releived that its now fixed and that I don't have an expensive paperweight
Thank you soooo much!!!
:laugh::good:
Very good mate !
CASE CLOSED !
Hi guys, finally got a HOX. I've rooted, flashed a new recovery and bootloader unlocked it. When ever I flash a JB ROM (4.1.x or 4.2.x) I have issues with major lags to the point where everything seems to operate at 3fps and it's unusable. Anyone know why this is so?
Weird, can you give some more detailed info ?
What rom
What kernel
What recovery (type & version number)
Steps you perform before flashing and installing ?
Mr Hofs said:
Weird, can you give some more detailed info ?
What rom
What kernel
What recovery (type & version number)
Steps you perform before flashing and installing ?
Click to expand...
Click to collapse
When I bought the phone it had stock 4.1.1 firmware and had the major lag issues and then I flashed Android Revolution ROM v9.9 I think on 4.0.4 and it smoothed out.
I tried CM10.1 and flashed the boot.img in fastboot and then rebooting into recovery (Lastest CWM) to do wipes and then flashing CM10.1. The phone proceeds to boot but lags immensely from that point on.
Okey, but what recovery are you using ? So i can give steps to install properly, not saying you didn't but to be safe.
Then we can try CM10.1 again or another sense rom just to test.
After that we can try different governer settings or different kernels.
Mr Hofs said:
Okey, but what recovery are you using ? So i can give steps to install properly, not saying you didn't but to be safe.
Then we can try CM10.1 again or another sense rom just to test.
After that we can try different governer settings or different kernels.
Click to expand...
Click to collapse
I'm using ClockWorkMod Recovery v5.8.4.0 I think. My usual method is
1. Boot into bootloader
2. fastboot flash boot boot.img (flash boot image for CM10.1)
3. Boot into recovery
4. Wipe all partitions
5. Install CM10.1 and Gapps.
6. Reboot into OS.
After flashing boot.img use fastboot erase cache . Dont know if this help but this step is missing
Maybe after flashing rom first reboot ,after that ,reboot and then flash gapps.
Sent from my HTC One X using xda app-developers app
Fastboot erase cache is very good, always good to do that but always flash gapps before reboot
Steps looks fine, i give a detailed one so you can compare
Flash boot.img
Fasboot erase cache
In recovery :
Factory reset
Wipe cache partition
Advanced - wipe dalvik cache
Mounts & storage - format cache,system,data
Then install of the the rom.
Is this on all roms (did you try a sense based one) ?
Can you post the outcome of :
Fastboot getvar version-main
It even lagged the same way with the stock ROM and the phone still being 'virgin'? Aka no root, flashing, unlock etc.
In that case I would suspect a hardware failure, such as the memory.
Mr Hofs said:
Fastboot erase cache is very good, always good to do that but always flash gapps before reboot
Is this on all roms (did you try a sense based one) ?
Can you post the outcome of :
Fastboot getvar version-main
Click to expand...
Click to collapse
3.14.401.31 is the outcome of fastboot getvar version-main.
It is weird because on stock HTC 4.1.1 ROM it's laggy as hell and any other 4.1.x or 4.2.x ROM is just laggy as hell. I flash back to Android Revolution v9.9 on 4.0.4 and it's smooth as normal.
Alright lets try this :
Relock the bootloader :
Fastboot oem lock
Then run this ruu with admin rights by right clicking the ruu and select that option
http://bugsylawson.com/files/file/1...-r-radio-5120416229-release-302015-signedexe/
Then you get it back to stock including of flashing the firmware
Mr Hofs said:
Alright lets try this :
Relock the bootloader :
Fastboot oem lock
Then run this ruu with admin rights by right clicking the ruu and select that option
http://bugsylawson.com/files/file/1...-r-radio-5120416229-release-302015-signedexe/
Then you get it back to stock including of flashing the firmware
Click to expand...
Click to collapse
Just done this and booted into Stock 4.1.1. It's a LOT smoother than it was before, still not quite buttery smooth but hey it's usable. Would it now be a good idea to get rooted and Custom Recovery?
I suggest you let this stock rom settle for a couple of hours or a day.....check if its getting better.
But yes if you wish you can custom rom it again
Mr Hofs said:
I suggest you let this stock rom settle for a couple of hours or a day.....check if its getting better.
But yes if you wish you can custom rom it again
Click to expand...
Click to collapse
I flashed back to CM10.1 and it still is incredibly laggy. I have no clue why it's doing this.
Can you download trickster from the playstore and set the governer to performance, see if that makes a difference ?!
Mr Hofs said:
Can you download trickster from the playstore and set the governer to performance, see if that makes a difference ?!
Click to expand...
Click to collapse
Just tried it. No changes to report. Still slow as hell. Clock speeds look normal as well.
Then im afraid i cant help you any further
Hoooold on a second.
Please provide me the following information: CID and HBOOT version.
To get your CID, download CID Getter from the Play Store. Your CID will be displayed in the top area of the app.
To obtain your HBOOT version, simply reboot to the bootloader and check the version there.
Zulake said:
Hoooold on a second.
Please provide me the following information: CID and HBOOT version.
To get your CID, download CID Getter from the Play Store. Your CID will be displayed in the top area of the app.
To obtain your HBOOT version, simply reboot to the bootloader and check the version there.
Click to expand...
Click to collapse
Well his main number is 3.14.401.31 that's a wwe cid with hboot 1.39
Already gave this on page 1, plus he ran the ruu with succes already .....
Mr Hofs said:
Well his main number is 3.14.401.31 that's a wwe cid with hboot 1.39
Already gave this on page 1, plus he ran the ruu with succes already .....
Click to expand...
Click to collapse
True, it's just that it was unclear to me whether he got on that ROM by OTA or by custom ROM. In the second case the HBOOT could be a too low version.
True, but the fastboot getvar version-main always tells the true main version (and can be automatically be linked to the hboot) of the phone and not the running software
my Htc one M8 has Stock 4.4.4 kitkat and
i have HBoot Version- 3.190.0000
and radio- 1.09.20.0119
and TWRP Recovery version- V2.7.0.2 (Older bcoz New recovery not working)
Q.1 - i want to install SkyDragon 6.0 Marshmallow Sense 7 based Rom.. Do i Need or I have to install Stock 5.0.1 before flash 6.0 marshmallow ?
Q.2- Do i need to update HBoot version ?
Q.3- Do i need to update TWRP Recovery ?
Lets start by posting your output from the fastboot command :
Fastboot getvar all
Delete the serial and imei before posting. Then i can answer your questions
Mr Hofs said:
Lets start by posting your output from the fastboot command :
Fastboot getvar all
Delete the serial and imei before posting. Then i can answer your questions
Click to expand...
Click to collapse
i'm Sorry bro.. i didn't understand... did i do some mistake?
info2shail2010 said:
i'm Sorry bro.. i didn't understand... did i do some mistake?
Click to expand...
Click to collapse
No just read my post again. If we have all the information from the device we can't make mistakes in answering your questions. So if you would be so kind to post the result we can continue
Mr Hofs said:
No just read my post again. If we have all the information from the device we can't make mistakes in answering your questions. So if you would be so kind to post the result we can continue
Click to expand...
Click to collapse
Like this ? (i'm Sorry i m too Slow)
and i did a Big mistake... i think i Bricked the Device......
Mistakenly i touched on "Format Data" instead of "Factory Reset" on TWRP 2.7.0.2... and then i tried to Flash MaximusHD 5.0.1 ROM... now everytime i touch on reboot, phone comes on on boot loader.... Did i do something wrong with partition ? what should i do ?
As i suspected. In your first post you wrote your hboot was 3.19.....but it's 3.16 and therefore way too low for the latest roms.
You need to update the firmware first, then TWRP to the latest one and then flash one of the latest MM roms.
What was your cid before you changed it to supercid ?
And no you didn't brick it. This is just a software issue. A brick is when the phone won't go the bootloader or recovery anymore.
Mr Hofs said:
As i suspected. In your first post you wrote your hboot was 3.19.....but it's 3.16 and therefore way too low for the latest roms.
You need to update the firmware first, then TWRP to the latest one and then flash one of the latest MM roms.
What was your cid before you changed it to supercid ?
And no you didn't brick it. This is just a software issue. A brick is when the phone won't go the bootloader or recovery anymore.
Click to expand...
Click to collapse
thank you sir... you just saved my life... Sorry it was my mistake... you are right... hboot is 3.16.... i dont have Old CID... is it a gonna next prob ?:crying:
info2shail2010 said:
thank you sir... you just saved my life... Sorry it was my mistake... you are right... hboot is 3.16.... i dont have Old CID... is it a gonna next prob ?:crying:
Click to expand...
Click to collapse
Old cid should be a sprint one and software number is somewhat like 1.54.654.x
I would suggest to get back to a stock rom + recovery and then update the phones software + firmware via official ota.
Let's see if there is a backup available.
Edit :
I don't know much about sprint devices so check in the specific sprint section for a suited backup. The 1.54.654.x
Here you can find very detailed instructions on how to restore a backup successfully !
http://forum.xda-developers.com/showthread.php?t=3086860
Mr Hofs said:
Old cid should be a sprint one and software number is somewhat like 1.54.654.x
I would suggest to get back to a stock rom + recovery and then update the phones software + firmware via official ota.
Let's see if there is a backup available
Click to expand...
Click to collapse
ok but i dont have old CID ... will going back on stock rom and stock recovery will lock again my CID ?
how will i get stock rom and recovery... i mean should i search on HTC site or XDA ?
info2shail2010 said:
ok but i dont have old CID ... will going back on stock rom and stock recovery will lock again my CID ?
Click to expand...
Click to collapse
Edited my post above. Your supercid should not interfere with ota updates at all. More important is to get a pure stock backup. Or a RUU ..... hold on, a ruu would be an option too but it wipes the ENTIRE phone !
Edit : are you using it on sprint network ?
http://androidruu.com/getdownload.p..._NV_SPCS_1.52_003_release_418492_signed_2.exe
Here is a ruu that would suit your device. Put the phone in the bootloader/fastboot usb menu and execute the RUU.exe with admin rights from the pc (windows, usb 2.0 port connection) it will flash the phone to full stock.
When the ruu is successful you can flash the latest TWRP and flash the skydragon rom
Mr Hofs said:
Old cid should be a sprint one and software number is somewhat like 1.54.654.x
I would suggest to get back to a stock rom + recovery and then update the phones software + firmware via official ota.
Let's see if there is a backup available.
Edit :
I don't know much about sprint devices so check in the specific sprint section for a suited backup. The 1.54.654.x
Here you can find very detailed instructions on how to restore a backup successfully !
http://forum.xda-developers.com/showthread.php?t=3086860
Click to expand...
Click to collapse
tried lots of stock/custom rom... but none of them working.. bcoz i dont no the CID... "Get var all" is only showing 11111111... how do i know which model my phone is ?
Mr Hofs said:
Edited my post above. Your supercid should not interfere with ota updates at all. More important is to get a pure stock backup. Or a RUU ..... hold on, a ruu would be an option too but it wipes the ENTIRE phone !
Edit : are you using it on sprint network ?
http://androidruu.com/getdownload.p..._NV_SPCS_1.52_003_release_418492_signed_2.exe
Here is a ruu that would suit your device. Put the phone in the bootloader/fastboot usb menu and execute the RUU.exe with admin rights from the pc (windows, usb 2.0 port connection) it will flash the phone to full stock.
When the ruu is successful you can flash the latest TWRP and flash the skydragon rom
Click to expand...
Click to collapse
No.. i am from India.. and not using Sprint network...
info2shail2010 said:
No.. i am from India.. and not using Sprint network...
Click to expand...
Click to collapse
You can't flash the latest roms NOT because of your CID but because the firmware is outdated ! And as far as i can tell about your MID is that it's a sprint device.
You can only flash old kitkat roms at this time.
Maybe @redpoint73 can chip in .......
info2shail2010 said:
my Htc one M8 has Stock 4.4.4 kitkat and
i have HBoot Version- 3.190.0000
and radio- 1.09.20.0119
and TWRP Recovery version- V2.7.0.2 (Older bcoz New recovery not working)
Q.1 - i want to install SkyDragon 6.0 Marshmallow Sense 7 based Rom.. Do i Need or I have to install Stock 5.0.1 before flash 6.0 marshmallow ?
A. You only need to flash the firmware from Stock 5.0.1.
Go to the link below and flash this:
4.25.651.18 Full Firmware from RUU (fastboot flashable)
http://forum.xda-developers.com/showthread.php?t=2729173
This will also update your hboot to 3.19 so no need to answer Q.2.
Now, flash the latest TWRP, then go flash your favorite "SkyDragon 6.0 Marshmallow Sense 7 based Rom" by following the Dev's instructions on its OP.
All done.
Q.2- Do i need to update HBoot version ?
A. Answered Above.
Q.3- Do i need to update TWRP Recovery ?
A. Yes, flash the latest TWRP because the stock firmware you flashed has already replaced your custom recovery with a stock recovery. Obviously, you can't flash any custom ROM from Stock recovery.
Click to expand...
Click to collapse
Note: To go back to stock HTC:
Flash the stock RUU from here (follow the instructions in OP):
http://forum.xda-developers.com/showthread.php?t=2729173
Cheers
Mr Hofs said:
You can't flash the latest roms NOT because of your CID but because the firmware is outdated ! And as far as i can tell about your MID is that it's a sprint device.
You can only flash old kitkat roms at this time.
Maybe @redpoint73 can chip in .......
Click to expand...
Click to collapse
Yes... i tried some old kitkat but failed... as you said try sprint RUU.. i tried... and it worked.. ! u r god
info2shail2010 said:
Yes... i tried some old kitkat but failed... as you said try sprint RUU.. i tried... and it worked.. ! u r god
Click to expand...
Click to collapse
Great ! Good news
Enjoy
Mr Hofs said:
Great ! Good news
Enjoy
Click to expand...
Click to collapse
yeh... good news.. but Sim Network not working even i tried flashing boot.img via fastboot... ( flashed SkyDragon 6.0 marshamallow rom)
Mr Hofs said:
And as far as i can tell about your MID is that it's a sprint device.
You can only flash old kitkat roms at this time.
Maybe @redpoint73 can chip in .......
Click to expand...
Click to collapse
I agree, its the Sprint version according to the Model ID. I also agree with the above posts, that RUU is the best way to update the firmware.
But be aware that firmware is not the only potential pitfall on the Sprint version. Custom ROM support for the Sprint version is a little tricky due to kernel differences (with most other versions of the M8). You either need to stick to ROMs that explicitly state they support Sprint; or you may also be able to flash the proper kernel to make the ROM work. As-is (without modifying the kernel) Viper MM will not work on Sprint. I was reading on the ARHD thread, that some Sprint folks got that ROM working with the proper kernel, so the same may be true for Viper. But you should read up and learn more before messing with these ROMs and kernels.
info2shail2010 said:
yeh... good news.. but Sim Network not working even i tried flashing boot.img via fastboot... ( flashed SkyDragon 6.0 marshamallow rom)
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=64539538&postcount=32
Select mode GSM / UMTS, restart your device
Hi guys,
I tried to make a custom rom on my new HTC10 - something goes wrong (no it wasnt my first one )
But now I am a little bit stucked:
First the data:
** UNLOCKED **
htc_pmeuhl PVT S-OFF
CID-11111111
MID-2PS620000
ColorID-WHT00
LK-1.0.0.0000
[email protected]
OpenDSP-v20.0.8996.00007_0809
OS-2.41.401.41
Aug 2 2017,12:18:15(857212)
The Error happend after "updating" the firmware cause the Lee-Rom suggested the newst one. After the first "Loop" I tried the next one and the next and the next... I dont know how much Firmwares I tried honestly...
I am able to boot into TWRP and I am able to come back to Stock Recovery... So that will work... Maybe my partition crasehd with the Rom?
Any Idea or a little step by step suggestion?
I did the "How to root and TWRP" - Youtube tutorial by Rootjunky and until than everything worked fine... after that the failed Firmware-Update...
I have an EU-Phone, based in Germany
Hope anyone can help and thanks a lot for any ideas!
Cheers
majo
majomathes said:
Hi guys,
I tried to make a custom rom on my new HTC10 - something goes wrong (no it wasnt my first one )
But now I am a little bit stucked:
First the data:
** UNLOCKED **
htc_pmeuhl PVT S-OFF
CID-11111111
MID-2PS620000
ColorID-WHT00
LK-1.0.0.0000
[email protected]
OpenDSP-v20.0.8996.00007_0809
OS-2.41.401.41
Aug 2 2017,12:18:15(857212)
The Error happend after "updating" the firmware cause the Lee-Rom suggested the newst one. After the first "Loop" I tried the next one and the next and the next... I dont know how much Firmwares I tried honestly...
I am able to boot into TWRP and I am able to come back to Stock Recovery... So that will work... Maybe my partition crasehd with the Rom?
Any Idea or a little step by step suggestion?
I did the "How to root and TWRP" - Youtube tutorial by Rootjunky and until than everything worked fine... after that the failed Firmware-Update...
I have an EU-Phone, based in Germany
Hope anyone can help and thanks a lot for any ideas!
Cheers
majo
Click to expand...
Click to collapse
You are on the latest firmware for you phone. Did you try flash a US Unlocked firmware? Best thing to do is to flash the latest WWE RUU. Thanks @Kisakuku
https://androidfilehost.com/?fid=817550096634797504
Download and rename the zip to 2PS6IMG. zip
Place on external sdcard
Boot to download mode and press volume uo to flash. The RUU will erase EVERYTHING but you will be completely stock.
yldlj said:
You are on the latest firmware for you phone. Did you try flash a US Unlocked firmware? Best thing to do is to flash the latest WWE RUU. Thanks @Kisakuku
https://androidfilehost.com/?fid=817550096634797504
Download and rename the zip to 2PS6IMG. zip
Place on external sdcard
Boot to download mode and press volume uo to flash. The RUU will erase EVERYTHING but you will be completely stock.
Click to expand...
Click to collapse
I didnt know which one I all tried to flash - I think an US had a try
Do you have any other wink? Or is it just the WWE RUU? Can you explain what RUU stands for? I thought its a Russian version
Thank you a lot, Ill try it later :good:
edit: I always flashed Xiaomi & Sony devices, yet
majomathes said:
I didnt know which one I all tried to flash - I think an US had a try
Do you have any other wink? Or is it just the WWE RUU? Can you explain what RUU stands for? I thought its a Russian version
Thank you a lot, Ill try it later :good:
edit: I always flashed Xiaomi & Sony devices, yet
Click to expand...
Click to collapse
RUU = Rom Update Utility. It flashes the phone completely as if it came out of the box. Firmware, software.... the whole thing.
Mr Hofs said:
RUU = Rom Update Utility. It flashes the phone completely as if it came out of the box. Firmware, software.... the whole thing.
Click to expand...
Click to collapse
Thanks for explain =)
So I just have to flash the RUU - after that if the bootloader is still unlocked I can go ahead to flash a custom rom - right?
Thank you very much guys!
majomathes said:
Thanks for explain =)
So I just have to flash the RUU - after that if the bootloader is still unlocked I can go ahead to flash a custom rom - right?
Thank you very much guys!
Click to expand...
Click to collapse
Yes flash ruu to get the phone working again then reflash twrp then flash ROM. the bootloader will stay unlocked.
majomathes said:
Thanks for explain =)
So I just have to flash the RUU - after that if the bootloader is still unlocked I can go ahead to flash a custom rom - right?
Thank you very much guys!
Click to expand...
Click to collapse
Yup, flash the RUU, the bootloader will indeed remain unlocked. Flash TWRP and install the desired custom rom
Mr Hofs said:
Yup, flash the RUU, the bootloader will indeed remain unlocked. Flash TWRP and install the desired custom rom
Click to expand...
Click to collapse
Ok after flashing the RUU in download mode via sd-card with the volume up ... phone still not booting (hanging on the htc powered by android logo)
didnt flash twrp and custom rom,yet ... just want to test if its booting, seems to be not
sorry all good
majomathes said:
Ok after flashing the RUU in download mode via sd-card with the volume up ... phone still not booting (hanging on the htc powered by android logo)
didnt flash twrp and custom rom,yet ... just want to test if its booting, seems to be not
sorry all good
Click to expand...
Click to collapse
So is it working? Might take a while on first boot.
yldlj said:
So is it working? Might take a while on first boot.
Click to expand...
Click to collapse
No it doesnt work.
After flashin RUU I can boot into system (with the red warning for htc developement) but I cant install any custom rom ... bootloop is the result
and if i had the highest frustrationg, my "its really the last try" - worked... god damn it.. thank you guys. I dont know what the problem was... I did 10 times exactly the same thing
Thanks a lot... for people who stucking around like me:
1. use the link in post 2 and install
2. flash twrp ( https://twrp.me/htc/htc10.html) explained there
3. go into twrp do a data format or wipe ... or both and flash rom - gapps - supersu
4. reboot and wait sth like 5 minutes
majomathes said:
No it doesnt work.
After flashin RUU I can boot into system (with the red warning for htc developement) but I cant install any custom rom ... bootloop is the result
and if i had the highest frustrationg, my "its really the last try" - worked... god damn it.. thank you guys. I dont know what the problem was... I did 10 times exactly the same thing
Thanks a lot... for people who stucking around like me:
1. use the link in post 2 and install
2. flash twrp ( https://twrp.me/htc/htc10.html) explained there
3. go into twrp do a data format or wipe ... or both and flash rom - gapps - supersu
4. reboot and wait sth like 5 minutes
Click to expand...
Click to collapse
You mention flash gapps, for sense roms you don't have to do that, for aosp roms yes. But most of the time it's mentioned in the OP of aosp roms that you have to flash it twice, or flash the boot.img seperatly via fastboot to make it work. The correct gapps will do wonders too...... so i guess one of those things were the issue.