Related
Hello I have a mytouch3g with CM 4.2.10.1. Both my radio and SPL are the stock ones.
Now, I want to flash my Perfect SPL to a Non perfect one.
First of all can someone FINALLY explain to me what a non perfect SPL will do for me?
And can someone please epxplain WHICH SPL to use and a step by step guide on how to flash it? i dont want to brick my phone . I HAVE googled this and have found guides for G1 and 32A but not for mytouch (32B)
Also im not sure if this is where to post but because Dream Dev forums also server as Magic 32B forums Im going out on a limb here lol
Again any help would be appreciated!
as long as you are running CM rom you don't need to flash/update spl
... wat if i want to try another rom?
can you please not reply 'you dont need it' and instead reply what the benefits are and how to flash it?
thanks!
The reason you flash a new SPL is so that you can use different ROMs that need it. Unless you want to switch from Cyanogen then there isn't a reason to flash a new SPL. If you want to flash Haykuro's SPL (A.K.A "Death" SPL) then here are my instructions.
1. Make sure you have a custom recovery.img like Amon-Ra's or Cyan's
2. Download the new radio and Haykuro's SPL from here. http://code.google.com/p/sapphire-port-dream/
Also download whatever new ROM you want to try out that uses the new SPL. Put those 3 .zips onto your SD card.
3. Put your phone into recovery and make a Nand Backup, just in case.
4. FLASH THE RADIO FIRST!!! IF YOU FLASH THE SPL BEFORE THE RADIO THEN YOUR PHONE WILL BRICK!!!
5. Flash the SPL.
6. Flash your new ROM.
Yes, exactly in that order, and yes, you have to flash a new ROM or reflash the one you're using.
BTW, I am not responsible if you brick your phone.
what about flashing custom splash images?
and yes i do want to try some other roms
melterx12 said:
what about flashing custom splash images?
and yes i do want to try some other roms
Click to expand...
Click to collapse
Those you'll need fastboot for, and a fastboot-enabled spl (i.e. Haykuro spl). There are very nice guides in the theme section on what you'll need and how to do it
melterx12 said:
Hello I have a mytouch3g with CM 4.2.10.1. Both my radio and SPL are the stock ones.
Now, I want to flash my Perfect SPL to a Non perfect one.
First of all can someone FINALLY explain to me what a non perfect SPL will do for me?
And can someone please epxplain WHICH SPL to use and a step by step guide on how to flash it? i dont want to brick my phone . I HAVE googled this and have found guides for G1 and 32A but not for mytouch (32B)
Also im not sure if this is where to post but because Dream Dev forums also server as Magic 32B forums Im going out on a limb here lol
Again any help would be appreciated!
Click to expand...
Click to collapse
Since you said you're on a T-Mobile MyTouch 3G you might want to check out this thread
http://forum.xda-developers.com/showthread.php?t=529019
Using an SPL file for the dream, like you've been linked to in a previous post could quite possibly brick you're phone.
CyanogenMod work's on both Dream's & Sapphires but not all associated fies for theese phone are interchangeable, solely based on the fact that the ROM you're using is.
My best advice to you would be to browse the Sapphire threads before going any further with you're mod's
woot flashed my SPL to 1.33.2005 and it worked like a charm! also flashed my splash image.
jsut one question: on my bootloader screen the SPL says H, instead of G. My stock perfect SPL said G. I know H stands for HTC SPL and G is the Google SPL, but what is the difference in functionality?
melterx12 said:
woot flashed my SPL to 1.33.2005 and it worked like a charm! also flashed my splash image.
jsut one question: on my bootloader screen the SPL says H, instead of G. My stock perfect SPL said G. I know H stands for HTC SPL and G is the Google SPL, but what is the difference in functionality?
Click to expand...
Click to collapse
Did you flash the radio?
Haykuro SPL allows larger roms to be installed(i feel like a broken record repeating this) that's all you need to know the other details arent necessary to know.
no i did not flash the radio? why, do i need to?
melterx12 said:
no i did not flash the radio? why, do i need to?
Click to expand...
Click to collapse
Then you will brick you phone, radio first then SPL
this is all my info on bootloader:
------------------------------------
SAPPHIRE PVT 32B ENG S-OFF H
HBOOT-1.33.2005 (SAPP30000)
CPLD-10
RADIO-2.22.19.26I
APR 20 2009, 15:30:43
[FASTBOOT]
<VOL DOWN> HBoot Mode
<SEND> Reset Device
<ACTION> Restart to HBoot
<MENU> Power Down
------------------------------------
I followed the instructions from the first post here
http://forum.xda-developers.com/showthread.php?t=548218&page=14
but it mentioned nothing of flashing the radio... do i need to flash one? AM I SCREWED????
melterx12 said:
this is all my info on bootloader:
------------------------------------
SAPPHIRE PVT 32B ENG S-OFF H
HBOOT-1.33.2005 (SAPP30000)
CPLD-10
RADIO-2.22.19.26I
APR 20 2009, 15:30:43
[FASTBOOT]
<VOL DOWN> HBoot Mode
<SEND> Reset Device
<ACTION> Restart to HBoot
<MENU> Power Down
------------------------------------
I followed the instructions from the first post here
http://forum.xda-developers.com/showthread.php?t=548218&page=14
but it mentioned nothing of flashing the radio... do i need to flash one? AM I SCREWED????
Click to expand...
Click to collapse
You didnt mention you had the 26I radio, nevermind then thought you had a older one. Also you should have said your using mt3g since it doesnt need the radio.
i did say i have a mt3g its in my original post
im so confused. I KNOW i didnt brick my phone causei m already booted into cyanogen mod and definatly NOT bricked.
so wat the hell is going on????
why is my letter changed from a G to an H? what does this mean to me?
melterx12 said:
i did say i have a mt3g its in my original post
im so confused. I KNOW i didnt brick my phone causei m already booted into cyanogen mod and definatly NOT bricked.
so wat the hell is going on????
why is my letter changed from a G to an H? what does this mean to me?
Click to expand...
Click to collapse
Nothing. you didnt brick, i got you confused with someone else that asked about help with rooting.
You dont need to worry about the stuff in bootloader its from the SPL upgrade.
then why did my letter change from a G to an H?
should i flash something else?
im freaking out right now !
melterx12 said:
then why did my letter change from a G to an H?
should i flash something else?
im freaking out right now !
Click to expand...
Click to collapse
Do you mean in fastboot?
Its suppose to change...
I dont understand why your so concerned with that, its should say Hboot.
Sapphire/Magic/Ion/MT3G roms are here, some G1 roms work though
http://forum.xda-developers.com/forumdisplay.php?f=493
what?? No everything works i can load into bootloader, change from Hboot mode to fastboot mode, i can boot into my ROM (cyanogen 4.2.10.1) and everything seems to be working.
to clarify: in bootloader, on top it it used to show me (on stock perfect SPL) SAPPHIRE PVT 32B ENG S-ON G
now it shows me (on danger SPL) SAPPHIRE PVT 32B ENG S-OFF H
the G changed to an H
I have read that the H stands for an HTC SPL and G stands for Google SPL. Since the stock SPL was google and I changed to HTC is this going to cause any problems? and was it suppose to change to an H in the first place or did i do something wrong??
melterx12 said:
I have read that the H stands for an HTC SPL and G stands for Google SPL. Since the stock SPL was google and I changed to HTC is this going to cause any problems? and was it suppose to change to an H in the first place or did i do something wrong??
Click to expand...
Click to collapse
You didnt say that though, i was unsure of what you meant. You see that SPL is from the HTC Magic which has the H not G. It suppose to show H. That is the HTC SPL not the standard google one shiiped w/ google experience phones .
i understand that but does this affect my Mytouch 3g (which is a google phone) in any way?
Can i install the danger SPL on the dream100 pvt or i'm risking to brick the phone? i didn't saw somewhere the guide for this kind of phone....
Thanks in advance
atsic said:
Can i install the danger SPL on the dream100 pvt or i'm risking to brick the phone? i didn't saw somewhere the guide for this kind of phone....
Thanks in advance
Click to expand...
Click to collapse
There is *NO BENEFIT* to it (despite what all the MORONS will claim, it is NOT required for ANYTHING), and regardless of your hardware, there is ALWAYS a risk.
Fact is that the deathspl is NOT COMPATIBLE with ANY HTC DREAM, so don't be using it!
lbcoder said:
There is *NO BENEFIT* to it (despite what all the MORONS will claim, it is NOT required for ANYTHING), and regardless of your hardware, there is ALWAYS a risk.
Fact is that the deathspl is NOT COMPATIBLE with ANY HTC DREAM, so don't be using it!
Click to expand...
Click to collapse
it means that if i would like to install a version of eclaire where everywere is requied a danger spl i don't need this spl? I can install it with any sort of problem without the update of the spl?
thanks
atsic said:
it means that if i would like to install a version of eclaire where everywere is requied a danger spl i don't need this spl? I can install it with any sort of problem without the update of the spl?
thanks
Click to expand...
Click to collapse
All it means is that the rom dev was REALLY LAZY. All you need to do is a VERY MINOR modification and resign to the update.zip. Move some files into /cache and symlink them back.
Or, you could simply use a rom where the rom dev(s) aren't so lazy and actually made the thing to intelligently move files around...
i.e. this one: http://forum.xda-developers.com/showthread.php?t=629932
or this one: http://forum.xda-developers.com/showthread.php?t=624545
(note re the second one: the requirements list shows DEATHSPL. This is NOT the case.)
lbcoder said:
All it means is that the rom dev was REALLY LAZY. All you need to do is a VERY MINOR modification and resign to the update.zip. Move some files into /cache and symlink them back.
Or, you could simply use a rom where the rom dev(s) aren't so lazy and actually made the thing to intelligently move files around...
i.e. this one: http://forum.xda-developers.com/showthread.php?t=629932
or this one: http://forum.xda-developers.com/showthread.php?t=624545
(note re the second one: the requirements list shows DEATHSPL. This is NOT the case.)
Click to expand...
Click to collapse
Im confused. Im not trying to offend you (as maybe Im not getting something), but are you saying that Dwang and Cyanogen ar lazy? After all, they are responsible for Super D 1.8 (which I hear is AWESOME) and it requires the danger spl.
Or is there a better way to flash Super D?
Dai323 said:
Im confused. Im not trying to offend you (as maybe Im not getting something), but are you saying that Dwang and Cyanogen ar lazy? After all, they are responsible for Super D 1.8 (which I hear is AWESOME) and it requires the danger spl.
Or is there a better way to flash Super D?
Click to expand...
Click to collapse
They are not responsible for Super-D but rather their work is the base for it. I don't agree with lbcoder but I understand what he is saying. Lazy is not the choise of words I would choose to use.
billquinn1 said:
They are not responsible for Super-D but rather their work is the base for it. I don't agree with lbcoder but I understand what he is saying. Lazy is not the choise of words I would choose to use.
Click to expand...
Click to collapse
Gotcha. Im assuming then that you have nothing against using the Danger SPL when required (and if the hardware matches)?
Lazy, ignorant, how about a FAKE.
99.9% of rom cookers haven't the FAINTEST idea what they're doing. They haven't written a single line of code in their LIVES and all they do is mix and match APK files in the update archive, put their own personalized B.S. in the build.prop file, and resign the archive.
So "lazy" *IS* the right word. Too lazy to actually learn something of any significance. Note: the work needed to get ANY rom onto a STOCK SPL is quite literally *TRIVIAL*. Drag a few files around, add a couple of lines to the update-script, done.
Dai323 said:
Gotcha. Im assuming then that you have nothing against the Danger SPL when required (and if the hardware matches)?
Click to expand...
Click to collapse
The only hardware that it matches is HTC MAGIC, which is where it was copied from.
lbcoder said:
The only hardware that it matches is HTC MAGIC, which is where it was copied from.
Click to expand...
Click to collapse
Wow. Ok, now I'm a bit paranoid to flash Super D tomorrow on my G1 (waiting on Class 6 micro), as I haven't heard this issue brought up before.
The forums have been chock full of anger lately. Not sure where it all comes from except maybe the weather has people down.
I think the WG roms do not require the Danger SPL so that would be a good choice. Our phones are a very tight fit but some roms do fit just fine.
I am running out of here with my head down! Good Luck.
So no answers that are clearing the situation. Is possible or not to install Danger SPL/ Death SPL over the DREA100 PVT version???
atsic said:
So no answers that are clearing the situation. Is possible or not to install Danger SPL/ Death SPL over the DREA100 PVT version???
Click to expand...
Click to collapse
Yes just follow this guide and you will be fine.
http://forum.xda-developers.com/showthread.php?t=625886
Joe333x said:
Yes just follow this guide and you will be fine.
http://forum.xda-developers.com/showthread.php?t=625886
Click to expand...
Click to collapse
The problem is that on my phone is showed DREA100 PVT and not "DREAM PVT" as the guide says to be. Can i flash anyway?
atsic said:
The problem is that on my phone is showed DREA100 PVT and not "DREAM PVT" as the guide says to be. Can i flash anyway?
Click to expand...
Click to collapse
Which SPL are you currently using? You should be fine since you have a PVT board, its just the DVT boards that cannot use the Danger SPL. When I reboot holding the camera button this is what the top line says
"DREAM PVT 32B ENG S-OFF"
What does yours say?
Joe333x said:
Which SPL are you currently using? You should be fine since you have a PVT board, its just the DVT boards that cannot use the Danger SPL. When I reboot holding the camera button this is what the top line says
"DREAM PVT 32B ENG S-OFF"
What does yours say?
Click to expand...
Click to collapse
holding camera and power button appear
DREA100 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-2.22.19.26I
This in in the upper left corner.
More down and centered is also written Seria10
Hope that is useful.
Are you still on the stock SPL? I just did a little googling and it seems that DREA100 PVT 32B is normal to see on the stock SPL. The key is to know that you have a PVT board, which you do. I would say you should be fine. Check out the link in my sig and ask in that thread and maybe someone else will weight in. The dev section gets a lot more traffic than the q&a section.
Don't let lbcoder scare you, if you know what your doing, DEATH spl is completely safe. Follow Joe's guide, its easy to follow and guaranteed not to screw you up. I've been using death spl for the last few months and my G1 is still running It makes life a helluva lot easier for you just to have it installed, then you won't have to worry about a rom not fitting in your phone. GL
Joe333x said:
Are you still on the stock SPL? I just did a little googling and it seems that DREA100 PVT 32B is normal to see on the stock SPL. The key is to know that you have a PVT board, which you do. I would say you should be fine. Check out the link in my sig and ask in that thread and maybe someone else will weight in. The dev section gets a lot more traffic than the q&a section.
Click to expand...
Click to collapse
Yes of course is the stock SPL.
I posted on the other 3ad too. Thanks anyway!
hi guys I've already read this:
http://forum.xda-developers.com/showpost.php?p=5501185&postcount=1
but my fear persists...
Dream PVT 32B SHIP S-ON
HBOOT-1.38.0000 (DREA20000)
CLPD-4
RADIO-2.22.19.26I
Feb 28 2009, 18:40:30
PVT mean i can do that but if I brick there's nobody who can help me..
Wrong section but since your radio is already 26i you should be safe.
1. Flash danger spl
2. Reboot via home and back
3. should be back in your recovery
4. reboot again to be safe I always do.
5. flash the radio 2.22.23.02
6. reboot via home and back
if some can give better directions go ahead.
Also it's safer to flash through Fastboot, but I don;t really know how.
This belongs in the Q/A section not the Dev section. That being said just follow the guide and you will be fine.
Thread Moved to Q&A.
AustinAce said:
Wrong section
Click to expand...
Click to collapse
Joe333x said:
This belongs in the Q/A section not the Dev section.
Click to expand...
Click to collapse
sorry guys I didnt know I thought it was right here
anyway, ok I'll try. I hope it goes well
im rooted using androot,i have rom manager free and have done the clockwork and nandroid backups and followed all instructions and it just wont work and always says "status 7" when installing through clockwork
its my first time trying any of this.
phone: htc g1
build number:dmd64
firmware 1.6
cyanogenmod 6.0.0
any help would be greatly appreciated!!!!!!
I am also getting this error!
E:Error in /sdcard/update-cm-6.0.0-DS-signed.zip (Status 7)
Click to expand...
Click to collapse
Here's some info from my device.
DREA100 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-2.22.23.02
Sep 2 2008
maybe?
read this link and maybe it will shed some light on the subject if you haven't already read it.
http://forum.cyanogenmod.com/topic/4118-firerat-patch-help/
johnson8cyl said:
read this link and maybe it will shed some light on the subject if you haven't already read it.
http://forum.cyanogenmod.com/topic/4118-firerat-patch-help/
Click to expand...
Click to collapse
After reading what you supplied looks like I needed DangerSPL
My HBOOT read 0.95.0000 and it needs to read 1.33.2005
After flashing DangerSPL install went smooth!
dannycsc said:
After reading what you supplied looks like I needed DangerSPL
My HBOOT read 0.95.0000 and it needs to read 1.33.2005
After flashing DangerSPL install went smooth!
Click to expand...
Click to collapse
Glad to hear. Good for you. I suspected something didn't go as u thought originally. Hope all is well
Sent from my HTC Magic SparksMod using XDA App
i have same problem but i did install the dangerspl, im using this tut:
wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod#Rooting_the_HTC_Dream_2
but i dont kn ow maybe something is missing from the root part of that tut?
FIXED , it was a missnamed ROM
(actually wrong ROM with right name lol)
I have a Rogers Dream/G1 with T-Mobile rc29 rom (doh!), which works and is usable but I want to get back to CM5. Please show me the way or put me out of my misery if its hopeless.
Recovery hangs at Tmobile G1 screen.
Fastboot gives me "00028002 Not Allow" code then is stuck with serial0.
DREA210 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-1.22.12.29
Tried Adb to get amon-ra 1.7.0, but still won't boot into recovery and is stuck at G1 screen. No memory error, just an immediate echo of the "flash_image recovery data/local/recovery.img" command after I hit enter.
fastboot won't show my device in cmd when at the 4colored screen but adb does recognize.
I'm pretty sure I mixed up the radio and spl, but does having access to the OS give me any options?
Please, point me in the right direction.
****SOLVED**** see Post#20 for my conclusion.
Download clockwork recovery, flash clockwork, then you'll have recovery?
Not sure tho, I think this was how I did it.
I think what you're talking about is ROM Manager, it includes Clockwork Recovery if I understand the dev's description correctly. I haven't tried it myself though.
Seems to me, that he is on a stock ROM and doesn't have root access.
If the phone is booting, a chance could be, to install 1-click-root (don't know how it is called exactly, but you can google for it) and then from there to install a custom recovery. After that, you can install CM5 or something else. Probably first I would install is an engineering SPL (1.33.2003 for example) which supports fastboot. With your current SPL you will not have a chance to get fastboot running.
But be careful: 1.33.2003 supports only radio version 1.x and 2.x. I am not sure if 1.33.2003 is the best solution for you, because you have a rogers dream.
i recomend the old way.. get the fflashrecapk. and use io file manager to flash it.. only problem is you need to be 1.5 if your on 1.6 than you need to downgrade.. but that would be difficult since you have no recovery lol
While a bit more work.. before all the how to's confuse you into bricking your phone, I'd make yourself a gold card, and use it to flash the orange nbh from the 2708+ thread.. (rename to DREAIMG.nbh and place on the goldcard, then boot with camera+power it will ask you to flash it)
Once you have the orange rom you will have fastboot and a 2.x radio.. if you don't need the 3.22 radio .. just flash the 2708+ radio+spl+hboot as per normal followed by a rom.. if you do need the 3.22 radio (rogers customer who has not signed the wavier and wishes to keep data) either flash the rogers e911 update and re-root or 1.33.2005+3.22.26.17 and a rom
Sorry lack of links.
is it rooted?
maybe you can flash the recovery through terminal
Thanks for the replies, lots to research.
I'v tried a bunch of rooting methods.
exploid pushed from ADB said it worked (but didnt)
SuperOneClick said it worked after some rapid OFF-ON-OFF-ON debugging(but didnt install superuser even after reboot)
Universal androot forcecloses on launch
flashrec has the "download cyan...." button blocked out, tried renaming amon-ra to the recovery-backup.img and it said successful, but still is stuck at g1 screen.
I found another post with someone in the same situation at:
http://forum.xda-developers.com/archive/index.php/t-580669.html
They did the same thing by flashing the tmobile firmware 1.0 and we have the same numbers:
Model Number: T-Mobile G1
Firmware version: 1.0
Baseband Version: 62.33.20.08H_1.22.12.29
Kernel Version: 2.6.25-01843-gfea26b0 [email protected]#6
Build Number: kila-user 1.0 TC4-R29 115247 ota-rel-keys,release-keys
When I start up (CAMERA + POWER) I get the following settings (on red/green/blue/white screen *sigh*)
DREA210 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-1.22.12.29
Sep 2 2008
Serial 0
Funny thing is I was so excited when SuperOneClick said it was successful and asked if I wanted to donate that I didnt even check if I had superuser before going through paypal. I'v wasted so many hours on this dinosaur G1 but damn I want it back to CM5. Please continue with the help.
kl3vr said:
Thanks for the replies, lots to research.
I'v tried a bunch of rooting methods.
exploid pushed from ADB said it worked (but didnt)
SuperOneClick said it worked after some rapid OFF-ON-OFF-ON debugging(but didnt install superuser even after reboot)
Universal androot forcecloses on launch
flashrec has the "download cyan...." button blocked out, tried renaming amon-ra to the recovery-backup.img and it said successful, but still is stuck at g1 screen.
I found another post with someone in the same situation at:
http://forum.xda-developers.com/archive/index.php/t-580669.html
They did the same thing by flashing the tmobile firmware 1.0 and we have the same numbers:
Model Number: T-Mobile G1
Firmware version: 1.0
Baseband Version: 62.33.20.08H_1.22.12.29
Kernel Version: 2.6.25-01843-gfea26b0 [email protected]#6
Build Number: kila-user 1.0 TC4-R29 115247 ota-rel-keys,release-keys
When I start up (CAMERA + POWER) I get the following settings (on red/green/blue/white screen *sigh*)
DREA210 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-1.22.12.29
Sep 2 2008
Serial 0
Funny thing is I was so excited when SuperOneClick said it was successful and asked if I wanted to donate that I didnt even check if I had superuser before going through paypal. I'v wasted so many hours on this dinosaur G1 but damn I want it back to CM5. Please continue with the help.
Click to expand...
Click to collapse
ok ummm wow you did a lot lol are you sure you did the flaskrec.apk thing right? so as of right now your phone is not rooted? and you are on 1.0? if thats the case you should get automatic updates and hopefully that could help you.. if not try downloading rom manager than flash the clockwork recovery.. personally i hate clockwork but if you can get that to work than i could help you get back to RA if you would like..
Well its a one-click solution, I must have missed the options... I installed it and ran the back up, but the "download" button was grayed out. was I supposed to do something with the entry field?
Rom Manager gives me "Application install unsuccessful" using AndExplorer and I think Clockwork gave me this problem in the first place back when I was using CM6.
kl3vr said:
Well its a one-click solution, I must have missed the options... I installed it and ran the back up, but the "download" button was grayed out. was I supposed to do something with the entry field?
Rom Manager gives me "Application install unsuccessful" using AndExplorer and I think Clockwork gave me this problem in the first place back when I was using CM6.
Click to expand...
Click to collapse
I think Ezterry's post (#6) is your best option
you don't mention you have tried that
you will need to do some research into goldcards and finding the orange.nbh link
hint for the orange see threads started by ezterry (via his profile) look at the kernel for 2708 thread
Ok thanks, I'v got my gold card made but is safe to flash 1.33.200* SPL with 1.22.12.29 Radio? Isnt it a DangerSPL? Sorry if thats way off base.
kl3vr said:
Ok thanks, I'v got my gold card made but is safe to flash 1.33.200* SPL with 1.22.12.29 Radio? Isnt it a DangerSPL? Sorry if thats way off base.
Click to expand...
Click to collapse
for the record
1.33.2003 is compatible with 1.x and 2.x radios but will brick with 3.x
1.33.2005 is compatible with 2.x and 3.x radios but will brick with 1.x
so 1.33.200* is only compatible with 2.x
read Ezterry's 2708 post, the answers you seek are in it
sorry for delay lol but with the flashrec file wat you do is press backup than when your typing in the box you have to put exactly what your file says...
ex.. sdcard/recovery-RA-dream-v1.0.7-cyan.img (yours could be diff but make sure you type exactly what your file says that you placed on sd card) hope it helps
You guys are awesome, thank you everyone who was interested and especially ezterry, Effdee and Idrifta for the enduring help. I'm now on CM5.0.8 2708+ and loving it.
Final issue, I'm wondering about going to EBI1 to get 3.22 radio. Is it as simple as updating hboot to 1.33.2010 then flashing 3.22? Is it worth doing?
Again, sorry if that is way off base but this is the first week my phone has been usable in months, and I won't jeopardize it again.
New phone specs:
DREA PVT 32B SHIP S-ON
HBOOT-1.33.0013d (DREA21000)
CPLD-4
RADIO-2.22.27.08
Recov: Cyan1.7
Rom: CM 5.0.8 - 2708 port
Thank you,
-kl3vr
kl3vr said:
You guys are awesome, thank you everyone who was interested and especially ezterry, Effdee and Idrifta for the enduring help. I'm now on CM5.0.8 2708+ and loving it.
Final issue, I'm wondering about going to EBI1 to get 3.22 radio. Is it as simple as updating hboot to 1.33.2010 then flashing 3.22? Is it worth doing?
Again, sorry if that is way off base but this is the first week my phone has been usable in months, and I won't jeopardize it again.
New phone specs:
DREA PVT 32B SHIP S-ON
HBOOT-1.33.0013d (DREA21000)
CPLD-4
RADIO-2.22.27.08
Recov: Cyan1.7
Rom: CM 5.0.8 - 2708 port
Thank you,
-kl3vr
Click to expand...
Click to collapse
hey no prob glad to help!! how did you end up fixing it? haha just curious
kl3vr said:
I'm now on CM5.0.8 2708+ and loving it.
Final issue, I'm wondering about going to EBI1 to get 3.22 radio.
Click to expand...
Click to collapse
Why ebi1 is equivalent to the old ebi0 and you loose the extra ram.
Thus unless there is a very specific reason it's a downgrade
kl3vr said:
New phone specs:
DREA PVT 32B SHIP S-ON
HBOOT-1.33.0013d (DREA21000)
CPLD-4
RADIO-2.22.27.08
Click to expand...
Click to collapse
Best stay as is or upgrade the radio to 2.22.28.25.. As it has been distributed world wide. (Including to all locations 2.22.27.08 was previously distributed)
what did you do?
I would like to know if you solved this issue as mine is similar. I DO have root though, but i have no recov/fastboot. I am using a dev phone though.
ps, grats on getting it working
cacaface said:
I would like to know if you solved this issue as mine is similar. I DO have root though, but i have no recov/fastboot. I am using a dev phone though.
ps, grats on getting it working
Click to expand...
Click to collapse
If you flashed 0.95.0000 you are no longer using a dev phone (what do you see when you boot holding camera?)
The good news is that the ADP1 used the universal CID (11111111) and is thus not restricted to a particular carriers nbh file.. so you can probably just flash the orange nbh without the goldcard [just renamed DREAIMG.nbh on the root of your SDCard], then follow the 2708+ radio instructions.. or install 1.33.2003/5 via fastboot if you need the old radio.
The reason I'm pointing to the orange nbh is it will let you bypass the whole "I bricked my phone because I insisted on flashing death SPL via recovery" since you have an engineering SPL and 2.x radio after flashing that orange NBH from the 2708+ thread.
This is what worked for me, going from:
- a non responsive recovery
- OS locked at activation, so no usb debugging
- OS refused to root
- quadicolored fastboot screen that wouldnt recognize usb
To CM5 2708+ with RA-cyan1.7.
Before this thread I had to use this to get post the verizon data plan only activation to enable usb debugging.
Made a goldcard
Put the orange nbh renamed to DREAIMG.nbh (can't remember where i got it from, just searched) on the goldcard, Booted with camera+power to get fastboot, and applied the update.
Followed ezterry's post and at step 5 flipped over to this post on CM5 2708+
Now I'm gonna update the radio using exterry's advanced zips. Thanks again everyone, another successful thread.