• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [ROM][WIP] BACKside ROM (CM7) + Green Machine Theme

JerryScript said:
I'm beginning to think those who have issues with GPS may have a hardware issue. Definitely not certain about it yet, but I have never had an issue with GPS, and only a handful of users have ever complained about it. One of the IHO devs, mrg666 has two OVs, and one gives him GPS trouble, so I'm leaning towards hardware on this one.
Click to expand...


Must be hardware.

My family has a total of five OVs, two 2.2.1s, the rest 2.2.2. Of these, two of the 2.2.2s have issues with GPS. Both of these are stock. The rest are rooted, and no issues with GPS.

Got Vs for my some of my non-smartphone using friends when they were on sale last year, and out of the six I got for them, three had issues with GPS. They had VM replace them, and had no issues since.
 
@Jerry

I tried flashing the radio update a few times using BOBZ Recovery and Xionia Recovery and the file never updated from ZV5 to ZV9. Been wanting to play with the new rooting method anyway so went ahead and flashed the VM update file and returned to stock. Before rerooting and flashing back to backside my phone showed ZV9. I flashed a new install of backside and the file still showed ZV5. I can't find in QPST where to see the current baseband version to verify what it says, but by stock rom before I rooted I had ZV9. Hope this helps a little
 
In QPST open EFS Explorer, in "err" folder there is some modem crash log files in which you can see the radio version and it's the old one. If your modem didn't crash after radio update you can't be sure what the radio version is currently on phone. That is the only place I could find radio version in QPST.
But CDMA Workshop shows radio version read from phone with build date and everything and it is the old one so I think Jerry is right. The radio update is not flashed.

I'm wondering if flashing radio.img in bootloader with fastboot would work!?

kwknott, can you check your radio version with CDMA Workshop?
 
VM670ZV4 here too. I suppose that means flashing the radio update did nothing, or does it?

Perhaps someone will come up with a way to flash the radio update that is less complicated than reverting the phone to updated stock and starting all over again.
 
JerryScript said:
I'm beginning to think those who have issues with GPS may have a hardware issue. Definitely not certain about it yet, but I have never had an issue with GPS, and only a handful of users have ever complained about it. One of the IHO devs, mrg666 has two OVs, and one gives him GPS trouble, so I'm leaning towards hardware on this one.
Click to expand...

Oh well it works enough and now I get use out of that gps reciever I bought.

That boot animation is funny because my kids get the same screen from time to time playing games on backside. I've never mentioned because there on an old build and I've thrown it up to game errors. And it fixes with a battery pull.
 
nijel said:
In QPST open EFS Explorer, in "err" folder there is some modem crash log files in which you can see the radio version and it's the old one. If your modem didn't crash after radio update you can't be sure what the radio version is currently on phone. That is the only place I could find radio version in QPST.
But CDMA Workshop shows radio version read from phone with build date and everything and it is the old one so I think Jerry is right. The radio update is not flashed.

I'm wondering if flashing radio.img in bootloader with fastboot would work!?

kwknott, can you check your radio version with CDMA Workshop?
Click to expand...

Checked phone with CDMA Workshop and it's still showing ZV5. Stock was showing ZV9 before rooting and flashing but must have just been rom thinking it was ZV9. Doesn't look like radio is getting properly flashed with the radio patch or the full update. Wonder if it's something custom recoveries can't do? If it wasn't such a P.I.A. I would flash back to stock with stock recovery and try it.
 
Thanks for all the feedback on the radio. I'm investigating various methods to get the radio to flash properly. I just wish people had been patient in the beginning when I asked them to be. Now I have to dig through each persons flashing history to determine what worked and what didn't. ;)
 
JerryScript said:
Thanks for all the feedback on the radio. I'm investigating various methods to get the radio to flash properly. I just wish people had been patient in the beginning when I asked them to be. Now I have to dig through each persons flashing history to determine what worked and what didn't. ;)
Click to expand...

Hey Jerry I finally got the radio updated. Per the suggestion of nijel I used CDMA Workshop to check the baseband.

I started with ZV5. I flashed Leslie's radio patch multiple times with Bob's recovery and Xionia recovery and CDMAWS still showed ZV5 radio.

Next I tried flashing the full update and even though stock rom showed ZV9, Rerooted and flashed backside and checked build_id file and it stated ZV5. Double checked with CDMAWS and it still showed ZV5.

Finally flashed the full update, booted into stock, rebooted into stock recovery and flashed full update again using stock recovery. This time CDMAWS showed ZV9. Rooted and restored my NANDROID backup and checked the build_id file and it also showed the ZV9 radio

