yashsingh1/xdaforums huggingface dataset:
[G4] gazman86:
Well over a year ago I bought the MDA-Vario and back then promptly flashed the rom to remove T-Mobile default. I installed MR.Clean Rom, after a few months of medium usage I completely forgot about the device and never used it.

Found it again the other day and came back here so I could upgrade/flash it so I can use the device as SatNav on the latest rom/build.

I can confirm that my device is G4:

WIZARD SERVICE TOOL REPORT

Wizard Service Tool v4.2.2

13/07/08 18:24:16

CPU: Texas Instruments - OMAP850

MODEL: Wizard

IMEI: *************

=> Bootloaders:

IPL: 2.21.0001 (G4 device)

SPL: 2.21.0001 (G4 device)

Built on Mar 9 2006 at 13:52:14

Copyright (c) 2003 High Tech Computer Corporation

=> Firmware:

OS: 5.1.xxx (Build 14955.2.3.0)

ROM: 2.24

Registry AKU: .2.3.0

Radio: 02.25.11

Protocol: 4.1.13.12

=>Extended_ROM:

Version: 2.24a Mr. Clean

Name: Extended_ROM

Status: hidden

=> Drives and partitions:

|--Handle--|---Size---|

0e9e4332 - 9.99M (0x9fd800)

aea9c13a - 43.24M (0x2b3e000)

cfb25f96 - 50.95M (0x32f4000)

4fb25f42 - 2.94M (0x2f0000)

0fb25fba - 3.06M (0x30fc00)

=> DOC chip unique ID:

00000000f23102052b35008f13050698

Key Index: 57

Now, I am having great difficulty searching these forums because after not being around here for so long I don't even know what I'm searching for.

I have been reading different posts/guides since last night pretty thoroughly and I haven't gotten any closer to figuring out what I need to do etc.

