Database Info

[Q] need help flashing CWM on the latest 1.63.531.2 710RD mt4gs

and i went on this link below
[How To] Flash ICS ROMs with S-ON Unlocked
I'm assuming you have
•Fastboot set up as a PATH, or copied to the folder you are extracting boot.img to
•HTC Drivers installed
•Clockwork Recovery
i have the drivers installed but i dont know the path and its not giving me details and to make it easyier to me i put everything on my desktop so please help me out here cause im about to sell this device and buy myself a g2 or g2x or a samsung android phone i really like bulletproof rom installed bad all i need for help is get CWM on this phone then i can handle it from there thanks.

you can download rom manager from play and install cwm

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

You at least have to be unlocked and rooted. You're obviously not rooted, yet.

see
you see i got the bootloader unlocked but still have s-on and the other thread says i can still flash custom rom with s-on still on but you still need to flash cwm on it and its not letting me

crimedave1987 said:
you see i got the bootloader unlocked but still have s-on and the other thread says i can still flash custom rom with s-on still on but you still need to flash cwm on it and its not letting me
Click to expand...
Click to collapse
Have you pushed Superuser from a PC to the phone via USB? After that you can load CWM from ROM Manager.
Hastily spouted for your befuddlement

crimedave1987 said:
you see i got the bootloader unlocked but still have s-on and the other thread says i can still flash custom rom with s-on still on but you still need to flash cwm on it and its not letting me
Click to expand...
Click to collapse
Just being unlocked is not the same as being rooted. You need to be Unlocked AND rooted to install CWM through Root Manager. You're only half of that.

Coug76 said:
Have you pushed Superuser from a PC to the phone via USB? After that you can load CWM from ROM Manager.
Hastily spouted for your befuddlement
Click to expand...
Click to collapse
nope im having trouble doing that i need help on that part

With an unlocked bootloader I simply copy the fastboot and adb files, as well as whatever recovery image I want to flash and push the recovery via fastboot... however if you aren't confident in your skills with the command prompt or fastboot there is always the all-in-one toolkit for the MT4GS that can be downloaded from its own thread in the dev forums (I don't have the link handy but it seemed to work for me on my sister's mt4gs).

I'm having trouble flashing CWM from the market as well. I've rooted (or at least I think I have) via Hasooon2000's tool and the superuser icon shows up in my drawer but when I try to run it I'm never prompted with the usual permission request, just the permission error that OP posted. I am also unable to install anything like Busybox or ROM Toolbox. It seems like the root just wasn't properly set up but none of the methods I've found actually work. I have tried to redo the rooting process, but to no avail.
I flashed CWM from Hasoon200's tool too, and can boot into it, however when I try to take a backup it just goes to a screen with the CWM logo in it and doesn't do anything. I have to pull the battery to get it to reboot.
Never had this much trouble with rooting or flashing a recovery before, but if anyone can help I'd appreciate it.

I'd say do a flash of CWM via adb. Then install Superuser through CWM using a zipped Superuser. Worked flawlessly for me.

yupThisIsMyName said:
I'm having trouble flashing CWM from the market as well. I've rooted (or at least I think I have) via Hasooon2000's tool and the superuser icon shows up in my drawer but when I try to run it I'm never prompted with the usual permission request, just the permission error that OP posted.
I flashed CWM from Hasoon200's tool too, and can boot into it, however when I try to take a backup it just goes to a screen with the CWM logo in it and doesn't do anything. I have to pull the battery to get it to reboot.
Never had this much trouble with rooting or flashing a recovery before, but if anyone can help I'd appreciate it.
Click to expand...
Click to collapse
Are you using the trackpad to select things in recovery? All of my other phones used power while in recovery to select things but the doubleshot uses trackpad to select
Sent from my myTouch_4G_Slide using Tapatalk 2

I'm of two different schools of thought here - my first thought is bad download of CWM... Honestly I'd just read up on fastboot flashing the recovery image and do that to ensure a good root. However as noted above the trackpad select did throw me off at first.
Sent from my myTouch_4G_Slide using XDA

OK, it looks like I don't actually have S-Off and I've got the newer Hboot which, from what I can tell, prevents me from using this method and the only two ways to do this seem to involve either doing some crazy stuff with wires or flashing stuff without taking a backup first. Both of these methods make me very nervous, especially since as far as I can tell there is no way to use anything like Odin or RSD Lite with this phone to restore it in case something gets messed up.
If anyone has a way I can take a backup before flashing a ROM or, better yet, has a way to restore the phone completely in case something goes awry that would be awesome.

Update: Yeah, looks like it was the trackpad thing preventing me from doing this properly. Totally bizarre considering the fact that I was able to select things just fine using the volume buttons but when I hit power (which selects on most devices), it didn't work right.
Thanks for helping me get past this hurdle everyone! Hopefully I can figure out how to get s-off.
Edit: Update - I flashed a ROM that already had root and now that works too. Good enough for now, I'll wait for a less scarey method to get S-off. I'm not about to start messing around with wires.

