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

[Verizon] [ROM]JDX (formerly Jelly Belly) AOSP+ - v15 (7/28)

Chief flashing a bootloader is as simple as all the flashing you already do. Getting a hold of the bootloaders is even easier. They are on rootz.....I'll post link when I get home if someone else doesn't first. ;)
 
The_Chief said:
I don't want to flash a one-way ticket here with no return possible...
Click to expand...

jbdan said:
Uhhh...who in the world would want to go back to ICS :laugh:

I kid.....not really!
Click to expand...
I'm with Chief on this one. I don't like one way streets. Contrary to my nature I may pass on the hybrid.

I'm missing the data from one of my apps and I can't get it back via Titanium or MyBackup Pro so I may have to restore a Nandroid to get it. Maybe going back to ICS for a short time may make me appreciate the butter of Jelly Bean!
 
There ARE people dirty flashing 2.6 with no problems. Wipe Dalvik, cache, FORMAT system.

Gapps 7-4 Proper

EDIT: I am going to hold off until 2.7 comes out and we're on FULL AOSP. At that point, I think I can comfortably flash the JB bootloader; whatever ROM I choose from then on WILL be a JB ROM. I can't imagine going back to ICS at this point.

Is the JB bootloader flashable in Clockwork? Just flash the zip?
 
The_Chief said:
Hawk, my mind doesn't work that way.

I need a step-by-step, play by play, go here, type this, do that sort of thing.

If you can point me to something like that (with images), I would be grateful :)
Click to expand...

This is the link to get Google's factory images for nexus devices. https://developers.google.com/android/nexus/images

Flashing the bootloader is possibly the riskiest flash because if it goes wrong, it will probably result in a hard brick, and not the easy to fix soft brick.

I assume since you have used the tool kit, that somewhere on your computer is the android sdk tools. You want to extract the file "bootloader-toro-primela03.img" from the tzg file to where the fastboot sdk file is located. Open command prompt and change to the directory that has that the fastboot.exe cd C:\...

Make sure the phone is in fastboot mode and hooked up to the computer at this point.

type "fastboot devices" in the terminal to make sure it sees your device.
if it does, then the command "fastboot flash bootloader bootloader-toro-primela03.img" will actually flash the bootloader.

You might want to wait on jbdan to provide a cwm flash, but if you want to attack it old school, that is how.
 
The_Chief said:
Damn I hate scary phone stuff... and ADB / fastboot is scary phone stuff for me :p
Click to expand...

Yeah, it's very intimidating to be honest. The threat of the hard brick is nerve racking especially since while I was a noob a year ago, i hard bricked a phone because I was too noobish to check md5's. You live, you learn.
 
The_Chief said:
Well, worst case scenario, I hook up Wug's toolkit ad flash all the way back to locked stock, re-unlock, re-root, and start all over again.

Wouldn't be the first time :rolleyes:
Click to expand...

Just curious, so did Wug's take care of everything for you? i.e. you just hook you Gnex up to your pc and could root and unlock it with Wug's? Didn't have to the it the old manual way using fastboot and all that (guess that is best way to describe it :D )

Also, has anyone noticed any kind of improvement with the JB bootloader? Is there really any benefit right now I guess is the question.

jhawkkw said:
This is the link to get Google's factory images for nexus devices. https://developers.google.com/android/nexus/images

Flashing the bootloader is possibly the riskiest flash because if it goes wrong, it will probably result in a hard brick, and not the easy to fix soft brick.

I assume since you have used the tool kit, that somewhere on your computer is the android sdk tools. You want to extract the file "bootloader-toro-primela03.img" from the tzg file to where the fastboot sdk file is located. Open command prompt and change to the directory that has that the fastboot.exe cd C:\...

Make sure the phone is in fastboot mode and hooked up to the computer at this point.

type "fastboot devices" in the terminal to make sure it sees your device.
if it does, then the command "fastboot flash bootloader bootloader-toro-primela03.img" will actually flash the bootloader.

You might want to wait on jbdan to provide a cwm flash, but if you want to attack it old school, that is how.
Click to expand...

Which image is for the USA VZW GNex?
 
I'm on 2.4 right now and everything seems to be fine but I don't know how to check the deep sleep issue. I was going to flash 2.5 but now that 2.7 should be out soon I guess I'll just wait for that.
 
