Database Info

[Q] Removing CWM / Restoring Stock Recovery

Hello everyone,
after only one day my Desire S is starting to make trouble. The Softkeys are not working anymore
I used the HTC Unlocker, so my warranty is gone. But I contacted HTC and they said it's no problem as long as I haven't changed the ROM (I would like to know what the ROM has to do with the fact that the Touchscreen is not working correctly anymore)
Luckily I did a backup of the Stock Rom with CWM, so I have the original ROM. Now I would like to change back to the Stock Recovery, so how can I remove CWM? I tried to install a RUU but it didn't work. Are there any other possibilities?

@klausewitz23
I have my doubts if your backup will work..... There was a case the other day where the backup would not work (see here), basically the (assumption) problem is do to with the new lib (library) partition of hboot 2.00.0002.
So IF it does not work (also make a backup of your current ROM) then read on.
It was suggested to try flash the PG88IMG.zip from this thread (it has a leaked lib img) but it wasn't attempted so I don't know if it will work.
If you do attempted it do it this way; restore your backup, then place the PG88IMG.zip on your SDCARD and try flash it in your hboot.
The only other alternative is to restore your phone with a RUU.
_________________________________________
The new lib partition is required for sense 3.0, thus the reason why your backup most likely won't work (the lib is not backed up currently, however the 4ext developer has added it recently).
Old hboot has the table;
/dev/block/mmcblk0p25 /system
/dev/block/mmcblk0p26 /data
/dev/block/mmcblk0p27 /cache
/dev/block/mmcblk0p28 /devlog
Click to expand...
Click to collapse
and the new one is;
/dev/block/mmcblk0p25 /system
/dev/block/mmcblk0p26 /data
/dev/block/mmcblk0p27 /cache
/dev/block/mmcblk0p28 /system/lib
/dev/block/mmcblk0p30 /devlog
Click to expand...
Click to collapse

4ext does now have the functionality to backup and restore lib partition, but it needs to be enabled in options
Swyped from my Desire S using XDA Premium

So as I thought, it's not so easy to go back. I will try to convince the HTC Support that it really has nothing to do with the software, maybe they will have mercy (when I press the touchscreen at the spot were the Search Softkey is and power on the phone than everything works fine. After putting my finger away it works for a couple of minutes until the same problem occurs again. the Screen is just loose on this spot and that's the problem )
Thank you for your advice!

@klausewitz23
Still easy enough, if you rather avoid this lib partition and flashing things like recovery and lib, and restoring your backup then a RUU (and eng hboot) is your only option.
Run the fastboot command 'fastboot command getvar all' and post the result (don't forget to remove the serial+imei) Then I will direct you to a RUU and how to.

foX2delta said:
@klausewitz23
Still easy enough, if you rather avoid this lib partition and flashing things like recovery and lib, and restoring your backup then a RUU (and eng hboot) is your only option.
Run the fastboot command 'fastboot command getvar all' and post the result (don't forget to remove the serial+imei) Then I will direct you to a RUU and how to.
Click to expand...
Click to collapse
alright, I will give it a shot in a few days when I'm back home. Thank you again foX2delta!

It's been a while. I had a long discussion with the htc support with no good ending. It was dumb of me to use the official Unlocker, but whatever. I just removed the display partially, took some glue to make sure the display doesn't stick out anymore and now it's working like a charme again

klausewitz23 said:
It's been a while. I had a long discussion with the htc support with no good ending. It was dumb of me to use the official Unlocker, but whatever. I just removed the display partially, took some glue to make sure the display doesn't stick out anymore and now it's working like a charme again
Click to expand...
Click to collapse
Glue?! Now your warranty is void. Wish I'd seen your thread earlier. For a fact, the old Sense ROMs work with the new HBOOT(tried it a few times while trying to get out of sticky experiments). It's the new Sense ROMs which won't work with the old HBOOT.

[ROOT] Nexus 7 Root

I have the IO version of Nexus 7 for the next 12 hours.
Anyways, I've tried most of Nexus 7 root scripts including latest Transformer Prime, Amazon Kindle, etc...etc...
The main problem with jellybeans is that root cannot be attained through /data/local as you cannot move /data/local/tmp directory as most ICS root scripts can do.
Fastest way would be to build a ClockworkMod Recovery then flash supersu zip files. But I do not have the skills to do that, but I do have the device.
If anyone needs adb pull, let me know and also let me know how to do it.

reserved
reserved for root tomorrow hopefully, i will post some funny lol photos here.

Nexus7 root
Hi, long time no write this forum.
I uploaded root kit for Jelly beans.
you can download shell script and archives to do it.
twitter
@goroh_kun
JellyBeanGetroot.zip
https://t.co/c732G7CM
This is only for developers who can read shell script, and understand
what the script doing. It's not so difficult to understand ;-) .
---------- Post added at 07:16 PM ---------- Previous post was at 06:37 PM ----------
If anyone joinig the Google I/O 2012, I can help you to get root with your Nexus7 / GalaxyNexus(JB ver.). I'm in SF now. ( I don't need donation, but wanna be friend in same hobby !)

Thanks bud, trying this now!!! YOU ROCK!!!
goroh_kun said:
Hi, long time no write this forum.
I uploaded root kit for Jelly beans.
you can download shell script and archives to do it.
twitter
@goroh_kun
JellyBeanGetroot.zip
https://t.co/c732G7CM
This is only for developers who can read shell script, and understand
what the script doing. It's not so difficult to understand ;-) .
---------- Post added at 07:16 PM ---------- Previous post was at 06:37 PM ----------
If anyone joinig the Google I/O 2012, I can help you to get root with your Nexus7 / GalaxyNexus(JB ver.). I'm in SF now. ( I don't need donation, but wanna be friend in same hobby !)
Click to expand...
Click to collapse

