Related
Hello Guys
I am new to android so please correct my mistakes and i will try to give every detail as possible.
I am having Genx tablet GX pad 300 (It is rooted). By mistake i left my tablet as home and my small brother tried to unlock it. As it was password protected so after 15 failed failed attempts, it got hard locked and Asked for my Gmail ID and PASSWORD to unlock. BUT my wifi was disabled so i was not able to reset it.
An other method was to use ADB and bypass the Password, but The usb debugging was disabled so it didnt worked either
thirdly I saw a method (on XDA) to use Recovery mode to flash AROMA Filemanager and delete the files that were related to the password.
Now the real problem begins so please cross your fingers.
First i copied the 'aroma file manager" .zip file in external sd card. the file is in the attachment and here is the link to its XDA page, click here
First i booted my device into the Recovery mode and seleted the the option "Apply update from external sd" and selected the update file (.zip format). It gave me error
E Signature verfication failed
Installation aborted
I had Android System Recovery 3e
I did a five hour research and came to know that it is security in android system recovery 3e to reject unofficial installation, i came to know that if i have to fix these errors the either i have to flash a Custom rom like CWM or a MODDED Android system recovery 3e which allows the installation of unofficial apps. the problem is that there is now Custom CWM for my device and i dont know how to make one from the source code. Secondly they have to be installed by ADB but i cant acess my device locked. I also found that sometimes we try to flash a new recovery form within a recovery it may brick the device. i also found that the updates that can be flashed by android system recovery should be named Update.zip and should be officially signed.
I know that there are many methods and apps to sign the .zip files so that they are accepted by the Android system recovery 3e.
i came across apps like zipsigner and signapktic both of them are available on google play. I also used used manual method to sign the aroma filemanager .zip file but every thing i tried it gave me the E signature verification error installation aborted.
My Question is this that how to Sign files so that they are accepted in the ANDROID STOCK RECOVERY 3e
Please keep it simple as possible.:good::laugh:
Download APKManager (5.1). Extract it, copy your zip to ./other/ folder, run cmd.exe, change directory to ./other/ then sign using following command in cmd.exe:
java -jar signapk.jar -w testkey.x509.pem testkey.pk8 your-rom.zip signed.zip.
~It does not require internet connect connection..you can sign in to google account without internet~
Me too!
I have the same problem and can not find an answer for my life! I really need something that can sign the zip for the stock recovery!
do not recognize the command
Hey Guys -
I have had my A9 for about 2 months and love it. When I first purchased it, I rooted it using the method pinned to this forum which seemed to work well. Soon afterwards, I found out that when I inserted and tried to format an SD card as "internal", it wouldn't work and result in it showing as "corrupted." I soon found out that this seemed to be due to the root replacing the original boot.img which messes with encryption. Since the root was posted, SuperSU has been updated and that step has changed supposedly.
Now that I have some time, I want to fix this issue. Before doing so, I've read through many posts and think I have a plan. I wanted to post the steps I need to follow as I understood them to make sure my plan is correct and will result in not only being able to format an SD internally and be rooted, but also a working phone Below are the specs of my phone, the steps I think it may take to resolve, and a few questions I have after reading through numerous posts. Any help is appreciated!
Phone Specs
Some as currently listed in Settings
- HTC One A9
- AT&T USA
- Rooted / s-off
- Android 6.0 / Sense 7.0g
Software Number: 1.10.502.3
Kernel: 3.10.73-perf-g28d66e0
Baseband: [email protected]_29.05_F
Build: 1.10.502.3 CL635081 release keys
Android Security Patch Level: 2015-10-01
Steps to Fix
1. Backup any data desired (I have a nightly Titanium backup)
2. Download RUU for same version (1.10.502.3) from http://forum.xda-developers.com/one-a9/general/wip-ruu-htc-one-a9-t3240344
Should I use newer version or are those for different carriers?
3. Apply RUU (via embedded EXE or try to extract and apply using adb/fastboot)
4. Once phone is restored, make a backup of boot.img from phone just in case it's needed later
5. Install TWRP via adb/fastboot
6. Install SuperSU via TWRP
At this point (if I can make it to this point), test and see if the phone's rooted and I can format the SD internally. If so, great. If not, continue with the following steps...
7. Download & flash modded boot.img from A9 Root post
8. Install TWRP via adb / fastboot
9. Install SuperSU via TWRP
10. Flash original boot.img backed up in step #4 to my phone (since modded one was only needed initially to install SuperSU) So that encryption keys match and I may successfully format sd cards for internal use
My Questions
1. Are the steps above basically the process i need to perform or is there a better / easier way? I don't know if I could flash a common boot.img from an RUU or if it needs to be flashed to phone first for encryption purposes. Even if I can, I've tried to extract it from ruu.zip before and could not
2. Should I use an RUU for a newer version (over 1.10.502.3) or are those for different carriers and not work with my AT&T phone?
3. Does it make a difference if I install the RUU via embedded EXE or extract and apply using adb/fastboot?
4. What versions of TWRP & SuperSU should I use?
Any additional suggestions would be appreciated - I just want to get this resolved once and for all! - Thanks!
bzowk said:
Hey Guys -
I have had my A9 for about 2 months and love it. When I first purchased it, I rooted it using the method pinned to this forum which seemed to work well. Soon afterwards, I found out that when I inserted and tried to format an SD card as "internal", it wouldn't work and result in it showing as "corrupted." I soon found out that this seemed to be due to the root replacing the original boot.img which messes with encryption. Since the root was posted, SuperSU has been updated and that step has changed supposedly.
Now that I have some time, I want to fix this issue. Before doing so, I've read through many posts and think I have a plan. I wanted to post the steps I need to follow as I understood them to make sure my plan is correct and will result in not only being able to format an SD internally and be rooted, but also a working phone Below are the specs of my phone, the steps I think it may take to resolve, and a few questions I have after reading through numerous posts. Any help is appreciated!
Phone Specs
Some as currently listed in Settings
- HTC One A9
- AT&T USA
- Rooted / s-off
- Android 6.0 / Sense 7.0g
Software Number: 1.10.502.3
Kernel: 3.10.73-perf-g28d66e0
Baseband: [email protected]_29.05_F
Build: 1.10.502.3 CL635081 release keys
Android Security Patch Level: 2015-10-01
Steps to Fix
1. Backup any data desired (I have a nightly Titanium backup)
2. Download RUU for same version (1.10.502.3) from http://forum.xda-developers.com/one-a9/general/wip-ruu-htc-one-a9-t3240344
Should I use newer version or are those for different carriers?
3. Apply RUU (via embedded EXE or try to extract and apply using adb/fastboot)
4. Once phone is restored, make a backup of boot.img from phone just in case it's needed later
5. Install TWRP via adb/fastboot
6. Install SuperSU via TWRP
At this point (if I can make it to this point), test and see if the phone's rooted and I can format the SD internally. If so, great. If not, continue with the following steps...
7. Download & flash modded boot.img from A9 Root post
8. Install TWRP via adb / fastboot
9. Install SuperSU via TWRP
10. Flash original boot.img backed up in step #4 to my phone (since modded one was only needed initially to install SuperSU) So that encryption keys match and I may successfully format sd cards for internal use
My Questions
1. Are the steps above basically the process i need to perform or is there a better / easier way? I don't know if I could flash a common boot.img from an RUU or if it needs to be flashed to phone first for encryption purposes. Even if I can, I've tried to extract it from ruu.zip before and could not
2. Should I use an RUU for a newer version (over 1.10.502.3) or are those for different carriers and not work with my AT&T phone?
3. Does it make a difference if I install the RUU via embedded EXE or extract and apply using adb/fastboot?
4. What versions of TWRP & SuperSU should I use?
Any additional suggestions would be appreciated - I just want to get this resolved once and for all! - Thanks!
Click to expand...
Click to collapse
First off, this isn't Development.
Secondly, I explained to you how to fix this in the very root thread you linked several times.
Thirdly, there's a newer, official RUU from HTC right on their ROM Downloads website. I'd start by installing that (though I also have a recovery-flashable version of that ROM in my Base ROM thread).
Fourthly, with access to an official RUU, and my ROM decrypt script, you have access to the stock boot.img (which is also in the firmware zip in my Base ROM thread), which you can use as your baseline for restoring the verity key to the ramdisk, thereby allowing you to use adopted storage without any issues. Note however that I was only able to use adopted storage with the "forceencrypt" flag enabled.
Fifthly, you can't just restore the stock boot image (at least not if you want to stay rooted). You can be both rooted and encrypted, but you have to first make sure SuperSU is flashed and set up prior to allowing the device to be encrypted again (adopted storage only works with an encrypted device, and then you won't be able to access your storage with TWRP).
OK, OK - sorry.... It had been a while since posting and honestly forgot about that thread - my fault.
I decided to start fresh so have already restored the phone to HTC's latest RUU (1.27.502.5 ATT) as I already had it downloaded. I've also flashed TWRP 2.8.8.1 to the phone, but am obviously prompted to enter a password when I try to enter recovery. Based off what I've read, the steps below seem to be what I need to do so that I may be rooted + still have encryption for internal sd formatting. Is it correct (or close to it)
Using an Ubuntu 14.04 x86 VM...
1. Download & extract your decrypt script to a temp folder in linux vm
2. In Windows, run same RUU I applied and copy out rom.zip from %temp%
3. Rename "rom.zip" to "rom_a9.zip"
4. Copy rom_a9.zip to the ""place_rom_zip_here" folder of your extracted script in the vm
5. Run ./decrypt-htc and wait for script to complete to get img files
On Phone (Currently has same RUU installed + TWRP but not rooted)
6. Root phone using original method of flashing modded boot.img, install SuperSU, and get rooted
7. Once done and rooted, flash boot.img I extracted using your script above to phone via adb
Once that's done, it should be rooted + have encryption thus allowing me to use internal sd card, right? Sorry to be such a bother - just want to get this fixed and done with
Thanks!
bzowk said:
OK, OK - sorry.... It had been a while since posting and honestly forgot about that thread - my fault.
I decided to start fresh so have already restored the phone to HTC's latest RUU (1.27.502.5 ATT) as I already had it downloaded. I've also flashed TWRP 2.8.8.1 to the phone, but am obviously prompted to enter a password when I try to enter recovery. Based off what I've read, the steps below seem to be what I need to do so that I may be rooted + still have encryption for internal sd formatting. Is it correct (or close to it)
Using an Ubuntu 14.04 x86 VM...
1. Download & extract your decrypt script to a temp folder in linux vm
2. In Windows, run same RUU I applied and copy out rom.zip from %temp%
3. Rename "rom.zip" to "rom_a9.zip"
4. Copy rom_a9.zip to the ""place_rom_zip_here" folder of your extracted script in the vm
5. Run ./decrypt-htc and wait for script to complete to get img files
On Phone (Currently has same RUU installed + TWRP but not rooted)
6. Root phone using original method of flashing modded boot.img, install SuperSU, and get rooted
7. Once done and rooted, flash boot.img I extracted using your script above to phone via adb
Once that's done, it should be rooted + have encryption thus allowing me to use internal sd card, right? Sorry to be such a bother - just want to get this fixed and done with
Thanks!
Click to expand...
Click to collapse
Re-read my post. If you flash the stock boot.img, you will no longer be rooted.
And as I said in the original thread, you need to pull the rooted boot.img and add the verity key from the stock one to it. Also you'll need to add the forceencrypt and verify flag back.
P.S. You also need to re-read the instructions in the decrypt thread. You don't have to rename anything anymore.
Good Afternoon -
OK - sorry to frustrate you, but I think I finally have it figured out. I started from scratch, re-read many posts, and took notes. I was a little confused on the last part so wanted to verify, please...
I've already unpacked the boot.img from the latest HTC A9 (AT&T) RUU and have the two folders. I restored the same RUU to my phone, flashed TWRP 2.8.8.1, backed up the boot.img, and unpacked it before realizing that I should have probably rooted it first.
Correct me if I'm wrong, but here's all I need to do to finish....
1. Download modified A9 boot.img from top of root thread
2. Flash modded boot.img using fastboot
3. Verify TWRP is still installed then use it to install SuperSU 2.67 (latest)
4. Back up boot partition just like I did before in TWRP
5. Unpack it on PC to create ramdisk and split_img folders
6. Copy verity_key from unpack of the actual RUU and overwrite one in rooted unpack
7. Edit the file fstab.qcom in the ramdisk folder of the rooted unpack in Notepad++ and add the "verify" flag after the wait flag on the fist uncommented line - save
8. Repack rooted boot.img
9. Flash phone with repacked boot.img using fastboot
10. Reboot & enjoy a rooted phone + encryption allowing sd internal formatting
Promise not to bug anymore if I can just get this resolved.
Thanks again for your assistance!
UPDATE
Hmm - was just prepping and went to download modded file from root thread's first post. Doesn't seem to have one that matches newest build of RUU I flashed - if I'm interpreting it correctly. Researching further, but if know of alternate method or another solution to get through steps 1 & 2 about (assuming they are correct), I'd appreciate it. Thanks
bzowk said:
Good Afternoon -
OK - sorry to frustrate you, but I think I finally have it figured out. I started from scratch, re-read many posts, and took notes. I was a little confused on the last part so wanted to verify, please...
I've already unpacked the boot.img from the latest HTC A9 (AT&T) RUU and have the two folders. I restored the same RUU to my phone, flashed TWRP 2.8.8.1, backed up the boot.img, and unpacked it before realizing that I should have probably rooted it first.
Correct me if I'm wrong, but here's all I need to do to finish....
1. Download modified A9 boot.img from top of root thread
2. Flash modded boot.img using fastboot
3. Verify TWRP is still installed then use it to install SuperSU 2.67 (latest)
4. Back up boot partition just like I did before in TWRP
5. Unpack it on PC to create ramdisk and split_img folders
6. Copy verity_key from unpack of the actual RUU and overwrite one in rooted unpack
7. Edit the file fstab.qcom in the ramdisk folder of the rooted unpack in Notepad++ and add the "verify" flag after the wait flag on the fist uncommented line - save
8. Repack rooted boot.img
9. Flash phone with repacked boot.img using fastboot
10. Reboot & enjoy a rooted phone + encryption allowing sd internal formatting
Promise not to bug anymore if I can just get this resolved.
Thanks again for your assistance!
UPDATE
Hmm - was just prepping and went to download modded file from root thread's first post. Doesn't seem to have one that matches newest build of RUU I flashed - if I'm interpreting it correctly. Researching further, but if know of alternate method or another solution to get through steps 1 & 2 about (assuming they are correct), I'd appreciate it. Thanks
Click to expand...
Click to collapse
You don't need anything from that root thread. Everything there is deprecated (which I've said several times).
If you already have the stock boot.img unpacked and ready to go, all you have to do is flash SuperSU, then back up the rooted boot.img that you now have on your device thanks to SuperSU. Unpack that boot.emmc.win and add the verity_key from the stock ramdisk and replace the fstab.qcom with the one from the stock ramdisk. Repack, flash to your device via fastboot or TWRP, and your device will encrypt on that first boot and you'll be good to go.
Just to make sure - you did a Format Data in TWRP prior to flashing SuperSU, correct?
Captain_Throwback said:
You don't need anything from that root thread. Everything there is deprecated (which I've said several times).
If you already have the stock boot.img unpacked and ready to go, all you have to do is flash SuperSU, then back up the rooted boot.img that you now have on your device thanks to SuperSU. Unpack that boot.emmc.win and add the verity_key from the stock ramdisk and replace the fstab.qcom with the one from the stock ramdisk. Repack, flash to your device via fastboot or TWRP, and your device will encrypt on that first boot and you'll be good to go.
Just to make sure - you did a Format Data in TWRP prior to flashing SuperSU, correct?
Click to expand...
Click to collapse
Thanks -
Well, that's the thing... One of the two unpacked boot.img I have currently is wrong. The two I have are:
- One unpacked boot.img extracted from latest RUU using your script in linux
- One unpacked boot.img backed up from unrooted phone which only had TWRP flashed
That was part of my question. I know that the 2nd unpacked boot.img above is worthless as the phone needed to be rooted prior to me backing it up. The question for me is how to flash superSU onto the phone (which currently has the same latest RUU + TWRP 2.8.8.1 installed) if I can only access TWRP is a read-only mode as I'm prompted for password upon booting to recovery. That's why I brought up the legacy root method as I don't know of an alternative... unless SuperSU doesn't require write permissions to whatever TWRP has locked down currently.
Once I can root it, backup it's boot, and unpack it; I just need to literally copy & overwrite the "verity_key" and "fstab.qcom" files (assuming the only difference is the fstab.qcom I'm overwriting doesn't have the verify flag), repack, then flash back to phone via fastboot, right?
Thanks for your patience!
bzowk said:
Thanks -
Well, that's the thing... One of the two unpacked boot.img I have currently is wrong. The two I have are:
- One unpacked boot.img extracted from latest RUU using your script in linux
- One unpacked boot.img backed up from unrooted phone which only had TWRP flashed
That was part of my question. I know that the 2nd unpacked boot.img above is worthless as the phone needed to be rooted prior to me backing it up. The question for me is how to flash superSU onto the phone (which currently has the same latest RUU + TWRP 2.8.8.1 installed) if I can only access TWRP is a read-only mode as I'm prompted for password upon booting to recovery. That's why I brought up the legacy root method as I don't know of an alternative... unless SuperSU doesn't require write permissions to whatever TWRP has locked down currently.
Once I can root it, backup it's boot, and unpack it; I just need to literally copy & overwrite the "verity_key" and "fstab.qcom" files (assuming the only difference is the fstab.qcom I'm overwriting doesn't have the verify flag), repack, then flash back to phone via fastboot, right?
Thanks for your patience!
Click to expand...
Click to collapse
Once you Format Data in TWRP and reboot recovery, you can flash SuperSU and you will be rooted. You just have to back up the boot.img after flashing SuperSU on the unencrypted device to re-enable verity so that adopted storage will work.
P.S. And no, the verify flag isn't the only difference. As I also said earlier (I'm constantly repeating myself), the device must be encrypted for Adopted Storage to work, so the forceencrypt flag from the stock fstab must also be present. That's why it's easier just to replace the whole file. The problem you have at the end of the day is that, while you'll be rooted and be able to use adopted storage in Android, you still won't be able to access said storage (or /data) in TWRP.
Captain_Throwback said:
Once you Format Data in TWRP and reboot recovery, you can flash SuperSU and you will be rooted. You just have to back up the boot.img after flashing SuperSU on the unencrypted device to re-enable verity so that adopted storage will work.
P.S. And no, the verify flag isn't the only difference. As I also said earlier (I'm constantly repeating myself), the device must be encrypted for Adopted Storage to work, so the forceencrypt flag from the stock fstab must also be present. That's why it's easier just to replace the whole file. The problem you have at the end of the day is that, while you'll be rooted and be able to use adopted storage in Android, you still won't be able to access said storage (or /data) in TWRP.
Click to expand...
Click to collapse
Great - Thanks!!
Just to make sure, below's my plan with a small question @ step #5. Does it get your stamp of approval?
Phone (A9) already had latest RUU restored (same RUU I ran against your script to pull boot.img from) and TWRP 2.8.8.1 flashed
1. Boot into TWRP & bypass initial screen prompting for password
2. Format Data
3. Reboot back into TWRP
4. Flash SuperSU 2.76 zip
5. Reboot to system then back to TWRP and backup boot partition? / Stay in TWRP and backup boot partition? / Reboot back into TWRP and backup boot partition?
6. Unpack backed up boot partition from phone
7. Copy "verity_key" & "fstab.qcom" files from ramdisk folder in unpacked RUU boot and paste into & overwrite same files in ramdisk folder of unpacked boot from rooted phone
8. Repack rooted phone boot (which includes both new files)
9. Flash newly packed boot.img to phone using fastboot
10. Enjoy
I really appreciate your help and patience with me!
bzowk said:
Great - Thanks!!
Just to make sure, below's my plan with a small question @ step #5. Does it get your stamp of approval?
Phone (A9) already had latest RUU restored (same RUU I ran against your script to pull boot.img from) and TWRP 2.8.8.1 flashed
1. Boot into TWRP & bypass initial screen prompting for password
2. Format Data
3. Reboot back into TWRP
Click to expand...
Click to collapse
Good so far . . .
bzowk said:
4. Flash SuperSU 2.76 zip
Click to expand...
Click to collapse
I'm sure this is just a typo, but that should be 2.67, not 76 (there is no 2.76).
bzowk said:
5. Reboot to system then back to TWRP and backup boot partition? / Stay in TWRP and backup boot partition? / Reboot back into TWRP and backup boot partition?
Click to expand...
Click to collapse
Bolded the correct one above (no need to leave TWRP as the necessary modifications have already been made).
bzowk said:
6. Unpack backed up boot partition from phone
7. Copy "verity_key" & "fstab.qcom" files from ramdisk folder in unpacked RUU boot and paste into & overwrite same files in ramdisk folder of unpacked boot from rooted phone
8. Repack rooted phone boot (which includes both new files)
Click to expand...
Click to collapse
Looks good . . .
bzowk said:
9. Flash newly packed boot.img to phone using fastboot
Click to expand...
Click to collapse
TWRP can also flash the new image, but fastboot is probably the most reliable way to do it.
bzowk said:
10. Enjoy
Click to expand...
Click to collapse
Hopefully . . . You'll likely get a reboot on the first boot (possible multiple reboots), as SuperSU needs a reboot to install the necessary files. Since your device will also encrypt on that initial boot, I'm not sure whether there will be a conflict or not.
bzowk said:
I really appreciate your help and patience with me!
Click to expand...
Click to collapse
Guess we'll see if it all works out . . .
Thanks!
I proceeded by formatting data, booting directly back intoTWRP, flashing SuperSU, backing up the boot partition, then mounting and copying it over to my PC. The boot.img size was 65,536kb - the same size as the one I unpacked from the RUU. Once unpacked, it was missing the verity_key file and the fstab.qcom file was different + missing the verify flag.
I replaced those two files, then ran repackimg.bat which created image-new.img which I renamed to boot.img. Interesting, though, that this file was only 45,890kb. If it's a repack, shouldn't it be the same or similar? Anyways, the phone was still in TWRP (hadn't booted to system since before the format data) so booted it into bootloader directly and tried flashing boot using my new 45mb boot.img.
If failed - but - my phone was only at 17% power. Don't know if that's why it failed or not so it's charging right now while still in the bootloader. Below is what was echoed when I tried flashing it:
Code:
c:\adb>fastboot flash boot boot.img
target reported max download size of 800000000 bytes
sending 'boot' (45890 KB)...
OKAY [ 3.488s]
writing 'boot'...
(bootloader) HOSD CL#656287
FAILED (remote: 4 RU_BATTERY_LOW please connect charger (17% < 30%))
finished. total time: 4.506s
The reason I didn't boot to system is that I thought that was when the encryption might take place. Going to wait until above 30% power then try flashing again. Powered down to charge, but plan to boot straight back into bootloader to flash. If you see anything that stands out or that I need to do otherwise, please let me know. Otherwise, I'll report back what the result was after getting above 30%.
Thanks again!
bzowk said:
Thanks!
I proceeded by formatting data, booting directly back intoTWRP, flashing SuperSU, backing up the boot partition, then mounting and copying it over to my PC. The boot.img size was 65,536kb - the same size as the one I unpacked from the RUU. Once unpacked, it was missing the verity_key file and the fstab.qcom file was different + missing the verify flag.
I replaced those two files, then ran repackimg.bat which created image-new.img which I renamed to boot.img. Interesting, though, that this file was only 45,890kb. If it's a repack, shouldn't it be the same or similar? Anyways, the phone was still in TWRP (hadn't booted to system since before the format data) so booted it into bootloader directly and tried flashing boot using my new 45mb boot.img.
If failed - but - my phone was only at 17% power. Don't know if that's why it failed or not so it's charging right now while still in the bootloader. Below is what was echoed when I tried flashing it:
Code:
c:\adb>fastboot flash boot boot.img
target reported max download size of 800000000 bytes
sending 'boot' (45890 KB)...
OKAY [ 3.488s]
writing 'boot'...
(bootloader) HOSD CL#656287
FAILED (remote: 4 RU_BATTERY_LOW please connect charger (17% < 30%))
finished. total time: 4.506s
The reason I didn't boot to system is that I thought that was when the encryption might take place. Going to wait until above 30% power then try flashing again. Powered down to charge, but plan to boot straight back into bootloader to flash. If you see anything that stands out or that I need to do otherwise, please let me know. Otherwise, I'll report back what the result was after getting above 30%.
Thanks again!
Click to expand...
Click to collapse
The repack is smaller because the backup uses "dd" to copy the entire block device. Not all that space is actually used after compression. That's nothing to worry about.
And these devices are very picky about flashing only when there's sufficient battery, so I'm sure that's the only reason it failed. TWRP, however, doesn't care how much battery you have, so you could always flash the new boot.img in recovery.
Captain_Throwback said:
The repack is smaller because the backup uses "dd" to copy the entire block device. Not all that space is actually used after compression. That's nothing to worry about.
And these devices are very picky about flashing only when there's sufficient battery, so I'm sure that's the only reason it failed. TWRP, however, doesn't care how much battery you have, so you could always flash the new boot.img in recovery.
Click to expand...
Click to collapse
Hey, hey, hey - think it worked!!
Once I got above 30%, I flashed without issue. I rebooted and was able to format an sd internally successfully, too. Now, I just need to verify it's rooted, but think it is. Thank you so much for your help! I'm going to write a guide for newbs like me to use in the future soon.
Thanks again!
bzowk said:
Hey, hey, hey - think it worked!!
Once I got above 30%, I flashed without issue. I rebooted and was able to format an sd internally successfully, too. Now, I just need to verify it's rooted, but think it is. Thank you so much for your help! I'm going to write a guide for newbs like me to use in the future soon.
Thanks again!
Click to expand...
Click to collapse
If your adopted storage doesn't show as corrupted, and you're able to open the SuperSU app in your app drawer and not get a message that no su binary is installed, you should be good to go .
bad topic
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I successfully ported TWRP to Panasonic Eluga Note (MTK6753) after a four day effort. Not a dev here. First time doing this.
<TLDR? skip this>
When I started using android in my HTC HD2, every ROM was pre rooted. I took it for granted.
So I get this cheapo MTK and breaking into it is like banging head against a wall!! I was frustrated with the battery drain: Device never sleeps since the last OTA!
So I learnt SP flash tools and downgraded. ( wiped nvram and created another mess in the process- which is a different story. I solved it)
I could spend this effort and time to stop that pesky "Panasonic" bootaudio too. And that's the first thing I deleted after I booted TWRP, even before rooting.
</TLDR? skipped this>
First things first, enable ADB, enable OEM unlock in developer options, and go to bootloader to unlock it <fastboot oem unlock> THIS WILL WIPE DATA!!
Second thing: Backup nvram.img by sp flash readback and learn how to flash it back (search XDA)- Sometimes you can learn from other's mistakes too! I spent a day and half writing back IMEI and WIFI Mac.
Process (if you don't trust me and want to reproduce the steps yourself)
1. Download stock firmware. (google knows)
2. Patch boot.img so that it doesn't overwrite TWRP with stock recovery on each boot (extract by Carliv Image kitchen and hash out the three lines 663, 664 and 665 mentioning "service flash_recovery /system/bin/install-recovery.sh" in init.rc). I created two copies in the same folder (boot.img, and boot-verified.img) and copied scatter into the same folder for flashing. That's what I saw in the firmware folder.
3. Port TWRP using Carliv Image Kitchen method. I downloaded TWRP from here https://forum.xda-developers.com/android/software/twrp-porter-maker-mediatek-mt67xx-32-t3681861 but didn't use their method. It didn't work. The TWRP for this chip was stated as android N, but worked well.
4. Flash ported TWRP after copying scatter file to the Carliv Imagekitchen output folder and selecting that scatter in SP droid tools. I again created recovery.img and recovery-verified.img. Don't know if its needed that way. You could wait and flash boot and recovery together from the same folder.
5. That's it, you can enter custom recovery now. Get that pesky "panasonic" bootaudio off the system/media folder now! You can stay content after this or proceed to root.
<nandroid backup now, including Nvram and NVdata. Just in case>
6. Download Supersu zip flashable and flash it via TWRP. https://download.chainfire.eu/1113/SuperSU/UPDATE-SuperSU-v2.82-20170528234214.zip?retrieve_file=1 worked for me.
7. Reboot, check root!
If you're more daredevil,
8. Download Xposed flashable zip SDK23 and flash it. Download Xposed installer and copy it to SDcard too.
9. Reboot to recovery and flash the zip. Reboot, install xposed installer. Reboot again.
You're done!
I'll upload my boot.img and ported TWRP if anyone shows any interest in this.
Cheers!
(Bonus: this phone has built in IPtables support in the kernel! I used to flash custom kernel for this ability in other Stock ROMs. AFfirewall works "out of the box"- after rooting, of course!)
Edit: uploaded my modded boot.img and ported TWRP. find it here https://drive.google.com/file/d/1sM1BnyBUFN7PfncFcM7vzIet6gKt3G_L/view?usp=sharing
If you want to go the easy route, unzip the folder and flash it with sp flash. You'll be able to boot into recovery and do the other steps for rooting.
Rememer ONLY DOWNLOAD, don't format, or format and download, or anything!
Brilliant Work man. I also was sort of in your situation as well . i have a panasonic Eluga A3 (Qmobile Noir E2) in my country. Stock Qmobile rom was horrendous. so i flashed the panasonic rom but hated the boot audio and the bloatware that came with it. so i decided to make a slimmed down version of it and successfully did it by using superr's kitchen. and also using the kitchen i removed the encryption on the boot.img and then patched it using magisk for easy rooting without recovery. when flashed together with the modded system.img and modded boot.img and twrp, i was totally in control of my device.
If you need any help with anything mtk send me a pm
also are you able to access internal storage in twrp or not ??
andromodgod said:
If you need any help with anything mtk send me a pm
also are you able to access internal storage in twrp or not ??
Click to expand...
Click to collapse
I can access internal storage in twrp. There's a choice to select the internal storage. Havent backed up to it or anything. But its there. I copied a file into it through TWRP now, and it works. I think its all about the fstab. If you don't get access to internal storage, see for any red errors in TWRP output. I can look into my fstab to see what's relevant.
I have a little hiccup though. Now my network drops (both sim at a time), even during a call. But maybe its because I swapped sim 1 and sim 2. I'll let things settle and see if it will persist. In the meanwhile, I swapped sims back to original.
bad.bid said:
I can access internal storage in twrp. There's a choice to select the internal storage. Havent backed up to it or anything. But its there. I copied a file into it through TWRP now, and it works. I think its all about the fstab. If you don't get access to internal storage, see for any red errors in TWRP output. I can look into my fstab to see what's relevant.
I have a little hiccup though. Now my network drops (both sim at a time), even during a call. But maybe its because I swapped sim 1 and sim 2. I'll let things settle and see if it will persist. In the meanwhile, I swapped sims back to original.
Click to expand...
Click to collapse
i wasn't able to access internal storage at first because device was encrypted beforehand. also sim issues might be caused by imei/nvram . check if your device imei matches your imei on the device box.
andromodgod said:
i wasn't able to access internal storage at first because device was encrypted beforehand. also sim issues might be caused by imei/nvram . check if your device imei matches your imei on the device box.
Click to expand...
Click to collapse
Ya, I fixed Imei issues. this one is like a signal drop once every 15 minutes.
bad.bid said:
I successfully ported TWRP to Panasonic Eluga Note (MTK6753) after a four day effort. Not a dev here. First time doing this.
<TLDR? skip this>
When I started using android in my HTC HD2, every ROM was pre rooted. I took it for granted.
So I get this cheapo MTK and breaking into it is like banging head against a wall!! I was frustrated with the battery drain: Device never sleeps since the last OTA!
So I learnt SP flash tools and downgraded. ( wiped nvram and created another mess in the process- which is a different story. I solved it)
I could spend this effort and time to stop that pesky "Panasonic" bootaudio too. And that's the first thing I deleted after I booted TWRP, even before rooting.
</TLDR? skipped this>
First things first, enable ADB, enable OEM unlock in developer options, and go to bootloader to unlock it <fastboot oem unlock> THIS WILL WIPE DATA!!
Second thing: Backup nvram.img by sp flash readback and learn how to flash it back (search XDA)- Sometimes you can learn from other's mistakes too! I spent a day and half writing back IMEI and WIFI Mac.
Process (if you don't trust me and want to reproduce the steps yourself)
1. Download stock firmware. (google knows)
2. Patch boot.img so that it doesn't overwrite TWRP with stock recovery on each boot (extract by Carliv Image kitchen and hash out the three lines 663, 664 and 665 mentioning "service flash_recovery /system/bin/install-recovery.sh" in init.rc). I created two copies in the same folder (boot.img, and boot-verified.img) and copied scatter into the same folder for flashing. That's what I saw in the firmware folder.
3. Port TWRP using Carliv Image Kitchen method. I downloaded TWRP from here https://forum.xda-developers.com/android/software/twrp-porter-maker-mediatek-mt67xx-32-t3681861 but didn't use their method. It didn't work. The TWRP for this chip was stated as android N, but worked well.
4. Flash ported TWRP after copying scatter file to the Carliv Imagekitchen output folder and selecting that scatter in SP droid tools. I again created recovery.img and recovery-verified.img. Don't know if its needed that way. You could wait and flash boot and recovery together from the same folder.
5. That's it, you can enter custom recovery now. Get that pesky "panasonic" bootaudio off the system/media folder now! You can stay content after this or proceed to root.
<nandroid backup now, including Nvram and NVdata. Just in case>
6. Download Supersu zip flashable and flash it via TWRP. https://download.chainfire.eu/1113/SuperSU/UPDATE-SuperSU-v2.82-20170528234214.zip?retrieve_file=1 worked for me.
7. Reboot, check root!
If you're more daredevil,
8. Download Xposed flashable zip SDK23 and flash it. Download Xposed installer and copy it to SDcard too.
9. Reboot to recovery and flash the zip. Reboot, install xposed installer. Reboot again.
You're done!
I'll upload my boot.img and ported TWRP if anyone shows any interest in this.
Cheers!
(Bonus: this phone has built in IPtables support in the kernel! I used to flash custom kernel for this ability in other Stock ROMs. AFfirewall works "out of the box"- after rooting, of course!)
Edit: uploaded my modded boot.img and ported TWRP. find it here https://drive.google.com/file/d/1sM1BnyBUFN7PfncFcM7vzIet6gKt3G_L/view?usp=sharing
If you want to go the easy route, unzip the folder and flash it with sp flash. You'll be able to boot into recovery and do the other steps for rooting.
Rememer ONLY DOWNLOAD, don't format, or format and download, or anything!
Click to expand...
Click to collapse
Can you please mention the steps and software needed for rooting the device plz plz plz
gt612 said:
Can you please mention the steps and software needed for rooting the device plz plz plz
Click to expand...
Click to collapse
No need to quote the whole post!
Download twrp and boot from here. https://drive.google.com/file/d/1sM1BnyBUFN7PfncFcM7vzIet6gKt3G_L/view?usp=sharing
download super su from the link in original post. flash iso files in the twrp boot zip (they are for the updated latest version of android 6.0.1). flash supersu via twrp. search for how to do these things.
Hello. I have an Allveiw V2 Viper S (the romanian version fo the eluga note). I got a stock rom (not from my phone) from where i took and modified both the boot.img and the recovery.img and also used the scatter from here to. I couldn`t make mtk droid tools to see my device. I managed to unlock the bootloader, but when i tried to flash the boot and recovery spft gave me a " Obtain DRAM Faild" error. Can you please help?
Thanks!
madhogg said:
Hello. I have an Allveiw V2 Viper S (the romanian version fo the eluga note). I got a stock rom (not from my phone) from where i took and modified both the boot.img and the recovery.img and also used the scatter from here to. I couldn`t make mtk droid tools to see my device. I managed to unlock the bootloader, but when i tried to flash the boot and recovery spft gave me a " Obtain DRAM Faild" error. Can you please help?
Thanks!
Click to expand...
Click to collapse
This was an impulse project. I learned many things in the way. But I have left that effort behind. So, for now: no idea. Hope google helps!
bad.bid said:
I successfully ported TWRP to Panasonic Eluga Note (MTK6753) after a four day effort. Not a dev here. First time doing this.
<TLDR? skip this>
When I started using android in my HTC HD2, every ROM was pre rooted. I took it for granted.
So I get this cheapo MTK and breaking into it is like banging head against a wall!! I was frustrated with the battery drain: Device never sleeps since the last OTA!
So I learnt SP flash tools and downgraded. ( wiped nvram and created another mess in the process- which is a different story. I solved it)
I could spend this effort and time to stop that pesky "Panasonic" bootaudio too. And that's the first thing I deleted after I booted TWRP, even before rooting.
</TLDR? skipped this>
First things first, enable ADB, enable OEM unlock in developer options, and go to bootloader to unlock it <fastboot oem unlock> THIS WILL WIPE DATA!!
Second thing: Backup nvram.img by sp flash readback and learn how to flash it back (search XDA)- Sometimes you can learn from other's mistakes too! I spent a day and half writing back IMEI and WIFI Mac.
Process (if you don't trust me and want to reproduce the steps yourself)
1. Download stock firmware. (google knows)
2. Patch boot.img so that it doesn't overwrite TWRP with stock recovery on each boot (extract by Carliv Image kitchen and hash out the three lines 663, 664 and 665 mentioning "service flash_recovery /system/bin/install-recovery.sh" in init.rc). I created two copies in the same folder (boot.img, and boot-verified.img) and copied scatter into the same folder for flashing. That's what I saw in the firmware folder.
3. Port TWRP using Carliv Image Kitchen method. I downloaded TWRP from here https://forum.xda-developers.com/android/software/twrp-porter-maker-mediatek-mt67xx-32-t3681861 but didn't use their method. It didn't work. The TWRP for this chip was stated as android N, but worked well.
4. Flash ported TWRP after copying scatter file to the Carliv Imagekitchen output folder and selecting that scatter in SP droid tools. I again created recovery.img and recovery-verified.img. Don't know if its needed that way. You could wait and flash boot and recovery together from the same folder.
5. That's it, you can enter custom recovery now. Get that pesky "panasonic" bootaudio off the system/media folder now! You can stay content after this or proceed to root.
<nandroid backup now, including Nvram and NVdata. Just in case>
6. Download Supersu zip flashable and flash it via TWRP. https://download.chainfire.eu/1113/SuperSU/UPDATE-SuperSU-v2.82-20170528234214.zip?retrieve_file=1 worked for me.
7. Reboot, check root!
If you're more daredevil,
8. Download Xposed flashable zip SDK23 and flash it. Download Xposed installer and copy it to SDcard too.
9. Reboot to recovery and flash the zip. Reboot, install xposed installer. Reboot again.
You're done!
I'll upload my boot.img and ported TWRP if anyone shows any interest in this.
Cheers!
(Bonus: this phone has built in IPtables support in the kernel! I used to flash custom kernel for this ability in other Stock ROMs. AFfirewall works "out of the box"- after rooting, of course!)
Edit: uploaded my modded boot.img and ported TWRP. find it here https://drive.google.com/file/d/1sM1BnyBUFN7PfncFcM7vzIet6gKt3G_L/view?usp=sharing
If you want to go the easy route, unzip the folder and flash it with sp flash. You'll be able to boot into recovery and do the other steps for rooting.
Rememer ONLY DOWNLOAD, don't format, or format and download, or anything!
Click to expand...
Click to collapse
Brother i try this method at Panasonic eluga ray 700 (MT6753_EB_90S55ER7_V1008) flash complete and successful install problem my set dead not On so i install original Panasonic eluga ray 700 (MT6753_EB_90S55ER7_V1008) flash set is dead and not connecting to pc plz help me what i can do ......
andromodgod said:
Brilliant Work man. I also was sort of in your situation as well . i have a panasonic Eluga A3 (Qmobile Noir E2) in my country. Stock Qmobile rom was horrendous. so i flashed the panasonic rom but hated the boot audio and the bloatware that came with it. so i decided to make a slimmed down version of it and successfully did it by using superr's kitchen. and also using the kitchen i removed the encryption on the boot.img and then patched it using magisk for easy rooting without recovery. when flashed together with the modded system.img and modded boot.img and twrp, i was totally in control of my device.
If you need any help with anything mtk send me a pm
also are you able to access internal storage in twrp or not ??
Click to expand...
Click to collapse
Panasonic eluga ray 700 (MT6753_EB_90S55ER7_V1008) after flash set is dead and not connecting to pc plz help us expert......
....
Network drop
Hello dear friend I successfully flash twrp 3.0.2 but I see network signal problem signal drop many time..
Pls tell me how to resolve these issue..
Singnal drop
bad.bid said:
Ya, I fixed Imei issues. this one is like a signal drop once every 15 minutes.
Click to expand...
Click to collapse
Dear sir panasonic eluga note network signal drop many time a day after installing ur ported twrp ..Pls tell me how to resolve signal drop issue..
Really wanna do it but your steps sound way complicated for "non-MTK pro guy". I have that device lying unused. it would be awesome if you could throw a "readme" file in your drive or here with simpler guidance steps like other "TWRP & root installation guide" we have for other phones. Plus You seem like you could port/build a ROM for this device and make substratum friendly. I know it's a big ask & I have a feeling that you like dark UI for that device too . Hoping for the best response.
If you're more daredevil,
8. Download Xposed flashable zip SDK23 and flash it. Download Xposed installer and copy it to SDcard too.
9. Reboot to recovery and flash the zip. Reboot, install xposed installer. Reboot again.
I have a doubt about these two steps
Should i have to flash it twice and have to download two separate file which is one flashable zip and installer. And in the next step 9th which zip file should i flash.
My questions might sound silly but i am asking so because when last time i tried i installed xposed, installed its firmware and then downloaded a module it was cynolockscreen something and applied it. It asked ne to reboot i did but then my phone crashed. Screen was going on and off then i rebooted to recovery and did a factory reset amd since then i haven't done any thing in my phone not even flashed the SuperSU...
Can you please help me with the further steps...
rooting eluga note
can u pls tell me how to root eluga note? i've tried many apps to root it but nothing worked
DISCLAIMER: I'm not responsible for anything that happens to your device. Use the steps below at your own risk . Be mindful of the facts unlocking bootloader voids your warranty and also hard resets your device - ALL YOUR DATA, SETTINGS, FILES AND APPS WILL BE DELETED. Rooting your device voids warranty as well. I own the Chinese SHT-AL09 8.4" LTE device and tested this root procedure ONLY WITH THIS MODEL. However, I believe there is a good chance the steps below will work for all other models of MediaPad M5, including WiFi only variants and 10" models. You MUST unlock your bootloader first. Do NOT use ramdisk image I provide in the steps below for any other model besides SHT-AL09 - doing so is guaranteed to render your device unusable. Ramdisk I provided is ONLY for SHT-AL09. You will need to extract your own ramdisk from stock firmware, specific to your device model
Credits:
@Wirmpolter - this root method largely based on his Magisk guide for Mate 9
@topjohnwu for creating the awesome Magisk Manager, which was used to patch ramdisk image with superuser binary
People, who created HuaweiUpdateExtractor
@magnumlove who pointed me in the right for developing root method in this post
This site, for hosting stock firmware for Huawei MediaPad M5
1. First, you will need to unlock the bootloader of your M5. Follow this guide
2. Transfer this patched ramdisk image to your device
Note for users with version of M5 other than SHT-AL09: Do NOT use the above ramdisk image. Download the full stock rom (update.zip) from the site I linked in the credits. Extract UPDATE.APP file from the zip. Then use HuaweiUpdateExtractor to extract ramdisk.img specific to your device. If you get errors in HuaweiUpdateExtractor - uncheck first 2 checkboxes for checksum verification on Settings tab and try again
3. Once bootloader is unlocked, install latest Magisk Manager from the official Magisk thread
4. Once Magisk Manager gives you a pop-up prompt to either download Magisk zip or patch the boot image file - chose to patch the boot image, but instead of boot.img select ramdisk.img from step 2. Magisk Manager should give you a message the image was successfully patched. It will be saved as patched_boot.img in MagiskManager folder on your sdcard. If it does not say success - do NOT proceed
5. Transfer the newly created patched_boot.img back to your PC
6. If you already have ADB and Fastboot tools installed on your PC you can just use what you've got. If not - get them from here
7. Connect your M5 to PC via USB cable
8. Run command prompt. If your ADB and Fastboot are installed as system app - you can do this from any path in CMD. If not - you need to switch in CMD to your ADB and Fastboot folder. Either way, the patched ramdisk patched_boot.img file must be in the same path, from which you will be running commands below in CMD window
9. Type "adb " in CMD window to start android debug bridge
10. Type "adb reboot-bootloader" and wait until your device restarts in Download mode
11. Once in Download mode, type "fastboot flash ramdisk patched_boot.img" - you should see some output from flash procedure, indicating successful flash
12. Once patched ramdisk is flashed, type "fastboot reboot"
That is it - you're done. Once your device reboots it will be rooted.
Note 1: Magisk Manager has it's own built-in superuser app and uses Systemless root, which works completely differently - you will not see external, standalone app like SuperSU or SU you might be familiar with in your App Drawer. The way to control the superuser app is from Magisk Manager itself: Settings->Superuser section
Note 2: I don't do tech support via PM, so don't PM me for help or with questions. Use the thread instead, and some other XDA members or myself will probably help you. Good luck!
Note 3: You may find some links to Huawei stock firmware in the 2nd post
UPDATE - August 6, 2018
Huawei officially approved 8.0.0.171 firmware with GPU Turbo for installation on SHT-AL09 devices. If you're doing first time root - just follow the original steps above. If you are already rooted and want to upgrade to 8.0.0.171 - follow the steps below:
1. Boot into download mode:
Code:
adb reboot-bootloader
from CMD window
2. Flash stock recovery from 8.0.0.171 to your device in fastboot:
Code:
fastboot flash recovery_ramdisk recovery_ramdis.img
3. Download and install the official OTA through Settings (full or just the update)
4. Boot into download mode again and flash patched ramdisk from 8.0.0.171
Code:
fastboot flash ramdisk patched_boot.img
5. OPTIONAL: If you were using TWRP or any custom recovery - you will need to reflash it back
Code:
fastboot flash recovery_ramdisk twrp.img
or whatever you named your custom recovery image
REMINDER: Do NOT use ramdisk image I provided for any other model besides SHT-AL09 - doing so is guaranteed to render your device unusable. This patched ramdisk is ONLY for SHT-AL09. You will need to extract your own ramdisk from stock firmware, specific to your device model
Needless to say, all the images you are going to flash must reside in the same directory, from which you are going to be running the CMD commands. If your ADB/Fastboot folder is not in your WIndows' PATH environmental variable - the images must be placed in the same folder where ADB/Fastboot binaries are, and CMD commands must be run from that folder.
C5Longhorn said:
Yes, they still work. I have the same model and build as you and I'm rooted.
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
I'm considering buying an SHT-W09 with firmware version 8.0.0.200 (C567), but I'd like to know if I can root it first. I do not know if the bootloader has been unlocked. Since you have the same version, can you confirm that it's possible to unlock and root, and if so, sketch out how it's done? I'm confused about whether it's possible with this firmware.
samiller said:
I'm considering buying an SHT-W09 with firmware version 8.0.0.200 (C567), but I'd like to know if I can root it first. I do not know if the bootloader has been unlocked. Since you have the same version, can you confirm that it's possible to unlock and root, and if so, sketch out how it's done? I'm confused about whether it's possible with this firmware.
Click to expand...
Click to collapse
Unlocking is possible *only* if you've gotten already your unlock code. As this service was suspended about 2 years ago there is no easy way to get it unlocked.
Small request to developers, or people with access to reliable file hosting: I don't have a developer account, so all the files I linked or referenced in the OP are hosted on free hosting sites. That file hosting has expiration date and max downloads limit, so the files will become inaccessible sooner rather than later. Please upload these files to reliable hosting and create a post with the links. I will link your post in the OP as a mirror.
In the meantime, mirror for SHT-W09 firmware: https://mega.nz/#!asVjmZrR!bW2OmXgTjnyVN4pqb9fA7OzAJ4bzil7YZxNW14qoCmk
I can confirm that this works on the 10.8" wifi model using the devices relevant ramdisk.img.
Hello, can somebody test sixaxis controller tool with root and magisk? There is a Trial in Google Play Store, that is called sixaxis compatibility checker without purchise the App. Maybe i want to buy the Tablet, but only with Dualshock 4 Support...
Just a heads up, been following threads on this forum for flashing a GSI. Now that you guys can root, you can also make backups of your own stock system image if you can't find one from Firmware Finder. Then you can safely try flashing the GSI.
@MishaalRahman well it's bit like chicken egg dilemma. As we do not have a stock system image for e.g. SHT-W09 we cannot patch the ramdisk.img and so we cannot get the stock system image ...
Thanks Apo11on, great to have root so soon for the M5! Do you know if there's a way to get Xposed working? I tried the Xposed Framework SDK 26 from inside Magisk, but it put me in a boot loop.
Question is, for those of us with the Non Pro version, can this still be done.
@OHP Yes. The OP did it with the 8.4" version which has no pro option.
I'm looking to buy the Chinese 10" wifi version myself but need Google Play Store + Services on it which I'm guessing the Chinese version doesn't have. Is one of the firmwares at the website you link to a global version of the firmware that will work on this model?
OHP said:
Question is, for those of us with the Non Pro version, can this still be done.
Click to expand...
Click to collapse
Doesn't matter what version you have as long as you have access to your device firmware and the ramdisk.img. You really need to reread the guide.
magnumlove said:
Doesn't matter what version you have as long as you have access to your device firmware and the ramdisk.img. You really need to reread the guide.
Click to expand...
Click to collapse
Problem I have is :
CMR-W09C432B123 (8.0.0.123) from download headlines.
notice the Bold letter.
my Firmware on device:
CMR-W09C432123 (8.0.0.123)
obliviously it could be nothing but I wouldn't want to brick my tablet :fingers-crossed:
OHP said:
Problem I have is :
CMR-W09C432B123 (8.0.0.123) from download headlines.
notice the Bold letter.
my Firmware on device:
CMR-W09C432123 (8.0.0.123)
obliviously it could be nothing but I wouldn't want to brick my tablet :fingers-crossed:
Click to expand...
Click to collapse
I have exactly the same tablet/firmware as you and it was fine. The additional letter also threw me a little. But if you are unsure, download Huawei Firmware Finder from Google play and it will automatically detect your tablets firmware (which you can download if you wish).
magnumlove said:
I have exactly the same tablet/firmware as you and it was fine. The additional letter also threw me a little. But if you are unsure, download Huawei Firmware Finder from Google play and it will automatically detect your tablets firmware (which you can download if you wish).
Click to expand...
Click to collapse
I took the plunge, and I am sucessfully rooted now :silly:
struggling with this part
2. Transfer this patched ramdisk image to your device
Note for users with version of M5 other than SHT-AL09: Do NOT use the above ramdisk image. Download the full stock rom (update.zip) from the site I linked in the credits. Extract UPDATE.APP file from the zip. Then use HuaweiUpdateExtractor to extract ramdisk.img specific to your device. If you get errors in HuaweiUpdateExtractor - uncheck first 2 checkboxes for checksum verification on Settings tab and try again
I have a CMR-W09 :s i can got the files downloaded and the huwai software not sure how i make a img
The good news is I followed these instructions yesterday and they worked perfectly (SHT-AL09).
The bad news is, I seem to have lost root overnight.
---------- Post added at 06:41 AM ---------- Previous post was at 06:22 AM ----------
And I figured out why I lost root; I was playing around with Developer options and switched the default GPU renderer from 'default' to 'Skia.' Apparently, this disables root access until you switch back. I regained root access on a reboot, lost it again after switching back to Skia, and then regained it after switching back to default.
I got the right image file from the site and huwai extract. I have googled how to use this app but what files do I extract as there appears to be. Alot ? I extracted all of them ? I don't have a ramdisk.img
Also thanks for writting this up. Without it I would be lost
Thanks for the efforts making this thread. Unfortunately my device is SHT-W09 and I'm still waiting for the right firmware. Is there anything I can help, considering I have the device?
@dkk6 I am in the same boat as you. Unfortunately I installed the update to 8.0.0 123 without having the Firmware Finder installed on the device. Do you have installed already the update to 8.0.0 123?
If not, you could install Firmware Finder and provide us with the ota url ...
This works perfectly no issues. i had some how maanged to download the wrong rom first. AND thankfully it did not have a ramdisk in. it is important that your firmware matches the firmware present on the site as explained. This was easy guide to follow now to flash it with somthing other then andriod
AndDiSa said:
@dkk6 I am in the same boat as you. Unfortunately I installed the update to 8.0.0 123 without having the Firmware Finder installed on the device. Do you have installed already the update to 8.0.0 123?
If not, you could install Firmware Finder and provide us with the ota url ...
Click to expand...
Click to collapse
I'm on 8.0.0.101
ULEFONE NOTE 9P, Stock rom is not real bloated, but just a little.
From Build
GQ3092SH1-HC-M629-ULEFONE-20200703_V05
Patch for the newer build (20200904-V07) is ready for sharing also.
****NOTE TESTING HAS NOT BEEN DONE ON MIXING NEW SYSTEM.IMG ON OLD VENDOR*****
****RECOMMEND DOING FULL UPDATE OR DOWNGRADE BEFORE FLASHING MODIFIED SYSTEMS****
Stock roms are published on ULEFONE gdrive.
https://drive.google.com/drive/folders/1Bq16pmRMaFEVT_xZilWhhdzTzk9fojV8
I removed the adupus/FOTA apps, child mode, simple_mode, mfg customization to chrome, verizon provider remote sim lock app.
Added adaway hosts file for ad-blocking in browser.
Flashed back to phone in same way as flashing GSI rom.
adb reboot fastboot (fastbootd, not bootloader)
fastboot flash system modified-system.img ( fastboot.exe on pc needs to be from July 202 or newer)
when flashing is done, from menu on phone screen select boot to recovery.
perform factory reset and reboot.
https://www.androidfilehost.com/?w=files&flid=318156
In case you are wondering , how I made changes. I will tell you.
I used SuperR-Kitchen script/ tool
credits to @SuperR.
Start a new project. Add the stock firmware. Needs to be as a zip. So extract the embed-ed *.rar file downloaded from Ulefone. Re-zip just the contents of the final folder. In other words, the zip needs to be the files, not the files inside a folder, inside other folder.
The kitchen will ask if you want to extract the vendor and product images and use them in you rom. I did not make changes to those partitions, so did not extract or include them.
When unpacking is completed. You can browse the extracted system folder.
The attached files have an .txt extension in order to upload them here. But in the kitchen tool you need to remove the extension.
Code:
Add "host" file to /system/system/etc in your extracted rom folder and replace host file that is already there.
Add "bloat_custom" to the kitchen folder "super_r/tools/root/
run #6 debloat menu then #2custom debloat option from kitchen #8 rom tools menu
run deodex option from #8 rom tools
When edits are done. Use #8 rom tools , #7 build menu, #2 build etx4 img
select system, then sparse, system.img
Keep permission type as raw_image
That's all. Use caution when adding additional programs you want removed.
Hi. On Ulefone Gdrive, there are both android 10 and 11 rom files. but it says upgrading from 10 to 11 is 'forbidden'. Is there any way to bypass this restriction?
Edit for those who are wondering: Ulefone has removed the restriction and it can be upgraded to android 11 without any issue. You do lose your data during the process, though.