[Guide / Tool][10/15/12] - Update to Official Jellybean Then Root or Custom ROM!

I wrote this guide do to the general lack of information for users about the Jellybean update. This guide is basic in nature and will provide you with all the tools and links you need to update from an ICS based ROM to the official JB ROM then re-root or prepare for custom ROM.
If you already have the Official JB Update simply unlock it and proceed to Section #2. This guide was intially intended for those who cannot update because of Asus stupid lock out program once you unlock.
Warning
I have tested this guide on my device multiple times and never have one single issue. I cannot say it will work perfect for you! I am not responsible for anything that goes wrong including but not limited to; A $500 brick! The economy imploding worse, Nuclear war, End of the world on 12/12/12!
Pre-requisites
Unlocked bootloader
Custom Recovery
Any version of TF700T
Windows 7 or Windows 8 PC
General Overview
Flash Asus JB update
Flash TWRP 2.2.3
Flash SuperSU or Custom ROM
Profit!
Please do not be afraid to ask for help!
This guide was written for people who need help. I didint write it for myself because I already know how to do it, lol
Donations gratefully accepted but never expected!
Please hit Thanks and Rate the thread 5 Stars
Click to expand...
Click to collapse
-Scott

Section 1 - Flash Asus JB update
Obtain the appropriate Jellybean update from the Asus Support Site HERE
Go to Downloads and pick the local / region specific update file for your device. For the intent of this guide I will focus on the US Based variant but all other devices will follow the exact same steps.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After you download the Jellybean update you must extract the zip file in the zip (I dont know why they did this!). The name of the first zip file will be "US_epad_user_10_4_4_16_UpdateLauncher.zip"
The zip file inside of that will be "US_epad-user-10.4.4.16.zip" This is the file we will flash to update to JB!
To do this open the first zip file with your zip [rogram of choice, (as you can see I use 7zip) and pull out the only other zip file in there (US_epad-user-10.4.4.16.zip).
Once you have that file copy it to you internal SD card. Although, untested, external SD should work too.
Now.... Reboot to recovery. To do this power down the device, and then Hold Volume Down and then press power untill you get a menu that says press XX key to boot to recvoery.
Once in recovery you MUST wipe data before you continue!
Now flash the ROM file you just copied like it was a plain old fashioned custom ROM or Root.zip. Just select it and flash!
Once the flash is done reboot. Dont be scared... This will take a LONG time... Maybe in upwards of 3 to 5 minutes. This is normal. Its completely rebuilding the device!
Once the device is all booted up and you are at your desktop we can proceed to Section 2.

Section 2 - Flash TWRP 2.2.2.3
First we need to obtain TWRPREcovery. You are free to use any version you want, including ClockworkMod (although I highly discourage CWM and recomend TWRP).
You can find TWRP HERE. Remember I recommend the 2.2.2.3 version. 2.3.0.0 gave me some issues.
Now that you have the file download you need to rename it to "recovery.blob" for use with my tool!
Now download the attached tool and unzip it. It contains the fastboot and ADB files you will need to flash the recovery.
Next place the recovery.blob in the folder
Turn on USB Degging in the developer menu of the device. This is very important otherwise you will be just sitting there forever, lol
Now initiate the "Recovery Install Tool.bat" file. This will reboot you to bootloader and flash the recovery for you ;c)
Done!

Section 3 - Flash SuperSU or Custom ROM
Needless to say I am partial to custom ROMS ;c) But I know some may be content with just flashing root so I will show you how to obtain the correct root file and or ROM and give a brief over view on how to flash them. This section will be pretty routine and will not contain a lot of new info for most of you!
Obtain my favorite root app, SuperSU, from HERE
Copy to storage
Reboot to recovery
Flash and Be rooted!
Same steps for a custom ROM. The best Custom ROM can be found HERE! ;c)

Section 4 - Thanks!
Thanks to Dess_troy for making TWRP for our devices!
Thanks to Chainfire for the root app!
Thanks to all the Developers on XDA that have taught me (in one way or another) everything I know!
Special Thanks to all the CleanROM users who have inspired me to push CleanROM to be the premier custom ROM for your Android Device!

Please feel free to rebuild this for the Linux or Mac platform and re-distrubute!

So, the very first step is unlocking the bootloader, correct?
Sent from my S2 Skyrocket using XDA app

scrosler said:
Pre-requisites
Unlocked bootloader
Custom Recovery
Any version of TF700T
-Scott
Click to expand...
Click to collapse
A number of people have asked and I have usually replied that it is possible to use the Asus provided UnLock tool - the one on the website that says is only compatible with ICS - with a tablet that has been updated to JB.
In short the Unlock tool works in Jellybean!
You might want to add this as an addendum to your original post.
Cheers,
Eric

