Unable to downgrade ... Help - G1 Android Development

When i follow all of the sticked guides, and the ones in the announcements i keep ending up with the same screen..
I have tried this with 2 different sd cards, both 2gb scandisk ones. Followed the guides..
Here is what i have tried so far, even though its listed in the guides..
Formated sd card both trying through the usb cable on the phone, and on an sd card reader on xp. to FAT 32, with allocation of 4096 (might have mispelled the number), done this using both the built in format function gui, and the cmd way using /fs and /a parameters.
I've tried both the RC7 and the RC29 versions of the DREAIMG.nbh file, even tried renameing to dreaimg.nbh, dreaimg.NBH and DREAIMG.NBH.
When i hit cam key + power, i get the first screen with a RGB and white row, and then it loads the bootloader aka grey screen. And when it gets past the second stage of loading it, i get a red number 00028002 followed by a blue text, Not allow.
Now it throws me back to the RGBW screen, with the Serial0 text to me..
The text otherwise available to me on the rgbw screen is as follows.
DREA110 PVT 32B
HBOOT-0 95.0000
CPLD-4
RADIO-2.22.23.02
Sep 2 2008
My Phone :
Model number : T-Mobile G!
Firmware version : 1.6
Baseband version : 62.50SC.20.17H_2.22.23.02
Kernel Version : 2.6.20-00479-g3c7df37
android-bı[email protected] #19
Build Number : DMD64

have you tried using the internal recovery buttons of power + home?

Related

The Ultimate Guide to put Hero Builds and other Builds to your G1/Magic Android