(神)　what is called GOD　　:good:

script
The script didn't work so I am looking into Saurik's exploit:
https://github.com/saurik/mempodroid
If someone can just figure out how to find the offset for exit() and sysresuid() we pretty much have ROOT!
Can anyone tell me how I can find this?

Unn? I tried with newest firmware(JRN84D). and I can see # prompt in command line,
when I use "adb shell".
here is the log of the tool.
http://pastebin.com/Fka5h427
the exploit which used by mempodroid is already fixed. you can't use this tool.
thanks

Looks like somebody may have a solution over at RootzWiki... I can't post a link yet, but look for "pain in the root-n7 root" in the N7 development section.
I have no way to verify if it works... Hope this helps.

Here you go:
http://rootzwiki.com/topic/28585-cwmeasyroot-nexus-7/

jcracken said:
Here you go:
Thanks for the help! And glad you found their updated post. I noticed after I posted the name of the RootzWiki post it was already old news...
Click to expand...
Click to collapse

THANK YOU!
This is awesome, works great.
EDIT: The linked method on RootzWiki, that is. Didn't try anything else before.
DOUBLE EDIT: I can confirm that it also works on Jelly Bean on my Galaxy Nexus.

Attempted while at I/O
Download: goo.im/devs/birdman/CWM-grouper-recovery.img
After oem unlocking and rebooting....
Quote
fastboot flash recovery CWM-grouper-recovery.img
reboot immediately to recovery
to keep cwm perm:
- mount system
- adb shell
- cd /system
- mv recovery-from-boot.p recovery-from-boot.bak
for root, flash this - static.clockworkmod.com/developer/3654/3095/JB-SuperSU.zip​
I'm here at I/O on the 2nd floor trying to root both of my mobile devices. IU followed these instructions (but doing a "fastboot oem unlock" first) but after I do the flash the CWM-grouper-recovery, I volume over to "Recovery mode" on my Galaxy Nexus and select it, it reboots to a "Google" screen and just sits there forever. I've tried a few variations on the loose instructions but never with any success. Sorry if I'm missing some n00b step.
Update:
It helps if you do a "fastboot erase recovery" before flashing.
CWM-grouper-recovery.img works well for the Nexus 7 once you understand that it is touch driven. I was silly and kept using the volume rocker and power key like the old-school CWMs.
On the Galaxy Nexus S, cwm_touch_alpha2_maguro.img is the go to CWM after you've rooted. On both the "JB-SuperSU.zip" works perfectly.

zedomax said:
The script didn't work so I am looking into Saurik's exploit:
https://github.com/saurik/mempodroid
If someone can just figure out how to find the offset for exit() and sysresuid() we pretty much have ROOT!
Can anyone tell me how I can find this?
Click to expand...
Click to collapse
Now that we have the kernel source from here https://github.com/drewis/android_kernel_grouper
it looks like they have a patch in place to block zx2c4's exploit (Saurik implemented it for us, but I would still attribute it to zx2c4). It appears to be the same quick fix that was implemented on the Transformer Prime.
You can read about the original exploit here http://blog.zx2c4.com/749

