Hima_DOC_Tool_1.0.exe will:
- reformat your Disk-On-Chip.
This change IS reversible with:
Hima_DOC_Restore_1.0.exe
This operation is SAFE. It will not destroy your device.
You will get:
- Storage partition 31MB
The main purpose of this tool was to get more storage space under WM2005,
but it can also be used on WM2003/SE.
HOW TO RUN IT
-------------------------------------------------------------------------
(it can be run on WM2003 or WM2005 as well)
1. Install ExtendedROM Unlocker.
2. UNHIDE and UNLOCK your ExtendedROM.
3. Run the Hima_DOC_Tool_1.0.exe on your device.
4. Hardreset your device
HOW TO RESTORE ORIGINAL DOC chip SIZE
-------------------------------------------------------------------------
1. Install ExtendedROM Unlocker.
2. UNHIDE and UNLOCK your ExtendedROM.
3. Run the Hima_DOC_Restore_1.0.exe on your device.
4. Hardreset your device
HOW TO HARD RESET
--------------------------------------------------------------------------
Press reset hole and keep holding camera + record button until menu "Boot Options" appears on the screen.
Then release cam + rec and use them for moving across the menu and to change the values.
To hardreset tou have to select:
Enable KITL = NO
Clean Reg Hive = YES
Format Storage = YES
THAT's IT FOR NOW
buzz net
---------------- WARNING ----------------
I would not believe responsible for any damage that could bring your phone with this solution!
I post a solution for this problem:
INSTRUCTION :
1. miniSD - formated in PC - FAT format (now FAT32 !)
2. Wizard On and Bootloader (press reset and keep photo button let go reset) 3 color display. Put in card to Wizard.
3. Connect USB - PCC to PC
4. Launch MTTY 1.42 with USB connection
5. Write command - r2sd os end press enter
6. Program it will record OS on miniSD
7. After recording make Hard Reset or turn on Bootloader
8. On Display should be written - Format partition ?? (5 sec.) - to confirm press Voice dial button. If inscription it will disappear repeat point 7.
9. If Format partition successful wait OS is write. Done.
10. Draw out miniSD
11. Make Hard Reset
12. Enter in bootloader
13. FOR NON CID WIZARD - Flashing Wizard RUU (must be proper version) - ERROR 300 is bad RUU ERROR 266 turn off Wizard and turn on connect to PC
14. With CID (for example CID G4) seek forum for flashing Wizard with CID G4
Here's MTTY 1.42
View attachment mtty1.42.zip
Hello guys!
I want to have a liitle databases of helpful tips taht can be used for the AiKi.
Please add yours by repy, i'll edit this post
Boot in recovery
- Shut down the phone
- Press Power + Volume up
- Here you go!
(You can also do Power => reboot => Recovery ^^)
Unbrick The AiKi
Note : you will lose your data... the phone can't boot
What do you need:
THE WORKING RECOVERY
A Microsd 512 MB card at least
Howto :
Download the lastet version of AiKi Rom and put it at the root o the microsd card
Start in recovery
Go to Flash an update => Find the zip => [Select the aiki update]
Select your language, and go to AVANCED MODE
select your setting, but check WIPE SYSTEM
It will format the /system partition, useful if the phone can't boot
wait for restart, and enjoy!
Since i am afraid, that my Guide will dissapear in the other Thread,
i post this guide in a new Thread !
I have just uploaded a collection of, how i have named it, - s60 essentials - there are ALL files included to flash stock, update to .033, flash twrp recovery and root.
(this is for Win7 x86, you have to check if it works for other versions yourself, sy..)
Here is my collection
HOW TO.... Stock, Update, custom recovery and root your s60 !!!!
Disclaimer: if you brick your phone, it's your fault, i have tested this way of rooting my s60 now for a several times and it works 100%
SO READ TWICE, CHECK TWICE, BEFORE YOU CLICK ONCE !!!!! i will not take any responsibility !!!
Thanks to everybody who contributed here in this thread (Cesarq, OpenMinded, Tuschi, BetonJohn, etc.......) the software in the link
is the collected data, freely available in the net and linked in the original Thread several times, i have only bundled one package and wrote
this, hopefully usefull guide.
in principle do as follows: (I will only explain once how to sideload or load via recovery, afterwards i will only state what kind and what file)
Prerequists
- install USB drivers (for recovery and adb)
- install "minimal ADB and fastboot"
- copy the two updates (update032 & update033) into the folder, where you have installed "minimal ADB and fastboot" (makes live easier later)
- install QPST (the version of QPST is the one from Androidmtk and should be virusfree
(The version of QFIL in my collection is the one without reboot, so you have to reset/reboot your phone manually (resetbutton below hatchdoor on your phone) whenever
stated in this guide.
- format micro SD card in fat32 ! and copy SuperSU.zip onto it.
- connect a WORKING USB cable to your phone (Not to your PC atm !!!)
getting twrp (for saving your old firmware only)
- power off phone.
- start minimal adb on your PC
- start QFIL (part of QPST) on your PC
- press VOL+ & VOL- simultanousely and connect phone with PC (it will vibrate once, top right LED starts blinking red, screen stays black) - DOWNLOAD MODE -
(just in case: to leave Download mode, press and hold power button for apprx. 15 seconds)
- as soon as you connect your phone to the PC, QFIL should show the Phone/port in the topline allready, if not, either try to manually select the port, or you probably still have
a problem with the USB drivers !
- tick in QFIL Flat Build (top left)
- QFIL - select Programmer, "browse" to the saved location of "update-twrp-recovery-nobootpatch" and select the "prog_emmc.blablabla...mbn" file and doubleclick
- QFIL - "load XML" ,select rawprogramm, doubleclick, select patch0, doubleclick
- QFIL - click on "download"
- if everything was OK up till now, it should start download - BE PATIENT- and read the status window on QFIL, when it shows "finish download"....
- disconnect phone from PC
- press and hold simultanousely POWER and VOL+ and use a small tool to push the reset button on the phone under the hatch, while still pressing Power and Vol+ !
- the phone should now be in twrp recovery. If so, do a full backup now to your (allready inserted and fat32 formatted) microSD card!!!
when done
- Power off your phone !
flashing stock 31.02
- enter download mode again (Vol+ & Vol-, connect phone to PC.......)
- this time in QFIL, browse in programmer path to "s60_stockFW_31.02" and select the programmer from there
- load XML's (the onces that belong to Stock31.02)
- start download... this will take a while !!!! BE PATIENT !!!!
- when QFIL status window shows finish download, push the reset button on the phone and let it reboot.
- it is normal, that the phone should restart itself 2, maximum 3 times at the first start, but sometimes it ends up in a bootloop (Cat Logo, reboot, CAT logo, reboot, etc, etc, .......)
(The bootloop mainly happens, if you clear, in twrp recovery, the whole OS, but that's no issue either...)
- if it ends up in a bootloop, no worries, just continue ! Believe me, i did the process now several times ! )
you are back on stock 31.02 !
-Power off your phone again
Updating to 032
- bring up minimal ADB sideload on your PC (start it, if not allready done in previous step (getting twrp)).
- press and hold POWER and VOL+ button on your phone - RECOVERY MODE -
- when in stock recovery select (with Volume keys) "adb sideload" and click the Powerbutton
- connect your phone to the PC
- on PC, type into the black ADB Terminal window "adb sideload update032.zip" and hit enter
- if drivers are there, phone will start downloading the update now.
- when complete, select clear cache, and clear data then reboot your phone.
- again, same as in the step (flashing stock), if bootloop, no worries, just continue, if it boots up, let it boot up and then..
you're on 032 now
- Power off the phone again
Updating to 033
- do the same steps as described under "Updating to 032" only difference, type in adb window " adb sideload update033.zip"
After updating to 033 your phone should boot up normally now, NO MORE BOOTLOOP !
getting twrp
- this is the same step as above "getting twrp" only difference, this time, no backup needed and...
- when in twrp-recovery, select "install" browse to your micro SD-card, and...
- install SuperSU.zip from SDcard.
- once more, clear cache and data and reboot.
The phone should boot up now, you should be on FW 033, with custom recovery and root !!!
That's all !!!
Would a TWRP or fastboot flashable stock recovery let us apply future OTA updates without wiping and starting from stock 031 if we're using systemless root like Magisk?
From stock recovery you can reboot to bootloader which puts us in fastboot (you can select boot mode with Vol +/-), so I'm thinking if we could boot TWRP from fastboot (without flashing, obviously), we could back up the stock recovery. Then when the next update comes around, we flash stock recovery back, apply the update, then reflash TWRP.
I tried fastboot boot recovery.img from update-twrp-recovery-nobootpatch but I got
FAILED (remote: unknown command)
and rebooting into recovery from there just got me stock recovery which makes sense.
QCN please
Hi guys, can anyone share me QCN backup of S60 because i've lost it! Thanks.
Last update for Android 6.0 was from 766 days ago.
Any suggestions on how to patch?
Thanks a million
Hi,
New to XDA, amazing place!
Did a search and nothing posted has helped except perhaps attempting maskrom, but I don't want to void my warranty in case I have to argue with Xtrons via aliexpress (want to leave the case uncracked).
Hope someone can give advice on something further to try to fix my issue as Xtrons won't do an RMA since they feel the bootloop is because I didn't allow updates to complete (which is not the case).
Trying to keep it brief:
my hu: Xtrons TE103AP (px5) CPU: 8 core 64-bit CPU Cortex-A53 @ 1.5G
Andy vers: 8.0.0 Oreo
Kernel vers: 4.4.93+, [email protected] #343, sat sep 15 2018
MTCE_GS_v2.94.3, sep 13 2018
Mem: 3891MB
The scoop:
Last week during a very cold day (windchill -31C) (probably not a factor) the unit locked up while Waze and PowerAmp where running. I was driving (so left it be) and after awhile it rebooted itself to a (recovery) screen with two choices:
1) Factory Reset
2) Reboot
Chose 2) reboot. Screen blanked, that was all she wrote.
Got home (1.5 hours later), took out hu to trouble shoot and possibly reflash system rom inside house (if required).
Test boot (using bench PS (computer PS 12+V and GND rails)): System shows Oreo car multi-media logo for 6 seconds and then Toyota boot animation then blank for 6 seconds and then Oreo car multimedia logo (for 6 sec) again, then blank for 6s then Oreo logo again for 6 sec... (Oreo bootloop). Link: removed Dropbox url - becasue: I'm too new
Contacted Xtrons (via aliexpress) they were quick to offer a link to ROM (sep 20, 2018 vers) Link: removed Dropbox url
and a poorly written, incomplete instruction sheet. Link: removed Dropbox url
Procedure attempted and results:
Used reset toggle to enter stock recovery on a TE103AP:
step 1- use paperclip hold in rst abt 20s (@ 15s panel lights will flash on an off), released for 1s, then
step 2- hold in rst for 3s, release for 1s, then
step 3- click RST (release immediately)
Get E: mount errors for ntfs? Just below the recovery Menu. (I'm assuming it's because I used 128GB tf in GPS and SD slots when hu was working (tfs formatted by Chrome OS, so why ntfs???) and now they are not there. Assuming this doesn't affect problem???)
E: trying mount /dev/block/mmcblk0p1 to ntfs.
E: tring mount /dev/block/mmcblk0 ntfs.
E: failed to mount /mnt/external_sd error: No such device
E: trying mount /dev/block/mmcblk0p1 to ntfs.
E: tring mount /dev/block/mmcblk0 ntfs.
E: failed to mount /mnt/external_sd error: No such device
(verbatim)
Used RESET (rst) to move selection to wipe cache and select (successful) and then factory reset (successful), then inserted TF (16GB FAT32) card with unzipped files) into GPS slot (SD slot (2nd TF slot) left empty).
Moved selection to Update system ROM, select (after 290.7s update successful) returned back to stock recovery menu.
Moved selection to Update MCU, selected. Checks for ROM (OK), flashes MCU (Front panel lights flash on and off). Successful.
System reboots itself: Screen flashes with Oreo logo (car multimedia system) for a few seconds and then blanks for 6 seconds and then Oreo logo reappears ad infinitum.
Link: removed Dropbox url
I have allowed the bootloop to run for 12 hours with no change.
I have also hard powered down (PS off) for 5-10 minutes and powered-on and get:
Oreo logo briefly, the Toyota Boot animation, starting android and a reboot to the 6s Oreo boot loop again or (sometimes) the homescreen (how I was able to get pictures of settings and attempt updates through settings). However, the hu will randomly start the 6s Oreo bootloop again.
Additionally, attempted update procedures:
2) stock recovery: factory reset, wipe cache, update system. select reboot in recovery. Result - same
3) stock recovery: wipe cache, factory reset, select reboot. Result - same
4) stock recovery: factory reset, wipe cache, update MCU (only). Auto-reboot (I release GPS card after it says successful). Result - same
5) From settings: Update system rom, (insert TF) select wipe option. (Successful). Select Update MCU (Successful). HU reboots automatic. Results - same
6) From settings: selcting update system rom OR MCU (successsful), rebooting. Results - same
7) From homescreen, insert TF card, Popup Update system ROM, select wipe option. Successful. Result - same.
Am I doing something wrong (as Xtrons assumes)?
What do I tell Xtrons it is so I can get an RMA and ultimately a working system?
Any help would be greatly appreciated!
Robert