Related
(STEP 1 GOLDCARD)
Finaly i done it all phew i had a really long day learning yesterday from the start i was on the tmobile latest rom RUU_Hero_TMobile_UK_2.73.110.26_release_signed_NoDriver.exe
I figured out the goldcard soulotion http://forum.xda-developers.com/showthread.php?t=572683
Great video guide here http://theunlockr.com/2009/10/18/how-to-downgrade-your-htc-hero-so-it-can-be-rooted/
01. Download QMAT 5.06 here http://revskills.de/downloads/qmat_506.zip
It’s a demo version so will only run for 10 minutes.
02. Format your SD card to FAT32. Please keep in mind some brands of SD cards do not work. Note sd card must be in phone here
03. Use adb to run this command: adb shell cat /sys/class/mmc_host/mmc1/mmc1:*/cid
04. Copy the SD card cid code displayed after the adb command.
05. Start Qmat and Click on Cyptoanalysis Tools > Crypto Toolbox.
06. Look at the bottom, there is a text box (beside the “Reverse String” button) enter the SD card cid code you got earlier.
Click on the “Reverse String” button, the result is reversed…
Example: 532600bd227d9c0347329407514d5402
07. Copy the reversed SD card cid code.
08. Go to QMAT goldcard site here http://revskills.de/pages/goldcard.html to generate your goldcard (yes it says for G1 but works for our Hero too).
09. Enter your email. For the correct SD card cid code, you need to replace the first 2 characters to 00.
Example: From “532600bd227d9c0347329407514d5402” to “002600bd227d9c0347329407514d5402”
10. Click Continue and you will receive the goldcard.img in .zip format in your email.
11. Go to your email, download the zip file and save it to a directory and unzip it to goldcard.img
12. Download HxD Hex Editor from here http://download.cnet.com/HxD-Hex-Editor/30....html?tag=mncol
13. Install and launch HxD Hex Editor program. Note SD Card has to be in your pc or reader here at this point NOTE ALSO (run the editor as administrator in order for it to appear)
14. Go to Extra tab > Open Disk. Under Physical disk, select Removable Disk (Must be your SD card), uncheck “Open as Readonly), click OK.
15. Go to Extra again, Open Disk Image, open up goldcard.img which you’ve saved/unzipped earlier.
Now, you should have two tabs, one is your removable disk, the other is goldcard.img. Press OK when prompted for “Sector Size” 512 (Hard disks/Floppy disks), click OK.
16. Click on goldcard.img tab. Go to Edit tab > Select All, edit tab again > copy.
17. Click on the “removable disk” tab. Select offset 00000000 till offset 00000170 (including the 00000170 line), click on Edit tab and then Paste Write.
18. Click on File > Save. now you can exit the program.
19. Reboot your phone with this SD Card (now GoldCard) inside
20. Use the Official HTC RUU to downgrade to 2.73.405.5 here ftp://xda:[email protected]/Hero...ed_NoDriver.exe
from which you can fastboot boot and/or root your phone with flashrec Here http://forum.xda-developers.com/showthread.php?t=559613 (Please see guide below for this)
Done.
(STEP 2 recovery)
You need to install this recovery first with flashrec instructions below
You can use flashrec to flash the patched recovery, from where you can do all the usual stuff (and even put the old hboot back on if you want!)
Notice:
flashrec is using an exploit that isn't patched yet in the current kernel used by HTC, however if/when HTC patches this, flashrec will stop working.
So for now it's ok but a next version might have patched this, so keep this in mind !
Quick Howto:
1. On your phone, goto Settings, Applications, and make sure Unknown source is checked ON.
2. On your phone, goto Settings, SD card and phone storage, and click Unmount SD card.
3. Then click Format SD card (it should automatically remount after this).
4. Plug the phone into the compuer via USB, then pull down the notification bar and click on the SD card notification. Then click mount.
5. Download this APK and recovery image and save it to your computer:
flashrec-20090815.apk
Cyanogen’s / Modaco Hero Recovery Image
Update: updated flashrec here
6. Extract the cm-hero-recovery.img out of the MoDaCoPatchedRecovery-1.0.zip and put it somewhere on your computer.
7. Save both the cm-hero-recovery.img and the flashrec-20090815.apk to your computer, then copy them both to your SD card
(do NOT put them inside any folders on the SD card, just put them in the root of the SD card itself).
8. Unplug the phone from the computer once they are downloaded to the SD card.
9. Goto the Market and download Linda File Manager or any file manager program if you do not already have one.
10. Open the file manager and goto SDCard and then find the flashrec-20090815.apk file and click on it.
If asked, tell it to use Package Installer to open it. It should automatically install the apk.
11. Open the FlashRec program and click on Backup Recovery Image and wait for it to finish.
12. Once done, click on the empty text box in the FlashRec program and type:
sdcard/cm-hero-recovery.img
Then click on the Flash Custom Recovery Image button and wait for it to finish.
13. Turn off the phone and turn it on into Recovery mode by holding down Home and Power to turn it on
(keep holding until the recovery screen comes up has a bunch of text on a black background).
As long as that screen comes up, you have done it correctly and can now go and load other ROM/hboot/whatever.
THIS IS OPTIONAL RECOVERY BELOW BETTER OPTIONS BUT YOU NEED THE ABOVE RECOVERY FIRST
I then flashed the new recovery-RA-HERO-v1.2.3 Great Video guide here http://theunlockr.com/2009/10/15/how-to-flash-a-new-recovery-image-if-you-are-already-rooted/
http://forum.xda-developers.com/showthread.php?t=561124
There are several ways to install a custom recovery, choose the one that suits you most
via adb -> Requires a custom recovery (with test-keys) like Cyanogen's v1.4 or my previous recovery
Code:
Copy recovery-RA-HERO-v1.2.3.img to the root of your sdcard
Boot into your current custom recovery (boot while holding HOME)
Connect your Hero via usb to your pc/mac/...
adb shell
$su (not required if you have root already)
#mount -a
#flash_image recovery /sdcard/recovery-RA-HERO-v1.2.3.img
(STEP 3 INSTALL CUSTOM ROM)
Then i installed the cool modaco custom rom v2.8 to my phone http://android.modaco.com/content/htc-hero...com/292018/xda/
Great Video guide here http://theunlockr.com/2009/08/27/how-to-load-a-custom-rom-on-your-htc-hero/
Also dont forget to upgrade your radio here http://android.modaco.com/content/htc-hero...ate-zip-format/
Download the latest one normally on the top to install rename the zip to Update put on root of SD card and boot into recovery and install update.zip option easy as that.
STEP 4 PARTITION SD CARD)
Then finaly i partioned my sd card using the recovery imiage with thease commands directly from the phone in recovery.
I ran the following commands in this order from recvoery mode:
- Wipe data + cache (factory reset)
- Wipe ext partition on SD-card
- Wipe Dalvik-cache on SD-card (NOT on /data !) [email protected] ALWAYS WORK
- Partition SD-card : 500MB Ext2, 32MB Swap, remaining Fat32
- Convert ext2 to ext3
- Installed ROM
ANOTHER GREAT GUIDE HERE FOR WINDOWS TERMINAL USERS http://androidandme.com/2009/08/news/how-to-manually-partition-your-sd-card-for-android-apps2sd/
what a nice day and now i have a super hero
PS ANY QUESTIONS I WOULD BE GLAD TO HELP WITH ANY PROBLEMS THATS WHAT I AM HERE FOR THANKS.
Mods if you think this is usefull for noobs then you may sticky if you want thanks to all.
If anyone wants to add anything or finds something wrong with the guide please let me know so i can edit it thanks to all that made this possible.
hi, i got an error 170 when trying to do step 20 in section 1(downgrade rom)!
GaRd3NiA said:
hi, i got an error 170 when trying to do step 20 in section 1(downgrade rom)!
Click to expand...
Click to collapse
you could have not done the steps corectly my advice is to start again from the start.
What is the point of this gold card process? Noobish question i am sure just i have a rooted phone already so will this give me anything additonal guys? Ta
MojUk said:
What is the point of this gold card process? Noobish question i am sure just i have a rooted phone already so will this give me anything additonal guys? Ta
Click to expand...
Click to collapse
the point of this is for users that upgraded to the new rom and can't downgrade back and updated there hboots u need the goldcard the rest is all optional hence the road to freedom for your hero.
need help
hi. is this procedure it will work with Htc Hero from Hong Kong? i was trying several procedures founded on google, but no one worked.
QMAT 5.06 link has changed
https://ssl.webpack.de/revskills.de/pages/download.html
HTC Hero problems after gold card procedeure
jutley said:
(STEP 1 GOLDCARD)
Finaly i done it all phew i had a really long day learning yesterday from the start i was on the tmobile latest rom RUU_Hero_TMobile_UK_2.73.110.26_release_signed_NoDriver.exe
I figured out the goldcard soulotion http://forum.xda-developers.com/showthread.php?t=572683
Great video guide here http://theunlockr.com/2009/10/18/how-to-downgrade-your-htc-hero-so-it-can-be-rooted/
01. Download QMAT 5.06 here http://revskills.de/downloads/qmat_506.zip
It’s a demo version so will only run for 10 minutes.
02. Format your SD card to FAT32. Please keep in mind some brands of SD cards do not work. Note sd card must be in phone here
03. Use adb to run this command: adb shell cat /sys/class/mmc_host/mmc1/mmc1:*/cid
04. Copy the SD card cid code displayed after the adb command.
05. Start Qmat and Click on Cyptoanalysis Tools > Crypto Toolbox.
06. Look at the bottom, there is a text box (beside the “Reverse String” button) enter the SD card cid code you got earlier.
Click on the “Reverse String” button, the result is reversed…
Example: 532600bd227d9c0347329407514d5402
07. Copy the reversed SD card cid code.
08. Go to QMAT goldcard site here http://revskills.de/pages/goldcard.html to generate your goldcard (yes it says for G1 but works for our Hero too).
09. Enter your email. For the correct SD card cid code, you need to replace the first 2 characters to 00.
Example: From “532600bd227d9c0347329407514d5402” to “002600bd227d9c0347329407514d5402”
10. Click Continue and you will receive the goldcard.img in .zip format in your email.
11. Go to your email, download the zip file and save it to a directory and unzip it to goldcard.img
12. Download HxD Hex Editor from here http://download.cnet.com/HxD-Hex-Editor/30....html?tag=mncol
13. Install and launch HxD Hex Editor program. Note SD Card has to be in your pc or reader here at this point NOTE ALSO (run the editor as administrator in order for it to appear)
14. Go to Extra tab > Open Disk. Under Physical disk, select Removable Disk (Must be your SD card), uncheck “Open as Readonly), click OK.
15. Go to Extra again, Open Disk Image, open up goldcard.img which you’ve saved/unzipped earlier.
Now, you should have two tabs, one is your removable disk, the other is goldcard.img. Press OK when prompted for “Sector Size” 512 (Hard disks/Floppy disks), click OK.
16. Click on goldcard.img tab. Go to Edit tab > Select All, edit tab again > copy.
17. Click on the “removable disk” tab. Select offset 00000000 till offset 00000170 (including the 00000170 line), click on Edit tab and then Paste Write.
18. Click on File > Save. now you can exit the program.
19. Reboot your phone with this SD Card (now GoldCard) inside
20. Use the Official HTC RUU to downgrade to 2.73.405.5 here ftp://xda:[email protected]/Hero...ed_NoDriver.exe
from which you can fastboot boot and/or root your phone with flashrec Here http://forum.xda-developers.com/showthread.php?t=559613 (Please see guide below for this)
Done.
(STEP 2 recovery)
You need to install this recovery first with flashrec instructions below
You can use flashrec to flash the patched recovery, from where you can do all the usual stuff (and even put the old hboot back on if you want!)
Notice:
flashrec is using an exploit that isn't patched yet in the current kernel used by HTC, however if/when HTC patches this, flashrec will stop working.
So for now it's ok but a next version might have patched this, so keep this in mind !
Quick Howto:
1. On your phone, goto Settings, Applications, and make sure Unknown source is checked ON.
2. On your phone, goto Settings, SD card and phone storage, and click Unmount SD card.
3. Then click Format SD card (it should automatically remount after this).
4. Plug the phone into the compuer via USB, then pull down the notification bar and click on the SD card notification. Then click mount.
5. Download this APK and recovery image and save it to your computer:
flashrec-20090815.apk
Cyanogen’s / Modaco Hero Recovery Image
Update: updated flashrec here
6. Extract the cm-hero-recovery.img out of the MoDaCoPatchedRecovery-1.0.zip and put it somewhere on your computer.
7. Save both the cm-hero-recovery.img and the flashrec-20090815.apk to your computer, then copy them both to your SD card
(do NOT put them inside any folders on the SD card, just put them in the root of the SD card itself).
8. Unplug the phone from the computer once they are downloaded to the SD card.
9. Goto the Market and download Linda File Manager or any file manager program if you do not already have one.
10. Open the file manager and goto SDCard and then find the flashrec-20090815.apk file and click on it.
If asked, tell it to use Package Installer to open it. It should automatically install the apk.
11. Open the FlashRec program and click on Backup Recovery Image and wait for it to finish.
12. Once done, click on the empty text box in the FlashRec program and type:
sdcard/cm-hero-recovery.img
Then click on the Flash Custom Recovery Image button and wait for it to finish.
13. Turn off the phone and turn it on into Recovery mode by holding down Home and Power to turn it on
(keep holding until the recovery screen comes up has a bunch of text on a black background).
As long as that screen comes up, you have done it correctly and can now go and load other ROM/hboot/whatever.
THIS IS OPTIONAL RECOVERY BELOW BETTER OPTIONS BUT YOU NEED THE ABOVE RECOVERY FIRST
I then flashed the new recovery-RA-HERO-v1.2.3 Great Video guide here http://theunlockr.com/2009/10/15/how-to-flash-a-new-recovery-image-if-you-are-already-rooted/
http://forum.xda-developers.com/showthread.php?t=561124
There are several ways to install a custom recovery, choose the one that suits you most
via adb -> Requires a custom recovery (with test-keys) like Cyanogen's v1.4 or my previous recovery
Code:
Copy recovery-RA-HERO-v1.2.3.img to the root of your sdcard
Boot into your current custom recovery (boot while holding HOME)
Connect your Hero via usb to your pc/mac/...
adb shell
$su (not required if you have root already)
#mount -a
#flash_image recovery /sdcard/recovery-RA-HERO-v1.2.3.img
(STEP 3 INSTALL CUSTOM ROM)
Then i installed the cool modaco custom rom v2.8 to my phone http://android.modaco.com/content/htc-hero...com/292018/xda/
Great Video guide here http://theunlockr.com/2009/08/27/how-to-load-a-custom-rom-on-your-htc-hero/
Also dont forget to upgrade your radio here http://android.modaco.com/content/htc-hero...ate-zip-format/
Download the latest one normally on the top to install rename the zip to Update put on root of SD card and boot into recovery and install update.zip option easy as that.
STEP 4 PARTITION SD CARD)
Then finaly i partioned my sd card using the recovery imiage with thease commands directly from the phone in recovery.
I ran the following commands in this order from recvoery mode:
- Wipe data + cache (factory reset)
- Wipe ext partition on SD-card
- Wipe Dalvik-cache on SD-card (NOT on /data !) [email protected] ALWAYS WORK
- Partition SD-card : 500MB Ext2, 32MB Swap, remaining Fat32
- Convert ext2 to ext3
- Installed ROM
ANOTHER GREAT GUIDE HERE FOR WINDOWS TERMINAL USERS http://androidandme.com/2009/08/news/how-to-manually-partition-your-sd-card-for-android-apps2sd/
what a nice day and now i have a super hero
PS ANY QUESTIONS I WOULD BE GLAD TO HELP WITH ANY PROBLEMS THATS WHAT I AM HERE FOR THANKS.
Mods if you think this is usefull for noobs then you may sticky if you want thanks to all.
Click to expand...
Click to collapse
hi, was following your procedure in order to crezte the Gold Card. Everything goes perfect up to step 20. After I used to flash with RUU_Hero_HTC_WWE_2.73.405.6_WWE_release_signed_NoDriver.exe; big mistake. after flashing I can't put phone in recovery mode, it showing a triangle with a exclamation mark in the center, also GPS is not existing at all, 3 G network not present. My phone has been bought from Hong Kong.
I was trying to follow the steps to recovery but useless; flashrec-20090815.apk is not working, even the new versions. If someone can help me with some advices, i'm really desperate. thanks
help please!!!!
Hi all. after I create the gold card, see link http://forum.xda-developers.com/showthread...187#post5036187, I RUU my Htc Hero from Hong Kong with SEA: (South East Asia)
RUU_Hero_HTC_Asia_SEA_WWE_2.73.728.5_release_signe d_NoDriver.exe and I'd seen there is no GPS, Market and 3G, than I'd applied another RUU RUU_Hero_HTC_WWE_2.73.405.66_WWE_test_signed_NoDri ver.exe and this time I have Market, but still no GPS and 3G. I tried different RUU from http://forum.xda-developers.com/showthread.php?t=559622, but no one working, not even the previous two. I tried to use flashrec-20090815.apk in order to flash, but no working. even the new version of flashrec not working. I tried to put in recovery mode holding POWER + HOME button, but after boot is showing a triangle with exclamation mark in the middle. Same is happening if I try to go in recovery mode from ADB (command adb shell reboot recovery). Is somebody so kind to explain me what to do in order to restore my phone at least how it was before, please? My skills in android development are 0. thanks
help please!!!!
so, nobody wants to help me ? i'm really desperate ...........
finally, I made again the gold card, after I re flash with RUU_Hero_HTC_WWE_2.73.405.5_WWE_release_signed_NoDriver.exe, and works. Than I used flashrec-1.1.3-20091107-2.apk and recovery-RA-hero-v1.5.2.img and I created Backup.img. Tried to put in recovery mode by pressing in the same time Power and Home and I got the following screen:
"reboot system now [Home+Back]
apply sdcard:update.zip [Alt+S]
wipe data/factory reset [Alt+W]"
"E:Can't open /cache/recovery/command"
BTW, GPS and 3G still missing from menu. Trying to update with 2.8-update-hero-modacocustomrom-core-chinese-signed.zip or with 3.0-update-hero-modacocustomrom-core-signed.zip, I got this :
" -- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:No signature (663 files)
E:Verification failed
Installation aborted."
Phone hanging, freezing.... HELPPPPPP please!!!!!!!!
I forgot to mention these details:
Original version
phone type is EBI132A
Firmware version: 1,5
baseband version 63.18.55.06EU_6.35.06.18
Kernel Version:**2.6.27 - 44690c1a
Build no: 2.73.721.9 **146733 CL#62020
Soft Version 1.0.0.A 6288
Actual version
Firmware version: 1,5
baseband version 63.18.55.06EU_6.35.06.18
Kernel Version:**2.6.27 - 8dd6deee [email protected])
Build no: 2.73.405.5**146733 CL#61267
Soft Version 1.0.0.A 6288
this is what I got:
What else i can do?
Is there anyone here in this forum who has been complimentary to this guide? I ask because I am an organizer of the recognition awards for Achievement in Technical Writing & Guides (to help people use their phones)... And the Android forums are new, and thus there has been very little response to the intention to recognize those who have contributed knowledge, apps, themes, guides to the community.
thank you. see my sig.
ovigt71 said:
I forgot to mention these details:
Original version
phone type is EBI132A
Firmware version: 1,5
baseband version 63.18.55.06EU_6.35.06.18
Kernel Version:**2.6.27 - 44690c1a
Build no: 2.73.721.9 **146733 CL#62020
Soft Version 1.0.0.A 6288
Actual version
Firmware version: 1,5
baseband version 63.18.55.06EU_6.35.06.18
Kernel Version:**2.6.27 - 8dd6deee [email protected])
Build no: 2.73.405.5**146733 CL#61267
Soft Version 1.0.0.A 6288
Click to expand...
Click to collapse
Hi, I have the exact same hero as you do (same system etc..). Didn't work with the "RUU_Hero_HTC_WWE_1.76.405.1_R3_WWE_release_signed_NoDriver.exe"
so am now about to try it with this one:
RUU_Hero_HTC_WWE_2.73.405.5_WWE_release_signed_NoDriver.exe
but after reading you post I am a lil weary...
is you hero still not working 100%??
Thx
1. Bricked my rooted G2 with 2.1 rom by interrupting the radio update process
2. Got it back within 5 days repaired in warranty FOC! mainboard replaced.
3. Flashrec backup recovery did not work, so had to go into goldcard method. (2.73.110.26 CL#69351)
4. Update succesfull. I thank you very much for your efforts Even the ugly static G2 T-Mobile screen now says HERO
5. Linda File Manager + FlashREC
6. Backup recovery -> Backup complete
THANKS
I got a Customer Id Error when I try to install either
RUU_Hero_HTC_WWE_1.76.405.1_R3_WWE_release_signed _NoDriver.exe
or
RUU_Hero_HTC_WWE_2.73.405.5_WWE_release_signed_NoD river.exe
I thought the purpose of the GoldCard was to help bypass the ID checking?
bob_harris said:
I thought the purpose of the GoldCard was to help bypass the ID checking?
Click to expand...
Click to collapse
It is - the point is that the creation of a goldcard is not an exact science. If your goldcard is not correct, for any reason, it won't work.
There have been many accounts on these forums of people having to try 3 or 4 times (usually using different SD cards) before getting a goldcard that works.
Regards,
Dave
foxmeister said:
It is - the point is that the creation of a goldcard is not an exact science. If your goldcard is not correct, for any reason, it won't work.
There have been many accounts on these forums of people having to try 3 or 4 times (usually using different SD cards) before getting a goldcard that works.
Regards,
Dave
Click to expand...
Click to collapse
I got it working on the second attempt. In the tutorial I was reading it advice I use a separate sd card reader when creating the gold card.
On my second attempt I just left the card in the phone the whole time and mounted it through the phone when I needed to perform hex editing on it.
Lovely job, now to choose what custom ROM I shall flash.
HI all,
Dexter wrote a super-cool folio 100 mod including Android Market, Flashplayer and much better performance. You find it here: http://dext3r.komodin.org/folio100/FolioModv13d.zip. I think this makes the folio 100 finally useful.
When I wanted to install it, however, I had to overcome several hurdles (which had nothing to do with Dexters work). Therefore, I thought that it would be useful to post a full description of what I had to do here.
1. Download the mod from the URL above. Put the update.zip file which you find in the archive into the root of an SD-Card with at least 150-200 MB of free space.
2. Shut down you folio 100
2. Put the SD Card into your folio 100
3. Start your folio 100, when you see boot image push "Power" and "Vol +" quickly (you only have 3 seconds to do this) ==> You should now see a message explaining that are in the recovery menu!
4. Press VOL + Factory reset or system update.
5. Press VOL - to continue to system update.
6. Press VOL + to confirm system update
==> WHEN ALL GOES FINE UPDATE SHOULD NOW START AND THE DEVICE WILL AUTOMATICALLY REBOOT (it is possible that you must shutdown and restart manually after update. This is the case when the android label is shown but the device does not start for a very long time).
BUT for some of you (including me) this will fail and you will see a text on the screen like booting recovery kernel image and the tablet freezes there.
In this case, it seems that your recovery image used to run updates is broken and you must first reload a working recovery image.
Now it gets a bit hairy:
We will use Android Development Environment and load a working recovery image via USB. Here are the steps:
1. Download the Android SDK here: http://developer.android.com/sdk/index.html. For Windows users I suggest to get the zip and NOT put it in Program Directory unless you want to run all commands with administrator privileges.
2. Now we must extend the drivers section to be able to load software onto our folio tablet. Goto %android_install_dir%/usb_driver/android_winusb.inf and enter the following lines in the sections [Google.NTamd64] and [Google.NTx86] (depending on your systems architecture you could place it only in one section but why not in both?).
;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
3. Last but not least you should ensure that the comand fastboot.exe located under %android_install_dir%/tools knows where it finds the AdbWinApi.dll. Test this by running the tool without option from a command line. If you get and error message add the path to AdbWinApi.dll to your PATH variabe. The path is usually: %android_install_dir%/platform-tools . The PATH variable you can enter under Control Panel->Maintenance->System->Environment Variables.
4. Now you must run your table in fastboot mode. To do so you should start your folio tablet and on the Toshiba loading screen quickly press 3 times the startbutton and then the VOL + button.
5. The tables should print a message that it is now in fastboot mode. Connect it via USB to your PC.
6. Windows will try to load a driver but it will fail to recognise it. Choose the option to manually add a driver. Ensure to manually select a file NOT search in a directory and select the aforementioned file %android_install_dir%/usb_driver/android_winusb.inf .
7. Windows will ask you what driver you want to lead. Choose Bootloader and Windows will install it.
8. In Dexters update.zip for the foliomod (mentioned above and found inside the package here: http://dext3r.komodin.org/folio100/FolioModv13d.zip) is a working recovery.img. Extract this image (file recovery.img) and best place it under %android_install_dir%/tools.
9. Now we are ready to replace the faulty recovery image. Open a command line and go to %android_install_dir%/tools. Type:
fastboot erase recovery
this will erase the old recovery image.
10. Now lets laod the working recovery image. Type
fastboot flash recovery recovery.img
this will load the recovery.img of Dexter which we placed in the %android_install_dir%/tools folder before. Note: If you do want to place the img file in this folder you must indicate the full path to it inside the command.
11. Now we are nearly done. You can unplug your tablet and restart the update procedure for the foliomod as described at the beginning of this post. This time the update should work fine.
Well, I hope this helps someone. At least in my case the update worked and I thought it might be use to sum up all information.
Best regards
Patrick
hi,
in order to rewrite the recovery image, do i need to be root ?
no, because the update.zip is signed with the same key toshiba's deployed is latest release.
enricogatti said:
hi,
in order to rewrite the recovery image, do i need to be root ?
Click to expand...
Click to collapse
Do I need the OS update for my Folio 100
Hi there,
I am a bit confused. I have installed the Super Dexter Folio 100 mod and it is great. Do I then need the OS update??
I cannot download it from Toshiba web site. After the Dexter install. the data needed like Model no. Serial no. and Part no. is blank !!
Any ideas.?
Regards,
Per.
If you have installed Foliomod 1.4 there is no need to update.
Foliomod 1.4 has the update integrated.
blank part and serial no
sorry,
but i have to enter correct model, part and serial numbers in order to send it back to Toshiba, how can we do?
Regards
Why do you need these numbers? They are not needed for custom roms.
in order to revert to original toshiba's rom to send it again for repair.
This method worked perfect for me, while I was having trouble with the other one. Thanks alot!
Thank you very much. You saved my life.
I was searching for days to fix my folio!!!
It worked excellent for me. Now everything is fine.
Downgrade
If I installed the toshiba stock rom it will be perfctly good. I mean the model number an so on..
i was to hasty when i bought my folio and i update my firmware to the latest , is there any way to downgrade ? , i tried both this way and an ADB shell command to restore my recovery image , but my recovery still dont start , after i press power button followed by VOL + it just goes black for 5 sec and then boots android with no message at all, :/ , possible to fix it ?
tried using fastboot to install update.zip but failed.
=>
C:\Program Files\Android\android-sdk\platform-tools>fastboot update update.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
<=
I don't know why the 'thanks' button isn't active for TS. But thanks for your comprehensive guide to put another ROM on the device. The Fastboot method of replacing recovery.img worked like a charm .
Hello,
Thanks for this very clear tutorial... but...
When I try to execute the fastboot command, the prompt hangs:
C:\Program Files (x86)\Android\android-sdk\tools>fastboot erase recovery
< waiting for device >
Click to expand...
Click to collapse
What to do?
Kind regards,
Daniel
Failed (remote: (00030003))
always this !!! I can't flash anything !!!
Hi, I tryed to reinstall, but 9th step is problem, because Commander in Windows 7 don't know this tag...
I can't connect to my touchpad by this tag
fastboot erase recovery
In others forums I found some notes about fastboot.exe, but this application is not in folder tools.
Can you some help me?
Thanks
In newer SDK versions it's in platform-tools.
so ,everything works installing it this way , but after that how do i get into recovery?
if i use "power" and "volume up" i'm getting the old recovery.
CWM 5.0.2.6 Recovery
Stable with all features working.
Features:
Working:
Backup&Restore
Installing ZIP from SD Card
Wipe DATA,CACHE,Dalvik-Cache,Battery Stats
EXT4 support for sd-ext(A2SD) partition
Added support for HOME, MENU,SEARCH & back button for menu navigation.
Volume key bug totally fixed
Enabled USB Mass Storage mount support during recovery.
Enabled ADB support during recovery.
All other functions working in the previous version.
Instructions:
Installation:
Download recovery image and save it in the root of your SD Card
Go to Terminal Emulator and type:
Code:
>su
>flash_image recovery /sdcard/recovery.img
>reboot recovery
Navigation:
UP:Home Button,Volume UP.
DOWN:Menu Button ,Volume DOWN
SELECT:Search Button,Power Key.
BACK:Back Button
Download Link:
HTML:
http://dl.dropbox.com/u/21654931/recovery.img
Credits:
Koush for his source
TJStyle for his kernel
Source:https://github.com/mb-14/android_device_fih_fm6
Note:
If ITE users are facing problems with CWM try this ITE version created by s2k7:
http://www.multiupload.com/0UA3OKWFWC
Nice one ! Thank you !
Thanks a lot, GHome
Sent from my HTC Sensation Z710e using XDA App
Thank manys man.
Volume key navigation is still bugged
LayZeeDK said:
Volume key navigation is still bugged
Click to expand...
Click to collapse
I know its bugged but i provided an alternative for up-down navigation i.e home key and menu key
googlehome said:
I know its bugged but i provided an alternative for up-down navigation i.e home key and menu key
Click to expand...
Click to collapse
Yes, that works
Sent from my HTC Sensation Z710e using XDA App
CWM 3.0.2.8 Recovery works good and stable on Viewsonic ViewPad 7.
Thank you again Googlehome, you're the best.
Not working for me on HWVer 1.06 and Android 2.2.2.
Won't let install me. Not enough memory when flashing.
CWRecovery 2.x works.
astuermer said:
Not working for me on HWVer 1.06 and Android 2.2.2.
Won't let install me. Not enough memory when flashing.
CWRecovery 2.x works.
Click to expand...
Click to collapse
Is your device running low on internal storage and/or available RAM ?
It was a quick & easy install/update for me - did it right after I re-flash one of the custom ROM upon rooting & the Vpad7 running. Followed instructions above & it was done - then, I restore settings, etc.
The newer Recovery is much improved & better, with more options to choose from. It shouldn't take up much, if any memory, to flash & install this at all ....
80 mb ram left...
flashed over cwrecovery 2.x and got errors.
i didn't try restarting the device - instead i reflashed cwrecovery 2.x and got no errors.
I also tried it with ROM Manager.
I manually select N700... and then CW 3.x.x
When trying to install i get an error message that installing went wrong.
If I install it manually via Shell I get many error messages (see posting before). Looks like the partition table is a bit changed since the CW 2.x is smaller than CW 3.x.
astuermer said:
Not working for me on HWVer 1.06 and Android 2.2.2.
Won't let install me. Not enough memory when flashing.
CWRecovery 2.x works.
Click to expand...
Click to collapse
Please provide exact error message.
mtd: read error at 0x00100000 (Out of memory)
...around 100 times
...with different read/re-read/write errors and different adresses (0x...)
Any idea?
astuermer said:
mtd: read error at 0x00100000 (Out of memory)
...around 100 times
...with different read/re-read/write errors and different adresses (0x...)
Any idea?
Click to expand...
Click to collapse
(Re-reading your posts) So, this is while you are trying to flash the downloaded recovery.img file saved to mSD card using Terminal connected to PC, and it even popped up with CWM 2.x ?
Tried using a fully wiped clean & different mSD card (re-formatted on PC with FAT32 or FAT) - I use a spare 2 GB or 4 GB mSD card to try out new Roms to avoid having to "corrupt" or risk losing all the "stuff" on the fast 16GB mSD card.
Have a spare PC or do it on a different one with another OS - Vista, Windows 7, etc. (done mine with XP SP3) & substitute a different mini-usb cable ? It seemed that the data transfer process between the "machines" could be the problem - a bad "connector" ?
Maybe try a fresh copy of your toolkits like fastboot-adB, su & busybox - SDK etc. are in the same directory/folder - and not missing ?
Here's a XDA link to a useful shell tool - Droid Explorer - good for exploring what's on your device - use it with extreme caution as the "Tools" it provided can be used to flash ROM, etc. (NOT tested or proven to work specifically with Vpad7 .... fine to use it to identify & read data, etc.) - http://de.codeplex.com/
Thanks, but I flashed it with "flash_image" and the tool "Shell Commander" directly on the device.
I used this tutorial for Clockwork 2.x...
http://android.modaco.com/topic/324042-clockwork-recovery-for-mi700n700viewpad-7/
And the same way I flashed Clockwork 3.x from the first post here.
The Clockwork Recovery 2.x I am using has 4.591.616 bytes.
Clockwork 3.x has 4.745.216 bytes - so it seems to me it's too big for the recovery partition.
astuermer said:
Thanks, but I flashed it with "flash_image" and the tool "Shell Commander" directly on the device.
I used this tutorial for Clockwork 2.x...
http://android.modaco.com/topic/324042-clockwork-recovery-for-mi700n700viewpad-7/
And the same way I flashed Clockwork 3.x from the first post here.
The Clockwork Recovery 2.x I am using has 4.591.616 bytes.
Clockwork 3.x has 4.745.216 bytes - so it seems to me it's too big for the recovery partition.
Click to expand...
Click to collapse
Those *.img files aren't the right size - I checked mine & also copies of the download that I kept, CWM 3.x is ONLY 4,484 kb or 4.37 MB in size (named: cwrecovery.img)
Similar recovery *.img are somewhere between 4 and 5 MB in size only including the stock recovery.img that I've saved. You might want to re-download using Googlehome's dropbox link on top of this post and tried it.
Then, connect device via usb cable to computer, execute terminal and push it onto device (follow GH's steps) I felt that those steps outline in the MoDaCo site a bit confusing when rooting - of course, that's just me (and, I ended up using GingerBreak to root, but 2nd. time around - the One Click worked too)
Something just doesn't look right from you description ....
That's what I did...
Flashing the same way CWR 2.5.1.2. results in no errors and a flashed recovery.
PS: I already tried downloading from the dropbox link several times, copied it over to my SD. No success when flashing...
PPS: 2 GB free on SD, 54 MB free internal memory and 181+77 MB free RAM.
Maybe you have the wrong flash_image. There are at least two different versions of it here on XDA, and I had trouble with one of them on my VPad. Unfortunately, I don't have my device atm.
Sent from my HTC Sensation Z710e using XDA App
[GUIDE/TUTORIAL] Asus Transformer Prime to Android 7.1/LineageOS 14.1
[GUIDE/TUTORIAL/HOWTO] Asus Transformer Prime/TF201 stock to Android 7.1 Nougat/LineageOS 14.1
This detailed step-by-step guide helps you transform your Asus Transformer Prime with Android 4.1.1 to a powerful one with Android 7.1 (Nougat).
### I'll make a few comments like this, read these or you may miss something.
### The Asus Transformer Prime codename is TF201.
Try to prefer USB2 connections, but USB3 works fine too.
CHANGELOG
v11. Improvemed unlock section
v10. Updated links
v9. ROM v39 and removed obsolete info
v8. ROM v35 and enhenced link for OpenGapps
v7. Refresh pack for ROM v32 and TWRP recovery 3.2.3-0
v6. Google Play certification
v5. Updated djibe pack for easier install (kang recovery 3.1.0-1, SuperSU, drivers if fails at Step 6) + switched to v26 of Katkiss
v4. TWRP Kang recovery 3.1.0-1
v3. Tweaks and walkthrough
v2. Android 7, many hints added for more accurate tutorial
v1. Initial release
BEFORE STARTING
Make sure you have the latest official updates for your tab :
In Android, go to Settings -> About tablet -> System Update
### Make sure you read all comments starting by ###
To make sure your tab is the correct model, go to Settings -> About tablet.
The details below are listed :
• Android 4.1.1 (JellyBean; Nvidia logo bottom right on boot)
bootloader V 10.4.2.18
### To verify bootloader version, shut down tab. Then hold Power + Volume- for 3 seconds and release.
### You are in bootloader : on top left corner is written Android (...) epad-10.4.2.18.
### To quit bootloader, press Volume- to go over the Android icon, then Volume+ to confirm.
### If not V 10.4.2.18, check official updates for your tab before starting this tutorial
### or check more info on Asus support web page and download the version identical to the Firmware Description written top left corner of the bootloader
### Asus support is here : https://www.asus.com/Tablets/Eee_Pad_Transformer_Prime_TF201/HelpDesk_BIOS/
• GPS 7.9.13
• Wi-Fi 7.1.0.24
• BT 10.33
• Camera FT201-0x9900
• Ecran MXT-2.0 build-170
• Kernel 3.1.10.00002-9599d0cf [email protected]
o #1 SMP PREEMPT Thui Nov 22:12:01 CST 2012
• Build nr JR003C.WW_epad-10.4.2.18-20121122
Still in Settings -> About tablet, tap 7 times on build number to unlock Developer menu.
0) BACKUP YOUR DATA
Backup SMS, photos, contacts before going any further (ex: use the backupyourmobile app).
Check that backup is located on microSD card.
Then copy the backup on your PC.
1) DOWNLOAD
djibe Transformer Prime pack v2: http://bit.ly/djibeTransformerPrimev2
(contains Windows Universal Naked drivers + android_winusb if step 6 is difficult + Asus UnLock_Device_App_V6.apk + fastboot.exe + adb.exe + nvflash.exe + HairyBean Bootloader and various recoveries necessary + SuperSU 2.82).
Unzip the file on Windows desktop.
+ ROM KatKiss Nougat v39 Android 7.1
XDA Thread: https://forum.xda-developers.com/transformer-tf700/development/rom-t3457417
Download here: https://downloads.timduru.org/android/tf201/K.A.T/KatKiss/7.x/dev/ or https://www.androidfilehost.com/?fid=14943124697586357425
+ OpenGapps ARM 7.1 ARM Pico (NO OTHER DISTRIB THAT ARM PICO please): https://opengapps.org/?arch=arm&api=7.1&variant=pico
You must have a microSD card (FAT32 format), copy the zip files from Katkiss ROM, OpenGapps and SuperSU.
Then insert it in the tab.
2) INSTALL WINDOWS DRIVERS FOR ASUS TRANSFORMER PRIME TF201
- Windows 8/10 :
On keyboard, type combo : "Windows key + R"
In the command prompt, type :
Code:
shutdown -o -r -t 0
It opens Windows Recovery menu:
Go to Troubleshoot -> Advanced Options -> Startup settings -> Restart.
At reboot, hit 7 (Disable driver control) and follow instructions for Windows Vista/7.
Once driver installation is completed, reboot PC as usual.
- Windows Vista/Windows 7 :
Go to folder /Universal Naked Drivers 0.72 you unziped earlier (on Windows desktop).
Select file android_apxusb.inf, then right click -> Install.
Force driver installation and wait until a success message prompts.
Repeat operation with android_winusb.inf .
Then plug tablet to PC (USB2 port) to end driver installation.
### If it fails to install you may try using Windows device manager :
### In Windows Device Manager menu -> Right-click on Asus Android Device -> Update Driver Software -> Let me pick -> Have disk -> Browse to the .inf file and install BOTH .inf files.
### See this post if still doesn't work : https://forum.xda-developers.com/showpost.php?p=75240547&postcount=166
- For Linux, I have no experience. Every tools should be here : https://github.com/AndroidRoot/androidroot.github.io/tree/master/download
- Copy the UnLock_Device_App in tablet's internal memory
Tab should normaly be seen in Windows explorer as TF201.
Check MTP file transfer protocol is active on the tab.
Copy the UnLock_Device_App_V6.apk in the root folder of the tab.
3) UNLOCK BOOTLOADER OF ASUS TF201
Tablet must be fully charged to 100 %.
In Android, go to Settings -> Security -> Check Unknown Sources.
Then Settings -> Developer options -> Enable USB debugging.
Launch the preinstalled app File Manager to install UnLock_Device_App_V6.apk.
### If it fails to install, delete your Google Account. Go to Settings -> Accounts. Delete the Google Account.
Launch the UnlockApp.
Accept User agreements. Your warranty is now void.
Accept and click to unlock the tab,
let the tab restart and work.
After reboot , "This device is unlocked" is written on top left screen.
### It probably won't work that simple.
### The solution is here, but I didn't have to test it: https://forum.xda-developers.com/t/howto-unlock-tf700t-in-2020.4157143/post-85255809
4) PREVENT BRICK : NVFlash
This step is optionnal but highly higly highly recommended, your tab will never be bricked after it !!!
1ST PART --------------------
Tab shut down, press Power + Volume- for 3 seconds and release, you are in the bootloader.
Use Volume- to move cursor over the USB logo, confirm with Volume+, you are in the fastboot mode.
Connect Transformer Prime to PC.
Select the "Files" folder you you unziped earlier.
Do Shift + right click on folder -> Open a Command Line.
Type:
Code:
fastboot -i 0x0b05 flash recovery flatline_tf201.img
and confirm with Enter.
### If you get error "fastboot : The term 'fastboot' is not recognized as the name of a cmdlet, function, script file, or operable program",
### type the command starting with a dot :
Code:
.\fastboot -i 0x0b05 flash recovery flatline_tf201.img
A blue bar appears on the tablet indicating flash success.
Wait until command line reports the flashing success.
then type :
Code:
fastboot reboot-bootloader
and confirm with Enter.
This time in Bootloader, use Volume- to select RCK (recovery) and confirm with Volume+.
You are in the flatline recovery.
Use Volume- to go to Advances, confirm with Power.
then wheelie, confirm (Power button),
then i accept the above statement (Power button),
then Step 1: flash AndroidRoot BL, tab powers down.
Start tab with Power only,
let the blue bar fill completly and start Android normally.
Once in Android, shut it down.
Start tab in bootloader Mode again (still Power + Volume- ;-) ), go to recovery again (RCK).
Connect tab to PC.
In recovery, return to Advanced -> wheelie then select Step 2: generate wheelie blobs.
It generates the backup files !!!
Open another Windows command prompt for fastboot mode and type :
Code:
adb pull /data/media/AndroidRoot
.
Backup files are stored in your "Files" folder. Make another backup of these files in a safe place.
(7 files are saved : recovery.bct, create.bct, bootloader.ebt, blob.log, blob.bin, pt_restore.log and pt_patch.log)
### If
Code:
adb pull /data/media/AndroidRoot
doesn't work : start Android normally, connect to PC as multimedia storage and
### navigate to My Computer -> Transformer Prime TF201 -> Internal Memory -> Android Root and copy the files in here.
Shut down tab.
2ND PART, NvFlash ----------------
Copy these 7 files in the folder "files/nvflash" (Another copy, in addition to the backup you made).
Connect tab to PC.
Start tab in Nvidia APX Mode : Hold Power + Volume+ for 3 seconds.
Anything happens, it's normal, screen stays black.
The tab is visible as an external drive and is called APX.
Open another Windows command prompt on the nvflash folder.
Type :
Code:
wheelie --blob blob.bin
and confirm with Enter.
If successful : the tab launches in bootloader mode and the Command prompt writes a few lines.
Type in command :
Code:
nvflash --resume --rawdeviceread 0 2944 bricksafe.img
then :
Code:
nvflash --resume --read 14 factory-config.img
then :
Code:
nvflash --resume --read 7 unlock-token.img
You have to backup 3 new files : bricksafe.img, factory-config.img and unlock-token.img.
Copy these files in a safe storage with your blobs for future repair if needed.
### If you need to restore those backups one day, follow the tutorial of craigacgomez : https://forum.xda-developers.com/showthread.php?t=1927818
### If you have error "not enough space for GApps (error 70), follow this tutorial https://forum.xda-developers.com/showpost.php?p=73403429&postcount=137
5) RECOVERY
(Only applies to stock bootloader V 10.4.2.18).
Charge tab to 100% before continuing.
Start it in bootloader mode (Power + Volume-).
Connect it to PC.
Set the icon over the USB selection.
Confirm with Volume+; you are again in fastboot mode.
Open a command prompt on the /files folder.
Type :
Code:
fastboot devices
.
if the serial number is written, tab is well connected.
### Or check driver installation if not.
then type :
Code:
fastboot -i 0x0b05 flash recovery twrp_tf201t.blob
and wait for the "finished" success message,
then type :
Code:
fastboot -i 0x0b05 reboot-bootloader
,
and confirm with Volume+ to get into RCK (recovery, again), it is now TWRP 2.6.3.0.
6) BOOTLOADER
Once in TWRP recovery, type in command prompt :
Code:
adb devices
-> terminal returns : 012345678ABCDEF recovery.
Type :
Code:
adb push HairyBean_Bootloader_TWRP2.5.zip /sdcard
Now on the tab, still in TWRP recovery, go to Install then click on HairyBean_Bootloader_TWRP2.5.zip
(file is in Internal memory, in folder /sdcard).
Swype to the right to confirm flashing, wait until Successful message appears.
Now click Reboot System and Do Not Install when SuperSU is proposed.
Let the tab reboot with another blue bar. Let it work.
The tab reboots and launches the HairyBean TWRP recovery (androwook).
In Windows command prompt, type :
Code:
adb reboot-bootloader
,
tab reboots in bootloader mode and the USB icon is gone, it's perfect.
### If Windows doesn't recognize your tab, or recognizes it as VID_0B05&PID_4C83, try the fix from XTCrefugee included in my pack : folder \Drivers android_winusb if hairybeen TWRP not recognized
### Install this .inf driver file as you did earlier
###
### YOUR BOOTLOADER IS NOW IN 10.6.1.27.1 VERSION
###
In command prompt, type :
Code:
fastboot -i 0x0b05 flash recovery twrp-3.2.3-0_KANG-tf201t.img
Wait till blue bar completes.
When finished message appears in terminal,
type :
Code:
fastboot -i 0x0b05 reboot-bootloader
, tab reboots.
Now enter in new recovery with Volume+ : recovery is now TWRP Kang 3.2.3-0 Recovery
### Your tablet will be seen by Windows as a TF201T now !
7) SET FILESYSTEM TO F2FS
F2FS is the fastest filesystem for read and write partitions on flash memories. Compared to EXT4, gain is from 15 to 280 %.
No need to format the /System partition because it is Read only and Ext4 is still faster.
Go to Wipe -> Advanced Wipe, select only the Data partition,
then tap on Repair or Change File System -> Change File System and tap on F2FS.
Swype to force partition system as F2FS. Wait till done prompts. Then go back to Advanced Wipe.
### If TWRP sends you this log in red : E:Failed to get default contexts and file node for storage files,
### Reboot to TWRP recovery again before going any further.
Repeat the operation of F2FS conversion for the Cache partition.
8) INSTALL ANDROID NOUGAT 7.1
Still on TWRP Advanced Wipe menu,
select Dalvik Cache, System, Cache, Data AND Internal Storage and Swype to force cleanup. Wait till completion.
Back to Home screen, tap Install, then Storage: Internal Storage and change it to microSD card -> OK.
Select KatKiss* .zip, and Add More Zips,
select SuperSU.zip, and Add More Zips,
then open_gapps-arm-7.1-pico*.zip and Swype to force install. Be patient.
### Make sure once again you have the Pico Gapps version or system will hang.
### If TWRP crashes to its Home screen, you microSD might be in cause. Find another one, and then try to install Zips 1 by 1.
### If error installing Gapps, see this thread : https://forum.xda-developers.com/android/help/fix-error-70-install-gapps-t3311779
When done prompts, tap on Wipe Cache/Dalvik and swype to confirm, wait.
Go back to Home when done.
Then Reboot -> System.
Let the tab start during at least 15 minutes.
9) START ANDROID N 7.1
### During first setup, manually toggle Wifi ON using the Wifi icon on the bottom right corner. If you don't, the setup app will crash.
### It can crash a few times before turning on, keep activating it.
Configure Android as you like.
In Settings -> Mediascanner filters, uncheck Scan.
In Settings -> About, tap 7 times on build number, it unlocks the Options for developers in Settings.
Enter this new menu.
In the Hardware acceleration, try both GPU rendering active and disabled.
I can't figure which one works best. Share with us.
Good to know about this ROM:
Bluetooth requires to be turned on twice before it turns on.
A few things including the navbar buttons can be tweaked in Settings => System UI Tuner.
AND more on XDA Katkiss thread (See DOWNLOAD CHAPTER ABOVE)
10) ROOT
Open app SuperSU to see more details about the Root access.
After ROM first launch, go to Settings -> About tablet.
Tap 7 times on build number, it will unlock the Developer menu.
In the developer menu -> Try to turn ON and OFF the Force GPU option and tell me what is the faster one.
(I think I prefer when GPU forcing is disabled).
11) PERFORMANCES AND OVERCLOCK
Source of benchmarks: http://androidmodguide.blogspot.fr/p/blog-page.html
Install Kernel Adiutor app from Google Play Store.
Launch app and go to Settings -> Kernel -> CPU :
Check Apply on boot and change CPU Maximum Frequency to 1600 or 1700 Mhz, set Governor to Interactive
Now Kernel -> I/O Scheduler :
Check Apply on boot and set Scheduler to Zen, then Readahead to 1024 Ko (or 2048. Try yourself)
Now Kernel -> Various :
Check Apply on boot and set TCP congestion to Cubic (or Westwood)
12) VARIOUS FIXES
### Your tablet doesn't see the Wifi ? (that is on Channel 13 by example).
Try this first : in the Wifi screen (where you see all visible networks), tap on the three-dots icon to open the menu -> Advanced wifi parameters.
Tap on the Wifi region code item to select the region : chose the corresponding region.
Now verify your Wifi network is visible.
If not, try this :
Open Kernel adiutor, Menu -> Build.prop editor.
In key search field, type wifi.
Click ro.wifi.channels -> Edit -> in the value field, set 13. Confirm with OK.
At the same time, you can set wifi.supplicant_scan_interval=180 to 180 (seconds) to reduce number of scans and reduce battery usage.
Restart tab, your wifi network should be visible again.
### Your keyboard isn't in the correct language
Go to Android Settings menu -> Languages & inputs -> Physical keyboard -> Android keyboard
Enjoy your new tab ;-)
djibe
Thanks : @timduru, matthill.eu, Kang for updated TWRP, TWRP team, Android Root Team, Lineage OS team, TacoNikky, Saber
Thanks for the step-by-step. I've worked my way to nougat and the path there is kind of forgotten after a while. Different bootloader, different file systems, sort of lose track of things.
Sent from my XT1575 using Tapatalk
HorthLithperer said:
Thanks for the step-by-step. I've worked my way to nougat and the path there is kind of forgotten after a while. Different bootloader, different file systems, sort of lose track of things.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Thanks for your support. It was a tough job to explain step by step.
Took me 3 days to discover all the details.
thanks
really great work.
i want to add a comment : When trying to unlock bootloader, it kept on asking pw for google account (and double authentification disabled). I deleted google account from prime and it went through.
yo29570 said:
really great work.
i want to add a comment : When trying to unlock bootloader, it kept on asking pw for google account (and double authentification disabled). I deleted google account from prime and it went through.
Click to expand...
Click to collapse
Thx for feedback.
I had the same problem and used the tab factory reset.
I've updated tutorial and told to delete the Google Account.
I just wanted to thank you for making these instructions. Ive never delt with any android device with this many steps. Compared to a nexus 6p this is nuts. Ive messed around with Motorola and Samsung phones but this tablet is a whole other league. You made it very simple to turn my daughters slow old tablet into a relevant one. I still cant believe there was that much to it. Its only 10 steps...lol
Woodrow256 said:
I just wanted to thank you for making these instructions. Ive never delt with any android device with this many steps. Compared to a nexus 6p this is nuts. Ive messed around with Motorola and Samsung phones but this tablet is a whole other league. You made it very simple to turn my daughters slow old tablet into a relevant one. I still cant believe there was that much to it. Its only 10 steps...lol
Click to expand...
Click to collapse
Glad you liked it and tab is healthy again !
I've made tuts for Xperia Tablet Z and Samsung devices too if you are interested
Problem with step 8 - INSTALL Android 6 ROM
Hello djibe89,
First of all, I would like to thank you very much for this well documented step-by-step guide for upgrading the TF201! It was no problem for me, a novice in this, to follow.
However i do have encountered a problem with booting after the installation of step 8. And i hope you are able to help me with this. When i try to boot the device after Successful installing KatKiss-6.0_TF201_029.zip, open_gapps-arm-6.0-pico-20160320.zip, and Beta-superSU-v2.52.zip, the device seems to be in a boot-loop. The OS never starts up.
I also tried the older KatKiss-6.0_TF201_028.zip with the two other zip files, but the result is the same.
Until step 8, all installations went without major problems. (i made a document from your instructions and documented every step i did, (including serial number received from fastboot etc). So my TF201 is now Unlocked and the bootloader TWRP is at version 2.8.3.0.
There is only one thing i received at step 7, wich i think i should mention. When i do Wipe -> Format Data, i receive the following message when it's Done:
Updating partition details ...
... done
Full SELinux Support is present.
(in red) E: Failed to get default contexts and file node for storage files.
MTP Enabled
Formatting Data using make_extfs function
You may need to reboot recovery to be able to use /data again.
Updating partition details ...
... done
I did not pay attention to this message, because there was also the Successful message.
But perhaps it does have something to do with my problem of not being able to boot into KatKiss.
Hope you are able to help me with this.
(Maybe i will try to install Nougat for the TF201, since the recovery with TWRP is OK.)
Kind regards, Bert
deltabert said:
Hello djibe89,
First of all, I would like to thank you very much for this well documented step-by-step guide for upgrading the TF201! It was no problem for me, a novice in this, to follow.
However i do have encountered a problem with booting after the installation of step 8. And i hope you are able to help me with this. When i try to boot the device after Successful installing KatKiss-6.0_TF201_029.zip, open_gapps-arm-6.0-pico-20160320.zip, and Beta-superSU-v2.52.zip, the device seems to be in a boot-loop. The OS never starts up.
I also tried the older KatKiss-6.0_TF201_028.zip with the two other zip files, but the result is the same.
Until step 8, all installations went without major problems. (i made a document from your instructions and documented every step i did, (including serial number received from fastboot etc). So my TF201 is now Unlocked and the bootloader TWRP is at version 2.8.3.0.
There is only one thing i received at step 7, wich i think i should mention. When i do Wipe -> Format Data, i receive the following message when it's Done:
Updating partition details ...
... done
Full SELinux Support is present.
(in red) E: Failed to get default contexts and file node for storage files.
MTP Enabled
Formatting Data using make_extfs function
You may need to reboot recovery to be able to use /data again.
Updating partition details ...
... done
I did not pay attention to this message, because there was also the Successful message.
But perhaps it does have something to do with my problem of not being able to boot into KatKiss.
Hope you are able to help me with this.
(Maybe i will try to install Nougat for the TF201, since the recovery with TWRP is OK.)
Kind regards, Bert
Click to expand...
Click to collapse
Hi, I'm glad you liked it.
Seems like you chose wrong Filesystem format " Formatting Data using make_extfs function".
We need a F2FS partition.
Go back to your TWRP 2.8 recovery,
wipe all partitions,
chose /data partition and change filesystem to F2FS.
Make sure /Cache partition is F2FS too.
Then you can Install the zips.
Keep in touch.
Merry christmas from France
djibe89 said:
Hi, I'm glad you liked it.
Seems like you chose wrong Filesystem format " Formatting Data using make_extfs function".
We need a F2FS partition.
Go back to your TWRP 2.8 recovery,
wipe all partitions,
chose /data partition and change filesystem to F2FS.
Make sure /Cache partition is F2FS too.
Then you can Install the zips.
Keep in touch.
Merry christmas from France
Click to expand...
Click to collapse
Hello djibe89,
Thank you for answering my question.
But before receiving your answer I was already trying to do the steps again (from step 4), which was (looking back) obviously a bad idea. I am afraid I made a mess of it right now. First of all i should have read the error msg carefully to see the file system type. I was aware that this KatKiss is using f2fs?
I already send you a pm describing what i had done, and that i had to stop experimenting until after Christmas
Today (27 dec.) i tried an other attempt to revive my tab, and started by: 2ND PART, NvFlash---
Got the tab in APX mode again (Windows Device Manager shows Asus T. P. APX..)
So i went on with 5 - RECOVERY
I do get the fastboot screen; with the menu's RCK - Android - USB - Wipe Date, and went to USB.
Giving the command fastboot devices gives the serial number, so its connected.
Then i gave fastboot -i 0x0b05 flash recovery twrp_tf201t.blob which gave sending 'recovery' <7934 KB>...
OKAY [2.213s]
writing 'recovery'...
OKAY [ 3.534s]
finished. total time: 5.747sthen a reboot bootloader with: fastboot -i 0x0b05 reboot-bootloader
After this i had the TWEAMWIN screen again.
with adb devices i get the 012345678ABCDEF recovery message. So, adb can connect.
But re-installing HairyBean_Bootloader with adb push HairyBean_Bootloader_TWRP2.5.zip /sdcardgives an error on the tab.
Then i realized that i have just re-installed TWRP 2.6, which is intended for JB bootloader! So i booted the tab to fastboot and installed the TWRP 2.8 with:
fastboot -i 0x0b05 flash recovery twrp.blob That went OK.
Now i tried to install KatKitt6 again, now with all partitions formatted as f2fs.
But i stil don't get Katkitt6 booting. It keeps rebooting.
===============================================================
Today, 28 dec. i did an other attempt and made photo's from the screen of the tab.
From within TRWP 2.8.3.0, I started at Step 7 – SET FILESYSTEM TO F2FS
Wipe :: Format Data, uses ext4 filesystem (as described in the tutorial) and takes indeed a long time.
Next Wipe :: Advanced Wipe ONLY the data folder, and set to F2FS
Also with the Cache partition also set to F2FS
Step 8 – Install Android 6 ROM. From TWRP Wipe :: Advanced Wipe. Select Dalvik Cache, System, Cache and Internal Storage. Swipe to cleanup. NO mention of changing the filesystem to F2FS so I left these as they are!
Installation of the tree .ZIP files, see pictures below:
Unfortunately, i am only able to put links to photo's when i have at least posted 10 posts. Since i am new here i try an other way of linking to the photos:
Step 7 and 8 - Photo 1 https: // deltabert.stackstorage.com/s/gszDWyVd9sqHiQs
Step 7 and 8 - photo 2 https: // deltabert.stackstorage.com/s/Ju0tmwMIUjJXHg4
Step 7 and 8 - photo 3 https: // deltabert.stackstorage.com/s/o0tTQ3tPBHF85Wu
Step 7 and 8 - photo 4 https: // deltabert.stackstorage.com/s/Cls41PHHcCa0TKr
And when I press Reboot, after Wiping Dalvik Cache, the tab keeps rebooting! This time I see no error messages.
And believe me, I left it booting for hours…
Any idea as what I could do next?
deltabert said:
Hello djibe89,
Thank you for answering my question.
But before receiving your answer I was already trying to do the steps again (from step 4), which was (looking back) obviously a bad idea. I am afraid I made a mess of it right now. First of all i should have read the error msg carefully to see the file system type. I was aware that this KatKiss is using f2fs?
I already send you a pm describing what i had done, and that i had to stop experimenting until after Christmas
Today i tried an other attempt to revive my tab, and started by: 2ND PART, NvFlash---
But unfortunately i am not able to get the tab in APX mode again.
Then i skipped this en went on with 5 - RECOVERY
I do get the fastboot screen; with the menu's RCK - Android - USB - Wipe Date, and went to USB.
Giving the command fastboot devices gives the serial number, so its connected.
Then i gave fastboot -i 0x0b05 flash recovery twrp_tf201t.blob which gave sending 'recovery' <7934 KB>...
OKAY [2.213s]
writing 'recovery'...
OKAY [ 3.534s]
finished. total time: 5.747sthen a reboot bootloader with: fastboot -i 0x0b05 reboot-bootloader
After this i had the TWEAMWIN screen again.
with adb devices i get the 012345678ABCDEF recovery message. So, adb can connect.
But re-installing HairyBean_Bootloader with adb push HairyBean_Bootloader_TWRP2.5.zip /sdcardgives an error on the tab.
Then i realized that i have just re-installed TWRP 2.6, which is intended for JB bootloader! So i booted the tab to fastboot and installed the TWRP 2.8 with:
fastboot -i 0x0b05 flash recovery twrp.blob That went OK.
Now i tried to install KatKitt6 again, now with all partitions formatted as f2fs.
But i stil don't get Katkitt6 booting. It keeps rebooting.
Besides this, I am still worried that NvFlash might be no longer on the tab...
And i don't get the FlatLine booting with volume-up and power anymore...
===============================================================
Today, 28 dec. i did an other attempt and made photo's from the screen of the tab.
From within TRWP 2.8.3.0, I started at Step 7 – SET FILESYSTEM TO F2FS
Wipe :: Format Data, uses ext4 filesystem (as described in the tutorial) and takes indeed a long time.
Next Wipe :: Advanced Wipe ONLY the data folder, and set to F2FS
Also with the Cache partition also set to F2FS
Step 8 – Install Android 6 ROM. From TWRP Wipe :: Advanced Wipe. Select Dalvik Cache, System, Cache and Internal Storage. Swipe to cleanup. NO mention of changing the filesystem to F2FS so I left these as they are!
Installation of the tree .ZIP files, see pictures below:
Unfortunately, i am only able to put links to photo's when i have at least posted 10 posts. Since i am new here i try an other way of linking to the photos:
Step 7 and 8 - Photo 1 https: // deltabert.stackstorage.com/s/gszDWyVd9sqHiQs
Step 7 and 8 - photo 2 https: // deltabert.stackstorage.com/s/Ju0tmwMIUjJXHg4
Step 7 and 8 - photo 3 https: // deltabert.stackstorage.com/s/o0tTQ3tPBHF85Wu
Step 7 and 8 - photo 4 https: // deltabert.stackstorage.com/s/Cls41PHHcCa0TKr
And when I press Reboot, after Wiping Dalvik Cache, the tab keeps rebooting! This time I see no error messages.
And believe me, I left it booting for hours…
Any idea as what I could do next?
Click to expand...
Click to collapse
did you ever get through this part?
im on the same boat.....finished everything successfully but once i install the ROM it keeps rebooting and stays on the TWRP until i reboot again
ALDO_MAC12 said:
did you ever get through this part?
im on the same boat.....finished everything successfully but once i install the ROM it keeps rebooting and stays on the TWRP until i reboot again
Click to expand...
Click to collapse
Hi ALDO-MAC12,
Unfortunately, i have not yet got my TF201 working. I'l wait now until djibe89 has time to react.
(When i opened his zip file i noticed he has also a France language description, and he is at the moment in France, So i guess he is a French-Canadian, on vacation in France.)
I did study the original posts from timduru and TacoNikky, but i can find no differences with the description of djibe89. Noticed there is also a Android 7 rom from timduru. But i think i should first get to manage the hole process.
For me all this is new. My tab became so horribly slow that i only sparsely used it anymore. So that's why i would like to give it a try.
BTW, i do get the tab in APX mode; with volume up and power, i get a black screen but in Windows Device Manager there shows up the Asus Transformer Prime APX ... driver.
If you're running Windows 10, you need to delete all your other android drivers, then disable the signature checking on your driver installation and install the Naked Universal driver.
Super SU wants update
Works for me on windows 10. Make sure tablet is plugged in directly and not into keyboard also. Although Super SU is now reporting an update in necessary. Is it recommended in update Super SU after installation? Btw thanks for bringing new life to my tablet!
Have you tried not to change /cache partition to f2s2. The original KatshMallow thread says:
This ROM is for TF201 and F2FS only
Convert just /data partition to F2FS
Click to expand...
Click to collapse
...
Hello all,
Thank you for thinking with me, I appreciate this very much! I will react to the suggestions given.
@lazuhrus, I think the Universal Naked Drivers 0.72 are correctly installed on my Win-10 PC. I followed the procedure for Win-10 to disable driver control. To confirm this: I am able to use fastboot from Win-10; fastboot devices gives me the serial number of the tf201.
Also the command adb devices gives me: 012345678ABCDEF recovery.
Further, when I bring the tf201 (with volume UP and power) in APX mode, I get a dark screen on the tab, but in Windows Device Manager there shows up the Android device: Asus Transformer Prime APX Interface.
So for me this seems OK. This lets me conclude that the Universal Naked Drivers 0.72 are correctly installed and working. Or am I overlooking something here?
Btw, I do this on the bare tablet, without the keyboard dock.
With volume DOWN and power, I get the tab in TWRP version 2.8.3.0.
And installing KatKiss seems to go well (see the screenshots I posted in #10 from the TWRP format and install process).
@ shaDNfro, I did change the /cache partition to f2fs, as the screenshots are showing too.
However, there is one strange thing. After the last install (post #10) when I am in TWRP and connect the tab to my PC (win10) I see in the File Explorer an entry for an ASUS Transformer Pad TF300T; while mine is an TF201!!
Picture File Explorer: https: // deltabert.stackstorage.com/s/Nj1C01jTyZ5MoWB
And in the Device Manager I see also references to the wrong tab type!
(But you can see the Asus Android Composite ADB Interface.
Picture Win10 Device Manager: https: // deltabert.stackstorage.com/s/zK2LIoAthr4jKJ7
(added spaces around // because i am as novice not (yet) able to post links)
Hopefully anyone can help me with this...
Hi guys,
I am French from France indeed
- Maybe try to reformat the /cache partition in EXT4 (instead of F2FS).
Then wipe all partitions and install all zips again.
- It is normal that your tab is seen as TF300 as the TWRP 2.8.3.0 is originaly openrecovery-twrp-2.8.3.0-tf300t.blob.
I no longer have my tab so it's tricky to help you. I'll try anyway
djibe89 said:
Hi guys,
I am French from France indeed
- Maybe try to reformat the /cache partition in EXT4 (instead of F2FS).
Then wipe all partitions and install all zips again.
- It is normal that your tab is seen as TF300 as the TWRP 2.8.3.0 is originaly openrecovery-twrp-2.8.3.0-tf300t.blob.
I no longer have my tab so it's tricky to help you. I'll try anyway
Click to expand...
Click to collapse
Thank you djibe89,
I really hope you can help me with this, I become a little desperate...
I wonder if there is something wrong with the bootloader (HairyBean_Bootloader_TWRP2.5.zip). When I boot the tab with vol-down and power I get the following bootloader info: Android cardhu-user bootloader <1.00 e> released by “WW_epad-10.4.2.15-20120917†A03
Do you know if this is correct?
OK, I put the tab in TWRP 2.8.3.0 mode.
Formatted the /Cache partition using make_ext4fs
Then I wiped Dalvik Cache, followed by /System, which formats to ext4fs.
Then format /Data, first with make_ext4fs, and when finished, I change the filesystem of /Data to f2fs. Wiped all other partitions, except Micro SDcard (not sure if this is the internal or external SDcard)
Then I installed the three .zip files. KatKiss-6.0_TF201_029.zip, open_gapps-arm-6.0-pico-20160320.zip and BETA-SuperSU-v2.52.zip.
I also put the MD5 checksum file of KatKiss-6.0_TF201_029.zip on the sdcard and the install procedure checks the .zip successful.
When install is done: Successful, I wiped Dalvik Cache and rebooted the tab.
But then I have the same reboot problem: First i see a blue bar for one second, then the tab boots with the ASUS splash screen at medium intensity, then switches for a moment to high intensity and back to medium intensity, and after a few seconds it reboots and it starts over again.
When I leave the tab booting for two hours, I can feel it is doing something; the backside is becoming slightly warm; processor: ~ 45°C.
The bootloader is part of HairyBeen isn't it? Could I re-install the correct HairyBean_Bootloader_TWRP2.5.zip again, by putting it on the external sdcard and selecting it from TWRP 2.8.3.0?
fastboot, adb and Nvidia APX Mode are still functioning, so there must be a solution...
Hopefully you have a good suggestion?
Kind regards, Bert
Yo Bert,
you must be in distress.
Maybe it's time to look for a NVIDIA APX restoration.
I hope you still have your backup files.
I don't know anything about it,
so read all Google carefully to proceed.
That's why I motivated you to backup APX in my tutorial, since we never what can happen with Android hardware.
Keep in touch
djibe89 said:
Yo Bert,
you must be in distress.
Maybe it's time to look for a NVIDIA APX restoration.
I hope you still have your backup files.
I don't know anything about it,
so read all Google carefully to proceed.
That's why I motivated you to backup APX in my tutorial, since we never what can happen with Android hardware.
Keep in touch
Click to expand...
Click to collapse
Hi djibe89,
I will look into the restoration option. I do have the APX backup files.
Will be continued....
How I can install twrp and flash gsi rom on Doogee N20?
I found this but I'm doesnt know Russian: pda.ru/forum/index.php?showtopic=955032&st=1220#entry89836105 (I cant post URL because I'm new user, so I delete the "4" from "4pda")
Sorry for my bad English.
צבי זלצברג said:
How I can install twrp and flash gsi rom on Doogee N20?
I found this but I'm doesnt know Russian: pda.ru/forum/index.php?showtopic=955032&st=1220#entry89836105 (I cant post URL because I'm new user, so I delete the "4" from "4pda")
Click to expand...
Click to collapse
That's the Google translation:
A little instruction on how to get RooT. And so, everything that you do, as always, is at your own peril and risk! All data is erased when unlocked! Make BACKUP !!! Is always!!!! I. Unlocking Boorloder-a (required for flashing the phone and everything connected with it): 1. Go to settings -> system -> About phone -> Build number (7 clicks) (Congratulations !!!! You are a developer!) < - About phone -> For developers: Enable USB debugging and OEM unlocking. 2. We connect the phone to the computer and install the ADB usb driver (on the Internet), a connection request should appear on the phone, you need to allow it. 3. Extract files from the N20_utils.rar archive (10.87 MB) (preferably not very far, the root of the disk or the created folder N20 will be there). Go to the Unlocked Bootloader folder and run the bat file, the phone will reboot and display the request "unlock? Yes / no" rocker up - yes / rocker down - no. Naturally, you need to press the volume up, otherwise there were so many actions)) 4. Congratulations! Now, with each reboot, you will have an Orange state (5-second inscription), and the ability to do whatever you want with your phone. II. We sew! 1. For the lazy (who value their time). Download the SP Flash tool (Internet), from the N20_utils.rar archive (10.87 MB) select MT6763_Android_scatter and boot_magisk_20 files for the boot partition, lk_pached for lk, etc. you can even twrp instead of native recovery. Turn off the phone, connect it to the computer and click Download in the SP Flash programs. After the OK circle appears, disconnect and reconnect the cable (easier than a forced reboot). We turn on the phone and put the magisk manager (internet). Congratulations!!! You have a root and no Orange State label! 2. Who wants more and himself: phone to computer -> go to the Unlocked Bootloader folder -> run CMD -> write "fastboot flash recovery" put a space and move the TWRP file with the mouse to the window (fast path to the file) and press ENTER -> reboot the phone to fastboot. Congratulations!!! you have TWRP. Boot into TWRP, skip the encrypted DATE message, go to formatting and format the DATE. Go to mount and connect MTP. A phone will appear on my computer, we drop the files DisableForceEncryption_Treble (disable date encryption), orange_state_disabler_v0.3 (remove orange_state) and magisk.zip (internet) into the memory section. In TWRP, click install all this and rejoice! 3. Who has nothing to do at all: go to the forum thread Development and porting of GSI firmware (Post bullik01 # 71222655) and try what catches your eye. Not all are loaded, but .... (although we do not seem to have an A / B structure, but only "arm64 A / B" were launched) PS: look for additional information here on the forum and for brotherly devices UMiDIGI A5 Pro - Firmware ( Post Xakep1993 # 86772223) Attached files recovery-TWRP_3.3-20191015-1714.img (22.81 MB) DisableForceEncryption_Treble.zip (4.24 MB)
jwoegerbauer said:
That's the Google translation:
A little instruction on how to get RooT. And so, everything that you do, as always, is at your own peril and risk! All data is erased when unlocked! Make BACKUP !!! Is always!!!! I. Unlocking Boorloder-a (required for flashing the phone and everything connected with it): 1. Go to settings -> system -> About phone -> Build number (7 clicks) (Congratulations !!!! You are a developer!) < - About phone -> For developers: Enable USB debugging and OEM unlocking. 2. We connect the phone to the computer and install the ADB usb driver (on the Internet), a connection request should appear on the phone, you need to allow it. 3. Extract files from the N20_utils.rar archive (10.87 MB) (preferably not very far, the root of the disk or the created folder N20 will be there). Go to the Unlocked Bootloader folder and run the bat file, the phone will reboot and display the request "unlock? Yes / no" rocker up - yes / rocker down - no. Naturally, you need to press the volume up, otherwise there were so many actions)) 4. Congratulations! Now, with each reboot, you will have an Orange state (5-second inscription), and the ability to do whatever you want with your phone. II. We sew! 1. For the lazy (who value their time). Download the SP Flash tool (Internet), from the N20_utils.rar archive (10.87 MB) select MT6763_Android_scatter and boot_magisk_20 files for the boot partition, lk_pached for lk, etc. you can even twrp instead of native recovery. Turn off the phone, connect it to the computer and click Download in the SP Flash programs. After the OK circle appears, disconnect and reconnect the cable (easier than a forced reboot). We turn on the phone and put the magisk manager (internet). Congratulations!!! You have a root and no Orange State label! 2. Who wants more and himself: phone to computer -> go to the Unlocked Bootloader folder -> run CMD -> write "fastboot flash recovery" put a space and move the TWRP file with the mouse to the window (fast path to the file) and press ENTER -> reboot the phone to fastboot. Congratulations!!! you have TWRP. Boot into TWRP, skip the encrypted DATE message, go to formatting and format the DATE. Go to mount and connect MTP. A phone will appear on my computer, we drop the files DisableForceEncryption_Treble (disable date encryption), orange_state_disabler_v0.3 (remove orange_state) and magisk.zip (internet) into the memory section. In TWRP, click install all this and rejoice! 3. Who has nothing to do at all: go to the forum thread Development and porting of GSI firmware (Post bullik01 # 71222655) and try what catches your eye. Not all are loaded, but .... (although we do not seem to have an A / B structure, but only "arm64 A / B" were launched) PS: look for additional information here on the forum and for brotherly devices UMiDIGI A5 Pro - Firmware ( Post Xakep1993 # 86772223) Attached files recovery-TWRP_3.3-20191015-1714.img (22.81 MB) DisableForceEncryption_Treble.zip (4.24 MB)
Click to expand...
Click to collapse
Hi, were you by any chance able to get a copy of these files ,Please upload if posssible
The original links are broken and the internet seemed to wipe all traces out, I'm looking for the N20_utils and possibly the Disable force encryption one
Good day
Had the same problem, (English not so good but I know you'll understand). What I did was just installing Corvus OS rom, the 11th version. It's been quite a while since i installed it.
Tried Lineage 18.1 and adding the smallest gapps available, but everytime i get code error 1. I guess it was the twrp 3.3 version i used cause some roms requer the latest TWRP versions. The lineage is installing just right nd can reboot to system with no hiccups.
None of Android 12 gsi versions has ever been able to installed. Cause when i try to install, i get the error of "file too large for the target partition. Tried everything from the net to increase the system partition to at-least 3gig. No success.....
Is anyone who can help to install android 12 even beta version will be ok for my N20 Doogee??
Thanx
flairepathos.info said:
Hi, were you by any chance able to get a copy of these files ,Please upload if posssible
The original links are broken and the internet seemed to wipe all traces out, I'm looking for the N20_utils and possibly the Disable force encryption one
Click to expand...
Click to collapse
The file is in the forum. But to make your life easier here are the link.
https://drive.google.com/drive/folders/18B-srDVia_H4aDt7uvCDUxg2e4R5kVVY?usp=sharing The file is of type .exe and that extracts when you run on the pc, the problem is that I was suspicious about the virus so I threw the file in the total virus (if you don't know what it is, just search) and 6 programs pointed it out as malware but many others didn't find anything including karpersky and bit defender, there to make sure the files were there i renown they from .exe to .zip and I looked and the files really were there but as I don't want to take the risk I didn't extract and I didn't even try anything. The file that fix the encryption are inside doogee n20.exe, the guy said it will be in .exe and when you run it extracts the file in the C folder of the computer I recommend you to rename it from .exe to .zip because if the file have a virus you can screw your pc when running
Da-Judges said:
Good day
Had the same problem, (English not so good but I know you'll understand). What I did was just installing Corvus OS rom, the 11th version. It's been quite a while since i installed it.
Tried Lineage 18.1 and adding the smallest gapps available, but everytime i get code error 1. I guess it was the twrp 3.3 version i used cause some roms requer the latest TWRP versions. The lineage is installing just right nd can reboot to system with no hiccups.
None of Android 12 gsi versions has ever been able to installed. Cause when i try to install, i get the error of "file too large for the target partition. Tried everything from the net to increase the system partition to at-least 3gig. No success.....
Is anyone who can help to install android 12 even beta version will be ok for my N20 Doogee??
Thanx
Click to expand...
Click to collapse
you can use the pixel experience lite https://github.com/ponces/treble_build_pe/releases ( remenber the lite version, because is 2,5 gig) i try and instal in my phone and worked but i cant access my storage so i search and here are the solution https://forum.xda-developers.com/t/...loop-after-any-custom-rom-doogee-n20.4357313/ i dont try it but if you want here are the solution
flairepathos.info said:
Hi, were you by any chance able to get a copy of these files ,Please upload if posssible
The original links are broken and the internet seemed to wipe all traces out, I'm looking for the N20_utils and possibly the Disable force encryption one
Click to expand...
Click to collapse
Hi, did you find N20_utils?