Database Develop

My HTC One is screwed?

Basically I successfully did everything necessary to unlock the bootloader and root the phone and I also flashed Superuser and had it confirmed by rootchecker. Where my phone got screwed is when i attempted to flash Android Revolution HD.
After flashing the ROM and pressing restart within TWRP recovery my phone went straight to the bootloader. Anything I did, from attempting to enter recovery or even power off the phone just sent me back to the bootloader.
I managed to re-flash TWRP and am able to access recovery BUT my entire phone is wiped (no backups ,roms, etc.) and my attempt to revert back to the original Sprint RUU has failed 3 times.
What I've noticed in the videos of people updating to the original Sprint RUU is that their image version for the current version is 1.2xxxx and is identical to the one they're updating to while mine is from: 1.31.651.2 to: 1.29.651.10.
Desperately in need of help as this phone is not even 2 weeks old.

MrAdrianP said:
Basically I successfully did everything necessary to unlock the bootloader and root the phone and I also flashed Superuser and had it confirmed by rootchecker. Where my phone got screwed is when i attempted to flash Android Revolution HD.
After flashing the ROM and pressing restart within TWRP recovery my phone went straight to the bootloader. Anything I did, from attempting to enter recovery or even power off the phone just sent me back to the bootloader.
I managed to re-flash TWRP and am able to access recovery BUT my entire phone is wiped (no backups ,roms, etc.) and my attempt to revert back to the original Sprint RUU has failed 3 times.
What I've noticed in the videos of people updating to the original Sprint RUU is that their image version for the current version is 1.2xxxx and is identical to the one they're updating to while mine is from: 1.31.651.2 to: 1.29.651.10.
Desperately in need of help as this phone is not even 2 weeks old.
Click to expand...
Click to collapse
Here you can find the RUU. I don't know wich one you want ..
Install this RUU in Fastboot (USB) otherwise it won't recognize your phone!

MrAdrianP said:
Basically I successfully did everything necessary to unlock the bootloader and root the phone and I also flashed Superuser and had it confirmed by rootchecker. Where my phone got screwed is when i attempted to flash Android Revolution HD.
After flashing the ROM and pressing restart within TWRP recovery my phone went straight to the bootloader. Anything I did, from attempting to enter recovery or even power off the phone just sent me back to the bootloader.
I managed to re-flash TWRP and am able to access recovery BUT my entire phone is wiped (no backups ,roms, etc.) and my attempt to revert back to the original Sprint RUU has failed 3 times.
What I've noticed in the videos of people updating to the original Sprint RUU is that their image version for the current version is 1.2xxxx and is identical to the one they're updating to while mine is from: 1.31.651.2 to: 1.29.651.10.
Desperately in need of help as this phone is not even 2 weeks old.
Click to expand...
Click to collapse
If you can still access TWRP, load another ROM onto a USB drive and plug it into your phone with an adapter. Flash properly by doing a complete wipe with TWRP and do a boot. It could have been a bad download initially. Did you do a MD5 sum check? As for the RUU, I've never done one (As I've never required an RUU *Knock on wood*) but from what I've read and seen, you need to revert everything you've done as in relocking the bootloader and reverting S-OFF if you've done that.

Athrun88 said:
If you can still access TWRP, load another ROM onto a USB drive and plug it into your phone with an adapter. Flash properly by doing a complete wipe with TWRP and do a boot. It could have been a bad download initially. Did you do a MD5 sum check? As for the RUU, I've never done one (As I've never required an RUU *Knock on wood*) but from what I've read and seen, you need to revert everything you've done as in relocking the bootloader and reverting S-OFF if you've done that.
Click to expand...
Click to collapse
Didn't check the MD5 & when attempting to use the RUU I did have S-ON(Never had S-OFF) and had the bootloader locked. But is there a way for me to push a rom to the phone using adb? I've tried before but it always says device not found.
Also, whenever i try to use the RUU the error I get has to with an incorrect Hboot version. Currently my Hboot is 1.44.0000.

MrAdrianP said:
Didn't check the MD5 & when attempting to use the RUU I did have S-ON(Never had S-OFF) and had the bootloader locked. But is there a way for me to push a rom to the phone using adb? I've tried before but it always says device not found.
Also, whenever i try to use the RUU the error I get has to with an incorrect Hboot version. Currently my Hboot is 1.44.0000.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2318497
Try this

