Q&A for Motorola Xt615 Motoluxe Miui Rom 2014
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Motorola Xt615 Motoluxe Miui Rom 2014. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
facebook not working!!
i solve
siemensserbia said:
I have created for old Motoluxe i use this rom based on stock 2.3.7 chinese rom and some parts from Relentless and other devices like Motorola Deffy.
It have pure MIUI launcher,QiucPic for images,Miui File Explorer,Miui like Music player with Cloud Play,Droid Flashlight,Modded 90% apps,Miui Status Bar with switches used from Enox rom theme.Dialer from one chinese custom rom and messaging app.Superuser,Odexed and prerooted.
Everything is working very well after install you have about 300-320 mb free on internal space and about 230-250 free ram.
I have removed.
Calendar sync.
Google Backup Transport
Stock Gallery
Other Motorolla junk.
Some ringtones and notifications(addes miui ui tones)
Flash with CWM recovery 6,0,3,2(by enox)recommended
You can get it here:
http://forum.xda-developers.com/showthread.php?t=2067510
First you must flash stock rom before you flash this one,reboot to recovery using recovery loader wipe dalvik,user data,cache and recommended to format system,data and cache.
Firmware/stock rom:
https://docs.google.com/open?id=0ByCIX_JAOmPeeGN2Vk9fM0h6TTQ
Motorola RSD stock flasher:
https://docs.google.com/open?id=0ByCIX_JAOmPeODBFcTBhS3gzWE0
To flash turn off phone and hold vol down + camera turn on then connect to pc.
Select firmware in RSD Lite and Flash.
Motorola drivers can be downloaded here:
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Then select instal from sd find zip and flash this rom.
If you get into boot loop turn off phone,hold vol up/down power then wipe data/cache again.
I will make my disclaimers: I m not responsible for anything that goes wrong on your phone. You yourself are responsible for it
Download Link(HIT THANKS!):
4Shared
http://www.4shared.com/zip/_TL30Hmqce/XT615MIUIbySiemensSerbia.html
Google Drive
https://drive.google.com/file/d/0B1Gwsoie8xLoeXVkUVRfaUo0T2c/view?usp=sharing
ScreenShots:
Click to expand...
Click to collapse
i install the rom evrything was right
but when dowload Facebook from play store and open it said
error open Facebook
this versión of android is no longer supported update the device and try again can fix it or help me please
thanks in advance:good:
basic question?
Hello, thank you in advance for what you did and probably helping me,
I didn't understand the firsts steps to flash my xt615...
I first installed drivers you give (on a win 8)
I understood i had to first flash with RSD Lite, having booted the phone with vol- and photo buttons pushed (which led me to a red screen with small text...)
which i tried, but RSD Lite don't seem to see my phone, i can only select rom an do nothing.
you say to "reboot to recovery using recovery loader wipe dalvik,user data,cache and recommended to format system,data and cache."
but what loader is it? no link for that one? can't find how to do it
i suggest you edit your post with basic step by step explanation for newbies to modding phones such as me
thx again
I think I finally understood, but still I got stuck...
ok, so...
as far as I understood, I simply have to:
1 DL clockworkmod
2 plug phone to computer, enable usb-debbuging
3 launch ~.bat file from clockworkmod, follow on-screen instructions...
4 reboot and do the cleanings you advice
5 unplug phone
6 reboot with red screen (vol down + camera + power button)
7 plug back phone and use RSD Lite (which detects the phone) and select ~.sbm file to flash stock rom
etc...
I now get stuck a step 7...
RSD Lite just don't detect my phone so I can't flash stock rom...
(i'm on win 8.1 and I did just as above) (+ when i was proposed to root while rebooting clockworkmod I accepted...)
So now my phone as no OS and just won't boot anymore...
any workaround? ( I tried installing Motorola Device Manager with win 7 compatibility mode, same thing...)
ps: tomorrow i'll try, on a real win 7, to flash stock rom, and post here my results
pps: i suggest you put something like these step by step explanations if they are correct, it seems easier to understand and follow
ppps: anyway thank you for you job again
Windows 8.1 not supported!
I managed to complete this guide today, on another laptop, with windows 7.
Conclusion: Motorola Device Manager is not compatible with Win 8.1 at the moment.
I give a thx
i install the rom evrything was right
but when dowload Facebook from play store and open it said
error open Facebook
this versión of android is no longer supported update the device and try again can fix it or help me please
New Facebook apk wont work with older based devices like 2.1/2.3.6/2.3.7 like Motoluxe.Instead try using Facebook Lite apk from Facebook developers.
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
Hallo everyone.
I have just tried to follow this guide to install Google Play and so on: http://forum.xda-developers.com/showthread.php?t=2256075
Guide:
I'm here for help you, and yes I bought K900
Here is the international .inb file to flash.
Part One: How flash international version:
1. create SDFUSE folder in the / of sdcard.
2. insert inb file there
3. go to fastboot mode (Vol+ + Power) and choose sdfuseupdate
4. done.
you'll get official international 47 rom (ROW region). It has google apps, it has play store.
INB file is here:
https://mega.co.nz/#F!xNdywAJA!AFbE_HikuoFODLpoc1j7Yg
But right after the message saying SDCARD UPDATE COMPLETED (as i remember it), the phone wont start again. The three buttons on the front flashes and nothing else happens.
Any clues to what might be the problem?
I hope you can help me!
Best regard
Jonas Kristiansen
Question
Hi Jonas,
Sorry to hear that.
Did you totally brick your phone? Can you still go into recovery or Hboot?
Is your phone recognized by adb and fastboot?
If you tell me more, maybe I can help.
Denis
Jonas Kristiansen said:
Hallo everyone.
I have just tried to follow this guide to install Google Play and so on: http://forum.xda-developers.com/showthread.php?t=2256075
Guide:
I'm here for help you, and yes I bought K900
Here is the international .inb file to flash.
Part One: How flash international version:
1. create SDFUSE folder in the / of sdcard.
2. insert inb file there
3. go to fastboot mode (Vol+ + Power) and choose sdfuseupdate
4. done.
you'll get official international 47 rom (ROW region). It has google apps, it has play store.
INB file is here:
https://mega.co.nz/#F!xNdywAJA!AFbE_HikuoFODLpoc1j7Yg
But right after the message saying SDCARD UPDATE COMPLETED (as i remember it), the phone wont start again. The three buttons on the front flashes and nothing else happens.
Any clues to what might be the problem?
I hope you can help me!
Best regard
Jonas Kristiansen
Click to expand...
Click to collapse
Same problem
Hello
I have same problem, i brick my K900. I try to start it, but phone is really little ignorant, absolutly not response to all. Flash using xFSTK is without chance.
Yep, Recovery and DroidBoot is unavilable. Phone only one flash touch buttons and nothing more... :crying:
Can you help me? I thing, hard-brick is too hard to solve.
Sorry for my english...
Maybe it will be usefull:
Volume down, hold it, then power button, Testing Menu appear, Droidboot, Recovery, Clear cache, Clear data (factory reset), reboot.
how unbrick ur k900 device
Jonas Kristiansen said:
Hallo everyone.
I have just tried to follow this guide to install Google Play and so on: http://forum.xda-developers.com/showthread.php?t=2256075
Guide:
I'm here for help you, and yes I bought K900
Here is the international .inb file to flash.
Part One: How flash international version:
1. create SDFUSE folder in the / of sdcard.
2. insert inb file there
3. go to fastboot mode (Vol+ + Power) and choose sdfuseupdate
4. done.
you'll get official international 47 rom (ROW region). It has google apps, it has play store.
INB file is here:
https://mega.co.nz/#F!xNdywAJA!AFbE_HikuoFODLpoc1j7Yg
But right after the message saying SDCARD UPDATE COMPLETED (as i remember it), the phone wont start again. The three buttons on the front flashes and nothing else happens.
Any clues to what might be the problem?
I hope you can help me!
Best regard
Jonas Kristiansen
Click to expand...
Click to collapse
(my english is veryyyyyyyyyy bad)
dont worry . there is a simple method :
this method work for hardbrick and softbrick too.
first download a favorite Rom you want
u can choice ur Rom from this page : http://m.kaskus.co.id/post/5300581ffbca17d47b8b457c#post5300581ffbca17d47b8b457c
download and install manufacturing flash tool and intel android device usb driver
https://dl.dropboxusercontent.com/u/26833962/K900 Tools/ManufacturingFlashTool_Setup_6.0.2.exe
http://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices
second Refer this : http://forum.xda-developers.com/show...postcount=3245
This method require computer with driver and software installed and USB cable for sure
( unzip ur rom and open xml file on ur rom with manufacturing flash tool softwre)
maybe this video can help you too :
https://www.youtube.com/watch?v=BhvA_T694kw
This method works on my hardbrick device succeesfully
tatu63 said:
(my english is veryyyyyyyyyy bad)
dont worry . there is a simple method :
this method work for hardbrick and softbrick too.
first download a favorite Rom you want
u can choice ur Rom from this page : http://m.kaskus.co.id/post/5300581ffbca17d47b8b457c#post5300581ffbca17d47b8b457c
download and install manufacturing flash tool and intel android device usb driver
https://dl.dropboxusercontent.com/u/26833962/K900 Tools/ManufacturingFlashTool_Setup_6.0.2.exe
http://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices
second Refer this : http://forum.xda-developers.com/show...postcount=3245
This method require computer with driver and software installed and USB cable for sure
( unzip ur rom and open xml file on ur rom with manufacturing flash tool softwre)
maybe this video can help you too :
https://www.youtube.com/watch?v=BhvA_T694kw
This method works on my hardbrick device succeesfully
Click to expand...
Click to collapse
hi tatu63
Me too got my K900 bricked while updating Rom from MFT .
Its not starting anymore. Complete black screen no menu lights at all.
When i connect my phone to usb cable it shows this in MFT tool and hangs up
07/01/14 12:47:15.886 DEBUG : New Android device -> serial: MedfieldEC710F76 status: 0 port: 1
and
Q&A for [ROM] [GUIDE] Lenovo S820, stock multilanguage rom
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Hi! I found here a completly info about flashing my lenovo s820 but i can't find links for kitkat roms, please post recommended links for that. thanks!
help mee... lenovo s820
hye, can anyone help me :crying: , i cannot find any official rom that work on my lenovo s820.
after erroneously hard reset my phone without backup it's difficult to flash it back :crying: help me plss..
i already try :
S820_ROW_S119_130922.rar
S820_S141_130813.rar
S820_S137_130711.rar
S820_ROW_S124_140404
VIBEUI_V1.5_1420_3_ST_S820_NK_baralajbi
but still none working
Latest official ROW update, S222 :
Click to expand...
Click to collapse
zura adler said:
hye, can anyone help me :crying: , i cannot find any official rom that work on my lenovo s820.
after erroneously hard reset my phone without backup it's difficult to flash it back :crying: help me plss..
i already try :
S820_ROW_S119_130922.rar
S820_S141_130813.rar
S820_S137_130711.rar
S820_ROW_S124_140404
VIBEUI_V1.5_1420_3_ST_S820_NK_baralajbi
but still none working
Click to expand...
Click to collapse
look here : http://www.needrom.com/category/lenovo/serial-s/s820/
Worked for ROW S820 too , just have to turn to CN firmware, flash CWM_CN_recovery and all roms available for you
Convert CN to ROW
Hello!
I am very new on this and I am a littlebit affraid to brick my phone. I have a china version of S820 with VIBEROM_V1.0_1340_3_ST_S820 rom (unrooted) and I would like to have the ROW version to get the latest updates. I missed the info from your post that does the phone has to be rooted before converting from CN to ROW? Sorry for the basic question but it is not clear for me.
Ps: none of the rooting tool worked on this current... khm... "nice" version (Framaroot, kingroot, etc....), probably those are only for ROW version.
Thanks for your help!
Problem with bootloader, fastboot, recovery menu
Hello everyone.
I am trying to get into the bootloader, so i will be able to use fastboot commands.
Prior to post here i made a thread in the [HELP THREAD] but unfortunately since the person that tried to help me did not had this device, he couldn’t help me, thus i’m posting here
So, first i tried to get into the bootloader by pressing the physical keys:
if power button and both volume keys are pressed i get into Android System Recovery(3e).
if power button and volume down key are pressed i get into meta mode.
if power button and volume up key are pressed i get into factory mode, which is entirly in chinese.
in all 3 occations, fastboot devices command did not reply anything….
Now the device is recognized by adb (i made the udev rule for it), all commands are working as should except one.
all except one: “adb reboot-bootloader” or “adb reboot bootloader” or “adb reboot fastboot” do not do anything. they just reboot the device into android os.
even “adb reboot recovery” works correctly…
Lenovo S820 is a new device. it was released in 2013, is it possible that it doesn’t have proper fastboot mode???
What should i do?
P.S.
Android system recovery <3e> options are:
reboot system now
apply update from ADB
apply update from sdcard
apply update from sdcard2
apply update from cache
wipe data/factory reset
wipe cache partition
in Meta mode just get this: Have been in meta mode, long press the power button and the normal boot.
factory mode (which is completely in english) has 8 options.
Lenovo S820 8GB Single SIM
I have a single SIM card Lenovo S820 8GB and I want to flash it.
I have two questions:
1. Is it necessary to use CWM or I can use TWRP?
2. Can I install any ROM without any worries for being single SIM? All the ROMs I have found are for dual SIM phones and I don't want troubles with my phone.
Thank you, and please answer.
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.
Hello my dear fellow community of XDA
I’m asking you for help, I found myself in a tough situation because I damaged system in tablet Nexus 9. Bootloader was already unlocked in my device when I bought it. I assume that the system was original. I didn’t notice any modifications. I damaged this system by uploading a file in a fastboot mode connected by ADB. This file is for rooting. I used this guide on the YouTube:
After doing everything step by step in this guide and switching my device on there was a sign of launching - vibration. The next thing I saw was white Google logo and after that the animation of loading appeared. It was loading without any success.
Before uploading the root file I also tried to upload TWRP file via ADB but it didn’t make any difference. After uploading TWRP files system launched properly, there is no new app in the app list and no combination of buttons such as power + volume that launches TWRP. Please tell me if I’m doing something wrong…
I tried to fix this bootloop by cleaning files via Hboot - factory reset but it didn’t change anything. I was searching for guides that would help me solve my problem but I couldn’t find anything useful. Each of them was old. They were from 2014 or 2015.
I would like to have a working tablet with TWRP, root and other unofficial system (you can give me some suggestions, I was thinking about Android 9). I don’t know where to start or what should I do first. Fix bootloop or upload TWRP ? What is correct order ? How to upload TWRP eligibly ? I rooted devices only several times so please excuse me, I am not a professional. I know that guide on YouTube mentioned before was for Android „L” not „N”.
Summary:
> Tablet Nexus 9 OP82100 WiFi version 32GB
> I use PC with Windows 10
> After connecting the tablet to the PC via USB cable in fastboot mode the tablet is visible in ADB console on the list of devices.
I hope that each information I gave you is clear enough. This is my first post on this forum. I hope somebody will find some minutes for reading this post. I’m counting on you. Thank you in advance for any help.
Ok, I honestly didn't read everything, but if you have and can access fastboot, flash TWRP, transfer a ROM to the internal memory, wipe data (not storage) and flash your ROM.
Try getting Wug's Nexus Root Toolkit, it's a graphical UI for adb and fastboot, might be a little friendlier for you.