Database Info

[ROM](Working Update.zip) -> Defy Update.zip Cookie Cutter Rom

Defy Froyo 3.4.2 Cookie Cutter Rom​
Q. How Do I use the Update.zip?
A. Go to Market & Download Defy SD-Recovery & Install..
1. Next place the Update.zip on the /sdcard via PC
2. Turn on MoTo Phone Portal ( SD-Recovery is SD Based so you need to Turn Off USB Mass Storage )
3. ADB Debugging does not have to be Turned Off on my version
Once Booted into the Recovery apply the update.zip
wait a few minutes & it should be done...
Please Reads the notes I left in the Update.zip if you build a Custom Update.zip, this will save you trouble down the road.
What's Flashed?
A. Boot.img
B. dev_tree
C. Moto Blur 3.4.2 Rom ( Yes I know it's not the latest, built off what I had )
D. UNO & TMO-TV Removed
E. Rooted ( SU & Superuser )
F. Busybox Installed to xbin
G. Rest of Rom is stock
Once installed, remove eugene.apk from /system/app ( Old boot strap that need adb turned off before rebooting / defy sd-recovery does not have this issue)
Q. I Edited the update.zip & Now it fails verf. in recovery when trying to flash!
A. example of signapk on signing the edited update
java -Xmx1024m -jar signapk.jar -w testkey.x509.pem testkey.pk8 update1.zip update.zip
Download: Original Post

To Update other parts of the Phone: Add this to the update-scripts for what you are flashing.
If we had all these Parts from 2.1 we could go back.
package_extract_file("lbl", "/tmp/lbl");
write_raw_image("/tmp/lbl","lbl");
delete("/tmp/lbl");
package_extract_file("device_tree.bin", "/tmp/device_tree.bin");
write_raw_image("/tmp/device_tree.bin","devtree");
delete("/tmp/device_tree.bin");
package_extract_file("cdrom", "/tmp/cdrom");
write_raw_image("/tmp/cdrom","cdrom");
delete("/tmp/cdrom");
package_extract_file("logo.bin", "/tmp/logo.bin");
write_raw_image("/tmp/logo.bin","logo.bin");
delete("/tmp/logo.bin");
package_extract_file("umts_wrigleyref_build.bin", "/tmp/umts_wrigleyref_build.bin");
write_raw_image("/tmp/umts_wrigleyref_build.bin","bpsw");
delete("/tmp/umts_wrigleyref_build.bin");
package_extract_file("cdt.bin", "/tmp/cdt.bin");
write_raw_image("/tmp/cdt.bin","cdt.bin");
delete("/tmp/cdt.bin");

Hey eugene,
Glad to see you working on Defy too
I think this will be major help for developers and btw that 3.4.2 version did you used? since there are many of them.
Thanks.

um. 107 I think since it has a floating update.zip someplace & sbf.
Ill update to the latest when I start building roms
Sent from my MB525 using XDA App

i don't understand. is the boot.img still the signed cg35.smg?
if so, can't we just use the cmw to do that?
can you post more detailed chages you made over cmw?
other than the signapk and usb debugging described.
many thanks.

eugene373 - great work!
racca said:
i don't understand. is the boot.img still the signed cg35.smg?
if so, can't we just use the cmw to do that?
can you post more detailed chages you made over cmw?
other than the signapk and usb debugging described.
many thanks.
Click to expand...
Click to collapse
Same here, i'm pretty interested in more details, thank you

this Zip File is for what ?
Thanks
Greetings

you can not use cwm due encryption. If you dont know what an update.zip is stick to nandroid...
This is for rom builders.
Heading out, when I get home ill make it clearer.
Though, now that I think about it cwm might be fine due to the nature of how it works.
Ill test later and let everyone know
Sent from my MB525 using XDA App

So we are able to install updates via the "normal" Motorola Recovery mode? So we are able to get a "unbrickable" Defy?
Edit: got it myself. The ZIP File won't be recognized by the motorola recovery... anyway thanks for your job

Now, what can SD-recovery do? Can it write other partitions, like cdt.bin?

Simplestas said:
Now, what can SD-recovery do? Can it write other partitions, like cdt.bin?
Click to expand...
Click to collapse
Yes. I can add the string if you would like
eugene373 said:
To Update other parts of the Phone: Add this to the update-scripts for what you are flashing.
package_extract_file("lbl", "/tmp/lbl");
write_raw_image("/tmp/lbl","lbl");
delete("/tmp/lbl");
package_extract_file("device_tree.bin", "/tmp/device_tree.bin");
write_raw_image("/tmp/device_tree.bin","devtree");
delete("/tmp/device_tree.bin");
package_extract_file("cdrom", "/tmp/cdrom");
write_raw_image("/tmp/cdrom","cdrom");
delete("/tmp/cdrom");
package_extract_file("logo.bin", "/tmp/logo.bin");
write_raw_image("/tmp/logo.bin","logo.bin");
delete("/tmp/logo.bin");
package_extract_file("umts_wrigleyref_build.bin", "/tmp/umts_wrigleyref_build.bin");
write_raw_image("/tmp/umts_wrigleyref_build.bin","bpsw");
delete("/tmp/umts_wrigleyref_build.bin");
package_extract_file("cdt.bin", "/tmp/cdt.bin");
write_raw_image("/tmp/cdt.bin","cdt.bin");
delete("/tmp/cdt.bin");
Click to expand...
Click to collapse

eugene373 said:
Yes. I can add the string if you would like
Click to expand...
Click to collapse
CwM can do exactly the same afaik, i've already made quite a few update.zip with it.
after reading all your notes, do you actually mean that we can't use format on those patitions?
if you do, well, i learned it the hard way, and delete_recursive also works for me.
thanks for putting up an excellent example if not for anything else, it's much needed.

racca said:
CwM can do exactly the same afaik, i've already made quite a few update.zip with it.
after reading all your notes, do you actually mean that we can't use format on those patitions?
if you do, well, i learned it the hard way, and delete_recursive also works for me.
thanks for putting up an excellent example if not for anything else, it's much needed.
Click to expand...
Click to collapse
Correct, you can only format with the stock recovery ( Hence the reason why I used the Stock Recovery ) any Partition with cwm recovery will cause a non-booting system..
regarding cwm I've not tested it, so Likely it will work.. Steven is still working on the cwm recovery & there is no point in me adding another cwm bootstrap recovery... Mine is just pure stock & works perfect.
I'm still weeding through the /bin /etc file's to find exactly what needs left...
but main goal was to provide an example of what is needed to make an update.zip with out breaking the system.

what exactly is the benefit of this new method?

drsouly said:
what exactly is the benefit of this new method?
Click to expand...
Click to collapse
um? Your joking right!
Update versus a nandroid, I would have thought it was a no brainier....
Build & edit roms on the fly + being able to flash boot.img & downgrading is fine without sbf unless you screw up completely..

eugene373 said:
um? Your joking right!
Update versus a nandroid, I would have thought it was a no brainier....
Build & edit roms on the fly + being able to flash boot.img & downgrading is fine without sbf unless you screw up completely..
Click to expand...
Click to collapse
ok now i got it thx

drsouly said:
ok now i got it thx
Click to expand...
Click to collapse
no problem, wasn't sure if you was being a smart-ass or honestly didn't know...
either way, sorry If I offended you.
~Eugene

I didn't understand yet . I can or not apply the update file using stock recovery?
EDIT: forget I understood now.
Sent from my MB525 using XDA App

psicodelico said:
I didn't understand yet . I can or not apply the update file using stock recovery?
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
Read OP.... Download Defy SD-Recovery from Market

Yeah, I read again slowly and understood.
Sent from my MB525 using XDA App

[RECOVERY]CWM-Based Recovery 5.0.2.8 For P999(Internal & External SD)

The image was provided by Mr Rusty over on the P990 thread and i asked him if we can have an update..well he gladly helped out so don't forget to thank Mr Rusty over on his Thread..
I repacked and added a script that you will just run in order to flash this CWM version..(Thanks to Russ for the script)
From his Thread:
By request a quick explanation of the difference between the two recoveries:
Usually, your recovery image will look on the external SD card for ROMs to flash, and backups to restore, and the external version here is no different. For the most part that is fine and dandy (unless you don't have an SD card I guess), however the stock O2X mounts it's internal SD card as /sdcard, which confuses ROM Manager a fair bit.
The internal version of the recovery mounts the internal storage as /sdcard as well, so ROM Manager can find backups it's made etc.
NOTE: Backups made with v5 are not compatible with earlier versions.
Click to expand...
Click to collapse
BIG Credits goes to Koush as well for his great work for innovating the CWM..
Get it Here: CWM 5.0.2.8 For P999 or from Here
Instructions on HOW to use/WHAT to do:(For Windows)
- Once you have downloaded the Package from the link Above..extract it to a Folder..
- Inside the folder all you have to do is look for the flash-recovery_xp.bat file..
- now turn your G2x OFF..
- remove the BATTERY and make sure your G2x is not connected to the PC via USB
- Press the VOLUME DOWN button together with the VOLUME UP..
- now CONNECT the USB Cable..
- If by all means Windows prompts for a new DEVICE you have to install the APX drivers from here(extract the package and manually install from this source)..
- Else if windows does not prompt OR you are already done installing the APX drivers you can now proceed on Running the flash-recovery_xp.bat by double clicking it..
- Choose 1 and Then press Enter..Wait for a few seconds till it prompts you that the FLASH was successful..IMHO you ought to wait another 5 more seconds after the prompt for not to have issues..
- After that Reboot into CWM by Pressing Power Button together with VOLUME DOWN til you see the LG Logo with waves..upon seeing that now release the buttons and wait for the CWM menu..
For Linux/Ubuntu Users:
- Download the Package
- Extract the folder somewhere
- Now turn your Phone OFF and DO NOT plug the USB cable yet..
- Now while Phone is OFF press VOLUME UP and DOWN together and now PLUG the USB cable in..keep them held together throughout the process..
- Run the Terminal and locate the Directory on where the Files are located..
- Type the ff:
Code:
chmod +x flash-recovery.sh
./flash-recovery.sh
- Once DONE you can now reboot..
FAQ:
Q: I am getting NVflash errors?
A: You might be on a BAD Cable or either way upon installing the drivers do a reboot..also DO THIS ON WINDOWS XP..on Windows 7 there are circumstances that the device is not recognized properly..also make SURE your unit is a P999 or P999DW(my unit is P999DW and touch WORKS!!) and not P990 or SU660..
Q: My device is not Recognized?
A: You have to download the APX drivers from one of the instructions above
Changelog: Github Source
Thanks and also vote for the page..

Seems the Chinese are on to this files too..lolz..

Thank you!! It flashed perfectly, no issues here.
Troy.

thegreenfamily04 said:
Thank you!! It flashed perfectly, no issues here.
Troy.
Click to expand...
Click to collapse
Glad it worked??

So internal and external mounting are all fine with this one?
Sent from my LG-P999 using xda premium

Wow thanks man. I may have to ask a out posting the CWM touch to the G2x.
Sent from my LG-P999 using xda premium

Just flashed it with no problems , when are we getting the touch CWM? Now that will look sexy

thy for your work. coming from ClockworkMod 5.0.2.0 what are the differences / improvements? could someone explain please?
thanks in advance

Just an update: I flashed a MIUI rom (Look in my sig) used the "Nullifier 2.0" (Double wipe) and flashed the current Trinity Kernel all with no issues
Phone is running GREAT now! Thank you once again
Troy.

Волк said:
Wow thanks man. I may have to ask a out posting the CWM touch to the G2x.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
I was thinking the exact same thing. Seems strange to me that Koush made it for the O2x and not for us.

Im getting a nvflash error when trying to install the new clockwork.
It says check apx driver and usb cable. The drivers are already installed so Im thinking its the usb cable, but not sure.

MWBehr said:
I was thinking the exact same thing. Seems strange to me that Koush made it for the O2x and not for us.
Click to expand...
Click to collapse
the recovery's on a different partition, might make it a pain in the ass to access the touch drivers...
or he might just like the o2x more (everyone likes those Europeans more than us anymore)

Touch Recovery
I'm just gonna throw this out there, just because I wanted to try, I flashed the O2x Touch Recovery to my G2x. Everything as far as the application goes worked, touch to select, ect. The only problem is when you ask it to do something, the mounts are wrong, naturally. What I'm getting at is that both devices use cwm 5020, obviously, mounts changed. How hard would it be to decompile both versions of 5020 and apply the differences to the new touch recovery app?
p.s. for those who wonder how I flashed touch to my G2x, I just swapped out the recovery images in the one-click nvflasher, pretty simple. when you're done, put back correct file, nvflash again.

mustangtim49 said:
I'm just gonna throw this out there, just because I wanted to try, I flashed the O2x Touch Recovery to my G2x. Everything as far as the application goes worked, touch to select, ect. The only problem is when you ask it to do something, the mounts are wrong, naturally. What I'm getting at is that both devices use cwm 5020, obviously, mounts changed. How hard would it be to decompile both versions of 5020 and apply the differences to the new touch recovery app?
p.s. for those who wonder how I flashed touch to my G2x, I just swapped out the recovery images in the one-click nvflasher, pretty simple. when you're done, put back correct file, nvflash again.
Click to expand...
Click to collapse
It's all in the ram disk. Just swap out the vold.fstab in the ram disk. Recovery images are simply boot.imgs.

Interesting, because the differences are only 1 partition. And using the O2x CWM to wipe /system (iirc) would just wipe our internal SD. Ours is partition 7 theirs is partition 8, our partition 8 is the internal SD. Since the phones are 99% the same, it should be that simple. and I need to get up early... I do have one untested tool for decompiling a boot.img....
@Kairi: Can you mirror this on Dropbox? Or somewhere not blocked by my work? Wifi at home is down and I am just chewing away at my data with having to tether.

Волк said:
Interesting, because the differences are only 1 partition. And using the O2x CWM to wipe /system (iirc) would just wipe our internal SD. Ours is partition 7 theirs is partition 8, our partition 8 is the internal SD. Since the phones are 99% the same, it should be that simple. and I need to get up early... I do have one untested tool for decompiling a boot.img....
@Kairi: Can you mirror this on Dropbox? Or somewhere not blocked by my work? Wifi at home is down and I am just chewing away at my data with having to tether.
Click to expand...
Click to collapse
http://db.tt/rEpbpRfA here you go. Really interested on what you can do with it
Sent from my LG-P999 using Tapatalk

Волк said:
Interesting, because the differences are only 1 partition. And using the O2x CWM to wipe /system (iirc) would just wipe our internal SD. Ours is partition 7 theirs is partition 8, our partition 8 is the internal SD. Since the phones are 99% the same, it should be that simple. and I need to get up early... I do have one untested tool for decompiling a boot.img....
@Kairi: Can you mirror this on Dropbox? Or somewhere not blocked by my work? Wifi at home is down and I am just chewing away at my data with having to tether.
Click to expand...
Click to collapse
that might work. Id try it out myself if i didn't f up my Linux install...
Nvidia graphics got the best of me there too
Sent from my LG-P999 using Tapatalk

Works as advertised! Thanks!

works great! thanks!

So, my idea worked? I'm not at home and since I'm a collision tech by trade, my boss don't like me playing with my phone. Volk, if you read this pm me and fill me in if you can. Thanks brother.
[email protected]

[Q] Ubuntu SBKv2 & Asus Stock Apps.

First does anyone have a .zip for the Asus stock apps? I had an older copy of the revolver removed apps file and I accidentally deleted it, the one that is currently linked on the revolver ROM shows as corrupted.
Has anyone been able to successfully Dual-boot Ubuntu on sbkv2 devices? What is your current method to doing so?
I tried the modified version of OLiFE with wheelie but ended up in an APX boot loop and had to flash back to stock.
I tried to use my own ROM (revolver) and the net-install version of ubuntu so perhaps I 'injected' them incorrectly.
Could not find much of a guide to do this...
Was interested in trying franks tools because that seems to be the easiest option (My main OS is windows but I have Ubuntu installed on an flash drive)
I tried the method here http://forum.xda-developers.com/showthread.php?p=23428126 but I didnt add or copy the .lib modules and my recovery was internal sd access only (working on updating that)
Plus the whole pseudo dual boot thing seems like a pain in the ass...
Any thoughts on the net install version of ubuntu?
How do you go about flashing or updating Roms when you are dual booting?
Thanks!

Wanna try my tutorial?
Well its bit messy, but i am lookign for osme fixes in ubuntu.

The Part where I get confused is the boot image and system image I may have messed up there?
Where do you place/name the net-install img?
Also as far as the rom and kernel go do you have to get that set up and then do a backup and use that or do you still have access to android recovery to flash zips?
Thanks!

fauxsoul said:
The Part where I get confused is the boot image and system image I may have messed up there?
Where do you place/name the net-install img?
Also as far as the rom and kernel go do you have to get that set up and then do a backup and use that or do you still have access to android recovery to flash zips?
Thanks!
Click to expand...
Click to collapse
OH SHOOT! i didn t say where to paste >.<
Ok paste in the image folder.
its inside he olife folder.
Yeah you have set up roms and kernel.
I dont recommend to go stock, but AR HD. In find its only proper working stock ICS and a working usb.
Further I had some difficulties installing ... Libre if oyu want to use as office.

vietchinh said:
OH SHOOT! i didn t say where to paste >.<
Ok paste in the image folder.
its inside he olife folder.
Yeah you have set up roms and kernel.
I dont recommend to go stock, but AR HD. In find its only proper working stock ICS and a working usb.
Further I had some difficulties installing ... Libre if oyu want to use as office.
Click to expand...
Click to collapse
So install the rom and kernel you want to use, do a backup then copy the system & boot imgs from the backup.
From what i understood you have to rename the net-install img to ubuntu.img? Is that correct?
Yeah definitely planning on using it for word editing etc (for school)
Right now I'm using team EOS nightlys for the rom and the kat kernel.
It's running very well so i might stick with that.
So you are not able to flash updates for android once you go dual boot?
Thanks I will probably try this out again when I get home later.

fauxsoul said:
So install the rom and kernel you want to use, do a backup then copy the system & boot imgs from the backup.
From what i understood you have to rename the net-install img to ubuntu.img? Is that correct?
Yeah definitely planning on using it for word editing etc (for school)
Right now I'm using team EOS nightlys for the rom and the kat kernel.
It's running very well so i might stick with that.
So you are not able to flash updates for android once you go dual boot?
Thanks I will probably try this out again when I get home later.
Click to expand...
Click to collapse
You mean recovery? If you want recovery u need to wait for Franktools SBk2v, but it cause apx bootloop so its removed.
Backup ur data to with recovery or titanium backup.
I recommend to use normal ubuntu ( with GDM) and then install enlightment.
Why i recommend normal ubuntu, becasue it was only working libre office, but you can try something else

So far no luck still isn't working.
Maybe it's the net-installer I'm having issues with I might just try the regular ubuntu.img if franks tools aren't back up soon (I just wanted to try the easier way.)
I tried just installing linux by itself and got some penguins and scripts running but it was in apx boot loop after that.
Had to flash to stock and rebuild.
I think I might wait for kenshin to fix franks tools (which might take a while from the looks of it)

fauxsoul said:
So far no luck still isn't working.
Maybe it's the net-installer I'm having issues with I might just try the regular ubuntu.img if franks tools aren't back up soon (I just wanted to try the easier way.)
I tried just installing linux by itself and got some penguins and scripts running but it was in apx boot loop after that.
Had to flash to stock and rebuild.
I think I might wait for kenshin to fix franks tools (which might take a while from the looks of it)
Click to expand...
Click to collapse
U got teamviewer and skype or somesort?
I can help u with that if you dont understand any thing of the tutorial.
IF you add me at skype (naruto.fbi any one can add me ) i can help u :].
Did you have any errors?
I had error thatkernel was to big ( 9.4 mb) i change some code adn i could flash it.
Maybe u have the same?
I hear form u soon

No errors, Have had my rom and kernel installed. Did the android backup using olife. Copied the olife backup files and renamed them (boot and system IMG files) to the images folder.
Then flashed device with dual boot tried both android and linux as the default and neither way worked.
Tried installing linux only and it doesnt work.
I just keep getting apx boot loops.
I dont have team viewer or skype so I was wondering if you might share your olife folder that you used to install (in case I was doing something wrong)
but if you have personal info in the backups i understand.
I think I might take you up on that offer and hit you up on skype or with team viewer, but maybe later this week because I'm going to be very busy with work/school for a few days.
Thanks for your help

fauxsoul said:
No errors, Have had my rom and kernel installed. Did the android backup using olife. Copied the olife backup files and renamed them (boot and system IMG files) to the images folder.
Then flashed device with dual boot tried both android and linux as the default and neither way worked.
Tried installing linux only and it doesnt work.
I just keep getting apx boot loops.
I dont have team viewer or skype so I was wondering if you might share your olife folder that you used to install (in case I was doing something wrong)
but if you have personal info in the backups i understand.
I think I might take you up on that offer and hit you up on skype or with team viewer, but maybe later this week because I'm going to be very busy with work/school for a few days.
Thanks for your help
Click to expand...
Click to collapse
Well i can send u my olife folder.
It contain the 2.1 gb ubuntu (11.10) and the net installer. Also android system are: AR HD( ICS) with gevour kernel if you dont mind.
It also contin a jhinta kernel which you can flash over it. Flash it with chromeOS ( in update and then advance)
Also i change some size for the kernel.
Kernel size was to big.
All fixed :3.
I will send u the folder as soon as i can ^^.
Few backdraws at the moment with ubuntu:
No flash support anymore by adobe (few alternetives like gapps( to slow and laggy) and lightspark(need to be tested)
Libre has some difficulties installin in gnome classic install of net installer and englightment.
At the moment libre works in ubunu with gdm.
Even linux for tegra installed it seems like it cant see the processor ( currenly in net-installer, it does show in livistie ubuntu.),
Google chrome cant be installed :\ ( no arm packages).
Net-installer can have some frustation on the wifi configuration.

fauxsoul said:
Any thoughts on the net install version of ubuntu?
Click to expand...
Click to collapse
Have you compared the pros & cons using my version of Debian/Ubuntu Android integration?
http://forum.xda-developers.com/showthread.php?t=1780378
I'm running it on my TF101 with flying colours.

kuisma said:
Have you compared the pros & cons using my version of Debian/Ubuntu Android integration?
http://forum.xda-developers.com/showthread.php?t=1780378
I'm running it on my TF101 with flying colours.
Click to expand...
Click to collapse
I think its slow ?
becasue its chroot.
I dont know.
At the moment i am trying allot of things ^^.

vietchinh said:
I think its slow ?
becasue its chroot.
.
Click to expand...
Click to collapse
Slow? You tell me.

kuisma said:
Have you compared the pros & cons using my version of Debian/Ubuntu Android integration?
http://forum.xda-developers.com/showthread.php?t=1780378
I'm running it on my TF101 with flying colours.
Click to expand...
Click to collapse
That actually looks pretty cool, I really wanted ubuntu for a more powerful text editor and maybe a few other things.
Might be more convenient.
I'm going to try it.

fauxsoul said:
That actually looks pretty cool, I really wanted ubuntu for a more powerful text editor and maybe a few other things.
Might be more convenient.
I'm going to try it.
Click to expand...
Click to collapse
If a powerful text editor is all you need, I'd say this solution is way overkill.

kuisma said:
If a powerful text editor is all you need, I'd say this solution is way overkill.
Click to expand...
Click to collapse
Plus I just want to play around with it in general.
I'm sure you can understand that feeling.

fauxsoul said:
Plus I just want to play around with it in general.
I'm sure you can understand that feeling.
Click to expand...
Click to collapse
Yes indeed.
If you are skilled, this is quite a neat solution giving you lots of power over the Android device. But since it can be somewhat tricky for the beginner to implement, if only a GNU/Linux environment is needed, and not the control over the Android environment, it is much easier to run the GNU/Linux environment jailed, instead of Android jailed as here.
But this is of course way much cooler.

kuisma said:
Slow? You tell me.
Click to expand...
Click to collapse
I take my words back ._.

Using RK Batchtool on a bricked Joying 5.1.1 headunit

Hi Everyone,
I did a stupid thing and flashed my head unit with a 4.4.4 rom.
I can no longer get into recovery unless I use sd_Firmware tool. sd_Firmware tools doesn't restore the image though.
I am trying to use RK Batchtools to reimage the device but I cannot get the head unit to show up in device manager.
Am I correct in using any of the 2 USB leads that come out of the back of the head unit (normally used for 3g adapter or USB thumb drive) with a A to A USB cable to join to the laptop?
Is there any button pressing process required for it to connect to the laptop?
Many many thanks in advance. So angry with myself.

Same problem, Someone Can help us?
Inviato dal mio Redmi Note 3 utilizzando Tapatalk

colostro said:
Same problem, Someone Can help us?
Inviato dal mio Redmi Note 3 utilizzando Tapatalk
Click to expand...
Click to collapse
OK Success, my head unit is back up and running.
I believe (somebody please correct me if i'm wrong) that the issue lies in the MCU.
I used sd_Firmware tool to generate a bootable SD card. This on it's own should've been enough to flash the device but mine would fail with an error asking to remove the SD card. Once you remove the SD card you're presented with a recovery menu.
Have a USB stick with ONLY the mcu img file, select restore from USB + wipe. This will re-apply the MCU file.
One that is done, the device will reboot but will not post. Restart the device using the boot SD card once again to repeat the process but replace your MCU file with your dupdate.img file.
This should get your device bootable again. Don't forget to load the recovery menu from the device and select the wipe data + cache option.
Let me know how you go

Thanks, i'm going to try.
I still used sd_firmware tool, but the sw doesn't recognize my sd card (Windows is ok, recognize it)...
I Can put my unit in recovery mode
Inviato dal mio Redmi Note 3 utilizzando Tapatalk

colostro said:
Thanks, i'm going to try.
I still used sd_firmware tool, but the sw doesn't recognize my sd card (Windows is ok, recognize it)...
I Can put my unit in recovery mode
Inviato dal mio Redmi Note 3 utilizzando Tapatalk
Click to expand...
Click to collapse
run SD firmware tool "as administrator" if you cannot see the tool.
Are you saying you can enter recovery mode without the use of a bootable SD card? Because if that's the case, we do not share the same issue.

We have not the same issue, i know.
After using Malaysk rom, my unit doesn't boot anymore, I entered in recovery mode and trying to update original rom but i receive an errore like this "device block required"
EDIT: I DID IT!!!!!!! Using your method (first MCU and then ROM), I recovered my hed unit... Thanks so much.... GREAAAAATTTTTT
Inviato dal mio Redmi Note 3 utilizzando Tapatalk

Can you please tell me what you put onto your drive to make it "bootable" ?
Did you put the MCU file onto the drive or the firmware ?
My HU does nothing its just black screen
Thank You !!

You have to put firmware file (much greater file), then put the sd into gps slot and at least turn on your head unit and wait
Inviato dal mio Redmi Note 3 utilizzando Tapatalk

colostro said:
You have to put firmware file (much greater file), then put the sd into gps slot and at least turn on your head unit and wait
Inviato dal mio Redmi Note 3 utilizzando Tapatalk
Click to expand...
Click to collapse
Thank you I tried this but the tool wont write the file to the sd card as its not a .img file
Do I need to rename it ?
Thank You

have you original dupdate.img? I tried with my original head unit file and works fine

colostro said:
have you original dupdate.img? I tried with my original head unit file and works fine
Click to expand...
Click to collapse
No I dont =\

What version of MCU have you?

I'm actually trying to unbrick my Allwinner R16
I dont even know if this will work
Quadcore-r16-1.6g
Android 4.4.2
MCU Version
5.3.18-98-13-E50201-160406
SYSTEM VERSION
4.5.9_20160322

Cid6.7 said:
I'm actually trying to unbrick my Allwinner R16
I dont even know if this will work
Quadcore-r16-1.6g
Android 4.4.2
MCU Version
5.3.18-98-13-E50201-160406
SYSTEM VERSION
4.5.9_20160322
Click to expand...
Click to collapse
I'm Sorry but i can't help you... I don't know
Inviato dal mio Redmi Note 3 utilizzando Tapatalk

Cid6.7 said:
Thank you I tried this but the tool wont write the file to the sd card as its not a .img file
Do I need to rename it ?
Thank You
Click to expand...
Click to collapse
The SD card is just to boot the device, flash the MCU from a usb flash drive.
You do have to create the SD card using the update.img file though. Get one from the "Factory images" thread.

Factory images thread ? I haven't seen this got a link ?
Thank You !

http://forum.xda-developers.com/and...ent/rom-factory-firmware-rk3188-mtcd-t3366561

morgish said:
OK Success, my head unit is back up and running.
I believe (somebody please correct me if i'm wrong) that the issue lies in the MCU.
I used sd_Firmware tool to generate a bootable SD card. This on it's own should've been enough to flash the device but mine would fail with an error asking to remove the SD card. Once you remove the SD card you're presented with a recovery menu.
Have a USB stick with ONLY the mcu img file, select restore from USB + wipe. This will re-apply the MCU file.
One that is done, the device will reboot but will not post. Restart the device using the boot SD card once again to repeat the process but replace your MCU file with your dupdate.img file.
This should get your device bootable again. Don't forget to load the recovery menu from the device and select the wipe data + cache option.
Let me know how you go
Click to expand...
Click to collapse
I was able to successfully flash an MCU using your USB method. Now to flash the rom image do I select restore from UBS + Clear all or just restore from USB in recovery? What's the difference?
Also, what does the 'upgrade' checkbox on the sd_firmware tool do vs. just drag and dropping the image file in windows? This piece of software is perplexing to me. Is its main function to create disks (cards or sticks) that will flash a device w\o having to go through recovery?

rotomoto said:
I was able to successfully flash an MCU using your USB method. Now to flash the rom image do I select restore from UBS + Clear all or just restore from USB in recovery? What's the difference?
Click to expand...
Click to collapse
I believe you can upgrade and keep your settings etc if you're going from one version to the bump up.
If you're going from major version diferences (or recovering from a big fault) it would be best to do the clear all (same as factory reset).
If you have flashed your MCU successfully, you may find you can use the unit's recovery and not the "bootable sd card"
rotomoto said:
Also, what does the 'upgrade' checkbox on the sd_firmware tool do vs. just drag and dropping the image file in windows? This piece of software is perplexing to me. Is its main function to create disks (cards or sticks) that will flash a device w\o having to go through recovery?
Click to expand...
Click to collapse
I wouldn't worry too much about the sd_firmware tool settings, simply use it as a boot disk to get into recovery then use recovery to reflash the device (As you have done with your MCU file)
Yes that's correct, flashing a device without using it's own recovery. I believe it's for band new units that has never had software (recovery) flashed?

morgish said:
I believe you can upgrade and keep your settings etc if you're going from one version to the bump up.
If you're going from major version diferences (or recovering from a big fault) it would be best to do the clear all (same as factory reset).
If you have flashed your MCU successfully, you may find you can use the unit's recovery and not the "bootable sd card"
I wouldn't worry too much about the sd_firmware tool settings, simply use it as a boot disk to get into recovery then use recovery to reflash the device (As you have done with your MCU file)
Yes that's correct, flashing a device without using it's own recovery. I believe it's for band new units that has never had software (recovery) flashed?
Click to expand...
Click to collapse
Hi,
does anybody know why I get this error in the SD Firmware Tool, every time when I tick "SD Boot"? My device is bricked and it doesn't enter recovery mode. Therefore I tried this tool, as I don't have a USB A-A. Creating the firmware SD without ticking "SD Boot" works fine, but trying to make it bootable gives me this error. Tried with 3 versions of the firmware for my device. Started the tool as an administrator, on a win7.
Thx in advance!

"auto deploy" question

Hi,
I've received a chinese X86-64 tablet (Cube iwork10 ultimate) from someone to make this tablet run few apps including Linux. I rooted the device, installed everything needed, configured it and it works perfectly well. I also used TWRP to backup the whole tablet.
The problem is this: I need to replicate this tablet to few others (same model) tablets. I can make a full backup with TWRP, stick a MicroSD on a new tablet, oem unlock it, boot TWRP and do a restore from image, which works...
But I'm looking to do it automatically and not manually, preferable with some script using fastboot, so my questions are:
Is there anyway to boot using fastboot and running a restore? (the image will be on the MicroSD which will be inserted prior to restore)?
Is there any app (the device is root) which is capable of copying the entire tablet to some big "update.zip" so I can use it with "fastboot update"?
How do I "feed" the fastboot boot recovery.img with parameters to TWRP to auto start restore?
Thanks

Search and download system firmware image zipped for Nexus devices or OnePlus One: they use a flashall.bat batch script that you could easily modify to your needs..
I'm not to my PC now but I could link it later..
Inviato dal mio P80h(D4C5) utilizzando Tapatalk

My problem is that in order to create such a zip, I need somehow to pull from the tablet all the partitions as an images format, any links how to do this would help a lot

As far as I understand you want to make partitions image once and then restore them on many devices, don't you?
In that case you could use dd command from a rooted device or Macrium Reflect from Windows side of the tablet..
EDIT also, don't know which variant you own but all image partitions are already available (stock not rooted or already rooted)
Inviato dal mio P80h(D4C5) utilizzando Tapatalk