Hello All!
Relative noob here...but more seasoned all the time. Firstly my viewpad device info from FTM:
SWVer=3.410
Model: FM6-001
HWVer: 107
In a nutshell: My bluetooth wasn't turning on (would turn on..then off). So tried to fix by:
1) Rooting and install CWM 5.0.2.6 (awesome tool BTW) and various ROMs, all done with success.
2) No good, oh well now want to give up. Contacted Viewsonic got RMA to return unit..however now concerned they'll not honor warranty if I rooted the device (sigh). So thought I'd return to stock. I did backup..but was already rooted when I thought of it.
3) Trying to return to stock using many versions Sutl3 and Sutlr...and on different PCs none work..once it boots to CWM menu...just stalls with error eventually.
4) Tried to install Napster's CWM with Recovery Menu to be able to return to original state with stock recovery. My version of CWM won't install it...errors out (another great tool though by the sounds of it).
5) Can't use fastboot..never sees device...although ADB works OK. Believe that the Bluetooth issue may be a hardware problem and may be effecting devices ability to work in "download mode". Note that HS-USB device is never present in device manager in Windows even though driver is installed.
So...my question...how can I return my device to stock with one of the below .nb0 files without stock recovery, sutlr or sutl3?
Files I have:
FM6-3310-0-5029-A02.nb0
FM6-3350-0-1008-A01.nb0
Can I somehow use CMW? Can I somehow use adb and "flash_image"?
Will super appreciate any thoughts!
Many thanks in advance!
Johnster25
If I remember correctly, you use SUTL3 from Viewsonic on your PC with the *.nb0 file in the same sub/directory - and just run it to flash the stock ROM or return it to factory condition, you do NOT use CWM to flash or re-install the *.nb0 file ... Part of this process involved overwriting the CWM installed on your rooted device & reversing it to become unrooted, look under the Development subforum here in this section as there's a link/discussion about how to restore, please double check on the details written up.
Also, make sure you have a mSD card in the slot - and that the USB drivers are loaded & running (they should be installed already back then) - might want to power down & restart the PC and do the same to the Vpad7.
Let us know how it go & good luck !
Many thanks for your response.
Well, what has happened when I've used SUTL3 so far is that I select the .nbo image I wish to flash, then the program restarts teh VPAD7 into recovery mode.
From what I've read, after a few moments the phone is then supposed to enter some sort of "download mode" whereby the new image is pushed across the USB cable.
It's at this point with SUTL3 seems to error out, and the phone simply remains in CWM.
I've read a few posts that suggest that not using the correct image could produce a response like this, so I'll retry again this PM having tried re-downloaded the two .nbo files I've tried, and one I've not tried.
Will let you know how it goes!
J.
Hi Again,
OK I've retried it with a fresh copy of SUTL3, and new .nb0 files. Still no good.
Take a look at the enclosed pictures. The first time I try to run SUTL3 the device not configure error shows up. By this point CWM is showing on the VPAD7. I try to run SUTL3 again in this state and now the device not detect error shows up.
So all in all it seems to me that the device when in CWM mode is not exposing an interface to the computer...or the computer lacks the driver needed to utilize the interface.
I've also enclosed a picture of my windows devices when the VPAD7 is connected, as well a copy of the drives that show up when it's connected. The only time the drives change is when the VPAD7 is in CWM mode, at which time the H: drive (where the adb program are) is not present.
So am I missing a driver?
BTW: Have tried to copy down the synchronization program that is on the H: Drive and ran it while running SUTL3...thinking somehow it acted like a bridge to the VPAD7 (I've seen some posts that suggest this). Still no good.
J.
OK..one more piece to the puzzle...or maybe off the trail...but when trying on two differnt PCs when the VPAD7 is first plugged in I get one set of driver installs...and note that the HS-USB has an error.
Later when trying to run SUTL on it...another set of driver installs...again HS-USB error.
See enclosed.
try run sutl with viewpad in FTM mode that worked for me good luck
I have same problem before..n my solution is change back CWM with old ..mine to CWM 2.5.1..found that CWM 5.0.2.6 got problem with SUT L3..and everythind done successfully..as long u can still access ur Viewpad to change CWM its ok..
Wow! Thanks so much for your reply! This would be a huge help. Any idea where I might be able to find that older version of CWM?
Alleycatzero you're a genius! Running SUTL in FTM mode has done it!
THANK YOU!!!!!!!!!!!!!!!!!!!!!!
Johnster25 said:
Wow! Thanks so much for your reply! This would be a huge help. Any idea where I might be able to find that older version of CWM?
Click to expand...
Click to collapse
This is under the Development section - just d/l and unpack the zip file, copy to mSD card & follow the instructions. This verison should be the earlier one and I personally find it worked best together with ext3 and/or ext4 partitioning as needed.
http://forum.xda-developers.com/showthread.php?t=1015005
The issues with SUTL3 and other apps not working/running has to do with the usb drivers not auto-installing & running as they should, try to uninstall Vpad7 drivers, reboot the PC - turn off any firewall and anti-virus software, connect the Vpad7 and let it finish installing/rebooting both devices again. Then, turn back on antivirus & firewall so that you will have easier time flashing rom, connecting mSD card & copying/moving files, etc.
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
Have a Sprint TP2. Had Android running off my SD card last year and ready to try it again. My main computer is Win 7 64-bit, but I have access to other computers with Win 7 32-bit, and possibly another with XP if it is necessary.
-----------8<------------------
A few questions, if you please.
-----------8<------------------
I) To get a *complete* backup of my phone, I can use SPB Backup, right? (Will allow me to get *everything* back the way it is right now?)
II) Recommended Android ROMs are OMGB and GBX0*?
III) For OMBG:
.....1) I need to have ADB working (I installed it last night)
.....2) The readme said I needed to "have all the drivers installed". I don't know what that means.
.....3) The "How-To" also said I "must have Fastboot working".
.......a) Where do I get this? From here?
.......b) Is it difficult to install and/or run?
.......c) Found this, but no idea what it means
IV) For GBX0*, I need to download and install ClockworkMod Recovery. Where do I get this? From here?
You'll need the same things for Android NAND. They both require fastboot, and some sort of recovery. I prefer CWM.
Edit - Your links are pretty much all wrong. You should be getting pretty much everything from here.
Use whatever ROM you desire. Fastboot and CWM are agnostic to ROM.
For any NAND ROM to work, you need adb working. If adb works, fastboot *should* work.
Fastboot flashes from the NBH. If you flash the NBH for Android, you have fastboot (installed on the phone...)
It is a little difficult/tricky. Not for the feint of heart. Read a lot, test a lot, before you flash anything. Make sure you know the process and what you need to do.
Most importantly perhaps is a fully charged battery. I've seen a few users get stuck in fastboot mode because they let their battery die - and now without CWM or WinMo, the phone won't charge. Don't want to be in that situation.
If battery life is most important to you then OMGB is the way to go. If you need native tethering then GBX is the way to go. I use GBX as my daily. Either way read the threads, and you can see the features that work on either.
I am trying to get my Rhod 250 prepped. I have the flash program to unlock the Hard-SPL but the phone will not connect via USB and I am fairly certain attempting a flash over Bluetooth would brick the phone. I have tried disabling Advanced Network Functionality and have also tried installing the .cab file found in another thread but neither have made a difference. I am running Windows 7 64-bit Ultimate, and the Rhod is showing up as Unknown USB Device.
bigspoondude said:
I am trying to get my Rhod 250 prepped. I have the flash program to unlock the Hard-SPL but the phone will not connect via USB and I am fairly certain attempting a flash over Bluetooth would brick the phone. I have tried disabling Advanced Network Functionality and have also tried installing the .cab file found in another thread but neither have made a difference. I am running Windows 7 64-bit Ultimate, and the Rhod is showing up as Unknown USB Device.
Click to expand...
Click to collapse
Please make sure ADB works before you flash anything.
You need to do the unlock before you can flash any unsigned images regardless. HSPL is the first thing before flashing anything - custom WinMo ROM or Android.
Hey guys,
a friend's Galaxy S2 (GT-i9100) hangs in a boot loop after updating Android (she says). She asked my if i could rescue her photo's, contacts, etc...
Booting Phone to Download-Mode works, connecting then via USB Windows 8 device manager prints USB\DEVICE_DESCRIPTOR_FAILURE as Hardware-ID.
There's no custom ROM installed, the device is not rooted and there's no CWM installed.
In Download mode, there's no option to "apply update from external sd card".
Tried "wipe cache partition", still boot loop.
Any ideas?!
EDIT:
I've tried to use/install various drivers. But IMHO if there's no Hardware ID / Vendor ID in the Windows Device Manager, Windows can't decide which driver matches for this device. So, if there's no device driver loaded, there's no chance for Odin or adb?! Correct me if I'm wrong.
Same as everyone else who's trying to do an Odin flash & having problems; Hopper8's 'Odin troubleshooting' thread stickied in General - go through the troubleshooting steps methodically (pay particular attention to the ones that relate to connectivity as that's the problem you're obviously having). Don't be surprised if your only option is to use another PC though given previous instances like yours I've seen.
Also, why would there be an option to 'update from external sd card in download mode ? You seem to be confused between it & recovery.
Download mode is very 'low level'; the only option you have is to get a stock rom from Samfirmware & flash it with Odin. This may/may not fix the problem. If it does, no data will be lost. But it's quite possible you may need to do a factory reset after the flash to fix, or even in some cases, flash the 3 part firmware linked in the thread I mentioned - in both cases this will wipe the phone.
Yes, you're right, i've mixed up Download & Recovery Mode. But i hope you know what my problem is.
Tried these steps (although another laptop using Windows 7), but no success.
I have another GT-i9100 which is successfully recognized by Windows 7 & 8 using Odin v1.85.
Is here any chance to extract / backup the user data from the device?
Btw:
If I boot it in Reocvery Mode, and choose "apply update from sdcard", it's possible to browse through /storage/sdcard0. It's soo depressing to see the user data and have no chance to backup them :silly:
Unless you either get a stock rom on the phone or get the phone & PC to connect to each other so you can maybe use ADB to pull the data, you have no other way to access that data.
If after trying everything in that thread for a day or two & you still have no joy, I'd be looking at replacing the USB board in the phone (you mentioning another I9100 can connect to the same machine just fine makes me suspect this might be the cause). This is a more & more common fault with the I9100 as the period since it was released increases, and this will absolutely cause the connectivity issues you're seeing. Unfortunately, you don't really have a way to test for this definitively, best you can do is replace it & see if if works.
However, fortunately, this is easy & cheap (~US$10) to do yourself. If you decide to go down this path, search for KeithRoss39's guide in General (search for 'replacing USB charger board'/similar). This guide has all the info you need to get it done painlessly.
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.