sparkym3 said:
Now that we have the kernel source from here https://github.com/drewis/android_kernel_grouper
it looks like they have a patch in place to block zx2c4's exploit (Saurik implemented it for us, but I would still attribute it to zx2c4). It appears to be the same quick fix that was implemented on the Transformer Prime.
You can read about the original exploit here http://blog.zx2c4.com/749
Click to expand...
Click to collapse
So this is a security patch?

sparksco said:
So this is a security patch?
Click to expand...
Click to collapse
I'm not sure what your question is exactly, but I will still try and answer. In the new kernel that is being used on the Nexus 7, it includes a patch to block the exploit that we being referred to in that post.

I've made a guide on the forum that has worked for others. I do not see why you are all trying to find an exploit and such. It was pretty straight forward. Did it to mine, all three of my friends the third day of the conference.
http://forum.xda-developers.com/showthread.php?t=1741395

FadedLite said:
I've made a guide on the forum that has worked for others. I do not see why you are all trying to find an exploit and such. It was pretty straight forward. Did it to mine, all three of my friends the third day of the conference.
http://forum.xda-developers.com/showthread.php?t=1741395
Click to expand...
Click to collapse
The post about mempodroid was prior to anyone rooting by unlocking and flashing. I just wanted the knowledge out there that the exploit he was referring to had been patched.
Also, for some of us it is the fun of looking for those types of things and it will ultimately help secure the system in the future, as the found exploits are fixed.

When rooted can you still get OTA updates from google? Someone on here mentioned an app that let's u switch between rooting and unrooting to allow updates is that right?
Sent from my HTC One S using xda app-developers app

[Root] Republic Wireless Motorola Defy XT - Jan 28th update (1_65l_1027)

July 20th 2013
Updated with cyanide2.2, fixing bug that resulted in the su binary being deleted when extracted.
Original Release (bloggers re-source this link): http://www.androidpolice.com/2013/0...band-with-the-newest-ota-1_65k_1027-or-older/
Republic Wireless pushed a new update today, breaking the previous root I released. Here is a new root, that works on all versions of the firmware to date.
Install the app, run the app, press agree, phone will reboot twice, and then you have root. Then install supersu from the market.
APK : attached
Sourcecode: http://github.com/cunninglogic/Cyanide

So quick and easy it took 3 minutes total Thanks
jcase said:
original release (bloggers re-source this link): http://www.androidpolice.com/2013/0...band-with-the-newest-ota-1_65k_1027-or-older/
republic wireless pushed a new update today, breaking the previous root i released. Here is a new root, that works on all versions of the firmware to date.
Install the app, run the app, press agree, phone will reboot twice, and then you have root.
Apk : http://d-h.st/swm
sourcecode: http://github.com/cunninglogic/cyanide
Click to expand...
Click to collapse
thank you!

I was previously rooted on my Defy XT, and had installed busybox. Now I've updated my phone to RW latest, but you're Cyanide utility doesn't work. I'm not sure if it's perhaps busybox related issue, or some other root required app. All the binaries from before the update have stayed in the system, but something isn't running through correctly, because I'm not getting root, and SuperSU is not being installed. Any ideas?
thanks

lancethepants said:
I was previously rooted on my Defy XT, and had installed busybox. Now I've updated my phone to RW latest, but you're Cyanide utility doesn't work. I'm not sure if it's perhaps busybox related issue, or some other root required app. All the binaries from before the update have stayed in the system, but something isn't running through correctly, because I'm not getting root, and SuperSU is not being installed. Any ideas?
thanks
Click to expand...
Click to collapse
Cyanide is made to work on stock, or as stock as possible phones. Alterations surely can break it. Setup adb, get it working with the phone, then PM me.

Are there roms for this thing?

No, there are no ROM's available. You root it, there is no going "back".
However, good job jcase! I keep your cyanide on the phone, ready to launch it. Still having 30 days warranty thou.

tethering
I have the Republic defy XT and would consider rooting if I can then tether my tablet to it while out an about.
I used to have the HTC Hero and rooted with custom ROM and was able to tether my Nexus 7 (wifi version) to it via bluetooth. That gave me internet when away from wifi.
If I root the defy, will I be able to get tether working? Has anyone actually done this? Currently, bluetooth can see and pair with the phone, but won't connect.
Thanks