i apologize for my beligerant question but if i want to try the new cwm touch recovery, do i just rename it to recovery.blob? when i downloaded it it was the usual iso. when renamed it didnt change anything so i dont wanna brick my tab. figured id ask first. thanks for the awesome walk through tho man. i really apreciate it. loving your roms. have 2.0 downloaded already. also can you pm the link to your tf300 kernel you used? i need to show off some high quadrant numbers lol

Confused...
How do I get a custom recovery on my tablet before this whole process? I've read thru some threads, do I need to be rooted first on ICS before starting this process of updating to JB? I'm not getting the official ASUS JB OTA...I've checked for the update about 500 times, I'm just not getting it.
At this point, I have an unlocked but unrooted, and wiped stock TF700T on ICS. Whats my next step?

BlastTyrantKM said:
So, the very first step is unlocking the bootloader, correct?
Sent from my S2 Skyrocket using XDA app
Click to expand...
Click to collapse
BlastTyrantKM said:
How do I get a custom recovery on my tablet before this whole process? I've read thru some threads, do I need to be rooted first on ICS before starting this process of updating to JB? I'm not getting the official ASUS JB OTA...I've checked for the update about 500 times, I'm just not getting it.
At this point, I have an unlocked but unrooted, and wiped stock TF700T on ICS. Whats my next step?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
This guide is for people who have already unlocked there device any may have had a custom ROM installed pre-JB.
You fall into a unique and rather off situation. I have never heard of some one not getting the OTA.
You could follow these steps but as a pre-step...
Download and unlock with the Asus unlock tool. Its on the same download page.
Download an ICS based recovery and use that in in place of the one noted for now. And then just start at Section 2. Then start back over at Section 1.
Basically we will put a recovery on your device in Section 2. Then start over at step 1 by applying the JB build then put a recovery back on, as it gets wiped off by Asus builds and your all set.

So I got the OTA JB update from Asus. I unlocked the boot loader using the Asus app. I downloaded and extracted US_epad-user-10.4.4.16.zip then threw it on the insternal SD card ( /storage/sdcard0 ). I rebooted with the volume key press and selected recovery. It gave me a message saying "booting recovery kernel". The next thing I see is an android on his back with a red exclamation sign.
What am I doing wrong?

beowolfschaefer said:
So I got the OTA JB update from Asus. I unlocked the boot loader using the Asus app. I downloaded and extracted US_epad-user-10.4.4.16.zip then threw it on the insternal SD card ( /storage/sdcard0 ). I rebooted with the volume key press and selected recovery. It gave me a message saying "booting recovery kernel". The next thing I see is an android on his back with a red exclamation sign.
What am I doing wrong?
Click to expand...
Click to collapse
The stock recovery will only flash firmware zips with a certain name. Rename the zip to EP201_768_SDUPDATE.ZIP and try again.

I upgraded to jb firmware and lost root. My 700T is unlocked. I thought I followed the procedure correctly but I did not get the message correct message when I ran the program. My device is not rooted. Can you tell me what I might be doing wrong.

yes you lose root. this will make your tf700 like the factory jellybean firmware which is not rooted. go back to op and keep reading. each section builds on the previous. first get the jellybean firmware. im still playing with mine stock its so damn smooth. then you flash a custom recovery using his tool. then you flash the zip which gives you root. then i would make a back up so you can always get back to that point. then you can look into custom roms like scotts sweet clean rom for tf700 series
joseph473 said:
I upgraded to jb firmware and lost root. My 700T is unlocked. I thought I followed the procedure correctly but I did not get the message correct message when I ran the program. My device is not rooted. Can you tell me what I might be doing wrong.
Click to expand...
Click to collapse

beowolfschaefer said:
So I got the OTA JB update from Asus. I unlocked the boot loader using the Asus app. I downloaded and extracted US_epad-user-10.4.4.16.zip then threw it on the insternal SD card ( /storage/sdcard0 ). I rebooted with the volume key press and selected recovery. It gave me a message saying "booting recovery kernel". The next thing I see is an android on his back with a red exclamation sign.
What am I doing wrong?
Click to expand...
Click to collapse
If you have the JB Update why ware you trying to install it again? Proceed to section #2. You just need the Recovery and the Root portion. Skip step 1.
joseph473 said:
I upgraded to jb firmware and lost root. My 700T is unlocked. I thought I followed the procedure correctly but I did not get the message correct message when I ran the program. My device is not rooted. Can you tell me what I might be doing wrong.
Click to expand...
Click to collapse
To me it looks like you are trying to run the batch file without extracting the contents.

Thank you for this guide! Although it took me some time to understand it as I was on non-rooted/locked JB stock rom.
---------- Post added at 01:34 PM ---------- Previous post was at 01:29 PM ----------
scrosler said:
If you have the JB Update why ware you trying to install it again? Proceed to section #2. You just need the Recovery and the Root portion. Skip step 1.
Click to expand...
Click to collapse
I actually had similar problem as this guy. I was already on JB and the guide is made for people that are on ICS.

