Does anyone have a working version of the stock CDMA kernel ver.1.13.651.7?
I downloaded the one listed on this link, but after flashing it using TWRP recovery, and deleting the caches, the system rebooted in the same version I previously had.
After trying this twice, I can only assume that either the flash didn't work at all, or that the version is not actually 1.13.651.7, rather it's 1.11.651.3.
Any ideas?
Dudemeister said:
Does anyone have a working version of the stock CDMA kernel ver.1.13.651.7?
I downloaded the one listed on this link, but after flashing it using TWRP recovery, and deleting the caches, the system rebooted in the same version I previously had.
After trying this twice, I can only assume that either the flash didn't work at all, or that the version is not actually 1.13.651.7, rather it's 1.11.651.3.
Any ideas?
Click to expand...
Click to collapse
all the stock files are kept at http://goo-inside.me/shooter/ruu .
if you need an individual kernel, extract from the PG86IMG.zip file. either create your own .zip (replace files in an existing one) to flash from recovery, or flash just the kernel boot.img via fastboot and manually load the modules after booting.
not sure why you're going down to a previous version, but the steps above should get you on the right track.
good luck!
I'm not trying to go back. I have a rooted 3D EVO with ver. 1.11.651.3. I would like to upgrade the kernel to version 1.13.651.7.
Also when I said I was looking for the "Stock" kernel, I meant the basic kernel, not a modded one. However I do want one that will not wipe out my root.
Forgive my ignorance, but does using the official Sprint kernel also result in a loss of root ? Or is that only if I do the OTA upgrade process ?
In the RUU folder you linked, there are 2 versions of each file. The RUU signed version and the plain one. The unsigned ones are about 25MB smaller. What is the difference between them?
Last but not least, can I do a kernel only update, or do I have to get the complete ROM ( so the kernel and ROM match).
Dudemeister said:
I'm not trying to go back. I have a rooted 3D EVO with ver. 1.11.651.3. I would like to upgrade the kernel to version 1.13.651.7.
Also when I said I was looking for the "Stock" kernel, I meant the basic kernel, not a modded one. However I do want one that will not wipe out my root.
Forgive my ignorance, but does using the official Sprint kernel also result in a loss of root ? Or is that only if I do the OTA upgrade process ?
In the RUU folder you linked, there are 2 versions of each file. The RUU signed version and the plain one. The unsigned ones are about 25MB smaller. What is the difference between them?
Last but not least, can I do a kernel only update, or do I have to get the complete ROM ( so the kernel and ROM match).
Click to expand...
Click to collapse
1) In the link I provided, there is not a "signed" and plain version. The RUU is a .exe ran from a Windows based computer while the PG86IMG.zip file (also signed) can be flashed directly from the bootloader.
2) Using an official kernel will not result in a loss of root as root *should* be stored in the /system partition not in the kernel. If you're unsure how your device is rooted, feel free to use my Root Checker application and post your advanced Root Check results here.
3) You will lose root if you directly flash a full RUU or if you use any of the official OTA files. If you flash the latest hboot version 1.5, you will more than likely be forced to use the HTC unlock method to gain permanent root access. The HTC unlock method is not as thorough as the revolutionary method.
4) You can do a kernel only update. The modules stored in /system/lib/modules must match the kernel being loaded. There are some posts which have the stock kernel bundled into a .zip file. As long as these .zip files contain both the kernel boot.img and the kernel's modules, they can be loaded and should function well.
There will be two ways to load these kernels, assuming you've already rooted by running Revolutionary. 1) My app, Flash Image GUI. 2) Custom Recovery - Clockworkmod or TWRP.
Hope that helps!
Related
So i think i am getting lost and I really want to be careful before i re-start my crack flashing habits again.
I flashed senseless ics, loved it, but wanted to go back to gb. So i went back to senseless 1.1, extracted boot.img, and adb pushed and flashed then did a nandroid back up and every thing is A-ok .
Here is my confusion.
What problems are ppl refering to with Mainver? ( what is that even )
Why do ppl have to RUU ( again what is it)
is my method right ? Which is : if the rom came with an auto script to flash from hboot then hurray, if not, then flash boot.img from adb via fast boot and flash to my liking ?
the only roms i gave been on so far : cleanrom 1.5.5, inefebellis, senesless 1.1, senseless ecs, then back to senseless 1.1 via nandroid like mentioned.
jmichaels1982 said:
So i think i am getting lost and I really want to be careful before i re-start my crack flashing habits again.
I flashed senseless ics, loved it, but wanted to go back to gb. So i went back to senseless 1.1, extracted boot.img, and adb pushed and flashed then did a nandroid back up and every thing is A-ok .
Here is my confusion.
What problems are ppl refering to with Mainver? ( what is that even )
Why do ppl have to RUU ( again what is it)
is my method right ? Which is : if the rom came with an auto script to flash from hboot then hurray, if not, then flash boot.img from adb via fast boot and flash to my liking ?
the only roms i gave been on so far : cleanrom 1.5.5, inefebellis, senesless 1.1, senseless ecs, then back to senseless 1.1 via nandroid like mentioned.
Click to expand...
Click to collapse
ruu is flashing stock. method is right with the boot.img which is also the kernel but without other kernel files found in the flashable zip. If the rom doesnt have the boot.img u can also use cleanflash tool to flash the kernel/boot into your current rom,restart,then wipe/flash rom
sent from my rezound using tapatalk
RUU files are the official software releases from HTC.
RUU files are signed. (They give proper "official" codes to hboot to get past the s=on security)
This means that they can flash all parts of the device, even the bootloader and radio firmware, which we can not normally flash because it is write locked. (do to s=on we can't flash them even with root)
Sometimes people have issues and need to get the phone back to pure stock so they use the RUU.
Mainver is data on the software version number of the kernel (I believe... it may be for some other part, either way it is version info)
Think V1... V1.2... V1.5... V1.5.5
Because of s=on we are not allowed to "downgrade/revert" to older software versions.
The leaked ICS build has a newer Mainver, some people flashed the leak unmodified, and that changed the Mainver info. Now they need to use a special trick to trick the s=on security to allow flashing of older kernels. The ICS ROMs we have now, have been modified so they do not change the Mainver. This makes it easier to go back to GB or switch to other ROMs.
Marine6680 said:
RUU files are the official software releases from HTC.
RUU files are signed. (They give proper "official" codes to hboot to get past the s=on security)
This means that they can flash all parts of the device, even the bootloader and radio firmware, which we can not normally flash because it is write locked. (do to s=on we can't flash them even with root)
Sometimes people have issues and need to get the phone back to pure stock so they use the RUU.
Mainver is data on the software version number of the kernel (I believe... it may be for some other part, either way it is version info)
Think V1... V1.2... V1.5... V1.5.5
Because of s=on we are not allowed to "downgrade/revert" to older software versions.
The leaked ICS build has a newer Mainver, some people flashed the leak unmodified, and that changed the Mainver info. Now they need to use a special trick to trick the s=on security to allow flashing of older kernels. The ICS ROMs we have now, have been modified so they do not change the Mainver. This makes it easier to go back to GB or switch to other ROMs.
Click to expand...
Click to collapse
Good write up !
waw
Thank you Thank you Thank you ! best crash course ever ...
Hey all,
I'm currently running Innefabilis Deus Alpha Preview and I like it, but will wait for another update that's more stable. Anyway, I tried reverting back to Ineffabilis v1.0 (GB) but when I installed a Kernel by dsb, it says something about "Main version is older!" in fastboot. I read that if you've already flashed the latest leak (ICS), it's not easy to revert back to GB.
I'm wondering if I'm able to use CleanTool to flash dsb's Kernel instead after flashing a GB Rom. Can anyone help me? I've already tried flashing other Kernels via fastboot on my phone and have failed.
This is a common problem right now and you can do a few things...fastest and easiest way is you can flash boot.img via fastboot for short term fix. Just pull the boot.img from the ROM you are flashing. This will get you up and running...but you will run into this again.
For a long term solution...I just came across this...which should help you...
con247 said:
No offense, but this is what you get for flashing a leak without understanding the repercussions. Fortunately, you can be helped but in the future it may not be possible to restore to an earlier version if you flash a leak via a PH98IMG.zip.
Several things you and others must understand now that you have flashed your phone via the PH98IMG.zip leak. If you flashed scott's rom of the leak, you are fine and this DOESN'T apply to you.
1) Your mainver was updated. It is possible you WILL NOT be able to EVER use an RUU to restore in the future. The RUU checks for the mainver and if yours is newer, it will error. A new RUU of the official ICS update will probably work, but that could be a ways off and you could be screwed if you need to RUU in the mean time.
2) Since your mainver was updated, the current ways to install kernels that involve PH98IMG.zips won't work unless you modify them yourself. So you will have to install them via fastboot. Some of them are distributed as zImages so you can't flash those anymore without devs updating their tools. It is unlikely that they will, because in order for them to work with your phones, it will update everyone elses mainver when they run the kernel installation and doing that for everyone would be irresponsible.
DO NOT FLASH THIS IF YOU DIDN'T UPDATE TO THE LEAK VIA A PH98IMG.ZIP IF YOU FLASHED THE BOOT IMAGE WITH FASTBOOT OR CLEANFLASH YOU ARE FINE. IF YOU MODIFIED THE android-info.txt YOURSELF BEFORE FLASHING BECAUSE YOU ARE SMART, DON'T FLASH THIS EITHER.
Anyway, to use:
1) Wipe in recovery
2) Format /system in recovery
3) Run your nandroid restore or install a rom of your choice.
4) Flash the PH98IMG.zip from the bootloader.
Restart and you should be OK
Click to expand...
Click to collapse
get the PH98IMG from his post here...
http://forum.xda-developers.com/showpost.php?p=21442702&postcount=3
this works well. Myself I just cleaned everything up installed my GB rom, let it fail then pulled the battery and used the trusty droid to mount the sd card from the rezound and put this file on it. booted in to recovery let it do its thing and it worked perfect.
However I'm not sure if pulling the battery after the the file fails is safe, just a risk I took.
Ok, I am looking to S-OFF my device so I can flash ROMs onto it via CWM. I was using this tutorial: http://forum.xda-developers.com/showthread.php?t=1495657
One thing that troubles me is that it says you need a custom ROM already, but how? Do I need to flash a ROM via adb? I was looking to flash LeeDroid.
Thanks and sorry for all the questions,
Ubuntuz
Ubuntuz said:
Ok, I am looking to S-OFF my device so I can flash ROMs onto it via CWM. I was using this tutorial: http://forum.xda-developers.com/showthread.php?t=1495657
One thing that troubles me is that it says you need a custom ROM already, but how? Do I need to flash a ROM via adb? I was looking to flash LeeDroid.
Thanks and sorry for all the questions,
Ubuntuz
Click to expand...
Click to collapse
Not sure how the "Tool" works, but the process is fairly generic across HTC devices which allow the bootloader to be downgraded.
If the "Tool" provided in that post requires a custom ROM to be loaded while only having unlocked via the HTC official method, then you would need to load a custom recovery to flash the ROM .zip. If the ROM .zip has a custom kernel, my application, Flash Image GUI, can help flash the kernel portion of the ROM .zip. Guides are in my OP for HTC unlocked devices.
Off the top of my head, I could see a person writing a tool which relied on binaries being present in a custom ROM, instead of providing those binaries in the "Tool". If this is the case, it would make sense why the "Tool" requires a custom ROM be loaded first.
If you had the time and were wanting to expand your knowledge, I would recommend downgrading the bootloader manually instead of using a "Tool". Either way, the suggestions above should help. Best of luck!
joeykrim said:
Not sure how the "Tool" works, but the process is fairly generic across HTC devices which allow the bootloader to be downgraded.
If the "Tool" provided in that post requires a custom ROM to be loaded while only having unlocked via the HTC official method, then you would need to load a custom recovery to flash the ROM .zip. If the ROM .zip has a custom kernel, my application, Flash Image GUI, can help flash the kernel portion of the ROM .zip. Guides are in my OP for HTC unlocked devices.
Off the top of my head, I could see a person writing a tool which relied on binaries being present in a custom ROM, instead of providing those binaries in the "Tool". If this is the case, it would make sense why the "Tool" requires a custom ROM be loaded first.
If you had the time and were wanting to expand your knowledge, I would recommend downgrading the bootloader manually instead of using a "Tool". Either way, the suggestions above should help. Best of luck!
Click to expand...
Click to collapse
Well, I have CWM installed - I wanted s-off because from what I believe you need it to flash roms via recovery...
Different ROMS require different procedures, with s-on, Meanrom, my personal favorite is easily flashable with .zip files, With other ROMS you will have to unzip the ROM and take the boot.img and place it in SDK tools and push ADB. from usb fastboot through the terminal. zedomax on youtube is super helpful with 3d rooting.
* Make sure to us CWM 4.0.1.4
Be careful, you read a lot about people turning off/on bricking
zbergmark said:
Different ROMS require different procedures, with s-on, Meanrom, my personal favorite is easily flashable with .zip files, With other ROMS you will have to unzip the ROM and take the boot.img and place it in SDK tools and push ADB. from usb fastboot through the terminal. zedomax on youtube is super helpful with 3d rooting.
* Make sure to us CWM 4.0.1.4
Click to expand...
Click to collapse
What about if use this guide to downgrade from 10.4.0018?
It's just like that:
instead of flashing the PGXXX.IMG you can simply flash any RUU.
Except of the branding that is on ur device. If your device is branded by vodafone you can just flash a vodafone RUU.
The number that you have to change in the mmcblk block has to be the number that the RUU has. So if you choose to flash a RUU, and the ruu number is 1.20.401.8, you change the number to 1.20.401.8. With this way you can flash any RUU no matter which Hboot Version is included.
The one and only restriction is your branding.
Step 1: Change your mmcblk0p31.img Version number to the number that your RUU has. I.E. you are on 1.207.50.8 and your ruu has 1.20.401.8 change it to that number. (how to extract etc can be taken from the OP)
Step 2: Push it back as described in the OP
Step 3: boot into bootloader and do
Code:
fastboot oem lock
Step 4: Run the RUU and Enjoy.
I did that already twice with 2 german people that have had a problem because they were not able to change their cid.
Hope you can understand my explanation.
A list of RUU's:
http://www.filefactory.com/f/4ef0ef536face67a/
Hello,
I just HTCdev unlocked and rooted my phone AGAIN because the first time i tried to flash a ROM (CM 10 Nightly) I bricked my phone. First i re-locked, Ran the RUU, and unrooted completely to stock. Now I Re-unlocked, Re-rooted, I'm S-ON, and I Put TWRP and SuperSU on as well as Flash Image GUI and GooManager. Now I really want to get MeanRom on my phone but the two methods i've tried had no success.
1st attempt:
I put the MeanRomv65 zip on my phone from my macbook, I factory reset, wiped cache, wiped dalvic cache, and then went to install. Found the zip file and swipe to flash.. everything seems fine until i get an error and fail message at the end. It also says there is no MD5 file when i do this.
2nd attempt:
I restored my phone to my backup. I already had the MeanRomv65 zip on my phone from my previous attempt to flash it. So then i go into flash image GUI and go through finding the zip and everything. Then i get an error right above the Flash Image button saying "zip file must contain only one of the following: recovery.img, zimage, or a type of boot.img!" So I go on my computer, unzip the file and looked inside and all I see the boot.img and some folders but no recover or zimage so i dont know what it is talking about.
I then tried to download the older MeanRomv34 zip to see if maybe I had to have the older version on first but I got the same error.
I really dont want to go through the processes of unrooting and relocking my phone again so i want to do this right. Any help from here would be greatly appreciated! (and i do not have a windows 7 32bit computer, only a mac and a Windows 7 64bit so i don't believe that going S-off is an option for me without going out and buying a new computer)
I dont know how much of this matters but here is some info on my phone:
HTC EVO 4G LTE on hBoot 1.19 Software v. 2.13.651.1 71ORD HTCdev unlocked, Rooted, and I have TWRP and SuperSU
Kernel Version:
3.0.8-01680-gb6402b4
[email protected] #1
SMP PREEMPT
Other info:
Baseband v: 1.12.11.0809
Android Version: 4.04
HTC Sense: 4.1
HTC SDK API level: 4.24
I know this post is really long and I probably put waaayyy more information then I actually needed to but I just want to be safe. It seems like everything I try for putting any Roms on my phone goes wrong with an error or failed message and I really want to do this right now.
jklatt747 said:
Hello,
I just HTCdev unlocked and rooted my phone AGAIN because the first time i tried to flash a ROM (CM 10 Nightly) I bricked my phone. First i re-locked, Ran the RUU, and unrooted completely to stock. Now I Re-unlocked, Re-rooted, I'm S-ON, and I Put TWRP and SuperSU on as well as Flash Image GUI and GooManager. Now I really want to get the newest version of MeanRom on my phone but the two methods i've tried had no success.
1st attempt:
I put the MeanRomv65 zip on my phone from my macbook, I factory reset, wiped cache, wiped dalvic cache, and then went to install. Found the zip file and swipe to flash.. everything seems fine until i get an error and fail message at the end. It also says there is no MD5 file when i do this.
2nd attempt:
I restored my phone to my backup. I already had the MeanRomv65 zip on my phone from my previous attempt to flash it. So then i go into flash image GUI and go through finding the zip and everything. Then i get an error right above the Flash Image button saying "zip file must contain only one of the following: recovery.img, zimage, or a type of boot.img!" So I go on my computer, unzip the file and looked inside and all I see the boot.img and some folders but no recover or zimage so i dont know what it is talking about.
I then tried to download the older MeanRomv34 zip to see if maybe I had to have the older version on first but I got the same error.
I really dont want to go through the processes of unrooting and relocking my phone again so i want to do this right. Any help from here on out would be greatly appreciated! (and i do not have a windows 7 32bit computer, only a mac and a Windows 7 64bit so i don't believe that going S-off is an option for me without going out and buying a new computer)
I dont know how much of this matters but here is some info on my phone:
HTC EVO 4G LTE on hBoot 1.19 Software v. 2.13.651.1 71ORD HTCdev unlocked, Rooted, and I have TWRP and SuperSU
Kernel Version:
3.0.8-01680-gb6402b4
[email protected] #1
SMP PREEMPT
Other info:
Baseband v: 1.12.11.0809
Android Version: 4.04
HTC Sense: 4.1
HTC SDK API level: 4.24
I know this post is really long and I probably put waaayyy more information then I actually needed to but I just want to be safe. It seems like everything I try for putting any Roms on my phone goes wrong with an error or failed message and I really want to do this right now.
Click to expand...
Click to collapse
You've got to make sure TWRP is updated, you can do that with goo manager. There were lots of users that had an issue flashing Mean because they're TWRP was outdated. 2.3.0.1 should be the latest
Fyi and future use, download the rom directly to ur phone. I own a mac book and when I transfer files from it to my LTE I get double files, one of which is the the actual file and the other is some sort of no media file (4.00k in size). Good luck
banccalif said:
You've got to make sure TWRP is updated, you can do that with goo manager. There were lots of users that had an issue flashing Mean because they're TWRP was outdated. 2.3.0.1 should be the latest
Fyi and future use, download the rom directly to ur phone. I own a mac book and when I transfer files from it to my LTE I get double files, one of which is the the actual file and the other is some sort of no media file (4.00k in size). Good luck
Click to expand...
Click to collapse
I have 2.3.1.0 TWRP and okay i'll do that. You just download it like you would on a computer? Also I still need to know.. New version of MeanRom first, or go straight for new version?
Question: If i go with the process below to get MeanRom on my phone, do i need to go with the old version (MeanRomv34) or the new one (MeanRomv65).
"Use root explorer and extract meanrom move the boot.IMG to an easy location, browse to that location and try flashing thru flash image GUI."
also since I did the HTCdev unlock and TWRP on followed by rooting with SuperSU. Do i need to get rid of the SuperSU root first or something before trying to flash MeanRom? Or does that not matter? If i do need to get rid of it.. How?
jklatt747 said:
Question: If i go with the process below to get MeanRom on my phone, do i need to go with the old version (MeanRomv34) or the new one (MeanRomv65).
"Use root explorer and extract meanrom move the boot.IMG to an easy location, browse to that location and try flashing thru flash image GUI."
also since I did the HTCdev unlock and TWRP on followed by rooting with SuperSU. Do i need to get rid of the SuperSU root first or something before trying to flash MeanRom? Or does that not matter? If i do need to get rid of it.. How?
Click to expand...
Click to collapse
Just flash the latest version of MeanROM just like any other rom boot to recovery wipe cache/del cache/factory reset/system then find the MR file and flash away
I would recommend getting s-off. It makes things sooooo much easier
I used dirty racun on my windows 7 ultimate 64 bit system and it worked flawlessly.
Sent from my EVO using xda app-developers app
I tried to s-off my Desire 601 using rumrunner unde ubuntu and I received tis message:
unfortunately this isn't going to work out with your configuration. you have 2 options:
1.) flash an unsecure kernel that's compatible with your ROM and retry rumrunner (preferred and most reliable method).
2.) flash a different rom.
NOTE: No amount of messing around with su binaries and apk's is going to fix this issue for you!!!.
Better luck next time!!!!bye
When I enter in recovery apears S-OFF, but the phone restarting at the HTC logo.
Where can I find unsecure kernel or differnt room?
boot into recovery and select "mount" then select "system" then select "file manager" and go to /system/bin/hcheck and delete or rename "hcheck" then reboot
Thank you! You save my day!
Another issue now.
I've instaled Lyberty kernel and the only rom working is ClockWorkSenseless. Antoher rom's put the phone in bootloop and I cant do anything. The /system/bin folder is empty.
I want to go back to stock kernel and rom. How can i do that?
I'm on 4.2.2 S-off twrp 2.8.0.2
L.E. Solved. TWRP 2.8.0.2 was the problem. I put 2.7.0.0 and now I can see all the files.
What's means this message?
This build is for
development purposes
only Do not distribute outside of
HTC without HTC's written permission.
Failure to comply may lead to legal action
blue74lion said:
What's means this message?
This build is for
development purposes
only Do not distribute outside of
HTC without HTC's written permission.
Failure to comply may lead to legal action
Click to expand...
Click to collapse
It's hTC's standard message on S-OFF devices.
I have a thread going for removing that red text, but it's only got hboots from the 4.4.4 OTA.
If you want to remove it you can follow the instructions in post 2 of this thread which help you with saving your OTA zip if you plan to update to to 4.4.4 (only need to save it if your carrier's version isn't there already) or dump your current hboot if you plan on staying on 4.2.2.
blue74lion said:
Another issue now.
I've instaled Lyberty kernel and the only rom working is ClockWorkSenseless. Antoher rom's put the phone in bootloop and I cant do anything. The /system/bin folder is empty.
I want to go back to stock kernel and rom. How can i do that?
I'm on 4.2.2 S-off twrp 2.8.0.2
L.E. Solved. TWRP 2.8.0.2 was the problem. I put 2.7.0.0 and now I can see all the files.
Click to expand...
Click to collapse
Also, not sure where/why you got 2.7.0.0 on there, but as of 10/22 2.8.1.0 is the official version. Yes, the version of TWRP posted here on XDA is for KitKat devices, but the official builds from their website work fine on JB (4.2.2) devices.
I've tried to update to 4.4.2, but something is missing me. OTA didnt find nothing. What are the steps to following to update?
Software number is 1.10.401.8
Kernel version 3.4.10-g31cb4f3
Zara_UL pvt ship s-off
CID-VODAP021
HBOOT-2.20.0000
Flash a stock kernel via fastboot and flash a stock rom via twrp
Child's Play said:
Flash a stock kernel via fastboot and flash a stock rom via twrp
Click to expand...
Click to collapse
You'll also need to flash stock recovery.
-Duir- said:
You'll also need to flash stock recovery.
Click to expand...
Click to collapse
No he wanted to go back to a stock kernel and rom
Child's Play said:
No he wanted to go back to a stock kernel and rom
Click to expand...
Click to collapse
Oh, I thought what you posted was in response to getting the OTA update to work.
Still no working to update to 4.4.2. I followed this steps to back to stock:
http://forum.xda-developers.com/showpost.php?p=55850035&postcount=23
Can be an issue that my phone has CID Vodafone Australia and the stock is for Europe?