NO ROOT for BT Tether
jneg123 said:
I have the Republic defy XT and would consider rooting if I can then tether my tablet to it while out an about.
I used to have the HTC Hero and rooted with custom ROM and was able to tether my Nexus 7 (wifi version) to it via bluetooth. That gave me internet when away from wifi.
If I root the defy, will I be able to get tether working? Has anyone actually done this? Currently, bluetooth can see and pair with the phone, but won't connect.
Thanks
Click to expand...
Click to collapse
You do not nned to root the Defy XT to be able to tether. Download and install PDANet for
Install this on phone:
https://play.google.com/store/apps/..._apps#?t=W251bGwsMSwyLDEwOSwiY29tLnBkYW5ldCJd
Install this on tablet:
https://play.google.com/store/apps/...=W251bGwsMSwyLDEsImNvbS5wZGFuZXQudGFibGV0MiJd
The free version restricts speed and HTTPS.

nilesf said:
You do not nned to root the Defy XT to be able to tether. Download and install PDANet for
Install this on phone:
https://play.google.com/store/apps/..._apps#?t=W251bGwsMSwyLDEwOSwiY29tLnBkYW5ldCJd
Install this on tablet:
https://play.google.com/store/apps/...=W251bGwsMSwyLDEsImNvbS5wZGFuZXQudGFibGV0MiJd
The free version restricts speed and HTTPS.
Click to expand...
Click to collapse
I'll give it a shot. Thanks very much for the suggestion!

jneg123 said:
I'll give it a shot. Thanks very much for the suggestion!
Click to expand...
Click to collapse
I tried PDANet and didn't have very good luck. I can get basic internet connection for browsing but run into issues with some apps. I installed the paid version and tested to see if this would help and still no go.
I tried Google Maps and it tracked position just fine. I tried the "Layers" feature to add traffic info and had a message that there wasn't a network connection. This message came up with both the free and paid version.
"No Network Connection" came up again with Words with Friends and the Gmail apps. I didn't test further and got the refund from Google Play. I didn't want to keep testing and then not be able to get a refund.
Any other BT tethering suggestions?
thanks

Thumbs Up!
Just a thumbs up and let you know that your app worked on my RW Defy running the latest build 1_65K_1027. Working just fine and glad to see since I'm coming from my rooted Droid Bionic and missed Call Blocker featured I used all too often.
Thanks, Sorli...

It is not working for me
I received new phone today from RW and it is stock with 1_65K_1027 when I run Cyanide it does not install SuperSU and I do not have root access. I have used this method previously on my old original RW phone. I reran after factory data reset and still same result, not working for me. Any help would be great as I love my old RW phone when it was rooted.
Thanks in advance.

Hmm...not sure really, but figured I reply to your post just to let you know someone is out here, running the same build 1-65K_1027, and successful months ago.
Did you hear back from the Cyanide developer and hopefully he has some notes of interest and what may have changed?
Obviously, I did my installation months ago and hopefully nothing has changed, but you also said you are now using a newer Defy. What happened to your older unit?
Hope you figure it out and I'm actually waiting for a new RW phone. Been waiting a while and may just drop kick RW if they don't come out with something new soon as reported "End of Summer!" in previous Blog posts. Sorli...
daedreamah said:
I received new phone today from RW and it is stock with 1_65K_1027 when I run Cyanide it does not install SuperSU and I do not have root access. I have used this method previously on my old original RW phone. I reran after factory data reset and still same result, not working for me. Any help would be great as I love my old RW phone when it was rooted.
Thanks in advance.
Click to expand...
Click to collapse

Old RW phone locked up and had over-heating issues...I could not use GPS wile plugged in to car charger at the same time. RW swapped phone and new one was sent to me. My old phone I used Cyanide no problems to install and use Titanium Back up to make backups of the pre-installed apps then uninstall them. I performed another Factory data reset from the privacy settings on the phone and then reinstalled Cyanide - still no go for me - does not install SuperSU and I do not have root access.
Thanks for you reply, do you have any suggestions ?