I would like a fast/simple/clean G4 WM6 Rom, so far I have been unable to find one on these forums aswell (Why? Read the 2 previous paragraphs.. I honestly do not know what I'm looking for regarding compatibility with my device etc)

I understand I probably have to revert my rom to the T-Mobile original and start from there.

Please can somebody link me to the files I need, including roms/programs/guides.

Better still add me to MSN cr0sis at hot*mail d0t c0 d0t uk *(Not bothered about having this email listed publically, I never use it as email at all)*
[G4] zabardast_1:
Well,its not that hard to find what you are looking for,To upgrade read and follow either 'SoftSPL' or 'HardSPL' posted as stickies on the top of this thread.

To get a rom of your choice,look in the 'Wizard Mobile6' forum,all the latest custom build wm6 or 6.1 roms are safe for flashing a G4 phone.
[G4] gazman86:
I managed to figure out Shelltool (despite a ton of broken download links etc)

and successfully flashed TNT 19213. I was getting too many errors (on first boot "Timesomething not working" blah blah, then a lot of programs it claimed to have installed simply did not work (No icons in program viewer or anything).

Anyway, not here to complain about a specific rom not working, so I'll just get on with trying another. Shelltool seems to be the only working flash tool out there, and since last night I have tried a lot of different methods to the exact guide instructions.

I need to go through a list of the roms I can find which ARE successfully linked to still (Again, so many broken links on here it's unreal!). I'll report back when I've cracked it and got a rom I can actually use.

----

Ok, I ****ed up during a flash. Won't go into detail of how/what I did but basically, I need the original MDA-Vario Rom for T-Mobile or I can't continue, Anyone know a working link please??
[G4] Genesis3:
SoftSPL works. You do need a ROM that boots tho - if whatever you try to load DOESN'T boot you're screwed and left on the tricolor screen, and need an ORIGINAL load for that device (with the proper CID) to recover.

DO NOT screw around with loading things on a G4 unit without a proper CARRIER ORIGINAL firmware file you can use to recover with if something goes wrong.

Guess why I know this.....
[G4] gazman86:
Hehe Hmm, I wonder.

Well, yeah, I know this too now. But I wasn't screwing around I just had really bad luck because less than 20 seconds after starting shelltools I had a power surge followed by a brief power cut, effectively "Removing the USB cable during this operation" which of course we all know full well not to do :)

So I can use SoftSPL even when stuck in bootloader/RGB screen? I'll need a little help on how because I get "unable to copy files, try again?" dialogue. Gone into Activesync, told it not to accept USB connections, Killed activesyncs exe file in running processes in task manager and still no joy. Then again, do I really need to use SoftSPL if what I'm doing now is only putting on my carriers original rom (Yes, I found it.. Eventually! The rapishite links weren't working for me at the time, strange that suddenly they all started to late last night)
[G4] Genesis3:
No, you need to get a copy of a valid firmware file for the unit and carrier you have, and flash that - then, once you've done that and its running again, use SoftSPL again.

SoftSPL will NOT work from the tricolor screen.
[G4] gazman86:
Ok this is going to sound really dumb but:

Stuck in bootloader completely

I have my devices original rom

Extracted the nk.bf file

Ran shelltools, it froze

Ran RUU, Errors (Possibly wrong .dll version, I'm not sure?)

I am following all the wrong guides because not one is telling me how to flash when stuck in bootloader, with what program or version.

My head is fried
[G4] Genesis3:
If you have an ORIGINAL carrier ROM (which is an EXE, self-extracts and then runs the RUU that is in it) you can run that from the tri-color screen and it will flash successfully.

Don't try to extract anything or get cute with the carrier ROM - just run the loader (the EXE) and it should self-extract and execute.

You CANNOT flash a cooked rom from the tricolor screen on a G4 phone. It won't work - the loader will complain about being an invalid file or device and quit.

You need an ORIGINAL carrier ROM load for that phone - not a cooked one. Load it, go through the startup (screen cal, etc) and then use SoftSPL again.
[G4] gazman86:
Ok well I thought I had the correct original Rom for this device, but after 3 times trying to flash it to my device by just running the .exe I get

Error[294] Invalid Vender ID

This update cannot be used for your PDA phone. Please check your update utility

----

Nevermind, seems I was linked to the G3 version in a G4 thread. Goddamnit.

I can't find the G4 version so I'm going to try and flash Wizard_Love rom.
[G4] mestrini:
In the days of SoftSpl and HardSPL, messing with RAPI tools like Shelltool is really risky. You should have taken more time with the wikis and guides.

Now you must use an official RUU (from your provider) or you won't be able to recover your phone (since it's G4 and it's CID locked)
[G4] gazman86:
Ok Brightrom installed, no panic anymore :)

Easier than I was first led to believe after spending a little more time figuring out the guides.
[G4] mestrini:
THUMBS UP :D
[G4] gazman86:
And today after a greatly anticipated arrival of my new miniSD card, my device completely destroyed it! I switched off the wizard, plugged the card in, switched on, noticed the card was really hot within a matter of seconds.. card wasn't readable in the Wizard/PC/Card reader/Digital Camera/Second phone...

I already stuck it in my Card reader after unpacking it just to be sure it was working...

:(

Anyway, I'll buy two more lol. Could just be that I bought a ****ty card.

Anyone know where to get the latest TomTom + UK map?
[Xiaomi Mi 8 Questions & Answers] to-bu:
Hi

I'm on a MI 8 global version with the latest miui (dipper_global_images_V11.0.3.0.QEAMIXM_20200118.0000.00_10.0_global_515bcbba58). I unlocked the phone, did a clean install (flash_all) and now i try to get twrp to work. So i went back to fastboot mode, run the commands:

fastboot flash recovery twrp-3.3.1-1-dipper.img
Sending 'recovery' (42044 KB) OKAY [ 1.166s]
Writing 'recovery' OKAY [ 0.121s]
Finished. Total time: 1.292s
fastboot boot twrp-3.3.1-1-dipper.img
Sending 'boot.img' (42044 KB) OKAY [ 1.134s]
Booting OKAY [ 0.064s]
Finished. Total time: 1.234s

and then... nothing. It reboots to android... next try flashing and manual reboot by holding power + volume up in fastboot mode until it vibrates and the mi logo is shown. Two seconds later the screen goes black, the device (seems to) reboot and android again.

Next try was a different image (using the lineage custom recovery)... same result. And if i try to boot to recovery when the device was off with power + volume up the original recovery is shown....

I'm out of ideas.
[Xiaomi Mi 8 Questions & Answers] tsongming:
Obviously, you did something wrong.

Try renaming the recovery that you downloaded to "recovery" with no quotation marks

Place the file in the platform tools directory

For example: C:\Android\platform-tools\

Then use these commands.

fastboot flash recovery recovery.img

fastboot boot recovery.img

The commands above will flash the recovery.image to the recovery partition, then reboot then phone to recovery, you will then need to flash root.

If that doesn't work just use the Tool all in One
[Xiaomi Mi 8 Questions & Answers] to-bu:
It seems that i "holding it wrong" but in fact it doesn't work eather.

I'm original on linux but to ensure that it's working i switched to the windows system:

* downloaded and installed "Tool all in One"

* choose correct device

* ensure device allows ADB Access to PC

* ensure unlock status in tool

* use "Recovery Flasher and Rooter"

* selected "TWRP 3.3.1 mauronofrio XMI8" with "Automatic TWRP MD5 Check" and "And boot it" options

* flashed... and nothing again....

So i downloaded the and unpacked "dipper_global_images_V11.0.3.0.QEAMIXM_20200118.0000.00_10.0_global" to C:\ and used the "Flash Factory Images" to reset the device to a clean state (again.) After the flash and the automatic reboot of the device i went manual Fastboot mode and repeat "Recovery Flasher and Device Router"... with the same result....

So definitly something is wrong
[Xiaomi Mi 8 Questions & Answers] tsongming:
Are you sure that you have developer options setup? ADB debugging is enabled?

If you plan on staying on the stock rom that you are currently using you may need to flash DM verity. personally I prefer to use Orange Fox because it has DM verity built in.

once you are finally successful flash TWRP you might consider switching it. But be warned the layout takes some getting used to.

The latest Orange Fox is here: https://files.orangefox.tech/OrangeFox-Beta/dipper/OrangeFox-R10.1_002-Beta-dipper.zip

Worst case scenario; If you are located in the US, I can do it for you. ( just send me a PM if you want me to do it)

I have provided this service for a lot of people, you pay shipping and buy me a beer. This will take no more than 10 minutes.

If that is not an option:

A lot of people have trouble flashing TWRP, so dont get discouraged. After flashing recovery you must immediately boot to recovery and flash root then choose reboot to recovery. You may see check boxes asking to install TWRP manager, choose yes and reboot to TWRP.

A Lot of times when things fail it is due to some silly such as forgetting to rename the file to twrp or recovery when your adb command looks like this: 1. fastboot flash recovery recovery.img or 2. fastboot flash recovery twrp.img my guess that this is your issue or its developer options not setup correctly. Again : ADB debugging must be enabled?

If your phone doesn't reboot in TWRP it may be overwritten by the ROM's recovery.

Unplug Your phone then Manually boot it into recovery

PS: Welcome to XDA, good manners when someone takes their time helping is to give thanks by clicking the thanks button. Don't say thanks click the button. See the signature. good luck.
[Xiaomi Mi 8 Questions & Answers] to-bu:
Hi,

Yes, I am. This is not the first time i switched to lineage /cyanogen mod. I already customized a Nexus 4 (mako), Motorola Moto G (falcon), Samsung Galaxy S4 (jfltexx), Samsung Galaxy Tab S2 (gts210vewifi)

and LG V20 (h990ds). So I'm not new to this.

I see this in this subsection and i marked it already, since you suggest it i will try it as soon the flashing is working.

Sorry, Germany :D

I don't see the point why the image must have a name with only characters, but i renamed the image to twrp.img and tried:

In Android with developer options enabled (and pc allowed):

adb reboot fastboot

Now i'm in fastboot and using my zsh on linux, im on my home directory located the twrp.img:

~ fastboot flash recovery twrp.img
Sending 'recovery' (42044 KB) OKAY [ 1.279s]
Writing 'recovery' OKAY [ 0.118s]
Finished. Total time: 1.402s

Now the command to upload and boot to the same image:

~ fastboot boot twrp.img
Sending 'boot.img' (42044 KB) OKAY [ 1.236s]
Booting OKAY [ 0.067s]
Finished. Total time: 1.341s

On device: bank screen (about 5 sec) > mi logo with unlocked symbol/text (about 3 sec) > mi logo with android symbol/text/animation (again about 3 sec) => I'm back on android.

Second try manual:

adb reboot fastboot

Flashing...

~ fastboot flash recovery twrp.img
Sending 'recovery' (42044 KB) OKAY [ 1.248s]
Writing 'recovery' OKAY [ 0.107s]
Finished. Total time: 1.360s

Unplug the phone, pressing now together VOLUME-UP and POWER until device going black and mi logo showing and devices vibrates. => mi logo with android symbol/text/animation (again about 3 sec) => I'm back on android.
[Xiaomi Mi 8 Questions & Answers] dojabato:
Similar issue

I have the exact same issue. Did you manage to find a solution?
[Xiaomi Mi 8 Questions & Answers] to-bu:
Sorry for the REALLY LATE REPLY. But no..... nothing worked... currently i also don't try either.
[Xiaomi Mi 8 Questions & Answers] ogh1979:
I found the solution

Hello,

I was in the same case like you, to resolve this issue you must install this TWRP : TWRP-3.3.1-1031-XIAOMI8-Q+Version-CN

Sorry I'm new and can't post links...

I installed with the TOOL ALL IN ON => Erase all data => recovery flasher (check only automatic TWRP...) => POWER+Volume down => POWER+Volume up very quickly => Enjoy it !
[Xiaomi Mi 9 SE Questions & Answers] vmlc:
Well, already tried global and xiaomi.eu dev and they both are bad at battery duration.

Anyone can advice a better ROM?
[Xiaomi Mi 9 SE Questions & Answers] zgfg:
Debloat by ADB
[Xiaomi Mi 9 SE Questions & Answers] kagazushi:
The best is Bliss. Next build will be official and you'll be able to download it from this website: https://blissroms.com/

You can test Derpfest too which is already official (OTA updates): https://derpfest.org/devices
[Xiaomi Mi 9 SE Questions & Answers] gabi4175:
you can try havoc too it's more battery friendly then xiaomi.eu roms
[Xiaomi Mi 9 SE Questions & Answers] tomgougoutte:
Hi,

Do you know if official blissrom have OTA update ?
[Xiaomi Mi 9 SE Questions & Answers] kagazushi:
Yes it does, and a very active dev. Derpfest too.
[Xiaomi Mi 9 SE Questions & Answers] kagazushi:
Bliss gives an AOSP experience and Derpfest is more like PixelExperience
[Xiaomi Mi 9 SE Questions & Answers] tomgougoutte:
Thanks ! ;)
[Xiaomi Mi 9 SE Questions & Answers] kagazushi:
You should wait tomorrow to flash Bliss, a new build is expected today with a lot of changes.
[OS Porting] Klais1407:
Tem como colocar nike run no sistema tizen ? Do Galaxy watch ?
[Android Q&A, Help & Troubleshooting] Deleted member 10679719:
Is it normal that my device don't have fastboot mode with key combinations?

Also adb reboot bootloader dont work...

EDIT: Device - Hisense STARADDICT 6 (L730) Android 6.0.1
[Android Q&A, Help & Troubleshooting] jeangraff30:
Before sending a question you have to send which device is
[Android Q&A, Help & Troubleshooting] Deleted member 10679719:
Done amigo!
[Android Q&A, Help & Troubleshooting] Deleted member 10689923:
Yup same problem is with me So last night i found a recovery.img File for my mobile and flash it via Twrp.

Then when i start it in recovery it was in fastboot mode.

Maybe there is same method of fastboot mode for ur device like mine device keep searching.
[Touch Diamond, MDA Compact IV General] net777:
What tool do you use to edit the register?
[Touch Diamond, MDA Compact IV General] pedmond:
Humm, I think it's called Search... Really, did you try it? It can answer all kinds of questions :p
[Samsung Galaxy S7 Edge Questions and Answers] sadlyken:
The curved screen is annoyed while gaming, is there any app that can cutout the display on two edges ?
[Samsung Galaxy S7 Edge Questions and Answers] shah22:
Yeah edges can be blocked by samsung app "Edge Touch" available in Good Lock, although you will need to manually enable/disable it when gaming. You can search it on apkmirror.
[Fire General] cozzysa:
Thanks for the guide, do you know if this also applies to Fire OS 6.3.1.5 ? as I have a fire 7 mustang version
[Fire General] _SWaTcH_:
At first start i connet the fire 7 with wifi and it makes a small update to 6.3.1.4 then i make a factory reset with stock recovery and i was back to 6.3.1.2

Try the factory reset :D if that dont work and you are still on 6.3.1.5, dont try this Guide i only test it with a 6.3.1.2 device!
[Fire General] cozzysa:
It's all good, followed your guide and I'm on lineage os now. Thanks again!
[Fire General] nimrodk3:
So just to understand, Cozzysa: you sis it with 6.3.1.5 ?
[Fire General] lucas.lop:
Hi, I try here, and I stooped in the step 4.6, the result is: No such file or directory.

What's wrong?

edit: I founded the error, in the step, please correct the folder temp to tmp.
[Fire General] _SWaTcH_:
Thanks! i edit it! if you find some other things tell me :D

Thats a good question
[Fire General] lucas.lop:
I try here with 6.3.1.5 and don't work. I'm with this problem too.
[Fire General] Michajin:
This guide will only work if you are on 6.3.1.2 or below.

MTK-su = Amazon Fire 7 2019 -- up to Fire OS 6.3.1.2 build 0002517050244 only

---------- Post added at 01:19 PM ---------- Previous post was at 01:10 PM ----------

---------- Post added at 01:22 PM ---------- Previous post was at 01:19 PM ----------

[MENTION=10687537]_SWaTcH_ [/MENTION]

You might want to give credit to "diplomatic" for his temp root and you should possibly change to links to their threads.

For example 14.1 has this right next to the link to download. "*** Please do NOT create any mirrors ***"

I would also recommend a note that any OS above 6.3.1.2 needs to have the hardware unlock and link them over to the over thread.

Very nice instructions though!
[Fire General] lucas.lop:
Is no way out for 6.3.1.5?
[Fire General] Michajin:
Go here for the hardware unlock method-

https://xdaforums.com/amazon-fire/orig-development/fire-7-2019-mustang-unbrick-downgrade-t3944365

Once you get into TWRP, you can install Lineage. You can put the lineage on your sdcard, or transfer to your download folder from a PC. You odnt have to use adb to push files. an easy way of transfering files is to use adblink from here...

https://xdaforums.com/fire-tv/themes-apps/adblink-v2-04-t3389826

Or when plugged in set it to file transfer and it would come up as a removable media on a computer.

follow the instructions from the 14.1 thread for install.
[Fire General] _SWaTcH_:
Im sorry that i miss the credit for diplomatic :silly:

I add note that you need to use the hardware method for Os version above 6.3.1.2 and add links to their threads.
[Fire General] cozzysa:
Yeah it worked perfectly with the hardware hack
[Fire General] _SWaTcH_:
So i think you have install TWRP and you only need to copy the files to your fire 7, Michajin post a other way:
[Fire General] DrGuns4Hands:
Worked then broke

Not sure what happened. Got everything installed booted into lineage 14.1 downloaded apps browsed the web etc. I went into the list of apps and turned off auto start on things I wasn't planning to use the tablet for. Mail, messages, etc to save on memory usage these devices don't seem to come with much to spare. Then held the power button, clicked restart and it never came back, doesn't respond on the power button. Not sure where I need to go from here.

Additional Info: I had to use the hardware method since reset to factory took me back to 6.3.1.5
[Fire General] Michajin:
Hold the power button for about 10 seconds to do a power off...

It is a known issue with 14.1 Lineage rom for this. Did you install the sod patch? Check out the 14.1 thread here.... Post #566

https://xdaforums.com/amazon-fire/orig-development/rom-lineage-14-1-t3957329/page57
[Fire General] DrGuns4Hands:
Not sure what sod means. I did hold down the power button for quite a while and the tablet wouldn't turn on, but I can't say for certain it was 10 seconds I'll have to try again when I get home. Perhaps this patch should be in the installation instructions here if this is a known issue?
[Fire General] Michajin:
Screen Of Death. You might have to pull the battery. The Developer who created the Rom has been unavailable, being custom roms expect bugs. Always good to look at the last few pages of any thread to know status and current issues. When the GGOW returns he will likely update the latest security patches and install the patches into the latest. Remember these are volunteers who have no obligation to do this. Some don't even accept donations.
[Fire General] DrGuns4Hands:
Thanks. This is my first time with a custom ROM. I got the tablet just to do chromecast control for my TV in the living room and realized quickly that Fire OS just felt to clunky to keep on the device. Guess I'll be learning how to do update patches since I think that lineage will still be the better solution overall. Any suggestion on where to look to understand how to do the updates? I followed this guide as a step by step assuming it would be the whole kit and kaboodle, so can't really say I understand what pieces I'd need to update or where to look to keep things up to date to the most stable version.
[Fire General] Michajin:
Right now mostly just the patch for the SOD issue. I have seen suddenly the Developer GGOW has updated one of his roms. So hopefully he is back and we can get the patch into the rom and update the base. The fire 7 (2019) is a newer device so should be good for a while. I hope he continues to support it, or another developer picks up the custom rom and continues it. The updates will come in the 14.1 thread. The patches are a little unusual when it comes to custom roms. But people volunteer their time to come up with solutions for their devices and share them. Without a Dev to update the ROM you have to make due. Follow the thread for 14.1 (Mustang) as i think most bugs will be fixed. Also there may be updates to newer versions of Lineage. I am a novice user who like to tinker, but i am a repair person by trade who enjoys the challenge of fixing things. I try to add my experiences to help where i can, to pay it forward.
[Fire General] DrGuns4Hands:
You were correct about disconnecting the battery to be able to get it to boot again. I took the opportunity to do a clean install. Updated TWRP and changed my gapps to the pico version, mini just takes too much ram. Finally I installed all of the SOD related fixes in the thread you posted. Things seem to be going well now. Much appreciated. I fall into the same category Novice to Roms and linux, but I can get around if I need to just takes some time. Used to be in the repair field my self, got my associates degree in automotive repair. Since then, I've stumbled into the industrial automation. I don't miss the grease, but I still love to tinker with and fix things.
[Fire General] glilly:
Worked great on Fire 7 9th Gen as of 5/3/2020

I just used this method to successfully install LineageOS on a new Fire 7 9th Gen and it worked great as of 5/3/2020. However, there were a few caveats to the instructions that I had to work around or diverged from with success and wanted to point out where I had issues or difficulties so anyone else may benefit from my experience.

Is it ok to share my issues and experiences here? If they've already been documented, I don't want to repeat.