Hello. I need help!! I want my htc sense 3.6 back on my phone but I am not sure how to uninstall MIUI ROM. In other words, I wanted what I had right after I rooted my phone, before I installed MIUI ROM. Anyone know how to do this? Thanks!
If you made a recovery file in the recovery then just install the file if not then relock the bootloader and run the Stock ruu file and then just re unlock root ect.
menachemt said:
Hello. I need help!! I want my htc sense 3.6 back on my phone but I am not sure how to uninstall MIUI ROM. In other words, I wanted what I had right after I rooted my phone, before I installed MIUI ROM. Anyone know how to do this? Thanks!
Click to expand...
Click to collapse
I imagine you would have rooted your phone, unlocked bootloader (maybe), and flashed a custom recovery (like clockworkmod or wcx). I don't think any of those things would have changed during your use of MIUI.
Easiest way? Relock your bootloader (if you had unlocked it), and then run the stock RUU for your phone to revert your phone to stock. Then you can unlock bootloader again and then root your stock rom (I believe there is the all-in-one tool that makes rooting quite easy).
Or... if you want to try another custom rom, download the rom zip, copy it on your SDCard, and....
1) Pull the battery, and re-insert
2) Boot phone by holding VOLDOWN and POWER. You are in bootloader. At this screen you can see if you are S-ON or S-OFF (good to know for the later steps)
3) Choose recovery
4) If you're in WCX recovery or ClockWorkMod recovery, then you can do the 4 wipes (Data/Cache/Dalvik/System). ** But if you see you are NOT in a custom recovery, stop now.
5) Then you can flash the custom rom zip.
6) *At this point - if you are S-OFF, then the rom's kernel would have flashed with the rom, so you're done.
*But if you're S-ON, you will now need to flash the rom's kernel manually via fastboot. (on your computer, just extract the boot.img from the rom's zip, put it in the same folder where your fastboot.exe is, and run
Code:
fastboot flash boot boot.img
Related
Anyone know how to root Nexus One 2.3.4? I've done a few search but I can't find a full guide for that.
Thank you. Peace.
Since Gingerbreak doesn't work with 2.3.4(IIRC), what you can do is:
1.
- Downgrade to 2.3.3.
- Use gingerbreak to get root, flash custom recovery.
(If you downgraded to froyo, you can root it with z4root or SuperOneClick)
- Get ChainsDD's Superuser in flash-able .zip file. Copy it to SD card.
- Get 2.3.4 OTA update patch, copy it to SD card. If you don't want to lose custom recovery, open zip file with any archive utility, delete /recovery from zip. It will prevent stock recovery from restoring.
(If you downgraded to froyo and rooted, you need to get all OTA patches for upgrading to 2.3.3 and 2.3.4)
- Boot to recovery, flash (modified) OTA update patch. Don't reboot the device yet.
- Flash Superuser.
If you can use any application that requires root permission, you're done.
2. Unlock bootloader, push custom recovery and Superuser.
3. This requires Android Kitchen.
- Downgrade to 2.3.3 and root, flash custom recovery, same as 1.
- Get 2.3.4 system dump here.
- Use Android Kitchen to make rooted stock 2.3.4 package. When it's done, copy it to SD card.
- Backup all your data before proceed.
- Reboot to recovery, flash the package you made.
- Reboot and check. If nothing's wrong, you will have rooted stock with custom recovery.
Or when you're on 2.3.4, go to fastboot, flash a custom recovery, flash the superuser.zip
illuminarias said:
Or when you're on 2.3.4, go to fastboot, flash a custom recovery, flash the superuser.zip
Click to expand...
Click to collapse
You need to unlock bootloader to do that.
LFact said:
You need to unlock bootloader to do that.
Click to expand...
Click to collapse
unlock bootloader will wipe all data on device.
Hi guys, thank you for the tips.
So the best way is tho unlock the bootloader? I have no issue to do that since my warranty is finished. Doesn't matter whether it wipes out my data. I have few questions:
1. After I unlocked my bootloader, can I update any upcoming firmware OTA in the future? Or I have to flash it via sdcards.
2. I've heard about rebooting will unroot the phone. Is it true?
3. How do I unlock my bootloader?
4. Is changing rom will reset the phone to factory setting? Will my phone get unrooted?
Sorry I'm quite a noob here. Peace! Appreciate any helps.
1. With unlocked bootloader you do what you want.
2. No.
3. Read the wiki or a another guide. Mainly get the needed software onto a computer and run fastboot oem unlock when the phone is in the bootloader.
4. Flashing/updating to any rom that does not have root included you will loose root. With unlocked bootloader that is no issue. Flash custom recovery then flash su = root.
Great! Thanks!! I will search for a guide and unlock my bootloader soon!
I just picked up a nexus one unlocked with 2.3.4 stock. I want to downgrade to 2.2.2 or 2.2.1, root it with super one click, then after I get root go to rom manager and get my recovery and then flash a cyanogenmod rom. Saying all that what is the easiest way to downgrade to 2.2.1 or 2.2.2 ???
Thanks
vinnyjr said:
I just picked up a nexus one unlocked with 2.3.4 stock. I want to downgrade to 2.2.2 or 2.2.1, root it with super one click, then after I get root go to rom manager and get my recovery and then flash a cyanogenmod rom. Saying all that what is the easiest way to downgrade to 2.2.1 or 2.2.2 ???
Thanks
Click to expand...
Click to collapse
Use passimg.zip. However, if it has really unlocked bootloader, all you have to do is use fastboot to flash custom recovery and any custom rom you want without doing so.
I have locked bootloader and have stock 2.3.4 on my nexus one... How to downgrade it to 2.3.3?
william31518 said:
I have locked bootloader and have stock 2.3.4 on my nexus one... How to downgrade it to 2.3.3?
Click to expand...
Click to collapse
Use passimg.zip, though it depends on your main version saved in bootloader. If you can get FRG33 or FRG83 passimg.zip(though I wonder if you can find it...), use that, then (manually) update them until you reach 2.3.3.
Hey peeps I've unlocked my bootloader and rooted it. So far so good. Thanks for all the helps.
cjoshua said:
Hey peeps I've unlocked my bootloader and rooted it. So far so good. Thanks for all the helps.
Click to expand...
Click to collapse
I feel daft; I have unlocked the bootloader but cannot root, how ridiculous is that.. Am on 2.3.4 build GRJ22.
I'm trying to install "Root" (point V) on http://forum.xda-developers.com/showthread.php?t=636795 but cannot enter the recovery, getting "triangled" for ever & ever.
Please help guys..
(P.S. It is 06:30 here and I've just worked the whole night, that doesn't make anything any easier..)
Not sure what the guide says, but:
Download and place this zip on your SD.
http://dl.dropbox.com/u/6408470/su-releases/su-2.3.6.1-ef-signed.zip
When connected in fastboot, type:
fastboot flash recovery name-of-recovery.img
fastboot boot name-of-recovery.img
Then flash the su zip - DONE!
Note:
name-of-recovery.img should be replaced with the actual name of the recovery image you have.
The recovery image needs to be located in the same folder on your PC as fastboot.
If your using mac or linux, fastboot may need to be substituted for fastboot-mac or fastboot-linux, etc.
danger-rat said:
Not sure what the guide says, but:
Download and place this zip on your SD.
http://dl.dropbox.com/u/6408470/su-releases/su-2.3.6.1-ef-signed.zip
When connected in fastboot, type:
fastboot flash recovery name-of-recovery.img
fastboot boot name-of-recovery.img
Then flash the su zip - DONE!
Note:
name-of-recovery.img should be replaced with the actual name of the recovery image you have.
The recovery image needs to be located in the same folder on your PC as fastboot.
If your using mac or linux, fastboot may need to be substituted for fastboot-mac or fastboot-linux, etc.
Click to expand...
Click to collapse
Thanks for the reply!
I think the problem is in that the "recovery-RA-passion-v2.2.1" isn't supporting build GRJ22 yet. Doing the above correctly (I think) but cannot boot into recovery.
You think wrong. Do it EXACTLY as danger said.
albundy2010 said:
You think wrong. Do it EXACTLY as danger said.
Click to expand...
Click to collapse
Woa, easy mate.. Found the problem, I think. There's no SD card in the phone. Would that explain it?
(Need to wait a while now until I can use the girlfriend's..)
SD isn't required to install recovery, but you will need it for the su zip.
What sort of message are you getting when you flash recovery?
danger-rat said:
SD isn't required to install recovery, but you will need it for the su zip.
What sort of message are you getting when you flash recovery?
Click to expand...
Click to collapse
I get OKAY on both "sending" & on "writing" the recovery in fastboot. I just cannot boot into recovery. It gets stuck on the triangle and I have to pull the battery
Using the super tool, I managed to unlock bootloader, install superuser, and the modified cwm, but can't achieve Su permissions and can't flash Roms...
This is all after unbricking the device... Lol. I failed to properly install the android SDK tools, but proceeded to unlock bootloader, then flashed the holicakes kernel with the thought that it was a full Rom, lol... Needless to say, it was bricked... So I downloaded the HTC ics ruu and brought it back to stock. From there I re-unlocked the bootloader, flashed modified cwm, and installed superuser... Now what?
Installed su in recovery?
Sent from my HTC PH39100 using Tapatalk 2
Mr_Random said:
Using the super tool, I managed to unlock bootloader, install superuser, and the modified cwm, but can't achieve Su permissions and can't flash Roms...
This is all after unbricking the device... Lol. I failed to properly install the android SDK tools, but proceeded to unlock bootloader, then flashed the holicakes kernel with the thought that it was a full Rom, lol... Needless to say, it was bricked... So I downloaded the HTC ics ruu and brought it back to stock. From there I re-unlocked the bootloader, flashed modified cwm, and installed superuser... Now what?
Click to expand...
Click to collapse
If your goal is to flash a new modified rom then you can already proceed to do so with the unlocked bootloader and custom recovery. Your new modified ROM will have root access built in already. Just make sure when you flash a new ROM, you also flash the accompanying kernel (boot.img) as it is not flash automatically (unless you have already s-offed and the ROM chef has it written in his installation script) regardless it won't hurt to install the accompanying kernel just prior or after the ROM install.
Here is something important, if you are flashing ICS and you don't have the right bootloader, you have to get the new bootloader BEFORE flashing any ICS ROMs. You can do this by flashing the correct RUU with ICS (which requires you to relock and blah blah blah, but you already know this). Good luck with your flashing.
Thank you guys! I did install su from recovery, but I forgot that stock Roms still show as unrooted. I was hoping to just use flash image GUI to flash the kernel, boot into recovery, then Rom, but now I realize that without s-off/custom Rom, I need to use the supertool to flash the kernel.
However, supertool won't recognize the device when trying to push kernels... Should I check for and remove htc sync on the computer? Otherwise the right usb drivers and android SDK tools are present :-/
Also, when I go to flash the kernel for the Rom I choose, do I just unzip and pull the boot.img from within and replace the stock kernel in the supertool file? I've never successfully flashed an alternate kernel on to a device before, how do I know what is compatible?
If I ran the ruu, I should have the right bootloader, correct?
http://forum.xda-developers.com/showthread.php?t=1676787
How to ROOT Stock ICS
Root is working now, thanks! Now flash some custom rom's.
I am trying to get rid of the CM7.1 on my Incredible S. I have fastboot on my Ubuntu machine and all the android libraries necessary. I tried a lot of commands from fastboot a couple of days ago but nothing happened. Miui got stuck on boot screen, CM7.2 also did the same. I want to wipe my phone. Delete everything. I am sick of the CM7.1 it is old.
My bootloader says this:
***UNLOCKED***
VIVO .. S-ON
HBOOT-2.00.0000
RADIO-3822.10.08.28_M
I want a step by step way to wipe my phone and install the STOCK ROM (but keeping my root), and using Ubuntu. I have been through dozens of tutorials, my phone wont wipe.
OFFICIAL ROMS:
http://www.filefactory.com/f/e45d6fe3dcf51228/
question: which one do I download (which one is the latest) and why do they have 100mb + difference? thanks a lot!
I need your help before I smash the phone on the wall
Since you're s-on still and unlocked, have you flashed the boot.img from the roms are flashed? Its required after a new rom/kernel flash in order to get the rom booting.
Why do I have to flash the boot.img? I download the *.zip file and flash the whole zip file using ROM manager. That should be enough
alrosh7 said:
Why do I have to flash the boot.img? I download the *.zip file and flash the whole zip file using ROM manager. That should be enough
Click to expand...
Click to collapse
With s on you still have to fast boot flash boot.img to get the phone booting
Search how to do it, you probably did it when you flashed CM7
Sent from my Nexus 7
alrosh7 said:
Why do I have to flash the boot.img? I download the *.zip file and flash the whole zip file using ROM manager. That should be enough
Click to expand...
Click to collapse
With the unlocked bootloader, the boot partition only gets mounted as ReadOnly when in Recovery mode, thus when you flash a ROM in recovery mode, the boot.img file does not get written to your phone.
You manually have to flash the boot.img while in FASTBOOT USB mode using the command:
fastboot flash boot [boot.img file]
Also, you stated that you want to install a stock ROM but keep your root. Here are some things to keep in mind:
1. In order to flash an official HTC stock RUU, you must relock your bootloader. If you attempt to flash a RUU on an unlocked bootloader, you will get a 155 error.
2. Depending on which stock RUU you choose to flash, that particular bootloader may or may not be unlockable.
In the Development section there are several IncS stock, rooted ROMs that were built from official RUUs. I would recommend you give those a try. You may also want to look at mike1986's ARHD ROM which is based on the IncS ICS ROM.
Hi,
I just got a brand new HTC One 7 (WWE, CID E_11) after my last one died. Im trying to root it and install a custom recovery to install arhd or insertcoin. I used htc one toolkit for this. Everything seemed to work ok, but after booting the installed rom (ARHD or insertcoin) the phone reboots after i see the login screen. I somehow managed to reinstall my phone again yesterday, as it was a complete (soft) brick.
I used this to return to stock:
http://forum.xda-developers.com/showthread.php?t=2759000
Now does anyone know why I get a reboot loop? Does anyone know if i installed this stock rom if I get the normal OTA updates again? And do i need to relock the bootloader for this? I would really like to install stock roms again but I'm a little anxious after yesterday. (I've installed custom roms since the old HD2/HTC desire, and also on my old HTC One M7, never had any problems, I think it has to do with the Hboot).
Hoping to hear from you guys,
best wishes,
Olaf
Agil1ty said:
Hi,
I just got a brand new HTC One 7 (WWE, CID E_11) after my last one died. Im trying to root it and install a custom recovery to install arhd or insertcoin. I used htc one toolkit for this. Everything seemed to work ok, but after booting the installed rom (ARHD or insertcoin) the phone reboots after i see the login screen. I somehow managed to reinstall my phone again yesterday, as it was a complete (soft) brick.
I used this to return to stock:
http://forum.xda-developers.com/showthread.php?t=2759000
Now does anyone know why I get a reboot loop? Does anyone know if i installed this stock rom if I get the normal OTA updates again? And do i need to relock the bootloader for this? I would really like to install stock roms again but I'm a little anxious after yesterday. (I've installed custom roms since the old HD2/HTC desire, and also on my old HTC One M7, never had any problems, I think it has to do with the Hboot).
Hoping to hear from you guys,
best wishes,
Olaf
Click to expand...
Click to collapse
Flash the stock firmware 5.11.401.10! I think your firmware is mismatched.
By flashing the firmware after installing the Rom I might fix the bootloop? Or is the stock firmware necesarry to go back to stock? Sorry bit confused, thanks for your response btw
Sent from my HTC One using XDA Free mobile app
Agil1ty said:
By flashing the firmware after installing the Rom I might fix the bootloop? Or is the stock firmware necesarry to go back to stock? Sorry bit confused, thanks for your response btw
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
Flashing the firmware might fix the boot-loop, since you flashed the stock rom! If it does stop the boot-loops, you can re-install TWRP or CWM to get the custom recovery.
Agil1ty said:
By flashing the firmware after installing the Rom I might fix the bootloop? Or is the stock firmware necesarry to go back to stock? Sorry bit confused, thanks for your response btw
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
when using a sense custom rom you need to make sure you use twrp 2.6.3.3 recovery, do not use the toolkits, most of the time they are out of date and not updated, this would explain the bootloops, take the time to learn how to use adb and fastboot, you'll never look back.
nothing to do with the firmware and no need to flash it, if your firmware was knackered, you would have a hard brick.
Seanie280672 said:
when using a sense custom rom you need to make sure you use twrp 2.6.3.3 recovery, do not use the toolkits, most of the time they are out of date and not updated, this would explain the bootloops, take the time to learn how to use adb and fastboot, you'll never look back.
nothing to do with the firmware and no need to flash it, if your firmware was knackered, you would have a hard brick.
Click to expand...
Click to collapse
First of all thanks for the quick response. I know how to use adb and fastboot (at least I think).
If i would (in this order) do the following, would that be correct?:
unlock using htdev
Flash twrp 2.6.3.3 using fastboot command: "fastboot flash recovery recovery.img" (naming twrp 2.6.3.3.img = recovery.img)
reboot bootloader
Flash SuperSU.zip in TWRP
reboot twrp
flash custom rom (ARHD).
The thing is it isn't a normal bootloop (which normally would come with the HTC logo all the time)
It reboots when I try to setup the phone (in the setup menu). Restoring the phone with the link in the OP, ive recoverd my phone, but I would still love to use custom roms again.
Agil1ty said:
First of all thanks for the quick response. I know how to use adb and fastboot (at least I think).
If i would (in this order) do the following, would that be correct?:
unlock using htdev
Flash twrp 2.6.3.3 using fastboot command: "fastboot flash recovery recovery.img" (naming twrp 2.6.3.3.img = recovery.img)
reboot bootloader
Flash SuperSU.zip in TWRP
reboot twrp
flash custom rom (ARHD)
Click to expand...
Click to collapse
unlock using HTC Dev
flash TWRP 2.6.3.3
fastboot erase cache
fastboot reboot-bootloader
enter recovery
no need to flash super user it will be included in the rom you flash
flash custom rom, or stock reset rom, if its not rooted, twrp will ask you if you would like to root upon exit.
Seanie280672 said:
unlock using HTC Dev
flash TWRP 2.6.3.3
fastboot erase cache
fastboot reboot-bootloader
enter recovery
no need to flash super user it will be included in the rom you flash
flash custom rom, or stock reset rom, if its not rooted, twrp will ask you if you would like to root upon exit.
Click to expand...
Click to collapse
It seems that insertcoin had a problem in it's installer:
http://insertcoin-roms.org/category/devices/one_m7/one_sense6/
the changelog says: Fixed SuperSU install (might solve the sudden reboot issue in SetupWizard)
It left me without any rom to install, so i had to sideload ARHD, which it didnt want to install via sideload... The next step I isntalled stock again, which I'm using right now.. but I miss xposed framework and other tweaks too much..
I'm gonna try to unlock it again this afternoon and install insertcoin again, but this time ill make a backup first. Does installing the recovery wipe anything?
Agil1ty said:
It seems that insertcoin had a problem in it's installer:
http://insertcoin-roms.org/category/devices/one_m7/one_sense6/
the changelog says: Fixed SuperSU install (might solve the sudden reboot issue in SetupWizard)
It left me without any rom to install, so i had to sideload ARHD, which it didnt want to install via sideload... The next step I isntalled stock again, which I'm using right now.. but I miss xposed framework and other tweaks too much..
I'm gonna try to unlock it again this afternoon and install insertcoin again, but this time ill make a backup first. Does installing the recovery wipe anything?
Click to expand...
Click to collapse
no it doesn't wipe anything, but you can use xposed and its tweaks on stock rom, you just need to root first, just install TWRP, enter recovery and again upon exit it will offer to root stock rom for you.
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