What is weird is my install (x2) went perfectly without problems both times. Test drove on my wife's phone did not have any problems.
Does it work at all...initiate the process, reboot, and then nothing?
May need to document your steps (what seems to work, where it may fail, errors if any, etc) and then email the developer to see what he may have to say and see if he can help. Sorli...
daedreamah said:
Old RW phone locked up and had over-heating issues...I could not use GPS wile plugged in to car charger at the same time. RW swapped phone and new one was sent to me. My old phone I used Cyanide no problems to install and use Titanium Back up to make backups of the pre-installed apps then uninstall them. I performed another Factory data reset from the privacy settings on the phone and then reinstalled Cyanide - still no go for me - does not install SuperSU and I do not have root access.
Thanks for you reply, do you have any suggestions ?
Click to expand...
Click to collapse

Unboxed new phone, activated it, put in old SDCARD with Cyanide on it, Under application settings checked unknown sources, installed via the built in file manager and then ran the app on the phone, Agreed to the warning, phone rebooted then rebooted again. No SuperSu and no root. Downloaded the latest Cyanide and re-installed same results. I have done this before an another RW Defy and no problems like all of you, but this one will not work for me.
Thanks.

daedreamah said:
Unboxed new phone, activated it, put in old SDCARD with Cyanide on it, Under application settings checked unknown sources, installed via the built in file manager and then ran the app on the phone, Agreed to the warning, phone rebooted then rebooted again. No SuperSu and no root. Downloaded the latest Cyanide and re-installed same results. I have done this before an another RW Defy and no problems like all of you, but this one will not work for me.
Thanks.
Click to expand...
Click to collapse
This could have been silently patched some how, I am getting other report of it not working on firmware that I have confirmed it to work on. I will release a new root around Aug 11th. Possibly sooner if someone put one of these phones in my hands for a little while.

jcase said:
This could have been silently patched some how, I am getting other report of it not working on firmware that I have confirmed it to work on. I will release a new root around Aug 11th. Possibly sooner if someone put one of these phones in my hands for a little while.
Click to expand...
Click to collapse
If I can be of any help via trial and error please let me know. At this time the RW is my only phone otherwise I would send it in...I have managed to get it to communicate via ADB using the adb devices command and it responded. If you want to test I am up for it. Thanks

jcase said:
This could have been silently patched some how, I am getting other report of it not working on firmware that I have confirmed it to work on. I will release a new root around Aug 11th. Possibly sooner if someone put one of these phones in my hands for a little while.
Click to expand...
Click to collapse
Same issue here, it appears that the permissions of the symlink are being changed and not the target of the symlink.
I changed the app, so that it would have to be launched 2x instead of doing the 2nd step automatically.
Here's what I saw.
/system/etc/install-recovery.sh did not exist
$ ls -l
ls -l
-rw-r--r-- root root 135246 2013-07-11 22:41 last_alog_system_20130711_224159
-rw-r--r-- root root 138909 2013-07-11 22:41 last_alog_events_20130711_224159
-rw-r--r-- root root 144210 2013-07-11 22:41 last_alog_radio_20130711_224159
-rw-r--r-- root root 139601 2013-07-11 22:41 last_alog_main_20130711_224159
-rw-rw-rw- app_98 app_98 2 2013-07-11 22:41 onboot
lrwxrwxrwx app_98 app_98 2013-07-11 22:41 with_love_from_jcase -> /system/etc
lrwxrwxrwx app_98 app_98 2013-07-11 22:41 i_like_pie -> /system/etc/install-recovery.sh
/system
drwxr-xr-x root root 1980-01-05 17:00 etc
Tried modifying the sym link to a file that did exsit.
lrwxrwxrwx shell shell 2013-07-11 22:54 with_love_from_dlm -> /system/etc/init.qcom.post_boot.sh
permissions on /system/etc/init.qcom.post_boot.sh were unchanged.
I could get you remote access to the phone, sending may be an option.