MrAdrianP said:
What I've noticed in the videos of people updating to the original Sprint RUU is that their image version for the current version is 1.2xxxx and is identical to the one they're updating to while mine is from: 1.31.651.2 to: 1.29.651.10.
Click to expand...
Click to collapse
If your are S-ON you cannot flash an RUU that is older than your current firmware that's why its not working, you either have to stay on the same firmware or upgrade but you cannot downgrade so what you have to do is sideload a ROM using the tutorial dgtiii provided and everything will be back to normal, don't worry

[Q] need some serious help with return to stock

hi all,
sorry to sound like a complete idiot in advance !
I have been trying for over a month now to find some way to return my phone to stock so I can get the new ota update but im just having no luck !
I have tried everything to unroot , relock boot loader, and return to stock, I can successfully unroot, successfully relock the boot loader but cannot update OTA everytime I download the ota and allow the phone to start update process the phone boots into bootlaoder and a new line appears in the normal messages **** security warning*** when this happens I loose recovery and the phone hasn't updated. I then have to re-unlock the bootloader to then flash a recovery.
I cant flash RUU as there isn't an RUU available for me, H3G_001 , I have tried the suggested CWM nandroid backup, but this fails half way through something to do with android_secure
I cant seem to get the phone to successfully grant s-off to try the change cid method, I have tried to do this using HTC one kit by hasoon but no luck,
if anyone could please help it would me much appreciated
regards
okz19

Probably you don't have the stock rom or the recovery, because the secure warning come out when you aren't fully stock..

Look on this site: http://www.htc1guru.com/downloads/stock-rom-downloads/
Mine One works now fine and i have update to the latest OTA.

Justin2003 said:
Look on this site: http://www.htc1guru.com/downloads/stock-rom-downloads/
Mine One works now fine and i have update to the latest OTA.
Click to expand...
Click to collapse
Is better link to XDA

still stuck!
hi all as you can probably tell form the age of this topic, I have been stuck for a while !!! (11 October ! )
I am still having problems trying to get the new update 2.24.771.3
my phone is carrier locked to three uk
it is unrooted
custom recovery cwm touch
bootloader unlocked / tampered
I understand I need stock recovery and to lock bootloader
I don't have stock rom
my problem is as follows, my phone has been telling me for atleast 4 months now that I have a software update, when I click it it restarts takes me to cwm recovery verifys install then gets stuck on cannot mount data ....
I understand I need to flash stock recovery, I have tried to do this using the "all in one kit" however when I click flash my own recovery, (phone reboots into bootloader) I then proceed to select the stock recovery.img the cmd box then hangs "waiting for device" I am then alerted by my computer that the usb device has malfunctioned. ( I am on windows 8 and have turned of signature verification)
I cannot use the supposed simple method of RUU as there isn't one available for my stupid network!!
I have tried to use a cwm recovery image, this usually starts then spits out android_secure is missing.
yes I do have a hammer ready to hit the phone with, but just before I do this is there ANYONE with any last tips to help me, because ive just about had enough with this stupid phone !
the phone has 24 hours left to live, can you save its life ?
thanks in advance for any help.

1. You cannot install an OTA with a custom recovery.
2. I've encountered a CWM bug having to do with .android_secure. There's a hidden folder in /sdcard that caused it, I don't remember whether this file is ".android_secure" or another. You can probably wipe the sdcard before restoring the backup. If that fails, you can probably manually restore the backup with ADB (this will be hard).
3. If you want to install the custom recovery, boot to the fastboot and use USB to install the recovery. Don't use a toolkit because they're useless when anything goes wrong.

[Q] HTC One semi bricked!! i think help

