Database Develop

Stuck G1 - but Not your typical

Okay.
I dont think my problem is typical, and Ive searched google and xda for answers. Some situations seem similar, but none exact.
Here is the story:
G1 was running wifi tether and on charge. No bumps or bruises, just sitting by itself. The tether stopped working, so I went over to look at the G1 and the phone was frozen. Display was lit up and working, just frozen. Had to pop the battery out to shut it down.
After powering back up, the sits at the splash screen indefinitely.
I can go into fastboot but I can NOT get into recovery.
I have going into fastboot usb mode and:
1) flash a recovery image (works)
2) flash a nandroid backup (works)
3) flash rc29 (see below)
4) flash hboot (always fails)
What I mean by works is the flash indicates it was good, but there is no change in functionality of the phone. Hboot gives me device errors.
Dream PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA10000)
CPLD-4
Radio-2.22.19.26I
Apr 20 2009,15:30:43
I have also flashed a different splash image - and even though it says it succeeded the image doesnt change.
When I attempt to flash the original RC29 using the SD card mode or fastboot mode it indicated I need HBOOT 1.33.2004. 2004 *will not install* --- it gives an error (I think something to the effect of wrong device.)
I know my way around fastboot and adb, but I dont know what "hboot mode" is used for. For grins, I tried flashing the recovery in hboot mode and it says "waiting on device" forever.
It seems almost like this is a hardware problem that is presenting itself as a software issue.
Also - *sometime* when I hold home/power to try to boot into recover the phone will connect to ADB (listed in adb devices) but no commands seem to work.
Im an a loss. 10+ hours trying to fix this thing...
Any ideas?
Thanks.
Blade

Blade10 said:
When I attempt to flash the original RC29 using the SD card mode or fastboot mode it indicated I need HBOOT 1.33.2004. 2004 *will not install* --- it gives an error (I think something to the effect of wrong device.)
Click to expand...
Click to collapse
Tried with a goldcard?

No. Maybe I didnt read enough, but I thought the goldcard required a WM Device? All my machines are win xp, obvously I can use a live cd to boot linux.
BTW, the SDcard method of installing dream.nbh (RC29) gives me a checksum error, while fastboot finishes but doesnt make a difference. Yes, tried different SD cards and ran checksum after coipying to the card - checksum is correct.
Any other ideas, or maybe some links that make a goldcard easy?
Thanks,
Blade

Stuck at t-mobile logo after flash danger spl

Phone spec:
HTC G1
4.2.15.1 cyanogen mod
2.22.23.02 Radio
Dream PVT 32B ENG
I've been reading several post but could not find a fix for my phone. I had ADB running before when I install the cyanogen mod. When I plug the phone into usb my computer cannot detect the phone. When I tried to run ADB it said there is no device. But when i tried the fastboot device my phone show up.
C:\android-sdk-windows\tools>fastboot devices
MB010LC08461 fastboot
What step should i take to fix my soft-brick phone?
Thank you

This is a real simple fix & there are many posts on this topic (which belongs in the Q&A section btw)
Getting stuck at g1 screen is standard after updating to that spl. It requires a rom be flashed after the update is complete
What recovery image do you have installed? Chances are, if you can access fastboot, recovery will work too. Boot into it, wipe, and flash a working rom from SD.
Otherwise: enter fastboot wipe and flash good system & boot partition images to the device

phimtau123 said:
Phone spec:
HTC G1
4.2.15.1 cyanogen mod
2.22.23.02 Radio
Dream PVT 32B ENG
I've been reading several post but could not find a fix for my phone. I had ADB running before when I install the cyanogen mod. When I plug the phone into usb my computer cannot detect the phone. When I tried to run ADB it said there is no device. But when i tried the fastboot device my phone show up.
C:\android-sdk-windows\tools>fastboot devices
MB010LC08461 fastboot
What step should i take to fix my soft-brick phone?
Thank you
Click to expand...
Click to collapse
You've got fastboot working... what's the problem? Load a system image and be happy!

Mod edit: not dev related, moved to q&a

I'm not very familiar with fastboot and it command.... I do however have the cyanogen rom on the sd card. wat command would i use to flash that rom?

Bricked? Can't get out of bootloader & "not allow" problem