scrosler said:
To me it looks like you are trying to run the batch file without extracting the contents.
Click to expand...
Click to collapse
I am using a borrowed PC. I am a Mac user so forgive my ignorance. But when I look at the folder with Scott's Tool in it it looks like everything is extracted.

scrosler said:
If you have the JB Update why ware you trying to install it again? Proceed to section #2. You just need the Recovery and the Root portion. Skip step 1.
Click to expand...
Click to collapse
I actually tried this last night with no luck. I guess it was something funny with my desktop in that it couldn't connect using fast boot. Anyway I brought it in to work and ran it here and everything is fine. I am going to throw your stock/root rom on it now. Thanks for your help!

CWM-SuperSU-v0.96.zip
Hello,
thanks a lot for the guide, it is really clear and detailed.
My question is something I did not find on the previous question and it is more a double check to be sure I am not doing something I should not.
You say to install SU with the package copied on the internal SD, and you added a link to the SU thread. in this thread, the only SU as a package you can find is CWM-SuperSU-v0.96.zip, as it is CWM, will it work if I install it with TWRP? or there is special settings in this package that will not be recognised by TWRP?
Thanks in advance for your help
Regards

S4 T-Mobile + 4.3 = "there is no su binary installed and supersu can not install it.

S4 T-Mobile + 4.3 = "there is no su binary installed and supersu can not install it.
Did ODIN, then CFRoot (CF-Auto-Root-jfltetmo-jfltetmo-sghm919), SuperSu fails with "There is no SU binary installed and SuperSU cannot install it"...
Anyone had luck getting SuperSU wrking on 4.3?

no, there's no working root at this time.
Sent from my GT-I9505 using Tapatalk 4 Beta

Thank you for the info.
I have to say this, the speed improvement on 4.3 is very noticeable. I am back to CM10.1 and it feels slow in comparison...
beaver2233 said:
no, there's no working root at this time.
Sent from my GT-I9505 using Tapatalk 4 Beta
Click to expand...
Click to collapse

dotpage said:
Thank you for the info.
I have to say this, the speed improvement on 4.3 is very noticeable. I am back to CM10.1 and it feels slow in comparison...
Click to expand...
Click to collapse
How did you get back to CM10.1?

AlAmeri said:
How did you get back to CM10.1?
Click to expand...
Click to collapse
Flash it using a custom recovery
Me Gusta!

Me Gusta said:
Flash it using a custom recovery
Me Gusta!
Click to expand...
Click to collapse
So flashing ROM without root is possible?

AlAmeri said:
So flashing ROM without root is possible?
Click to expand...
Click to collapse
Directly from Android, no. You'll need root to do that. Just power off your device, when its turned off press and hold volume up, home and power at the same time. Flash from recovery.

fcknghst said:
Directly from Android, no. You'll need root to do that. Just power off your device, when its turned off press and hold volume up, home and power at the same time. Flash from recovery.
Click to expand...
Click to collapse
So Android 4.3 without root. I have a costume recovery, CWM, I could simply just flash a new ROM and it wouldn't brick my S4?
Sorry for the newbie questions but I'm coming from zero experience.

AlAmeri said:
So Android 4.3 without root. I have a costume recovery, CWM, I could simply just flash a new ROM and it wouldn't brick my S4?
Sorry for the newbie questions but I'm coming from zero experience.
Click to expand...
Click to collapse
Yup. Just do a wipe and flash whatever you like. As long as you have access to bootloader, and keep a backup it is very hard to brick your phone - Im new to samsung, but as i understand with Odin it is even harder to brick it.
On a side note, i had some issues getting it to mount /system - Turns out that it cant if the phone is plugged into the computer (i did a facepalm after trying ~3hours getting it to flash CM )

fcknghst said:
Yup. Just do a wipe and flash whatever you like. As long as you have access to bootloader, and keep a backup it is very hard to brick your phone - Im new to samsung, but as i understand with Odin it is even harder to brick it.
On a side note, i had some issues getting it to mount /system - Turns out that it cant if the phone is plugged into the computer (i did a facepalm after trying ~3hours getting it to flash CM )
Click to expand...
Click to collapse
The thing is I backed up my old system before I flashed Android 4.3. Now CWM cant access the directory. I'm afraid if it can't access the directory then it wont be able to flash properly and I will for ever be stuck on bootloop.

AlAmeri said:
The thing is I backed up my old system before I flashed Android 4.3. Now CWM cant access the directory. I'm afraid if it can't access the directory then it wont be able to flash properly and I will for ever be stuck on bootloop.
Click to expand...
Click to collapse
So you cant restore your backup, from before 4.3?

