Database Develop

[How to] Root from stock 4.2.x in 1 minute

Since I've seen many people downgrade to 4.1.2 just to use unsecure kernel first and root then upgrade to 4.2 and some still wonder how to install root on latest stock android, here's easy steps for you:
1. Let's say you have just installed factory image from Google. You don't need unsecure kernel. Download SuperSU Binary for CWM to your tablet.
2. Reboot to bootloader (adb reboot bootloader)
3. Type: fastboot flash recovery xxxxxx.img (where xxxxxx.img will be the filename of your favorite recovery. I choose CWM Touch since it's working good)
4. Boot to recovery and install SuperSU Binaries.
5. Reboot and you are done! Now you have fully working root without modified unsecure kernel fast and easy.
Note: tested it twice and it works. Hope this clears some questions.
Hit thanks if that helped you.
Have a nice evening!
Edit: Works for all android versions.

Actually, you forgot to mention unlocking the bootloader.

OK...so I will still get OTA updates?

I can beat that
Code:
fastboot boot superboot.img
Wait for the bootanimation (the colorfull X) to show up, reboot (by holding the power button till it reboots if it got stuck at the anim) - DONE

mrao said:
OK...so I will still get OTA updates?
Click to expand...
Click to collapse
Fotakill.apk

mrao said:
OK...so I will still get OTA updates?
Click to expand...
Click to collapse
Yes unless you change any system apps or odex files.... If you don't want ota updates install from market fotakill.apk
I am not so sure about using adb commands etc I use the root kits and these work fine on 4.2 and 4.2.1
Sent from my LT15i using xda premium

Declan.Gao said:
Actually, you forgot to mention unlocking the bootloader.
Click to expand...
Click to collapse
Of course you must have unlocked bootloader first, as well as usb debugging if you wanna reboot via adb.
HellcatDroid said:
I can beat that
Code:
fastboot boot superboot.img
Wait for the bootanimation (the colorfull X) to show up, reboot (by holding the power button till it reboots if it got stuck at the anim) - DONE
Click to expand...
Click to collapse
This is not a competition. Just quick help for users.
mrao said:
OK...so I will still get OTA updates?
Click to expand...
Click to collapse
As long as you stay stock - yes.

Jack Barrett said:
This is not a competition. Just quick help for users.
Click to expand...
Click to collapse
Sorry Sir, usually UK folks carry a certain sense of humor with them.
Shall I undo (delete) my posting?

Cool...thanks...what i meant was that I wanted the OTA updates...that answers it..thanks

Jack Barrett said:
3. Type: fastboot flash recovery xxxxxx.img (where xxxxxx.img will be the filename of your favorite recovery. I choose CWM Touch 6.0.1.9 since it's working good)
Click to expand...
Click to collapse
My 2 cents:
sudo fastboot flash recovery xxxxxx.img
I was frustrated "Waiting for device ..."

linuxwarrior said:
My 2 cents:
sudo fastboot flash recovery xxxxxx.img
I was frustrated "Waiting for device ..."
Click to expand...
Click to collapse
1. Driver problems (sudo? I bet you use linux) or
2. Adb started already. Kill it.
Sent from my Nexus 7 using Tapatalk 2

Bump so noobs can stop struggle with nexus 7 toolkit and install sdk blah blah...

[LOLLIPOP 5.1][STOCK] Cherry Mobile One H940 Official Links

Here're the official links for Cherry Mobile One H940:
For fastboot flashable images:
Builds Available: LBY29G, LMY47O
Download: here
For OTAs:
Build: LBY29G -> LMY47O
Android Version: 5.1 (Beta) -> 5.1 Official
Download: here
Flashing Instructions:
A. Using ADB sideload (for recovery flashable update zips):
1.) Flash stock recovery.
2.) Boot to stock recovery.
3.) Perform up + power button to show menu.
4.) Select Apply update from ADB.
5.) Install ADB drivers if on Windows and not yet installed.
6.) Open cmd prompt.
7.) Change directory to where you downloaded the update zip.
8.) Issue cmd: adb sideload <update.zip filename>
9.) Wait until completed.
10.) Select reboot.
B. Using fastboot:
1.) Boot into bootloader.
2.) Flash image using fastboot flash <partition name> <image filename>.img command.
3.) Reboot using fastboot reboot command.
C. Using DD (for flashing images like system.img):
1.) Boot into custom recovery. (you could use fastboot boot custom-recovery.img so that you don't overwrite your existing one)
2.) Push image file to /sdcard using adb push command. (you might have to mount the sdcard partition before doing this)
3.) Open an ADB command shell.
4.) Go to /sdcard.
5.) Find the system partition by issuing a cat /proc/partitions command. It should be the one sized exactly 1GB (1,024,000 shown).
6.) Use dd if=/sdcard/<image filename>.img of=/dev/block/<name of partition> .
7.) Reboot either using custom recovery or just issuing an adb reboot after exiting from ADB command shell.

