I hold no responsibility to how you use or not use this info and if you brick phone - you do this at your own risk
Mini How To
How to install recovery and custom ROMs
Changelog and Downloads
2011-02-11
IMPORTANT NOTE: I have not tested this ROM as I not own U8150 anymore
FILENAME: U8150V100R001C191B822_021211_094422.zip
MD5: 110c084c71729aca1ea8361dcb5fe5f5
* Reverted back to Launcher2
* Added Apps2SD
* Add couple apps I think is useful: wifi analyzer, android terminal, alogcat, cache cleaner-ng. (these can be easily uninstalled)
* Built with latest kitchen 0.120
* Removed Gingerbread keyboard and Google Goggles
2011-01-15
FILENAME: U8150V100R001C191B822_011511_221843.zip / Mirror
MD5: 357e5efb21d3272bb0820c0e14cfe913
* Added Boot Animation - Android Scribble 2.0 no flare
* Added Gingerbread Keyboard - Renamed Gingerbread Keyboard - updated 2010-12-28
* Unlocked Market - thanks xxhp for the package
* Added Google Goggles and AdFree
2011-01-09
This ROM should have overall better performance(hopefully)
Note:
Do a wipe of data and must clear dalvik-cache because of JIT being enabled (under 'wipe' in AmonRA Recovery 1.6.2 ROM)
FILENAME: U8150V100R001C191B822_010911_182214.zip
MD5: d8fae03567ebfa1602a116cc9e5aa587
* Added more ring tones from CM rom
* Ring delay fix
* CDRom symlink fix
* Fixed proximity delay (phone come off of the "black screen" faster)
* Turned Automatic brightness ON
* Now wifi will scan once every 1 minutes when not around a known location.
Help minimize battery drain.
* Added JIT
* Set Setup Wizard to run 'Optional'
2011-01-05 Initial Release
FILENAME: U8150V100R001C191B822_010511_014603.zip
MD5: 059fe7693164b1031a63fce373d57717
* Rooted (Superuser.apk + su)
* BusyBox installed
* /system/framework is deodexed
* /system/app is deodexed
* twitter/facebook/documents2go moved to /data/app
* swapped out Launcher 2 for Zeam Launcher
* Apps like Gmail, Maps, Vending etc updated.
If you like my work please make a donation via the Donate to me button on the left
Enjoy
Thanks for the update quail!
Do you have the AUS version of the Ideos? If so, who'd you get yours from?
Also, can we use this thread as a ROM request? (i.e. overclocking ability, gingerbread development)
Thanks. But can you plz post a guide or give a link on how to install the modified ROM in IDEOS for noobs like me
hachoo said:
Thanks for the update quail!
Do you have the AUS version of the Ideos? If so, who'd you get yours from?
Also, can we use this thread as a ROM request? (i.e. overclocking ability, gingerbread development)
Click to expand...
Click to collapse
Yes I have the AU version and I bought a Crazy Johns pack with 4GB micro HCSD carded included from Aus. Post for 159AUD. I was luck and go one that was not locked to any network.
Yes you can use the thread for ROM requests, I personally will be ignoring requests for OCing, as there is a very nice little app called setCPU which works great on the U8150.
[How to] install recovery and custom ROMs
I hold no responsibility to how you use or not use this info and if you brick phone - you do this at your own risk
Part 1 Installing Recovery ROM
Please refer to this post before flashing Recovery ROM - AmonRA Recovery 1.6.2 and BLUE Screen
The custom recovery allows you to do all sorts of lovely things such as installing ROM update zips (for the forthcoming custom ROMs), wiping various parts of the device, backing up and restoring and much more.
You can enter recovery mode - turn it off, then press the power button while holding the 'volume up' and 'send' (green).
Downloads
AmonRA Recovery 1.6.2 - DOWNLOAD (MediaFire Pro) / MIRROR (CoBlitz / ROMraid) - MD5: 65d4dcbbedb956a9f88dd1981fb31ef8
How to install - Windows, Linux and OSX
Download the recovery image of your choice above and extract the zip file
Put your device in bootloader mode - turn it off, then press the power button while holding the 'Volume Down' and 'End (Red)' keys
WINDOWS - double click 'install-recovery-windows.bat'
MAC - Open a terminal window to the directory containing the files, and type 'chmod +x install-recovery-mac.sh' followed by './install-recovery-mac.sh'
LINUX - Open a terminal window to the directory containing the files, and type 'chmod +x install-recovery-linux.sh' followed by './install-recovery-linux.sh'
Part 2 Installing Custom ROM
Note: When using the Custom Recovery image use the Trackball to move up / down and press to select. Use the volume down button to go back.
Download a Custom ROM of your choice and place the ENTIRE ZIP (Do not extract it) onto the root of your SD card. By "Root" I mean do not place the file in any subfolders
Enter recovery mode - turn it off, then press the power button while holding the 'volume up' and 'send' (green).
From Custom Recover Main menu and select the 'Backup/Restore' option. Choose a 'Nand backup' and let it run it's course
Return to the Custom Recover Main menu and select the 'Wipe' option. Choose the First option 'Wipe data/factory reset' and confirm. <- this is optional after installing one of my ROMs. I personally have not bothered with it with my ROMs
Return to the Custom Recover Main menu and select the 'Flash zip from sdcard'. Select the custom rom you wish to flash, confirm and wait.
Part 3 Restoring back to original ROM
Note: Upgrade operations will erase the user data.
Find and Download ROM from Link provided on WiKi that you want to install
Copy the entire dload folder (with UPDATE.APP in it) to the root directory of the MICRO SD card.
Make sure your handset is power off. Insert the MICRO SD card into the handset. Pressing the END key and VOLUME UP key, and then press the POWER key to power on the phone and enter the Software Upgrade Mode.
You can see process bar start from 0 on the screen. (this take a few minutes)
Then the handset will restart automatically. Then it is OK.
Reference:
Part 1 info taken from here
quail said:
Yes I have the AU version and I bought a Crazy Johns pack with 4GB micro HCSD carded included from Aus. Post for 159AUD. I was luck and go one that was not locked to any network.
Yes you can use the thread for ROM requests, I personally will be ignoring requests for OCing, as there is a very nice little app called setCPU which works great on the U8150.
Click to expand...
Click to collapse
I got the same deal!
Have you played around with the kernel at all? I'm not experienced in programming etc. but apparantly to OC the IDEOS U8150 more than 600mhz (setcpu does this automatically), it needs a kernel hack like other phones do.
Trekker56 said:
Thanks. But can you plz post a guide or give a link on how to install the modified ROM in IDEOS for noobs like me
Click to expand...
Click to collapse
Sorry I did think to add a how to install recovery/custom ROM how to, well there is one now.
Thanks
hachoo said:
I got the same deal!
Have you played around with the kernel at all? I'm not experienced in programming etc. but apparantly to OC the IDEOS U8150 more than 600mhz (setcpu does this automatically), it needs a kernel hack like other phones do.
Click to expand...
Click to collapse
I have played around with Linux Kernels in the past just not the Android kernel yet... but I am sure it not that hard to patch it and recompile.
I am happy with the 600MHz that setCPU unlocks it too.
quail said:
You can enter recovery mode - turn it off, then press the power button while holding the 'volume up' and 'send' (green).
[*] Put your device in bootloader mode - turn it off, then press the power button while holding the 'Volume Down' and 'End (Red)' keys
Click to expand...
Click to collapse
The Main thinkg about these two parts here, when i enter recovery mode i get a blue screen is that right... nothing BUT a blue screen.
When i try to enter the bootloader mode it stays on the IDEOS logo, the first one when you turn it on...
Also im guessing it has to be plugged into the usb at all times for these.
tankknat said:
The Main thinkg about these two parts here, when i enter recovery mode i get a blue screen is that right... nothing BUT a blue screen.
When i try to enter the bootloader mode it stays on the IDEOS logo, the first one when you turn it on...
Also im guessing it has to be plugged into the usb at all times for these.
Click to expand...
Click to collapse
You should not be getting a blue screen, you sure your using the correct key combination?
Yes you need the USB cable plugged in to use the bootloader. Yes the bootloader is ment to just sit at the IDEOS logo
yeah im 100% sure i used the correct key combo for the restore recovery mode, and sweet as for the bootloader, just wasnt 100% sure on that one.
Thank you OP for the info here, I used them to flash the recovery and I'm going to flash your ROM.
Having a Desire from the very first day I'm not new to these things, but this little boy is in my hands since this afternoon and it's amazing that you came with this just in time.
Will report back in a while with impressions.
OK, here I am. Just attempted to flash the ROM (after a full wipe), but it fails with an "Installation aborted." message just after the ISO symlink one. Looking at the update script, I guess there was a problem while flashing the BOOT partition.
Rebooting into the OS result in the new (rooted) ROM, but something is missing: the build.prop is likely the old one (I still see the old build string) and I have only 118 MB of free NAND space.
Coming from the Vodafone Italy ROM.
Any hint?
@ngel said:
OK, here I am. Just attempted to flash the ROM (after a full wipe), but it fails with an "Installation aborted." message just after the ISO symlink one. Looking at the update script, I guess there was a problem while flashing the BOOT partition.
Rebooting into the OS result in the new (rooted) ROM, but something is missing: the build.prop is likely the old one (I still see the old build string) and I have only 118 MB of free NAND space.
Coming from the Vodafone Italy ROM.
Any hint?
Click to expand...
Click to collapse
What package did you download? I forgot to test one my builds and aborted installation on me, but I have fixed it and already put up a work version. Please try the newer version
quail said:
What package did you download? I forgot to test one my builds and aborted installation on me, but I have fixed it and already put up a work version. Please try the newer version
Click to expand...
Click to collapse
Hi, I flashed "U8150V100R001C191B822_010711_042603", the one I guess is the newest (despite the "2010" typo on the first post ).
Is there a newer one?
@ngel said:
Hi, I flashed "U8150V100R001C191B822_010711_042603", the one I guess is the newest (despite the "2010" typo on the first post ).
Is there a newer one?
Click to expand...
Click to collapse
thanks, fixed the typo.
ATM there is no newer version.
@ngel said:
OK, here I am. Just attempted to flash the ROM (after a full wipe), but it fails with an "Installation aborted." message just after the ISO symlink one. Looking at the update script, I guess there was a problem while flashing the BOOT partition.
Rebooting into the OS result in the new (rooted) ROM, but something is missing: the build.prop is likely the old one (I still see the old build string) and I have only 118 MB of free NAND space.
Coming from the Vodafone Italy ROM.
Any hint?
Click to expand...
Click to collapse
Another thing I am not sure what the diff is between the Italian ROM and the Australian ROM. I wonder if you phone is not fully compatible with the Australian ROM?
ARGH, ok not good...
booted up to flash my loving ideos and i think i killed it...
'Firemware update step 1/2
Unpacking
[=============] (thats a progress bar
!
update failed
and all my buttons are blinking...
First version working
I had the same problems as @ngel using the newer version. Fail with the iso symlink.
Used the first version you posted up and that worked without a problem.
Zeam Launching is really snappy. Or I just haven't bogged down my phone with a whole bunch of crap yet.
Thanks for your work I bought my Ideos through 2 Degrees in New Zealand.
Request:
I quite like the look of the black notification bar and green icons. Would you be able to theme this rom with those? Also could you include the gingerbread keyboard. I know I can install it separately but would be cool to have Touch Pal and the original keyboard removed and replaced with the gingerbread one.
tankknat said:
ARGH, ok not good...
booted up to flash my loving ideos and i think i killed it...
'Firemware update step 1/2
Unpacking
[=============] (thats a progress bar
!
update failed
and all my buttons are blinking...
Click to expand...
Click to collapse
Did you power on your unit holding the 'volume up' and 'red' key?
Related
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
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.
Kernel Update Utility 0.9YouTube video"Making kernel flashing a bit easier"
About:
This lightweight tool takes a kernel, and flashes it to your device. You can give it the kernel in zImage or CWM flashable zip format. Some people have come across bootloops when using clockworkmod to flash kernels, hopefully this tool will prove to fit better for the job. It can also push and apply kernel modules. I have now flashed a kernel using this tool more times than I can count, and not a single bootloop or failed flash.
This tool is ideal for people who do not want to mess with command lines, and people who want the job done fast and easy.
System requirements:
Windows XP SP2 or higher
.NET 4.0
HTC Sync (or ADB drivers)
Rooted, ENG S-OFF Desire HD
Changelog:
0.9:
- Added support for Lee's kernels
0.8:
- Added support for Kamma's new kernels
0.7:
- Fixed Windows XP file not found -bug
- Optimized the code further
0.6:
- Most cmd windows hidden
- Better instructions in module pushing
- Out of beta!
0.5a:
- Optimized a lot of code
- Improved SU permissions; fixed modules not getting pushed with phones that do not have root adb by default
- Cleans up /system/lib/modules to ensure cp functionality
0.4:
- It is now possible to choose multiple modules
- It cleans up afterwards
0.3:
- CWM zip file flashing, pushes all modules
- Space in filename -bug fixed
0.2:
- Initial release
Click to expand...
Click to collapse
If you like my work, please consider (or just hit the thanks button ):
Hi,
thanks !!
Please add more selections for ko files:
- tun.ko
- cifs.ko
- other
with friendly greet
starbase64
Yeah, I will
I will also make this work with CWM flashable zips, I am programming that in right now.
Hi,
good news, thanks.
with friendly greet
starbase64
It can now flash zip files that would usually be flashed in clockworkmod. Using my app to flash it should reduce the possibility of a bootloop. Also the space in filename -bug has been fixed.
e: Another update, now for selecting and applying kernel modules. Please leave feedback! Is there something I should change? Any features you would like to see in this tool?
Keep in mind that this tool can also be used for recovering from some bootloops, where kernel itself is not properly flashed. In some situations, however, boot.img corrupts in CWM flash, then you will have to restore a partial nandroid.
thanks.. now i wish there is a tool for pushing ENG hboot and CWM recovery .. where is unrevoked
Well, I can enable my tool to flash a recovery, but because flashing hboot is so risky, I think I will not do that feature..
So, are people interested in a recovery flasher?
So now I can flash the .zip files that before I was flashing with the recovery with this application?
Yeah, if those files are kernels. This tool has been tested with Apache14's 1.2 and 1.5 GHz OC/UV kernels.
jkoljo said:
Yeah, if those files are kernels. This tool has been tested with Apache14's 1.2 and 1.5 GHz OC/UV kernels.
Click to expand...
Click to collapse
Wow it's amazing guy!!! i have tried now, with, before my htc desire hd was going in eternal bootloop with origianl rom and 1,2 kernel now it's ok really tank you!!!
No problem, glad it helped!
Hi,
support for german users here > www.handy-faq.de
with friendly greet
starbase64
Noob question but how can you revert back to original kernal?
Not tried this yet But this is What I been waiting for. How long does the process take?
Thanks
Sent from my Desire HD using XDA App
Used this tool to flash the Buzz 1.51GHz Kernel. First off, congrats on such an easy to use tool for noobs like me. It's really simple and straightforward. However, I now have a problem with my wifi not working (just shows 'error' in wifi settings). I'm guessing this is because the module didn't apply properly? I've tried it a couple of times now with the same result...although I fully accept it could be stupidity on my part.
Further info:
I have root (permenant, via visionary+) and S-off (Eng HBoot installed) but not installed clockwork recovery yet.
I start the app, set my DHD to 'charge only', tick 'I understand the risks' and click next.
Browse to the file I downloaded for the Kernel (this one) and click 'next'.
click 'go to fastboot' (phone reboots in fastboot mode) click 'Flash' and something about 'writing zimage' flashes past. Click Next. (phone reboots)
When phone reboots I enter my PIN, unlock the phone and select 'charge only' for the USB connection (this isn't mentioned, but I figure it needs to be connected like this for the adb stuff to work) and press 'apply modules'. Something on my phone requests superuser access (not sure if this is just co-incidence or something the app is doing) so I allow it. Loads of messages flash past on my desktop (I assume this is applying the modules) and the app says 'modules pushed and applied'.
My wifi status shows 'error' so I try a reboot. Still shows error.
Any ideas?
Deicist said:
Used this tool to flash the Buzz 1.51GHz Kernel. First off, congrats on such an easy to use tool for noobs like me. It's really simple and straightforward. However, I now have a problem with my wifi not working (just shows 'error' in wifi settings). I'm guessing this is because the module didn't apply properly? I've tried it a couple of times now with the same result...although I fully accept it could be stupidity on my part.
Further info:
I have root (permenant, via visionary+) and S-off (Eng HBoot installed) but not installed clockwork recovery yet.
I start the app, set my DHD to 'charge only', tick 'I understand the risks' and click next.
Browse to the file I downloaded for the Kernel (this one) and click 'next'.
click 'go to fastboot' (phone reboots in fastboot mode) click 'Flash' and something about 'writing zimage' flashes past. Click Next. (phone reboots)
When phone reboots I enter my PIN, unlock the phone and select 'charge only' for the USB connection (this isn't mentioned, but I figure it needs to be connected like this for the adb stuff to work) and press 'apply modules'. Something on my phone requests superuser access (not sure if this is just co-incidence or something the app is doing) so I allow it. Loads of messages flash past on my desktop (I assume this is applying the modules) and the app says 'modules pushed and applied'.
My wifi status shows 'error' so I try a reboot. Still shows error.
Any ideas?
Click to expand...
Click to collapse
Same issue here, does not push the wifi module
Strange, it does push it for me. I'll investigate. It may have something to do with root rights, does bcm4329.ko appear to your sdcard?
Nope, doesn't appear in sdcard.
For further info I tried it with 0.3 as well, same result.
Also, none of the modules get pushed, it's not just the wifi one.
My app removes the files from sdcard afterwards, so they might not be there anymore when you check it. I have now uploaded a new version with completely new SuperUser access code, also a lot of the code has been optimized.
This version works for me 100%, I just flashed from Apache14's kernel to kamma's kernel and back, wifi worked every time.
Also keep in mind that you should wait for the Android system to fully boot up before trying to push and apply the modules. So wait for "Usb debugging connected" and "Charge only"
Please give feedback!
jkoljo said:
My app removes the files from sdcard afterwards, so they might not be there anymore when you check it. I have now uploaded a new version with completely new SuperUser access code, also a lot of the code has been optimized.
This version works for me 100%, I just flashed from Apache14's kernel to kamma's kernel and back, wifi worked every time.
Also keep in mind that you should wait for the Android system to fully boot up before trying to push and apply the modules. So wait for "Usb debugging connected" and "Charge only"
Please give feedback!
Click to expand...
Click to collapse
Nope, will not push wifi module, all phone settings are as per instructions
Which rom are you on? Do you have HTC Sync 3.0 on your computer?
Try pushing modules manually as per Apache14's thread first post, if it works then the problem is propably in my tool, if it does not work, the problems is at your end.
Recovery BootStrap (TWRP) - Motorola Defy\Bravo
Version: 4.0
Install Recovery BootStrap (TWRP) for Motorola Defy\Bravo via a USB cable. For computers running the Windows\Linux (port version) operating system.
Download: (Windows: MEGA / Google Drive) | (Linux: port by nastys post>>)
Install Recovery BootStrap (TWRP) you can right out stock firmware (without custom recovery) with superuser.
Recovery BootStrap (TWRP) - for the recovery say thank Quarx, after installation, you can install the rom CyanogenMod from Quarx for December 2014 (but do not forget about resize.zip).
Can be installed on Defy (MB525), Defy Plus (MB526), Bravo (MB520).
Requirements for smartphone:
Enable USB debugging
Superuser (ROOT)
Free space on the memory card of 100 megabytes
Instructions:
1. Download the archive
2. Unpack it somewhere else with a short path, for example D:\andro
3. Connect your phone via USB cable ("debugging on USB" should be included)
4. Run the install_bootstrap.cmd
5. When you see the label "Let's Start? =)", press any key
6. If the superuser ask permission for full access "ADB Shell", allow.
7. After installing the smart phone will automatically restart
!IMPORTANT! after restarting the Stock firmware will not start!, but you will have BootStrap (TWRP) so you can safely install custom firmware\rom
Change log:
V3:
Changed how the script
Fixed installation errors recovery on Android 4.x and later
V4:
The script changed drastically
After installation removes trash from the memory card (so far only on Android 4.x and later)
Made for normal (mortals) users , before you start the installation script checks (by model) which smartphone connected to the computer, if your smartphone is not supported script report it and stop installation, if supported will give something "Device: MB525".
Serviceability checked on the Chinese 231 (Defy) firmware with superuser (what say thank borndead), and on the Asian 231 (Defy)
Questions\FAQ:
Error "[ERROR] Verify device!", what to do?
Error "[ERROR] Verify device!", it is may mean the following:
1. You have not enabled USB debugging
2. Your smartphone does not support this Recovery. (only for MB525, MB526, MB520)
3. You need to confirm the action ADB on your smartphone
4. Or you have some other connection problems
Stock transition to CyanogenMod 11 of Quarx
Stock transition to CyanogenMod 11 (firmware and find all necessary files can be here) of Quarx in short (generally as described on the website Quarx, only simpler and under Windows)
1. Install Recovery BootStrap (TWRP) via USB
2. Enter Recovery install resize.zip
3. Restart your smartphone
4. Install CyanogenMod 11 and GApps
Good work, comrade! I flashed CM11 on the Moto Defy - everything works!
We did observed some cases, where a "new life (resized)" Defy is not booting anymore. Only solution was to reflash SBF and start from scratch.
Does this mean, it is possible to recover TWRP from PC? That would be a step a head!
This is amazing! Everytime I needed to reflash the stock ROM I needed to install cm10, then cm11, then new bootsrap etc...
Unfortunately I don't use Windows...
@Octanium91 Would you mind if I port your script to GNU/Linux?
starbright_ said:
We did observed some cases, where a "new life (resized)" Defy is not booting anymore. Only solution was to reflash SBF and start from scratch.
Does this mean, it is possible to recover TWRP from PC? That would be a step a head!
Click to expand...
Click to collapse
I tried to do something like that, is not yet happened. Perhaps in the future even try
nastys said:
This is amazing! Everytime I needed to reflash the stock ROM I needed to install cm10, then cm11, then new bootsrap etc...
Unfortunately I don't use Windows...
@Octanium91 Would you mind if I port your script to GNU/Linux?
Click to expand...
Click to collapse
Maybe. If Iunderstand with GNU/Linux scripts
The new version, V4
The new version, V4
Changes:
The script changed drastically
After installation removes trash from the memory card (so far only on Android 4.x and higher)
More debugging: Now the script itself is not closed, and tells the user exactly what happened.
Sorry debris removal only works on Android 4.x and later.
Linux port done!
@Octanium91 I ported it to C++ (for Linux only at the moment). Please add it to the first post . Here is the link: MediaFire | MEGA
On Ubuntu just mount the ISO as image (not archive) then click 'Run' (or you can also extract the ISO and run the executable directly). It works on x86 (32 bit) and x86_64 (64 bit) CPUs. The source code is also included in the ISO. Tested on Ubuntu 14.10 and 16.04 (64 bit).
I tested it with both stock 2.3.6 rooted and CM11. It seems that the stock ROM won't boot after flashing the new bootstrap, but the recovery works fine
Also your version has a very bad bug: it flashes Defy bootstrap even on Bravo!!! It should flash Motorola Bravo specific bootstrap instead. My version only works for Motorola Defy and Defy+ at the moment, but you can edit the source code. EDIT: they are the same file with different names. I updated my version to support MB520.
After run the command script, when i boot in TWRP SDcard shows 0mb.
Already tried flashing the SBF recommended by quarx and after that the root SBF, but the result is always the same.
With CM recovery i can see the SDcard properly, but after the resize, or bootstrap, i always get 0mb at SDcard.
Any help?
Thanks!
evilinheaven said:
After run the command script, when i boot in TWRP SDcard shows 0mb.
Already tried flashing the SBF recommended by quarx and after that the root SBF, but the result is always the same.
With CM recovery i can see the SDcard properly, but after the resize, or bootstrap, i always get 0mb at SDcard.
Any help?
Thanks!
Click to expand...
Click to collapse
Format your SD card (to FAT32) or use another one.
Octanium91 said:
The new version, V4
Changes:
The script changed drastically
After installation removes trash from the memory card (so far only on Android 4.x and higher)
More debugging: Now the script itself is not closed, and tells the user exactly what happened.
Sorry debris removal only works on Android 4.x and later.
Click to expand...
Click to collapse
nastys said:
@Octanium91 I ported it to C++ (for Linux only at the moment). Please add it to the first post . Here is the link: https://www.mediafire.com/folder/candnhxj8aovj/Defy_Bootstrap_Installer_for_Linux
On Ubuntu just mount the ISO as image (not archive) then click 'Run'. It works on x86 (32 bit) and x86_64 (64 bit) CPUs. The source code is also included. Tested on 14.10 x86_64.
I tested it with both stock 2.3.6 rooted and CM11. It seems that the stock ROM won't boot after flashing the new bootstrap, but the recovery works fine
Also your version has a very bad bug: it flashes Defy bootstrap even on Bravo!!! It should flash Motorola Bravo specific bootstrap instead. My version only works for Motorola Defy and Defy+ at the moment, but you can edit the source code.
Click to expand...
Click to collapse
Greetings guys, I'm a user from the Atrix 2 section and a part of the current device supporters there. It's a pleasure to finally post here, 'the domain of Quarx' haha.
I was wondering if this recovery is able to flash and boot android Lollipop 5.0 roms yet? If so, then is there some way to port it from source to my or other similar Moto devices in the OMAP bracket with locked bootloaders?
I'm an Android novice, but I'm experienced in building custom recoveries and roms, as well as beginner git commands, so no need to hold anything back, lol. I appreciate the work you're all doing here, please continue to make the difference. Thanks for reading this and take care!
answer
Aceofzeroz said:
Greetings guys, I'm a user from the Atrix 2 section and a part of the current device supporters there. It's a pleasure to finally post here, 'the domain of Quarx' haha.
I was wondering if this recovery is able to flash and boot android Lollipop 5.0 roms yet? If so, then is there some way to port it from source to my or other similar Moto devices in the OMAP bracket with locked bootloaders?
I'm an Android novice, but I'm experienced in building custom recoveries and roms, as well as beginner git commands, so no need to hold anything back, lol. I appreciate the work you're all doing here, please continue to make the difference. Thanks for reading this and take care!
Click to expand...
Click to collapse
Hi!
flash and boot android Lollipop 5.0 roms - just can not say, but it is theoretically possible (need to check).
If so, then is there some way to port it from source to my or other similar Moto device - No, this is not possible (specifically, in this case). BUT this method you can set recovery to another smartphone (it is theoretically, need to try)
Here recovery that are in the public domain, I think that they can install Lollipop 5.0 roms - TWRP2 \ Safestrap
Moto devices in the OMAP bracket with locked bootloaders? - Most likely will not work, but no one stops to try
Octanium91 said:
Hi!
flash and boot android Lollipop 5.0 roms - just can not say, but it is theoretically possible (need to check).
If so, then is there some way to port it from source to my or other similar Moto device - No, this is not possible (specifically, in this case). BUT this method you can set recovery to another smartphone (it is theoretically, need to try)
Here recovery that are in the public domain, I think that they can install Lollipop 5.0 roms - TWRP2 \ Safestrap
Moto devices in the OMAP bracket with locked bootloaders? - Most likely will not work, but no one stops to try
Click to expand...
Click to collapse
Many thanks for the prompt and well ordered reply! I'll look into your suggestions and I'm aware that there aren't many available recovery software for our locked bootloader phones.
We were actually trying to get Safestrap working on our device since last month, but it's failing to work correctly in booting our kexec roms. So I thought I'd ask here since the Defy works by using the 2nd boot like us, but it's still under investigation. Thanks again for your assistance, we're not out of the game yet and we'll get things rolling eventually. Take care!:thumbup:
Sent from the Ace's MB865 using Tapatalk
Error. More than one device and emulator
what am i doing wrong?
LoeWn said:
Error. More than one device and emulator
what am i doing wrong?
Click to expand...
Click to collapse
Perhaps you have not enabled USB debugging
Requirements for smartphone:
Enable USB debugging
Superuser (ROOT)
Free space on the memory card of 100 megabytes
I did enable usb debugging
LoeWn said:
I did enable usb debugging
Click to expand...
Click to collapse
You can send us a screenshot?
I had a successful installation of a december build and twrp 2,6x installed, everything ran just fine. But when the CM tells me there is a update and i download it does not install from recovery, get errormsg. Also apps like rom manager pro tells my phone is not compatible with any updates, and that i should install CWM recovery. So is it possible to install a real CWM on a defy mb526?
Hi, I flashed Recovery BootStrap v4 on the Defy MB525, but its not working. After flash and reboot, phone starts booting, but it ends up with the following screen.
Doesn't matter if I choose Recovery or continue. I can press the menu button (to choose recovery) and nothing happen, till the 3rd press. Than display goes black and thats all .
Any idea where could be the problem or what I'm doing wrong?
Edit: maybe its related to the bootloader version, which is 09.10
Haldy said:
Hi, I flashed Recovery BootStrap v4 on the Defy MB525, but its not working. After flash and reboot, phone starts booting, but it ends up with the following screen.
Doesn't matter if I choose Recovery or continue. I can press the menu button (to choose recovery) and nothing happen, till the 3rd press. Than display goes black and thats all .
Any idea where could be the problem or what I'm doing wrong?
Edit: maybe its related to the bootloader version, which is 09.10
Click to expand...
Click to collapse
Based on first screenshots, Recovery installed. Now you need to install system.
Than display goes black and thats all - maybe have to wait
marcooleo said:
I had a successful installation of a december build and twrp 2,6x installed, everything ran just fine. But when the CM tells me there is a update and i download it does not install from recovery, get errormsg. Also apps like rom manager pro tells my phone is not compatible with any updates, and that i should install CWM recovery. So is it possible to install a real CWM on a defy mb526?
Click to expand...
Click to collapse
In principle it is possible, but it does not make sense.
Infocus M810/T/U thread. (Also wth interesting things for m812 holders.)
Infocus m810 thread on facebook
Note:
All roms on this page are remade to use with Infocus m810 so don't flash on m812. MULTILANGUAGE
Bootloader unlock (m812/m812):
Custom recovery (m810/m812):
SUT flashable images (SUT Factory tool 3.0.8):
SUT 3.1.4 cracked.
Video tutorial SUT flashing on Android 6
ROMS M812(A/I) VN2/PHX:
Android 5.0.2 m812 OFFICAL sut. (Suitable for m810 too) to be used with SUT
cm13 for m812(a) http://forum.xda-developers.com/showpost.php?p=68355126&postcount=1110
ROMS M810(T/I/U):VNA
25/07/16 CM13 beta 2 (release) http://forum.xda-developers.com/showpost.php?p=67901403&postcount=1074
20/03/16 Android 6 custom ROM (ported from m812 ver 617A firmware)
23/02/16 Android 6 custom ROM (ported from m812 ver 6130 firmware)
27/12/15 Android 5.1.1 (internal version 511C(D updated)) (port from m812 ver 511C firmware)
Official Android Kitkat 4.4.2 (VNA-1640-0-00WW-A02)
Older roms
Older ROMs are designed for recovery installation and need some knowledge:
Before the installing of thiose ROMs you must be common with Adb/fastboot driver and installation. working fastboot.exe and adb.exe here
Im the author of this work. So feel free to ask and report.
All you install from here is on your responsibility.
m810.ROM Android 5.0.2: (October 2015) MULTILANGUAGE.
This ROM is full upgrade, so its able to install over Android 4.4.2 ROMS.
How tot install: Russian installation site
1. Put the zip file to sdcard.
2. Connect phone by USB cable. Press and hold volume down+power buttons
(10s), when phone restarts, release power button after vibrating and keep
holding volume down button until FASTBOOT message appear on screen.
3. Download boot recovery https://yadi.sk/d/v_LrtBVdk8pAj and place in fastboot/adb
folder
4. Run in cmd: fastboot boot tw101_recovery_repack_by_titovich.img
5. When recovery booted, Choose firmware UPDATE502_M810_v1.zip and
install.
In the end you should get this error: apply parsed perms lsetfilecon from
/cache to u_object_r:cache_file:s0 failed operation not supported on transport
endpoint set_metadta: some changes failed.
Ignore it. Its issue of recovery.
6 Besides, ROOT and Xposed for 5.0.X framework preinstall can be copied to
sdacard and installed same time after rom installed from boot recovery.
7. Hold power button 10 sec and reboot.
Enjoy.
5.0.2 DOWNLOAD
m810.ROM Android 5.1.1A 08/10/15 The beta version of Lollipop
5.1.1A
ROM from official 511A m812.
Same install instructions as above
Main changes
-Wifi reception better;
-GPS;
-Added buttons config, e-compass, g-sensor calibrations to display menu .
5.1.1 DOWNLOAD.
XPOSED for 5.1.1 . ROOT
Note Xposed from version 5.0 and 5.1 are different!
To flash via SUT:
ODEXED ROM Android 5.1.1B 11/15 The beta version of Lollipop
5.1.1B from official m812 511B update ROM. |For SUT installer. With
unbricking feature.
- ROM designed for odexed files so it contains resized partition for system
(by titovich). means one you install the partition table will remain - 2.5gb for
system. original system parttion is less 2gb. You will be able to install all
m810 roms but I noticed you.
-not for XPLOSED framework. The ROM is full odexed. So don't try Xposed it
will fail;
-minor changes from my side diff to previous ROM;
-fixes from Infocus to battery life.
bugs: haptics not working for hard buttons (to be fixed)
To be installed via SUT utility SUT 3.0.8: DOWNLOAD
-install SUT (drivers will be installed with SUT);
-download zip with nb0 image. Unzip.
-open nb0 image file in SUT.
-Check "Normal Download" and "Erase data".
-Download ignore warning messages.
-Flash will complete in less than 1 min.
5.1.1B for SUT DOWNLOAD LINK2
EOL
Tweaks and enchantments :
M810 service manual
http://forum.xda-developers.com/showpost.php?p=68520451&postcount=1123
Edit boot logo m81X
http://forum.xda-developers.com/showpost.php?p=68956713&postcount=1163
Other party hears the noise durine the phone call
build.prop file
persist.audio.fluence.voicecall=false
Secret codes:
*#*#4636#*#*, *#*#653837#*#*, *#*#76278#*#* Settings.
Note, never tap "USA Band", otherwise you will need to reflash modem part or firmware to make phone back to work.
*#*#873#*#* Upload service
*#*#225#*#* Calendar
*#*#2324636#*#* , *#*#232#*#*, *#*#23273#*#* ,*#*#233#*#*, *#*#231#*#*, *#*#2324678#*#* CDA
*#*#278#*#* CPUDaemon
*#*#324#*#* DebugCfg
*#*#368#*#* Device manager
*#*#3721#*#*, *#*#6721#*#*, *#*#372#*#*, *#*#672#*#*, *#*#4867#*#* High Temperature Monitor
*#*#744#*#*, *#*#628#*#* Mobile Assistant
*#*#787#*#* PackageUsageTool
*#*#227#*#* Pandora Box
*#*#272#*#* Permission Control
*#*#33546#*#* Permission Detection
*#*#793#*#*, *#*#795795#*#* Power Detective
*#*#795#*#* power Monitor
*#*#277#*#*, *#*#3277#*#* Stability Monitor
*#*#28274663#*#* TeleService
Themes pack for 511B/C:
http://forum.xda-developers.com/showpost.php?p=64725810&postcount=429
Disable buttons backlight. (pale blue led shine instead). ROOT needed.
Replace system\lib\hw\lights.msm8974.so to get rid of buttons backlight. Instead, PALE blue led will be on.
Don't forget to backup the original file.
Advanced users can control that API /sys/devices/virtual/input/touch/light_led (with echo 0,1)
There is no any other control to disable or enable it.
XPOSED framework can't do anything too
Noise fix. When party on other side is claiming on noise above your voice.
This is typical issue of dual mic QUALCOMM devices on 5+ Androids. Edit built.prop
persist.audio.fluence.voicecall=true change to false
Enable DIAG port for QXDM (QPST). Rooted.
adb shell
su
setprop persist.sys.usb.config diag,serial,mass_storage,adb
Increase speaker volume
http://forum.xda-developers.com/showpost.php?p=64566136&postcount=330
Sound volume mod working on m810
https://www.youtube.com/watch?feature=player_embedded&v=DOo7sT_JIs8
IMEI, Serial number, MEID, MAC, BT changer. Service tool (m810/m812) DANGEROUS!!!
https://drive.google.com/open?id=0B3Wy4Ok3qGszcmZlMDFCbGdwUjQ
I was trying to follow up this conversation on 4pda but i don't speak russian and google translate does a terrible job.
So a couple of questions:
Is this a multilanguage rom?
Does 2g-3g-4g work?
What about wifi?
Thanks.
will Infocus m810 get android 5.1???
there is an ota update for m812 to android 5.1 but i am unable to find the file.
My phone its on the way.Im interesting this thread
sknipas said:
I was trying to follow up this conversation on 4pda but i don't speak russian and google translate does a terrible job.
So a couple of questions:
Is this a multilanguage rom?
Does 2g-3g-4g work?
What about wifi?
Thanks.
Click to expand...
Click to collapse
Yes, its Multilanguage.
2g-3g-4g work
sknipas said:
there is an ota update for m812 to android 5.1 but i am unable to find the file.
Click to expand...
Click to collapse
If you find it, pls share, it can be used for further development.
@ heineken78
Thanks for coming here at XDA
I am daily following your good works at 4PDA and I am actually with Titovich's 5.02 rooted and i feel more than satisfied.
I take the opportunity to send you my grateful Thanks.
I will install the new update and let comment as well. I hope and wish the system repartitioning will not give any issue ( I don't like playing with root partition!!).
Question: Was not possible to make the system file as lean as possible , eg removing apk that are unnecessary or available at Playstore for everybody choice in order to avoid this modification.
Regards
good work bro. looking for rom based on 5.1 . following this thread
lolo9393 said:
@ heineken78
Question: Was not possible to make the system file as lean as possible , eg removing apk that are unnecessary or available at Playstore for everybody choice in order to avoid this modification.
Regards
Click to expand...
Click to collapse
Stock reserved place in m810 for system partition is ~1,6 gb. Making firmware less, won't bring any changes, unless repartitioning it to lets say 1,1 gb. This operation needs lot of system knowledge from people who will install it.. And profit of changes will be only 500 mb? is nothing.
m812 has partition of 3 gb, that's huge, but suitable for oxdexed roms.
repartition means- you need to change start sectors of emmc in order to set sizes of system, cache. Everything before those partitions remain the same.
Ok, tweak as promised
http://forum.xda-developers.com/showpost.php?p=63576292&postcount=2
Wow,wonderful news... i will test it,downloading...
Hi Guys!
I would like to ask that ROM by titovich, which languages contains?
Thanks
@ heineken78
I've just finished the new Rom install. I followed instructions and had no issue . Rebooted via recovery and installed my stuffs.
-Wifi reception is the same as before and always weaker than my other phones. (minus 8 db)
-GPS IS NOT GETTING ANY FIX. 25 SAT in view and no one fixed.
-New Rom is a HUGE bit of improvement and feel more pleasant and very fast.
-DISPLAY is vibrant and very well set. Automatic mode is perfect also at night reading. good
- Battery leak in stand by is impressively low. less 1% full night. very good
THANKS TO THE TEAM BUILDING FOR THIS REALIZATION.
Can we suggest next challenge to make unlock the 3G 900Mhz Euro Band N°8 in a practical way?
I care less about the 4G...
---------- Post added at 03:52 AM ---------- Previous post was at 03:40 AM ----------
[email protected] said:
Hi Guys!
I would like to ask that ROM by titovich, which languages contains?
Thanks
Click to expand...
Click to collapse
Indonesian/Deutch/ENGLISH/Espanol/Filipino/FRENCH/Portugues/VIET/Russian/chinese/ and 2 symbolic i can't know ....sorry may be Hebreu,
lolo9393 said:
Can we suggest next challenge to make unlock the 3G 900Mhz Euro Band N°8 in a practical way?
I care less about the 4G...
---------- Post added at 03:52 AM ---------- Previous post was at 03:40 AM ----------
Click to expand...
Click to collapse
Yes Im trying that.
But for now, "adb reboot ftm" to reboot in ftm mode and enable qualcomm diag driver.
Then change nv's as written here and here. Uz mztool to calculate right entry's.
@heineken78
Thanks dude!
Its an official or unofficial translated ROM?
Im just ask the reason of hope, maybe put into some more languages too.
Im get this phone yesterday, it looks really great, but enter the recovery and fastboot mode its terrible.
Do you know TWRP or CWM recovery for this phone?
ilhi, i tried to disable backlight with .rar file you attached and it does work but i
heineken78 said:
TWEAKS:
1. Disable buttons backlight. (pale blue led shine instead). ROOT needed.
Replace system\lib\hw\lights.msm8974.so to get rid of buttons backlight. Instead, PALE blue led will be on.
Don't forget to backup the original file.
Advanced users can control that API /sys/devices/virtual/input/touch/light_led (with echo 0,1)
There is no any other control to disable or enable it.
XPOSED framework can't do anything too
Click to expand...
Click to collapse
ilhi, i tried to disable backlight with .rar file you attached and it does work but i can't adjust screen brightness in settings. Now its full bright and can't switch it low or automatic
a1dahiya said:
ilhi, i tried to disable backlight with .rar file you attached and it does work but i can't adjust screen brightness in settings. Now its full bright and can't switch it low or automatic
Click to expand...
Click to collapse
Dude, this is patched driver the from the build on first page. Drivers are different on stock502(titovich) so you may have an issue.
what should i do please help me
heineken78 said:
Dude, this is patched driver the from the build on first page. Drivers are different on stock502(titovich) so you may have an issue.
Click to expand...
Click to collapse
What should I do, please help me out
---------- Post added at 08:46 AM ---------- Previous post was at 08:38 AM ----------
a1dahiya said:
What should I do, please help me out
Click to expand...
Click to collapse
What drivers to change or any other change of value .....?
I'm on stock lollipop 5.0.2 rooted
I also tried to replace the patched file with original which I copied before replacing but nothing helped