Related
When I got my G tablet yesterday and rooted/flashed to 2.2 Lite, I did it using my G1's SD, but since then I backed up my SD to what I had it on my G1. My question is, can the G tablet naturally boot from an SD card(micro) as long as its named update.zip? I mean so I can do the flash again or is it perma bricked? If it is perma bricked, should I return it to store and start all over with a dedicated SD card?
Thanks!
necromonger89 said:
When I got my G tablet yesterday and rooted/flashed to 2.2 Lite, I did it using my G1's SD, but since then I backed up my SD to what I had it on my G1. My question is, can the G tablet naturally boot from an SD card(micro) as long as its named update.zip? I mean so I can do the flash again or is it perma bricked? If it is perma bricked, should I return it to store and start all over with a dedicated SD card?
Thanks!
Click to expand...
Click to collapse
Necro,
This tablet is 99% unbrickable (I would say 100% because I haven't head of one bricked yet but nothing is impossible). you just need to boot into APX mode and reflash stock firmware
how to get into APX mode can be found here
http://wiki.tegratab.com/index.php/Nvflash_FAQ
you are going to need to download the complete NVflash restore file
which can be found here: http://forum.tegratab.com/viewtopic.php?f=13&t=18
dsf767 said:
Necro,
This tablet is 99% unbrickable (I would say 100% because I haven't head of one bricked yet but nothing is impossible). you just need to boot into APX mode and reflash stock firmware
how to get into APX mode can be found here
http://wiki.tegratab.com/index.php/Nvflash_FAQ
you are going to need to download the complete NVflash restore file
which can be found here: http://forum.tegratab.com/viewtopic.php?f=13&t=18
Click to expand...
Click to collapse
The download link for the SDK is broken or old. Is there another place I can download it. Stupid google keeps bringing me the PDFs for Nvidia. Nevermind about the SDK, found it on their site. What about the original ROM/IMG? That link is also broken.
Is there a better guide. I'm getting a headache from all the files the SDK dumped onto my computer. Can someone show me a noob proof version of how to do this?
I only undertand the APX mode on the G Tablet. Other than that I cannot get windows to recognize the device even after installing the SDK. Where are the drivers for the APX?
There are instructions on the main post for TNT-Lite for what to do if you get into the boot loop. I ended up having to get to the step where I repartitioned the internal flash and re imaged.
You can avoid the SDK and driver issues and only use the computer to put some files on the SD card:
Easiest way to fix for me was (I had same issue problem with 2.0):
1. Download "Clockwork .8" (links at XDA)
2. Unzip the recovery file and update.zip to root of a micro sd
3. Change the recovery folder's command file to "microsd2" & save it
4. Put the card in the Gtablet
6. Interrupt the boot loop by pressing power and volume up at same time
7. Clockwork should install
8. Power down and restart the G tablet
9. Download TnT Lite 2.20
10. Repeat 2 and 3, but this time extract the update.zip file from TnT 2.20 and copy over the update.zip already in the root directory. YOU WILL NOT NEED A RECOVERY FILE FOR THIS METHOD.
11. Delete the recovery file in the root directory
12. Power down
13. Restart by pressing power and volume up
14. Should be in Clockwork
15. You want to clear both cache and data (two options on main screen)
16. After clearing both, choose install update.zip.
17. The next screen will show the update.zip. Go to its row and choose it by pressing home button
You should auto reboot and be set. You can then install the Folio Flash apk and install Titanium so you can do the market fix.
This is process is what saved me, at least.
rushless said:
You can avoid the SDK and driver issues and only use the computer to put some files on the SD card:
Easiest way to fix for me was (I had same issue problem with 2.0):
1. Download "Clockwork .8" (links at XDA)
2. Unzip the recovery file and update.zip to root of a micro sd
3. Change the recovery folder's command file to "microsd2" & save it
4. Put the card in the Gtablet
6. Interrupt the boot loop by pressing power and volume up at same time
7. Clockwork should install
8. Power down and restart the G tablet
9. Download TnT Lite 2.20
10. Repeat 2 and 3, but this time extract the update.zip file from TnT 2.20 and copy over the update.zip already in the root directory. YOU WILL NOT NEED A RECOVERY FILE FOR THIS METHOD.
11. Delete the recovery file in the root directory
12. Power down
13. Restart by pressing power and volume up
14. Should be in Clockwork
15. You want to clear both cache and data (two options on main screen)
16. After clearing both, choose install update.zip.
17. The next screen will show the update.zip. Go to its row and choose it by pressing home button
You should auto reboot and be set. You can then install the Folio Flash apk and install Titanium so you can do the market fix.
This is process is what saved me, at least.
Click to expand...
Click to collapse
Did not work... I might go and return it tomorrow. I even tried flashing to original firmware and nothing.
I got stuck in an unrecoverable boot loop as well. I tried to install TNT Lite 2.2, got a boot loop.
Tried to install TNT Lite 2.2, 2.2.1, 2.3 from microsd (yes changed the line to SDCARD2), always got the giant exclamation mark.
Tried to install the vanilla restore and stock TNT from here http://forum.xda-developers.com/showpost.php?p=9439414&postcount=7 still exclamation mark.
Tried to install Clockwork Mod, still exclamation mark.
EDIT: Finally got out of my bootloop by flashing the ViewSonic G-Tablet Restore file from DroidPirate
http://www.droidpirate.com/download/click.php?id=1777
http://droidpirate.com/category/ablets/viewsonic-gtablet/
Its the only one that worked.
Heya,
Since there is not enough info on the web regarding the rooting procedure for Videocon A55 HD and custom recovery for this awesomely smooth device, I'm uploading the necessary files and step by step guide. Hope it helps all the users of this device.
Remember rooting would tamper the warranty of the device and should be exercised carefully. The procedures mentioned below have been personally tested by me however I take no responsibility in case you ruin your device although I would be here to help you in such a scenario. Besides this the rooting script was not created by me and all the credit goes to the respective developer.
1. Rooting Procedure
Make sure you have enabled "USB Debugging" under Developer Options on your phone.
Keep your phone disconnected from computer via USB
a) Download and Install the ADB Interface driver for MTK 6589
Link to ADB Drivers
b) Download and extract the rooting package
Link to the Rooting Package
c) Now go to the extracted package and open a command prompt to that location as Administrator.
d) Type run.bat in Command Prompt and a message must appear "Press enter to root your phone..."
e) Press any key
f) Now after a few seconds the message should be " * daemon started successfully *"
g) Now connect your phone via USB to the computer
h) The cmd would automatically start pushing the necessary files onto your phone and when the process completes your phone will restart
Now you are rooted.To check install any Root checker application from playstore. Remember to grant permission while running Root Checker app when a pop up appears. It is suggested to update the SuperSU app from playstore and execute it at least once after that to update the su binary. You can also update the busybox package from playstore because busybox supplied with the rooting package is pretty old.
2. Installing CWM Recovery
Okie, since you are now rooted, most likely you would require a custom recovery to create full nandroid backups or test different ROMs. The CWM recovery provided here was created using MTKDroid Tools and is version 5.x (Non Touch). Again all credit goes to the developer of MTKDroid Tools for making such a powerful piece of software.
a) Download and extract the recovery package.
Link to CWM 5.x and Original Recovery for A55 HD
b) There are two files in the package , one is the custom CWM recovery and the other one is Stock Recovery (Names are pretty self understood)
c) Copy "Custom_Recovery_CWM_A55HD.img" to the root of your SD card
d) Rename it to "recovery.img"
e) Install Mobile Uncle Tools [MUT] from the playstore.
f) Open MUT and go to recovery update
g) Now you must see the recovery.img in a list. Just select it and follow the pop ups.
h) Now your phone would restart.
i) To check if the recovery update was successful, go to MUT and select "Reboot into Recovery" and your phone would most likely start in CWM recovery..
Alternative to get into recovery mode is to Press Power button + Volume Down key together when switched off.
3. Stock ROM for Videocon A55 HD
Okie, here we go, as I mentioned that I had got hold of the stock rom, so here I'm publishing it. The credit goes to Pratap Solunke (psolunke) for providing the Factory ROM zip.
I have just divided it into update.zip and files for SPFT for ease of downloading. Besides I have splitted each section into 4 parts and reuploaded it so you can download them at your ease. I'm providing the link for the whole folder which includes the changelog, update.zip and files for SPFT.
The ROM version is V7 (2013.07.15) which is different from the original ROM which was V5 (2013.06.08).
You can read the changelog for the updates in this ROM.
Link to ROM Folder
If using update.zip to flash this ROM, then
Step 1. Open the update.zip with winrar, Do not extract.
Step 2. Navigate to \META-INF\com\google\android\updater-script and extract this file only, then use "Notepad++" to open the file.Don't use default notepad.
Step 3. Delete assert(getprop("ro.product.device") == "A55HD" || getprop("ro.build.product") == "A55HD");
Step 4. Save the file, put it back to the same location in archive (It will take some time to add to archive)..Done...then proceed as usual.
a) update.zip is for reinstalling Factory Image of the ROM from recovery mode. The zip file is signed.
b) Files for SPFT are to be used with SP Flash Tool and can be used in case your phone is bricked. Do not flash the preloader unless you know what you are doing.
c) To download the files just go to the respective folder and right click on each file and hit download. After all four parts are downloaded, extract Part 1 of the downloaded splitted files and the files would be ready to be used as is.
d) Keep all four parts of the splitted files in a single folder and do not rename the splitted files.
If you have any questions related to A55 HD you can ask them here and I would try to help you the best way I can.
I'm still testing some custom ROMS but none seem to work . So far I've tested LEWA OS and MIUI ROM for xiacoao G6 Youth. However I'll keep trying and update once I have a working Custom ROM.
One more project in mind is to port Custom ROMS to A55 HD if none is available as is on the web.
If anyone of you is able to find a working Custom ROM for A55 HD kindly post it here so that we can have a repository of successful and useless attempts. I'm sure it would help others.
Rooting procedure worked after two attempts. The device is rooted.
While trying to install CWM recovery, get a problem. Can not see custom recovery in MUT. Pasted on both SD cards, internal and external also.
---------- Post added at 01:35 PM ---------- Previous post was at 01:34 PM ----------
Rooting procedure worked after two attempts. The device is rooted.
While trying to install CWM recovery, get a problem. Can not see custom recovery in MUT. Pasted on both SD cards, internal and external also. All the recoveries shown in the list are only remote recoveries
nanachitang420 said:
Rooting procedure worked after two attempts. The device is rooted.
While trying to install CWM recovery, get a problem. Can not see custom recovery in MUT. Pasted on both SD cards, internal and external also.
---------- Post added at 01:35 PM ---------- Previous post was at 01:34 PM ----------
Rooting procedure worked after two attempts. The device is rooted.
While trying to install CWM recovery, get a problem. Can not see custom recovery in MUT. Pasted on both SD cards, internal and external also. All the recoveries shown in the list are only remote recoveries
Click to expand...
Click to collapse
I forgot to mention , rename the recovery image to "recovery.img" and then put it in root of SD card and it would get detected by MUT...It will get detected instantly...Thankyou for bringing it to notice...Just updating the post...
done but some observations!!!!
DONE.
Some observations:
1. In CWM, cant see internal SD card. While, after mounting usb storage, can see external SD card only. NOTE, CANT SEE INTERNAL SD CARD ONLY WHEN TRY TO MOUNT INTERNAL PHONE STORAGE IN CWM. WHILE NORMAL WORKING NO PROBLEM.
2. Deleted.
3. Deleted.
4. Deleted,
5. Deleted.
6. The font size of Stock and CWM recovery is very small still it can serve the purpose.
Do any body have original/stock update.zip from Company?
Updates:
I think I figured out the problem with touch. Uninstalled an application called "Go Power Master" and the touch is ok even after connecting USB or charger. Thanks man. The phone is working very nice after rooting.
nanachitang420 said:
DONE.
Some observations:
1. In CWM, cant see internal SD card. While, after mounting usb storage, can see external SD card only.
2. After rooting, before even installing CWM, got some irratic behavior with touch. Like, while USB is connected, touch was not working as expected, it took long time to make USB storage active as after touching a specific required operation, like pulling down task bar it was doing something else like opening play store, opening game, or opening date and time settings. While unlocking lock screen, it was just opening any random phone application and is not even allowing to go back with back button or home button. Don't know this is related with what?
3. Irratic application were opening while touching different application but after removing USB, things were working better.
4. Rebooted in CWM and first tried to "fix permissions" to avoid that irratic touch behavior, thinking there was problem with permissions. Took nandroid back up, after fixing permissions. Wiped cache and dalvik cache and restarted.
5. Now, till now phone is not connected to PC with USB cable or connected to charging; it behaves better with touch but it is very troublesome to perform any operation after phone connected to PC with USB or to charger.
May be you have faced these issues or may not! Any suggested solution? Do any body have original/stock update.zip from Videocon?
Updates:
I think I figured out the problem with touch. Uninstalled an application called "Go Power Master" and the touch is ok even after connecting USB or charger. Thanks man.
Click to expand...
Click to collapse
For me the touch works without any problems...and as for detecting internal sd card...that also works flawlessly..i don't have the phone with me right now...Yesterday I was trying something and the nvram got corrupted [No baseband]...so right now it is resting at service center...Hope to get it next week...
One suggestion never install Carliv Touch Recovery on this phone...it messes with the baseband and display...Stick to this recovery until I build a more updated CWM...
Latest V-Store attached
Attached
nanachitang420 said:
Attached
Click to expand...
Click to collapse
Nice...let's make this thread a repository of A55 HD..And I have also got hold of the original update.zip and files for SPFT ...Will split them and upload to my google drive...and then share them..
update.zip
Aaaaanuj1 said:
Nice...let's make this thread a repository of A55 HD..And I have also got hold of the original update.zip and files for SPFT ...Will split them and upload to my google drive...and then share them..
Click to expand...
Click to collapse
The current version of my phone is 08062013. Can I flash this latest version through CWM and upgrade?
Tried to flash update.zip through CWM...
Installing: /sdcard/update.zip
Finding update package...
Opening update package....
Installing update....
assert failed: getprop("ro.product.device")=="A55HD" || getprop("ro.build.product")=="A55HD".
E: Error in /sdcard/update.zip
(Status 7)
Installation aborted...
Restored nandroid backup after this.
nanachitang420 said:
Installing: /sdcard/update.zip
Finding update package...
Opening update package....
Installing update....
assert failed: getprop("ro.product.device")=="A55HD" || getprop("ro.build.product")=="A55HD".
E: Error in /sdcard/update.zip
(Status 7)
Installation aborted...
Restored nandroid backup after this.
Click to expand...
Click to collapse
Okie it is an easy fix...
Step 1.Open the update.zip with winrar, Do not extract.
Step 2.Navigate to \META-INF\com\google\android\updater-script ,use "Notepad++" to open the file.Don't use default notepad.
Step 3.delete assert(getprop("ro.product.device") == "A55HD" ||
getprop("ro.build.product") == "A55HD");
Step 4.Save the file, update to archive..Done
Done
Successful.
Please add in above step 2 "to extract file Updater-script on PC" and then use N.........
Flashed modified update.zip from CWM and phone upgraded to version 15072013. To be strange it is showing v1.0 20130715 in build ie in about phone. All the applications were intact but lost root and also CWM recovery; then managed to root the phone and flash CWM with your fantastic guide.
After booting in CWM, wiped cache and dalvik cache(why? don't know). Phone is working nice. Thanks,
nanachitang420 said:
Successful.
Please add in above step 2 "to extract file Updater-script on PC" and then use N.........
Flashed modified update.zip from CWM and phone upgraded to version 15072013. To be strange it is showing v1.0 20130715 in build ie in about phone. All the applications were intact but lost root and also CWM recovery; then managed to root the phone and flash CWM with your fantastic guide.
After booting in CWM, wiped cache and dalvik cache(why? don't know). Phone is working nice. Thanks,
Click to expand...
Click to collapse
Nice...Yeah, people at Videocon forgot to change the version number i guess...and loss of root and cwm was due to restoring of system.img and recovery.img in the ROM file...so it's normal..
Besides one should always perform a clean install from CWM..i.e. Clear Data, Clear Cache, Clear Dalvik Cache, Format /system/ and then install ROMS..
And yes this ROM is a bit better then the one on phone..I received my phone today from service center and software was updated to this ROM..It felt much better .And the version was same , so this seems to be the latest ROM for A55 HD.. Enjoy
How to flash phone with sp flash tools
was trying to flash a recovery build on CWM site. I think it has spoiled baseband. No sim is getting detected. Any idea how to flash phone with SP tool? Don't have access to service station as am very far.
Edit: Managed to flash with SP tool. Used the files you have uploaded for SPFT. Selected all options and now phone is on and showing base band version, also sim are getting detected. The issue was preloader drivers for windows 8 which managed to install by disabling driver signature verification. Device rooted and installation of CWM through MUT was successful. Thanks.
Try this and this. Its as good as custom rom installation works very well with MTK6589
nanachitang420 said:
was trying to flash a recovery build on CWM site. I think it has spoiled baseband. No sim is getting detected. Any idea how to flash phone with SP tool? Don't have access to service station as am very far.
Edit: Managed to flash with SP tool. Used the files you have uploaded for SPFT. Selected all options and now phone is on and showing base band version, also sim are getting detected. The issue was preloader drivers for windows 8 which managed to install by disabling driver signature verification. Device rooted and installation of CWM through MUT was successful. Thanks.
Try this and this. Its as good as custom rom installation works very well with MTK6589
Click to expand...
Click to collapse
You must understand that the recovery partition is of 6 mb....and most likely the recovery you received from CWM online builder was more than 6 mb..hence your secro.img was also overwritten...hence the problems with baseband and imei....same thing happened with me 7 days back when I had to submit my phone to Service center. Unfortunately i didn't had the flash image then but it is good to know that it can also recover baseband and imei. And congrats for recovering your phone and I'm glad my contribution helps you...
Just remember one thing...if the boot, recovery,secro partitions are of more than 6mb then don't flash them as they would mess one thing or other...and hopefully you had disabled preloader in SPFT.....if not then from next time onwards please do it....because rarely you need to flash preloader...and a wrong flash can make your device a brick which can only be recovered by Test points.Hence never flash preloader until unless you know what you are doing.....And yes, I already use Gravity Box along with Xposed Framework...Great mod...Besides them I also use xhalofloatingwindow with bubble launcher and lwinrecent ...Both are xposed modules and work as expected.I also have init.d support which allows to make boot persistent changes on device....Along with that a few build.prop tweaks that take my ROM to the custom level...Let me know if you need any of this...
Please
Thanks for preloader advise. was not that much aware and will take care next time. Please share init.d support, build.prop tweaks and their usefulness.
For init.d, use term-init by ryuinferno.
http://forum.xda-developers.com/showthread.php?t=1933849
This is the link to the thread. Do not use zip-init or uni-init. Follow the guide on the thread. It works flawlessly.
Sent from my A55HD using Tapatalk
Which other phones has MTK6589 and same config ?
Tell me model number and brand, i will try to upload stock firmware.
it will help us built custom rom with custom features.
@anuj - Anyways if it brick again and need to send service center, please text me imei and location, i will make it done fast for you dear.:fingers-crossed:
Thank you Pratap bro. I'll let you know next time if I get to the point where I need to go to service center but I'm sure that with the ROM you provided I wouldn't need to go to one. And yes people you can ask for stock ROM from Pratap. He has excellent connections and can get you at least the Videocon ROM and may be others . Don't forget to thank him. Besides he is an excellent person who wouldn't shy away from helping you if he can. Ciao Pratap brother.
Sent from my A55HD using Tapatalk
Any new updates from Videocon for our A55HD?
File not found
File not found bro
(Rooting guide at post #5 http://forum.xda-developers.com/showpost.php?p=63803008&postcount=5)
(Stock ROMS at post #7 http://forum.xda-developers.com/showpost.php?p=63939728&postcount=7)
Hi,
The new flagship from Wiko, the Wiko Fever, it's a great device. :good:
Here my research with it:
- MT6753 with 16GB ROM and 3G RAM
- Bootloader LOCKED (you can unlock it using one option in the developers hidden menu (you know how to enable it!) and then after reboot in the bootloader execute "fastboot oem unlock" (note, that selecting OK you will erase your data!).
:good:
- You can download an EXPERIMENTAL (=ALPHA) custom Recovery (CWM-Carliv) from here (you need to flash it to use it):
***removed***
- Also you can download the original DUMP of the boot.img and recovery.img from here:
http://www.sendspace.com/file/zy9q6g
:silly:
You can pack/unpack the recovery/boot using the CarlivImageKitchen selecting "normal" (not MTK) version!
..
Hi,
This device (Wiko Fever) is the same as Micromax Canvas 5 E481:
http://www.micromaxinfo.com/mobiles/smartphones/canvas/canvas-5-e481
Also, is identical to Blue Life ONE X:
http://www.bluproducts.com/index.php/life-one-x-2016
Follow the thread (with custom Kernels) at:
http://forum.xda-developers.com/general/device-reviews-and-information/blu-life-one-x-2016-t3287428
Then the same firmware and rooting procedure will be shareable between both!
Here a great guide for Wiko Fever & Clones:
http://forum.xda-developers.com/android/general/guide-clones-t3421539
Hi,
Here the scatter file for Wiko Fever Lollipop 5.1.
Two versions: a) extracted from stock update (scatter_stok); b) made by hand (scatter3).
Rooting GUIDE
Hi,
Good news: Rooting is done! :victory:
Here is the guide for rooting your Wiko Fever:
Warning (for newbies): First copy all indicated files to your SD card using your phone in normal state. Or use a PC and a SD reader for copy them when indicated.
1) Unlock bootloader:
1.1) Boot for first time your device. I recommend to NOT register/login/add Wifi/add accounts/etc., because the unlock process DELETES all your data in the device. So to go more fast, skip all, and go directly to SETTINGS. In section ABOUT DEVICE, enable the developer options with eight time picks over “Build number”. Then in SETTINGS/DEVELOPER OPTIONS, enable the option “OEM unlocking”. Then power off.
1.2) Power on the device in the BOOTLOADER mode (using ADB: "adb reboot-bootloader"). Execute in your computer the command “fastboot oem unlock”, say YES with “vol+” and “power” buttons. Then select reboot. This ERASES completely your device (factory restore), but the bootloader will be UNLOCKED! Two reboots needed.
2) Install custom Recovery:
2.1) Download from here the BETA 1 of CWM BETA 2 of CWM BETA 3 of CWM: http://www.sendspace.com/file/4g87bj
OR Download TWRP Beta 1 for Lollipop 5.1 from Hanuma: http://www.sendspace.com/file/y4jel8
(Original post: http://forum.xda-developers.com/showpost.php?p=64543542&postcount=45)
OR Download TWRP 3.0.2.0 for Marshmallow from Hanuma: https://www.sendspace.com/file/9ms9zz
(Original post: http://forum.xda-developers.com/showpost.php?p=67531723&postcount=217)
2.2) Boot in the BOOTLOADER mode (using ADB: "adb reboot-bootloader"). Then execute command “fastboot flash recovery recovery-custom-wiko-fever.img”; and then “fastboot reboot”.
3) Rooting:
3.1) Copy last beta of SuperSU v2.52 to your SD Card (file BETA-SuperSU-v2.52.zip).
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
3.2) Boot in the CWM with “Vol+” and “Power” buttons.
3.3) Install ZIP from external-sd card.
3.4) Reboot and don’t select “fix root”, only “Yes”.
3.5) After boot, start SuperSU and configure it. Root done!
4) Xposed install:
4.1) Copy last release of Xposed Installer to your SD Card. Use files from here:
http://forum.xda-developers.com/showthread.php?t=3034811
* xposed-v78-sdk22-arm64.zip
* XposedInstaller_3.0_alpha4.apk
* xposed-uninstaller-20150831-arm64.zip (in case of errors).
4.2) Boot in the Recovery, and install the framework (file xposed-v78-sdk22-arm64.zip).
4.3) After reboot, install the Xposed APK (file XposedInstaller_3.0_alpha4.apk).
4.4) Reboot. The Xposed framework is running.
Enjoy!
Notes: Before starting to root your device I recommend to do a full DUMP of the firmware using the SP Flash Tool. Use my handmade scatter file. :angel:
Thank you to all developers & supporters! :highfive:
ChangeLog:
- Beta 3: Fixed ADB shell with root uid.
- Beta 2: Fixed SELinux context support in ext4 filesystem. Full woking for rooting!
Note: If you like to use adb shell in recovery but an error like "exec '/system/bin/sh' failed: No such file or directory" then first mount /system partition.
- Beta 1: Don't use this version, has a bug with SELinux contexts!
- Alpha(1,2,3): Pre-releases.
List of stock ROMs (for flashing with SPFlashTools) for Fever V8 (16GB/3GB) only:
- Lollipop v39 (last version until 5/2016): http://world.wikomobile.com/scripts/telecharger.php?id=140&type=MAJ
- Lollipop v22 (update 02.12.2015): http://fr.wikomobile.com/scripts/telecharger.php?id=105&type=MAJ
- Lollipop v18 (update 10.11.2015): http://fr.wikomobile.com/update-918-FEVER-4G
In case you need it!
List of stock OTA ROMs (for flashing with CWM/TWRP Custom Recovery):
If you have rooted your device, you can upgrade using these ROMs...
- Lollipop v39 (pre-rooted, with Xposed and ViPER Audio):
part 1: http://www.sendspace.com/file/d0js30 md5: e8706e0f5860e907fb8169856fc5e3b9
part 2: https://www.sendspace.com/file/iv4mnb md5: dd76926221ef40c872e4548a9b9e1f19
part 3: https://www.sendspace.com/file/6lfd18 md5: 838e6e608983a296611a284831fffd47
WARNING: At time this is untested! Give feedback with a post in the thread!
Decompress it using 7zip in your PC, copy files to your SD Card TWRP/Backup folder, and restore this backup with TWRP
Probably you want to use these versions!
Hi,
God news! I de-bricked my device... ****ing erroneous selinux context attributes in /system/lib64/ and /system/bin/ are the reason!
So, I don't futher need the stock SYSTEM partition. I'll continue with the rooting process... soon I'll publish it.
this device can support cm12-cm13?
djsolidsnake86 said:
this device can support cm12-cm13?
Click to expand...
Click to collapse
I hope!
Maybe will be easy for some developer to port one CM13 firmware for MT6753 to this device.
The opensource package for this device isn't at time available. Sorry!
Verify that the bootloader is unlocked
Hi manos78, first of all thanks for this guide and all the efforts you are putting into this.
manos78 said:
1.1) Boot for first time your device. I recommend to NOT register/login/add Wifi/add accounts/etc., because the unlock process DELETES all your data in the device. So to go more fast, skip all, and go directly to SETTINGS. In section ABOUT DEVICE, enable the developer options with eight time picks over “Build number”. Then in SETTINGS/DEVELOPER OPTIONS, enable the option “OEM unlocking”. Then power off.
1.2) Power on the device in the BOOTLOADER mode. Execute in your computer the command “fastboot oem unlock”, say YES with “vol+” and “power” buttons. Then select reboot. This ERASES completely your device (factory restore), but the bootloader will be UNLOCKED! Two reboots needed.
Click to expand...
Click to collapse
I just followed these steps to unlock the bootloader and I think everything worked as expected. Anyway, is there a way to be 100% sure that the bootloader is unlocked before (and without) flashing the recovery?
Thanks again!
hi guys, i followed the guide and all worked also with the last update
cippaciong said:
I just followed these steps to unlock the bootloader and I think everything worked as expected. Anyway, is there a way to be 100% sure that the bootloader is unlocked before (and without) flashing the recovery?
Click to expand...
Click to collapse
After the command "fastboot oem unlock" If you see the Warning message and the device is rebooted and formating the data partition, then you have for sure unlocked the bootloader.
But if you like to check it: "fastboot getvar all"; then find for the status of bootloader.
Thank you manos78!!
The only way of rooting is unlock bl->cwm->flash superSU? or is it possible to flash just a prerooted system.img keeping bootloader locked?
Also, have you noticed that sdcard0 become sdcard1 when inserting a sd card (wich replaces sdcard0) ? is there a way to avoid that? Choosing "internal memory" as default storage didn't avoid apps writing their datas on the slower SD :/
manos78 said:
But if you like to check it: "fastboot getvar all"; then find for the status of bootloader.
Click to expand...
Click to collapse
Unlocked
You have been really helpful, thank you!
oile said:
Thank you manos78!!
The only way of rooting is unlock bl->cwm->flash superSU? or is it possible to flash just a prerooted system.img keeping bootloader locked?
Also, have you noticed that sdcard0 become sdcard1 when inserting a sd card (wich replaces sdcard0) ? is there a way to avoid that? Choosing "internal memory" as default storage didn't avoid apps writing their datas on the slower SD :/
Click to expand...
Click to collapse
Hi,
I try to boot the custom recovery image with fastboot without flash and it fails. So for rooting, at time, the only way is: unlock->flash custom recovery->install superSU. But after that, you can try to: flash stock recovery->re-lock, if you like (not tested by me! Be carefull!). However, with the custom recovery you can do full backups, so I recomend it. The side effect is that you can't upgrade with OTAs.
Another option is use the original stock firmware and readback/flash the SYSTEM partition and modify it using an external computer (modify the IMG). But, this solution is quite complex.
Finally, related to the SD-CARD. The "internal memory" is only for "media", not for Apps. I use one 64GB SD on my Fever and I store in it: photos, music & ISO/IMG images. Any other data is in the internal storage (emulated sdcard). Also, I "installed" (=moved) some huge games (>100MB) to the sdcard (the real SD); and I store my Google Kiosk and Music files on the sdcard (also the real SD). Please, don't care about the sd storage, is working right on the stock firmware.
:good:
Actually I could inject root files into the system.img can anybody provide it? Do you know if bootloader only accepts images signed by manufacturer? In that case, a modded image can cause a security error. But I don't think it is so complicated on mediatek, given the fact that is possible to flash a custom recovery without any security check using flash tool.
About sd, I don't think I get what you mean by "media". System needs a "sdcard0" for a lot of apps like Sygic and Whatsapp and games like real racing. If sd card replaces it being sdcard0 instead of sdcard1 everything seems screwed to me: these apps are forced to write and read from a very slow memory (even a class 10 is way slower than internal memory)
oile said:
About sd, I don't think I get what you mean by "media". System needs a "sdcard0" for a lot of apps like Sygic and Whatsapp and games like real racing. If sd card replaces it being sdcard0 instead of sdcard1 everything seems screwed to me: these apps are forced to write and read from a very slow memory (even a class 10 is way slower than internal memory)
Click to expand...
Click to collapse
In stock Fever ROM:
/sdcard --> the REAL SD Card (the Sygic data, Google Music & Kiosk, etc. are in the REAL SD Card)
/storage/sdcard1 --> the EMULATED SD (internal memory)
Then you can use the SD as real one with Apps, and use alternative (emulated) when you like. The "media" Apps can use sdcard0 (real) or sdcard1 (emulated).
Related to this sentence: "hese apps are forced to write and read from a very slow memory (even a class 10 is way slower than internal memory)"
Please, remember: both, external memory and internal memory, have LIMITED life (write operations). Then, what you prefer: write more on the internal and not interchangable memory, or in a removable and inexpensive memory?
Please, think well! :angel:
Also, FYI, in my current Wiko Fever I use a 64GB SDXC UHS-II, far away than a simple class 10 (x15 reads/x30 writes).
oile said:
Actually I could inject root files into the system.img can anybody provide it? Do you know if bootloader only accepts images signed by manufacturer? In that case, a modded image can cause a security error. But I don't think it is so complicated on mediatek, given the fact that is possible to flash a custom recovery without any security check using flash tool.
Click to expand...
Click to collapse
I'm quite accustomed to filesystems and partitions since I've been using Linux for many years but I've got almost zero experience with Android internals, so please help me to understand if I got this right.
Now that I have unlocked the bootloader I can (potentially) flash "any" .img file on "any" partition (given that I'm using the right file on the right partition), right? So I could dump my system partition, put the su binary inside and then reflash it in fastboot mode?
I'm sorry if my questions might sound dumb to you but I'd like to start tinkering with Android a bit more but having a hard time finding a good starting point.
cippaciong said:
Now that I have unlocked the bootloader I can (potentially) flash "any" .img file on "any" partition (given that I'm using the right file on the right partition), right? So I could dump my system partition, put the su binary inside and then reflash it in fastboot mode?
Click to expand...
Click to collapse
Hi,
Unlock bootloader is for booting NON-SIGNED kernels (the boot or the recovery), not for partitions.
When you unlock the bootloader you can install (or boot) a CUSTOM recovery. In the custom recovery you can mount and modify the SYSTEM partition (where is included the root).
For "flash" or "dump" the internal memory of the device, if it's using a MTK cpu (like the Fever) then you can use SP FLASH TOOL. You have the scatter file in this thread!
Hi,
I'm new to this forum and a beginner to learn about android devices. I have a Gionee E3 android device (Asian version - English) with Android 4.2.1 on it. Unfortunately I have forgot the pattern lock and to make matter worse the following problems are also included -
1) No root - the device is not rooted
2) No USB Debugging
3) No custom recovery (I guess, only (stock recovery), Android system Recovery is displayed when tried pressing volume + and power key combination )
4) No wi-fi or mobile data could be enabled as the lock won't allow even to slide the screen from the top to get quick access to these things.
5) Windows Xp on my pc
I have tried the following -
1) ADB method to delete the gesture.key, but as the device is not rooted, failed with this attempt with several errors.
2) Tried from Cygwin, but the SU command gave error - -bash: su: command not found
3) Tried Aroma file manager zip file from Android system recovery ----> apply update from SD card, returned error - Installation aborted. Tried to resolve by fixing the updater script file through Notepad++ with different versions of Aromafm but nothing works.
4) Tried with several pattern cracking software zip files through Android system recovery ----> apply update from SD card, still getting error - Installation aborted.
Kindly help me to recover my data intact.
Don't want to root the device and there may be the risk of wiping the data off.
I have also tried to backup from Android system recovery ----> backup user data and 300 MB of data has been backup on SD card. Does this include SMS and phone contacts too with whatsapp data also?
Thanks in advance and sorry for long description, just wanted to make sure you guys know all the things I have tried. Your help will be greatly appreciated.
Sam
sam_h said:
Hi,
I'm new to this forum and a beginner to learn about android devices. I have a Gionee E3 android device (Asian version - English) with Android 4.2.1 on it. Unfortunately I have forgot the pattern lock and to make matter worse the following problems are also included -
1) No root - the device is not rooted
2) No USB Debugging
3) No custom recovery (I guess, only (stock recovery), Android system Recovery is displayed when tried pressing volume + and power key combination )
4) No wi-fi or mobile data could be enabled as the lock won't allow even to slide the screen from the top to get quick access to these things.
5) Windows Xp on my pc
I have tried the following -
1) ADB method to delete the gesture.key, but as the device is not rooted, failed with this attempt with several errors.
2) Tried from Cygwin, but the SU command gave error - -bash: su: command not found
3) Tried Aroma file manager zip file from Android system recovery ----> apply update from SD card, returned error - Installation aborted. Tried to resolve by fixing the updater script file through Notepad++ with different versions of Aromafm but nothing works.
4) Tried with several pattern cracking software zip files through Android system recovery ----> apply update from SD card, still getting error - Installation aborted.
Kindly help me to recover my data intact.
Don't want to root the device and there may be the risk of wiping the data off.
I have also tried to backup from Android system recovery ----> backup user data and 300 MB of data has been backup on SD card. Does this include SMS and phone contacts too with whatsapp data also?
Thanks in advance and sorry for long description, just wanted to make sure you guys know all the things I have tried. Your help will be greatly appreciated.
Sam
Click to expand...
Click to collapse
Hello,
Try posting your query here Android Q&A with all relevant details, the experts there maybe able to assist you.
-Vatsal
Hello Vatsal,
Thanks for your reply. I have moved it to the appropriate place.
And yes, I like your Iron Man.:good:
Folks,
I recently bought a Honor 8 and was trying to unlock the bootloder, install twrp and supersu by following the link below
https://forum.xda-developers.com/honor-8/how-to/guide-unlock-bootloader-install-twrp-t3554789
As stated in the link above, I got to the steps to install supersu. However, on following step 12, it has formatted the data and now the phone is in a bootloop(stuck on the blue screen showing HONOR label)
I'm guessing my phone will not boot up since the OS has been erased. Could someone please help me restore this phone to back to the stock firmware and steps needed to do so. I am new to Honor phones, so not sure what I need to do and steps needed. Would appreciate any help if possible??
1. Boot into TWRP
2. Once there, when asked to keep system read only? - swipe to allow modifications
3. Tap Install
4. Tap Select Storage - Select your SD card
5. Select the supersu file "SuperSU-v2.79-201612051815-EMUI5.0.zip"
6. Swipe to confirm flash
7. Ignore the multiple errors: "Failed to mount '/data' (Invalid argument)
8. Go back to the main menu
9. Select Reboot to Recovery
10. When asked to keep system read only? - swiped to allow modifications (again)
11. Tap Wipe
12. Tap Format Data
13. Type YES then hit enter
14. It will format data using make_ext4fs..
15. When finished, tap Reboot System
16. Reboot back into TWRP
17. Swipe to allow modifications (You can check the box to never show this again)
18. Tap Install
19. Select storage
20. Select your SD card
21. Select the supersu file "SuperSU-v2.79-201612051815-EMUI5.0.zip"
22. Swipe to confirm flash
23. You should see NO ERRORS now when installing SuperSU
24. Wipe cache/dalvik
25. Swipe to wipe
26. Reboot system
Download the rollback and marshmallow firmware package from honors website. Rename the rollback package to "UPDATE.APP" and place it in a folder called "dload" in your micro SD card. Put the micro SD in your phone, and boot into the firmware update screen (volume up + volume down + power all at the same time). Once it's done, delete the old UPDATE.APP file from the dload folder, rename your marshmallow firmware package to "UPDATE.APP", place it in the dload folder on your micro SD card, place the micro SD in your phone, and again flash the firmware using volume up +volume down +power
Since you still have access to the SD Card via USB, you can just download your firmware, extract it and put the UPDATE.APP in a dload folder on a microSD card and press all 3 buttons when starting up the phone to start installing the OS again.
Appreciate the feedback. I tried going to the below website to pick up the rollback package and the firmware( Android 6.0)
http://www.hihonor.com/us/support/search-result/index.html?keywords=Honor%208%20Firmware
My question is that is it possible to just restore it back to android nougat(7.0) in the U.S or has the 7.0 not released for the U.S markets yet?
I found the following link below for the Android 7.0(Nougat) firmware for Honor 8 but not sure if this work on the phones bought in the U.S
http://hwmt.ru/oth/HWFF/info/view.php?find_model=FRD-L14
Appreciate your feedback on this..
Since the phone is in bootloop, I would have to use a different phone and it's SD card slot to download the firmware and then put it on the Honor 8. I'm guessing the rollback process would only apply if I wanted to go back to the Marshmellow firmware. My question though is would I be able to restore it back to Android Nougat(7.0) if possible.
I found the following link below for the Nougat(7.0) firmware. Not sure if this will work on the U.S phones. Is there a different process to restore it back to Nougat?
http://hwmt.ru/oth/HWFF/info/view.php?find_model=FRD-L14
You can try just getting the nougat firmware onto your micro SD, then pressing volume up + volume down + power to see if it works. Worse case scenario is that you'll get an error.
If you do get an error, your can try the rollback procedure. Once you get marshmallow running you can always just update back to nougat with OTA.
Oh yeah, you don't necessarily need another phone. Just get a micro SD card adapter and plug it into your computer, then transfer the files into the dload folder
---------- Post added at 07:37 PM ---------- Previous post was at 07:34 PM ----------
You can use the following link for marshmallow firmware. Again, you can always update to nougat later using OTA
https://forum.xda-developers.com/honor-8/development/models-stock-firmware-packages-honor-8-t3501942
thanks for the info..just another clarification. The nougat firmware I found online was a zip file that included 3 files(attached snapshot) . I noticed one of the files is the UPDATE.APP.
My question is on creating the new dload folder do I need to remove the other two files or just copy all of 3 files in the dload folder before I try to restore the phone back.. Sorry if it's a straight-forward question, but I just want to make sure I'm doing this right.
Much thanks...
Just the UPDATE.APP
What are the other 2 files? Just curious
there is a folder called : META-INF which has some files in it and also a file called: full_mainpkg.tag which is only a 1KB file so maybe that's inconsequential.
Did you try out the procedure yet? The META-INF folder should not be necessary. You can always try the method with and without the folder included if you really need to.
I did...it did do the update following the steps you mentioned and it seems everything went fine as far as the update is concerned. I didn't get any errors, but once the phone rebooted it is still stuck on the blue screen with the Honor logo on it
Have you tried the rollback procedure as well?
---------- Post added at 04:16 AM ---------- Previous post was at 04:08 AM ----------
If neither procedure worked, you can try another procedure which involves extracting SYSTEM.IMG, BOOT.IMG, RECOVERY.IMG, and CUST.IMG from the UPDATE.APP file, then flashing all of them through fastboot, and finally preforming the rollback procedure again.
was finally able to get the phone to reboot and load the firmware. It does seem that there is some issue with the keyboard now as it's only showing OK google as the keyboard so I don't have a keyboard anymore. Not sure how to go around this. Also the phone seems a little laggy and unresponsive at times which wasn't happening earlier. I'm thinking of trying the rollback method to see if that helps or improves the performance of the phone. Let me know of you have any suggestions. Thanks again for your help...
That's a known issue with the keyboard. For some reason it does not function correctly after a factory reset. The rollback should fix everything. Once you are back on marshmallow, just update back to nougat (if you want to) through OTA system update.
Edit: it might actually be easier to just perform a factory reset on the nougat firmware. I'm assuming your data was wiped through the procedure anyway, right?
I can do the rollback but I just realized that I have the 64GB version which is the FRD-L14
http://www.phonemore.com/huawei-honor-8/models/629
I'm not sure if there is a FRD-L14(64GB) variant of the MM firmware available anywhere. If so, I'm not aware of the link of the site to find it. Secondly, if I do install the FRD-L04(32GB) variant of the MM firmware would that create problems for the phone in upgrading and later trying to root and install custom ROM etc.
Much Thanks
The nougat firmware your flashed earlier, was it the L14 firmware? I would not flash a L04 firmware on a L14. Instead, you can probably flash the L14 nougat firmware (unless you already did) and then perform a factory reset
EDIT: Refer to this thread:
https://forum.xda-developers.com/honor-8/how-to/frd-l14-users-how-to-restore-downgrade-t3537433
The OP uploaded the correct L14 firmware files. Remember to first flash the rollback package, then the firmware.
the firmware I flashed earlier was the L14 firmware. I went to the link you mentioned above in your post. It's a little confusing as far as the exact steps that need to be followed as people seem to be adding/modifying steps. Would help if I could get a clear step process on how/what to follow.
Also, is it okay to flash the rollback package and then flash the nougat firmware package for L14 if I am currently on nougat(not fully functioning as mentioned in the posts above).
This link below from your reference thread has a few L14 firmware's. I had earlier picked up the first one from the list. Not sure if that's the correct one to flash..
http://hwmt.ru/oth/HWFF/info/view.php?find_model=FRD-L14
Thanks again...
The rollback package is only used if you're downgrading from nougat to marshmallow. Otherwise, you don't need it. Since you were having some issues after flashing the nougat firmware, I would recommend that you rollback, and then update to nougat afterwards. Here's a step by step:
1. Get an micro SD card. Create a folder on it called "dload"
2. Download the F14 rollback package from the following link:
http://download-c.huawei.com/download/downloadCenter?downloadId=92098&version=360320&siteCode=us-h
Extract the UPDATE.APP file, and place it into your dload folder. Pace the micro sd into your phone
3. With the phone shut off, press volume up + volume down + power to flash the UPDATE.APP. Once it's done, shut down your phone and remove the sd card
4. Download the F14 Marshmallow firmware from the following link:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1201/g88/v66294/f1/full/update.zip
Extract the UPDATE.APP, and replace the old UPDATE.APP in the dload folder with the new one you just downloaded.
5. Place the micro sd into your phone. Repeat the button combination to flash it. Once it's done, shut down your phone.
6. Press volume up + power to boot into system recovery. Wipe the phone's data from this screen.
7. Boot into the phone. Go to settings -> About
Check to see if the model# etc is correct. If it is not, complete step 8. Otherwise go to step 9:
8. Download the following file:
http://update.hicloud.com:8180/TDS/...94/f1/full/hw/usa/update_data_full_hw_usa.zip
Extract the UPDATE.APP, place it in the dload folder, and flash it.
9. Boot into the phone. If you want to update to nougat, do the following:
Go to your dialer, and type *#*#2432546#*#*
This will force your phone to check for updates.
Then go to Settings -> Updater to update to nougat
I did follow your steps, but my keyboard has now vanished when the set up screen appears. It only shows google voice and I'm having trouble setting up my phone. Has anyone had the same problem. What can I do to get my keyboard back?
Note: my phone is unrooted. Not sure if that makes a difference