I'm ready to root this again, please contact me via jcase at cunninglogic dot com.
Even if I can't find a root I can release, I will guarantee leaving the phone rooted when I am done testing
DewJunkie said:
Same issue here, it appears that the permissions of the symlink are being changed and not the target of the symlink.
I changed the app, so that it would have to be launched 2x instead of doing the 2nd step automatically.
Here's what I saw.
/system/etc/install-recovery.sh did not exist
$ ls -l
ls -l
-rw-r--r-- root root 135246 2013-07-11 22:41 last_alog_system_20130711_224159
-rw-r--r-- root root 138909 2013-07-11 22:41 last_alog_events_20130711_224159
-rw-r--r-- root root 144210 2013-07-11 22:41 last_alog_radio_20130711_224159
-rw-r--r-- root root 139601 2013-07-11 22:41 last_alog_main_20130711_224159
-rw-rw-rw- app_98 app_98 2 2013-07-11 22:41 onboot
lrwxrwxrwx app_98 app_98 2013-07-11 22:41 with_love_from_jcase -> /system/etc
lrwxrwxrwx app_98 app_98 2013-07-11 22:41 i_like_pie -> /system/etc/install-recovery.sh
/system
drwxr-xr-x root root 1980-01-05 17:00 etc
Tried modifying the sym link to a file that did exsit.
lrwxrwxrwx shell shell 2013-07-11 22:54 with_love_from_dlm -> /system/etc/init.qcom.post_boot.sh
permissions on /system/etc/init.qcom.post_boot.sh were unchanged.
I could get you remote access to the phone, sending may be an option.
Click to expand...
Click to collapse

Mobile Q Upgrade 5.0.0 upgraded me to MM (6039S)

Background : I have a recently purchased 6039S, came with Lollipop 5.0.2. I was successful in unlocking bootloader, but when attempting to flash twrp and boot into recovery, got stuck in bootloop. Thinking I must have messed something up, I attempted to return to stock using Mobile Upgrade Q 5.0.0, so that I could try again.
Problem: Mobile Q upgraded my phone to MM 6.0.1, which I was trying to avoid so that I could root. It was my understanding it would restore my phone to stock.
Questions: Did I do something wrong?
I assume my next step to return to stock is to follow this guide (see post by wiemar)? :
http://forum.xda-developers.com/idol-3/help/bricked-idol-3-help-recovering-t3177174/page12
Thanks for any guidance.

You didn't do anything wrong. From my experience, the programs loads the most recent released onto the phone, regardless of the version on the phone before upgrading/restoring.

Thanks for the reply. Any idea if the post I linked to will work for 6039S? Or is there another way to revert to 5.0.2 in my case?
P.S. I saw somewhere that people successfully used Mobile Upgrade Q and selected Pixi 3 to revert. Since it looks like Pixi 3 is still on Lollipop, would this maybe revert me back?
Thanks!

You can flash recovery without bootloader unlocking.
Hello,
The fact that your Idol 3 has been upgraded to MM doesn't have to mean that you can't root or install recovery.
I recently found a way to flash recovery to my device and flash SuperSU.zip using that recovery, which is TWRP.
All you have to do is the following
Download Sahara & Firehose Test from This post
Download the latest Super SU
Get yourself a TWRP image for the Idol 3.
First off
Turn off your phone
Connect your phone to your computer using a Micro USB cable
Hold both volume up and down and press power to start up the device
Once you get onto a screen that says "Download Mode", release both volume buttons and hold volume up to continue. The screen will now turn black
Then you open up Sahara & Firehose Test
Click on "Detect" to detect your device, a connected COM port should appear above the buttons
Click on "NPRG" to load the Sahara & Firehose flasher into your phone's memory
Click on "Get GPT" to fill up the list on the bottom of the window
In the list, find the partition with the name "recovery"
There should be a small checkbox in that item, make sure it's checked
Double click on the textbox next to that checkbox and select where you want to save a backup of the stock recovery image
Click on "Read" to backup your recovery
Double click on that textbox again and select your TWRP image file
Click on "Write" to flash the recovery image to your phone
For SuperSU
Shut down your phone
Press and hold the volume up button and start the phone with the power button
As soon as the "TEAMWIN" logo appears, let go of the volume button
First you want swipe to allow modifications
In the menu that appears next, you want to select "Install"
Now select your downloaded SuperSU ZIP file, it might be on the external storage. You can change storages by ticking on "Storage: Internal Storage".
Swipe again to apply the zip package
Now reboot the device. If it asks to install the SuperSU, tick on "Do Not Install"
I hope I could help you with this,
With kind regards,
Niels Koomans.

Wow, thanks, Niels, for all the detailed information. I will give it a try when I am home and see how it goes!
Thanks!

Yay! Success! Thank you Niels for step by step instructions, and decker su for tools. I now have a stock 6.0.1 rooted 6039s.
The only change I had to make from the above instructions was to use this SuperSu file, as the other one failed for me.