fcknghst said:
So you cant restore your backup, from before 4.3?
Click to expand...
Click to collapse
Exactly. I tried searching for stock firmware, couldn't find one. So I thought either I find a way to restore. Or flash an already rooted ROM. You see my dilemma.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
dotpage said:
Did ODIN, then CFRoot (CF-Auto-Root-jfltetmo-jfltetmo-sghm919), SuperSu fails with "There is no SU binary installed and SuperSU cannot install it"...
Anyone had luck getting SuperSU wrking on 4.3?
Click to expand...
Click to collapse

Use Odin to reload TWRP, it happened to me too... Put phone in Download mode, use PDA option pointing to TWRP's file...
AlAmeri said:
The thing is I backed up my old system before I flashed Android 4.3. Now CWM cant access the directory. I'm afraid if it can't access the directory then it wont be able to flash properly and I will for ever be stuck on bootloop.
Click to expand...
Click to collapse

dotpage said:
Use Odin to reload TWRP, it happened to me too... Put phone in Download mode, use PDA option pointing to TWRP's file...
Click to expand...
Click to collapse
But I don't have TWRP. I use a CWM based recovery.
How does it work?
So I flash TWRP using odin, and then what?

AlAmeri said:
But I don't have TWRP. I use a CWM based recovery.
How does it work?
So I flash TWRP using odin, and then what?
Click to expand...
Click to collapse
In any case - Back up your current (working) installation - There will be a way to get root in the future. Now you dont have to worry about not being able to use the phone (since you have a working backup), and you can goahead and flash something else.
Dont bother installing different recoveries, they all work just fine - And TWRP wont be able to restore from a CWM backup anyways..
But I dont understand why CWM cannot access your former backup.

fcknghst said:
In any case - Back up your current (working) installation - There will be a way to get root in the future. Now you dont have to worry about not being able to use the phone (since you have a working backup), and you can goahead and flash something else.
Dont bother installing different recoveries, they all work just fine - And TWRP wont be able to restore from a CWM backup anyways..
But I dont understand why CWM cannot access your former backup.
Click to expand...
Click to collapse
That's actually genius. Don't know why I haven't thought of it earlier. Backup and experiment.
Thanks.
Chainfire is taking longer than usual. Its got me worried. I'm loving Stock Android, going to try flashing 4.2.2. Hopefully won't run into trouble.

If you find 4.2.2 vanilla(T-Mobile) let us know, I am looking for that ROM....
AlAmeri said:
That's actually genius. Don't know why I haven't thought of it earlier. Backup and experiment.
Thanks.
Chainfire is taking longer than usual. Its got me worried. I'm loving Stock Android, going to try flashing 4.2.2. Hopefully won't run into trouble.
Click to expand...
Click to collapse

dotpage said:
Did ODIN, then CFRoot (CF-Auto-Root-jfltetmo-jfltetmo-sghm919), SuperSu fails with "There is no SU binary installed and SuperSU cannot install it"...
Anyone had luck getting SuperSU wrking on 4.3?
Click to expand...
Click to collapse
dont know if this will work for you but here goes. i have a T999L (T-Mobile LTE S3) i have twrp installed on it and i have slimbean 4.3 official build installed on it, i had the same issue with getting 4.3 rooted but i got it figured out first make sure in the developer options you have superuser allowed by adb and apps.
( if you don't see developer options in your settings menu
go to :Settings>About Phone> click on your build number several times until you get a toast that says your almost a developer keep clicking until it says it has been enabled)
then you will use motoChopper to push the exploit to get the superuser.apk added to the system/apps folder once you do this it won't work as they have somehow allowed access for the expoit to push the .apk but not push the binary to the system/xbin folder.
now pull the SU binary out of the motoChopper folder on your computer and place in on your sdcard
boot into TWRP, mount the file system and copy it from your sdcard to the system/xbin folder and voila you are done, when you go to reboot your device from TWRP it will ask you if you want to fix the Superuser permissions just skip and reboot
( all rights thanks and so on go to the original developer djrbliss and i do not take any credit for his work, nor did i get permission to modify his work, i tried but got no response so i modded it for myself to use and i am now sharing, all i did was swap the Superuser.apk and SU binaries he used in his exploit.) @djrbliss if you would like this post removed just let me know and i will pull it!
not sure why the list showed up as 1 1 1 2 but i think you get the point

[SOLVED] Can't update further (3.4 kernel)

Hello everyone,
I had installed CM10.1 some time ago, everything was good except some Wi-Fi problems which I somehow fixed with Bubba kernel. I decided to update my build after staying for a long time on the same one. So I downloaded the latest CM10.1 nightly, went on to install it, only to get surprised by a red sign on the recovery screen saying that the kernels don't match or is not compatible (or something similar). So I searched around to find a way to update my kernel but I was very confused with the guides I found, and as a result, I turned to TrickDroid with Sense 5, which I'm currently on.
It's time now to update again but I'm still confused about the whole thing. I have no idea where to start and that's the reason you're reading this thread right now.
My hboot is 1.13 and my baseband 0.16 (Europe). Also, I'm S-On and not SuperCID-ed.