I dug too greedily and too deep, and now I'm afraid my phone is bricked. Any help would mean the world to me!
Summarized: phone will only boot into bootloader, and not further. Installing images does not work because of a "not allow" error message.
Current device situation
Works: boot into bootloader with camera/power, boot into standard google recovery with home/power
Does not work: Boot to full OS. Powering the phone just starts the bootloader. Fastboot/ADB
Device info:
Dutch T-Mobile G1, 1.5 years old.
Bootloader screen:
DREA110 PVT 32B
HBOOT-0.95.0000
CPLD-5
RADIO-1.22.12.29
Sep 2 2008
Serial0
Installed ROM
No clue! See below.
What I did before the brick
I had a fully working, rooted, installation of OpenEclair 1.2.0.1. SPL (forgot, by this time, which one), newest radio, Cyanogen's recovery, and all that.
OpenEclair started refusing to boot after batteries had been drained once. Needing phone immediately, I hastily installed dream_devphone_userdebug-ota-14721.zip from my SD.
Noticed that phone was not rooted anymore. Fatal mistake.
Wanted to re-root. So, followed (to the letter) all steps under "Downgrade" on Cyanogen's Cyanogenmod full update guide for the g1/dream firmware. I.e. tried to install RC7 via DREAIMG.nbh (rightly spelled)
Rebooted.
What then happened
G1 finished installing RC7, then I rebooted. On subsequent boots, it would directly go to the bootloader and not the OS. I think somehow the install corrupted.
What I've tried since the brick
Searching forums: Could not find situations similar to mine with any answers.
ADB/Fastboot: I've tried both of these. For ADB, it seems you need to be able to get into full Android mode, so that's a no. Fastboot does not seem to be enabled on this bootloader (no mention of it to be found, logically, since it's a stock bootloader). In windows, USB device is not recognized, throws an error and allows no installation of drivers.
Nandroid: Useless without working ADB/fastboot? I do have several backups of old working installs.
Images: Tried if re-downloaded RC7 or RC29 worked. No dice. Gives 0028022 "not allow"
Installing dream_devphone_userdebug-ota-14721.zip using the recovery mode. Gives no signature/verification filed errors.
Goldcard: Have no winphone, or access to one. Terminal emulator method does not work without working Android OS...
I'm at a loss what to try anymore. Help much appreciated!

Sigh .. your mistake was flashing an nbh in the firstplace..
The ota image is for the android dev phone and had root access over adb.. there are even guides as to how to reinstall a custom recovery from the ota.
Also its most likely that you had danger or another fastboot enabled spl that could have been used to get yourself out of any firmware issue.
However now you have a half installed stock T-Mobile system.. and will need to reflash a nbh.
This will either require a goldcard (see if you can get your Linux PC to read the sd cards cid, or find someone in your area to make one for you)
Or a Dutch T-Mobile rru/nbh not sure I've heard of such a thing in the wild.

G1 get's to Fastboot, but not recovery

Hi there.
This is not the first problem I have had with my G1 and Cyanogen cm5 or cm6. Yesterday my phone was working just fine, battery got low so I turned it off and out it on the charger. So I go to turn the phone on and I am stuck at the bootscreen.
I can get into fastboot use the cam/power button combo. But I can not get into recovery at all.
At the hboot/fastboot screen I have the following listed, BTW it's the screen with the 3 androids at the bottom on skateboards.
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (Drea10000)
CPLD-4
RADIO-2.22.23.02
Apr 20 2009, 15:30:43
When I switch over to Fastboot then back to Hboot screen I get this.
SD checking.
Loading...[DREADIAG.zip]
No image!
Loading...[DREADIA2.nbh]
No image or wrong image!
Loading...[DREADIAG.nbh]
No image or wrong image!
SD Checking...
Loading...[DREADIAG.zip]
No image!
Loading...[DREADIA2.nbh]
No image or wrong image!
Click to expand...
Click to collapse
What can I do to get back in business? If I have to put it back to stock, that is fine. I plan on selling it and getting the new Samsung Vibrant.
I have to stock 1gb card in the G1 right now. I have the following files on it.
recovery.img
update.zip
DREAIMG.nbh
In fastboot I get this for device.
HT852GZ12970
UPDATE:
I have been able to flash recovery via fastboot, now just trying to get a good image on there to reflash.

Also curious about this.. friend's having the same problem with the same rom.

Well I am back up and running.
What I had to do was flash a new recovery image using fastboot. Once I did that I was able to boot into recovery; wipe everything and reflash a new ROM (went with SuperBad, since CM keeps messing me up).
If you need more details, let me know.

svtcontour said:
Well I am back up and running.
What I had to do was flash a new recovery image using fastboot. Once I did that I was able to boot into recovery; wipe everything and reflash a new ROM (went with SuperBad, since CM keeps messing me up).
If you need more details, let me know.
Click to expand...
Click to collapse
I was going to tell you to do just that until I read:
UPDATE:
I have been able to flash recovery via fastboot, now just trying to get a good image on there to reflash.
Click to expand...
Click to collapse
I thought you had figured it out already. I probably could have saved you some time. Sorry.

How did you flash recovery in fastboot? Right now I am going through the same thing that you did!
I have a G1/Cyanogen 5.0.8

mjybarr said:
How did you flash recovery in fastboot? Right now I am going through the same thing that you did!
I have a G1/Cyanogen 5.0.8
Click to expand...
Click to collapse
Code:
fastboot flash recovery recovery.img
The standard procedure is to power on the phone with camera/power button combo, be sure to get the phone into fasboot mode.
Open up the CMD window in windows, CD to the directory you have the recovery.img file in. Use the above command. Then you can wipe and reinstall the update.zip with another rom.
That should do it,l assuming you already installed all the USB and ADB drivers and software.

svtcontour said:
Code:
fastboot flash recovery recovery.img
The standard procedure is to power on the phone with camera/power button combo, be sure to get the phone into fasboot mode.
Open up the CMD window in windows, CD to the directory you have the recovery.img file in. Use the above command. Then you can wipe and reinstall the update.zip with another rom.
That should do it,l assuming you already installed all the USB and ADB drivers and software.
Click to expand...
Click to collapse
So what is CMD and what do you mean "CD to the directory you have the recovery.img file in." I did some research on xda-forums about adb, sdk, fasboot. Do I need to do that and install all those programs. As you can tell I am a new to this. So I need some thorough directions. Thank you so much for helping. I need to get back to Android, right now I am using an old blackberry......and it totally sucks!

CMD will bring up the DOS window in windows. Go to the START button and look for RUN, them type in CMD. A black window will pop up.
CD means change directory. Example: cd c:\temp\adb will bring you to that exact directory. Just make sure you remember where you put the recovery.img file and CD to that.
I would go to this post and follow the directions to install ADB and the USB drivers.
http://androidcommunity.com/forums/f10/adb-fastboot-for-rookies-18124/

I had the same problem in a rooted Hero, but i lost the recovery image as well as the ROM. I could not flash the new recovery image using fastboot because my SPL does not allow it.
Search in google for
Follow the instructions in
wiki.cyanogenmod.com/index.php?title=RE-recovery-img#Restoring_the_custom_recovery_image
to flash a recovery image (cyanogen or amon-ra, just check it to be the one for your model).
It solved my problem!

I have the same problem (with CM6)
adb works well, but fastboot is waiting for devices
G1 is on fastboot usb screen
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA20000)
CPLD-4
RADIO-2.22.19.261
Apr 20 2009,15:30:43
the command "fastboot devices" doesn't work : i don't even have a feedback like "list of devices attached"
does anyone know what I have failed ?
Update: miserable failure: I forgot to cd to C:\path\android-sdk-windows\tools\
sorry about it