do you have another working file for LMY47O system.img? i'm getting a fastboot flash fail (chunk unkown) error. thanks

Reuploading now. Might be a bad upload from my end. Will post updated hashes later for the system.img.

intersectRaven said:
Reuploading now. Might be a bad upload from my end. Will post updated hashes later for the system.img.
Click to expand...
Click to collapse
same problem here
thank you

Uploaded. If it still fails, you might have to use dd to restore. Odd that it fails now when it was fine before. :/

OTA Flashing Error
Hello. I would like to ask why I cannot flash the OTA Update for CM1. I am currently on LBY29G, rooted, unlocked bootloader and stock recovery. Thanks.

erickho0407 said:
Hello. I would like to ask why I cannot flash the OTA Update for CM1. I am currently on LBY29G, rooted, unlocked bootloader and stock recovery. Thanks.
Click to expand...
Click to collapse
Go back to stock boot. Since you're rooted, I'm assuming your boot has been modified to be insecure.

intersectRaven said:
Go back to stock boot. Since you're rooted, I'm assuming your boot has been modified to be insecure.
Click to expand...
Click to collapse
Ok By going back to "stock boot," does this mean I have to re-lock the bootloader? I believe that I have only used the ALL-IN ONE TOOL in this thread to do the 3 things mentioned above, and also installed Lucky Patcher, Greenify, Busybox (Free) and Ad-Away in relation to root access, so I am not 100% sure by what you mean. Thanks again.

erickho0407 said:
Ok By going back to "stock boot," does this mean I have to re-lock the bootloader? I believe that I have only used the ALL-IN ONE TOOL in this thread to do the 3 things mentioned above, and also installed Lucky Patcher, Greenify, Busybox (Free) and Ad-Away in relation to root access, so I am not 100% sure by what you mean. Thanks again.
Click to expand...
Click to collapse
No you don't need to relock the bootloader. You just need to flash stock boot partition. This is usually replaced when rooting.

intersectRaven said:
No you don't need to relock the bootloader. You just need to flash stock boot partition. This is usually replaced when rooting.
Click to expand...
Click to collapse
Ok. So this means that I reflash boot.img right (would probably use fastboot). Thank you very much for assistance

Sir
can you capture ota for myphone uno

gabisonfire98 said:
Sir
can you capture ota for myphone uno
Click to expand...
Click to collapse
Unfortunately, I don't have an Uno so no.

still the same problem, will try DD **update still failed, and now can't flash old build...will try to restore a backup from CWM

Working internal detect for pc and file ?

marjoejoejoe said:
still the same problem, will try DD **update still failed, and now can't flash old build...will try to restore a backup from CWM
Click to expand...
Click to collapse
I see. Very weid. Might be some form of protection now for the system partition. I'll just take it down now so that no one else uses it.

intersectRaven said:
I see. Very weid. Might be some form of protection now for the system partition. I'll just take it down now so that no one else uses it.
Click to expand...
Click to collapse
I'll have another go at it later today. Was able to flash my own backup using CWM

marjoejoejoe said:
I'll have another go at it later today. Was able to flash my own backup using CWM
Click to expand...
Click to collapse
Still, it should be foolproof. I already checked and double-checked the system image I uploaded and it's mountable in Linux so it should restore correctly like the previous LBY image. I can't think of any other reason aside from some sort of protection that would disallow flashing of the system image through both fastboot and dd.
*On second thought, I'm reupping the image. I just flashed it using dd on my device and it works perfectly.