Chris95X8 said:
Hello everyone,
I had installed CM10.1 some time ago, everything was good except some Wi-Fi problems which I somehow fixed with Bubba kernel. I decided to update my build after staying for a long time on the same one. So I downloaded the latest CM10.1 nightly, went on to install it, only to get surprised by a red sign on the recovery screen saying that the kernels don't match or is not compatible (or something similar). So I searched around to find a way to update my kernel but I was very confused with the guides I found, and as a result, I turned to TrickDroid with Sense 5, which I'm currently on.
It's time now to update again but I'm still confused about the whole thing. I have no idea where to start and that's the reason you're reading this thread right now.
My hboot is 1.13 and my baseband 0.16 (Europe). Also, I'm S-On and not SuperCID-ed.
Click to expand...
Click to collapse
Why not flash the boot.img from the New Build.zip as you are S-ON?

khan.orak said:
Why not flash the boot.img from the New Build.zip as you are S-ON?
Click to expand...
Click to collapse
Obviously I tried that with no luck.
But here's the thing. The CM thread says "you need to update your firmware to use the 3.4x kernel click me". I followed the tutorial provided and the update did not work. That's where I'm stuck.

Chris95X8 said:
Obviously I tried that with no luck.
But here's the thing. The CM thread says "you need to update your firmware to use the 3.4x kernel click me". I followed the tutorial provided and the update did not work. That's where I'm stuck.
Click to expand...
Click to collapse
Aahhh yess
Can you just run an RUU from your carrier? That's a one-stop solution: will upgrade your firmware and HBOOT and you should be good to go.
Sent from my HTC One S using Tapatalk 4 Beta

Can you guide me please?
I found a page with a bunch of RUUs but I don't know which one to run. Also, my One S was carrier locked but I unlocked it by following a tutorial I found in the forum. Does that mean I should run a carrier RUU?
Sent from my HTC One S using Tapatalk 4

Chris95X8 said:
Can you guide me please?
I found a page with a bunch of RUUs but I don't know which one to run. Also, my One S was carrier locked but I unlocked it by following a tutorial I found in the forum. Does that mean I should run a carrier RUU?
Sent from my HTC One S using Tapatalk 4
Click to expand...
Click to collapse
Okay. Sure.
First, You will have to tell me your CID. You can find that out by getting CID GETTER from play store. It should tell you your CID in RED color.
Also, you run the RUU, it will upgrade you plus get you on stock, afterwards, IF it is locked again, you can unlock it and flash CM latest nightlies again. So no biggie there.

Hey thank you very much for your time.
The app says my CID is H3G_001
Sent from my HTC One S using Tapatalk 4

Chris95X8 said:
Hey thank you very much for your time.
The app says my CID is H3G_001
Sent from my HTC One S using Tapatalk 4
Click to expand...
Click to collapse
I suppose that is Three (3) UK .
Okay, I found that there is no JellyBean RUU for your carrier. Same as they did with HTC One X.
But here's the deal, after relocking your bootloader, you can use This RUU which is an ICS RUU.
It will bring you to Stock ICS without changing your HBOOT and firmware. Afterwards, you should check for System Updates and receive JellyBean OTA. So that will take you to JellyBean + 2.15.0000 HBOOT + Newer Firmware.

OK so if I get it right... I lock my bootloader, run that RUU which will bring me back to ICS, update through OTA (does that work everywhere?) and then just do the rooting and recovery stuff again and install the latest CM build. Alright, I'll give it a shot!
Sent from my HTC One S using Tapatalk 4

Chris95X8 said:
OK so if I get it right... I lock my bootloader, run that RUU which will bring me back to ICS, update through OTA (does that work everywhere?) and then just do the rooting and recovery stuff again and install the latest CM build. Alright, I'll give it a shot!
Sent from my HTC One S using Tapatalk 4
Click to expand...
Click to collapse
Yeah, that's right.
Yes, udpdate through WiFi as it is a big update to JB OTA. works everywhere.
---------- Post added at 05:12 PM ---------- Previous post was at 05:10 PM ----------
Chris95X8 said:
OK so if I get it right... I lock my bootloader, run that RUU which will bring me back to ICS, update through OTA (does that work everywhere?) and then just do the rooting and recovery stuff again and install the latest CM build. Alright, I'll give it a shot!
Sent from my HTC One S using Tapatalk 4
Click to expand...
Click to collapse
Also, I'll advise that you do a complete backup after you update to JellyBean, as I can see no JellyBean RUU/OTA for your carrier. So in case of any problems, you can restore NANDroid backups.
So, after JB update, flash a custom recovery (TWRP 2.3.3.0 preferable), before rooting and any other stuff, do a complete backup of BOOT+SYSTEM.

