Related
Keep in mind bootloader unlock will not work if you have done the latest OTA update without previously using supercid. See bootloader unlock guide below for more details.
This procedure is designed to be EXTREMELY EASY and for people using windows. Following this guide will give you the knowledge you need to use ADB and Recovery menus in order to flash all of the ROMs, Kernels and APK (apps) files that you want. I am not responsible if anything undersireable happens in this procedure that makes you sad, poo yourself or ends the world.
Even if you have accidentally formatted your internal storage and you have no files on your phone, this section is down the bottom of the thread. Only follow this if you have no access to your phone and have nothing installed on your sdcard. For everybody else simply follow from step 1.
WINDOWS DRIVERS
You will need the USB drivers for your phone to communicate with your computer. You can search around and get these drivers separately or if that is not possible then please download and install The HTC Sync Manager from here
UNLOCKING YOUR BOOTLOADER
Since the new method came out, it is ridiculously easy to unlock your bootloader now. If you haven't unlocked your bootloader than please visit this thread and follow the instructions. I found this video on youtube that will make this process easier for you too.
INSTALLING ADB/FASTBOOT (SDK) (Please read this even if you have already installed this)
I would recommend following the guide to install adb (sdk) I have included below. If you have already done this step then keep in mind you should always have sdk updated and to make life easier rename your 'platform-tools' folder to something easier, for example rename the folder to android-adb. Now copy the 'android-adb' folder to a convenient location on your PC e.g: root of the C: so it will now look like this c:\android-adb *If you're having trouble locating this folder it will usually be here c:android-sdk-windows\platform-tools or something along those lines* At this stage the Windows’s Path Environment Variables will now have to suit this change, which in this case is: ;C:\android-adb - If you would prefer to leave things as they are than so be it and continue reading.
If this is all sounding too hard than you really need to start again and follow the EASY!!!!!! guide below
Make sure you have SDK installed and updated. If you haven't already than follow this extremely easy guide
DOWNLOADING REQUIRED FILES FOR FLASHING
(Download the following items listed below)
1. CWM Recovery This is what you will be using ALL THE TIME to flash ROMs and Kernel Modules. There is an alternative recovery called TWRP which can be found here but I am not using that right now so for the purpose of this guide please use CWM, if for some reason you need to use TWRP then the steps will be very similar just look on screen for the right area and touch the screen to select, pretty straight forward right?
2. Your desired ROM I would 100% recommend ViperDNA from HERE if not you can grab a different one from HERE or HERE
3. You now need all required kernel files you are planning to use with the ROM you have selected. If you don't have the kernel installed correctly you will face bugs, the most common is WiFi not working correctly (keeps searching) or something else like that. Now for the Droid DNA at the moment the kernel is broken down in to 2 parts. The first file is kernel modules and the second file is the the boot.img. Now whatever ROM you choose to download and install, it should already be using a specific kernel. When you flash a ROM the kernel modules will already be installed for the specific kernel the ROM is using.
For example If you listened to my advice and are going to use ViperDNA, this ROM already comes with the kernel modules required for the kernel it is using. The only thing that is left for you to do is download the second part of the kernel which is the boot.img file. Every kernel needs both the kernel modules and boot.img files to work 100% without fault, and every kernel has different modules and a boot.img that will only work for that specific kernel.
Each ROM should give you a download link for the required boot.img so just make sure to read the first few posts - If you are planning to use ViperDNA then it can be found on the first page post number 2 of the ViperDNA thread and it is named Stock DSB System Write Boot.img -
* If that wasn't already clear enough I would like to say that if you are download a complete kernel zip separately (which you can do) then you will get both files required. The first is the "already included in the ROM" kernel modules and the second file will be the boot.img - You can find all of the different kernels here - as you can see in this list the kernel included in ViperDNA is the one named "[KERNEL]Droid DNA Cubed Kernel Stock" - Once you have finished installing a ROM then I would recommend having a look at some different kernels if you want. Down the very bottom of this post I have included instructions on how to flash a kernel so please check it out.*
Now read this next part carefully. before doing anything else, I want you to prepare the files that you are going to be flashing with ADB.
PREPARING FILES FOR FLASHING
1. ** Using your computer, unzip your CWM Recovery zip and move the recovery.img to your platform-tools folder which you may or may not have renamed by now. this is where adb and fastboot.exe files are. for example If you have followed the guide I provided it will be c:\android-adb if not it will be whatever you have named it as, and wherever you have installed it to. Usually c:android-sdk-windows\platform-tools or something along those lines. I'm assuming by this stage you have changed the Windows’s Path Environment Variables, if not then you really should be following the very simple guide above!
(if you don't have a zip program, use this one)
2. ** Next I need you move the boot.img (for your kernel) to the same location you just moved your recovery.img (If you have followed my advice then you can get this file from the first page of the ViperDNA thread) if you didn't then the boot.img file might be on the first page of your desired ROM. *If you have downloaded the same kernel used in the ROM, but as a complete zip then you will need to unzip the kernel zip to access the boot.img and continue as above*.
Do not close the folder where you have copied these files, simply leave it open
3. ** Now connect your phone to a USB port. Sometimes it's best to stick to USB 2 rather than USB 3. Copy and paste the ROM.zip (Whatever the name of your ROM is, you don't need to rename it ) file that you want to flash over to your phone (make sure to not accidentally drop it in to an already existing folder) So as soon as you open the contents of your device it should be pasted right there - Once this is complete disconnect the phone and switch it off.
4. ** Boot your phone in to bootloader by holding down the "power button" and the "volume down" key at the same time until you see the bootloader screen on your phone. Now press the power button once to make sure you're in fastboot (If you don't your phone will not be found by ADB and will be constantly "waiting for device") - Now connect your phone to your computer again and continue reading
5. ** Back to your computer, while still in the same folder you have copied your recovery.img and boot.img I want you to hold the shift button at the same time as right clicking on a blank space inside the folder and click on "open command window here"
FLASHING YOUR FILES IN FASTBOOT
Now you are ready to flash your files. Starting with your recovery.img file and then followed by your kernels boot.img - In your command window type the following commands
1. ** To flash a recovery you will need to type**
fastboot flash recovery recovery.img
2. ** To flash your kernels boot.img you need to type**
fastboot flash boot boot.img
Before flashing the boot.img, you can in fact flash your ROM.zip with the instructions given below. However, it is strongly recommended to do it before you flash the boot.img. This is the standard procedure that should be used for every single ROM.
USING CWM FOR THE ROM INSTALLATION AND A CLEAN WIPING PROCEDURE
Go back to your phone and scroll down to where it says recovery and hit the power button. Your phone will now reboot in to CWM Recovery. (If you can't see the recovery option then you might be in the main bootloader menu screen, try pressing the power button once to change back to fastboot). Your phone should now reboot and display a white HTC screen and up the top it will read "Entering Recovery" - After it has finished you can now navigate through CWM Recovery by using the volume keys and pressing the power button to enter. Some versions of CWM you can also touch the screen to make selections. Lets begin
*WARNING* Although you don't have to, but if you do choose to use the recommended Step 3 which is found below, it will wipe all of your games and apps including saved game data and such. Don't worry all of your photos and music will be fine. Make sure to sync your contacts with your Google account**
1. Scroll down to -advanced and hit power, then do as follows
- wipe dalvik cache
-***go back***
2. Scroll down to -mounts and storage and hit power then:
-format system
-press your back key on the phone to go back
3. Scroll down to -wipe data/factory reset and hit the power button
"you can skip this process but it is a highly recommended one if you want less bugs in the ROM" (If you decide to skip make sure you you also -wipe cache partition which is in the same menu)
4. Scroll down to install zip from sdcard and hit power and then:
-choose zip from sdcard. (Locate your ROM.zip and hit power)
- Wait for this process to finish or follow on screen prompts from here on.
- go back to the main menu and reboot your device if it isn't already
This method will work with every other zip file that is flashable through CWM including kernel modules. You will not however need to follow all of the steps for wiping and such, simply just start from step 4
This is the end of my guide!. If you already have a ROM installed and you want to change the kernel, then scroll all the way to the bottom of this post
__________________________________________________________________________________________________________________________
*NOTE* KEEP SCROLLING DOWN IF YOU ARE LOOKING AT HOW TO FLASH A DIFFERENT KERNEL. THIS SECTION IS FOR PEOPLE WHO HAVE ACCIDENTALLY FORMATTED THEIR INTERAL STORAGE. OR FOR ANY OTHER RANDOM REASON YOU CAN'T USE A COMPUTER TO DROP AND DRAG FILES TO YOUR PHONE.
Place desired ROM, kernel modules, recovery files, or APK (apps) files inside the same folder your adb/fastboot.exe files. It's usually found here c:android-sdk-windows\platform-tools or something along those lines unless you have moved or renamed it. If you are having trouble then please follow the ADB installation guide I have listed at the beginning of this thread.
Now while your phone is booted in Android and you make sure to have USB Debugging on, we are going to push these files depending on the file type by typing in commands:
adb push ROM.zip /sdcard/ROM.zip ***replace the word ROM with the exact name of the file you are pushing***
For example if you were using ViperDNA ROM you would type: adb push ViperDNA-version2.3.zip /sdcard/ViperDNA-version2.3.zip
And if it was a kernel (boot) file you would change the name respectively. For example: adb push cubedversion1000.boot/sdcard/cubedversion1000.boot
Now for applications such as games etc. You can either install the game directly or push the file to you phone to be installed later. Personally I always like to install from my phone so I always just push the file. But I will give you both options. ***To clarify if you are confused right now: adb push will copy any file to the phone, whereas adb install will only accept an apk file, and will install it onto the device***
To install an apk, it is quite simple, however it has a different path than what we have spoken about previously. The files will automatically push install themself in the correct area with your current installed apps .
If you want to install apps then you would type:
adb install apkfile
***For example if it is the game temple run, it would look like this: adb install templerun.apk
If you would prefer to manually install the game from your phone than you will need to push the file like we have mentioned already with the other file types:
adb push templerun.apk/sdcard/templerun.apk
Now remember if your phone is working correctly you can simply copy and paste all of these files directly to your phone and then flash in recovery for your ROMs or if you want to install apps you would then use a file explorer and locate the apk on your sdcard of the phone and then install it all from your phone. This was simply written for people that have no files on their sdcard due to accidental formatting of internal memory
INSTALLING ANOTHER KERNEL
If you have flashed a ROM and do want to use a kernel that isn't included with your ROM, then you can get another one from HERE Now this process is exactly the same as the stuff you have already done. Instead you will need to flash both of the kernel files included in the kernel zip file.
The first part is identical to what you did earlier. Move the boot.img file to the same place I mentioned earlier in this guide, and flash it the same way I mentioned in fastboot. This time the path will need to be changed because it is a boot file not a recovery file. So use this command: fastboot flash boot boot.img
In this second part move the kernel modules file to your phone and do exactly the same as you did in order to flash the ROM in CWM Recovery as mentioned earlier, only this time start from step 9 section 4.
That is all. Keep in mind things like wifi might not work if you forget to flash the kernel modules! - Just be sure it is always a 2 step process.
*Credits*
nitsuj17 for the greatest ROM on our phone ViperDNA
Jailbreak Eye for the wonderful ADB guide
DroidModd3rX for his video
dsb9938 for his awesome kernel work
jcase and beaups for their unlocking methods
htcdev.com for the unlocking
All of the fantastic developers for Android
Good guide. I would suggest adding a link to unlocking the phone because you have the about everything else. I really like that you included changing PATH and such in your guide because a lot of people kept getting the adb not found stuff.
I need a video. Its hard for me to learn so much by reading, esp when you could brick your phone.
good write up though!
Followed instructions and it says
sending 'recovery' (6944 KB)... OKAY [ 1.162s]
writing 'recovery'... OKAY [ 0.760s]
finished. total time: 1.924s
Then i go back to the recovery and go to it, does the HTC recovery..Also going back into the boot screen, the top says unlocked but also now says tampered on top.
treahuggs said:
I need a video. Its hard for me to learn so much by reading, esp when you could brick your phone.
good write up though!
Followed instructions and it says
sending 'recovery' (6944 KB)... OKAY [ 1.162s]
writing 'recovery'... OKAY [ 0.760s]
finished. total time: 1.924s
Then i go back to the recovery and go to it, does the HTC recovery..
Click to expand...
Click to collapse
I would reboot the phone in to bootloader mode and then press the power button once to switch to the fastboot menu. Now scroll down to recovery again and press the power button. If this doesn't work than try flashing the recovery again using the step for it. When you do in fact click on recovery in your bootloader, does it reboot in to a white HTC screen that says up the top Entering recovery?
A video would be extremely tedious to make for this guide. If you have already unlocked your bootloader than the bricking of this device would be drastically minimised. I wouldn't worry too much at this stage.
uppon2 said:
I would reboot the phone in to bootloader mode and then press the power button once to switch to the fastboot menu. Now scroll down to recovery again and press the power button. If this doesn't work than try flashing the recovery again using the step for it. When you do in fact click on recovery in your bootloader, does it reboot in to a while screen that says up the top Entering recovery?
A video would be extremely tedious to make for this guide. If you have already unlocked your bootloader than the bricking of this device would be drastically minimised. I wouldn't worry too much at this stage.
Click to expand...
Click to collapse
Yes it says that.
Let me ask some questions, you say copy the complete ROM.zip over to the phone. Where at on the phone? Does it have to be named ROM.zip?
Does the CWM need to be copied over too? Using your guide to download the viper files and the second boot.img is confusing since the .zip with the viper has a boot.img with it, should we use that, ignore it, or what?
I thank you for taking the time to write a guide but with so many variables that are being used and referenced, there needs to be more specific instructions.
ALL i want to do is use mt titanium backup to get my old apps and app data on my DNA. Is it really this many steps just to gain root access to the DNA? With the Razr maxx it was just connecting it to the computer in debugging mode, and running a batch file.
:victory:
---------- Post added at 06:21 PM ---------- Previous post was at 06:15 PM ----------
:silly:
treahuggs said:
Yes it says that.
Let me ask some questions, you say copy the complete ROM.zip over to the phone. Where at on the phone? Does it have to be named ROM.zip?
Does the CWM need to be copied over too? Using your guide to download the viper files and the second boot.img is confusing since the .zip with the viper has a boot.img with it, should we use that, ignore it, or what?
I thank you for taking the time to write a guide but with so many variables that are being used and referenced, there needs to be more specific instructions.
ALL i want to do is use mt titanium backup to get my old apps and app data on my DNA. Is it really this many steps just to gain root access to the DNA? With the Razr maxx it was just connecting it to the computer in debugging mode, and running a batch file.
Click to expand...
Click to collapse
1. Sorry I didn't mean to put complete at the beginning of ROM.zip and no you do not need to rename the ROM zip file
2. To avoid confusing anybody, please ignore the boot.img file inside of the ROM
3. If you read the whole guide you will know exactly what to do with CWM file and every other file
4. It is unfortunately an annoying process to root this phone. However if you follow the guide completely you will have root. I'm not sure about a batch process for the DNA, sorry. It makes it very hard that we can't write to system easily, if and only if we gain this access will we be able to pack the the files which installs the su binary and busybox in to the kernels like you would find with other phones such as Samsung etc. Then you would be able to just flash a kernel and have root, without installing a custom ROM. (I could be wrong and would like further education here from other users as there might in fact be a file flashable through fastboot or recovery that gives you root and nothing else, I simply don't know about this file)
Ok where do you put the downloaded files onto the phone. When you plug the phone in you get many different windows pop up that is gives you access to different parts in the phone.
EDIT: of the three opitions that pop up when you plug the phone in only one is large enough for the viper rom so it has the viper folder AS WELL as the .zip onto it now.
My paths are "C:\android" for all my android files like the adb and the boot.img and recovery.img. I am able to write the two .img files to the phone with the console telling me it wrote ok.
I go to the recovery on the phone and it says entering recovery on the top of the phone screen but then it boots straight into android.
I will redownload all of the files, if anyone else has any ideas id love to hear.
EDIT 2: Got it to work, i think the CWM files were the problem. I just used the TWRP files and it is flashing now! Also found this video which was a huge help. http://www.youtube.com/watch?v=vAwfgi0suJQ
treahuggs said:
Ok where do you put the downloaded files onto the phone. When you plug the phone in you get many different windows pop up that is gives you access to different parts in the phone.
EDIT: of the three opitions that pop up when you plug the phone in only one is large enough for the viper rom so it has the viper folder AS WELL as the .zip onto it now.
My paths are "C:\android" for all my android files like the adb and the boot.img and recovery.img. I am able to write the two .img files to the phone with the console telling me it wrote ok.
I go to the recovery on the phone and it says entering recovery on the top of the phone screen but then it boots straight into android.
I will redownload all of the files, if anyone else has any ideas id love to hear.
EDIT 2: Got it to work, i think the CWM files were the problem. I just used the TWRP files and it is flashing now! Also found this video which was a huge help. http://www.youtube.com/watch?v=vAwfgi0suJQ
Click to expand...
Click to collapse
I'm glad you got it working
Kinda, i have wifi issues. Ive read thats because of the boot.img. Ive tried both boot.img files that you can get with the ViperDNA page and both dont seem to work.
Nvm... again. I have been writing "fastboot flash recovery boot.img" instead of boot... I feel like a noob to reading.
treahuggs said:
Kinda, i have wifi issues. Ive read thats because of the boot.img. Ive tried both boot.img files that you can get with the ViperDNA page and both dont seem to work.
Nvm... again. I have been writing "fastboot flash recovery boot.img" instead of boot... I feel like a noob to reading.
Click to expand...
Click to collapse
Hehe, I did mention that I tried to be as clear as possible with my instructions - How are you liking ViperDNA? Be sure to check out all of the options in viper tweaks
2. ** To flash your kernels boot.img you need to type**
fastboot flash boot boot.img
Before flashing the boot.img, you can in fact flash your ROM.zip with the instructions given below. However, it is strongly recommended to do it before you flash the boot.img. This is the standard procedure that should be used for every single ROM.
Click to expand...
Click to collapse
I find this part a bit confusing. Can you reword? Am I supposed to flash boot.img first then flash my rom or flash my rom first and then flash the boot.img? The "however" is making me hesitant!
Thanks for this wonderful guide!
---------- Post added at 01:49 AM ---------- Previous post was at 01:20 AM ----------
ro roh,
I am now stuck at the htc white screen with the red lettering at the bottom. I held the power button down and the power + vol down and both times the three lights at the bottom (back key, home, and recent apps) just flash at me.
I got it to go back into HBOOT by holding down power + vol down for about 12 secs, it restarts itself.. and when i tell it to reboot, it just goes back to the same screen and gets stuck.
I think i fixed it now. I went back to fastboot, flashed the recovery.img, the boot.img and then launched into cwm and reflashed viper rom. Looks like its working again.
adamjamess said:
I find this part a bit confusing. Can you reword? Am I supposed to flash boot.img first then flash my rom or flash my rom first and then flash the boot.img? The "however" is making me hesitant!
Thanks for this wonderful guide!
---------- Post added at 01:49 AM ---------- Previous post was at 01:20 AM ----------
ro roh,
I am now stuck at the htc white screen with the red lettering at the bottom. I held the power button down and the power + vol down and both times the three lights at the bottom (back key, home, and recent apps) just flash at me.
I got it to go back into HBOOT by holding down power + vol down for about 12 secs, it restarts itself.. and when i tell it to reboot, it just goes back to the same screen and gets stuck.
I think i fixed it now. I went back to fastboot, flashed the recovery.img, the boot.img and then launched into cwm and reflashed viper rom. Looks like its working again.
Click to expand...
Click to collapse
That's great news. I'm glad you worked it out. Because it is such a long guide, it does get a little bit repetitive and hard to concentrate on. You can flash the kernels boot.img before or after the ROM. You might have random issues with the ROM until you do flash the boot.img. It's really not dangerous or anything. I would say if this was your first time ever flashing a ROM on to the device, it would be safest to flash the boot.img first.
I might take this information out that you have brought up because I think I am giving too much information that is not needed right now. Even though it is factual, it can sometimes confuse people. I will leave it in there for now but if 1 more person is a bit held back because of it I'm going to reword it
I love ViperDNA Do you like it so far?
So far i like it. I tried their theme first but i dont like all the red cause i feel like it is telling me something is wrong so i re did it without the theme, Now only the clock is red and i still want to find a way to change that.
Also this phone will be sent back to verizon tomorrow for a replacement. Can i put it back to stock and also get rid of the "tampered" in the boot screen?
I was pretty impressed with the ViperDNA video review. So far it's given me what I was looking for: 3 dot menu gone, wifi nag, and gps reticule gone. I like the red accents. Although the round icons that are all red are ugly. I have the employee edition of the dna so some red goes well with the back. Again thanks for this!
Edit: The status bar tweaks don't allow me to hide NFC icon!
Edit 2: How do I get the sweep to lock and unlock to work?
Sent from my HTC6435LVW using Tapatalk 2
adamjamess said:
I was pretty impressed with the ViperDNA video review. So far it's given me what I was looking for: 3 dot menu gone, wifi nag, and gps reticule gone. I like the red accents. Although the round icons that are all red are ugly. I have the employee edition of the dna so some red goes well with the back. Again thanks for this!
Edit: The status bar tweaks don't allow me to hide NFC icon!
Edit 2: How do I get the sweep to lock and unlock to work?
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
I believe it will depend on your kernel too. If you use cubed it will work, I tested with elkays and it didn't work. If you are not sure how to activate this then open up viper tweaks. For slide2wake the option is in lockscreen and another good feature is hold back to kill which is in the buttons tab. Good luck
Sent from my HTC6435LVW using Tapatalk 2
uppon2 said:
I believe it will depend on your kernel too. If you use cubed it will work, I tested with elkays and it didn't work. If you are not sure how to activate this then open up viper tweaks. For slide2wake the option is in lockscreen and another good feature is hold back to kill which is in the buttons tab. Good luck
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
For some reason the option is grayed out.
Sent from my HTC6435LVW using Tapatalk 2
adamjamess said:
For some reason the option is grayed out.
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
The bottom one "Enable slide 2 unlock" you already have checked is all you need for it to work. This is the only option I have checked out of the last 4 options and it works fine for me. Try to uncheck the option to "Block Pulldown" if you are having problems? I did try to enable "Block Pulldown" but I could not reproduce your problem. Mine is working fine.
Which kernel are you using?
Dsb's cubed. The one recommended in your guide.
Sent from my HTC6435LVW using Tapatalk 2
adamjamess said:
Dsb's cubed. The one recommended in your guide.
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
Should be working. You might want to leave a comment in the kernel and ViperDNA threads. As long as that bottom option is checked it should work with Cubed
Here are instructions on how to unlock and root your htc desire 610. These work for both models, but the files are for the AT&T version.
BEFORE WE BEGIN, SOME TERMINOLOGY:
Unlocked Bootloader: HTCDev website will help us do this. It's free. It allows you to flash a recovery and signed boot image, which we have. It does not allow you to flash unsigned images.
S-On: Security on. This is how our phones come stock. Htc will not allow us to flash unsigned images because of this.
S-off: once someone achieves this for us, it will allow us to modify anything and everything, signed or not. We can flash new boot image and radios without worry of version number or signature.
Root: Allows you "administrative access" to your device, to move files and do certain things. However, our phone also has...
System Write Protection: HTC included this in the kernel, and it basically means that unless you have a kernel or boot image that gets around it, any changes you make to the system partition (aside from flashing in recovery) won't stick through a reboot. Essentially they will be temporary in an effort to preserve the phone. We don't like this.
Now then, with that out of the way...
1) HTCDev Bootloader Unlock: Under "Select Your Device", scroll ALL THE WAY TO THE BOTTOM, and choose "All Other Supported Models". I know it works, because I just did it. IT WILL WIPE YOUR DEVICE DATA. If you want the data backed up beforehand, turn on USB Debugging and use this command through adb to make a backup:
Code:
adb backup -apk -shared -all -f C:\desirebackup.ab
2)Download ClearD's Root Tool V3(USE VERSION 2.1 BELOW, VERSION 3 DOESN'T WORK FOR MOST PEOPLE): After you have drivers installed for your desire (install htc sync, plug in your phone, then let them load, then uninstall htc sync), fastboot turned off in the battery options in settings, and USB debugging turned on through the hidden developers menu, read the disclaimer in red below, and download and run this exe on your Windows machine with your phone plugged in. It'll install twrp recovery 2.8.0.1, install the engineering boot image, install SuperSU and root, and then install jmz's system-unlocked kernel to make root work like it should. I'm still working out kinks, so if it doesn't work right the first time, run it a second time! Thanks go to jmz, deez_troy, AdriVelazquez, and chainfire for the pieces to make this work.
DISCLAIMER: ONCE YOU USE THIS TOOL, YOUR DEVICE WILL HAVE THE ROOTED ENGINEERING BOOT IMAGE, WHICH CANNOT BE REVERSED. THERE ARE NO SIDE EFFECTS TO THIS IMAGE EXCEPT THAT IT SHOWS A DISCLAIMER ON YOUR SPLASH SCREEN WHEN YOU BOOT THE PHONE. THIS CANNOT BE CHANGED UNTIL WE GAIN S-OFF, WHICH HAS BEEN ACCOMPLISHED, BUT IS NOT YET PUBLICLY AVAILABLE. IF YOU ARE OK WITH THIS, PROCEED.
IF V3 DOESN'T WORK, HERE IS VERSION 2.1: Download ClearD's Root Tool V2.1. THIS VERSION INSTALLS ENGINEERING BOOT IMAGE AND JMZ KERNEL.
Return to Stock (AT&T ONLY) :http://dl3.htc.com/application/RUU_...16_10.20.4187.00L_release_392486_signed_2.exe
This ruu will bring you back to complete stock, version 1.50.502.7. It has to be run through Windows, and you have to have a locked bootloader to run it. If you're unlocked, you can relock it in fastboot with the command:
Code:
fastboot oem lock
. Feel free to unlock it again after updating through the RUU. You can use your original unlock token or get it again through htcdev.
Older root tool version 1:
Download ClearD's Desire 610 Root Tool V1. This version does not contain the engineering boot image, and needs it to work fully, thus is buggy and probably won't root you with one click. It will fail to adb remount, which will fail to auto install the zip files in recovery. If you've already flashed the engineering boot image, then it will work properly without issue. Otherwise, it'll place the root zip files on your phone, but you'll have to flash them manually in recovery.
Click to expand...
Click to collapse
Old manual method:
2) Recovery: After you're unlocked, download TWRP recovery from this thread, rename the image file to "recovery.img", and flash through fastboot with the command:
Code:
fastboot flash recovery recovery.img
This will give you the official Team Win Recovery Project recovery for our device, which will allow you to root.
3) Insecure Boot Image and Root: Once you have recovery installed, the rest is easy. In recovery, if you try to reboot back into the rom, it will ask you if you wish to root. Select yes. It will do the rest I believe, and install SuperSU when you boot back into the rom. You'll also want to download and flash JMZ's insecure kernel, which unlocks the system file lock that htc places on their newer devices. Once flashed, you can then change system files and the changes will stick through reboots.
Click to expand...
Click to collapse
HTC Engineering Boot Image:
Once unlocked, download the root zip provided in this thread, then open it. We can't just flash the zip file because most of us have an updated rom version than the one it was intended for, and I'm not sure how to fix that. But no bother. Pull out the boot image file, and place it somewhere you can find it. I put it right in my MiniADB/Fastboot folder for easy access. Then, you need to flash it. Here's how:
Code:
fastboot flash boot boot_root.img
You'll then have an insecure boot image, and it will say so on your splash screen. Trust me, the words are pretty ominous.
To restore your backup you made before unlocking, use this in adb:
Code:
adb restore C:\desirebackup.ab
Click to expand...
Click to collapse
A few superstars are currently working on s-off, and this will be updated once that occurs.
Special thanks to:
-JMZ (Recovery and Kernel)
-Deez_Troy (officiating recovery)
-AdriVelazquez (Insecure boot image)
-Chainfire (SuperSu)
Also, to save this spot and before I forget it going to sleep tonight, I'm actually not sure if firewater or sunshine will work or not yet because I haven't gotten app root yet for them to function. I'll have to get that, then we'll try one or the other of those. /end thought
Edit: I do believe we will need the wp_mod to disable system write protection and allow su to stick before we continue. That'll allow us full root. Or, we could continue with a twrp build or a Clockworkmod build if someone can assist.
ClearD said:
Edit: I do believe we will need the wp_mod to disable system write protection and allow su to stick before we continue. That'll allow us full root. Or, we could continue with a twrp build or a Clockworkmod build if someone can assist.
Click to expand...
Click to collapse
I could help with that, but you will have to build, I currently don't have a cyanogenmod source around. I need outputs of:
cat /proc/emmc
mount
cat /system/build.prop #<-- root maybe required
and I need your stock recovery.img, try getting it from an ota, or using dd.
The kernel source for this phone is released, you don't need to use the wp_mod.
It is? Where did you find it released? And how would we go about getting system writable without wp_mod? I'm still trying to work out all the kinks and have never built from source.
The outputs you need should be in my dev info thread except for the build prop, but I can remount and pull that.
ClearD said:
It is? Where did you find it released? And how would we go about getting system writable without wp_mod? I'm still trying to work out all the kinks and have never built from source.
The outputs you need should be in my dev info thread except for the build prop, but I can remount and pull that.
Click to expand...
Click to collapse
? never built from source? You are RD!
http://www.htcdev.com/devcenter/downloads Filter device desire 610.
About the system write protection: https://github.com/dummie999/android_kernel_htc_z4u/commit/19626f6c38b56b715dcc0b005ec8b82ce8ca264a
Should work
Well, build.prop then,
Edit: I need your stock recovery. You can get this with:
Code:
dd if=/dev/block/mmcblk0p41 of=/path/to/file/recovery.img
But you'll need busybox installed.
Edit2: You play subwaysurf! :highfive:
dummie999 said:
? never built from source? You are RD!
http://www.htcdev.com/devcenter/downloads Filter device desire 610.
About the system write protection: https://github.com/dummie999/android_kernel_htc_z4u/commit/19626f6c38b56b715dcc0b005ec8b82ce8ca264a
Should work
Well, build.prop then,
Edit: I need your stock recovery. You can get this with:
Code:
dd if=/dev/block/mmcblk0p41 of=/path/to/file/recovery.img
But you'll need busybox installed.
Edit2: You play subwaysurf! :highfive:
Click to expand...
Click to collapse
I'll add this hear also since I was adding it to the rooted forum. But dummie999 is right.
AdriVelazquez said:
That logic is sound; however slight differences in the model maybe.
Currently in the M8 this file is located in block/blk-core.c, which has the following.
Code:
#ifdef CONFIG_MMC_MUST_PREVENT_WP_VIOLATION
sprintf(wp_ptn, "mmcblk0p%d", get_partition_num_by_name("system"));
if (!strcmp(bdevname(bio->bi_bdev, b), wp_ptn) && !board_mfg_mode() &&
(get_tamper_sf() == 1) && (bio->bi_rw & WRITE)) {
pr_info("blk-core: Attempt to write protected partition %s block %Lu \n",
bdevname(bio->bi_bdev, b), (unsigned long long)bio->bi_sector);
err = 0;
goto wp_end_io;
} else if (atomic_read(&emmc_reboot) && (bio->bi_rw & WRITE)) {
pr_info("%s: Attempt to write eMMC, %s block %Lu \n", current->comm,
bdevname(bio->bi_bdev, b), (unsigned long long)bio->bi_sector);
err = -EROFS;
goto wp_end_io;
}
#endif
That line of code will need to be intercepted at boot to allow permanent root.
I haven't checked recently, but is the source for desire 610 posted?
Click to expand...
Click to collapse
Also, you'll need to build from source for this.
Also, you can just create modules to intercept the data on boot, which would be easier.
AdriVelazquez said:
Also, you can just create modules to intercept the data on boot, which would be easier.
Click to expand...
Click to collapse
Lol, no I couldn't get that working , compiling from source was a lot easier, at least for my d500
Edit:
My company has actually done a lot of work with the desire 610 and HTC, unfortunately some proprietary. But other's aren't.
Click to expand...
Click to collapse
Just curious, where do you work?
I usually build from pre built stock, then change what I want through decompiling and recompiling, also do gui things and script things and theme things. This is new territory, but nothing I'm not uncomfortable doing by any means. I'll work on it tonight.
Also, those outputs were not from my device, but from an unlocked and s-off device of a friend lol. I noticed that also, but was too lazy to remove it.
ClearD said:
I usually build from pre built stock, then change what I want through decompiling and recompiling, also do gui things and script things and theme things. This is new territory, but nothing I'm not uncomfortable doing by any means. I'll work on it tonight.
Click to expand...
Click to collapse
Well, then I hope you have a linux pc/laptop somewhere around
Good luck!
dummie999 said:
Well, then I hope you have a linux pc/laptop somewhere around
Good luck!
Click to expand...
Click to collapse
One of each. we'll see what happens lol.
dummie999 said:
Lol, no I couldn't get that working , compiling from source was a lot easier, at least for my d500
Edit:
Just curious, where do you work?
Click to expand...
Click to collapse
Yonder Music. It's a new music streaming app.
ClearD said:
One of each. we'll see what happens lol.
Click to expand...
Click to collapse
http://xda-university.com/as-a-developer/getting-started-building-a-kernel-from-source before I forget. There is also a readme included with your download.
AdriVelazquez said:
Yonder Music. It's a new music streaming app.
Click to expand...
Click to collapse
Why do you make your devices S-off? (the thread in general)
dummie999 said:
http://xda-university.com/as-a-developer/getting-started-building-a-kernel-from-source before I forget. There is also a readme included with your download.
Why do you make your devices S-off? (the thread in general)
Click to expand...
Click to collapse
Instead of you paying a subscription fee every month, Yonder Music sells the app bundled with the phone which you have free streaming music for the lifetime of the device.
S-off let's us do all of that.
The only source code currently offered by HTC is:
Device Carrier Region Type Kernel Android Size Description
Desire 610
Vodafone
UK
CRC
3.4.0
v4.4.2 152 MB
1.29.161.2
Desire 610
Vodafone
CH GER
CRC
3.4.0
v4.4.2 155 MB
1.29.166.2
Any idea if either of those would work? :/
ClearD said:
The only source code currently offered by HTC is:
Device Carrier Region Type Kernel Android Size Description
Desire 610
Vodafone
UK
CRC
3.4.0
v4.4.2 152 MB
1.29.161.2
Desire 610
Vodafone
CH GER
CRC
3.4.0
v4.4.2 155 MB
1.29.166.2
Any idea if either of those would work? :/
Click to expand...
Click to collapse
They usually work, you just have to be sure that your software version (1.29.sth) matches. For example, if you are on 1.29.401.3, it should work. I'm not sure, but I think this usually is only a problem on high end smartphones (one m7&m8), because the carriers there modify the kernels of those devices.
Mine (and I assume others) are on 1.30.x.x
ClearD said:
Mine (and I assume others) are on 1.30.x.x
Click to expand...
Click to collapse
Try it anyway, it might work. For example:
On my phone, the kernel for 1.20 runs fine on 1.13 1.10 1.16, but it doesn't run on 1.26 1.32 1.34. You can't know if it works before you try it.
Root achieved thanks to jmz (confirmed on my unit after his) , s-off is being worked on (by pros, not by me). Jmz built us a twrp recovery that allows for an easy root. Hopefully it'll be released to the masses soon!
first post
Does this image works with At&t devices because I am running firmware 1.19.502.4 not sure if it would stop me from booting...I have attained root by using TWRP however nothing sticks whenever i restart my phone so I was hoping this would be a solution
Shattariff said:
Does this image works with At&t devices because I am running firmware 1.19.502.4 not sure if it would stop me from booting...I have attained root by using TWRP however nothing sticks whenever i restart my phone so I was hoping this would be a solution
Click to expand...
Click to collapse
Nope that wont fix it. I am working on a kernel that will solve that problem
OKay,
Philz/Advanced CWM build for;
SM-T230/NU/31 Philz 6.59 and Aromafm [Marvell]
https://www.androidfilehost.com/?w=files&flid=28382
SM-T237p Philz 6.59 [QCOM/MSM] Thanks @hookem2oo7 for testing.
https://www.androidfilehost.com/?fid=95916177934549969
SM-T230nt Philz 6.59 [QCOM/MSM] Thanks @Erus Tyrannus for testing.
https://www.androidfilehost.com/?fid=23991606952612934
SM-T330/NU/31 Philz 6.58.9
https://www.androidfilehost.com/?w=files&flid=23544
SM-T530NU/31/35 Philz 6.58.9
https://www.androidfilehost.com/?w=files&flid=23537
SM-T533 Philz 6.58.9 <-this is a temporary test build - no noobs.
https://www.androidfilehost.com/?fid=24336189125296272
After usage you may need to reflash the stock LP 5.1 releases recovery.
https://www.androidfilehost.com/?fid=24338798368260119 <-This zip is recovery flashable.
Click to expand...
Click to collapse
NOTE remove .md5 extension if Odin complains -- 64gig sdcards must be formatted exfat
As soon as i get reorganized i will get device trees reconstructed and posted.
My hard drive failed and i lost most of what i had.
the source code for Philz recovery is here https://github.com/PhilZ-cwm6/philz_touch_cwm6
----------------------------------------------------------------------------------
Thanks to the following for support and testing
Huge thanks to @g_ding84 for testing the SM-T230/NU31 process
A special thanks to @Aben314 for supporting me in my efforts.
On the SM-T33XX- @Rusell - the main man , primary tester @pre4speed initial tester and moral support @Flashalot device tree and moral support
On the SM-T53XX thanks to @tgalal @sub77 for their previous work and @mariojuniorjp for testing on the sm-t531
-----------------------------------------------------------------------------------
These are the tools you need if you don't have them already - Odin and Samsung USB Drivers
https://www.androidfilehost.com/?w=files&flid=25040
----------------------------------------------------------------------------------
For builders, this is the default.prop of the sm-t330nu recovery, to make sure your rom assert entries will be correct
Code:
# PHILZ SM-T330NU-MB74
#
persist.security.ams.enforcing=0
ro.adb.secure=0
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.sys.usb.config=adb
persist.sys.root_access=1
ro.build.product=milletwifi[COLOR="Red"]ue[/COLOR]
ro.product.device=milletwifi[COLOR="Red"]ue[/COLOR]
ro.product.model=SM-T330NU
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.board.platform=msm8226
Sources
Device Trees Per Build
MOD EDIT: LINKS REMOVED
dev host link does not work for me.
rsktkr1 said:
dev host link does not work for me.
Click to expand...
Click to collapse
Did you read the OP completely?
If so, my apologies. Sometimes devhost goes down for inexplicable reasons.
Try again later.
m
UPDATE; see OP
SM-T330NU Philz/ADV CWM recovery
corrected storages, sdcard1 , usb-otg
TODO - orient to landscape, adjust/optimize read/write speeds
I now have the sm-t330nu so, hopefully, things will pick up.
m
EDIT- Okay, new version, storages corrected, no landscape orientation yet.
YOU MUST MAKE A NEW BACKUP AFTER INSTALL !
Backups made with previous version encounter selinux context/permission problem
and result in bootloop.
Double-checking file info for Odin
Does the sm-t330nu-philz-recovery-D-3.tar file for Odin contain the same update as the zip? I'm still new to Odin, but I've gleaned from searching that it can't use flashable zip files, they must be tar or tar.md5. Want to make sure I get the correct file before giving this a go. Thanks for a small bit of hand-holding.
K,
hi, no, odin flash d-3 first then flash the update in recovery.
i'm working on final build, so once that's done the current odin flashable file and the update zip
will be replaced, read the update post as well as the OP and be aware of the selinux issue ,
i believe i've corrected that issue in the current/final build i'm working on and should hopefully
have it up soon
thanks.
m.
Final Build Uploaded
Okay,
see OP for link, will be moving things over to android file host soon [mirror], will add link to OP
Final Build, orientation will remain in portrait, from what i've been reading, i would need to modify
kernel source to achieve landscape, which i won't be doing until after i get a rom [successful] to build through, sorry.
I tried increasing font size but, in portrait the text becomes jumbled and looks sloppy, [ yuck ! ]
The virtual keys will come in handy
Storages and selinux issue corrected, sdcard1 :good: usb-otg :good:
As a precaution, make a brand new backup, especially to preserve your full stock rom !
When/if i get landscape orientation and font sizes done i will release a really final version,
provided someone else doesn't do it first.
Sorry for the goofs and delays.
m
Thank you all!!!!
I'm getting a MD5 error when attempting to flash this Recovery to my T330NU Galaxy tab 4 8.0 Via ODIN
I tried redownloading it several times and got the same results.. I tried to flash this over the TWRP recovery port, its not mounting Cache so I can't flash the Zip..
Zaphodspeaks said:
I'm getting a MD5 error when attempting to flash this Recovery to my T330NU Galaxy tab 4 8.0 Via ODIN
I tried redownloading it several times and got the same results.. I tried to flash this over the TWRP recovery port, its not mounting Cache so I can't flash the Zip..
Click to expand...
Click to collapse
Z,
hi,
the .md5 extension can be removed, meaning, rename blah.recovery.tar.md5 to blah.recovery.tar
i scripted the odin packing process for my recovery builds a while back so, the md5 gets added as a matter of course.
the recovery will flash, as a step to defeat the automatic restoration of the stock recovery by the rom,
uncheck auto restart/reboot in odin and perform your flash, wait for the RES OK message, give it a second or two longer,
then disconnect your tab and use the three button combo to force boot to recovery, home,volume-up,power
from recovery reboot as normal.
m
moonbutt74 said:
Z,
hi,
the .md5 extension can be removed, meaning, rename blah.recovery.tar.md5 to blah.recovery.tar
i scripted the odin packing process for my recovery builds a while back so, the md5 gets added as a matter of course.
the recovery will flash, as a step to defeat the automatic restoration of the stock recovery by the rom,
uncheck auto restart/reboot in odin and perform your flash, wait for the RES OK message, give it a second or two longer,
then disconnect your tab and use the three button combo to force boot to recovery, home,volume-up,power
from recovery reboot as normal.
m
Click to expand...
Click to collapse
Ill do just that.. While I was sleeping, that idea did occur to me
Edit, yup that worked! Thanx..
Edit: Like the TWRP recovery, this recovery won't mount Cache..?
deleted, no longer relevant.
Pulling this conversation into the right thread.
I have the milletwifiUE SM-T330NU. This recovery wouldn't flash on it. The title is misleading b/c this recovery isn't for all of the SM-T330NU devices. Since it wouldn't flash, there isn't any harm done, but having read almost every other thread in the Tab 4 forum, I'd suggest pointing out the code name of each device is important in the OP. There are differences between the SM-T330NUs apparently.
Still, M, thank you for your work on the device. If you can link me to directions on how to pull a recovery.log or boot.img or whatever you may need to include the milletwifiue, I'd be glad to. If you've already posted those directions and I missed them, point me to the post.
Can you make one for smt331
Dewang rocky said:
Can you make one for smt331
Click to expand...
Click to collapse
D,
hi, try this version, flash via odin. http://d-h.st/de2u click the download now button.
the name of the file is sm-t331-Philz-6_58_9-recovery-round1.tar
m
xnatex21 said:
Pulling this conversation into the right thread.
I have the milletwifiUE SM-T330NU. This recovery wouldn't flash on it. The title is misleading b/c this recovery isn't for all of the SM-T330NU devices. Since it wouldn't flash, there isn't any harm done, but having read almost every other thread in the Tab 4 forum, I'd suggest pointing out the code name of each device is important in the OP. There are differences between the SM-T330NUs apparently.
Still, M, thank you for your work on the device. If you can link me to directions on how to pull a recovery.log or boot.img or whatever you may need to include the milletwifiue, I'd be glad to. If you've already posted those directions and I missed them, point me to the post.
Click to expand...
Click to collapse
The recovery is for the milletwifi sm-t330nu, again if you read the op you will see the codename clearly stated in the posted default.prop.
If i understand your issue, you either attempted to flash this recovery's .zip installation from another recovery, or you attempted to flash
a modified repackaged "stock" rom in which, during the process, the assert in the updater-script determined your device to be incorrect.
In which case your custom rom and/or previous custom recovery are in error.
I say this bluntly yet, without malice, I have done this before and have a fairly good handle on it. I would certainly modify a version for you
if you provide me with the actual original stock boot or recovery image for your device. Images from custom/modded roms will not do.
m
moonbutt74 said:
The recovery is for the milletwifi sm-t330nu, again if you read the op you will see the codename clearly stated in the posted default.prop.
If i understand your issue, you either attempted to flash this recovery's .zip installation from another recovery, or you attempted to flash
a modified repackaged "stock" rom in which, during the process, the assert in the updater-script determined your device to be incorrect.
In which case your custom rom and/or previous custom recovery are in error.
I say this bluntly yet, without malice, I have done this before and have a fairly good handle on it. I would certainly modify a version for you
if you provide me with the actual original stock boot or recovery image for your device. Images from custom/modded roms will not do.
m
Click to expand...
Click to collapse
If I'm one of the only people that would benefit from it, lets not worry about it. At this point I don't have the stock recovery b/c I flashed twrp first and then tried to flash this.
I see you did post the code name in the OP but I think it would help to point out that there are sm-t330nu variants, like mine. Coming from years of flashing, I know most people here are used to checking model #s that are posted in the title. Its very unusual to get a model with different code names and not a different carrier, in this case wifi (as opposed to Verizon ot Sprint etc).
Edit: typos
X,
hi,
the ue thing is weird, , i am wondering if my tab might have been a refurbished device.
this should do you, it the same recovery adjusted to milletwifiue
Derp on me, sorry https://www.androidfilehost.com/?fid=95887005526787734
the name of the file is sm-t330nu-Philz-6_58_9-milletwifiue-recovery.zip
I'll add it to OP and make an edit. Let me know if you have an issue.
m
moonbutt74 said:
X,
hi,
the ue thing is weird, , i am wondering if my tab might have been a refurbished device.
this should do you, it the same recovery adjusted to milletwifiue
https://www.androidfilehost.com/?fid=95887005526787126
I'll add it to OP and make an edit. Let me know if you have an issue.
m
Click to expand...
Click to collapse
M,
I flashed it in twrp .3 and it failed. It didn't give me the wrong device error though.
My device is a refurb too. I pulled this from bug report, not sure if it helps:
milletwifiue-user 4.4.2 KOT49H T330NUUEU1ANCA
Had the phone for 2 weeks. without being rooted it is so boring! Please any devs come up with a custom recovery soon
htcmusic said:
Had the phone for 2 weeks. without being rooted it is so boring! Please any devs come up with a custom recovery soon
Click to expand...
Click to collapse
that's why i gave mine to my wife, she doesn't like root. not positive this device will really get alot of development.
fix-this! said:
that's why i gave mine to my wife, she doesn't like root. not positive this device will really get alot of development.
Click to expand...
Click to collapse
Guys the device was just launched. Right now I'm working on teaming up with Brinly Taylor so we can develop for this.
Moto e 3g Variant boot.img and recovery.img
give me the following and i will try to compile a custom recovery
- boot.img(from 3g variant)
-recovery.img(from 3g variant)
Saumitra Yadav said:
give me the following and i will try to compile a custom recovery
- boot.img(from 3g variant)
-recovery.img(from 3g variant)
Click to expand...
Click to collapse
I have this model. But when i try to extract boot.img from adb shell. it says access denied, and when i type su the it says not found . any idea how this can be resolved.
We seem to have a chicken and egg problem here. We need a custom recovery to get root, but we need root to get the bits to make a custom recovery. I'll try to make something when I have time, but I don't have a device to test with, so I'll need the community's help to test.
squid2 said:
We seem to have a chicken and egg problem here. We need a custom recovery to get root, but we need root to get the bits to make a custom recovery. I'll try to make something when I have time, but I don't have a device to test with, so I'll need the community's help to test.
Click to expand...
Click to collapse
Well i have this 3g variant of moto e 2015. I am ready to help but i am new to all this stuff. Yesterday i pulled system.img but can't pull boot image.
Ravx said:
Well i have this 3g variant of moto e 2015. I am ready to help but i am new to all this stuff. Yesterday i pulled system.img but can't pull boot image.
Click to expand...
Click to collapse
I made something. I have no clue if it will work. Things usually don't work on the first try, but we have to start somewhere. Try this at your own risk. I'm not responsible for bricking your phone. I don't have a Moto E 3G to test with.
As a good first test with this recovery, try flashing SuperSU: http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1
TWRP for 3G Model only! Flash at your own risk! Completely untested first attempt!
Download link for my test recovery: http://www.mediafire.com/download/uple1nxzzpg1cb5/otus_twrp-2.8.6-untested.img
To install:
Code:
fastboot flash recovery otus_twrp-2.8.6-untested.img
EDIT: Don't use this image, it's too big and I've identified other issues.
Ravx said:
I have this model. But when i try to extract boot.img from adb shell. it says access denied, and when i type su the it says not found . any idea how this can be resolved.
Click to expand...
Click to collapse
This will be possible only when moto release sources,
squid2 said:
I made something. I have no clue if it will work. Things usually don't work on the first try, but we have to start somewhere. Try this at your own risk. I'm not responsible for bricking your phone. I don't have a Moto E 3G to test with.
As a good first test with this recovery, try flashing SuperSU: http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1
TWRP for 3G Model only! Flash at your own risk! Completely untested first attempt!
Download link for my test recovery: http://www.mediafire.com/download/uple1nxzzpg1cb5/otus_twrp-2.8.6-untested.img
To install:
Code:
fastboot flash recovery otus_twrp-2.8.6-untested.img
Click to expand...
Click to collapse
I had someone try it and found out that the image is too big. I will post a smaller one that should fit when I find time. I'll need to create a stripped down kernel and device tree for otus. To do that, I'd probably need my own device to test on. The 3G model is unavailable in Canada, but for the sake of the community, I've ordered a 3G model from abroad, at a cost much greater than what it is worth, so that I have a unit to test on. My test unit won't arrive for another week I'd expect.
squid2 said:
I had someone try it and found out that the image is too big. I will post a smaller one that should fit when I find time. I'll need to create a stripped down kernel and device tree for otus. To do that, I'd probably need my own device to test on. The 3G model is unavailable in Canada, but for the sake of the community, I've ordered a 3G model from abroad, at a cost much greater than what it is worth, so that I have a unit to test on. My test unit won't arrive for another week I'd expect.
Click to expand...
Click to collapse
Thankyou so much squid bro, you are great . Please make a new thread for moto e 3g 2015 version in which all the development and testing work will be carried out. I thought that i have made wrong descision by buying Moto E 3g version because of no dev support. You are a life saver bro.....
As far as testing goes , I am in.....:good:
Ravx said:
Thankyou so much squid bro, you are great . Please make a new thread for moto e 3g 2015 version in which all the development and testing work will be carried out. I thought that i have made wrong descision by buying Moto E 3g version because of no dev support. You are a life saver bro.....
As far as testing goes , I am in.....:good:
Click to expand...
Click to collapse
Here goes my second attempt. I've tried to backport my Linux 3.10.74 based "Squid Kernel" to the 3G Moto E. This is a rather crazy idea, and I don't think anyone has ever done this for the MSM8x10 family. I've managed to create a kernel binary that is half the size of the stock kernel. I don't expect this recovery to boot at all. If it does boot, I would be quite pleased.
Download link for the adventurous: https://www.mediafire.com/?j5wgj035ml7nng9
I'd suggest first trying fastboot boot twrp-otus-2.8.6-test2.img before you flash it, since it is experimental and probably won't work. If it does boot, check the file manager to see if it is able to view all your data. If it boots and is able to see your data, then we have a miracle, so go ahead and flash it if you'd like.
If this recovery doesn't boot, don't worry, I will make a recovery that works, just be patient. I'm waiting for my test unit to arrive. It's been crawling along through the USPS. Hopefully, I'll have it by this time next week.
REMINDER: This is totally untested, and probably won't work. Try at your own risk. Make sure to try booting it with "fastboot boot" before flashing it. This might brick your device. Be careful. Even if it appears to work, I don't recommend flashing anything with this recovery until I receive my test device and properly verify it.
P.S. I'll make a new thread once I have something that works.
squid2 said:
Here goes my second attempt. I've tried to backport my Linux 3.10.74 based "Squid Kernel" to the 3G Moto E. This is a rather crazy idea, and I don't think anyone has ever done this for the MSM8x10 family. I've managed to create a kernel binary that is half the size of the stock kernel. I don't expect this recovery to boot at all. If it does boot, I would be quite pleased.
Download link for the adventurous: https://www.mediafire.com/?j5wgj035ml7nng9
I'd suggest first trying fastboot boot twrp-otus-2.8.6-test2.img before you flash it, since it is experimental and probably won't work. If it does boot, check the file manager to see if it is able to view all your data. If it boots and is able to see your data, then we have a miracle, so go ahead and flash it if you'd like.
If this recovery doesn't boot, don't worry, I will make a recovery that works, just be patient. I'm waiting for my test unit to arrive. It's been crawling along through the USPS. Hopefully, I'll have it by this time next week.
REMINDER: This is totally untested, and probably won't work. Try at your own risk. Make sure to try booting it with "fastboot boot" before flashing it. This might brick your device. Be careful. Even if it appears to work, I don't recommend flashing anything with this recovery until I receive my test device and properly verify it.
P.S. I'll make a new thread once I have something that works.
Click to expand...
Click to collapse
Ok probably a noob qiestion. But does booting recovery from adb makes any changes to my device. Is there a probabilty of soft bricking the device by this method.
And should the boot loader be unlocked before trying this.
Ravx said:
Ok probably a noob qiestion. But does booting recovery from adb makes any changes to my device. Is there a probabilty of soft bricking the device by this method.
And should the boot loader be unlocked before trying this.
Click to expand...
Click to collapse
You need an unlocked bootloader. First boot your device into bootloader mode (turn phone off, press and hold PWR and VOL- together for 3 seconds, then let go). You will see a bootloader menu. Then use fastboot on your computer to boot the recovery.
Running "fastboot boot xyz.img" will not make any changes to your device. As long as you don't flash anything with the recovery, it's fairly safe to try. Booting it up and browsing with the file manager shouldn't hurt anything. Note that when you try to leave recovery, TWRP will ask you if you want to root your device with SuperSU. If you want to be safe, read the screen carefully and make sure you say no for now.
The risky operation would be to flash the recovery (fastboot flash xyz.img) and then use the recovery to flash other ROMs or customizations. I would not recommend doing this if you don't have enough experience or are worried about messing up your phone.
squid2 said:
You need an unlocked bootloader. First boot your device into bootloader mode (turn phone off, press and hold PWR and VOL- together for 3 seconds, then let go). You will see a bootloader menu. Then use fastboot on your computer to boot the recovery.
Running "fastboot boot xyz.img" will not make any changes to your device. As long as you don't flash anything with the recovery, it's fairly safe to try. Booting it up and browsing with the file manager shouldn't hurt anything. Note that when you try to leave recovery, TWRP will ask you if you want to root your device with SuperSU. If you want to be safe, read the screen carefully and make sure you say no for now.
The risky operation would be to flash the recovery (fastboot flash xyz.img) and then use the recovery to flash other ROMs or customizations. I would not recommend doing this if you don't have enough experience or are worried about messing up your phone.
Click to expand...
Click to collapse
Sorry bro but it is not booting. The steps i followed
1.) unlocked bootloader ( Success ...getting unlock msg when booting
2.) got to bootloader.
3.)booted the recovery ( i changed the name of recovery to "recovery" for convinience)
4.) cmd showed msg booting but the phone shows android logo and does not act from there.
5. I had to reboot the phone by pressing power button for 10 secs.
Have i done anything wrong????
Ravx said:
Sorry bro but it is not booting. The steps i followed
1.) unlocked bootloader ( Success ...getting unlock msg when booting
2.) got to bootloader.
3.)booted the recovery ( i changed the name of recovery to "recovery" for convinience)
4.) cmd showed msg booting but the phone shows android logo and does not act from there.
5. I had to reboot the phone by pressing power button for 10 secs.
Have i done anything wrong????
Click to expand...
Click to collapse
It might just be that it doesn't work, but your comment about it showing the Android logo doesn't sound right. Does it show a "dead" android logo laying on its back with a door open on its body? If you see that, you booted up the stock recovery. The stock recovery will show that logo forever until you use a certain button combo to bring up a menu.
How did you boot the recovery? I assume you downloaded my file, renamed it to "recovery.img", and then ran this command from the folder that contains my recovery image:
Code:
fastboot boot recovery.img
squid2 said:
It might just be that it doesn't work, but your comment about it showing the Android logo doesn't sound right. Does it show a "dead" android logo laying on its back with a door open on its body? If you see that, you booted up the stock recovery. The stock recovery will show that logo forever until you use a certain button combo to bring up a menu.
How did you boot the recovery? I assume you downloaded my file, renamed it to "recovery.img", and then ran this command from the folder that contains my recovery image:
Code:
fastboot boot recovery.img
Click to expand...
Click to collapse
No it showed the logo of moto powered by android and yes i renamed the file and entered the same command you typed.
As soon as i typed it. It showed that logo and got hanged. And then i rebooted. And it booted normally.
Ravx said:
No it showed the logo of moto powered by android and yes i renamed the file and entered the same command you typed.
As soon as i typed it. It showed that logo and got hanged. And then i rebooted. And it booted normally.
Click to expand...
Click to collapse
I had someone else try it too, with the same result as you. No big surprise to me, didn't expect it to work. I'll make one with a more conventional 3.4.x kernel when I get time.
Otus TWRP Attempt 3
@Ravx
Alright everyone, I've made a third attempt at creating a recovery for the Moto E 3G. I still don't have the device, so you have to test yourself. I made this one with a more conventional 3.4.x kernel. I would guess that this recovery is more likely to work than the the previous one. As before, try fastboot boot xyz.img before flashing. I suspect that this recovery might boot sometimes and fail other times. If it fails to be boot the first time, try a couple more times before giving up.
Download Link: http://www.mediafire.com/download/1he2ys1832441s7/twrp-otus-2.8.6-test3.img
If it boots, try using the file manager. Check that it is able to see all your files. I don't recommended using this recovery to flash things until I'm able to verify it myself.
Try at your own risk. I'm not responsible for messing up your device. This recovery has not been tested.
squid2 said:
@Ravx
Alright everyone, I've made a third attempt at creating a recovery for the Moto E 3G. I still don't have the device, so you have to test yourself. I made this one with a more conventional 3.4.x kernel. I would guess that this recovery is more likely to work than the the previous one. As before, try fastboot boot xyz.img before flashing. I suspect that this recovery might boot sometimes and fail other times. If it fails to be boot the first time, try a couple more times before giving up.
Download Link: http://www.mediafire.com/download/1he2ys1832441s7/twrp-otus-2.8.6-test3.img
If it boots, try using the file manager. Check that it is able to see all your files. I don't recommended using this recovery to flash things until I'm able to verify it myself.
Try at your own risk. I'm not responsible for messing up your device. This recovery has not been tested.
Click to expand...
Click to collapse
Bro you have done it. the recovery booted and i moved a file from one folder to another by using file manager. :good::good::laugh:
EDIT: For now i the recovery's file manager isnt showing "build.prop" and other folders in /system
only the "bin" folder is visible. Is it ok beacaause we havent flashed the recovery or its the other way around.
Here's the latest release 6.2.8.1_r3_4054 of the pre-rooted rom I've combined into one patched ota removed zip which packs the downgraded older interface with accessibility settings working again. After flashing, clear data in settings/applications/Appstore to prevent issues with apps and reboot.
There's no bugs in this rom that I know of.
No efuse is present in this rom and is completely safe to flash. Remember to not flash stock images that are 6.2.8.0 and higher. Only flash the pre-rooted roms from @rbox so that the efuse doesn't burn.
Nothing is removed in this rom, only re-edited for system app downgrades that include the com.amazon.tv.launcher (KFTV launcher), com.amazon.tv.settings.v2 (Amazon Settings), and lastly, com.amazon.venezia (Appstore) with options to hide cloud apps, to adjust AV Sync Tuning, as well with the Wi-Fi icons when connecting wirelessly altogether with the older interface.
Things that don't work
Amazon FreeTime
Profiles
Some apps that recognize a bootloader is unlocked and forcibly closes i.e Peacock TV
OTA updates?? Of course ota updates no longer work. This rom removes the fota and any type of updates from occurring
Amazon Live Shopping (The app does work, but the older UI somehow doesn't recognize it as one)
For those that prefer using the newer interface with the same patches, download this rom from this link:
https://forum.xda-developers.com/attachments/6-2-8-1_r3_4054_patched-zip.5425403/
I created 6.2.9.5 for (mantis) with a patched DeviceSoftwareOTA that never updates the system ever again and I used the pre-rooted 6.2.8.1 updater-script to remove the ewriter and efuse_check.sh. I'll need help making the accessibility patches. More are to follow with testings of the older interface and features removed within the newer software.
Is eFuse removed in the firmware?
9lalex9 said:
Is eFuse removed in the firmware?
Click to expand...
Click to collapse
I'm sure it is. I double checked the updater-script and it says this
(getprop("ro.product.device") == "mantis" || getprop("ro.build.product") == "mantis") || abort("This package is for \"mantis\" devices
this is a \"" + getprop("ro.product.device") + "\".");
ifelse(is_mounted("/system"), unmount("/system"));
package_extract_dir("install", "/tmp");
set_metadata("/tmp/backuptool.sh", "uid", 0, "gid", 0, "mode", 0755);
mount("ext4", "EMMC", "/dev/block/platform/soc/11230000.mmc/by-name/system", "/system", "");
run_program("/tmp/backuptool.sh", "backup");
unmount("/system");
ui_print("Copying system image...");
block_image_update("/dev/block/platform/soc/11230000.mmc/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");
ui_print("Copying vendor image...");
block_image_update("/dev/block/platform/soc/11230000.mmc/by-name/vendor", package_extract_file("vendor.transfer.list"), "vendor.new.dat", "vendor.patch.dat");
mount("ext4", "EMMC", "/dev/block/platform/soc/11230000.mmc/by-name/system", "/system", "");
delete("/system/bin/efuse_check.sh",
"/system/bin/ewriter");
unmount("/system");
ui_print("Copying kernel...");
package_extract_file("boot.img", "/dev/block/platform/soc/11230000.mmc/by-name/boot");
package_extract_dir("magisk", "/dev/tmp/install");
set_metadata("/dev/tmp/install/install-magisk.sh", "uid", 0, "gid", 0, "mode", 0755);
run_program("/dev/tmp/install/install-magisk.sh");
mount("ext4", "EMMC", "/dev/block/platform/soc/11230000.mmc/by-name/system", "/system", "");
run_program("/sbin/mkdir", "/system/addon.d");
run_program("/tmp/backuptool.sh", "restore");
unmount("/system");
Whereas with the original stock 6.2.8.0_3236, it activates some type of blocklist from Amazon without the disable efuse_check in this updater-script:
So to answer your question, yes it disables the efuse in the modded rom. The script is important when flashing zips and why only flashing rbox's pre-rooted roms are necessary. He edits the scripts from the stock rom to make it compatible with rooted 4K devices so the efuse stays disabled under that line he added above.
So in conclusion, when you extract the pre-rooted rom, you'll see the META-INF/com/ without all the Amazon stuff added to it to make it disable the efuse under their scripts because these scripts tell the operating system to block anything from being modified
getprop("ro.product.device") == "mantis" || abort("E3004: This package is for \"mantis\" devices; this is a \"" + getprop("ro.product.device") + "\".");
ui_print("Target: Amazon/mantis/mantis:6.0/NS6280/3236N:user/amz-p,release-keys");
show_progress(0.650000, 0);
ui_print("Patching system image unconditionally...");
block_image_update("/dev/block/platform/soc/11230000.mmc/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat") ||
abort("E1001: Failed to update system image.");
show_progress(0.100000, 0);
ui_print("Patching vendor image unconditionally...");
block_image_update("/dev/block/platform/soc/11230000.mmc/by-name/vendor", package_extract_file("vendor.transfer.list"), "vendor.new.dat", "vendor.patch.dat") ||
abort("E2001: Failed to update vendor image.");
show_progress(0.050000, 5);
package_extract_file("boot.img", "/dev/block/platform/soc/11230000.mmc/by-name/boot");
show_progress(0.200000, 10);
package_extract_file("images/logo.bin", "/dev/block/platform/soc/11230000.mmc/by-name/logo");
package_extract_file("images/lk.bin", "/dev/block/platform/soc/11230000.mmc/by-name/lk");
package_extract_file("images/tz.img", "/dev/block/platform/soc/11230000.mmc/by-name/tee1");
package_extract_file("images/tz.img", "/dev/block/platform/soc/11230000.mmc/by-name/tee2");
package_extract_file("images/preloader.img", "/dev/block/platform/soc/11230000.mmc/mmcblk0boot0");
package_extract_file("META-INF/com/amazon/android/target.blocklist", "/cache/recovery/last_blocklist");
set_metadata("/cache/recovery/last_blocklist", "uid", 0, "gid", 0, "mode", 0444, "capabilities", 0x0);
set_progress(1.000000);
Skel40 said:
I'm sure it is. I double checked the updater-script
Click to expand...
Click to collapse
Afaik the efuse doesn't burn during ROM flashing (i.e. you can't find the efuse burning in the updater scripts).
Afaik it can only burn, if TZ gets an update during ROM flashing, then the efuse gets burned at the next reboot (only possible in case of a locked Stick = stock recovery).
But as you know, for an unlocked stick, TWRP recovery will block updating/flashing TZ to tee1 and 2, same for LK and PL images. No LK/TZ updates = no fuse burning
I think @9lalex9 asked about what rbox did with his last prerooted, cuz rbox removed the kernel script that burns the efuse in the boot.img of his prerooted Rom. This is not needed as long as TWRP is always there, but it if you like you can do it too. Maybe ask @Pretoriano80 I guess he can tell you some detailed things about the kernel Another way may be to grab the prerooted rom as source for your modded rom...
Skel40 said:
Added back the old interface because the new ui is horrendous.
Click to expand...
Click to collapse
Yes. You're right, it's awful, the most terrible thing they did in the last years^^
So keep going on with this, please
Skel40 said:
I'd like to introduce you all rooted Fire TV Stick 4K users a mod I've been working on to get the old interface back on your devices without the new interface. In this beta release, you will find the old interface on this version and the current version of this stock rom is 6.2.8.0_3236. Everything works. Apps install just fine as if you were on the previous OS, 6.2.7.7. What you'll also find in this mod is notable improvements in performance. Before doing any changes to your Fire TV Stick 4K, make a full backup of your system and data before proceeding. Flash this zip in TWRP after wiping everything in recovery. Be sure to block updates so the old ui isn't overwritten with the new ui.
Bugs:
The UI will lag occasionally, don't know what's causing this issue. This isn't really considered a bug but the 'Who's watching Fire TV' screen will appear without the actual icon because of this being an older launcher.
Notes:
Added back the old interface because the new ui is horrendous. I can't even go to my apps like I would before so this mod prevents me from staying on an older OS. What I've done with this mod is very simple. Amazon only updated the interface so I downgraded back to a previous version with AV Sync Tuning as well with the Wi-Fi Icons. Feel free to leave any feedback about adding or removing features if this rom isn't working right and please report any bugs.
The efuse is also disabled with this rom. It's found in the script to disable the efuse_check.
Requirements: A rooted and unlocked Fire TV Stick 4K without the eFuse chip blown after 6.2.7.7, basic knowledge that this stock modded rom is beta so there will be a few bugs.
Official Modded Pre-Rooted Rom Latest (6.2.8.0_3236):
Click to expand...
Click to collapse
Can you also fix Accessibility? Only thing which is keeping me from upgrading
@
Sus_i[EDIT]
So I was thinking of patching to fix Accessibility,
I have deodexed the ROMs and I was thinking of following few approaches.
1. Replace logan
2. Replace Services with older version
3. Try to patch the jar of Services.
Even though i have some experience with smali jar and basic stuff but i have no experience with binary files.
Now i have some questions relating some problems.
Changing stuff in TWRP does not affect the System
So i have to find a way to flash without taking to much time.
And what's the matter with efuse??
On which version does it blow up and what are the caveats?
Hi again,
I have patched this file (fosservices.jar) its from 6.2.7.3, can anyone check if it fixes accessibility.
SweenWolf said:
Hi again,
I have patched this file (fosservices.jar) its from 6.2.7.3, can anyone check if it fixes accessibility.
Click to expand...
Click to collapse
Where can I overwrite this file? 6.2.7.3 patches accessibility. Get the file from 6.2.7.1. I'm glad to test it out rn
Skel40 said:
Where can I overwrite this file? 6.2.7.3 patches accessibility. Get the file from 6.2.7.1. I'm glad to test it out rn
Click to expand...
Click to collapse
replace this with /system/framework/fosservices.jar , there should also be an odex file in /system/framework/oat/arm/fosservices.odex (delete this file).
this file is from 6.2.7.3 where accessibility services are restricted to system apps only.
on 6.2.7.1 there is no such restriction.
if you are on 6.2.7.1 then theres no need to test because accessibility works just fine. i need to test this on newer version, and i am also unable to download your zip file for whatever reason. if i had then i could have gave you patched version from 6.2.8.0
The reason why I am not doing is because i have removed root and TWRP.
if this worked on 6.2.8.0 then i will update to that using TWRP, remove OTA apps, and patch this file and lock the bootloader again.
[Question] If i relock the bootloader and it replaces the boot image with stock one. will it blow the efuse?
SweenWolf said:
replace this with /system/framework/fosservices.jar , there should also be an odex file in /system/framework/oat/arm/fosservices.odex (delete this file).
this file is from 6.2.7.3 where accessibility services are restricted to system apps only.
on 6.2.7.1 there is no such restriction.
if you are on 6.2.7.1 then theres no need to test because accessibility works just fine. i need to test this on newer version, and i am also unable to download your zip file for whatever reason. if i had then i could have gave you patched version from 6.2.8.0
The reason why I am not doing is because i have removed root and TWRP.
if this worked on 6.2.8.0 then i will update to that using TWRP, remove OTA apps, and patch this file and lock the bootloader again.
[Question] If i relock the bootloader and it replaces the boot image with stock one. will it blow the efuse?
Click to expand...
Click to collapse
Thanks for getting back to me. That's strange. It's downloading fine on my end. I'll try to upload it on mega or something like that. That's not recommended. Any OS after 6.2.7.7 will blow the efuse on a locked bootloader so the exploit is no longer working unless you kept your device in an unlocked state like mine. I own 3 4K's fully unlocked with 6.2.7.7 because of older easy to navigate ui and the efuse being disabled as well thanks to TWRP. Once you're unlocked you're safe. What I should recommend instead is getting one of the latest pre-rooted roms available due to the efuse check being removed then replace the boot.img. Don't update with the official stock version as that will keep your device locked for good. No bootrom to access anymore. It's impossible so if you want to take the risk go ahead but I don't advise doing so.
Skel40 said:
Thanks for getting back to me. That's strange. It's downloading fine on my end. I'll try to upload it on mega or something like that. That's not recommended. Any OS after 6.2.7.7 will blow the efuse on a locked bootloader so the exploit is no longer working unless you kept your device in an unlocked state like mine. I own 3 4K's fully unlocked with 6.2.7.7 because of older easy to navigate ui and the efuse being disabled as well thanks to TWRP. Once you're unlocked you're safe. What I should recommend instead is getting one of the latest pre-rooted roms available due to the efuse check being removed then replace the boot.img. Don't update with the official stock version as that will keep your device locked for good. No bootrom to access anymore. It's impossible so if you want to take the risk go ahead but I don't advise doing so.
Click to expand...
Click to collapse
Thanks, I was reading other post on XDA where people are stuck with locked bootloader on 6.2.8.0, I do not do OTA updates, and I certainly don't update without assurance that my apps work fine on it. i was thinking of getting an image and make some changes by removing the efuse binaries from bin and also was thinking of unlocking ADB on Boot.img and if found removing efuse from there, the thing is i have to patch boot.img as my stick becomes unstable with TWRP. but for now I just wanted to go 6.2.7.3 and check if everything goes right i will stay on it else jump back to 6.2.7.1
Sorry for bothering you, what version introduced profile in FireTV?
SweenWolf said:
Thanks, I was reading other post on XDA where people are stuck with locked bootloader on 6.2.8.0, I do not do OTA updates, and I certainly don't update without assurance that my apps work fine on it. i was thinking of getting an image and make some changes by removing the efuse binaries from bin and also was thinking of unlocking ADB on Boot.img and if found removing efuse from there, the thing is i have to patch boot.img as my stick becomes unstable with TWRP. but for now I just wanted to go 6.2.7.3 and check if everything goes right i will stay on it else jump back to 6.2.7.1
Sorry for bothering you, what version introduced profile in FireTV?
Click to expand...
Click to collapse
That makes sense! I don't update thru ota either. This is off topic but do you know why updating the settings V2 app on 6.2.7.1 won't do anything to add av sync tuning and wifi icons by any chance? It acts like an update but doesn't add those features in. Maybe it's the .jar files? I also have a slight issue with my old UI rom too. Its laggy as if something heavy is running in the background. Do you think I should run a logcat? I'll need to upload the rom to mega for you to see and possibly fix. The version that introduced profiles was 6.2.8.0_3233
@SweenWolf I tried the .jar file. It bootloops on version 6.2.8.0_3236
Skel40 said:
@SweenWolf I tried the .jar file. It bootloops on version 6.2.8.0_3236
Click to expand...
Click to collapse
Thanks for trying but this is to be installed on 6.2.7.3 not 6.2.8.0, I thought you had that, let me download the app from mega and then patch the file of 6.2.8.0
SweenWolf said:
Thanks for trying but this is to be installed on 6.2.7.3 not 6.2.8.0, I thought you had that, let me download the app from mega and then patch the file of 6.2.8.0
Click to expand...
Click to collapse
My fault. I should've paid attention..
Skel40 said:
That makes sense! I don't update thru ota either. This is off topic but do you know why updating the settings V2 app on 6.2.7.1 won't do anything to add av sync tuning and wifi icons by any chance? It acts like an update but doesn't add those features in. Maybe it's the .jar files? I also have a slight issue with my old UI rom too. Its laggy as if something heavy is running in the background. Do you think I should run a logcat? I'll need to upload the rom to mega for you to see and possibly fix. The version that introduced profiles was 6.2.8.0_3233
Click to expand...
Click to collapse
i haven't checked but as far as i know, the actual code is in the settings V2, but the shortcuts are embedded in the amazon launcher, so there will be two icons in two different places one in the network activity of the Settings apk where as the other is on Amazon Launcher itself.
Skel40 said:
My fault. I should've paid attention..
Click to expand...
Click to collapse
here is the patched version from the rom you provided.
try this one and make sure you have given correct permissions i.e. 644
SweenWolf said:
Thanks, I was reading other post on XDA where people are stuck with locked bootloader on 6.2.8.0, I do not do OTA updates, and I certainly don't update without assurance that my apps work fine on it. i was thinking of getting an image and make some changes by removing the efuse binaries from bin and also was thinking of unlocking ADB on Boot.img and if found removing efuse from there, the thing is i have to patch boot.img as my stick becomes unstable with TWRP. but for now I just wanted to go 6.2.7.3 and check if everything goes right i will stay on it else jump back to 6.2.7.1
Sorry for bothering you, what version introduced profile in FireTV?
Click to expand...
Click to collapse
People stuck with locked bootloader on 6.2.8.0 most likely never unlocked it before updating to 6.2.8.0.
Devices unlocked previously, before 6.2.8.0 are fine, unless you restore everything to stock, including boot, recovery, bootloader, and tz.
Also, as long as you keep TWRP (i don't know why you removed yours) then you are pretty safe, even if you install a full stock rom (TWRP has a failsafe mechanism which prevents flashing the critical images (recovery, tz, and bootloader).
As for modifying the boot image, there's not much to do, just disabling the efuse_check or anything efuse related from the ramdisk.
Pretoriano80 said:
People stuck with locked bootloader on 6.2.8.0 most likely never unlocked it before updating to 6.2.8.0.
Devices unlocked previously, before 6.2.8.0 are fine, unless you restore everything to stock, including boot, recovery, bootloader, and tz.
Also, as long as you keep TWRP (i don't know why you removed yours) then you are pretty safe, even if you install a full stock rom (TWRP has a failsafe mechanism which prevents flashing the critical images (recovery, tz, and bootloader).
As for modifying the boot image, there's not much to do, just disabling the efuse_check or anything efuse related from the ramdisk.
Click to expand...
Click to collapse
Thanks for the info, my stick randomly reboots itself if i have TWRP installed.
And File Manager of TWRP had no affect on the System partition (for me atleast)
And I also always has a pendrive attached with the stick with some movies and videos on it.
Which cause boot delay also because it waits for TWRP.
I upgraded to 6273 and there was no Accessibility, so i had to unlock the bootloader once again to go back to 6271.
I use many apps which requires Accessibility like and two main ones are for Launcher and for Mouse Services.
As i don't use google play services or make any changes to the system and with 6271 being last version to support Accessibility i decided to stick with it and just disable updates. And relocked the bootloader, because i had no use of TWRP anymore. Until now, if Accessibility is fixed i might upgrade.
But like you said, it burns the fuse when we update the TZ and that can only be updated by the recovery, TWRP will never update the TZ so we are safe, but even the stock recovery needs an update package to flash the TZ right?
Because of the script it will delete the efuse check and ewriter then it will not blow the fuse, Just like in OP.
Even if i then relock the bootloader, and the updates will be blocked to the system, because there are some update apps which sideloads the OTA package (i read their codes) then if their are no offline update file present in the system how will the stock recovery flash the TZ.
I'm just asking, i know amazon also has some tricks under their sleeves and they can do something notorious.
I confirm Accessibility works on 6.2.8.0 3236. Thanks @SweenWolf
I used Total Commander for chmod without commands too
Skel40 said:
I confirm Accessibility works on 6.2.8.0 3236. Thanks @SweenWolf
I used Total Commander for chmod without commands too
Click to expand...
Click to collapse
Good to hear, one more question. How have you disabled the OTA check, i was thinking of patching OTA files also