Reinstalling recovery, then installing the latest nightlies did the trick for me. Did not need to wipe.
Hope this helps.

[Q] Bricked my CEll upgrading the radio

Hello guys,
I know the first thing you may think is this is another moron who bricked his Cell. But please be patient with me and at least let me learn from my loss. Please let me know what I did wrong.
First I read 3 main thing before doing anything,(1) [Guide] One-Click Root for Rogers HTC Dream:, (2) the post by HYKO and and finally CyanogenMod Wiki. Since I cannot post URL I attached them at the end.
So first I tried to get a hboot 1.33.2005 SPL using the source (1) which went ok.
then I used CyanogenMod Wiki (3) to root my HTC DREAM. Every thing went ok till I tried to update the radio. After I flashed the radio my cell hangs on the rogers logo and does not go any further. I can go to the fastboot (camera butt and END). it is S-off and 1.33.2005 SPL. However, I can not reach the recovery menu (Home and END). I tried flashing back to the older radio 3.22.20.17 and 2.22.29.26I (using the haykuro zip file). none of them worked.
First I want ot know what did I do wrong. Second I noticed my SDcard is broken, and the HBOOT looks for deaimg and deardiag on sd. does anyone know if I can unbrick it using this.
Thanks
alrsar
(1)
1. Download Haykuro's root kit here.
2. Extract the recovery.img and update.zip files from the download and copy them to the root of your sdcard's fat32 partition (if you haven't partitioned your card yet for A2SD, then just the root of the card itself).
2. Last time I checked, the one-click root app, flashrec, has been pulled from the Market, so download it here.
3. Install the app and start it, it will look like this:
4. Tap 'Backup Recovery Image', in some cases the app will fail to backup the image. This shouldn't be a problem, but if it works, it's always nice to have a backup.
5. In the blank above the greyed-out button enter '/sdcard/recovery.img' without the quotes. If you were successful in making the backup, the top button should change to white and say 'Flash Custom Recovery Image'. If not, don't worry, there is a hidden button to the right of the backup button that will bypass the backup requirement. Like so:
6. Press 'Flash Custom Recovery Image'. If you get a flash failed message, try flashing with your phone unplugged from USB.
7. Power your phone down.
8. Power up your phone while holding the home button. You should get the older 1.2 Recovery Menu. If your phone hangs at the Rogers logo, remove your battery, re-install or try the 3-finger salute (Phone, menu, and power button together) and try again. If it still hangs on the Rogers logo, reboot without the home key, this will bring you back to normal boot. You won't be rooted but you won't be bricked.
9. Once you're at the recovery menu, choose the second option, apply sdcard:update.zip. In some cases you may get an error something like E: not found. If you choose the second option again, it should find the update.zip alright and then press home to continue.
10. Now click on reboot (Home & Back). Press and hold the camera button and you should boot into the new 1.33.2005 SPL.
11. If all has gone well and you see hboot 1.33.2005, you can safely follow the rest of the rooting instructions in this thread. There's also a great set of instructions for installing Cyanogen's 4.2.X roms in the same thread. The post is here.
Of course, these instructions may be rendered moot if Rogers chooses to fix the vulnerability that allows one-click root at which point we'll have to hope someone manages to find a way around the so-called 'perfect' SPLs.
If after a couple attempts you remain stuck at the Rogers logo, remove the battery, reinstall it and then power up normally. You should then boot back to the unrooted phone and it will restore the default recovery. You may not be rooted, but at least you're not bricked.
(3)
1. You will need fastboot on your computer to run the following commands. Set up ADB and fastboot on your computer.
2. Download exploid & Amon_Ra's Recovery:
* exploid (includes the source): Download
* Amon_Ra 1.7.0: Download
3. Rename Amon_Ra's Recovery Image to simply recovery.img.
4. Put both the exploid file & Amon_Ra's Recovery in the same directory as adb.
5. Turn on USB Debugging (Settings » Applications » Development).
6. Connect the Rogers Dream to the computer.
7. On the computer, open terminal & navigate to the adb folder
cd /path/to/adb/
8. Type in the following commands:
adb push recovery.img /data/local
adb push exploid /sqlite_stmt_journals
adb shell
cd /sqlite_stmt_journals
chmod 777 exploid
./exploid
9. You will see a message come up. The exploit has now been setup. Unplug & re-plug in the USB cable to the computer.
10. Now type in the following commands:
adb shell
rootshell
NOTE: This will prompt for a password, the password is "secretlol".
chmod 666 /dev/mtd/mtd1
flash_image recovery /data/local/recovery.img
NOTE: The first time this command runs, it may return "mtd: read error at 0x00000000 (Out of memory)". Simply run this command again & it should run without error.
11. The Rogers Dream has now been rooted & will have Amon_Ra's Recovery on it.
Flashing Radio
If the Rogers Dream already had the 911 patch, then the phone will already have the latest radio. Follow these instructions if the Rogers Dream did not have the 911 patch.
1. Download the latest version of the radio (3.22.26.17).
2. Rename the radio image to simply radio.img.
3. Power off the Rogers Dream.
4. Boot into bootloader mode. Hold the Camera button while powering on the Rogers Dream.
5. Connect the Rogers Dream to the computer.
6. On the computer, open the command prompt/terminal & navigate to the Android SDK Tools folder.
7. Type in the following command:
fastboot flash radio radio.img
8. Once finished, you can restart the Rogers Dream.