khan.orak said:
Also, I'll advise that you do a complete backup after you update to JellyBean, as I can see no JellyBean RUU/OTA for your carrier. So in case of any problems, you can restore NANDroid backups.
So, after JB update, flash a custom recovery (TWRP 2.3.3.0 preferable), before rooting and any other stuff, do a complete backup of BOOT+SYSTEM.
Click to expand...
Click to collapse
You see, I got this One S from the UK locked to Three but I live elsewhere, so I unlocked with a method I found on the forums. Does the process change at all?

Chris95X8 said:
You see, I got this One S from the UK locked to Three but I live elsewhere, so I unlocked with a method I found on the forums. Does the process change at all?
Click to expand...
Click to collapse
nope. I think you should be able to unlock it using This method IF it locks after the update.
But before doing any stuff (unlocking, rooting etc), make nandroid backups of the new JB ROM. People have to strive really hard in absence of RUU, OTA.zip and NANDroids.

khan.orak said:
nope. I think you should be able to unlock it using This method IF it locks after the update.
But before doing any stuff, make nandroid backups. People have to strive really hard in absence of RUU, OTA.zip and NANDroids.
Click to expand...
Click to collapse
That's how I did it :laugh:

Chris95X8 said:
That's how I did it :laugh:
Click to expand...
Click to collapse
Great. shouldn't be a problem then.

khan.orak said:
So, after JB update, flash a custom recovery (TWRP 2.3.3.0 preferable), before rooting and any other stuff, do a complete backup of BOOT+SYSTEM.
Click to expand...
Click to collapse
From what I see, TWRP needs root to install now (with the GooManager app). When I first installed it, I did it with a fastboot command since the recover was an image file.

Chris95X8 said:
From what I see, TWRP needs root to install now (with the GooManager app). When I first installed it, I did it with a fastboot command since the recover was an image file.
Click to expand...
Click to collapse
what recovery do you have right now?

khan.orak said:
what recovery do you have right now?
Click to expand...
Click to collapse
TWRP actually. But it's ok, I found this. I thought the RUU would restore the HTC recovery.
Why do you suggest 2.3.0.0 though? Can't I update to the latest one (2.6)?

Chris95X8 said:
TWRP actually. But it's ok, I found this. I thought the RUU would restore the HTC recovery.
Click to expand...
Click to collapse
If you want to root your device, just flash a flashable SuperSU.zip from recovery. Instant root.
---------- Post added at 03:44 PM ---------- Previous post was at 03:39 PM ----------
Chris95X8 said:
TWRP actually. But it's ok, I found this. I thought the RUU would restore the HTC recovery.
Why do you suggest 2.3.0.0 though? Can't I update to the latest one (2.6)?
Click to expand...
Click to collapse
actually, I have been having issues with 2.6.0.0 flashing Carbon ROM. PACman worked fine. Can't say anything. Both worked okay with 2.3.3.0. You may give the latest a try.

Ughhh what the hell is this now. The RUU can't run.
I locked the bootloader, went on to run the RUU and this happened...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Chris95X8 said:
Ughhh what the hell is this now. The RUU can't run.
I locked the bootloader, went on to run the RUU and this happened...
Click to expand...
Click to collapse
Oh. Just yesterday, some folks reported unsuccessful and corrupt RUU downloads from androidruu site.
You may use this one Here

[Q] Flash Stock and Unroot without USB possible? [SOLVED]

Hello Nexus friends!
Hope someone can help me:
Is there a way to flash my nexus 5 back to stock and unroot without USB?
I think my USB port is dead, it doesnt load and I m not able to connect it with any computer. I wiped it but nothing changed.
History:
I flashed and rooted my phone with Nexus Root Toolkit from stock (4.4.2 (KOT49H) i think) now after OTA updates its runnig 4.4.4 (KTU84P).
plz help!
regards
Mike

You could flash a stock recovery flashable ROM....would need root for that obviously.
As far as flashing stock recovery....not sure about that one. Maybe flashify can help? Never used it myself. You need a flashable stock recovery tho.
Also, the boot loader will be unlocked still, so that's kind of a dead giveaway. Nothing you can do about that without connecting to a computer for fastboot.

Need to know the full situation.
If you've lost root you NEED a custom recovery. If you have stock recovery, you NEED root.
OTA removes root and custom recovery.
Please give situation report.
Sent from my Nexus 5 using Tapatalk

rootSU said:
Need to know the full situation.
If you've lost root you NEED a custom recovery. If you have stock recovery, you NEED root.
OTA removes root and custom recovery.
Please give situation report.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
OTA removes ROOT? Didnt know that...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So now my Phone is unrooted and stock? SuperSU says its not installed but i have the app icon...?

Ok so you're stock unrooted. What recovery have you got?
Sent from my Nexus 5 using Tapatalk