The Ultimate Guide to put Hero Builds and other Builds to your G1/Magic Android Phones by hellogadgetman from Greece
or download from here for best structure and more
http://rapidshare.com/files/2522727..._Builds_and_other_Builds_to_your_G1_best.docx
for ROOTED Phones
I have no responsibility for mistakes and problems through this guide
1) Find your SPL and Radio Versions
• Radio
o Next you will want to confirm your Radio Baseband.
To Confirm this Press Menu - Settings - About Phone - Scroll down till you see Baseband version.
Compare the Baseband value to the value below to see if you are using the correct radio for your build or if you need to update.
o You will need 2.22.19.26I
• Currently there are three SPLs available. The G1 variant is the SPL that is installed in stock T-Mobile G1 phones. The Engineering variant is found in the Android Dev Phone 1. Finally, the HardSPL is a modification of the Engineering variant by cmonex, with additional hacker-friendly functionality.
• HardSPL
• VER: HSPL10.95.3000
• HardSPL is a modification of the Engineering SPL by cmonex. In addition to the functionality of the Engineering SPL, HardSPL also allows NBH files to be used without matching the CID (carrier ID) check.
• Engineering SPL
• VER: HBOOT-0.95.3000
• The Engineering SPL is a custom SPL installed in devices intended for Android development. It has existed since before the launch of the G1 and is now available to the general public as preinstalled on the Android Dev Phone 1.
• G1 Original SPL
• VER: HBOOT-0.95.0000
• This is the original SPL which is installed in a stock G1. It is easily distinguished by the "trademark" red-green-blue bootloader screen which appears in many HTC phones. This SPL does not support the fastboot protocol and thus will not allow the user to flash nand backup images.
2) Update the Radio to the Latest
• Download the Radio zip.
• http://android-roms.googlecode.com/files/ota-radio-2_22_19_26I.zip
• Rename it to "update.zip".
• Copy it to the root of your phone's SD card.
• Turn your phone off.
• Start up in recovery mode by holding Home and pressing Power.
• Press ALT+S to apply the update.
• Once the update is applied press Home+Back to reboot the phone. The Phone will start to boot up and then continue applying the update. Once this is completed the Recovery menu will ask you for the second time to reboot the phone via Home + Back
3) Update the SPL to the Latest
IF YOU HAVE ONE SD CARD:
• Upload new SPL on your microSD and rename to "update.zip"
• Reboot your phone into recovery mode. I ASSUME YOU MEAN HOLDING POWER AND HOME BUTTONS>>>RIGHT?
• THIS IS IMPORTANT (perform a nandroid backup, of course) APPLY THE UPDATE USING ALT-S..., and once complete DON'T DO ANYTHING.. read step 4.
• WITHOUT PRESSING ANY BUTTONS remove your microSD card from your phone, and plug it into your microSD card adapter/SD card reader
• Remove/rename the SPL update (to something other than "update.zip") and upload the update file of the build you are currently using onto your microSD card. Put your microSD card back in your phone AGAIN WITHOUT PUSHING ANY BUTTONS I KNOW THIS IS STUPID, BUT WE RENAME THE BUILD TO UPDATE.ZIP AS WELL
• Press Alt + x to go to the console. If your phone does not reboot automatically, press enter, type "reboot recovery", then press enter again.
• If you boot up in recovery, you have done everything correctly. Now APPLY THE UPDATE USING ALT-S, reboot, and you're done
4) Performing a NANDROID Backup
At this point you should backup your phone via NANDROID
1 Turn your phone off.
2 Hold Home, press Power button to boot into Recovery Mode
3 Press ALT+B to start the backup.
4 Once the backup has completed press Home + Back
Next your phone will reboot and load the OS, at this point you should copy the files your just backed up to your PC incase you need to recover your phone
1 Mount your SDCard to your PC
2 On your SDCard change to the nandroid/HT840GZ30985
3 Inside this folder you will see another folder the first 8 digits of this folder name is the date it was created in the YYYYMMDD format and the last four are the time.
4 Copy this entire folder to your PC and save it. As you make more backups to your phone repeat this process.
5) Format your sd card to Fat32 and Ext2/Ext3 Partitions
• Install the sdsplit executable to your phone. To so this, open the 'terminal' application / ADB Shell and type the following commands at the prompts:$ su
# cd /data
# wget http://64.105.21.209/bin/lib/droid/sdsplit
# chmod 555 sdsplit
# exit
• Decide the size of your FAT partition:
You should use one of two approaches to decide the size of your FAT partition. The first one involves simply directly deciding this size (i.e. I want a 5G FAT partition). In this case, the EXT2 partition will be the remainder of the card.
size_of_fat_partition = size
The second method is based upon the fact that you want to decide the size of the EXT2 partition and would like the FAT partition to be the remainder of the card. In this case, the size of the FAT partition will be based on the size of your sdcard and the size of the EXT2 partition that you want. Use this formula to calculate it:
size_of_sdcard - size_of_ext2_partition = size
So, if you have an 8GB sdcard and want 1GB of space for apps on your EXT2 partition, use 7000M for the FAT size.
No matter which method you use, you will need to specify either bytes (no parameter), kilobytes (K) or megabytes (M) . So, for a 5G partition would use a 5000M size parameter.
Note: The size parameter is currently case sensitive, use 7500M, not 7500m!
• Backup your SDCard onto your PC
Note: To figure out how much data (in K) you have on you FAT partition, you can type the following in your terminal / ADB Shell (the sdcard can not be mounted for this cmd to work):
$ du -s /sdcard
Note: to find out how much free space is left on your /data partition type (see available)
$ df /data
• Run sdsplit. Use the size from step 3 below (do not forget the "M" in size if you are specifying megabytes): (Note: you will need an internet connection on your phone for this step)
Note: If you are using the JF1.5 update, you should put a -nc at the end of the commands below since system configuration is not needed!
Non JF1.5 Build:
$ su
# /data/sdsplit -nd -fs size
# exit
JF1.5 Build:
$ su
# /data/sdsplit -nd -fs size -nc
# exit
Please, remember to record the output of this stage if you run into a problem. There will be a permanent record of it in, /data/sdsplit.log.
• Reboot your phone, via terminal:
reboot
• Restore your data from your PC to your Fat partition of your SDCard.
• You're done! You should have two partitions now on your sdcard. The FAT one mounted at /sdcard and the EXT2 one mounted at /system/sd.
6) Put the Cyanogen Recovery image 1.2
http://n0rp.chemlab.org/android/cm-recovery-1.2.img
To install raw image: copy it to your sdcard and run from a terminal:
flash_image recovery /sdcard/cm-recovery-1.2.img
It is suggested to fully shutdown the device and power it back up.
Check Recovery IMG by rebooting phone and pressing Home + Power to see the new Recovery IMG
If you have problems with a "no space on device" error, try using fastboot and erasing first:
fastboot erase recovery
fastboot flash recovery cm-recovery-1.3.1.img
7) Upload JACHero 2.2.3 or any other to sd card and rename them as update.zip
8)Last steps to finalize
• wipe
• run apps2sd from recovery image menu
• then run fix filesystems
• then run update.zip
• then run apps2sd from recovery image menu again
• then reboot
• when phone reboots, give it about a minute after the screen comes on and chose deny on swapper in SU permissions pop up.
• then go thru the setup for gmail and android..
• after you get logged in to everything, do your settings for backlight and whatever else,
• then go to programs and do the swapper settings -
• SWAPPER SETTING:
/system/sd/swapfile.swp
Change swapper size
i did 20mb / 32mb ( i think thats right )
• then reboot ( after Gmail has finished syncing your contacts )
• when it comes back up choose always allow on swapper ( in su permission popup )
• then do you market and flickr( disable wifi for a sec ) to accept the terms..
• then give it a few seconds, and in about 1 min the phone will be running faster like cupcake
Many thanks to JACHero,Cyanogen,Robpet2,Jesus Freke,Jon Pezz, xmoo, Haykuro, Stericson, dapro, The Dude, Darkrift, and many others!
very nice guide thank you...also very nice guide structure
gonna try this and see if i can really get this to run as fast as cupcake
Just a side note;
Http://twistedumbrella.googlepages.com/index.htm
The guide there has all the resources loaded to the site already and no longer requires you to have to use fastboot because the recovery there has restore built in.
pretty good guide...but this has nothing to do with porting builds -- only installing builds that have already been "ported"
porting (in the context you used it) means to change a build to work on another system / device:
http://en.wikipedia.org/wiki/Porting
also...Recovery 1.3.1 is the latest and greatest
cheers
alapapa said:
pretty good guide...but this has nothing to do with porting builds -- only installing builds that have already been "ported"
porting (in the context you used it) means to change a build to work on another system / device:
http://en.wikipedia.org/wiki/Porting
also...Recovery 1.3.1 is the latest and greatest
cheers
Click to expand...
Click to collapse
I know but 1.2 Cyanogen has Apps to sd and fix filesystems
alapapa said:
pretty good guide...but this has nothing to do with porting builds -- only installing builds that have already been "ported"
porting (in the context you used it) means to change a build to work on another system / device:
http://en.wikipedia.org/wiki/Porting
Click to expand...
Click to collapse
Yes, the title of this post is rather misleading. I was expecting a guide to porting. This is a well organized collection of instructions to prepare your phone for most modern builds, and will surely be useful to some, but the title should really be changed to better reflect the content of the post.
hellogadgetman said:
I know but 1.2 Cyanogen has Apps to sd and fix filesystems
Click to expand...
Click to collapse
1.3.1 does too, but much like fix_permissions its executed through concole instead of menu
If someone made the guide please post his thoughts
Thanks
Anyone or better None
thanx for your instructions!
and, is the Cyanogen Recovery Image the necessary part for flashing Hero roms on G1?
thanx again.
thanx for your instructions!
and, is the Cyanogen Recovery Image the necessary part for flashing Hero roms on G1?
thanx again.
Very good, indeed.
EDIT:
What happens if you miss a step, but still able to flash the latest 2.3.5 hero rom? (Following these steps reduces the lag?)
That's what exactly what I did:
1. I already had the latest radio update (so I didn't bother downloading again)
2. I installed latest SPL, renamed it to "update" in my sd card, turn off phone, turn-on phone (HOME+END button), hit ALT+S.
(I don't have a SD card reader yet.....but I have another phone (T-Mobile Wing), I removed SD card from G1, put it in T-Mobile Wing, opened folder where SD card is, and deleted "update" (SPL file), rename the 2.3.5 HERO rom to "update", took SD card out of T-Mobile Wing, put it in my G1)
3. Turn on G1 (HOME + END), wipe (ALT+W), then flash (ALT+S)
(Waited until it installed new hero ROM, it was installed, then I went to swapper application and changed settings to " /system/sd/swap.swp "
That's it.
I already had partition my SD card before doing this update. I dont know if it's necessary to do it again.
My G1 is working, and I have 72MB free space in internal phone storage (so far).
My question is:
Do I need to follow these steps to make the rom work better? To allow my apps go to my SD card (like it was before).?
By the way, I installed the OVERCLOCKWIDGET app from market and it won't open. (Launch Error, "Overclockwidget (need root) could not be launched")
Any inputs would be greatly appreciated.
Then I wipe, flash new ROM.
ss1271 said:
thanx for your instructions!
and, is the Cyanogen Recovery Image the necessary part for flashing Hero roms on G1?
thanx again.
Click to expand...
Click to collapse
Yes if you want to be a fast Hero ROM
jay22are said:
very nice guide thank you...also very nice guide structure
gonna try this and see if i can really get this to run as fast as cupcake
Click to expand...
Click to collapse
if it is let me lnow to make the change to hero
FAILURE to install
I followed your guide exactly but when I was flashing the hero update an error came back
"E: Cant't chown/mod /system/xbin
(no such file or directory)
E:Failure at line 14:
set_perm_recursive 0 2000 0755 06755 SYSTEM.xbin
Installation aborted."
Any suggestions???
NVM. Problem fixed. had to download the following spl
https://www.digital-bit.ch/g1devel/6.0-spl-signed.zip
Alt+M (apps2sd option) isn't showing up in v1.3.1
Anyone have any idea why Alt+M (apps2sd option) isn't showing up in Cyanogen's Recovery Image when all the other options that were updated in 1.3.1 are?
twistedumbrella said:
1.3.1 does too, but much like fix_permissions its executed through concole instead of menu
Click to expand...
Click to collapse
Thats the reason I put in my guide the 1.2 Cyanogen recovery
DirectMatrix said:
Anyone have any idea why Alt+M (apps2sd option) isn't showing up in Cyanogen's Recovery Image when all the other options that were updated in 1.3.1 are?
Click to expand...
Click to collapse
app2sd is automatic in version 1.3.1, but that's for new apps installation.
All the hero roms (at least that i know) require not the recommended "HardSPL" but Haykuro's updated SPL
This guide is very misleading esp since you bascially c/p from the other posts.
Dont take it personally, but it really needs to be cleaned up
B-man007 said:
All the hero roms (at least that i know) require not the recommended "HardSPL" but Haykuro's updated SPL
This guide is very misleading esp since you bascially c/p from the other posts.
Dont take it personally, but it really needs to be cleaned up
Click to expand...
Click to collapse
But this is the point of somebody who has to read over 500 posts to understand to have all the things straight away.
I have used it and it is fine and some others also ...(over 100 downloads of the document)
Thanks

How to: CyanogenMod your G1 from scratch incl hardspl

for the t-mobile g1 with 1.6 firmware and some number stuff like drc92 and other G ones that won't cooperate..
to mod it from a stock (t-mobile nl) rom.
What u need :
1 sd-card (preferably more then 128mb)
1 pc running windows (i run win 7 ultimate)
1 usb cord
1 phone-internet connection (there is a wifi version too but since i find it not neccesary i wont link it. instead if you dont have phone internet : just download the packages on pc and put them in the G1)
1 app from market called : mybackup (you can use it for backing up contacts and stuff.. backup to sdcard and copy it to pc)
Backup
-download app MyBackup from the google marketplace and make a backup of programs and contacts (if you dont have phone-internet then get it from pc)
Preparing Gold Card:
- insert sd card into G1 and format it (whatever sd card and whatever format (there is only one on G1 hehe so go find it. also format is to be found in G1.)
- attach to pc and copy the RC7 image(DREAIMG.NBH) on the sd card in the G1 (do not detach from pc, i know you wanted to)
- goto appstore and download terminal emulator (as it says like that)
- open Terminal Emulator on G1
- type:
cat /sys/class/mmc_host/mmc1/mmc1:*/cid
- write down the code somewhere, its ur CID thingy
- push backbutton
Reverse the CID:
Begin: 1c5356555344202010051cc3b7008cf4
1c 53 56 55 53 44 20 20 10 05 1c c3 b7 00 8c f4 (yes i copied it from you thnx - normal code... add the spaces so your CID looks like this (your own CID not this one )
f4 8c 00 b7 c3 1c 05 10 20 20 44 53 55 56 53 1c - reversed one (note the couples are reversed)
00 8c 00 b7 c3 1c 05 10 20 20 44 53 55 56 53 1c - now change the first two digit to 00
so you will have something looking like this: 008c00b7c31c0510202044535556531c (this is example CID so use ur own!)
- goto revskills and get a goldcard image with the code ur having now. revskills page
- now get the mail and save the attachement in a dir
Making your Goldcard:
- right-click and open as admin Hxd editor
- in HxD editor :
- goto extra menu and open disk > choose psysical disk > ur sd card
- goto extra menu and open disk image > choose the received file from mail called : goldcard.img and press ok on the popup saying some about 512
- now go to this tab goldcard and goto topmenu and edit>choose select all and then topmenu again and copy
- now go to first tab (ur sdcard) and select 00000000 to 00000170 with mouse (mark it)
- goto top menu and select edit> write
- now goto top menu and save
- pull the G1 out of pc
- yes you can
- ok now pull the battery out (or shutdown if u have the time)
- press camera button+power so it will give this rainbow 3 color shizzle
- you see a gray screen saying some words you probably wanna read.
- now press power to confirm overwrite the rom thing
- reboot by holding the two phone buttons (hangup and answer)and press menu or home and back (im not sure but one of these work and you see something saying it updates some stuff.
(if this dont work in ur G1 (specially latest versions) you can use a sdhc usb cardreader or a windows mobile phone or anything else with direct disk acces mode , probably nokia and sony ericsson too)
on the next boot you will have the old RC7
(if you have no internet on phone you can skip the next 2 lines and download the package and copy it to the G1 (dont know where so if anyone can tell me it would be nice to help people out )
- fill in your google account stuff
- Download Android "Telnet" application from the Market.
- Download recovery.img and copy it to your SD card. rename it to recovery.img
- Download the Hard SPL and copy the zip file to the SD card. (this is for G1 drea110 htc dream only so be carefull as this stuff can ruin your phone)
- All files must be on the root of your SD card.
- turn off the phone and detach from the pc
Rooting your G1- RC7 phone:
On RC7 Rom and lower, anything you type into your keyboard is also being run in a hidden console with root permissions.
To get root access, do the following:
- Restart your phone. Wait for your phone to start up fully and show the home screen.
- Unlock it by pressing menu after you typed code for sim and it fully started ( it will auto-lock itself)
- Hit the enter key twice,(Yes, it will start up a contact search, so you can see what you type . aint it cool) type "telnetd" and press enter.
- start telnet application you downloaded before on G1 and connect to localhost. (if you dont see localhost and connect window you have wrong app or need to reboot another time). If you connect successfully, you will have a root prompt "#".
Type the following into Telnet (these commands will give you root access for now):
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd sdcard
flash_image recovery recovery.img
cat recovery.img > /system/recovery.img
Power off your phone by pressing send/hangup&menu together when its done.
Now you have the modified recovery and root !
Now that you have root and stuff, you will want to apply "Hard SPL" to your phone. HardSPL includes engineer SPL and is what will allow you to apply any rom image from any other regions
(like UK on US phones, UK on dutch and vice versa), create full backups of your phone, install the latest build from the Android source, enable usb on recovery mode, usually resurrect your phone if it is "bricked" and give you allways root and ability to flash another rom. Allows fastboot. Fastbooting of images allows the flashing of 1:1 images of system, data, boot, cache, pretty much everything.
You have already downloaded the file to your SD card, so now you can apply it.
-Start up in recovery mode by holding home and pressing power.
-You will now enter recovery mode. You should see an exclamation.
-If you do not see a menu on screen, press Alt-L to show the menu. It is supposed to show the modified recovery menu.
-select update from zip to apply the update.zip (hardspl) from the SD card.
-After the update is complete, hold Home and press Back to restart.
ok your G1 europe 1.6 or whatever version is now unlocked.
Installing your modded rom:
now download this europe rom (or here: link ) and this cyanogen update mod
(here are more roms: android-roms make sure you READ what is needed for this roms as these all need different recovey and things which are all nicely written to you in the help and readme files that come with it.)
- copy both files to root of the sd-card
- detach G1 and shut it down
- press home and start to get into the menu
- wipe device
- wipe cache
- install from zip the europe rom and do not reboot or anything else
- install cyanogenMod
- after it finish press both talk&hangup button and tap menu
- its probably giving the recovery menu . take out the battery and put it in and start the phone normally
- wait a long while for the phone to setup and i donno what the heck it needs to do but let it.
enjoy...
THnx to this greatfull forum-members like myself, moneytoo, amon ra, cyanogen, mark_v, persiansown who do this coz few others can and they have a sort of happy feeling doing it.
hi.
this isnt working for me. i used the hex editor to copy sections 00000000 to 00000170 from goldcard.img to my sdcard, then shut down and turned on phone with HOME+POWER, it "hangs" on phone with exclamation mark image. if i press home+power again i'm presented with default android recovery. i did put DREAMIMG.NBH to the root of my sdcard.
that means no confirming anything... what am i doing wrong then?
Seriously, use 1Clickroot.
maxisma said:
Seriously, use 1Clickroot.
Click to expand...
Click to collapse
1clickroot doesn't work with 1.6, does it?
greglord said:
1clickroot doesn't work with 1.6, does it?
Click to expand...
Click to collapse
The new should work in theory.. idk..
greglord said:
hi.
this isnt working for me. i used the hex editor to copy sections 00000000 to 00000170 from goldcard.img to my sdcard, then shut down and turned on phone with HOME+POWER, it "hangs" on phone with exclamation mark image. if i press home+power again i'm presented with default android recovery. i did put DREAMIMG.NBH to the root of my sdcard.
that means no confirming anything... what am i doing wrong then?
Click to expand...
Click to collapse
thats probably coz i mixed up buttons for starting the rainbowscreen updating mechanism.. sorry for that
i dont own or have a G1 so im not used to the button layout
edit: you can in that screen press Alt-L to get the menu , once u have the recovery.img installed it will change there to the menu of the modded recovery
maxisma said:
The new should work in theory.. idk..
Click to expand...
Click to collapse
i have no idea
but it might be handy to put a link to the file you mentioned instead of shouting it without researching the fact whether it works or not in 1.6
can anyone quickly tell me what the advantages of having the hard spl are? all iv done is rooted, (via 1 click) and then flashed cyanogens latest. radio was already up-to-date. just wondered if flashing new spl changes anything? many thanks
Hard SPL enables you to install roms like Hero or others that have a large "update".zip
bbuchacher said:
Hard SPL enables you to install roms like Hero or others that have a large "update".zip
Click to expand...
Click to collapse
Actually...The Haykuro SPL allows that...
Ace42 said:
Actually...The Haykuro SPL allows that...
Click to expand...
Click to collapse
Right. HardSPL (and DangerSPL) are something that allow fastboot. Fastbooting of images allows the flashing of 1:1 images of system, data, boot, cache, pretty much everything.
You should always have HardSPL/DangerSPL installed so you can fastboot a nandroid image as a worstcase scenario.
Jesus, the amount of noobiness is this thread is astounding.
persiansown said:
Right. HardSPL (and DangerSPL) are something that allow fastboot. Fastbooting of images allows the flashing of 1:1 images of system, data, boot, cache, pretty much everything.
You should always have HardSPL/DangerSPL installed so you can fastboot a nandroid image as a worstcase scenario.
Jesus, the amount of noobiness is this thread is astounding.
Click to expand...
Click to collapse
thnx for clearing that out
as i said i dont own a G1 i modded a friends one . so i dont know anything about this G1 but getting a new rom on it hehe.
i choose the hardspl as precaution and it seemed pretty stable from what i read.
i choose the 1.5 recovery as i thought it should have the same recovery image as the rom . dont know about that. it is the 1.4 recovery with some extras which are usefull, cant deny that.
i choose the rom as it seemed to be the most stable at the moment and allows thetering . this is why i needed to rom upgrade in the first place. second place that i just like modding and unlocking so that one can do everything with the device as it is yours anyway.
APEX.7 said:
can anyone quickly tell me what the advantages of having the hard spl are? all iv done is rooted, (via 1 click) and then flashed cyanogens latest. radio was already up-to-date. just wondered if flashing new spl changes anything? many thanks
Click to expand...
Click to collapse
it is allready answered in the how to ..
I can vouch for the OP tutorial working on the Australian Optus(Singtel) HTC Dreams wtih DRD20 build. Just waiting on that final epic long load up now.
Anacche said:
I can vouch for the OP tutorial working on the Australian Optus(Singtel) HTC Dreams wtih DRD20 build. Just waiting on that final epic long load up now.
Click to expand...
Click to collapse
I'm also G1 / 1.6 / DRD20 ... it's sounds good news for me ...
Hahahhahahh.....
this post should be named "The Most Difficult Way to Root your G1". How bout this.....downgrade to 1.5, DL one click root, and you're done.
Please help!!! Pleasee!
Do help me out on this one. I really can't seem to actually make my SD card into the gold card part. Whenever i plug it in the G1 or on a USB reader it tells me it's damage and needs to format.
i have two questions, Can i flash SPL first, then do a downgrade then flash recovery?
2nd : If i can't then can i flash recovery, flash spl then do a downgrade to RC7?
if so how do i flash my recovery?
DO HELP ME OUT PLEASEE! i've been on this for days!!!
I know that this is going to cause problems and fighting but, I cannot read this thread and not say anything in good conscious.
With the amount of errors and misinformation in this thread, perhaps the OP should leave the tutorials and how-to's to the people that actually HAVE a G1, have modified ROMs on their phone, and can support the questions that are asked in the thread.
Just my two cents, but I have a feeling that my words are supported judging from the general consensus of the previous posts.
~DM
DirectMatrix said:
I know that this is going to cause problems and fighting but, I cannot read this thread and not say anything in good conscious.
With the amount of errors and misinformation in this thread, perhaps the OP should leave the tutorials and how-to's to the people that actually HAVE a G1, have modified ROMs on their phone, and can support the questions that are asked in the thread.
Just my two cents, but I have a feeling that my words are supported judging from the general consensus of the previous posts.
~DM
Click to expand...
Click to collapse
Id have to second that, while I may not have many posts here on XDA,I've rooted and rebuilt and replaced screens from 7 G1's using the how to's and wiki's here on XDA(thanks devs). My thought is if it the current guides work we should prob stick with them unless someone else figures a better faster way.(ie;one click root). By the way,just wanna say,I've never charged anyone to root their phone or fix one. The knowledge I've gained I learned here,it wasn't something I developed and I think its wrong for people to take open knowledge they didn't come up with and charge other people for it like I've seen at some of these cell phone repair shops and on craigslist. If your gonna charge for the knowledge then pay the people you gained the knowledge from. Sorry for going off topic,just had to vent.

[Q] Qtek 8310

My phone is only three color mode, if i switch on. I try different rom upgrade but nothing. What i can do?
A little more information is needed:
What does the 3 color screen tell?
What happens if you execute a ROM update?
How do you try to make the ROM update, shipped ROM (which) or a cooked ROM (which)?
Has the device ever worked?
Which ROM was on the device before it got stuck in bootloader (3 color screen)?
Tri-color screen meant by bootloaderit (red, green, blue). When I try to update the ROM, it shows that it would be done, but the re-launch the bootloader all the time. Try a different ROM, which is designed for the HTC Qtek 8310 and the Tornado. WM6, WM61 and WM65. WM5 device worked before, more detailed version i dont know. letter on the screen IPL: 2.00 SPL: 2.00.0009
It seems that the loaded ROM does not succeed to load. If you load a shipped ROM everything outlined below should be done automatically for you, so if that does not work as well, then the device may be broken. So check first if you can load a shipped ROM again.
For cooked ROMs you need to prepare the BINFS to match the size of a ROM before you load it. As you succeed in loading any ROM, the device seems to be CID unlocked already. Check the following:
Connect the device in bootloader mode. Switch off, then keep camera button pressed and insert USB cable.
Disable USB for Active Sync (Connection settings of AS).
startup a terminal program that can connect via USB (e.g. TTerm pro)
connect ot the USB port
press enter
Command prompt appears
enter "info 2" (no quotes) enter
read the last line, it should give something like "HTC SuperCID". If not, then you must CID unlock the device first. Lookup the relevant threads for the cooked ROMs or search for Lokiwiz.
If the device is already SuperCID, then you must match the BINFS formatted size to be larger or equal the ROM size (OS partition). For most cooked ROMs it is the binary file size. Relevant actions are also described in some cooked ROM threads, e.g. mine - see my signature.
What is shipped ROM? Original Rom? I do not have it.
Tera Term
info 2
GetDeviceInfo=0x00000002
+ SD Controller init
- SD Controller init
+StorageInit
CMD55 failed
+ SD Controller init
- SD Controller init
+StorageInit
CMD55 failed
HTCSBPT_0501 Lqœ»HTCE
I try unlock SuperCID with program lokiwiz02b.
But nothing happend.
machinagod's HTC Wizard Unlocker v0.2
NOW WITH CID Unlocking POWER!
--------------------
WARNING: This tool is highly experimental!
I will NOT be held responsible for any problems caused by this tool.
--------------------
Thanks to xda-developers, spv-developers, and especially itsme by the work they
released. This solution would not be possible without them.
--------------------
U. Unlock
L. Lock
C. CID Unlock (SuperCID)
Q. Quit
--------------------
Type the letter and press Enter: c
CID unlocking mobile... DO NOT DISCONNECT UNTIL THE PHONE REBOOTS!
What i try next?
IF your OS is not up, then the lokiwiz will not do anything to your device!
With THIS status you should not succeed in doing any update or format your BINFS. You first need to get the original OS up and running again before you van get any further on changing your OS. The steps to take are:
Get old OS running up again
Application unlock the old OS
CID unlock the device (backup your *.bin files!)
load new OS
1.) is your problem currently. There are several ways to achieve this, try a hard-reset first, this should work for your device:
switch off device
press L+R softkey and hold both
switch on device and keep L+R softkey pressed
wait until prompt and act accordingly
device will reboot to OS
OK now?
I do not have the original OS or even the old OS. After a hard reset as well as the OS does not come up.
# Switch off the Device
# Softkey Press L + R and hold Both
# Switch the device and keep L + R softkey presses
Press 0 to restore factory default. Other key to exit
I press 0
After hard reset load the bootloader again.
OK, then you need to load the CID matching old OS via the shipped ROM standard procedure. Look to: http://www.shipped-roms.com/shipped/Tornado/ and get 8310_2090_253121_020900_to_dan_eur_ship.exe
Execute it on the PC while the device is connected in bootloader mode. If that does not work, then try other ROMs in the same directory until you succeed with the loading.
Mind that a first boot takes 3-5 minutes, so be patient if the bootloader is not coming up any longer. Also do not interrupt the ROM loading in the first steps when the upload has started. It is normal that there are phases where the progress bar does not move. I think the sequence is per partition (IPL, SPL, Splash, OS): load to RAM (bar progressing), load from RAM to ROM = flashing (no bar progress, but color change of bar at the end). The large OS partition is loaded at the end of the sequence so the second step will take some time - be patient.
Good luck!
I try all ROM's but always give me ERROR 294 INVALID VENDOR ID.
And now the phone does not start anymore. No picture. I dont know what happend
This seems to prove that the device has something broken.
Make sure that the battery gets charged while the device is off. Despite the device was connected to USB all the time there is no charging happening in bootloader mode. Wait until the green light is there again before you continue - power drain in bootloader mode is quite heavy.
When none of the shipped ROMs work for upload, it really gets hard to load back an OS running on that for further steps :-(
There is a procedure called "Gold Card method", the rough procedure is (only did that once years back - so this is no step-by-step guide):
Prepare the card so that the bootsector contains the magic device specific "Gold Card" signature. For that you need a trial version of PSAS, and a working windows mobile device(!).
then you would have to load the *.nbh file that gets uploaded to the device (and fails) to that mini-SD card root directory,
rename it to TORNIMG.NBH there
load the card to the device,
then reboot to bootloader (Camera + on)
and hope it gets it loaded
A detailed procedure is described for the Excalibur device but this works equally well for Tornado if you adjust the relevant parts (PSAS is the success of QMAT). Mind that the miniSD card should be in really good condition (fresh full format, check that the file loaded can be read byte-identical from it). If the loading from the card fails or corrupts the IPL/SPL while loading then your device is really bricked. It happened to me with an Excalibur (read the whole thread linked above) - so be extra careful (though - what do have to loose?)!

Half Bricked - How to install Custom ROM

Hi friends,
I'm Karthik, Bangalore, India. I've HTC HD7 - SIM Unlocked mobile.
1) Below are my mobile details,
Model: HTC HD7 T9292
Software: Windows ® Phone 7.5
OS Version: 7.10.8773.98
Radio Software Version: 5.71.09.02a_22.51.50.21U
Radio Hardware Version: A.102.0.D4
BootLoader Version: 5.12.2250.0(139198)
2) When i start in Bootloader mode, I get
PD29100 SS-BC (4K)
SPL-5.12.2250.0(139198) MNG
MicroP(LED) 0x07
TOUCH S1(v1.8,#1624)
SD SANDISK 15193MB
Partition Info-v211v413
F400
Nothing in White block. :crying:
3) I can enter into USB Host mode (Camera button+Volume+Power)
It says "Enter Usb host mode"
Please guide me in installing any Custom ROMS.
(My aim is Developer Unlock/Full Unlock )
Please don't give a negative reply. I'm tired of people saying, "NO, Your mobile is bricked, You can't install any Custom ROMS". Please leave a positive reply.
Regards
Karthikeyan
You need to use a GoldCard to safely flash an older bootloader (SPL) onto your device. Once you've done that, you'll be able to install HSPL, then flash a custom ROM.
There is lots of guidance for GoldCard on the Dev&Hacking sub-forum.
here are some guidances for your request:
http://forum.xda-developers.com/showthread.php?t=1295068
http://forum.xda-developers.com/showthread.php?t=1371073
Not working
Friends, Thanks for info.
I made the Y cable correctly.
Downloaded all files.
But my HD7 is not detecting the .nbh file. :crying:
Details of items i used :
RUU_Schubert_hTC_Asia_SEA_WWE_1.54.728.01_Radio_5.51.09.29_22.32.50.10_Signed_SCHUBERT_RELEASE.exe ( .nbh file)
goldcardtool.exe
8 GB pendrive (fat32)
Y cable made by my own (I'm damn sure i made it perfectly! :good
karthikeyan1990 said:
Friends, Thanks for info.
I made the Y cable correctly.
Downloaded all files.
But my HD7 is not detecting the .nbh file. :crying:
Details of items i used :
RUU_Schubert_hTC_Asia_SEA_WWE_1.54.728.01_Radio_5.51.09.29_22.32.50.10_Signed_SCHUBERT_RELEASE.exe ( .nbh file)
goldcardtool.exe
8 GB pendrive (fat32)
Y cable made by my own (I'm damn sure i made it perfectly! :good
Click to expand...
Click to collapse
jayjojayson, @GoodDayToDie, I tried with newly bought Y cable, Ne Memory card reader, New 2GB MicroSD (& used MicroSD to SD Adapter).. Now the new message is "Loading.. No image file!"
Finished Flashing and installed Deepshine
After hard work for 2 weeks!
:angel:
:victory:
Thanks to all helped me (already pressed Thanks button)
Details:
Downgraded using 16GB Transcend Pen Drive (Partitioned to 1GB)
RUU_Schubert_HTC_Europe_5.10.401.04_SLSPL_Signed_by_ansar
Y Cable - made by me
Time taken
Flashing: 8 min
RSPL and HSPL : 2 min
Deepshine installation : around 7 min
For starting these work : 2 weeks and 1 day
Thanks... Mmmmmmmmmuahhh to all who have directly and indirectly helped me!!!
What method did you used, I'm stuck, I'll try with pen drives but what method, Gold Card or Y-Cable?
karthikeyan1990 said:
After hard work for 2 weeks!
:angel:
:victory:
Thanks to all helped me (already pressed Thanks button)
Details:
Downgraded using 16GB Transcend Pen Drive (Partitioned to 1GB)
RUU_Schubert_HTC_Europe_5.10.401.04_SLSPL_Signed_by_ansar
Y Cable - made by me
Time taken
Flashing: 8 min
RSPL and HSPL : 2 min
Deepshine installation : around 7 min
For starting these work : 2 weeks and 1 day
Thanks... Mmmmmmmmmuahhh to all who have directly and indirectly helped me!!!
Click to expand...
Click to collapse
So it doesnt matter which country code u use?
U changed from 728 --> 401
I have the exact same problem as you
And which program did u use to partition a usb drive down to 1gb??
Thanks!~!

[Q] Help unbrick AMLogic aml8726-mx tablet

Hi, i want some help with unbricking an aml8726-mx tablet. It's Prestigio Multipad Prime Duo, 7" 1024x600 tablet with 16gb internal storage and micro-sd card slot. It has only Power and + - volume buttons.
I've bricked it by flashing official firmware with default recovery. Entered recovery, made wipe, than installed update.zip from sd card. Progress bar started to move, indicating what process is on the way. And than in about 20%(no real percentage was in that recovery) tablet first freezed and than turned off. From this point there was no reaction on buttons, no display(even no backlight) - nothing. Connecting it to PC made the power on light flashing every 1 second(i guess). No device found by PC. I've tried turning on with - and + pressed, with both, without pressing anything - no luck.
So it was deep brick. Later i have found some info about 5th and 6th pins on NAND chip inside tablet, if those pins are connected to each other, after turning on tablet will be discovered by PC as M6 device. That worked! After hours dancing around AML usb flashing tool i was able to boot some uboot on tablet, started some recovery(not on the screen, it's still black as night), connect to recovery with ADB and trying to flash BOOT, BOOTLOADER and RECOVERY.
What i've tried:
1)adb push boot.img, boot loader.img and recovery.img i get from official firmware for this tablet
2)to make sure what my files now exists on tablet. I've pushed them to /cache/ so
Code:
#cd /cache/
#ls
and ls told me what my .img files are there
3)tried to flash
Code:
#flash_image boot /cache/boot.img
#flash_image bootloader /cache/bootloader.img
#flash_image recovery /cache/recovery.img
And here is a problem - each of those command gave me that:
error scanning partitions exit with code -1
I can't flash bootloaders and recovery. I've googled for days and still dont get it - why that "partition scaning" errors and what should i try.
If anyone can help me with that, or is there some different method of flashing it - i will be highly appreciated. I've used this tablet for less than a week and now it's totally bricked what i can't bring it back to life.
Same issue
I have the exact same problem! Could anyone help please?
Futaba0rus said:
Hi, i want some help with unbricking an aml8726-mx tablet. It's Prestigio Multipad Prime Duo, 7" 1024x600 tablet with 16gb internal storage and micro-sd card slot. It has only Power and + - volume buttons.
I've bricked it by flashing official firmware with default recovery. Entered recovery, made wipe, than installed update.zip from sd card. Progress bar started to move, indicating what process is on the way. And than in about 20%(no real percentage was in that recovery) tablet first freezed and than turned off. From this point there was no reaction on buttons, no display(even no backlight) - nothing. Connecting it to PC made the power on light flashing every 1 second(i guess). No device found by PC. I've tried turning on with - and + pressed, with both, without pressing anything - no luck.
So it was deep brick. Later i have found some info about 5th and 6th pins on NAND chip inside tablet, if those pins are connected to each other, after turning on tablet will be discovered by PC as M6 device. That worked! After hours dancing around AML usb flashing tool i was able to boot some uboot on tablet, started some recovery(not on the screen, it's still black as night), connect to recovery with ADB and trying to flash BOOT, BOOTLOADER and RECOVERY.
What i've tried:
1)adb push boot.img, boot loader.img and recovery.img i get from official firmware for this tablet
2)to make sure what my files now exists on tablet. I've pushed them to /cache/ so
Code:
#cd /cache/
#ls
and ls told me what my .img files are there
3)tried to flash
Code:
#flash_image boot /cache/boot.img
#flash_image bootloader /cache/bootloader.img
#flash_image recovery /cache/recovery.img
And here is a problem - each of those command gave me that:
error scanning partitions exit with code -1
I can't flash bootloaders and recovery. I've googled for days and still dont get it - why that "partition scaning" errors and what should i try.
If anyone can help me with that, or is there some different method of flashing it - i will be highly appreciated. I've used this tablet for less than a week and now it's totally bricked what i can't bring it back to life.
Click to expand...
Click to collapse
bal2nis said:
I have the exact same problem! Could anyone help please?
Click to expand...
Click to collapse
Bump, anyone?
Futaba0rus said:
Bump, anyone?
Click to expand...
Click to collapse
Hi I have a sirius Nvsbl equals this model and also takes AML8726. Turns out my tablet is dead and the clearing to see if you can revive and has a pin GND, TX, RX and vcc and this gives me the idea that it is a port to relive problem is not with that program .. I guess with riff box can but I have this box I have several cables Nokia I'm sure it is compatible (DKU5) the problem is with software that can burn the boot?
Enviado desde mi GT-I9300 usando Tapatalk 2
I have exactly the same problem. I managed to flash it with Crystal batch 3 SW. Can acess shell thru adb, but the screen is black too.
I also have boot.img, recovery.img, factory.img, system, but I don't have the bootloader.
Once I flash it with the files mensioned above the tablet doesn't even boot and I have to shunt the TF boot contacts that exist on the board.
It is a DINO 7.17.
AML8726-MX - dual core 1.5GHz
1GB RAM
8GB internal ROM
According to build.prop (original) the board is:
ro.product.model=DINO7.17
ro.product.brand=MID
ro.product.name=DINO7.17
ro.product.device=g08ref - can't seem to find any firmware with this reference
ro.product.board=g08ref
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
the original mtd table:
mtd0: 00400000 00100000 "bootloader"
mtd1: 00800000 00400000 "logo"
mtd2: 00800000 00400000 "aml_logo"
mtd3: 00800000 00400000 "recovery" - have it
mtd4: 00800000 00400000 "boot" - have it
mtd5: 30000000 00400000 "system" - have it
mtd6: 08000000 00400000 "factory" - have it
mtd7: 08000000 00400000 "cache"
mtd8: 90000000 00400000 "userdata"
mtd9: 12d000000 00400000 "NFTL_Part"
Did you fix your tablet?
Could someone help us out here?
:crying:
Futaba0rus said:
Hi, i want some help with unbricking an aml8726-mx tablet. It's Prestigio Multipad Prime Duo, 7" 1024x600 tablet with 16gb internal storage and micro-sd card slot. It has only Power and + - volume buttons.
I've bricked it by flashing official firmware with default recovery. Entered recovery, made wipe, than installed update.zip from sd card. Progress bar started to move, indicating what process is on the way. And than in about 20%(no real percentage was in that recovery) tablet first freezed and than turned off. From this point there was no reaction on buttons, no display(even no backlight) - nothing. Connecting it to PC made the power on light flashing every 1 second(i guess). No device found by PC. I've tried turning on with - and + pressed, with both, without pressing anything - no luck.
So it was deep brick. Later i have found some info about 5th and 6th pins on NAND chip inside tablet, if those pins are connected to each other, after turning on tablet will be discovered by PC as M6 device. That worked! After hours dancing around AML usb flashing tool i was able to boot some uboot on tablet, started some recovery(not on the screen, it's still black as night), connect to recovery with ADB and trying to flash BOOT, BOOTLOADER and RECOVERY.
What i've tried:
1)adb push boot.img, boot loader.img and recovery.img i get from official firmware for this tablet
2)to make sure what my files now exists on tablet. I've pushed them to /cache/ so
Code:
#cd /cache/
#ls
and ls told me what my .img files are there
3)tried to flash
Code:
#flash_image boot /cache/boot.img
#flash_image bootloader /cache/bootloader.img
#flash_image recovery /cache/recovery.img
And here is a problem - each of those command gave me that:
error scanning partitions exit with code -1
I can't flash bootloaders and recovery. I've googled for days and still dont get it - why that "partition scaning" errors and what should i try.
If anyone can help me with that, or is there some different method of flashing it - i will be highly appreciated. I've used this tablet for less than a week and now it's totally bricked what i can't bring it back to life.
Click to expand...
Click to collapse
Same problem here
I have the same problem with my prime duo, but I have a problem with aml flash tool too. Can you link the files (bootorig... config_progress.xml etc) what are worked for you?
I unbricked my android tv box, AML8726-MX g18ref box with a special sd card. I had similar problem....
Sent from my ST18i using xda app-developers app
BenniBenassi said:
I unbricked my android tv box, AML8726-MX g18ref box with a special sd card. I had similar problem....
Sent from my ST18i using xda app-developers app
Click to expand...
Click to collapse
Hello, can you tell us what kind off special SD card?
Thanks
ruyzalim said:
Hello, can you tell us what kind off special SD card?
Thanks
Click to expand...
Click to collapse
Yes I can.
It is a Generic MX Droid-TV (AML8726-MX G18REF) box, now with AndroidGadget ROM.
I used this program below to create a special SD card (with a new image), which booted and fixed my box, with AndroidGadget ROM.
FILE: DD
FILE: IMAGE
FILE: ROM (pw: androidgadget.co.uk)
The DD program used to create the special bootable SD only works under Win XP (Under VMware is also OK)
I hope it will be of help.
If anyone makes a kernel for this that supports CWM, CPU speed mod and CyanogenMod, I'd be grateful
BenniBenassi said:
Yes I can.
It is a Generic MX Droid-TV (AML8726-MX G18REF) box, now with AndroidGadget ROM.
I used this program below to create a special SD card (with a new image), which booted and fixed my box, with AndroidGadget ROM.
FILE: DD
FILE: IMAGE
FILE: ROM (pw: androidgadget.co.uk)
The DD program used to create the special bootable SD only works under Win XP (Under VMware is also OK)
I hope it will be of help.
If anyone makes a kernel for this that supports CWM, CPU speed mod and CyanogenMod, I'd be grateful
Click to expand...
Click to collapse
Thank you very much
WARNING, IF YOU DO NOT KNOW WHAT YOU ARE DOING, THEN DO NOT DO IT.
1) THE PROCESS IS ENTIRELY AUTOMATED.
2) NO NEED TO MANUALLY INSTALL ANYTHING ONCE THE PROCESS IS STARTED.
3) THE 2 ERRORS COMING AT THE END OF THE RECOVERY PROCESS ARE PART OF THE PROCESS.
AN IMPORTANT REMINDER:
If you can not follow the instructions correctly or you do not understand them, ASK BEFOREHAND on the FORUM and UNDER NO CIRCUMSTANCES PERFORM THE RECOVERY.
Under no circumstances should you do any manual installation of any of the files located on the recovery sd card.
The result may be a permanently bricked box with no way to recover.
Here is an almost-idiot proof ROM install and UNBRICK method instruction for AML8726-MX (M6) Android TV Box (1gb / 8gb dual core):
If you manage to brick your box, it is your fault entirely. I did the recovery image for myself and decided to share it with community. Use at your own reponsibility.
Also known as:
G18REF
DROIDBOX iMX6
DROIDTV MX
MX2REF
MATRICOM G-BOX MX2
or any generic Android MX Media Box with same hardware, AML8726MX 1G/8G set top box
HD18 V2.2
HD18 V2.21
HD18 V2.22
I created an easy-install SD Card image from this ROM: Matricom G-Box Midnight MX2 v1.1.5+ (ROM DATE = 9th of August 2013)
The ROM was used for creating the special install SD card.
It is very simple to install, just insert a 4gb or larger SD CARD into Windows PC and use this program to set up the card:
DOWNLOAD THIS:
http://hddguru.com/software/HDD-Raw-Copy-Tool/HDDRawCopy1.02Portable.exe
Then use the extracted sd card image file as a source and set a target to your sd card (4 gb), it writes the image, close the HDD RAW COPY program and eject the card (SAFELY - choose eject from PC, right click menu + eject).
DOWNLOAD THIS:
FILE: Matricom Midnight G-BOX MX2 v1.1.5+ image (August 9th, 2013)
WARNING: THIS METHOD WILL ERASE EVERYTHING FROM YOUR MX BOX AND INSTALL A NEW ROM. USE AT YOUR OWN DISCRETION.
As an added BONUS this will UNBRICK your device in case it is bricked.
Matricom image (Android 4.2.2): OTA works for XBMC etc
- Make sure MX device is powered off and power cable removed.
- Insert SD card you just created.
- Insert a match or a toothpick to reset hole - you will feel a click. (it is the AV hole in the back)
- Power on the MX box by inserting power cable, while holding the match in the reset hole.
- It will boot to recovery and start installing ROM.
- After finishing it will give 2 errors - these do not matter.
- Remove power cable and insert it again, the device will boot as MATRICOM MIDNIGHT G-BOX MX2
This is how the board looks from inside: (NO NEED TO OPEN FOR INSTALLING)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
BenniBenassi said:
Here is an almost-idiot proof ROM install and UNBRICK method instruction for AML8726-MX (M6) Android TV Box (1gb / 8gb dual core):
Also known as:
G18REF
MX2REF
GENERIC MX MEDIA BOX
HD18 V2.2
HD18 V2.21
I created an easy-install SD Card image from this ROM: Matricom G-Box Midnight MX2 v1.1.5+ (ROM DATE = 9th of August 2013)
The ROM was used for creating the special install SD card.
It is very simple to install, just insert a 4gb or larger SD CARD into Windows PC and use this program to set up the card:
DOWNLOAD THIS:
http://hddguru.com/software/HDD-Raw-Copy-Tool/HDDRawCopy1.02Portable.exe
Then use the extracted sd card image file as a source and set a target to your sd card (4 gb), it writes the image, close the HDD RAW COPY program and eject the card (SAFELY - choose eject from PC, right click menu + eject).
DOWNLOAD THIS:
FILE: Matricom Midnight G-BOX MX2 v1.1.5+ image (August 9th, 2013)
WARNING: THIS METHOD WILL ERASE EVERYTHING FROM YOUR MX BOX AND INSTALL A NEW ROM. USE AT YOUR OWN DISCRETION.
As an added BONUS this will UNBRICK your device in case it is bricked.
Matricom image (Android 4.2.2): OTA works for XBMC etc
- Make sure MX device is powered off and power cable removed.
- Insert SD card you just created.
- Insert a match or a toothpick to reset hole - you will feel a click. (it is the AV hole in the back)
- Power on the MX box by inserting power cable, while holding the match in the reset hole.
- It will boot to recovery and start installing ROM.
- After finishing it will give 2 errors - these do not matter.
- Remove power cable and insert it again, the device will boot as MATRICOM MIDNIGHT G-BOX MX2
This is how the board looks from inside: (NO NEED TO OPEN FOR INSTALLING)
Click to expand...
Click to collapse
Thanks for this
Question, I thought Matricom prevented loading their firmware on non Matricom boxes, will this definitely work on a DroidTV MX?
Thanks
jackhill said:
Thanks for this
Question, I thought Matricom prevented loading their firmware on non Matricom boxes, will this definitely work on a DroidTV MX?
Thanks
Click to expand...
Click to collapse
IF IT IS one of these and the board looks like the one on the picture:
G18REF
MX2REF
GENERIC MX MEDIA BOX
HD18 V2.2
HD18 V2.21
Make sure you check it is the correct hardware.
Don't forget to back up anything you need from it, since this will format everything and install a new rom.
ANSWER IS: YES
This is a special AMLogic Boot SD card image and YES it works.
This is how the MX box looks like:
MX Android 4.2.2 TV Box XBMC Amgloic 8726-MX Dual Core Unboxing
.
can not to flash the firmware with usb metode
Hi to all!
I have a problem with my eboda e300 tablet!
Tablet is bricked and works strange!!
With tablet off when connect this to pc into amlogicburnning software is detected like "standard enhanced" without press the button power and home.
My problem : can not to flash this tablet with original firmware!
Log is:
W/ Import upgrade file E:\Android\AML8726MX\eboda E300_SW-pc-1113-RD_20121129.zip
W/ [P3][20:50:01]Loading spl ...
W/ [P3][20:50:02]Transfer Complete! total size is 18556 Bytes
W/ [P3][20:50:04]Transfer Complete! total size is 500204 Bytes
W/ [P3][20:50:16]After load uboot, disconnect, mBurnWaitCount: 9
W/ [P3][20:50:19]After load uboot, disconnect, mBurnWaitCount: 12
W/ [P3][20:50:21]wait uboot run ,scan system again!!!
W/ [P3][20:50:22]After load uboot, disconnect, mBurnWaitCount: 15
W/ [P3][20:50:25]After load uboot, disconnect, mBurnWaitCount: 18
W/ [P4][21:47:32]Identify get 0, maybe device is reset, back from 0 step and retry
When try to flash this command work :
<command sn="0" path="usb_spl.bin" address="0xd9000000" run="true">load spl</command>
<command sn="1" path="u-boot-orig.bin" address="0x8f800000" run="false">load uboot</command>
<command sn="2" >crc 0x8f800000 size value</command>
and stopped here :
<command sn="3" >run 0x8f800000</command>
In this moment the tablet is not detected into hardware device!!
Thanks to all to any sugestion!:crying:
Confirmed working on my DroidTV MX
Thanks so much
BenniBenassi said:
Here is an almost-idiot proof ROM install and UNBRICK method instruction for AML8726-MX (M6) Android TV Box (1gb / 8gb dual core):
Also known as:
G18REF
MX2REF
GENERIC MX MEDIA BOX
HD18 V2.2
HD18 V2.21m
I created an easy-install SD Card image from this ROM: Matricom G-Box Midnight MX2 v1.1.5+ (ROM DATE = 9th of August 2013)
The ROM was used for creating the special install SD card.
It is very simple to install, just insert a 4gb or larger SD CARD into Windows PC and use this program to set up the card:
DOWNLOAD THIS:
http://hddguru.com/software/HDD-Raw-Copy-Tool/HDDRawCopy1.02Portable.exe
Then use the extracted sd card image file as a source and set a target to your sd card (4 gb), it writes the image, close the HDD RAW COPY program and eject the card (SAFELY - choose eject from PC, right click menu + eject).
DOWNLOAD THIS:
FILE: Matricom Midnight G-BOX MX2 v1.1.5+ image (August 9th, 2013)
WARNING: THIS METHOD WILL ERASE EVERYTHING FROM YOUR MX BOX AND INSTALL A NEW ROM. USE AT YOUR OWN DISCRETION.
As an added BONUS this will UNBRICK your device in case it is bricked.
Matricom image (Android 4.2.2): OTA works for XBMC etc
- Make sure MX device is powered off and power cable removed.
- Insert SD card you just created.
- Insert a match or a toothpick to reset hole - you will feel a click. (it is the AV hole in the back)
- Power on the MX box by inserting power cable, while holding the match in the reset hole.
- It will boot to recovery and start installing ROM.
- After finishing it will give 2 errors - these do not matter.
- Remove power cable and insert it again, the device will boot as MATRICOM MIDNIGHT G-BOX MX2
This is how the board looks from inside: (NO NEED TO OPEN FOR INSTALLING)
Click to expand...
Click to collapse
Must be an idiot. I can't get the card to flash without an error writing after it says 100. If I try it the box boots into recovery but nothing flashes to the box.. I've tried 2 different sd cards
joeblow3 said:
Must be an idiot. I can't get the card to flash without an error writing after it says 100. If I try it the box boots into recovery but nothing flashes to the box.. I've tried 2 different sd cards
Click to expand...
Click to collapse
Your box is not the correct hardware for this ROM.
It is not for other hardware than mentioned in my OP.
It can work in the G02REF(1gb / 4gb dual core)?
---------- Post added at 07:42 AM ---------- Previous post was at 07:35 AM ----------
BenniBenassi said:
Here is an almost-idiot proof ROM install and UNBRICK method instruction for AML8726-MX (M6) Android TV Box (1gb / 8gb dual core):
Also known as:
G18REF
MX2REF
GENERIC MX MEDIA BOX
HD18 V2.2
HD18 V2.21
I created an easy-install SD Card image from this ROM: Matricom G-Box Midnight MX2 v1.1.5+ (ROM DATE = 9th of August 2013)
The ROM was used for creating the special install SD card.
It is very simple to install, just insert a 4gb or larger SD CARD into Windows PC and use this program to set up the card:
DOWNLOAD THIS:
Then use the extracted sd card image file as a source and set a target to your sd card (4 gb), it writes the image, close the HDD RAW COPY program and eject the card (SAFELY - choose eject from PC, right click menu + eject).
DOWNLOAD THIS:
WARNING: THIS METHOD WILL ERASE EVERYTHING FROM YOUR MX BOX AND INSTALL A NEW ROM. USE AT YOUR OWN DISCRETION.
As an added BONUS this will UNBRICK your device in case it is bricked.
Matricom image (Android 4.2.2): OTA works for XBMC etc
- Make sure MX device is powered off and power cable removed.
- Insert SD card you just created.
- Insert a match or a toothpick to reset hole - you will feel a click. (it is the AV hole in the back)
- Power on the MX box by inserting power cable, while holding the match in the reset hole.
- It will boot to recovery and start installing ROM.
- After finishing it will give 2 errors - these do not matter.
- Remove power cable and insert it again, the device will boot as MATRICOM MIDNIGHT G-BOX MX2
This is how the board looks from inside: (NO NEED TO OPEN FOR INSTALLING)
It can work in the G02REF(1gb / 4gb dual core)?
Click to expand...
Click to collapse
I have no idea but I think NOT.
Sent from my ST18i using xda app-developers app

Categories

Resources