Perhaps try flashing a new recovey via fastboot?(aka screen with android skateboarding) with adb, looks at the rom bible in the dev section for more details. You also need the android sdk installed on your computer to do so, and a working mini usb cord.

ok first, you are not bricked, brick means cannot get into bootloader (camera+power) nor recovery (home+power), and it will be useless like a brick,thats why we call it "bricked" when you messed it up. Unless you use the jtag method, but thats for the super hardware geeks not for the people here in the forum.
Since you are not bricked, you can try to turn on the phone and wait for at least 5 minutes and see if the screen is still stuck on the same logo, because sometimes it takes quite long for the first boot after your new Flash. If it really stuck on the same logo for the damn 10 minutes, then you can try the following ways.
I dont know what version SPL and radio you use, but remember, always flash the radio first, then restart the phone then flash the SPL, because this really can brick your phone (i done it once)
- if your recovery support usb mount, then re-download the roms and double check with MD5, make sure the rom is 100% identical, then reflash it. because defected rom always caused your kinda problems.
-if it still doesnt work, do this also with your SPL and Radio zip files
-if still doesnt work, get the dreaimg.nbh file to sd, then camera+power to bootloader, and downgrade to 1.0. then start to root again carefully this time.

americanxo said:
I dont know what version SPL and radio you use, but remember, always flash the radio first, then restart the phone then flash the SPL, because this really can brick your phone (i done it once)
- if your recovery support usb mount, then re-download the roms and double check with MD5, make sure the rom is 100% identical, then reflash it. because defected rom always caused your kinda problems.
-if it still doesnt work, do this also with your SPL and Radio zip files
-if still doesnt work, get the dreaimg.nbh file to sd, then camera+power to bootloader, and downgrade to 1.0. then start to root again carefully this time.
Click to expand...
Click to collapse
Thanks for your reply, I have PVT 32B ENG S-OFF HBOOT -1.33.2005 drea21000
cpld-4
Radio 3.22.26.17
I can only go to the FASTBOOT mode (Camera and END) I dont have the recovery mode. So I think it rules out the first option. I can flash radio and done ut couple off time. No change to the situation. I dont know how to flash the SPL I should. Can you tell me what exactly the last option does?
thanks
Alireza