rootSU said:
Ok so you're stock unrooted. What recovery have you got?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Is there a way to read the header of the .ab files?
01-17-2014_13-37.ab (should be Stock 4.4.2 (KOT49H))
But I dont think its unrooted
I want back to stock ROM, RECOVERY, BOOTLOADER... to send it back for warranty repair of the USB port!
Thank you for your efforts!

w1m9 said:
Is there a way to read the header of the .ab files?
01-17-2014_13-37.ab (should be Stock 4.4.2 (KOT49H))
But I dont think its unrooted View attachment 2857791
I want back to stock ROM, RECOVERY, BOOTLOADER... to send it back for warranty repair of the USB port!
Thank you for your efforts!
Click to expand...
Click to collapse
I can walk you through it but I need to know for definite your current situation.
I need you to have either root, or a custom recovery.
To check custom recovery, hold vol down + power to boot to bootloader. Then use Volume up / down to navigate to "recovery" and press power to select. I want to see the recovery screen. Usually OTA will remove root and custom recovery.
Also, use root checker to check if you have root - I expect you will not have it.
First install SuperSU
https://play.google.com/store/apps/details?id=eu.chainfire.supersu
Then install root checker
https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck

rootSU said:
I can walk you through it but I need to know for definite your current situation.
I need you to have either root, or a custom recovery.
To check custom recovery, hold vol down + power to boot to bootloader. Then use Volume up / down to navigate to "recovery" and press power to select. I want to see the recovery screen. Usually OTA will remove root and custom recovery.
Also, use root checker to check if you have root - I expect you will not have it.
First install SuperSU
Then install root checker
Click to expand...
Click to collapse
OK u r right!! It is not rooted... here my recovery

w1m9 said:
OK u r right!! It is not rooted... here my recovery View attachment 2857903
Click to expand...
Click to collapse
OK This means you have full stock rom and stock recovery. Only thing you have that you might not want is an unlocked bootloader, which you need root to fix. Do you want me to "Try" to and help you do tht or are you just going to leave it?
Are you sending it to google or LG?

rootSU said:
OK This means you have full stock rom and stock recovery. Only thing you have that you might not want is an unlocked bootloader, which you need root to fix. Do you want me to "Try" to and help you do tht or are you just going to leave it?
Are you sending it to google or LG?
Click to expand...
Click to collapse
Would be very nice if u help me!!! Do you think its possible without USB?
I dont know if I have to send it back to google or LG? I bought it over the play store from Germany to Austria!
I think my warranty is lost if I send it back with the open bootloader... am I right?
regards

w1m9 said:
Would be very nice if u help me!!! Do you think its possible without USB?
I dont know if I have to send it back to google or LG? I bought it over the play store from Germany to Austria!
I think my warranty is lost if I send it back with the open bootloader... am I right?
regards
Click to expand...
Click to collapse
Google will not reject warranty of hardware failure due to unlocked bootloader. LG might. If you bought it from google, it usuall goes to google, but not sure if changign country changes things. Best to ask google.
Only chance to lock bootloader is to get root by using towelroot. It may or may not work.
https://towelroot.com/tr.apk
Run the app. It is supposed to reboot but sometimes it does not. If it does not, reboot yourself. Then ipen SuperSU and check if it has root.
If it does have root, install bootunlocker https://play.google.com/store/apps/details?id=net.segv11.bootunlocker&hl=en - and reset tamper flag and lock bootloader. Then unroot using SuperSU.
If towelroot doesnt give you root, you cannot lock bootloader

rootSU said:
Google will not reject warranty of hardware failure due to unlocked bootloader. LG might. If you bought it from google, it usuall goes to google, but not sure if changign country changes things. Best to ask google.
Only chance to lock bootloader is to get root by using towelroot. It may or may not work.
https://towelroot.com/tr.apk
Run the app. It is supposed to reboot but sometimes it does not. If it does not, reboot yourself. Then ipen SuperSU and check if it has root.
If it does have root, install bootunlocker https://play.google.com/store/apps/details?id=net.segv11.bootunlocker&hl=en - and reset tamper flag and lock bootloader. Then unroot using SuperSU.
If towelroot doesnt give you root, you cannot lock bootloader
Click to expand...
Click to collapse
Thank u man! U r the best! Everything worked well.

w1m9 said:
Thank u man! U r the best! Everything worked well.
Click to expand...
Click to collapse
No problem.
Sent from my Nexus 5 using Tapatalk

You can flash stock recovery via the TWP app, which allows this
#64268gkyJL#8653%dhjGUKVS357.

howard bamber said:
You can flash stock recovery via the TWP app, which allows this
#64268gkyJL#8653%dhjGUKVS357.
Click to expand...
Click to collapse
He already had stock recovery.
Sent from my Nexus 5 using Tapatalk

want to roll back to original one..
currently i have cyanogen recovery .i wanted get back to the original software(ie, same as the nexus 5 out of the box(which is not rooted and can get os updates from google(OTA)).can u please suggest me the procedure required for it???