Here I am uploading android partition dumps, you can use these files to fix your bricked devices. These images were rooted stock dumps of Indian version, build number is 13040. Use fastboot method to flash these images.
Warning: Please use them only if your device was bricked.
boot.img
recovery.img
recovery_bak.img
system.img
All those dumps were created using "yaffs" tool.
Now download the attached files below, extract fastboot+adb file and extact its contents to "c:\tools\", such that adb.exe and other files will be in c:\tools\ folder.
Now extract and install the second file (venue drivers windows 7).
Now go to command prompt and switch to "c:\tools" directory (cd c:\tools).
Now enter the following commands at c:\tools\>,
c:\tools\>fastboot flash system system.img (this command flashes system.img to system partition).
simillarly.
c:\tools\>fastboot flash boot boot.img
c:\tools\>fastboot flash recovery recovery.img
syntax:
\>fastboot flash []
Hope this guide helps...
Please let me know if you are successful...
Please click on THANKS if you find it useful.
Thank you...
If you have no idea on how to flash those dumps please let me know. I can post step by step procedure on how to flash them if you need.
After checking the contents, I reupload the set to match the set I already have.
Can you confirm that these images are clean, unmodified dumps? The ones I already have come from brand new devices and this was the first thing done to them. (they were used slightly by normal users, but that wont affect it, they didnt touch anything in /system beyond rooting it to dump the partitions)
Edit: I have downloaded them and compared them to the dumps I already have, 304 is slightly modified but I'm pretty sure I was able to fix it back to likely what it shipped with.
Now I was out of my wifi coverage area, ill test them when I go home.
Sent from my Dell Venue using XDA App
I mean ill test your build when i go home.
Sent from my Dell Venue using XDA App
rapol.goutham said:
If you have no idea on how to flash those dumps please let me know. I can post step by step procedure on how to flash them if you need.
Click to expand...
Click to collapse
thanx!!!!!!!
rapol.goutham said:
Here I was uploading android partition dumps, you can use these files to fix your bricked devices. These images were rooted stock dumps of Indian version, build number is 13040. Use fastboot method to flash these images.
boot.img
recovery.img
recovery_bak.img
system.img
All those dumps were created using "yaffs" tool.
Click to expand...
Click to collapse
how do I do it?!!!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Follow the above guide. And those drivers works with Windows 7 only, if you need drivers for windows xp plz let me know, ill upload them later, because i was running my internet on slower connection.
Dont mean to sound ungrateful,
but you should use the cleaned copy I posted on here.
The dump you posted was strangely missing a couple files and still had the dump tools. I cleaned it up and reincluded files that were missing.
It's only a couple files and doesnt really change how it works. But I only host as close to original copies that I can. The cleaned one should be virtually identical to a fresh install.
Just as much I actively maintain the fastboot+adb.zip package. The file name doesnt change as it's merely a copy of the latest one. You can check the folder it's in and older revs are there.
Hey manii, as you told me before that you don't have Dell Venue but Dell Streak, then how could you tell that those dumps are were missing some files? Those are the dumps that I was currently running on my Venue, and I haven't experienced any problem till now.
And i can't guarantee that the files you feel that were missing from Dell Venue when compared with Dell Streak works on Dell Venue.
If you want to share this builld in your forums leave the dumps as it is and share them, so that no bugs will arise.
The venue s5 s7 are all built off the same codebase.
I have ~90% of every known rom for those 3 devices
Doing a diff on yours vs the others reveals that some files are missing, such as /system/etc/hosts.
This is one of the files that is universally existant. It's in every rom on all 3 devices. There's some more that are missing, and clearly shouldnt be. But I cant recall off the top of my head.
You can do a diff vs the filesystem of 307 and that reveals most of it. There is the highly unlikely event that it was missing at the source. It's always possible but for the example of hosts I dont believe it's this case.
None of the missing files will cause run issues, just merely missing. The majority are in app\ and i believe there was only 1 that isnt bundleware in that case (ie it's a stock android app) but I cant recall for the moment which one that was.
For the moment I am the most knowledgable person on the s5/s7/venue filesystem layout. Though not so much on what each specific file does (as I dont code dev, but it's not difficult to look it up on google for specific files).
One thing i can say is it's unlikely that 304 ever existed as an update.pkg as system/etc/install-recovery.sh is missing. If it's missing by default that is essentially the definition of this, unless you removed it yourself (which I dont believe is the case)
yes you are right, I have modified host file to remove adds in applications but the file exists and install recovery.sh file also existed and every thing works fine but try those dumps only in case of emergency.
can you try those images on your streak.? If it works fine plz let me know, then ill try streak roms on my Venue.
And install_recovery.sh was also modified to support 2nd partition on sdcard.
It should load fine with the SD kernel, it will run but it's not useful beyond deving.
If you try and load a venue rom on a streak, the screen will be upside down and wifi doesnt work. There might be more but I havnt done any extensive testing on it
How could you boot through sdcard.
Sent from my Dell Venue using XDA App
You cant, not until someone makes a new bootloader.
With the popularity of the venue this is likely to be never
how do connect the dell venue for the command prompt to see the phone
thanx!
nexio said:
how do connect the dell venue for the command prompt to see the phone
thanx!
Click to expand...
Click to collapse
go to this link and download ADB Easy, install then connect your phone
Please be post "step by step" how to do it. Thanks
I have already posted step by step guide, please read the thread completely, this thread includes how to flash guide also. If there were any doubts plz ask me.
Sent from my Dell Venue using XDA App
Related
Can some help me ?
send me links to do it without messing up my phone?
http://streakdroid.com/?page_id=92
it thought ide post this to help others on a few steps that i posted on the other forum on using the great guide/site streakdroid,to take a dell streak,mine is white,from att and go to 2.2 froyo....but was'nt very clear "to me" in a few steps.....so i'm trying to make it easier to understand for some.....
http://streakdroid.com/?page_id=92
this is the qdltool...called "repair tool" http://streakdroid.com/?page_id=15&did=8
....once you download it,and run it,it will create a folder with the qdltool and some files in it,you need to put the other files you download from the download page http://streakdroid.com/?page_id=15 into the qdltool folder"do not unzip the rom .zip folders like 1.6.0"just put them in the qdltool folder as in my pic
this is how i did it.....i downloaded all the files,put them where they needed to go....installed streakdroid 1.6.0 using the qdltool......you need to put the 1.6.0 and recovery and amss image in the same folder as your qdltool is unzipped into.......i also put a copy 1.5.1,1.6.0 and 1.6.1 .zip files in the qdltool folder and also on my sd card, on my sd card to have them to boot into from ....clockwork recovery.... later ,if i wanted to.
you need to make sure you have the qualcomm diagnostic 9002 driver installed right and connected in the qdltool before you run it......watch this video http://streakdroid.com/?page_id=78
you might have to try this sevearal times.....dont worry if its stuck and wont boot.....
alot of people take their phone back when they think its "bricked" when its not....they just freak out,and take it back before trying more options and or being persistant.
you just have to try some different steps....ofcourse all the files,drivers i9nstalled and in right location.......you can use infranview app to take screenshots of how you have your folder setup to post here if you need someone to better help you.....like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i put a copy of 1.5.1 and 1.6.1 .zip files in just to have a copy of them here,and on my sd card......but you only need the 1.6.0.zip file in to go to 2.2 froyo
mine is the white dell bought at bb a week and a half ago
also if you want to flash the clockwork recovery ,i had problems and stoney73 helped me out here
Originally Posted by mokokawi
i tried to follow the instructions.....but i need a detailed guide on this part at the guide on streakdroid that i had problems with steps 8 to 11 here
http://streakdroid.com/?page_id=122
8.Open a command window and use ‘cd’ to change to the same directory as qdltool.
9.Run: fastboot -i 0x413c flash recovery recovery.img
10.Run: fastboot -i 0x413c flash amss amss.mbn
11.Run: fastboot -i 0x413c reboot
i can open a command window.....i tried pointing it to my folder,but im stumped
" posted by stoney73 .......
ok, have you got Fastboot on your pc? if so, just find it on your pc, and open up a window, then hold left-shift and right click within that window(without actually clicking on an actual file), and click on open command line(or similar) then just type in the instructions, which look to be correct.
if you dont have the android SDK installed:http://developer.android.com/sdk/index.html
download and install the one that is pertinent to your operating system. install it directly on C drive. then open it up, doubleclick tools, and without clicking on any files, hold in left shift and right-click, andchoose 'open command line here', then type in the commands you had in your post. Hope it helps."
--------------------------------------------------------------------------------
Last edited by stoney73; Today at 03:19 PM
heres a vid of my brother showing acouple apps,hes using the dx top lite UI instead of the dell stage
http://www.youtube.com/watch?v=4gv1w1Qr-gg
front facing app working clearsea....still playin with settings
http://www.youtube.com/watch?v=NIyBYhv5_IA
--------------------------------------------------------------------------------
Last edited by mokokawi; Today at 05:47 PM.
Yes qdl is the best method. Trickiest part is getting the pc to recognize the qualcomm driver but its not difficiult if u follow instructions.
Also if youre not looking for root and only want official 2.2, you dont have to go past qdl and mess with streakdroid/amss/recovery...u should be good to go once qdl succeeds.
p00kienrayray said:
Yes qdl is the best method. Trickiest part is getting the pc to recognize the qualcomm driver but its not difficiult if u follow instructions.
Also if youre not looking for root and only want official 2.2, you dont have to go past qdl and mess with streakdroid/amss/recovery...u should be good to go once qdl succeeds.
Click to expand...
Click to collapse
your right....thats where im at now,official 2.2 but have not flashed amss/clockwork/recovery yet, but want to so i can root,and install the overclocking app : )
and next time i can upgrade rom,straight from phone.....
All this talk about qdl but no one has a link to download it. What gives?
Sent from my sizzling, crackling, on fire, Samsung Galaxy "Vibrant" using the XDA APP. (NOTE: Due to modding, some effects may vary. Happy Modding!)
McBang2023 said:
All this talk about qdl but no one has a link to download it. What gives?
Sent from my sizzling, crackling, on fire, Samsung Galaxy "Vibrant" using the XDA APP. (NOTE: Due to modding, some effects may vary. Happy Modding!)
Click to expand...
Click to collapse
its on the "download" page of the first link.....ill update my post with though....good idea
heres the qdltool called "repair tool"
http://streakdroid.com/?page_id=15&did=8
hahaha.....and i like your android sig
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
By George I've got it! Not really actually but I do have a pre-alpha release of kubuntu mobile edition running on my gen 8 tablet
check it out here: http://forum.xda-developers.com/showthread.php?t=1052697
---------------------------------------------------------------------------------------------------------------------------------------------------------------
Here are some semi-complicated instruction for creating a bootable KDE mobile install on Archos gen 8 devices for self.
https://wiki.kubuntu.org/ARM/Archos101it
Hi,
You have prebuilt image for n900 there http://cdimage.ubuntu.com/kubuntu-mobile/daily-preinstalled/current/
As it is same processor, you can try, i m doing the test right now.
Babelo
BabelOued said:
Hi,
You have prebuilt image for n900 there http://cdimage.ubuntu.com/kubuntu-mobile/daily-preinstalled/current/
As it is same processor, you can try, i m doing the test right now.
Babelo
Click to expand...
Click to collapse
Yes I saw that but the touchscreen doesn't work. I've actually managed to compile it (you can find my new thread in the developer forum section) I'll add the download link on the new thread in a few hours. The major problem is that my current "build" takes my to the login screen but because there is no virtual keyboard, I can't log in
http://forum.xda-developers.com/showthread.php?t=1052697
It seems workable, but how about 70?
LeoNg628 said:
It seems workable, but how about 70?
Click to expand...
Click to collapse
I have an archos 70, that's what I'm testing it on.
shrewdlove said:
I have an archos 70, that's what I'm testing it on.
Click to expand...
Click to collapse
but he said virtual keyboard is not working and the touch screen is not response sometime.
LeoNg628 said:
but he said virtual keyboard is not working and the touch screen is not response sometime.
Click to expand...
Click to collapse
I use the word "test" loosely, I mean the archos 70 is the device I am testing the .img's I am compiling. I now can log in but the touch screen is still acting weird. You will be able to test it out in a few hours when the .img finished uploading.
This thread is pretty much dead so I suggest you check out my other developer thread, which is the one will be on mainly
http://forum.xda-developers.com/showthread.php?p=13243471#post13243471
I know I should post this to the new thread in the Gen8 Android Development section, but I'm new to the forums and can't post there yet. We know the kernel is fine since we get the kernel and modules from Angstrom. The major issue I see is that Angstrom has some highly customized init.d and rc.* scripts, as well as a ton of udev and xmod files not found in kubuntu by default. The Angstrom xorg.conf doesn't even include this line:
"Option "Device" "/dev/input/by-id/usb-UNITEC_USB_Touch__Win7_-event-if00"
So I'm sure if we traverse through what's in the Angstrom rootfs.img we should find our answer to at least the touchscreen.
Try taking a look at the archos-init.sh script in the /etc folder of Angstrom.
The modifications made on Angström to make it work on Archos are all told on the Archos website, (on the same page where you download the SDE, the button under the "Download AOS" one)
Well... Yes and No
Angstrom is built using a system called OpenEmbedded (OE). OE works much like rootstock but is a little bit more advanced. It not only allows you to build a .img from a certain distro (in this case Angstrom) but also allows you to build for specific embedded devices. Right now though the newest Archos devices aren't located in the OE repo yet, so what's on the site that your seeing is actually an overlay that goes over what you download from OE that has the configs to tell OE how to built for the Archos Gen 8 architecture. It doesn't actually contain any changes to the scripts or files.
Very interesting guys, thanks a lot.
MysticMgcn said:
I know I should post this to the new thread in the Gen8 Android Development section, but I'm new to the forums and can't post there yet. We know the kernel is fine since we get the kernel and modules from Angstrom. The major issue I see is that Angstrom has some highly customized init.d and rc.* scripts, as well as a ton of udev and xmod files not found in kubuntu by default. The Angstrom xorg.conf doesn't even include this line:
"Option "Device" "/dev/input/by-id/usb-UNITEC_USB_Touch__Win7_-event-if00"
So I'm sure if we traverse through what's in the Angstrom rootfs.img we should find our answer to at least the touchscreen.
Try taking a look at the archos-init.sh script in the /etc folder of Angstrom.
Click to expand...
Click to collapse
Do you have any idea if I could build an ubuntu or kubuntu .img with openembedded and then apply archos's changes to that. I've been looking for some documentation but all I have found so far is documentation relating to angstrom.
While it should be possible, as you've seen documentation is lacking for OE and I've personally had a lot of issues with it just from trying to create my own stock Angstrom .img to see how it worked. Plus it just seems like a lot of work as you have to create BitBake (.bb) files for the programs you want to install, compared to using rootstock and just being able to call out the programs you want installed by default with the --seed switch.
I think we're really a lot closer than we realize to start from scratch with OE. We have the kernel and drivers in place as well as the filesystem, we just don't have a way to tell the system to load the drivers the way they need to be loaded through either udev or init.d/rc.d*.
Well the problem was with udev and I've gotten the mouse to work without the need for an xorg.conf. I'll post more when I can but I may scrap this as everyone lost interest. I'm building a new image from Natty instead of Maverick anyway where udev isn't so flaky.
Sent from my PC36100 using XDA Premium App
ive actually been waiting on a work img, the last one i used just gave me an error msg. i'm not afraid to test anything out.
shrewdlove said:
Here are some semi-complicated instruction for creating a bootable KDE mobile install on Archos gen 8 devices for self.
https://wiki.kubuntu.org/ARM/Archos101it
Click to expand...
Click to collapse
I tried the instructions listed there and they DO NOT WORK. Here's what I did step by step. When I boot the device into developer mode, I get the boodting developer editon screen, but never any hits of kubuntu.
Interestingly, if I try to restore a backed up copy of the Linux Angstrom img it won't boot that either. I have to go back and re-install the SDE to get it to boot in developer mode again.
I just thought I would put it out there for new people like me who are not too familiar with the procedure to flash a new webtop version on our phones. I do not believe the procedure is outlined in an easy to find thread yet.
Things you will need
-Unlocked Atrix 4G ? (mine is unlocked)
-Moto-fastboot http://diamantephoto.com/fastboot.rar
-Latest Webtop IMG file http://forum.xda-developers.com/showthread.php?t=1163009
-Brain
First you need to extract fastboot and your webtop img file in the same directory. Make it something easy and short since you will have to access it in a command window. (c:\atrix)
Second you need to boot your phone in fastboot mode. Hook your phone via usb cable, hold the volume down buttom while powering up. When fastboot show up on your screen press volume up and it will put the phone in fastboot mode.
Third you need to open a command window and go to you fastboot directory. If in C:\Atrix you type "c:" then press enter then type "cd atrix" then press enter.
Lastly type these commands in order
"moto-fastboot devices" (just to make sure we have a connection before we get to business)
"moto-fastboot erase webtop" (this will erase your current webtop partition to make room for the new one)
"moto-fastboot flash webtop webtop.img" (this will flash the new webtop to your now empty webtop partition it will take about 2 minutes)
"moto-fastboot reboot" (voila your done, let your phone reboot into your rom and you can enjoy your newer webtop!)
All of this should look something like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here is a link to a guide to further customize your webtop if you want to. http://forum.xda-developers.com/showthread.php?t=1397583
Thanks to dicksteel for pointing me in the right direction for the actual procedure!
There's something easier than this, Fruit Cake. Flash it from CWM and your done. Plus I think someone made an automated cmd script that installed the 2.3.6 Webtop. Thanks for the effort though, search button could be used...
I searched myself for a method myself for about two days, if you can provide the link to such a thread I'll gladly add it here. I found many how-to's for customizing the webtop (such as webtopmod or webtop2sd) but I couldn't find an how-to just to update your webtop version itself.
xAlex79 said:
I searched myself for a method myself for about two days, if you can provide the link to such a thread I'll gladly add it here. I found many how-to's for customizing the webtop (such as webtopmod or webtop2sd) but I couldn't find an how-to just to update your webtop version itself.
Click to expand...
Click to collapse
I thought that I made one, but I guess it was just a ROM upgrade without the webtop.
But. This: Fruit Cakes All you pretty much do is flash the Webtop zip in CWM and your done. It's just a easier and quicker way of what your doing here.
web top
i am running wet dream 1.3.0 and it is great i also have webtop2sd but is does not work when i connect my hdmi cable i have the webtop option but it does not to any thing but the entertainment centre works perfectly can some one help
mikoyano said:
i am running wet dream 1.3.0 and it is great i also have webtop2sd but is does not work when i connect my hdmi cable i have the webtop option but it does not to any thing but the entertainment centre works perfectly can some one help
Click to expand...
Click to collapse
Try using Nebtop.
http://forum.xda-developers.com/showthread.php?t=1407092
Alaq said:
There's something easier than this, Fruit Cake. Flash it from CWM and your done. Plus I think someone made an automated cmd script that installed the 2.3.6 Webtop. Thanks for the effort though, search button could be used...
Click to expand...
Click to collapse
Yeah, I don't understand why he points you to the fruitcake image, but then has you extract it from the zip file. CWM includes a command to flash webtop images directly, rather than going through what is described.
Also, when I first read it, I though it mean actually updating my current webtop image, not flashing a new one. That would be a feat so I don't have to apply my changes when a new webtop arrives (already on 2.3.6, so right now that's not an issue for me).
troycarpenter said:
Yeah, I don't understand why he points you to the fruitcake image, but then has you extract it from the zip file. CWM includes a command to flash webtop images directly, rather than going through what is described.
Also, when I first read it, I though it mean actually updating my current webtop image, not flashing a new one. That would be a feat so I don't have to apply my changes when a new webtop arrives (already on 2.3.6, so right now that's not an issue for me).
Click to expand...
Click to collapse
if for whatever reason you cant flash the zip file like me, im on gingermod 2.3.6 but when i try to flash the cwm webtop file it doesnt let me. says i failed the authentication that sam built into his cwm file. anyways i dont think cwm is easier than fastboot, they are both very easy. btw make sure you use moto-fastboot from this thread i think the fastboot that OP linked to is just the normal fastboot and cannot be used to flash large file like webtop.
Try searching this site....wft ..also he points you to a fruit cake file for cwm and then tells you to use moto-fastboot...Please can the moderaters delete this kind of thread.
Hi Folks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As you may or may not be aware, I have been working on get CWM Recovery working on the Gen9's and basically make the layout of the Filesystems etc reflect some sort of Android Standard, In SDE mode at least. This is coming along nicely and I should be ready to kick out a Early Beta in the Next Couple of Weeks.
I would like to gather some input on any additional options people who like to see in CWM, Basically CWM Recovery Comes with a standard set of features but they maybe options that you have found useful on Device's you have had in the past etc.
I already plan to make it possible to boot into all modes on the device, that Archos Recovery, Archos Android, SDE Android and SDE CWM Recovery.
So Yeah, Give me Ideas and I'll seen If I can accomadate them
NOTE: Obviously We are just getting started on this and alternative recoveries will come in time, TWRP for example but one thing at a time eh :good:
Okay, Here's a currently "wishlist" of feature I think would be quite useful
Archos Specific Features
Include Stock Repair and Recovery Options
Include Stock Developer Edition Options
Reboot to Stock Recovery Option as a Fail Safe.
Reboot Stock Android
Flash Archos aos update
Upgrade Existing SDE Images to new structure
An the list goes on.....
Print system Properties
Print dmesg
Resize Partitions
Manage FS Image Location ( mainly nice to have on HDD Version I suppose )
Backup to Sparse Image ( I'm sure CWM5 Nandroid did this with ext4 partitions, god knows why they changed to a default choice between tar archives or dup differential blobs, What If I just a single portable file for my data partition backup!! )
Start Fastboot support ( could be useful for flash images rather the 'ffing around with edify scripts and update zips )
Power Off ( Suprisingly not include by default )
Full Touch Support with on screen keyboard and command line
I think those features will do nicely but If anyone has anymore then get involved!
The nandroid backup interests me a lot... its always nice to be able to "return" to when it was working if anything breaks.
Im watching this thread with interest good luck!!
TrOjAn
Maybe an ability to mount the whole system through usb? So one could DD clone the whole memory chip to PC. That could recover some bricks.
trevd said:
Resize Partitions
Click to expand...
Click to collapse
I'm not sure if this would be actually usefull for flash partitions (one-time update.zip flashing should be enough)
trevd said:
Start Fastboot support ( could be useful for flash images rather the 'ffing around with edify scripts and update zips )
Click to expand...
Click to collapse
But fastboot works on the bootloader level
gen_scheisskopf said:
I'm not sure if this would be actually usefull for flash partitions (one-time update.zip flashing should be enough)
But fastboot works on the bootloader level
Click to expand...
Click to collapse
Hi There,
I think, You've got your wires crossed None of this is related to letama CWM Recovery./ If you haven't already you may want to have a read of this thread in the development section I won't go into details here because It's all in there!
I well aware of how fastboot works but to supporting the fastboot protovol allows the same workflow when it come to work with the AOSP source as any over device. which is
Build Rom
Flash the Partitions with fastboot
Reboot Into Rom.
???
Profit
When you control both ends of the conversation, We are free to do as we please.
Any news ... are there any files to do some testing?
shalkam said:
Any news ... are there any files to do some testing?
Click to expand...
Click to collapse
Would you mind reading... ???
trevd said:
If you haven't already you may want to have a read of this thread in the development section I won't go into details here because It's all in there!
Click to expand...
Click to collapse
Follow the link and you are there.
Regards,
scholbert
Flash splash screen?
Swiped from my Galaxy Nexus using Tapatalk 2
I've seen countless tutorials for different phones/tablets and I want to know more specifically how to do it for a TB, considering I don't want to brick my phone. And I know there are a bunch of them floating around but there has only ever been one that I truly liked and I can't find it anywhere, so I'll make my own. This is what I had in mind...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Cuz who doesn't love Dr. Harleen Quinzel?
I've already got the image in the correct resolution (480x800) and have successfully converted it to both RAW and RLE formats but haven't the slightest clue where to go from there.
onedementedsmurf said:
I've seen countless tutorials for different phones/tablets and I want to know more specifically how to do it for a TB, considering I don't want to brick my phone. And I know there are a bunch of them floating around but there has only ever been one that I truly liked and I can't find it anywhere, so I'll make my own. This is what I had in mind...
Cuz who doesn't love Dr. Harleen Quinzel?
I've already got the image in the correct resolution (480x800) and have successfully converted it to both RAW and RLE formats but haven't the slightest clue where to go from there.
Click to expand...
Click to collapse
Fastboot flashing is the easiest and quickest
je2854 said:
Fastboot flashing is the easiest and quickest
Click to expand...
Click to collapse
Ok, that much I can understand but I don't know how to do that. It's like I said I have the image in PNG, RAW and RLE formats but no clue where to go from there. I know I'm supposed to make a boot.img somehow but that's where I'm stuck.
Take the boot.img from the rom you want to use it on and use the python script for splitting boot images. There is a guide for it on the interwebs. There is another method to flash it through fast boot but I am not sure how to package the file to make it ready for a fast boot flash. I know for a fact there are guides all over the place making splash screens.
Sent from my ADR6400L using Tapatalk 2
je2854 said:
Fastboot flashing is the easiest and quickest
Click to expand...
Click to collapse
disconnecktie said:
Take the boot.img from the rom you want to use it on and use the python script for splitting boot images. There is a guide for it on the interwebs. There is another method to flash it through fast boot but I am not sure how to package the file to make it ready for a fast boot flash. I know for a fact there are guides all over the place making splash screens.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
I have seen countless guides but not a single one that references the TB and I don't want to take the risk in doing something that was specifically said to work on some other device. I have used the split_bootimg.pl to split the boot.img but that doesn't seem to help me at all as it just gives me boot.img-kernel and boot.img-ramdisk.gz, neither giving any indication towards a PNG, RAW or RLE file
The principal behind inserting a splash image is the same for all devices that use a boot.img.
Sent from my ADR6400L using Tapatalk 2
Well I found this and it's pretty straight forward and to the point although I dislike it being specifically made for Windows considering in my experience it's impossible to get fastboot working in Windows 8. Ultimately you can use the above on Linux so long as you have Wine installed. I'm gonna try to port the batch script into something usable in Linux, if I succeed I'll post the results here.
Well I wrote a bash script now so anyone else looking for info go here
onedementedsmurf said:
Ok, that much I can understand but I don't know how to do that. It's like I said I have the image in PNG, RAW and RLE formats but no clue where to go from there. I know I'm supposed to make a boot.img somehow but that's where I'm stuck.
Click to expand...
Click to collapse
the exact command for a LOGO would be
here again I use Root Terminal for everything so I have no idea if it requires it or not
# adb reboot (this is if you are in the OS already)
# fastboot devices (make sure it's connected properly)
# fastboot flash splash1 'image.*' (can be anything in the RAW fomat BUT most conform to the 480x800 format)
# fastboot reboot (gives you a full reboot with the new image)
also.... I have a tutorial on how to flash images here