my FASTboot command works but ADB cannot connect. I assume you mean I should flash the recovery, right?

alrsar said:
Thanks for your reply, I have PVT 32B ENG S-OFF HBOOT -1.33.2005 drea21000
cpld-4
Radio 3.22.26.17
I can only go to the FASTBOOT mode (Camera and END) I dont have the recovery mode. So I think it rules out the first option. I can flash radio and done ut couple off time. No change to the situation. I dont know how to flash the SPL I should. Can you tell me what exactly the last option does?
thanks
Alireza
Click to expand...
Click to collapse
From where you are flashing fastboot or rom....
If you are able to go to fastboot mode, then flash the recovery from there....using fastboot from your PC....

alrsar said:
Thanks for your reply, I have PVT 32B ENG S-OFF HBOOT -1.33.2005 drea21000
cpld-4
Radio 3.22.26.17
I can only go to the FASTBOOT mode (Camera and END) I dont have the recovery mode. So I think it rules out the first option. I can flash radio and done ut couple off time. No change to the situation. I dont know how to flash the SPL I should. Can you tell me what exactly the last option does?
thanks
Alireza
Click to expand...
Click to collapse
the last option is to downgrade your phone to its stock version which i think it would be RC29, so you can root. I think you done it once before rooting your device right ?

americanxo said:
the last option is to downgrade your phone to its stock version which i think it would be RC29, so you can root. I think you done it once before rooting your device right ?
Click to expand...
Click to collapse
Please please please do not flash rc29 on a rogers dream.. if the flash fails but installs the spl you can be in an annoying position, best unroot to the rogers firmware and root that again..
However op just needs to flash the -r version of the dream recovery.

This thread is a case of the blind leading the blind. Ignore ALL of the nonsense and read the following:
You have fastboot. That's good.
Start by installing a proper radio image. 2.22.23.02. You do this with FASTBOOT.
Go into fastboot mode, type (on your computer) "fastboot flash radio radio.img", ensuring that you have a radio.img with 2.22.23.02 in the current directory, and the fastboot executable somewhere in your path variable.
Next, flash a proper recovery image to it. Again with fastboot. "fastboot flash recovery recovery.img". Use ANY standard EBI0 recovery image that you like.
Now it'll work.
DO NOT INSTALL ANY NBH FILES!!!!!