success, was running a windows 7 virtual machine in OSX. it must have been a protection, you are right...ran it using OSX instead (stupid me, why i didn't use it in the first place for fastboot).
files are good to go thanks man

Need help in Flashing the Stock Recovery.
Hi Guys,
I need help in flashing the stock recovery.
I've used the ALL-IN-ONE TOOL to unlock my phone's bootloader, flash the PhilZ Touch Customer recovery and Root my CM1
[http://forum.xda-developers.com/cro.../tool-master-tool-unlock-bootloader-t2997696]
However I'm unsuccessful flashing the stock recovery from the ALL-IN-ONE TOOL so I can update my phone's software to Android 5.1.1.
Can I flash the stock recovery using one of the files here? If yes, can someone please teach me how.
Thanks in advance!

OTG
Hi,
Just a quick question, after flashing using this ROM, will CM One support OTG? Or do I need to root the phone first? Is there a way to add support for OTG?
Pardon me if this may not be much related to the topic.

[Q] Htc Rooting Issue

So i was following this tutorial on youtube which showed me how to flash a custom image however, i have tried it but i keep getting this message pop up. Naturally, i followed everything the guy did and it got to: fastboot devices, fastboot flash recovery.img (the img name) and got this error. Please help me.

ChiefMustardo said:
So i was following this tutorial on youtube which showed me how to flash a custom image however, i have tried it but i keep getting this message pop up. Naturally, i followed everything the guy did and it got to: fastboot devices, fastboot flash recovery.img (the img name) and got this error. Please help me.
Click to expand...
Click to collapse
Right click the recovery image, click on rename. Name it recovery for simplicity. Put it in the folder where fastboot, adb etc. is.
Open cmd, direct it to your working folder. Type fastboot flash recovery recovery.img Not recovery .img.img

What next?
James L said:
Right click the recovery image, click on rename. Name it recovery for simplicity. Put it in the folder where fastboot, adb etc. is.
Open cmd, direct it to your working folder. Type fastboot flash recovery recovery.img Not recovery .img.img
Click to expand...
Click to collapse
So i have followed these steps and it came to the attachment below. How do i get supersu onto my htc and is it definately rooted now?

ChiefMustardo said:
So i have followed these steps and it came to the attachment below. How do i get supersu onto my htc and is it definately rooted now?
Click to expand...
Click to collapse
It seems you are still typing the wrong thing. Type in:
Code:
fastboot flash recovery recovery.img
Just copy/paste the above code in your command prompt.
That is just to get the custom recovery TWRP on your phone.
Next download the SuperSU app and you will see a # symbol in your notifications to let you know you need to download the su binaries.
Choose the TWRP option and it will reboot the phone to TWRP recovery.
It may restart after it is done or you will have to press Back and choose Reboot then System. I just did this and I received an error in TWRP. I simply rebooted and SuperSU is working perfect and I have root access.

blaqueknight said:
It seems you are still typing the wrong thing. Type in:
Code:
fastboot flash recovery recovery.img
Just copy/paste the above code in your command prompt.
That is just to get the custom recovery TWRP on your phone.
Next download the SuperSU app and you will see a # symbol in your notifications to let you know you need to download the su binaries.
Choose the TWRP option and it will reboot the phone to TWRP recovery.
It may restart after it is done or you will have to press Back and choose Reboot then System. I just did this and I received an error in TWRP. I simply rebooted and SuperSU is working perfect and I have root access.
Click to expand...
Click to collapse
The custom image worked but ... I do not have a twrp option. I have:
HBOOT <-------- i chose this then recovery and the phone loaded. I then installed supersu and launched it but it said there is no su binary installed, and supersu cannot install it. this is a problem!
if you just upgraded to android 4.3, you need to manually re-root - consult the relevant forums for your device. <---- I have not upgraded. Please Help
RAMDUMP
REBOOT
REBOOT FASTBOOT <-------- I am guessing it is this one?
POWER DOWN

ChiefMustardo said:
The custom image worked but ... I do not have a twrp option. I have:
HBOOT
RAMDUMP
REBOOT
REBOOT FASTBOOT <-------- I am guessing it is this one?
POWER DOWN
Click to expand...
Click to collapse
No, that will just reboot back into fastboot mode.
You have two options:
1. Press the Power button from that screen you just mentioned and click on the RECOVERY option
2. When you are in the OS type in the code below
Code:
adb reboot recovery

blaqueknight said:
No, that will just reboot back into fastboot mode.
You have two options:
1. Press the Power button from that screen you just mentioned and click on the RECOVERY option
2. When you are in the OS type in the code below
Code:
adb reboot recovery
Click to expand...
Click to collapse
Sorry to be so stupid but how do i get into the os?

ChiefMustardo said:
Sorry to be so stupid but how do i get into the os?
Click to expand...
Click to collapse
No, it's not stupid. I shouldn't have said it like that. Just turn the phone on, basically. I'm referring to the Android OS where you can use adb.

blaqueknight said:
No, it's not stupid. I shouldn't have said it like that. Just turn the phone on, basically. I'm referring to the Android OS where you can use adb.
Click to expand...
Click to collapse
So once i have turned the phone back on i input the code you gave me into cmd? <------ Did this and got this.

ChiefMustardo said:
So once i have turned the phone back on i input the code you gave me into cmd? <------ Did this and got this.
Click to expand...
Click to collapse
This is what i got

ChiefMustardo said:
This is what i got
Click to expand...
Click to collapse
I've seen that before. It usually means you have more than one adb.exe or it could really just be out of date. HTC Sync Manager and WinDroid both come with their own adb. I got rid of those two and the problem went away.
Type in the command prompt, in the same folder as adb.exe
Code:
adb version
The newest one is 1.0.32, just to rule out you don't have an older version.

blaqueknight said:
I've seen that before. It usually means you have more than one adb.exe or it could really just be out of date. HTC Sync Manager and WinDroid both come with their own adb. I got rid of those two and the problem went away.
Type in the command prompt, in the same folder as adb.exe
Code:
adb version
The newest one is 1.0.32, just to rule out you don't have an older version.
Click to expand...
Click to collapse
Yup i have that version. Shall i delete htc sync manager?

ChiefMustardo said:
Yup i have that version. Shall i delete htc sync manager?
Click to expand...
Click to collapse
If you don't use it, yes.

blaqueknight said:
If you don't use it, yes.
Click to expand...
Click to collapse
I have deleted now how do i sort it out because
adb reboot recovery didn't work last time. I have done adb reboot recovery and it started up the daemon rebooted the device. Now what do i do?

ChiefMustardo said:
I have deleted now how do i sort it out because
adb reboot recovery didn't work last time. I have done adb reboot recovery and it started up the daemon rebooted the device. Now what do i do?
Click to expand...
Click to collapse
I told you what to do in post #4.
I just said reboot into recovery to make sure you have TWRP installed
Next download the SuperSU app and you will see a # symbol in your notifications to let you know you need to download the su binaries.
Choose the TWRP option and it will reboot the phone to TWRP recovery.
It may restart after it is done or you will have to press Back and choose Reboot then System. I just did this and I received an error in TWRP. I simply rebooted and SuperSU is working perfect and I have root access.

blaqueknight said:
I told you what to do in post #4.
I just said reboot into recovery to make sure you have TWRP installed
Next download the SuperSU app and you will see a # symbol in your notifications to let you know you need to download the su binaries.
Choose the TWRP option and it will reboot the phone to TWRP recovery.
It may restart after it is done or you will have to press Back and choose Reboot then System. I just did this and I received an error in TWRP. I simply rebooted and SuperSU is working perfect and I have root access.
Click to expand...
Click to collapse
Sorry about the hassle. The reason why supersu isn't working is because bellend here has a phone running 4.4.3. How do i go about sorting out that issue?

ChiefMustardo said:
Sorry about the hassle. The reason why supersu isn't working is because bellend here has a phone running 4.4.3. How do i go about sorting out that issue?
Click to expand...
Click to collapse
It's no hassle, I just wanted to point that out to you.
Are you sure it is 4.4.3 or are you referring to an error message? Our phone should be 4.4.2. Even though one of the custom ROMs says 4.4.4.

blaqueknight said:
It's no hassle, I just wanted to point that out to you.
Are you sure it is 4.4.3 or are you referring to an error message?
Click to expand...
Click to collapse
It is i checked. I followed this guide instead http://forum.xda-developers.com/desire-510/general/guide-how-to-unlock-install-recovery-t2988292 and i launched it and it said this version is a development build and it ran. Now should it be rooted or is there another step i have to do? I just did root checker and it said that the root has been installed correctly

Thank you all. You have been a great help and i am hugely beyond belief grateful. The root has worked.

adb sideload issue

Can someone explain this to me as to why https://android.googleapis.com/pack...amu-ota-LMY48I-from-LMY47Z-superblock-fix.zip gives me the following error shown in the attach picture?
Looks like it should match correctly but sideload is errorring out saying otherwise
C:\Users\Double\AppData\Local\Android\android-sdk\platform-tools>adb shell getprop ro.build.fingerprint
google/shamu/shamu:5.1.1/LMY47Z/1860966:user/release-keys
C:\Users\Double\AppData\Local\Android\android-sdk\platform-tools>

Do it from stock recovery. It's kinda broken in twrp because twrp was build with a build.prop with old user keys so it won't let you flash it. All the Ota zip will see is those old user keys and kill it every time. Stock recovery will work.
Sent from my Nexus 6 using Tapatalk

david279 said:
Do it from stock recovery. It's kinda broken in twrp because twrp was build with a build.prop with old user keys so it won't let you flash it. All the Ota zip will see is those old user keys and kill it every time. Stock recovery will work.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I'm having the same problem with TWRP and the TMO LYZ28J update. How do I get back to stock recovery? Is it just a matter of uninstalling TWRP and reinstalling it when I'm done?

JimSmith94 said:
I'm having the same problem with TWRP and the TMO LYZ28J update. How do I get back to stock recovery? Is it just a matter of uninstalling TWRP and reinstalling it when I'm done?
Click to expand...
Click to collapse
Install the stock recovery in fastboot, you can download it from the factory images or just search for it
Sent from my Nexus 6 using Tapatalk

JimSmith94 said:
I'm having the same problem with TWRP and the TMO LYZ28J update. How do I get back to stock recovery? Is it just a matter of uninstalling TWRP and reinstalling it when I'm done?
Click to expand...
Click to collapse
If you have TWRP, chances are your rom would be modified in some way so the OTA Won't work anyway.

danarama said:
If you have TWRP, chances are your rom would be modified in some way so the OTA Won't work anyway.
Click to expand...
Click to collapse
I'm stock rooted, are you saying that won't work? What's the proper way to install this update without losing data?
I'm used to flashing updates from recovery, so this whole sideload thing is new to me.

JimSmith94 said:
I'm stock rooted, are you saying that won't work? What's the proper way to install this update without losing data?
I'm used to flashing updates from recovery, so this whole sideload thing is new to me.
Click to expand...
Click to collapse
Correct, root is a modification. An OTA will not flash unless the rom and kernel are 100% as expected.. This is regardless of whether the OTA zip is flahsed in adb sideload or as an OTA natively.
If there is a J factory image available, fastboot flash the system.img and boot.img and you're updated.
If there is not, do the above but with the version the OTA expects. .. Then flash the OTA

danarama said:
If there is a J factory image available, fastboot flash the system.img and boot.img and you're updated.
Click to expand...
Click to collapse
There is an LYZ28J factory image available, here > https://developers.google.com/android/nexus/images

danarama said:
Correct, root is a modification. An OTA will not flash unless the rom and kernel are 100% as expected.. This is regardless of whether the OTA zip is flahsed in adb sideload or as an OTA natively.
If there is a J factory image available, fastboot flash the system.img and boot.img and you're updated.
If there is not, do the above but with the version the OTA expects. .. Then flash the OTA
Click to expand...
Click to collapse
Thanks for the info! Since Google says they will release these updates monthly, I'm hoping to find a simple, painless, and repeatable method to do these updates. Will flashing your suggestions lose root or data?

JimSmith94 said:
Thanks for the info! Since Google says they will release these updates monthly, I'm hoping to find a simple, painless, and repeatable method to do these updates. Will flashing your suggestions lose root or data?
Click to expand...
Click to collapse
It will lose root, but you just flash supersu from recovery

I had to flash the stock recovery back on and then did the OTA update. :-/ I really like my full system backups that TWRP does though..

doublejz said:
I had to flash the stock recovery back on and then did the OTA update. :-/ I really like my full system backups that TWRP does though..
Click to expand...
Click to collapse
Just flash the system.img then

Unable to Unbrick phone

Hey guys,
My younger brother had TWRP installed on his OP3. Yesterday he applied OTA and his phone got bricked. I unbricked it from MSMtool method (Qualcom Driver). It got unbricked and i have stock rom now however phone is stuck at android is upgrading (45 minutes). I tried restarting it and now it is in boot loop. i tried to flash latest OxygenOS from adb sideload and it got bricked again. Can anyone tell me what to do now or what is wrong with the device.

abdullah.ahsan11 said:
Hey guys,
My younger brother had TWRP installed on his OP3. Yesterday he applied OTA and his phone got bricked. I unbricked it from MSMtool method (Qualcom Driver). It got unbricked and i have stock rom now however phone is stuck at android is upgrading (45 minutes). I tried restarting it and now it is in boot loop. i tried to flash latest OxygenOS from adb sideload and it got bricked again. Can anyone tell me what to do now or what is wrong with the device.
Click to expand...
Click to collapse
You have TWRP installed? Use Method 2 of the unbrick guide. Now you want to wipe every partition then adb push your rom (not sideload) and manually flash it. Make sure you are on the latest Bluspark twrp.

Puddi_Puddin said:
You have TWRP installed? Use Method 2 of the unbrick guide. Now you want to wipe every partition then adb push your rom (not sideload) and manually flash it. Make sure you are on the latest Bluspark twrp.
Click to expand...
Click to collapse
I am using method 2, the OS gets stuck on bootloop that's why i tried to sideload later
I don't have a working recovery, all i can get is stock recovery, how can i install twrp?
I've tried flashing (fastboot flash recovery recovery.img) it but it is not working

abdullah.ahsan11 said:
I am using method 2, the OS gets stuck on bootloop that's why i tried to sideload later
I don't have a working recovery, all i can get is stock recovery, how can i install twrp?
I've tried flashing (fastboot flash recovery recovery.img) it but it is not working
Click to expand...
Click to collapse
Why is it not working? Does it give an error or something?

Puddi_Puddin said:
Why is it not working? Does it give an error or something?
Click to expand...
Click to collapse
Yes, it says flashing partition not allowed.
I suppose it is because usb debugging is off.

abdullah.ahsan11 said:
Yes, it says flashing partition not allowed.
I suppose it is because usb debugging is off.
Click to expand...
Click to collapse
Nah, In windows, go to Device Manager. How does your device show up? It has to do with wrong drivers.

Puddi_Puddin said:
Nah, In windows, go to Device Manager. How does your device show up? It has to do with wrong drivers.
Click to expand...
Click to collapse
Yes It shows up correctly.

abdullah.ahsan11 said:
Yes It shows up correctly.
Click to expand...
Click to collapse
What is correctly? What does it say? You might want to try different ADB drivers. You should be able to always flash In fastboot..

abdullah.ahsan11 said:
Yes, it says flashing partition not allowed.
I suppose it is because usb debugging is off.
Click to expand...
Click to collapse
Check again the bootloader to be unlocked. Use the tool for that, is it on OP3 forum, then retry to get a stock rom up before anything else (TWRP, custom rom, etc)
Sent from my OnePlus3 using XDA Labs

follow this instruction -
1- go into twrp and wipe everything even internal and formate it .
2- unistall all adb driver and oneplus driver also .. then clean tmp file from window
3rd- install latest adb+ oneplus 3 driver ..again restrat ..
4th-boot in fastboot mod and lock your bootloader
5th-flast latest build of oxygen stock recovery from fastboot
6th than again wipe or factory reset the device via stock recovery
7th open stock recoery than flash latest build of oxygen os via sideload
8th reboot the device and setup quikly
9th-unlock bootloader, flash bluespark recovery , flash rom, flash supersu ..
10th play with device