Hi All,
I have Dell streak with EVT1 hardware. I flash all possible recovery images, but it isn't work. Black screen every time when I launch recovery mode. May be somebody know how to update this hardware?
Phone is working on 1.6 (performance is very poor)
P.S. Sorry for bad English.
Please help!!!
What is the currently installed rom exactly?
NikolayTLM said:
Hi All,
I have Dell streak with EVT1 hardware. I flash all possible recovery images, but it isn't work. Black screen every time when I launch recovery mode. May be somebody know how to update this hardware?
Phone is working on 1.6 (performance is very poor)
P.S. Sorry for bad English.
Click to expand...
Click to collapse
If you have a black screen at recovery with no Dell logo, you probably are going to need to restore your device using the QDLTool3rd.
Typically, this happens when flashing an "update" file mismatched with your recovery. I did this myself recently, and the only way I was able to get back was to use the QDL tool then re-flash my stock ROM.
It literally saved my phone.
EVT=evaluation/testing?
Without knowing the differences in hardware and possibly software you can't assume that solutions that work on production Streaks will work on his phone.
marvin02 said:
EVT=evaluation/testing?
Without knowing the differences in hardware and possibly software you can't assume that solutions that work on production Streaks will work on his phone.
Click to expand...
Click to collapse
EVT=evaluation/testing - Yes
i think that difference between EVT3 (product hardware) and EVT1 - smallest RAM size (145Mb is available)
in on board EVT1:
- QSD8X50 Processor (as per "Android System Info") with 998.4Mhz max frequency.
- Total RAM: 145Mb
I tried flash device via QDLTool3rd - unsuccessful. Maybe i used newest recovery images instead old? Black screen every time when i try to boot it in recovery mode. What additional info about EVT1 is needed and which application can provide this information?
BR. Nikolay.
TheManii said:
What is the currently installed rom exactly?
Click to expand...
Click to collapse
Sorry, but i don't know the currently installed rom.
Info in 'About device' menu:
- Firmware version: 1.6
- Baseband version: GAUSB1A1008151
- Kernel version: 2.6.29-perf
- OEM version: RerforceVerify_1012
- Build number: 1012
You definitely have an enginnering beta streak, from what've seen from attempting to get people to dump their roms off it, trying to update it will prob brick it.
It's only valuable if you can get the rom off it, but otherwise you likely wont be able to use it as a normal streak
TheManii said:
You definitely have an enginnering beta streak, from what've seen from attempting to get people to dump their roms off it, trying to update it will prob brick it.
It's only valuable if you can get the rom off it, but otherwise you likely wont be able to use it as a normal streak
Click to expand...
Click to collapse
Thanks, i think about that. I am use it as normal cell phone right now. But it is not easy, because it will reboot at any time as they wish. I like this phone and it isn't trouble to update RAM (on this device to appropriate size). I just want to know - device is 'upgradeable' to 2.2 or not?
I'l talking with people, which know about this device. And they said me - that this device can be ungraded, but build should be compiled in appropriate kitchen! Maybe somebody have appropriate build rom for this HW type/ or maybe somebody upgrade EVT1 HW?
how much did that specific streak cost you exactly?
You're much better off getting a normal retail streak unless you dont mind the hassle of making everything work on that submodel.
Clearly stock kernels and roms have trouble with that submodel, are you willing to investigate why? and are you willing to be forced to resort to making custom versions of roms just for your specific streak?
I am interested in getting the rom off that, but besides that unless you got it for free/next to nothing it's prob not worth the hassle compared to a retail streak, there's far too few owners of working prototype streaks left for premade roms to work on them
TheManii said:
how much did that specific streak cost you exactly?
You're much better off getting a normal retail streak unless you dont mind the hassle of making everything work on that submodel.
Clearly stock kernels and roms have trouble with that submodel, are you willing to investigate why? and are you willing to be forced to resort to making custom versions of roms just for your specific streak?
I am interested in getting the rom off that, but besides that unless you got it for free/next to nothing it's prob not worth the hassle compared to a retail streak, there's far too few owners of working prototype streaks left for premade roms to work on them
Click to expand...
Click to collapse
Yes, I got them for free. But this is a not major point for me. I would like to understand 'How it works'.... And I request help on this forum. I'm from Russia, Dell Streak mini 5 isn't selling in my country, So I would like to do 'candy' from it (not for sale, for me only). I thinking about purchasing Dell streak mini 5 with broken LCD, to change mainboard between my and broken device. But I'm not sure about compatibility this hardware (and I not have money to buy it........)
P.S. Sorry for bad English again.
I would assume the lcds would be compatable, but this is just an educated guess,
It sounds like a good idea to switch the motherboards if you want a real working streak
as you're not going to be using the original motherboard, could i ask you to make a dump of the system and boot partitions?
we should continue on #dellstreak on irc.freenode if you dont mind, prototype roms and devices are extremely rare and working ones with pre-release roms are even rarer. There's only a handful still in existance now
TheManii said:
I would assume the lcds would be compatable, but this is just an educated guess,
It sounds like a good idea to switch the motherboards if you want a real working streak
as you're not going to be using the original motherboard, could i ask you to make a dump of the system and boot partitions?
we should continue on #dellstreak on irc.freenode if you dont mind, prototype roms and devices are extremely rare and working ones with pre-release roms are even rarer. There's only a handful still in existance now
Click to expand...
Click to collapse
Please write instructions / 'how to' make a dump of the system and boot partitions
Do you know how to use ADB?
you will need to root your phone also before beginning
TheManii said:
Do you know how to use ADB?
you will need to root your phone also before beginning
Click to expand...
Click to collapse
My dell is rooted. I used ADB shell in my practice but a long time ago. So it would be perfect if you provide ADB commands...
Do you still have the original recovery installed?
first do a
Code:
cat /proc/mtd
and figure out which is boot / recovery / system
then do a
Code:
dd if=/dev/mtd/mtdx of=/sdcard/recovery.img bs=4096
dd if=/dev/mtd/mtdy of=/sdcard/boot.img bs=4096
where X and Y are the matching values from the first command
finally do a
Code:
cat /system /sdcard/system
then you'll have boot.img recovery.img (if you still have it) and a folder named system
send those 3 to me
TheManii said:
Do you still have the original recovery installed?
first do a
Code:
cat /proc/mtd
and figure out which is boot / recovery / system
then do a
Code:
dd if=/dev/mtd/mtdx of=/sdcard/recovery.img bs=4096
dd if=/dev/mtd/mtdy of=/sdcard/boot.img bs=4096
where X and Y are the matching values from the first command
finally do a
Code:
cat /system /sdcard/system
then you'll have boot.img recovery.img (if you still have it) and a folder named system
send those 3 to me
Click to expand...
Click to collapse
I used these commands in dell terminal app:
Code:
su
cat /proc/mtd
dd if=/dev/mtd/mtd1 of=/sdcard/recovery.img bs=4096
dd if=/dev/mtd/mtd2 of=/sdcard/recovery_bak.img bs=4096
dd if=/dev/mtd/mtd0 of=/sdcard/boot.img bs=4096
dd if=/dev/mtd/mtd3 of=/sdcard/system.img bs=4096
After that operations 4 files added to sdcard (recovery.img, recovery_bak.img, boot.img, system.img)
Incorrect length message was displayed after cat /system /sdcard/system command.
All files were added to archive (WinRAR used) and uploaded to fileserver
You have to use
cat /system /sdcard/system
as DD will not work on the system partition
TheManii said:
You have to use
cat /system /sdcard/system
as DD will not work on the system partition
Click to expand...
Click to collapse
following text message is displayed when i try cat /system /sdcard/system command.
Code:
/system: invalid length
/sdcard/system: invalid length
my *nix is really weak,
try
Code:
cp -r /system/* /sdcard/temp
but you might need to manually make /sdcard/temp first or it might get confused
it will complain about symlinks but that's ok
The device I am testing with is an LG Optimus V. The second generation model with the newer screen.
After obtaining root, but making no other changes I decided to backup using the method I will reference in these two links:
http://groups.google.com/group/andr...1c5c06d7f95?lnk=gst&q=backup#851e41c5c06d7f95
http://forums.androidcentral.com/lg...ense-back-up-your-phone-without-nandroid.html
Basically, it is doing:
cat /dev/mtd/mtd5 > /sdcard/mtd5.img
It turns out that this method does not work to restore the backups.
fastboot is locked on this device.
cat /sdcard/mtd5.img > /dev/mtd/mtd5 does not seem to actually write anything and hangs at LG logo.
flash_image will flash the img but does not seem to actually write anything and hangs at LG logo.
update.zip method does not work since I am not able to extract the img with any of 3 different unyaff programs.
Now I know to do a reliable backup to use Nandroid. But I would like to know where the cat method went wrong. As you can see, on some devices the cat method seems to work. Why not mine?
Is it because of corruption happening during the process? If so, could you please explain the source of the corruption in more detail.
Or is it maybe because the cat backup method is meant to only work when using fastboot to restore?
To add more information to the thread, it seems that some have used a similar method to this, instead using dd for cat. Thanks for the help.
EDIT: I know now that at least DD will work, because clockworkmod uses that internally in it's install script.
A favor please??
Hey guys. I am going to try and make a recovery that works 100% fully for everyone. I see a few people have issues and others don't. I try and fix it. Need some help. I don't have this phone so I need a few files before I can get started. If anyone could get me 3 things
If anyone knows how to do a dump_image the stock recovery.img for me.
Post the file /proc/partitions
Post the file /proc/mounts
For the 2 and 3. You can also do an adb commands. "adb shell" then "cat /proc/partitions" and "cat /proc/mounts"
Thank You Guys! and if everything goes well. I can port over CWM Touch.
Here's items 2 and 3. I just got my DNA so I haven't unlocked yet, and I don't know of a way to dump the recovery without unlock, but I'll post it as soon as I can.
Has anyone tried the method below to Re-Root and Re-Lock from Carrett's Thread:
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
How can I re-lock and un-root my phone? Remember the backups of the locked bootloader that you kept? You're going to need them. Obviously, you'll need USB Debugging enabled and LG USB drivers installed. Copy them to your phone's "Internal Storage" in a folder, in this example it's called "backups." Connect the phone to your computer via USB, open a command line (cmd) and type the following:
Code:
cd C:/some/folder/where/you/have/adb.exe/eg/your/freegee/download
adb shell
su
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/boot
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/aboot
dd if=/sdcard/backups/aboot-att-backup.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
dd if=/sdcard/recovery-att-backup of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/sdcard/boot-att-backup.img of=/dev/block/platform/msm_sdcc.1/by-name/boot
dd basically copies from the if= location and writes to the of= location. The first three dd steps write a bunch of zeros to the recovery, boot, and aboot partitons, the last three write the backups to aboot, recovery, and boot. If you want to know more, read all about dd here and/or Google. If you lost your backups, you can try writing mine.
Now you've restored the stock bootloader and recovery, but your phone is still rooted. To unroot it, open SuperSU, go to its settings, and tap "Full unroot." Do a factory reset (Settings->General->Backup & reset->Factory data reset) and you should be good to return the phone to AT&T (or whatever).
I did but I ended up having to LGNPST back to stock because I messed up somewhere along the way. You'll know if you messed up because when you try to boot you'll get the LG splash screen + Security Error.
If you choose to go this route, make sure you pay careful attention!
Murasakiii said:
I did but I ended up having to LGNPST back to stock because I messed up somewhere along the way. You'll know if you messed up because when you try to boot you'll get the LG splash screen + Security Error.
If you choose to go this route, make sure you pay careful attention!
Click to expand...
Click to collapse
Thanks for the response. So does it work and you simply messed up or is the code botched? It looks a lot simpler than LGNPST and I want a process that was a little simpler to do and quicker? Have not tried to LGNPST and was hoping not to but if I had to I wanted something I can't mess up.
Might want to check with SnowLeopard, I think there was a mention somewhere about making a zipped stock firmware that is unrooted and unlocked that can be installed.
Sent from my LG-E970 using xda app-developers app
jimi_pooh said:
Thanks for the response. So does it work and you simply messed up or is the code botched? It looks a lot simpler than LGNPST and I want a process that was a little simpler to do and quicker? Have not tried to LGNPST and was hoping not to but if I had to I wanted something I can't mess up.
Click to expand...
Click to collapse
There's a chance I messed up in the adb client, but there's no telling at this point. It was a few weeks ago. LGNPST really isn't hard, though some people think it is. Takes like one good run through to understand it, and there's several people in the LGOG IRC that can guide you through it.
Hello! I've got 2 identical Android 9 car head units: a new fully working one and another with corrupted software. What I am trying to accomplish is to dump all the partitions from the working device and then flash them to the broken one. I am a little limited because the only tool I've got is Android ADB via Wi-Fi (there isn't any custom recovery available for this device) and the stock recovery isn't helping much. I have to mention that the bootloader seems unlocked and the adb shell has root privileges. I've found some older posts about making a nandroid backup via adb, but I am not sure if the information is still valid.
So, to make my question short: Is there a way to fully dump a device via adb and then restore the dump also via adb (or at least pack the dump as a flashable zip)? I am a little lost, so any help is welcome! Thank you!