Please!
johnfgoodman said:
Yay! Success! Thank you Niels for step by step instructions, and decker su for tools. I now have a stock 6.0.1 rooted 6039s.
The only change I had to make from the above instructions was to use this SuperSu file, as the other one failed for me.
Click to expand...
Click to collapse
Hi!
Can you copy with ES File Explorer ( with root ON in app settings) this 2 files: mmcblk0p23 and mmcblk0p25 and upload it???
They are in /dev/block
mmcblk0p23 = boot.img
mmcblk0p25=system.img
Thanks!

persona78 said:
Hi!
Can you copy with ES File Explorer ( with root ON in app settings) this 2 files: mmcblk0p23 and mmcblk0p25 and upload it???
They are in /dev/block
mmcblk0p23 = boot.img
mmcblk0p25=system.img
Thanks!
Click to expand...
Click to collapse
Yes, I uploaded them here.

johnfgoodman said:
Yes, I uploaded them here.
Click to expand...
Click to collapse
Great! Thanks!
---------- Post added at 12:50 AM ---------- Previous post was at 12:36 AM ----------
A question
Does lockscreen options work fine?
Pin, password, etc... ?

Yes, I tested swipe, pattern, password, and PIN and they seem to work fine.

johnfgoodman said:
Yes, I tested swipe, pattern, password, and PIN and they seem to work fine.
Click to expand...
Click to collapse
Hi!
I flash it but the lock settings doesn´t work for me! Weird... must be persit.img but im afraid to flash that one... :\
and thanks for the images!

johnfgoodman said:
Yes, I uploaded them here.
Click to expand...
Click to collapse
Hi!
Is me again! Can you upload to me this images:
mmcblk0p27 - persist
mmcblk0p6 - sbl1
mmcblk0p8 - rpm
mmcblk0p06 - tz
mmcblk0p12 - hyp
mmcblk0p19 - fsg
mmcblk0p21 - aboot
i this this is what is update by OTA... I doesn´t insert modem image because your frequencies are diferent ...
Thanks :good:

persona78 said:
Hi!
Is me again! Can you upload to me this images:
mmcblk0p27 - persist
mmcblk0p6 - sbl1
mmcblk0p8 - rpm
mmcblk0p06 - tz
mmcblk0p12 - hyp
mmcblk0p19 - fsg
mmcblk0p21 - aboot
i this this is what is update by OTA... I doesn´t insert modem image because your frequencies are diferent ...
Thanks :good:
Click to expand...
Click to collapse
OK, I uploaded them to same directory. Only thing, I didn't find mmcblk0p06. So I uploaded mmcblk0p16, in case it was a typo.

johnfgoodman said:
OK, I uploaded them to same directory. Only thing, I didn't find mmcblk0p06. So I uploaded mmcblk0p16, in case it was a typo.
Click to expand...
Click to collapse
I write it wrong!
Is mmcblk0p10! Tz!
And, thanks for the help!

persona78 said:
I write it wrong!
Is mmcblk0p10! Tz!
And, thanks for the help!
Click to expand...
Click to collapse
OK, it's there now. Glad to help...

johnfgoodman said:
OK, it's there now. Glad to help...
Click to expand...
Click to collapse
Hi!
I made a mistake in persist, is mmcblk0p26 not 27.
Can you upload it!
Sorry...
Thank for the images!

persona78 said:
Hi!
I made a mistake in persist, is mmcblk0p26 not 27.
Can you upload it!
Sorry...
Thank for the images!
Click to expand...
Click to collapse
OK, I have updated cloud with 26. I also copied and uploaded 19 again, but it still looks like an archive, not sure why?

johnfgoodman said:
OK, I have updated cloud with 26. I also copied and uploaded 19 again, but it still looks like an archive, not sure why?
Click to expand...
Click to collapse
Ok, i think i have all now! Thank you for your support! Lets see if i update or brick the phone !!! ( i hope not )

@johnfgoodman, i try everything but i loose notification sound and lock screen..
I think is a kernel thing, same thing appens i Huawei. Diferent country kernel have some diferent configurations in the same device, so... i think 6039Y kernel doesn´t work properly on 6039S!
Bastards ...

persona78 said:
@johnfgoodman, i try everything but i loose notification sound and lock screen..
I think is a kernel thing, same thing appens i Huawei. Diferent country kernel have some diferent configurations in the same device, so... i think 6039Y kernel doesn´t work properly on 6039S!
Bastards ...
Click to expand...
Click to collapse
I'm sorry... That really stinks

!!!!!Bootloader Unlock & TWRP Achieved!!!!!