I don't know alot but appears stock recovery is only recovery having sucess at flashing the radio as of now. I'm sure you can figure something out. Hope this helps a bit
 
I agree, from what several people have posted, I'm inclined to believe the stock recovery that comes with the security update has whatever is missing to flash the radio.

Thanks for posting your results everyone!
 
Nice...

Well fastboot can't flash radio::confused:

Code: 
>fastboot flash radio radio.img
sending 'radio' (12496 KB)...
OKAY [  3.177s]
writing 'radio'...
FAILED (remote: unknown partition name)
finished. total time: 3.283s
 
Maybe we can isolate stock recovery and radio image, flash it and with two reboots change recovery, flash radio and change back to custom recovery without flashing stock ROM update and loosing root?
From the VM updater-script seems like we need to flash stock boot.img, copy some files to /system, /system/bin and /system/etc which will patch some memory addresses with stock recovery at next boot. Then reboot to stock recovery, flash radio, reboot and flash custom recovery. The only thing that bothers me is stock boot.img wont load custom ROM. Am I correct?
 
IMHO, it's simpler (and safer) to do a nandroid, then flash the security update twice, then use Gordita Root, then restore nandroid. ;)

Since we don't know exactly how the radio is flashed, and why it takes a second boot, I prefer this method.

Note- I assume the install-recovery.sh file is adding the what's needed during the first boot after flashing the update.zip, since it applies a patch. Once this patch is applied, then the radio seems to flash fine.
 
JerryScript said:
IMHO, it's simpler (and safer) to do a nandroid, then flash the security update twice, then use Gordita Root, then restore nandroid. ;)

Since we don't know exactly how the radio is flashed, and why it takes a second boot, I prefer this method.

Note- I assume the install-recovery.sh file is adding the what's needed during the first boot after flashing the update.zip, since it applies a patch. Once this patch is applied, then the radio seems to flash fine.
Click to expand...

I finally had the time to do this, now happily running 0401 on zv9. :)
 
This is how I did it:
-installed VM update twice;
-after second install and reboot run
"adb shell cat /sys/devices/system/soc/soc0/build_id" to verify radio update;
-run "adb reboot-bootloader"
-run "fastboot flash recovery path\to\recovery.img"
-removed battery;
-boot to recovery(volume_down+home+power keys);
-restore nandroid backup;
-reboot and... stuck in recovery, full wipe and clean ROM flash didn't help, clean flash ZV9 update again didn't help so I had to run:
adb shell "rm /data/amit/*"
adb shell "ln -s /dev/mtd/mtd2 /data/amit/AMI304_Config.ini"
adb shell "ln -s /dev/mtd/mtd2 /data/amit/AMI304_Config2.ini"
and reboot to boatloder and flash boot.img from backside ROM with fastboot to get phone to boot to ROM.

Then just for fun I restored nandroid backup again and gues what, I was stuck in recovery again. Had to rerun rm and ln commands and reflash boot.img again.
The bottom line - old nandroid backups prior radio update most likely will stuck in recovery. Anyone dare to confirm?

BTW, dump_image run from updated stock ROM did not recognize stock recovery partition.
 
I just did it on my sister's phone an hour ago:

1- downloaded VM update.zip, VM670NH_recovery.img, and jcase_rootme.zip to the sdcard
2- Rebooted into recovery,
3- nandriod backup
4- flashed update.zip
5- Booted up
6- Rebooted recovery
7- Factory reset
8- Flash update.zip
9- Booted up
10- Apply Gordita Root
11- Restore nandroid backup

New radio is flashed, and no problems at all.

Note- on one other phone, I had issues without doing the factory reset, had no issues this time. ;)
 
I had to do it twice. First try without factory reset, resulted in bootloop. Second try with update_wiper.zip and factory reset, ran flawlessly. I think you need to wipe the data before it'll boot post-update.
 
I was wrong. It's not the restore backup or "rm" and "ln" commands causes my "suck in recovery" problem. It's the boot partition. The fastboot command that I thought was flashing boot, actually just was booting the phone to ROM using backside boot.img, but didn't flash it. After trying a few different ways to flash boot still no luck. No errors flashing but can't boot ROM, goes straight to recovery. So something went wrong with my boot partition. Keep fighting it. Any ideas?

EDIT: Got it all working replying the update all over again, and then following kwknott's and Jerry's instructions. Thanks,guys. I think the key here is the flash_image binary from
Gordita Root. Moral of the story - don't try to reinvent the wheel.
But it was fun and learned something new.:)
 
You must log in or register to reply here.
Back
Top Bottom