2.6 with JB boot loader...dirty flashed everything from 2.5. Lovin the Speed!!! Looking forward to the AOKP baked in customizations, which is the only reason i have not gone back to lean kernel yet...but soon!!
 
The_Chief said:
Damn I hate scary phone stuff... and ADB / fastboot is scary phone stuff for me :p
Click to expand...

It's certainly nerve racking when you're not familiar with it I agree. Below, thanks to NSutherl, on Pete Alfonso's site, he has flashable bootloaders. Added to the OP under Misc links :)
 
CopperWires said:
I'm on 2.4 right now and everything seems to be fine but I don't know how to check the deep sleep issue. I was going to flash 2.5 but now that 2.7 should be out soon I guess I'll just wait for that.
Click to expand...

Use cpuspy free from market. Install, open, menu top right, reset timer, back out to home screen, turn screen off and set phone down for 10 minutes. Turn on and open cpuspy to see what it says. Deep sleep was completely fixed for me on 2.5 even through reboots and without having to open maps to get a gps lock.
 
I read through some of Jakeday's rootzwiki thread since 2.6 came out, and I've read about 3 or 4 instances so far where people have flashed the JB bootloader while on Jelly Belly, then flashed an ICS ROM using the JB bootloader with no issues. I hope it turns out that the JB bootloader is in fact backwards compatible with ICS, which would eliminate the need to flash down to an ICS bootloader. Check the thread for more info, but make sure you have some free time, that thread gets a new post at least once a minute.

EDIT: Check this thread for a few more cases of success flashing/restoring ICS ROMs from JB bootloader. This may be good news...
 
NSutherl said:
I read through some of Jakeday's rootzwiki thread since 2.6 came out, and I've read about 3 or 4 instances so far where people have flashed the JB bootloader while on Jelly Belly, then flashed an ICS ROM using the JB bootloader with no issues. I hope it turns out that the JB bootloader is in fact backwards compatible with ICS, which would eliminate the need to flash down to an ICS bootloader. Check the thread for more info, but make sure you have some free time, that thread gets a new post at least once a minute.
Click to expand...

I agree it would be real nice. I have been reading over on the devices threads of AOKP some having issues who flashed over to the JB bootloader then flashed aokp m6 or b40. I can't remember exactly what those issues were or if they were even serious enough to worry about.

edit: and this site might become priceless for those who want to flash back to stock as it looks like in order to do that you'd have to flash the ICS bootloader (in flashable zips for you Cheif ;))
 
jbdan said:
I agree it would be real nice. I have been reading over on the devices threads of AOKP some having issues who flashed over to the JB bootloader then flashed aokp m6 or b40. I can't remember exactly what those issues were or if they were even serious enough to worry about.

edit: and this site might become priceless for those who want to flash back to stock as it looks like in order to do that you'd have to flash the ICS bootloader (in flashable zips for you Cheif ;))
Click to expand...

Just found that page in the second thread I linked and bookmarked it. Lots of good stuff on there.
 
Patriot123 said:
I don't like the sound of this hybrid thing. I'm either going to a) wait for 2.7 which he's calling "pure" AOSP, or, b) which ever customizable ROM comes out first. And then from there its AOKP as soon as it drops! But yeah. No hybrid.
Click to expand...

I'll wait with you. I think he's going to call it 3.0 and reports are in that it'll be ready today sometime.
 
jbdan said:
I'll wait with you. I think he's going to call it 3.0 and reports are in that it'll be ready today sometime.
Click to expand...


Precisely why I shall wait! Though by that time I'm sure there will be other AOSP ROMs and since I'll need to do a clean wipe anyway, I'm going to choose very careful. May go to Bugless Beast for a while or something. Dunno, food for thought :D
 
Patriot123 said:
Precisely why I shall wait! Though by that time I'm sure there will be other AOSP ROMs and since I'll need to do a clean wipe anyway, I'm going to choose very careful. May go to Bugless Beast for a while or something. Dunno, food for thought :D
Click to expand...

Can't argue with "choices" it's a good thang!
 
Patriot123 said:
One appears to have bugs though...not quite sure how a purely vanilla compiled from source for our device ROM can have bugs..?
Click to expand...
Yup. To be fair though they've rushed it and are first to bat. They both have bugs Google Now isn't working yet. Progress though in my book and so soon.
 
You must log in or register to reply here.
Back
Top Bottom