I just picked up a Yoga 8 today. did some searching around and found this page instructing how to root it. I was hoping to have a bit more control over the process, but i could not find any other information either through google or through xda. (I realize the thread i linked to is not for yoga 8, but several people said it worked, and when i used it, it did indeed root it)
I would like to experiment with what can be done through the xposed framework with this tablet, but before i go anywhere i want a custom recovery on it so i can do a nandroid backup, should something go wrong. I have not been able to find any custom recovery for this device at all. looking through CWM and TWRP's databases of supported devices, I've come up with nothing. any assistance would be appreciated, whether you know of another recovery (or an unofficial CWM/ TWRP) for the yoga 8 or if you have another method of making/ restoring nandroid backups.
Anybody have this tablet? any success getting a custom recovery running on it?
I picked up one yesterday after spending 3/4 of an hour in front of the stores shelf. I just couldn't really decide which tablet to get. The first thing I've done with it was going online to see how to root. I found a thread where someone posted that using the ideatab method would work on the yoga too. But I was too hesitant because I had just updated the firmware. But it would be great if this little thing would get some developer love.
I have installed CM11 on my old razr HD before handing it down to my wife and already thought about installing it on my note 3.
Rooting is done using Framaroot 1.9.1 (old Framaroot had no Barahir exploit). You can make a backup using MTKDroidTools and you can flash using SP Flash Tools. All tools can be found here at xda-developers. Unfortunately I don't know about a recovery for the time being, I'd like that too
Mikegrmn, I found those parts about rooting tool for the ideatab working on the yoga, and I ran them after updating to lenovos latest firmware. I can say it worked perfectly.
AP756, thanks for the info. Still hoping for custom recovery but at least I can try a few things now.
TWRP for 3G version of B6000-H (( not my work )) >>> https://drive.google.com/file/d/0Bzwq8_00PhMUYmg4ZjlldW9SQXM/edit?usp=sharing
Root, lenovo driver's and knowdelege needed
Edit : picture with battery stat's after rooting and some changes in rom. Managed 20 h of screen on time with 50% brightness, wi-fi always ON and still 28% batt left.
criszz said:
TWRP for 3G version of b6000 (( not my work )) >>> https://drive.google.com/file/d/0Bzwq8_00PhMUYmg4ZjlldW9SQXM/edit?usp=sharing
Root, lenovo driver's and knowdelege needed
Edit : picture with battery stat's after rooting and some changes in rom. Managed 20 h of screen on time with 50% brightness, wi-fi always ON and still 28% batt left.
Click to expand...
Click to collapse
unfortunately I have the non-3G version of the yoga 8 (I dont think the 3G version is available where i am).
I'm wary to try it since it's not the exact same device. I would personally wait for more support to be available for custom stuff.
It will work but let me do more research about it
Sent from HTC One 802w Dual Sim with my hand...
this is TWRP for B6000-F WIFI only >>>> https://drive.google.com/file/d/0Bzwq8_00PhMUTm5uYkdrd19QWE0/edit?usp=sharing
criszz said:
this is TWRP for B6000-F WIFI only >>>> https://drive.google.com/file/d/0Bzwq8_00PhMUTm5uYkdrd19QWE0/edit?usp=sharing
Click to expand...
Click to collapse
tried to install it and completely failed the easy way (running the included batch file). the good news is i have a bit of experience in linux so i opened the batch file for reference of commands needed, transfered the files over adb to the tablet, and then did the rest from there using the commands from the batch file with an android terminal emulator and the hackers keyboard (not required by still awesome). i used ROM manager to reboot to recovery and I AM THERE.
Thanks so much for your help. I am also going to, upon your signature's request, use the thanks button.
Thanks, I'm glad to hear you're fine now. Because bat file didn't worked for you makes me think you don't have driver for processor installed.
Trimis de pe al meu Lenovo B6000-H folosind Tapatalk
I've got the drivers installed properly. i used them to root it and to send the recovery over adb. it coughed back that I didn't have the permissions to copy the file (i was running admin cmd) so i set the default action for SuperSU to allow, i tried again, and it still didn't work.
Either way it is done now and working. i did a backup and copied it to my computer, so i can start playing around with it.
I got one of these last week because I was very curious on the MK-8125 (quad a-7)
http://www.kingoapp.com/android-root.htm
worked for rooting
https://drive.google.com/file/d/0Bzwq8_00PhMUTm5uYkdrd19QWE0/edit?usp=sharing
worked for twrp
what I'm still unable to determine is how to actually enter recovery without sending adb reboot recovery, the VOL + power seems to still enter the chineese recovery. But other than that it's fine and functions correctly.
If someone knows how to replace the default recovery with twrp and the button combo that enters that recovery with power off please advise.
I have my eye on this as well
https://github.com/TeamYogaBlade/android_device_lenovo_b8000
Hopefully adapting the b8000 build to the b6000 won't be that hard once they get it working.
Thanks guys for the info, things are working great so far
johnsongrantr said:
I got one of these last week because I was very curious on the MK-8125 (quad a-7)
http://www.kingoapp.com/android-root.htm
worked for rooting
https://drive.google.com/file/d/0Bzwq8_00PhMUTm5uYkdrd19QWE0/edit?usp=sharing
worked for twrp
what I'm still unable to determine is how to actually enter recovery without sending adb reboot recovery, the VOL + power seems to still enter the chineese recovery. But other than that it's fine and functions correctly.
If someone knows how to replace the default recovery with twrp and the button combo that enters that recovery with power off please advise.
I have my eye on this as well
https://github.com/TeamYogaBlade/android_device_lenovo_b8000
Hopefully adapting the b8000 build to the b6000 won't be that hard once they get it working.
Thanks guys for the info, things are working great so far
Click to expand...
Click to collapse
ROM Manager has the ability to reboot to recovery...or if thats the only thing you need to do, download swift reboot
https://play.google.com/store/apps/details?id=com.Jerry.swift_reboot
I was more looking for a button combo, thinking of a solution to maybe overwrite the correct recovery or something of that nature. But thinking about it, there's probably one recovery built into the boot loader and a separate image as just the recovery maybe? The button combo is proabaly just different areas of the bootloader instead of it redirecting to a different image like what happens on other devices. I think I remember the transformer having this "issue" where it seemed to have two. I'm sure someone will come along with a fix this at some point, it functionally works, just not ideal.
I've got the yoga 8 3G/wifi version. Rooted with farmaroot and installed cwm with mtktools. But I need stock recovery back. Can anyone provide with it cus I don't wanna flash stock os n start all over
johnsongrantr said:
I got one of these last week because I was very curious on the MK-8125 (quad a-7)
http://www.kingoapp.com/android-root.htm
worked for rooting
https://drive.google.com/file/d/0Bzwq8_00PhMUTm5uYkdrd19QWE0/edit?usp=sharing
worked for twrp
what I'm still unable to determine is how to actually enter recovery without sending adb reboot recovery, the VOL + power seems to still enter the chineese recovery. But other than that it's fine and functions correctly.
If someone knows how to replace the default recovery with twrp and the button combo that enters that recovery with power off please advise.
I have my eye on this as well
https://github.com/TeamYogaBlade/android_device_lenovo_b8000
Getting in to Recovery is easy.
Hopefully adapting the b8000 build to the b6000 won't be that hard once they get it working.
Thanks guys for the info, things are working great so far
Click to expand...
Click to collapse
Hold Power button + (Vol+ & Vo- together) and hold it few few seconds until you see a black screen where you will see selection between recovery and normal boot. Read the screen. Selection of option using volume up button and entering to selection is vol down button. Once you selected Recovery and pressed vol down, you will see screen with triangle. Now press power button gently. There you go.... You are now in Recovery (either 3e or your custom recovery).
Hope it helps.
goldfinv said:
I've got the yoga 8 3G/wifi version. Rooted with farmaroot and installed cwm with mtktools. But I need stock recovery back. Can anyone provide with it cus I don't wanna flash stock os n start all over
Click to expand...
Click to collapse
hi
which version of cwm did you install ?
and where can i find it ?
thanks
Ricx94 said:
tried to install it and completely failed the easy way (running the included batch file). the good news is i have a bit of experience in linux so i opened the batch file for reference of commands needed, transfered the files over adb to the tablet, and then did the rest from there using the commands from the batch file with an android terminal emulator and the hackers keyboard (not required by still awesome). i used ROM manager to reboot to recovery and I AM THERE.
Thanks so much for your help. I am also going to, upon your signature's request, use the thanks button.
Click to expand...
Click to collapse
hi
batch file didn't work for me too, and unfortunately i have no experience in linux.
so would you be kind to explain to me how you did step by step, please ?
thanks
Tuan79 said:
hi
which version of cwm did you install ?
and where can i find it ?
thanks
Click to expand...
Click to collapse
I used mtkdroid tools to install cwm on it
Related
Dear All
I'm a new android user, I just get a new A50 from Australia and try to root it. It's successful with z4root and I try to install Thai font to system. Unfortuantely I did wrong by deleting font folder in the system, therefore I can't run the system again. When I power on, it still have only garmin asus android logo and can't use it again. Does anyone please let me know how to restore or resolve this problem, or I have to throw it away? Thank you in advance.
Cheers!
Winext
Android 1.6 or the new 2.1 Eclair update?
It's a new Eclair 2.1 update, is there any solution?
Connect it to your computer via USB cable.
Using ADB, try this:
ADB REBOOT RECOVERY.
If it works, a yellow triangle appears with the green android guy.
Hit the HOME button. A menu appears. Use volume up/down to move through the options. Tap power to select it I beleive.
Reset/wipe to factory is one of the options.
If you need it, ADB is found in the Android SDK.
If that doesn't work, try calling in to Garmin for support.
Sent from my Garminfone using XDA App
Dear Spazmogen
Thank you for your suggestion, but I'm really new with ANDROID.
I downloaded ANDROID SDK and try to install but it dodn't work.
I use Win 7 64bit, do I need another software to run this command.
If possible, please let me know some previous post that already teach for beginner.
Thank you in advance.
Cheers!
Winext
ADB is a command line tool. But you will have to get Android SDK installed on the computer 1st.
Read the instructions for installing the SDK here: http://developer.android.com/sdk/index.html
ADB commands: HERE.
Interesting. I got into the recovery screen using the Quick Boot app,used the home button to show the menu. The arrows and volume buttons move, but can't actually do anything. Probably related to missing files that are reported in the data/cache/recovery folder.
https://www.garminasus.com/en_US/support/eclair/006-B1130-00.update
official 2.1 update came out today for USA GARMINFONES. Not the A50 Nuvifones elsewhere in the world...
Is the update different from the leaked one?
Sent from my Garminfone using XDA App
I am waiting for an answer to that question myself. I have no plans to change from the leaked version Garmin posted in mid-November.
Sent from my Garminfone using XDA App
Apparently someone did a bit comparison and said they matched. Plus, I tried and it told me it was the same version. On the plus side, I messed up my recovery partition and recovered it using the backups I made of each partition after I loaded 2.1 (dump_image). I made img backups and tar backups of all the files in 1.6 (I am anal about backing up). Good thing because 2.1 doesn't come with flash_image.
I can get into fastboot and the driver loads and stuff, but I get no devices listed when I do fastboot devices command. Next stop is Ubuntu
I know it works,just need to know how to get to it. Btw,I tried both the Garmin fastboot and adb drivers as well as adding the device hardware id's into the android drivers and neither worked.
I also need to find out if there is a similar enough kernel that I can use to get a fully functional recovery mode. I did find out that you can use adb just fine in the stock one and it loads a serial driver as well.
any possible way I could get that backup you made? I apparently didnt save my backup to the pc. And currrently I messed up permissions on my Garmin trying to get recovery working. I cant run the update or anything.
I've just stumbled across this forum post from google, I too am need of fixing my phone. All that is faulty is that the recovery mode has been overwritten with an incorrect one. Is it possible to extract the recovery image and reflash it from the optus supplied Android 2.1 006-B1130-00.update file?
Or is there a way of just getting say Rom Manager to work some magic for me?
Yes, it is possible... would be easier if someone could just use dump_image on a phone that has a working recovery mode and root access. I can provide the dump app and instructions.
Where can I get the Optus update, and are you positive recovery works on it? Does it also have working fastboot?
And to the other poster, which partition do you need? Btw, Rom manager has a permission fix mode. I can get you a tar file if it is the system partition or your choice of img or tar for the others.
And to everyone, after updating to 2.1, do a master clear because a lot of 1.6 apps are left over... duplicates.
Also, odexing all apps speeds it up a lot, with the caveat that you have to re-run the odex.sh file (found somewhere here and modified by me to be more thorough) after every app update or you will get force closes.
Oh I just reflashed the update again, and I got my recover menu back!
I'm not sure if i need any help anymore, but thanks for your offer of help merwin.
By working, do you mean that you can get to it with a hardware key combination and can actually select items?
first of all ,i 'm sorry for my english .my a50 is dead too.i also delet font folder and i use the adb command 'adb reboot recovery'.but the error is device not found. and my pohone can not boot .it stop at the android guy . how can i setup the device..Q.......Q......help me ..pls
garmin-asus a50
i have this garmin asus a50 was running 2.1 after installing a few apps.
tried to reboot and now is stuck on android screen.
tried hard reset stuck on android screen with wipe userdata on top
please help!
garmin-asus a50 dead
yoyoset
i think i have the same problem please let me know of any progress
thank you
Hi folks,
unfortunately I somehow bricked my ZTE Open. I flashed cwm (worked fine) but after flashing both system AND userdata via flash_image, the phone won't boot and what is much worse it won't boot into cwm anymore as it hangs there with just showing the logo and the cwm version. The menus are missing, it does not react buttons and does not show up in adb. FTM mode is also non-functional, holding volup gets you also into broken recovery.
For earlier ZTE devices like the ZTE Blade it seems to be possible to low level flash them in diagnostics mode. Diagnostics mode is working fine on the ZTE Open (it shows up with the diagnostics port on USB. Luckily I also have all the 20 partitions backed up, but I don't know how to flash them in this diagnostics mode. I tried putting the files into the root of the SD card and including sha1/256/512 plus md5sum files, but it was not impressed by that. Not sure if this only works in FTM mode, though.
Any help would be highly appreciated! I highly assume that the procedure is the same as for the ZTE Blade.
This may help. http://pof.eslack.org/2013/07/05/zte-open-firefoxos-phone-root-and-first-impressions/
At least there is more going on for Firefox Open over there.
Thanks but as you might have noticed I posted several comments there already, but I thought XDA would be the right place for unbricking devices.
Defier525 said:
Thanks but as you might have noticed I posted several comments there already, but I thought XDA would be the right place for unbricking devices.
Click to expand...
Click to collapse
Sorry! Eyes tight shut!
Are there any updates on this one?
I have bricked Open too, I'm attaching the PCB picture, if it is any help to maybe find UART or JTAG pins?
Can someone be really nice and please dump the bootloader from working ZTE Open in send it to me?
I've found some guy, who maybe can help me write bootloder with JTAG.
I think this should work, but no promises: https://sites.google.com/site/zteopenfirmware/download-mode
psywolf said:
I think this should work, but no promises: https://sites.google.com/site/zteopenfirmware/download-mode
Click to expand...
Click to collapse
Thanks for your time to help, but this does not work for me. I get an error, when I press flash button (printscreen under attachments).
I've tried to probe the pins with the multi-meter and found GND and V+ (picture under attachment)
Now it would be nice to have something like this -> http://www.grandideastudio.com/portfolio/jtagulator/
Defier525 said:
Hi folks,
unfortunately I somehow bricked my ZTE Open. I flashed cwm (worked fine) but after flashing both system AND userdata via flash_image, the phone won't boot and what is much worse it won't boot into cwm anymore as it hangs there with just showing the logo and the cwm version. The menus are missing, it does not react buttons and does not show up in adb. FTM mode is also non-functional, holding volup gets you also into broken recovery.
For earlier ZTE devices like the ZTE Blade it seems to be possible to low level flash them in diagnostics mode. Diagnostics mode is working fine on the ZTE Open (it shows up with the diagnostics port on USB. Luckily I also have all the 20 partitions backed up, but I don't know how to flash them in this diagnostics mode. I tried putting the files into the root of the SD card and including sha1/256/512 plus md5sum files, but it was not impressed by that. Not sure if this only works in FTM mode, though.
Any help would be highly appreciated! I highly assume that the procedure is the same as for the ZTE Blade.
Click to expand...
Click to collapse
tpt files for the zte open
https://www.dropbox.com/sh/rnj3rja7gd54s98/_twgXEkMFH/P752D04_DEV_EU_20131212_v1.2.7z
Thank you for the link. But what tool is supposed to be used to flash the files? And is there a way I can use my backup as well? In this case: how can I transform it to TPT files?
Update: I tried flashing it by following the instructions of the link posted by psywolf, but unfortunately I am getting the same error as aversario. I tried also flashing just recovery, but it seems like no single partition is flashed successfully.
So, I've ordered jtagulator and it showed the pins. Now I need jtag programmer, which one do you guys recommend?
And I am still looking for some great guy to share with me his bootloader of a functional zte open.
aversario said:
So, I've ordered jtagulator and it showed the pins. Now I need jtag programmer, which one do you guys recommend?
And I am still looking for some great guy to share with me his bootloader of a functional zte open.
Click to expand...
Click to collapse
on what partition is the bootloader? i have a UK revision 02 one, i would help you out if you tell me how to get the bootloader?
linr76 said:
on what partition is the bootloader? i have a UK revision 02 one, i would help you out if you tell me how to get the bootloader?
Click to expand...
Click to collapse
Well, I don't know the partition names by heart, but as I remember the bootloader is one of the small partitions (so definitely not system or boot or userdata or recovery).
The way to get that small partitions would be installing CWM recovery first -> http://pof.eslack.org/2013/07/05/zte-open-firefoxos-phone-root-and-first-impressions/
then enter adb shell on computer
su # to get root privileges
then it should be something like explained here -> https://www.youtube.com/watch?v=j3GOzUURSgM&feature=player_detailpage#t=153
And thank you very much for your time
If i figure out how to do that without CWM i'll upload it for you. Cannot install CWM because i need to be on stock recovery for development of update packages, sorry
Sent from my V3 using Tapatalk
linr76 said:
If i figure out how to do that without CWM i'll upload it for you. Cannot install CWM because i need to be on stock recovery for development of update packages, sorry
Click to expand...
Click to collapse
OK, I get that. I'm sure there exists a way to do it without changing recovery also. I just can't figure it out because that's the only Firefox OS phone I've had.
try to reinstall
Hi, I bricked my ZTE Open (EU version) too. Had bought it from a German Ebay seller and tried to flash FirefoxOS 2.0 on my device. I don't have the CWM recovery installed, only the "Firefox OS System Recovery" Big mistake, I know . When I switch on the device, the Firefox OS logo appears, then disappeas after a few seconds, and so on, the perfect bootloop
I can't access the device via ADB or fastboot.
When I ty to install any downloaded zip (even from ZTE's homepage) from the SD card, I get following messages:
Code:
--Install /sdcard ...
Finding update package ...
Opening update package ...
Verifying update package ...
E: signature verification failed
Installation aborted.
So there is no valid signature.
Can you help me please? Thank you!
Heinz
Found a solution by myself!:victory:
I downloaded the update.zip file from firefox.ztems.com (Update package of Android GB for OPEN device) and installed it.
After that I could flash the CWM recovery. It seems to work...
Hello there, I have a Multilaser M8 and it has a ROCKCHIP 3066 processor. I've already lost one M8 because of a faulty firmware available on their website. It apparently has no recovery mode as I couldn't manage to get it to boot, the only thing that it shows is the android logo with a exclamation mark. I know that there's a way to get past this window on some devices, but mine doesn't have the + and - volume buttons and I've tried touching the window on the corners and pressing the available buttons with different combinations but none of them worked. I've also spent a lot of time searching for something on Google, but found only frustrated people who where also a victim from that firmware. As my hands itch to change something on my tablet, I had to do something to make it safe as I have no methods of recovering my device if I manage to brick it. So, I managed to dump my rom using the romdump method wich consists in dumping the rom using the terminal emulator. The files that I've got from this dumping are: boot.img, checksum.md5, config.gz, recovery.img, system.info.gz and system.tar. The firmware available on the website is a .img file that must be flashed using RkBatchTool. So, what I want to know Is if with those files I can manage to restore my system so I'll have no worries if I get bootlops while trying to mod my tablet. The first thing that I would like to do is to manually install CWM, but I believe that it's very risky and I must be sure that I'll have a backup from the system to rely on. I'm sorry about my English and thanks in advance!
Update: I've successfully installed CWM on this device and I'm able to use it with my usb keyboard.
bump
how?
Hi!
How you did it?
Olá, como você conseguiu instalar?
Wo11ven said:
Hello there, I have a Multilaser M8 and it has a ROCKCHIP 3066 processor. I've already lost one M8 because of a faulty firmware available on their website. It apparently has no recovery mode as I couldn't manage to get it to boot, the only thing that it shows is the android logo with a exclamation mark. I know that there's a way to get past this window on some devices, but mine doesn't have the + and - volume buttons and I've tried touching the window on the corners and pressing the available buttons with different combinations but none of them worked. I've also spent a lot of time searching for something on Google, but found only frustrated people who where also a victim from that firmware. As my hands itch to change something on my tablet, I had to do something to make it safe as I have no methods of recovering my device if I manage to brick it. So, I managed to dump my rom using the romdump method wich consists in dumping the rom using the terminal emulator. The files that I've got from this dumping are: boot.img, checksum.md5, config.gz, recovery.img, system.info.gz and system.tar. The firmware available on the website is a .img file that must be flashed using RkBatchTool. So, what I want to know Is if with those files I can manage to restore my system so I'll have no worries if I get bootlops while trying to mod my tablet. The first thing that I would like to do is to manually install CWM, but I believe that it's very risky and I must be sure that I'll have a backup from the system to rely on. I'm sorry about my English and thanks in advance!
Update: I've successfully installed CWM on this device and I'm able to use it with my usb keyboard.
Click to expand...
Click to collapse
Hi, I just bought this phone from TECA Mobility, it turns out to be an Alps S5. See attachement for a detailed description.
I tried to ge the root. I tried some different tools, without success.
MTK Droid Tools ROOT button doesn't work but gives a link to xda's MKT forum, so I started with the recommended procedure. I tried to read back the ROM with SP-FlashTools but no way, it doesn't start. I also made some attempts with the Android SDK but adb backup of course doesn't work for the System partition without root.
When I send the adb reboot recovery command the phone goes in download mode, with the adb reboot bootloader command it goes in fastboot mode, while to have it in the factory recovery mode I have to manually hold down the start and vol down buttons. However, it doesn't matter, the readback does not start.
Should I try to install the CWD recovery without having a backup of the ROM? I think it's too risky. I looked at NEEDROM to see if I can find my ROM, but didn't find. I found these, "S5 SM-G900 MT6592", but I cannot be sure it's the right one.
Somebody can help me? I want to root the device.
gt56 said:
Hi, I just bought this phone from TECA Mobility, it turns out to be an Alps S5. See attachement for a detailed description.
I tried to ge the root. I tried some different tools, without success.
MTK Droid Tools ROOT button doesn't work but gives a link to xda's MKT forum, so I started with the recommended procedure. I tried to read back the ROM with SP-FlashTools but no way, it doesn't start. I also made some attempts with the Android SDK but adb backup of course doesn't work for the System partition without root.
When I send the adb reboot recovery command the phone goes in download mode, with the adb reboot bootloader command it goes in fastboot mode, while to have it in the factory recovery mode I have to manually hold down the start and vol down buttons. However, it doesn't matter, the readback does not start.
Should I try to install the CWD recovery without having a backup of the ROM? I think it's too risky. I looked at NEEDROM to see if I can find my ROM, but didn't find. I found these, "S5 SM-G900 MT6592", but I cannot be sure it's the right one.
Somebody can help me? I want to root the device.
Click to expand...
Click to collapse
Hi
1) First root your device using MTK Chopper (from PC) or framaroot (from android app) . Both work fine for MTK phones
2) Then using MTK droid tools backup your ROM. Here is the guide for that
http://forum.xda-developers.com/showthread.php?t=2730031
3)Then using MTK droid tools , make CWM recovery for your phone and install it . Here is guide for that
http://forum.xda-developers.com/showpost.php?p=44660171&postcount=417
Hit THANKS if it works
4shreyas said:
Hi
1) First root your device using MTK Chopper (from PC) or framaroot (from android app) . Both work fine for MTK phones
2) Then using MTK droid tools backup your ROM. Here is the guide for that
http://forum.xda-developers.com/showthread.php?t=2730031
3)Then using MTK droid tools , make CWM recovery for your phone and install it . Here is guide for that
http://forum.xda-developers.com/showpost.php?p=44660171&postcount=417
Hit THANKS if it works
Click to expand...
Click to collapse
I think you mean MOTO Chopper? It doesn't work, same as framaroot. They are old tools, they don't work anymore on the ROMs released after June 2014.
ODIN could work but I have not the sure/right file to download.
Generally speaking, the first thing to do is that of getting a backup of the ROM from the un-rooted phone
The guides that have been reported to work in these cases are:
From XDA:
http://forum.xda-developers.com/showpost.php?p=38337401&postcount=5
From China Devices:
http://www.china-devices.com/Thread-ROOT-CWM-Readback-your-ROM-with-SP-Flash-Tools#
Hereunder is the link to a success case story:
http://www.china-devices.com/Thread-Rooting-new-octacore-S5
There is no way I know to get the root with one-click-tools, there is no case I could find of anybody being able to root these phones by following other procedures.
If anybody knows better, please send me a link (MTK phones with ROM s released after june 2014 only!!!)
My only problem now is that I cannot get the read back with Flash Tools. I have tried uncountable button-pressing combinations, I have put the phone in recovery, download, fastboot mode, I have tried with and without battery, phone switched off or on - no error, but the read-back doesn't start (however my phone doesn't have the USB connection working when it's off or without battery).
The only way to skip this step is, if I had already a copy of the firmware available, a sure one.
Kindly help me if you can
Hi
Odin doesn't work for MTK mate
Try this latest app . It worked for some latest MTK KK phones
http://www.kingoapp.com/index.htm
Some other KK phones got rooted using vroot and rootgenius
Try your luck
Final option is to read back from SPFT which has 90+ success rate
Link to your stock firmaware: ( Official ROM Kingelon G9000 Version: 20140710_e2706v92_jbla_fhd -> This model number matches with model no in your image)
http://www.needrom.com/download/alps-star-kingelon-g9000-style-s5-touchwiz/
As bizarre as this sounds, I managed to get root on a similar phone (another MTK6592 S5 knockoff) with MTK tools. After exhausting my options, I clicked the ADB button and tried to get root shell regardless (via 'adb root shell', which probably isn't the proper command but it works regardless), which caused some sort of hang. After a minute or so I unplugged my phone, which caused things to start responding again; plugging it back in showed me as having temporary root, and the get root button actually worked the next time I tried it. I have no idea how or why it worked, or if it was a once in a lifetime occurrence, but it can't hurt to try.
Also, if your phone is anything like mine (and is actually running some form of KitKat), good luck getting write support for external SD cards. I couldn't get the system partition to mount (to write changes to the necessary file) via anything but ADB shell.
Problem solved
Good to know, thank ypu.
However in the meantime I solved my problem.
My phone works this way: I have to remove the battery and connect it to the USB cable. Then it goes in "preloader mode" and tries to install a driver called "MT65XX preloader driver". This driver actually emulates a COM port. If data transfer doesn't start, then, after a few seconds, the device goes down and disappear from Windows list. So it is easy to miss it when we install all drivers. I had to dowload it (from Google cloud service in my case), install and ... the Read Back started !!! Now I have completed the procedure and my phone is rooted with the CWD recovery installed.
ALPS S5 phone, real FLASHROM total size, 64GB ext SDcard not working
FEGuy said:
As bizarre as this sounds, I managed to get root on a similar phone (another MTK6592 S5 knockoff) with MTK tools. After exhausting my options, I clicked the ADB button and tried to get root shell regardless (via 'adb root shell', which probably isn't the proper command but it works regardless), which caused some sort of hang. After a minute or so I unplugged my phone, which caused things to start responding again; plugging it back in showed me as having temporary root, and the get root button actually worked the next time I tried it. I have no idea how or why it worked, or if it was a once in a lifetime occurrence, but it can't hurt to try.
Also, if your phone is anything like mine (and is actually running some form of KitKat), good luck getting write support for external SD cards. I couldn't get the system partition to mount (to write changes to the necessary file) via anything but ADB shell.
Click to expand...
Click to collapse
Maybe your phone was using firmware dated before june 2014? These was a bug that was exploited by Framaroot, but now they fixed it.
Is your phone also from ALPS? They sold it to me as capable of installing an external 64GB SDHC card, but I cannot have it working. Did you face any similar issue?
Otherwise 32GB cards work fine. Have you tried Aparted app? I use it for formatting/maintenace. This app makes partitioning, I guess it should work.
Also, if your phone is from ALPS, does it really have the ROM memory that is advertised?
I am facing some interesting issues with my phone on this respect. It was sold as having 16GB internal ROM, of which about 12GB avalible for users. In fact, the settings menu shows 10GB ,( 8GB available) of internal memory, and about 4GB of phone memory. Well, if I am correct, this so called internal memory maps to the directory /data (the one highest level in the root), who corresponds to partirtion mmcblk0p7. This partition actually has a size of 2.3GB instead of 10 !!!. f I install and try to run online Nandroid backup, I cannot have it working on paths directed towards the SDcards, but it works on the path data/media. Well, a backup of about 1.2GB is shown in the setting menu of the phone as a memory consumption of about 5 GB !!!
Then I had also hard time in copying this file from the /data directory to one of the SD cards. Root Browser and Root Explorer didn't work, only ES Manager with root rights worked.
Maybe you can give me some advice in finding some tool or SDK procedure to assess what the real total size of the memory is? Or some suggestion on how to fix the ext 64GB card? I got bad feelings with the guys who sold this phone to me, so I would like to collect some more evidence if possible.
I downloaded some applications for making device inspection. They read the manufacturers' data, so they get cheated - even if, in some cases, they can show the right amount of unused memory still available (quite lower than declared by the phone) . Also I cannot see the real size of the RAM memory used by the CPU .
Need stock ROM for Teca g89 mobile.
Hi experts,
I need stock ROM of TECA G89W ANDROID 4.4 2.4GHz 4GB-RAM +32GB 18MP 5.5-inch GPS SMARTPHONE. I brought this phone 6 months back and unfortunately the software corrupted. I tried with other ROMs and currently bricked my phone. If anyone who might have this phone by fortunate can help me to post the stock rom by read back or any process whatever you wish as you know much than me.
Desperately need the ROM file as I want to have my phone back to working.... Thank you....
need that rom
hello. can you ... or someone else, upload that rom again?
the link is no longer online at needrom, and that was the best rom for my kingelon g9000.
i had made a flash to try another rom, but is wasn't better. when i wanted to download again that ALPS rom it was no longer online!
gt56 said:
Hi, I just bought this phone from TECA Mobility, it turns out to be an Alps S5. See attachement for a detailed description.
I tried to ge the root. I tried some different tools, without success.
MTK Droid Tools ROOT button doesn't work but gives a link to xda's MKT forum, so I started with the recommended procedure. I tried to read back the ROM with SP-FlashTools but no way, it doesn't start. I also made some attempts with the Android SDK but adb backup of course doesn't work for the System partition without root.
When I send the adb reboot recovery command the phone goes in download mode, with the adb reboot bootloader command it goes in fastboot mode, while to have it in the factory recovery mode I have to manually hold down the start and vol down buttons. However, it doesn't matter, the readback does not start.
Should I try to install the CWD recovery without having a backup of the ROM? I think it's too risky. I looked at NEEDROM to see if I can find my ROM, but didn't find. I found these, "S5 SM-G900 MT6592", but I cannot be sure it's the right one.
Somebody can help me? I want to root the device.
Click to expand...
Click to collapse
Hi see if the link helps you to find the mach of your phone model file:///data/data/com.android.browser/files/kingelon_g9000.mht
---------- Post added at 04:58 PM ---------- Previous post was at 04:53 PM ----------
gt56 said:
Hi, I just bought this phone from TECA Mobility, it turns out to be an Alps S5. See attachement for a detailed description.
I tried to ge the root. I tried some different tools, without success.
MTK Droid Tools ROOT button doesn't work but gives a link to xda's MKT forum, so I started with the recommended procedure. I tried to read back the ROM with SP-FlashTools but no way, it doesn't start. I also made some attempts with the Android SDK but adb backup of course doesn't work for the System partition without root.
When I send the adb reboot recovery command the phone goes in download mode, with the adb reboot bootloader command it goes in fastboot mode, while to have it in the factory recovery mode I have to manually hold down the start and vol down buttons. However, it doesn't matter, the readback does not start.
Should I try to install the CWD recovery without having a backup of the ROM? I think it's too risky. I looked at NEEDROM to see if I can find my ROM, but didn't find. I found these, "S5 SM-G900 MT6592", but I cannot be sure it's the right one.
Somebody can help me? I want to root the device.
Click to expand...
Click to collapse
Hi see if the link helps you to find the mach of your phone model file:///data/data/com.android.browser/files/kingelon_g9000.mht , you can root it using v root you will need a pc to root your phone.
Hi folks,
Today it's a great day for me : I have successfully patched the kernel to have a 100% working TWRP 3.2.1 for our Maze Alpha 4G.
I have port a Jemmini build for Bluboo S1 and I have patch the kernel to have a working touch panel
I have followed this Thead
For the Maze Alpha 6G version, you can test it and tell me please.
How to flash:
I Fastboot method (must unlock device) :
1- Reboot your phone in bootloader mode : adb reboot bootloader or phone off, press and hold at the same time POWER and Vol+ buttons
2- Connect your phone to your computer with adb/fastboot already installed
3- Unlock your bootloader : fastboot oem unlock (it will erase you data, only data)
4- Flash the recovery : fastboot flash recovery recovery_maze_alpha_4G_twrp-321.img
II SPFlashTool method (no need to unlock device) :
1- Download latest version of SPFlashTools.
2- Execute it and load the provided scatter (the recovery image must be in the same folder as the scatter and must be renamed to recovery.img) then press "Dowbload" button
3a- windows SPFlashTools users : phone off, press VOL+ and connect it to your PC (running SPFlashTool and waiting for phone connetion)
3b- linux SPFlashTools users : phone off and connected to PC , press VOL+ and POWER while your PC is running SPFlashTool (with sudo) and waiting for phone connetion.
Update : you can found here the latest version: TWRP 3.3.0 for MAze Alpha 4Ghttps://github.com/dreambo/android_device_maze_alpha/releases/tag/3.3.0
have a nice day.
Works great on Maze alpha 4G. Thanks.
But I forgot to save original recovery...
super_sonic said:
Works great on Maze alpha 4G. Thanks.
But I forgot to save original recovery...
Click to expand...
Click to collapse
You can get the original recovery from the stock rom designed for SPFlashTool, provided here
dreambo said:
You can get the original recovery from the stock rom designed for SPFlashTool, provided here
Click to expand...
Click to collapse
Thanks. Can you share stock recovery.img, if you have it? I have recovery-verified.img from V05 but I don't know if there is a new update and if size is correct: 11,54MB. Your TWRP recovery has got a size of 14.24MB...
Can you make a small procedure on how to install it? Will help many nOOb's out.
And people need to report back issues and successes !!!! Again I see many questions and people with issues that we seniors try to help out with that end up in no more response which to me is not done and not helping others.
I have a 6GB version that I could test on but at the moment I am using it for other stuff and I can't risk bricking it this week.
Would finally love to start some stuff happening on this phone.
Ok in the process of doing so on my 6GB/64GB version.
edit : congratz I now have a 'phone' that can only go into TWRP . Should have never ever done this!
Says no OS installed ... really nice
Edit 2: after hours wasted was able to get your zipped rom on the Maze but I got no boot with that TWRP, so flashed recovery-verified.img from the 6GB rom from Alpha I had downloaded ... It would then start up but show 4GB out of 6GB. No good but at least all the rest seemed to work. All other effort to get it going back with the proper kernel etc resulted in frustration.
So now to flash the official rom back via their tool... that one got me really frustrated and was completely my fault that I couldn't figure it out. But you know angry, frustrated, must get it back to work, can do this ... After all these years of toying with phones we are so used to pressing 'power and vol+ or vol-' together to make something work. Now in the end I re-read the manual again and saw that you only have to push vol+ and NOT vol+ and power together or it wont go in the mode it should go to make it flash!!
In case this happens : The best advice I can give to people is to download the proper MTK drivers. Search for vcom drivers for MTK and you will find.
Print out the instructions and mark every step you do to the letter. The flashing itself only takes like 3 or 4 minutes
lukesan said:
Ok in the process of doing so on my 6GB/64GB version.
edit : congratz I now have a 'phone' that can only go into TWRP . Should have never ever done this!
Says no OS installed ... really nice
Edit 2: after hours wasted was able to get your zipped rom on the Maze but I got no boot with that TWRP, so flashed recovery-verified.img from the 6GB rom from Alpha I had downloaded ... It would then start up but show 4GB out of 6GB. No good but at least all the rest seemed to work. All other effort to get it going back with the proper kernel etc resulted in frustration.
So now to flash the official rom back via their tool... that one got me really frustrated and was completely my fault that I couldn't figure it out. But you know angry, frustrated, must get it back to work, can do this ... After all these years of toying with phones we are so used to pressing 'power and vol+ or vol-' together to make something work. Now in the end I re-read the manual again and saw that you only have to push vol+ and NOT vol+ and power together or it wont go in the mode it should go to make it flash!!
In case this happens : The best advice I can give to people is to download the proper MTK drivers. Search for vcom drivers for MTK and you will find.
Print out the instructions and mark every step you do to the letter. The flashing itself only takes like 3 or 4 minutes
Click to expand...
Click to collapse
Haha I did the same exact thing..and managed to get it working after flashing it with the spflash tool but the trick is if you have Windows 10 latest version you won't be able to do this..at least I couldn't because of driver incompatibility so in my case:
1 I installed Windows 7 and installed mtk drivers for spflash tool
2.booted into twrp
2.1 if you can't boot into twrp or it doesn't turn on you can still try this
3.Start sp flash tool and download the zip the one(in case of trouble)that the moderator published
4. Load the scatter file and make sure that all of the files and the scatter are in the same folder.
5.click download and leave it like that
6.plug in your phone in fastboot if you can't try one of the following
6.1 just plug it in turned off and monitor spflash tool status
6.2 plug it in holding volume up key (just volume not power)
6.3 in twrp go to boot and boot into bootloader
And the tool should do the rest
If all else fails check the drivers one more time
After all that if you are feeling adventurous flash twrp one more time and do not factory reset through twrp ! Because that was the problem in my case and after you unlock bootloader boot your phone and go through the setup without setting the password because twrp will be locked.
Good luck.
frumac96 said:
Haha I did the same exact thing..and managed to get it working after flashing it with the spflash tool but the trick is if you have Windows 10 latest version you won't be able to do this..at least I couldn't because of driver incompatibility so in my case:
1 I installed Windows 7 and installed mtk drivers for spflash tool
2.booted into twrp
2.1 if you can't boot into twrp or it doesn't turn on you can still try this
3.Start sp flash tool and download the zip the one(in case of trouble)that the moderator published
4. Load the scatter file and make sure that all of the files and the scatter are in the same folder.
5.click download and leave it like that
6.plug in your phone in fastboot if you can't try one of the following
6.1 just plug it in turned off and monitor spflash tool status
6.2 plug it in holding volume up key (just volume not power)
6.3 in twrp go to boot and boot into bootloader
And the tool should do the rest
If all else fails check the drivers one more time
After all that if you are feeling adventurous flash twrp one more time and do not factory reset through twrp ! Because that was the problem in my case and after you unlock bootloader boot your phone and go through the setup without setting the password because twrp will be locked.
Good luck.
Click to expand...
Click to collapse
Wait a sec., missing a couple of things here.
1) Do you have a 6GB ?
2) In case you have a 6GB did you manage to get it working, rooted and all?
Your point 6) well I flashed mine on the latest 64bit win10 ... but.... if the phone is off and you connect the usb cable my phone tried to boot up either in twrp with no com port. Also booting it in bootloader doesn't make the comport visible so you can't flash.
The only way to make mine visible for the flashtool was to press vol+ and then connect the usb cable.
Btw I am glad someone finally responds and spreads information. A very good post! Your first 'thanks' well deserved!
I wonder where the guys are that I was trying to help. Did they throw their phones away or something? Sharing is caring I thought.
I want to root mine to alter the camera settings and the media xml file. I find it strange that our sensor, which is the same as in my wife's Xiaomi's, takes seriously bad pictures.
lukesan said:
Wait a sec., missing a couple of things here.
1) Do you have a 6GB ?
2) In case you have a 6GB did you manage to get it working, rooted and all?
Your point 6) well I flashed mine on the latest 64bit win10 ... but.... if the phone is off and you connect the usb cable my phone tried to boot up either in twrp with no com port. Also booting it in bootloader doesn't make the comport visible so you can't flash.
The only way to make mine visible for the flashtool was to press vol+ and then connect the usb cable.
Btw I am glad someone finally responds and spreads information. A very good post! Your first 'thanks' well deserved!
I wonder where the guys are that I was trying to help. Did they throw their phones away or something? Sharing is caring I thought.
I want to root mine to alter the camera settings and the media xml file. I find it strange that our sensor, which is the same as in my wife's Xiaomi's, takes seriously bad pictures.
Click to expand...
Click to collapse
Sorry forgot to mention I have a 4 GB version but since maze is not providing the roms on their website any further development will be limited..thank God for dreambo he is the only guy doing any work here and like you said nobody is responding to any questions asked..shame really because maze is a great phone with a terrible camera..which drivers did you use on Windows 10? because I tried a hundred of them and non of them recognize my phone..and in adb I can run the command fastboot reboot bootloader but after reboot none of the commands are working .
And yes I did manage to install twrp and root using magisk and I to hope that all those other guys didn't brick their phones
frumac96 said:
Sorry forgot to mention I have a 4 GB version but since maze is not providing the roms on their website any further development will be limited..thank God for dreambo he is the only guy doing any work here and like you said nobody is responding to any questions asked..shame really because maze is a great phone with a terrible camera..which drivers did you use on Windows 10? because I tried a hundred of them and non of them recognize my phone..and in adb I can run the command fastboot reboot bootloader but after reboot none of the commands are working .
And yes I did manage to install twrp and root using magisk and I to hope that all those other guys didn't brick their phones
Click to expand...
Click to collapse
This is the filename I used on Windows 10 VCOM Drivers (All MTK Devices & All Windows OS version).zip I think I downloaded it from XDA somewhere.
Also something you must know https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/
Another thing I experienced is that one USB connector is not the other one on a pc. Always connect it to the ones directly on the main board next to the other device outputs like audio etc. and preferably not go through ones that have been extended via a cable like the ones on top of the casing or so. Also a must have application is usbdeview.
Well should be easy to get it going if you can boot it into 'fastboot' then you can try as much as you want to. But djeeeeezzzz the letters are very small when you boot it with a power+volume up . Also check that volume up will toggle between 'fastboot', 'recovery' and 'normal start' and volume minus will select it, not the power button which would be more logical to me.
I might have another go at trying to get it working on my 6GB but it involves having a lot of time and knowing that I will get frustrated. Installing all apps and settings is also a time consuming thing. Once you have TWRP on it it all becomes easy to backup. So many things to test or try.
Maybe dreambo has an idea on how to get mine up to a 6GB one as it is probably only indicated in the kernel.
Anyway I will continue to write down my progress.
Ok more frustration. Done multiple things to try to get this running. It's good to know that the original rom is easy to install again after practice.
Take 1: Try to install clean 6GB rom and immediately install TWRP.
Results: Dreambo forgot 1 step and that is to allow OEM unlock in the developer options. If you do the adb command to unlock press volume up and it will unlock (very hard to see, very small letters on the display in bootloader mode)
Well TWRP starts but immediately I get a message 'mount decrypt data password' which I tried a couple of things but no go. Also googled... different solutions but always ending in a bootloop to TWRP
A possible solution that I read was to create a startup pin .... no go 'pin not valid'
Take 2: Take all the rom files and change the scatter file with the one dreambo provided.... Thought it was successful but ended up with the same Chinese recovery. Trying to figure out why since the filename was correct like indicated in the scatter file. Came to the conclusion that the original file was/is called recovery-verified.img and not recovery.img. Really really strange this one as in the original scatter file it also points to recovery.img. So this one I will have to investigate. Renaming the TWRP file to recovery-verified.img lead to a error during the initial scan of the flashtool.
So moral of the story is that I am back on square 1 and lost 2 hours today (plus putting all apps and settings back) today.
I get a bit lost, is this TWRP method only working with the 6GB or also with the 4GB version?
CYberdog11 said:
I get a bit lost, is this TWRP method only working with the 6GB or also with the 4GB version?
Click to expand...
Click to collapse
There is no fundamental difference between 6G and 4G version.
It must works in boat versions.
If you have issues with SPFlashTool try this (no need to install any drivers on Windows 10) :
Put the preloader.bin (found in the rom package designed for SPFlashTool) in the same folder as the recovery.img without checking it the list of partitions (only recovery must be checked) and click on Download to flash the recovery, as usual.
Perhaps SPFlashTool cannot read by himself the preloader in the EMMC, and we must provide it.
The linux version of SPFlashTool not works at this moment, I do not know why
With the SPflashtool I always get the error:
ERROR:STATUS_DA_HASH_MISMATCH (0xC0070004)
HINT
CYberdog11 said:
With the SPflashtool I always get the error:
ERROR:STATUS_DA_HASH_MISMATCH (0xC0070004)
HINT
Click to expand...
Click to collapse
From another thread:
mmakdz said:
google translate
Hello
I had the same problem, (error BROM ERROR: STATUS_DA_HASH_MISMATCH)
what I did: I use Windows 7 System
1- clear all drivers for smartphones with "usbdeview-2-17"
2- install Drivers "Drivers_Auto_Installer_v1.1236.00"
3- install "PdaNetA4170"
4- use "SP_Flash_Tool_v5.1708_Win" to flash the rom. first flash the preloader alone and then flash the others.
the problem was the bad installation of the drivers, after that everything went well for me.
try it can work for you too.
the mentioned software is easy to find on google
Click to expand...
Click to collapse
dreambo said:
There is no fundamental difference between 6G and 4G version.
It must works in boat versions.
If you have issues with SPFlashTool try this (no need to install any drivers on Windows 10) :
Put the preloader.bin (found in the rom package designed for SPFlashTool) in the same folder as the recovery.img without checking it the list of partitions (only recovery must be checked) and click on Download to flash the recovery, as usual.
Perhaps SPFlashTool cannot read by himself the preloader in the EMMC, and we must provide it.
The linux version of SPFlashTool not works at this moment, I do not know why
Click to expand...
Click to collapse
If there is no difference between the 4GB and 6GB then why did I literally spend days on trying this and documenting what happened?
lukesan said:
If there is no difference between the 4GB and 6GB then why did I literally spend days on trying this and documenting what happened?
Click to expand...
Click to collapse
Do you have the 2 versions of the phone and do you have notice any difference of the flashing procedure ?
dreambo said:
Do you have the 2 versions of the phone and do you have notice any difference of the flashing procedure ?
Click to expand...
Click to collapse
I only have the 6GB version of the Maze Alpha. But you wrote that the procedure should work for both versions. I think I wrote down what happened with mine if I installed TWRP.
I tried both the 'regular' flashing and then the full rom install with the trick to put the files in the directory and rename but both ended up as I've written in my previous post.
lukesan said:
I only have the 6GB version of the Maze Alpha. But you wrote that the procedure should work for both versions. I think I wrote down what happened with mine if I installed TWRP.
I tried both the 'regular' flashing and then the full rom install with the trick to put the files in the directory and rename but both ended up as I've written in my previous post.
Click to expand...
Click to collapse
From times to times, I notice trouble with flashing using SPFlashTools.
First (when I post my first post relating of the root) I use the linux version : no issues it works perfect, no need of any drivers!
Actually, no way to have it working on linux, why I do not know!
I have tried Windows 10 and I notice that we have to provide the preloader to have it working, as I write in my post.
In theory, and only in theory, the SPFlashTool must works the same manner in any phone with a Mediatek SOC.
But in reality, we have notice that with exactly the same phone the flashing procedure works for some users and not for others!
SPFlashTool is a very capricious software, there is no warranty to have it 100% working in any platform, even with the same OS.
dreambo said:
From times to times, I notice trouble with flashing using SPFlashTools.
First (when I post my first post relating of the root) I use the linux version : no issues it works perfect, no need of any drivers!
Actually, no way to have it working on linux, why I do not know!
I have tried Windows 10 and I notice that we have to provide the preloader to have it working, as I write in my post.
In theory, and only in theory, the SPFlashTool must works the same manner in any phone with a Mediatek SOC.
But in reality, we have notice that with exactly the same phone the flashing procedure works for some users and not for others!
SPFlashTool is a very capricious software, there is no warranty to have it 100% working in any platform, even with the same OS.
Click to expand...
Click to collapse
The thing is that I have no issue with flashing the software as I can perfectly flash the original rom. The problem is that when flashing the TWRP file, in both options by the way, so also via method 1, I get a boot loop.