lbcoder said:
This thread is a case of the blind leading the blind. Ignore ALL of the nonsense and read the following:
You have fastboot. That's good.
Start by installing a proper radio image. 2.22.23.02. You do this with FASTBOOT.
Go into fastboot mode, type (on your computer) "fastboot flash radio radio.img", ensuring that you have a radio.img with 2.22.23.02 in the current directory, and the fastboot executable somewhere in your path variable.
Next, flash a proper recovery image to it. Again with fastboot. "fastboot flash recovery recovery.img". Use ANY standard EBI0 recovery image that you like.
Now it'll work.
DO NOT INSTALL ANY NBH FILES!!!!!
Click to expand...
Click to collapse
Since he's on Rodgers, doesn't he need the 3.22 radio and a special recovery?

billquinn1 said:
Since he's on Rodgers, doesn't he need the 3.22 radio and a special recovery?
Click to expand...
Click to collapse
Shh people don't realize (ignoring carriers that may cause pain if they find a radio without an imei version of 3, only found on the latest 3.x radio) all dreams support 1.x, 2.x, and 3.x radios *if* installed properly.
The only thing to keep in mind is that like installing danger spl on a ebi0 stock dream, switching from ebi1 to ebi0 has a brick risk if done incorrectly.
To switch from 3.X->2.x or 2.X->3.x you need to flash the destination radio img file via fastboot (from hboot-1.33.2005) and *not* via recovery..
also after flashing you need to flash the recovery for the destination radio. (-r if 3.x otherwise the regular non -r)
As for if 2.x or 3.x is better.. they are nearly identical with some minor configuration changes that include some different memory offsets.. one or the other may or may not be better configured for any particular carrier.
Of corse there are many roms where we don't know what the kernel was pulled from for te ebi0 that since I don't know what kernel it has can't be used on ebi1.. I usually write these off however due to me not knowing where the source code is regardless of my target radio.
This only leaves the interesting aspect of lbcoder.. the amount he screams to ebi0 users not to use danger spl due to the dangers, but requests rogers/ebi1 users to switch to ebi0 radios despite the danger.. (note don't take this as you should or shouldn't do either recommendation, but that you need to understand what the approach means and what is your goal.. if you just want to access root to remove some bloat ware all you need is exploid or androot and you can keep the stock firmware.)
Ultimately however I expect people to take lbcoders advice with a grain of salt; and hopefully this will make the user actually read up on his suggestions, and what they where originally planning.. and figure out how to safely go from where they are to where they are going.

ezterry said:
Shh people don't realize (ignoring carriers that may cause pain if they find a radio without an imei version of 3, only found on the latest 3.x radio) all dreams support 1.x, 2.x, and 3.x radios *if* installed properly.
The only thing to keep in mind is that like installing danger spl on a ebi0 stock dream, switching from ebi1 to ebi0 has a brick risk if done incorrectly.
To switch from 3.X->2.x or 2.X->3.x you need to flash the destination radio img file via fastboot (from hboot-1.33.2005) and *not* via recovery..
also after flashing you need to flash the recovery for the destination radio. (-r if 3.x otherwise the regular non -r)
As for if 2.x or 3.x is better.. they are nearly identical with some minor configuration changes that include some different memory offsets.. one or the other may or may not be better configured for any particular carrier.
Of corse there are many roms where we don't know what the kernel was pulled from for te ebi0 that since I don't know what kernel it has can't be used on ebi1.. I usually write these off however due to me not knowing where the source code is regardless of my target radio.
This only leaves the interesting aspect of lbcoder.. the amount he screams to ebi0 users not to use danger spl due to the dangers, but requests rogers/ebi1 users to switch to ebi0 radios despite the danger.. (note don't take this as you should or shouldn't do either recommendation, but that you need to understand what the approach means and what is your goal.. if you just want to access root to remove some bloat ware all you need is exploid or androot and you can keep the stock firmware.)
Ultimately however I expect people to take lbcoders advice with a grain of salt; and hopefully this will make the user actually read up on his suggestions, and what they where originally planning.. and figure out how to safely go from where they are to where they are going.
Click to expand...
Click to collapse
Interesting stuff. I always thought there was a (carrier + hardware) reason for the different radio. Thanks for taking the time to explain.