Hi All,
Help required with my HTC One 801n. I have read and search numourse posts but still cant load a ROM or anything back onto it
The phone details
M7 UL
Hboot 1.54
Radio 4A.17.3250.14
CID HTC_001
S ON
The phone was unlocked and rooted shortly after I bought it in July. I was using a Google edition Revolution HD 22 Rom, but I decided to try a CM10.2 ROM and this is where it all started to go wrong. I downloaded the CM Rom and started to flash it on my phone but I got a boot loop with a different screen repeating over the recovery screen so I tried to wipe it and reflash but in doing so I deleted everything. At that time I could get into the recovery screen where it said there wasn’t a ROM installed, so I tried flashing the ROM again but this time I can only get into the boot loader and Fastboot, with no option into recovery.
Things I have tried
unlocked In fastboot tried flashing various ROMs but at the end it says FAILED: (remote:not allowed
ROMs i have tried are the latest from HTC dev web site PN07IMG_M7_UL_JB43_SENSE50_MR_BrightstarUS_WWE_3.22.1540.1 & CM10.2 roms and bootimg files but just get the Failed message at the end.
I have tried locking the boot loader and trying a RUU file but the same thing with failed messages at the end or wrong signature.
Is there something pretty basic I am missing because the fastboot cmds seem to work just not for flashing.
Aslo tried the adb side load but it doesn’t list my device and the cmd don’t work, they work fine in fastboot.
Any help would be appreciated before it ends up in bits!!

The cid on the phone and the ruu has to be the same.
---------- Post added at 07:03 PM ---------- Previous post was at 07:03 PM ----------
Try -off

andyp1 said:
Hi All,
Help required with my HTC One 801n. I have read and search numourse posts but still cant load a ROM or anything back onto it
The phone details
M7 UL
Hboot 1.54
Radio 4A.17.3250.14
CID HTC_001
S ON
The phone was unlocked and rooted shortly after I bought it in July. I was using a Google edition Revolution HD 22 Rom, but I decided to try a CM10.2 ROM and this is where it all started to go wrong. I downloaded the CM Rom and started to flash it on my phone but I got a boot loop with a different screen repeating over the recovery screen so I tried to wipe it and reflash but in doing so I deleted everything. At that time I could get into the recovery screen where it said there wasn’t a ROM installed, so I tried flashing the ROM again but this time I can only get into the boot loader and Fastboot, with no option into recovery.
Things I have tried
unlocked In fastboot tried flashing various ROMs but at the end it says FAILED: (remote:not allowed
ROMs i have tried are the latest from HTC dev web site PN07IMG_M7_UL_JB43_SENSE50_MR_BrightstarUS_WWE_3.22.1540.1 & CM10.2 roms and bootimg files but just get the Failed message at the end.
I have tried locking the boot loader and trying a RUU file but the same thing with failed messages at the end or wrong signature.
Is there something pretty basic I am missing because the fastboot cmds seem to work just not for flashing.
Aslo tried the adb side load but it doesn’t list my device and the cmd don’t work, they work fine in fastboot.
Any help would be appreciated before it ends up in bits!!
Click to expand...
Click to collapse
Based on your CID you got the incorrect RUU. You should have gotten this one: RUU_m7_ul_k44_sense55_mr_htc_europe_4-19-401-9_r_radio_4a-23-3263-28_10-38r-1157-04l_release_353069_signed_2-1-exe Going forward once you get back up, you should think of getting S-OFF. It would give you more flexibility with ROM etc. But you also have to be more carefull.
Also, to run the RUU your bootloader must be locked/relocked since you are S-ON.

majmoz said:
Based on your CID you got the incorrect RUU. You should have gotten this one: RUU_m7_ul_k44_sense55_mr_htc_europe_4-19-401-9_r_radio_4a-23-3263-28_10-38r-1157-04l_release_353069_signed_2-1-exe Going forward once you get back up, you should think of getting S-OFF. It would give you more flexibility with ROM etc. But you also have to be more carefull.
Click to expand...
Click to collapse
that wont work as he is s-on, his HBOOT is 1.54 and that RUU has HBOOT 1.56, too many steps up, it will fail with image error.
you need to use this: http://www.htc1guru.com/2013/10/guru-reset-3-62-401-1-stock-rom/
or this one is probably better for you which is probably the same version you had on the phone to start with: http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-8-zip/
push it to your internal storage and flash like a custom rom, select wipe data, install stock recovery and install stock radio when prompted, you should get OTAs after that.

[Q] HTC one reboots - Regardless of rom flashed

Hello everyone,
I've got a weird issue where I can recovery/fastboot/adb just fine.
But no matter what rom I install on my HTC One it boots up to a certain point (past the HTC logo to a midpoint of google boot up logo, sometimes into the os)
I had GPE 4.3
I tried to install 4.4 with the new radios. (S-Off)
It messed up once, I re-flashed cwm (had twrp) through fast boot - tried GPE 4.3 again .. still rebooting
re-flashed through fast new twrp again (just in case) - did advanced wipe - tried both roms still the same thing.
I've tried adb push and sideload.
Am I overlooking something here ? Any help or point to some reading material would be greatly appreciated.
I've been searching and searching and it seems most in similar situations can adb sideload roms when internal storage is not accessible and be right back up. I m stil stuck in the boot loop.
Currently downloading htc one sense 4.4. if I could get GPE 4.4 to work it'd be great.
Thank You in advance.
EDIT:
Phone is HTC ONE Rogers (Canadian)
Rooted - S-Off
Downloaded New ROM from - http://forum.xda-developers.com/showthread.php?t=2341395
Original ROM - http://htconeroot.com/htc-one-root/google-play-edition-rom-android-4-3-for-htc-one/

yasink said:
Hello everyone,
I've got a weird issue where I can recovery/fastboot/adb just fine.
But no matter what rom I install on my HTC One it boots up to a certain point (past the HTC logo to a midpoint of google boot up logo, sometimes into the os)
I had GPE 4.3
I tried to install 4.4 with the new radios. (S-Off)
It messed up once, I re-flashed cwm (had twrp) through fast boot - tried GPE 4.3 again .. still rebooting
re-flashed through fast new twrp again (just in case) - did advanced wipe - tried both roms still the same thing.
I've tried adb push and sideload.
Am I overlooking something here ? Any help or point to some reading material would be greatly appreciated.
I've been searching and searching and it seems most in similar situations can adb sideload roms when internal storage is not accessible and be right back up. I m stil stuck in the boot loop.
Currently downloading htc one sense 4.4. if I could get GPE 4.4 to work it'd be great.
Thank You in advance.
EDIT:
Phone is HTC ONE Rogers (Canadian)
Rooted - S-Off
Downloaded New ROM from - http://forum.xda-developers.com/showthread.php?t=2341395
Original ROM - http://htconeroot.com/htc-one-root/google-play-edition-rom-android-4-3-for-htc-one/
Click to expand...
Click to collapse
are you flashing the required version of TWRP ? TWRP_2.6.3.3_m7
also flashing rom's doesn't update radios .. flashing radios or firmware updates radios

Roger that
clsA said:
are you flashing the required version of TWRP ? TWRP_2.6.3.3_m7
Click to expand...
Click to collapse
Yep ... that is the exact one I got.
openrecovery-twrp-2.3.3.3-m7

yasink said:
Yep ... that is the exact one I got.
openrecovery-twrp-2.3.3.3-m7
Click to expand...
Click to collapse
are you doing fastboot erase cache after updating the recovery ?

As you are S-off, run a full RUU to remove any problematic flashes.

Thank you for the replys.
I've tried this fastboot cache erase .. didnt work
ruu is quite hard to find for Rogers HTC one (so far no luck ../ found some old ones links broken ... will keep looking)
I also got a chance to try and flash htc stock sense 5.5 with 4.4 kitkat from here:
(durm it .. can't post outside links yet sorry ..)
Phone still reboots before fully getting to os.
Weirdly enough, if I turn it off during this cycle. It turns back on by itself too.
So far to stop the loop, I have to boot to recovery (TWRP currently) and lock it.
I am guessing I should find a way to S-ON then flash an older rom.
Anything else I could try? :fingers-crossed:
Thank You everyone.

yasink said:
Thank you for the replys.
I've tried this fastboot cache erase .. didnt work
ruu is quite hard to find for Rogers HTC one (so far no luck ../ found some old ones links broken ... will keep looking)
I also got a chance to try and flash htc stock sense 5.5 with 4.4 kitkat from here:
(durm it .. can't post outside links yet sorry ..)
Phone still reboots before fully getting to os.
Weirdly enough, if I turn it off during this cycle. It turns back on by itself too.
So far to stop the loop, I have to boot to recovery (TWRP currently) and lock it.
I am guessing I should find a way to S-ON then flash an older rom.
Anything else I could try? :fingers-crossed:
Thank You everyone.
Click to expand...
Click to collapse
try this TWRP Nandroid Backup
http://www.htc1guru.com/dld/m7-twrp-nandroid-backup-cid-roger001-3-22-631-1-zip/
To use – download the latest version of the needed recovery and install it via fastboot:
fastboot flash recovery CWM.img
or
fastboot flash recovery TWRP.img
Then enter recovery either by holding power and vol down button until bootloader displays and then select recovery or if device is booted into the OS use this adb command:
adb reboot recovery
Now perform a test backup and allow it to complete. Then make a note of the folder in which the backup was created. Now copy the downloaded stock Nandroid into that same folder so that recovery will see the backup and allow you to restore it.
Click to expand...
Click to collapse

That nandroid backup method did take me the furthest so far.
(did wipe before doing it also)
The phone went into the os ... but only to reboot about 30 seconds later.
On the second reboot .. it said an app is asking for super user permission, before i could select allow or anything,
the phone has been boot looping again.
Weird.

yasink said:
That nandroid backup method did take me the furthest so far.
(did wipe before doing it also)
The phone went into the os ... but only to reboot about 30 seconds later.
On the second reboot .. it said an app is asking for super user permission, before i could select allow or anything,
the phone has been boot looping again.
Weird.
Click to expand...
Click to collapse
try wiping everything and try again

hi clsA,
thank you for replying.
I did try that, still bootloops. I also further tried:
install teaMseven - sense55 - kk - v2.3.6 with the new stock sense 5.5 rom flashed first.
I forgot to mention earlier, I did flash a radio after initially trying to upgrade to GPE 4.4.
The radio flashed was: RadioUpdate_4T.21.3218.21_10.16.1718.01L.zip
only because it was mentioned i'd get a boot loop going to GPE 4.4 without that update.
Theres no sim in the tray, could this radio update be causing this ? I tried re-downloading this radio for a fresh copy of the file also.
IF the radio is/could be causing this, is there a way to determine which radio to try?
I found: http://forum.xda-developers.com/showthread.php?t=2325564
Out of any further ideas for now

[SOLVED]
Hello everyone,
After so many days of trying, I finally found a way to fix my phone.
I noticed a lot of requests all over the web of a Rogers RUU. This is how I was able to bring my Rogers HTC back to life and stock.
I found this guide:
http://www.htc1guru.com/guides/return-stock-guide/
(Same website, that has the nandroid backup posted earlier by clsA)
follow ... that guide. Should be good.
I flashed 4.4 GP afterwards (as originally intended) and then OTA'd to 4.4.2. Everything seems to be running perfectly.
Thank You for the nandroid backup and leading me to that website clsA.

Softbrick (kinda) problem

Hi all,
So let me explain. I was given a HTC One for repair and the person just told me that her child did something wrong in the settings and the phone didn't boot anymore. The phone was on an older stock ROM and didn't get past the HTC One logo. Something was corrupted because the startup sound was cutting off before it had played like it should.
anyways: the phone is S-ON and I have unlocked the bootloader via HTCDev. I can install CWM, CWM Touch and TWRP but can't install any Sense rom because of the antique HBoot 1.56. I can however boot into CM 10.2.1 stable with no problems and ARHD 9.4 but with nou touch. On both ROMs firewather and rumrunner fail (usb debugging is on and root also for adb and apps).
Possible fixes I think off:
-Install an older ARHD version like 42 or 61 or 62 that is compitable with my firmware (but can't find them anywhere);
-install an insecure kernel compatible with CM10.2 (can't find one);
-Somehow just revert back to a Sense rom, wich I can't.
I just want S-off but every s-off tool fails. Is there another way to instal RUU exe or ZIP without S-OFF or at least upgrade the damn antique radio image that belongs in a museum ?
Thanks in advance

soulaiman said:
Hi all,
So let me explain. I was given a HTC One for repair and the person just told me that her child did something wrong in the settings and the phone didn't boot anymore. The phone was on an older stock ROM and didn't get past the HTC One logo. Something was corrupted because the startup sound was cutting off before it had played like it should.
anyways: the phone is S-ON and I have unlocked the bootloader via HTCDev. I can install CWM, CWM Touch and TWRP but can't install any Sense rom because of the antique HBoot 1.56. I can however boot into CM 10.2.1 stable with no problems and ARHD 9.4 but with nou touch. On both ROMs firewather and rumrunner fail (usb debugging is on and root also for adb and apps).
Possible fixes I think off:
-Install an older ARHD version like 42 or 61 or 62 that is compitable with my firmware (but can't find them anywhere);
-install an insecure kernel compatible with CM10.2 (can't find one);
-Somehow just revert back to a Sense rom, wich I can't.
I just want S-off but every s-off tool fails. Is there another way to instal RUU exe or ZIP without S-OFF or at least upgrade the damn antique radio image that belongs in a museum ?
Thanks in advance
Click to expand...
Click to collapse
Hboot 1.56 is not that old the current is 1.57! You can install RUU being S-ON the RUU must be the same or higher version, signed and the bootloader has to be locked/relocked. For Sense ROMs you might try TWRP 2.6.3.3 it seems to work best. ARHD 81 should work with your phone you have to wipe in Aroma before you install it.

I couldn't get ARHD 81 to work, but if someone is in the same situation here is what I did:
1) Relock your bootloader with this command:
fastboot oem lock
2) download this signed radio file : https://www.androidfilehost.com/?w=file-thanks&fid=23622183712460395&mid=70&download_id=t0kvkiiupbv0r5gakftasij7d5&tid=1412801244&hc=731cbdd91c39e4104b17bb47e6236fd9614838fa88b158009a1006be6b2ec5ea
3) Place the file in the same platform-tools directory for ease of use and insert this command:
fastboot oem rebootRUU
4) Once the phone reboots into a black HTC screen enter:
fastboot flash zip <name_of_the_file_here_without_quotes>
5) Normally it should succeed and tell you to immediatly flush, if it fails reattempt to flash the zip and it will succeed.
6) Download your prefered Recovery, mine is CWM but TWRP is even better sometimes and enter:
fastboot reboot-bootloader and then fastboot flash recovery <recovery.img>
6B) EDIT: to be able to flash a recovery IMG with S-On you need to unlock you bootloader again.
fastboot flash unlocktoken Unlocktoken_bin or whatever your unlocktoken is called
Then accept the security warning on your phone with the volume keys and power key.
7) Once succeed enter recovery and flash Maximus HD
8) Once done please enter bootloader again by pressing vol- + power or bij selecting advanced, reboot bootloader in recovery.
9) Because we're S-On, we need to manually flash boot.img
fastboot flash boot boot.img and if you get bootloops fastboot erase cache
Once this is done you should be able to boot into the rom and everything should work. Flashing this has upgraded my hboot to 1.57. Now I will report if I succeed to get S-off.