A-Team Digital Solutions
*Exclusive Release*
Idol 5 Bootloader Unlock & TWRP Recovery
Get ahold of me to see what else can be done with this phone, as I don't physically own it and can't help out getting things going unless I have the required info from someone who has one of these. I would Imagine GSI roms can now be installed on it, but more testing would need to be done. If someone would like to donate me a device, I can have something spun up in no time, otherwise there isn't much more that can be done without a device to test on.
-Bootloader Unlock & TWRP-
https://androidforums.com/threads/6060c-bootloader-unlock.1327876/
-Telegram Live Chat-
https://t.me/Android_General_Chat​

Wow! :good:

Update
[hi guys I'm the guinea pig haha,thanks to @PizzaG,and @diplomatic]
After a fun weekend of tweaking [no,not that kind] I have managed to mount the system and dev partitions to -rw and can report I've successfully managed to edit the build.prop as well as a few others by way of utilizing a multi user interactive ADB shell/terminal shell [xterm/color256term] and Ghost Commander file explorer. Not 100% sure how it's working but I'm thinking it's exploiting some loophole in the REMOTE/LOCAL-multiuser GID/UID protocols. Any ideas?

Firmware
Hi, is there anyone who has a way to install standart firmware, my phone is frozen on the initial boot screen. (Factort reset) does not work
HELPPP

Happytop said:
Hi, is there anyone who has a way to install standart firmware, my phone is frozen on the initial boot screen. (Factort reset) does not work
HELPPP
Click to expand...
Click to collapse
Yes, I have access to the alcatel stock firmware flasher and the stock firmware. Pm me for link

how can i get mtk-su?

stevegsames said:
how can i get mtk-su?
Click to expand...
Click to collapse
Experimental Software Root for HD 8 & HD 10

Thanks @diplomatic, im running out of steam, lol. Ill post the rest of what i have tonight so you idol 5 users have at least standard temp root. My tester kinda fizzled out so....... You guys have the prop line for oem unlock=1, but no fastboot access. And i cant find the intial release stock dump anywhere. I was hoping i could and it would have working fastboot like my device. Anyways, i need a new reliable tester to see if you guys are stuck with temp root or if you can have perm root

@PizzaG, you mean you can't boot your phone? If so, sorry to hear that. I don't know the details about Alcatel phones, but I hope there's some way to restore the firmware....
Also, will you have a chance to test what I proposed in my PM?

diplomatic said:
Experimental Software Root for HD 8 & HD 10
Click to expand...
Click to collapse
Thank$ for the help
---------- Post added at 05:39 PM ---------- Previous post was at 04:42 PM ----------
How can I mount the /$y$tem partition to -rw?

stevegsames said:
Thank$ for the help
How can I mount the /$y$tem partition to -rw?
Click to expand...
Click to collapse
If it's a recent phone, you probably can't due to dm-verity. You can check by running
mount | grep /system
If the first word is something like '/dev/block/dm-0', then remounting system is a no-go without unlocking the bootloader. If it doesn't say 'dm-0', but 'mmcblkXXX', then you might want to try
mount -o remount,rw /system
(BTW, I'm gonna guess your s-key is broken )

stevegsames said:
Thank$ for the help
---------- Post added at 05:39 PM ---------- Previous post was at 04:42 PM ----------
How can I mount the /$y$tem partition to -rw?
Click to expand...
Click to collapse
I'm not sure yet if you can.

diplomatic said:
If it's a recent phone, you probably can't due to dm-verity. You can check by running
mount | grep /system
If the first word is something like '/dev/block/dm-0', then remounting system is a no-go without unlocking the bootloader. If it doesn't say 'dm-0', but 'mmcblkXXX', then you might want to try
mount -o remount,rw /system
(BTW, I'm gonna guess your s-key is broken )
Click to expand...
Click to collapse
Yup key i$ broken
It i$ a recent phone and it $ay$ dm-0

So what is the process in rooting this phone

Some NEWS guys, check this out and let me know if it works for Idol 5. It's Based off the Working Temp Root Xploit, hopefully it will give you Magisk
https://github.com/JunioJsv/mtk-easy-su

Bootloader unlock and twrp
https://androidforums.com/threads/6060c-bootloader-unlock.1327876/
https://forum.xda-developers.com/idol-5/development/guide-alcatel-idol-5-6060c-bootloader-t4157411