Well I couldn't find an RUU that was signed and for my version. Also I don't know why but I couldn't get ARHD to work. Maybe I need s-off or another recovery but even with elemental X it didn't boot.

soulaiman said:
Well I couldn't find an RUU that was signed and for my version. Also I don't know why but I couldn't get ARHD to work. Maybe I need s-off or another recovery but even with elemental X it didn't boot.
Click to expand...
Click to collapse
Okay so what I want to suggest you do is for starters go in unlock the bootloader as re locking it before doing anything is pointless when once everything is fixed is when you'd need to do it. Also I recommend that you install the custom recovery first and flash the rom from there rather than trying to flash it using fastboot as then at least we can get a standard recovery message which may be easier to find an answer for, I recommend using the very latest twrp recovery from their site as that should be able to flash all roms but make sure you install a stock sense 6 rom as the phone needs to be on the latest update with the kk radios and obviously that means having an hboot of 1.57 which would allow you to install custom roms that are running on kk otherwise you'll have issues and if you've followed what I suggest and it doesn't work a logcat and even a video of what is actually happening will help a lot to see what's going on but first things first is make sure that phone is on the latest hboot and the latest radio.
Also what version of phone is it? is it a m7ul? I'll send you an ruu link if I know what version we're looking at

dc959 said:
Okay so what I want to suggest you do is for starters go in unlock the bootloader as re locking it before doing anything is pointless when once everything is fixed is when you'd need to do it. Also I recommend that you install the custom recovery first and flash the rom from there rather than trying to flash it using fastboot as then at least we can get a standard recovery message which may be easier to find an answer for, I recommend using the very latest twrp recovery from their site as that should be able to flash all roms but make sure you install a stock sense 6 rom as the phone needs to be on the latest update with the kk radios and obviously that means having an hboot of 1.57 which would allow you to install custom roms that are running on kk otherwise you'll have issues and if you've followed what I suggest and it doesn't work a logcat and even a video of what is actually happening will help a lot to see what's going on but first things first is make sure that phone is on the latest hboot and the latest radio.
Also what version of phone is it? is it a m7ul? I'll send you an ruu link if I know what version we're looking at
Click to expand...
Click to collapse
Thanks for the info and help.
The phone is allready been returned to the owner, it was just a repair job because the phone was out of waranty and nobody in this town could fix it. in fact, some idiot that didn't know what he was doing flashed the wrong hboot version (other phone/model) on it somehow and it was a mess.
I did manage to repair it trough an RUU I found I think or I did install a custom sense 6 rom... I don' remember exactly but it had a mismatching hboot version that's all I remember