Hello to all.... First and foremost, this will quite possibly be one of the "rookiest" questions EVER asked on all of xda in history and I apologize in advance!.. I've searched the countless new radio threads and can't quite find my answer so, i'm starting this thread knowing that you fine folks have all the answers I need!
First and foremost, is this radio in a good enough shape for a rookie like myself to switch to from Das BAMF 1.7? Assuming that it may be, can you give me any insight on what my procedure needs to be to get from my current Das BAMF 1.7 over to a gingerbread rom with the new radio??? Understand that I have NOT flashed any new radios/kernels etc.. on the my thunderbolt as of yet and need guidance. I finally gathered enough cohonies to root my bolt only yesterday and i'm a little more nervous, hesitant and unsure on this bolt than I was on my old Evo.. Especially since i'm brand spankin' new on ADB... Any insight from you geniuses would be GREATLY much appreciated!
Thanks in advance!
I understand why you may be apprehensive but I am also a fairly "rookie" ADB user and I did it and am now running GB. I flashed the GB rom I wanted first then booted the phone into HBoot and installed the radio using this guild xhttp://forum.xda-developers.com/showthread.php?t=1048128 it helped me a lot if you have any questions I would love to help more if I can.
flyodd said:
I understand why you may be apprehensive but I am also a fairly "rookie" ADB user and I did it and am now running GB. I flashed the GB rom I wanted first then booted the phone into HBoot and installed the radio using this guild xhttp://forum.xda-developers.com/showthread.php?t=1048128 it helped me a lot if you have any questions I would love to help more if I can.
Click to expand...
Click to collapse
Awesome, thanks my friend.... I'm gonna check it out right now
ouroborus2012 said:
Hello to all.... First and foremost, this will quite possibly be one of the "rookiest" questions EVER asked on all of xda in history and I apologize in advance!.. I've searched the countless new radio threads and can't quite find my answer so, i'm starting this thread knowing that you fine folks have all the answers I need!
First and foremost, is this radio in a good enough shape for a rookie like myself to switch to from Das BAMF 1.7? Assuming that it may be, can you give me any insight on what my procedure needs to be to get from my current Das BAMF 1.7 over to a gingerbread rom with the new radio??? Understand that I have NOT flashed any new radios/kernels etc.. on the my thunderbolt as of yet and need guidance. I finally gathered enough cohonies to root my bolt only yesterday and i'm a little more nervous, hesitant and unsure on this bolt than I was on my old Evo.. Especially since i'm brand spankin' new on ADB... Any insight from you geniuses would be GREATLY much appreciated!
Thanks in advance!
Click to expand...
Click to collapse
You can't run the new radio (MR2) on froyo based roms (das BAMF 1.7). You will need a gingerbread rom (das BAMF 2.0-5, gingeritis, etc) to be able to use the new radio.
So, once I download and flash the GB rom i want, do I allow the rom to boot up and then do all the new radio ADB stuff? Or, will allowing a GB rom to load up with my current radio jack it all up?
I'm tellin' ya dude, I'm very uninformed and suck at doing it this way... It was so much easier on the evo! hehe
thanks again
What I did to get to GB radio and rom:
Make sure usb debugging is on (checked in development)
1.Mount Phone into disk drive your phone will be connected to your computer for most of this.
2. Put the .zip of the rom and the radio onto my phones SD card
3. Rename the radio to PG05IMG.zip
4. Boot into recovery and flash the rom DO NOT REBOOT PHONE YET
5. Open ADB and put in
cd ..
cd ..
cd and*
cd tools
./adb devices
(each line is a new command press enter after each line and there are spaces between the cd and the dots)
Once done you should see this output or something like it:
List of devices attached
HT12R00422 device
if you do see that type this command into ADB
./adb reboot bootloader
this will bring you into Hboot
-Bootloader should be highlighted in blue -> Press the power button to execute.
The screen will change and Fastboot will be selected. Around 10 seconds later it will then proceed to the next step.
-You should see several files loaded and checked. Don't freak out at the warnings. The screen will eventually clear and you will see "checking pd05img.zip."
-Eventually, you will be asked: Do you want to start update? Press the volume up button to say yes.
Once you do, you will see a progress bar in the upper right corner and a bunch of stuff going on in the middle. Just be patient and let it do its thing.
Press power to reboot.
and bam you should be set!
I hope this was an okay guide I got most of it from here
http://forum.androidcentral.com/thunderbolt-rooting-roms-hacks/71919-mac-procedure-how-root-htc-thunderbolt.html
flyodd said:
What I did to get to GB radio and rom:
Make sure usb debugging is on (checked in development)
1.Mount Phone into disk drive your phone will be connected to your computer for most of this.
2. Put the .zip of the rom and the radio onto my phones SD card
3. Rename the radio to PG05IMG.zip
4. Boot into recovery and flash the rom DO NOT REBOOT PHONE YET
5. Open ADB and put in
cd ..
cd ..
cd and*
cd tools
./adb devices
(each line is a new command press enter after each line and there are spaces between the cd and the dots)
Once done you should see this output or something like it:
List of devices attached
HT12R00422 device
if you do see that type this command into ADB
./adb reboot bootloader
this will bring you into Hboot
-Bootloader should be highlighted in blue -> Press the power button to execute.
The screen will change and Fastboot will be selected. Around 10 seconds later it will then proceed to the next step.
-You should see several files loaded and checked. Don't freak out at the warnings. The screen will eventually clear and you will see "checking pd05img.zip."
-Eventually, you will be asked: Do you want to start update? Press the volume up button to say yes.
Once you do, you will see a progress bar in the upper right corner and a bunch of stuff going on in the middle. Just be patient and let it do its thing.
Press power to reboot.
and bam you should be set!
I hope this was an okay guide I got most of it from here
http://forum.androidcentral.com/thunderbolt-rooting-roms-hacks/71919-mac-procedure-how-root-htc-thunderbolt.html
Click to expand...
Click to collapse
WOW, so simple that even IIIIIIII should be able to do it! I can't thank you enough! I'll be working on it shortly!
good luck tell me how it goes!
flyodd said:
good luck tell me how it goes!
Click to expand...
Click to collapse
will do! Gettin' ready to do some work on it right now. Debating between DAS BAMF again or gingeritis.. Which did you chose? If either...
Is yours running farely smooth with the new radio?
I run BAMF 2.0 it works for me. I have never had issues with it minus the initial setup where the setup force closes 500 times but you get through that and it's great. 1.7 has better themeing options though there isnt much for GB BAMF yet.
Should I wipe battery stats or just do a normal wipe with dalvik and all that jazz??
yeah wipe whatever you can you can never be to sure. I always factory wipe everything whenever switching roms.
little help
Problem #1... I'm flashed and am at this part...
type ./adb devices
However, this is what it tells me.... '.' is not recognized as an internal or external command, operable program or batch file
What's that all about? I'm stuck
hmm try just the next command the one below in my post see if you can boot the phone into hboot still.
flyodd said:
hmm try just the next command the one below in my post see if you can boot the phone into hboot still.
Click to expand...
Click to collapse
aight.. now it says '.adb' is not recognized as blah blah blah.. same as the last one
am I doing the right thing by going in to "CMD" to do this?? I'm on windows 7
I am not quite sure with windows:S I am sorry I have a mac so I just use terminal:S
well, cmd is essentially "terminal"... wonder how the heck I can make this work
ok, i figured it out .. it was a different directory... So, I see my serial number but it says "recovery" instead of connected.... is that cool? Am i good to reboot
OP, u can flash the radio easily without using a computer. well make sure u have the right file on the root of your SD Card. turn off your phone. when its off, you hold power and the volume down button at the same time. it will go into HBoot by itself and flash the radio. just follow the instructions on the screen.
Related
Hi, I've had lot's of problems with my HTC recently, no adb access etc, device not being recognised and recovery playing up, ie not being able to wipe install roms etc... however I fixed the recovery issue and managed to do a nandroid backup, I put on I think it was 1.5 HTC sense hero rom... and recently realised that i can only flash 1.5 roms, not 2.1 anymore? would any developer know what would of caused this problem? Any 2.1 rom just locks on the Hero logo, and I've left it for over an hour in some cases and nothing happens. Again, I used to be able to put on any custom rom.... I'm all out of ideas.
wipe
did you wipe? what recovery image you using etc etc?
1. post in the correct section.
2. remove the ext4 partition from your sdcard, or change it to ext2 or ext3.
3. get adb logcat, otherwise this is like the question "my car won't run, can anybody tell me why?"
I have wiped numerous times... sorry for the "my car won't run type question etc...." just that I've done my research, gooogled, posted detailed info previously on here and another forum, I even fixed my own problem of the recovery image, without fixing that I would have nothing. But anyway the card is partitioned with swap, ext2, fat32 using the latest Amon_Ra image 1.6? something... i've spent weeks trying to resolve this and learnt a lot along the way.
Obviously not where to find the adb logcat... don't worry I'll google it.
Apologies for posting in the wrong forum, if it can be moved could a mod do so?
i had this problem with my magic,Using the goldcard method to downgrade and starting from scratch will fix this
bonesy said:
i had this problem with my magic,Using the goldcard method to downgrade and starting from scratch will fix this
Click to expand...
Click to collapse
Thanks for your reply, I will approach this method again at some point and give it a try, but I think I read somewhere that I couldn't do it for whatever reason, but I'll look into it again seeing as you've had the same issues. Thanks.
bonesy said:
i had this problem with my magic,Using the goldcard method to downgrade and starting from scratch will fix this
Click to expand...
Click to collapse
Actually I believe I didnt attempt this because I was no longer able to get my HTC hero working with ADB, as soon as I plug the device in, it comes up as device unrecognised, so I think goldcard method it out.. :-(
on the risk of offending you again (even though i am trying to help here...): you did not provide really much valid info. for most things you just said "doesn't work". what happens if you start by pushing home+power? saying the recovery doesn't boot up tells what does NOT happen, for a diagnosis we need the info what DOES happen.
anyway, if i get you right your recovery is now working. now repartition your sdcard (ext2 and fat, NO swap), do a full wipe, then install the rom you desire to use, then move the log to sdcard ("other" in recovery). reboot your phone and execute "adb logcat > c:\logcat.txt" on your pc. if it doesn't boot up after five minutes stop logcat with ctrl-c and post the two logfiles (recovery.log and logcat.txt). you need to set up adb, if you have problems with that sort them out, there is no way to get any information about your problem without the log.
oh, and about the goldcard: i don't know too much about goldcard'ing, but i can't see how this should help here. my strongest guess is that the swap partition interferes with the boot process...
No worries no offence taken. Pushing Home+Power works and takes me to recovery. Back+Power takes me to bootloader and USB Bootloader device is recognised, so I am able to get Fastboot.
Just recently installed stock rom, to see if that solved the USB and ROM issues but no such luck, re-rooted, put anom latest recovery back on, and went on to do what you have advised to help.. i've attached only the recovery.log in zip format only, as when doing adb logcat command use mentioned(after installing new rom), all I get is "waiting for devices" whilst the phone is stuck on the Hero logo, I waited about 10 minutes, exited from the adb, and the log file was empty as I guessed. I've tried every possible way that I found on the web to try and get the ADB function working again and I realise this is important to get some info.. but I've ran out of ideas for that.
Maybe the recovery(attached) may show something, all I noticed is that the cache and something else was not wiped for some reason? If you or someone has time, have a look through maybe someone knows what is going on.
Thanks for your help and patience
Ok, I've already searched the forums, both in the Evo3D section and outside, I've also have within the last week tried many different sense roms, all of which had the exact same problem: my camera does NOT work.
The closest thing to working was mike1986's Android Revolution HD (so far). The camera app boots into the window that ask to choose between Done or run the Demo Video. The Demo Video sends ye off to the internet browser. Hitting Done goes straight to my problem.
The application opens into a black screen. Sometimes the backlight is on (noticed this is a 'feature' of the newer roms that has came out/updated within the last month). That's it. After hitting home to exit the application, I have noticed I get either dimmer horizontal strips of the screen or the screen has a ghost of the lighter portions of the screen image that slowly moves to the left. After a few seconds of this strangeness, the screen reverts back to normal. A few times I got the impression that the screen's dual layers having synchronization problems.
I'm about ready to give up and go back to the stock rom, maybe I'll even try the 'cleaned' versions before trying the rooted shooter stockers. If all else fails, I'll even try to use the full OEM installer and return the phone back to stock, if this is the only option left to get a working camera. I'd prefer to use a custom rom that allows undervolting/overclocking and has the fat trimmed off, but if I have to, I'll go back to stock rooted. ...now that I think of it, I started to have problems with the camera right after I applied the HTCDev Root method. And, yes I DID follow the instructions to the letter.
This is quite frustrating as I've have as yet to find a rom that has a working camera! I've already tried the following roms:
Shooter-Rewind-3D-RLS2.1+RLS3
WTSB_Evo3d_1.91
CleanROM_2.7
CleanROM_DE_1.2
Chogardjr3D-2.3.4-Stock
Chogardjr3D-Blue-v1.3
STEAL25_inbREDedROM_2.1clock
viperROM_RC1.3
viperROM_RC2_Rebuild_Test28
Android_Revolution_HD-Evo3D_CDMA_1.1.1 (current)
I haven't tried but already downloaded:
Gerbil-6-shooter_v.2.2.4
freEVO+3D+2.1
WTSB Hydro e3d 2.3 (want to try this one, but keep having problems downloading, the server keeps on downloading a 35kb index.html instead of the rom itself)
If the above roms fails, then I going to try reloading the rooted stock rom
shooter_2.08.651.2_cleaned_v0.4.2
Else one of these two...
Shooter_2.08.651.2_deodexed_rooted
Shooter_2.08.651.2_odexed_rooted
If all these fails, sigh, I gonna start over again with the full oem install...
PG85IMG_2.08.651.2.zip
And see if the camera still broken. If so, then gonna apply all OTA updates FIRST before applying the HTCDev root method again. This is the only thing I did not do before. If this doesn't work, I dunno what else to do then.
Any suggestions, rom-wise or camera-wise? I've been reading around and found a thread in the Amaze section that suggested that the camera problem might be kernel-level. Think this may also apply to the e3d?
I've been doing sleepless nights for the past 5 days already trying roms after roms and apk after apks. I'm about reaching the end of my thread (and patience) and figured it's time to ask the pros here on xda.
Thanks in advance...
-Lance (Lanaka)
Reserved for Fixed Post.
I forgot to upload my hardware/software specs. I'm out of time as I have to go to work, so I'll edit it onto this post during a slow period at work.
K here's my hardware/software specs:
---Hardware:
------Hardware Version: .. 0002
------Processor: ............ 1.2 GHz Qualcomm MSM8660 Dual-Core
------Memory: ............... 1GB
------Display: ................ 4.3 inch QHD resolution
------Main Camera: ........ 5Mpx*2
------Front Camera: ....... 1.3Mpx
---Software:
------Android Version: ..... 2.3.4
------HTC Sense version: 3.0
------Software number: .. Android Revolution HD 1.1.1 by mike1986
------Kernel version: ...... 2.6.35.14RCMIX-ACS-EVO3D-CR-V9-g98e7362-dirty
------------------------- [email protected] #6
------------------------- SMP PREEMPT Mon Oct 24 13:13:49 CDT 2011
------Baseband version: . 0.97.10.0808
------Build number: ........ 2.08.651.2 CL130920 release-keys
------Browser version: .... WebKit/533.1
------PRI Version: .......... 1.24_003
------PRL Version: .......... 10602
Bootloader:
------SHOOTER XC SHIP S-0N RL
------HBOOT-1.50.0000
------eMMC-boot
------Aug 7 2011,10:21:40
---Recovery:
------Team Win Recovery Project (twrp) v1.0.3
------Based on Android System Recovery <2e>
Any other information you need, lemme know and where/how get it.
Mahalo Much
-Lan
Infected eternity ROM works...
Sent from my 3vo
http://infectedrom.com/showthread.php/561-ROM-Eternity-2.3.4?p=10369
Sent from my 3vo
nearly ALL the ROMs you posted, nay, all of them, work - if they didn't there would be a hellstorm in those threads. My guess is it has to do with how you're flashing the ROM. Since you have hboot 1.5, customized kernels (which contain camera stuffs) do not fully apply in a normal flash. You need to first fastboot usb INTO recovery and THEN flash the ROM. That should work. Also, update TWRP to 1.1.1. Of course you'll need to do a wipe as well. Hope this works for you.
You might also want to try one of the many superwipes.
User error. Camera works on roms. Maybe ur phone is broken
Sent from my PG86100 using XDA App
I'd go with what il Duce said. You have to flash the kernel seperately. If you do decide to go back to stock you can always add su and also remove what you don't want.
Sent from my PG86100 using XDA App
fsu311 said:
Infected eternity ROM works...
Click to expand...
Click to collapse
Ok, I'll give it a try next after the ones I've already downloaded. I'm a methodical type of guy (don't like leaving thing left undone).
il Duce said:
nearly ALL the ROMs you posted, nay, all of them, work - if they didn't there would be a hellstorm in those threads. My guess is it has to do with how you're flashing the ROM. Since you have hboot 1.5, customized kernels (which contain camera stuffs) do not fully apply in a normal flash. You need to first fastboot usb INTO recovery and THEN flash the ROM. That should work. Also, update TWRP to 1.1.1. Of course you'll need to do a wipe as well. Hope this works for you.
Click to expand...
Click to collapse
That's what I'm figuring. I start reading the original set of posts, then randomly check out a few posts in the middle, and then read the last 10%. The roms i've picked mostly had either minor issues caused by misflashing or other user errors. A few actually said had an issue or two but nothing that'd stop me from giving the rom a try.
Yup, that's the MO I've been using as instructed in the following thread:
http://forum.xda-developers.com/showthread.php?t=1239821
I'll go thru the step-by-step process I used and you can nitpick where I went wrong,
I've placed a copy of adb.exe, AdbWinApi.dll, fastboot.exe and TWRP's recovery.img into folder c:\adb\
A little tip here, as I play with windoze XP a lot, a trick I used to eliminate the need to cd so much with cmd.exe. I did this after the 3rd ROM!
I place a shortcut link to cmd.exe into this same folder with the above files and exes. Next I open the Properties window for this shortcut, I made the following changes:
Start In: c:\adb
Comment: Starts cmd.exe in adb folder.
What happen is that cmd will open its window with the c-prompt already IN the same directory as my android files. Also, when i mouse-over the shortcut icon, it will popup a message reminding me that this link starts cmd.exe in adb folder.
Then I do the following:
I connect the phone to the laptop using the usb cable, set the phone to disk drive mode. Once Windows recognizes the volume and mounts it, I type the following:
c:\adb>adb reboot bootloader
After the e3d reboots into hboot, I then type the following:
c:\adb>fastboot boot recovery.img
downloading 'boot.img'... OKAY [ 1.250s]
booting... OKAY [ 0.000s]
finished. total time: 1.250s
Once TWRP loads, I then switch to the phone (WITHOUT disconnecting the phone from the laptop). Here on, I use the keys on the phone to navigate to the necessary functions. The proceedure I used mirrors what Steel25 suggested in the following thread:
http://forum.xda-developers.com/showthread.php?t=1269610
I initially thought it was an overkill, but figured probably wouldnt hurt to be safe than sorry.
If the installed rom is something I liked, I nand it first...
I then enter the Wipe Menu proceed to hitting each of the following:
Wipe Cache
Wipe Dalvik Cache
Wipe Everything (Data Factory Reset)
Wipe Battery Stats
Then I go to Advanced/Format Menu and hit each of the following:
Format SYSTEM (/system)
Format DATA (/data)
Format CACHE (/cache)
Format SD-EXT (/sd-ext)
Then I go back to top menu and enter Install Zip Menu, and first I hit:
Wipe Cache and Dalvik Cache
Then I enable:
Reboot After Successful Flash
THEN I:
Choose Zip To Flash
(Navigate to where the rom or app zip is located and select it.) Here I take a break and let TWRP does it thingy and check back on the phone in 5 minutes or so.
After recovery reboots the phone back into system, I let the phone sit on the lockscreen for 10 minutes to let the rom complete it's init process. Then I skip thru the entire initial setup prompts (altho I enter NO for Tell HTC). I reboot phone back into system, let it sit for another 5 minutes on the lockscreen before I hit the Android Market app to trigger the process of linking the phone to my google account. I then let my account sync. Once my new email icon pops up on the notification bar, I check out the camera. By the time I've hit the 3rd rom, I've had read about the camera problem possibly being a kernel level issue, I've since then added this step....
Menu/Settings/About Phone/Software information/More
Here I took note on whether the Kernel version info has changed as well. (And for the most part, yes, the kernel information DOES change with each rom).
K, now ye can start thrashing me...
-Lan
Drewmungus said:
You might also want to try one of the many superwipes.
Click to expand...
Click to collapse
I'll try that, altho I've never used it before. Even when I had my e4g, I never heard of this one until I started my current research on the e3d. Any particular one you'd (or anyone else'd) recommend?
Sigh, lotta work rooting and flashing the 1.50 e3d, compared to the good ol' e4g! >8p HTC!
Mahalo Much!
-Lan
cajones42 said:
Maybe ur phone is broken
Click to expand...
Click to collapse
Gods! I certainly HOPE NOT! It'd be a real b!atch if this proves to be the case.
Seriously, tho. I'm thinking it'd probably not be the case as I had the phone and was playing with it stock and unrooted for nearly a week and during the whole time, the phone's camera worked with nary a problem. That's why as a check value, I'm going to restore the phone back to stock unrooted state AFTER I try the last 4 roms I still have en-queued. This doesn't include the cleaned/rooted stocker, the full/rooted stocker nor the full OEM stocker.
-Lan
unCoRrUpTeD said:
I'd go with what il Duce said. You have to flash the kernel seperately. If you do decide to go back to stock you can always add su and also remove what you don't want.
Click to expand...
Click to collapse
Ok, I'll try that next. Altho, I gonna have to read up on how to prepare the kernel for flashing separately. Am I correct in guessing that I probably could get away with making a copy of the zip file and deleting everything in it except for boot.img, then adb boot into recovery and set the flag for check sign off before flashing the custom zip I just made? If that's not correct, mind pointing me to the apropos thread? (...or tell me what I need to do for separate flashing?)
If all else doesn't work, that's what I intend with the stocker roms. SU, TI, RE. Then time for me to research on where what and how to root out all the bloat meself. I'll worry about that later cuz I no need do that IF i can get a pre-made rom and kernel to take root in me e3d!
Mahalo Much!
-Lan
You DON'T have to flash the kernel seperatly using the boot.img method with HBoot 1.50. As long as you access recovery from fastboot you can flash everything normally & the kernel will stick. Just sayin'
SketchyStunts said:
You DON'T have to flash the kernel seperatly using the boot.img method with HBoot 1.50. As long as you access recovery from fastboot you can flash everything normally & the kernel will stick. Just sayin'
Click to expand...
Click to collapse
except he's already doing that and running into problems...
@OP - man you are wordy lol. Just a simple FYI, when you're phone is running and you hook up to usb with the intention of running adb, DO NOT turn on disk drive, leave it as charge only. Also, the way to flash the kernel as a stand alone is pull the "boot.img" from the ROM zip, put in your path, and then "fastboot flash boot boot.img". Also, there's an app made by dev "joeykrim" called "flash image gui" that allows you to flash kernels (boot.img) from your OS and is known to work with hboot 1.5.
il Duce said:
except he's already doing that and running into problems...
@OP - man you are wordy lol. Just a simple FYI, when you're phone is running and you hook up to usb with the intention of running adb, DO NOT turn on disk drive, leave it as charge only. Also, the way to flash the kernel as a stand alone is pull the "boot.img" from the ROM zip, put in your path, and then "fastboot flash boot boot.img". Also, there's an app made by dev "joeykrim" called "flash image gui" that allows you to flash kernels (boot.img) from your OS and is known to work with hboot 1.5.
Click to expand...
Click to collapse
Ah, didn't know that, mebbe that's why I'm having problems. I'll try reinstall one of the earlier ROM and see if there's any difference. If that doesn't fly, I'll try the kernel separately. I went with hard drive mode cuz I got actual confirmation the device was loaded. Charge only, didn't get any indication that the pc seen the e3d, sigh, noticed the sense and adb interface is rather ...crude.
Heh, wordy, that's what you get when you have an English major for a mother and an English/Japanese Translation Specialist (aka Cultural Attache in the US Army) for a grandfather...
I'll give joeykrim's flash_gui a try too. Just downloaded it. Cross fingers for luck. (roll eyes at 1.50)
Thanks dude, if I could, I'd hit yer thanks button again for good measure.
EDIT: clicked the button again...
Update: Back to work on problem...
Been a while guys. Unfortunately, work becons (or more accurately, intruded). Had to deal with a bunch of sht from my job. Things gone to the dumps there. Well, enuff of that.
In meantime, with my phone being activated and in use, I tried to tether (teeether, hehe) my e4g to my e3d and noticed I'm also having wifi issues. What rang a bell is when I noticed my wifi tether issues disappeared after I turned off 3G. It's like, heeeeey, didn't I read something like this in xda??? After doing some researching (on xda, of course ) I've learned that this is also a kernel issue, most often because the new kernel was not properly flashed in conjunction to having the correct matched kernel modules (wifi, CAMERA, 3g/4g, etc.) installed as well. On reading these, I went 'hmmm...' Looks like all of these issues others and I that have been experiencing are all kernel/module misflashes (no thanks to hboot 1.50). Where I think I hit pay dirt is when I found a xda thread that actually explains in depth Flash Image GUI, which was also mentioned earlier in THIS thread (thanks, il Duce).
So, I have downloaded the apk, installed it. Downloaded a new ROM (Olympus Trinity XE Version IV) STRAIGHT to phone...
Oh, just remembered. I've noticed another possible cause of problems. I've originally downloaded the various files from xda and then either push it to phone or more often just enable hardrive mode and drag/dropped it into the phones sdcard directly. Normally, I check the md5 hash on download, but yesterday, I ALSO checked the md5 hash again after moving it to the phone. Meaning, I downloaded ROM to pc, then checked md5 hash, all good. Copied ROM to phone and then checked md5 hash again. NOT good. Somehow, it changed during the copy process. What prompted me to check was I also downloaded Flash Image GUI to pc and copied it to phone and then had phone try install it. It failed to "parse" file correctly, which tells me that the file may have been corrupted. I downloaded Flash Image directly to phone and tried again, and success! Suspicious now, I checked the md5 hash of all three copies of the apk. The laptop downloaded and the phone downloaded copies matched the source's md5, while the COPIED version did NOT match! Whaaa Daaaa FFF(bleep!)!!! I then checked the two copies of the ROM (pc downloaded and phone copied) and they DON'T match!
Sigh. I'm in a area that has poor 3G connection, while ironically, my laptop's 4G was good.
So, I bit the bullet and endured the nearly hour long download of the ROM directly to phone and double checked the hash (which matched the pc downloaded copy, the source didn't provide a hash). THEN I used the Flash Image GUI app to pull the kernel and modules and pop it into phone. Immediately rebooted phone into recovery. Well, tried. Wished Flash Image GUI gave the option to reboot directly into recovery or bootloader, like those 4-/5-/6-1 Reboot options offered in the various ROMs. Because it just simple did a reboot back into System.
I didn't want to take chance with problems with mismatched ROM/kernels (I was on Android Revolution 1.1.1 at the time), so I quickly turned to adb on my laptop and had it reboot phone into recovery.
Once in recovery, I immediately started doing my usual ROM change process. Wiped using every wipe option (except for sdcard) in TWRP (oh btw, I also updated it to 1.1.1 earlier) in both the standard wipe and advanced wipe menus. Once I did so, I then thought, hey where did Flash Image GUI dump the kernels into? Couldn't remember whether it was DATA or SYSTEM. But decided that with Flash Image GUI it's ain't no hassle to reflash the kernel again after the ROM is installed. Besides, read somewhere that some issues was resolved after reflashing the kernel again after the ROM, so wouldn't hurt to try anyway.
Will let ye know how it goes, TWRP is installing Trinity XE as I type this. Gonna continue the SOP by letting it sit for 7-10 minutes. Skip thru init setup. Reboot. Let sit for another 7-10 minutes. Relink my google account. Let first Sync finish. (Basically let it sit again for another 7 minutes). Reboot. Hit Market and download Flash Image GUI, and pay for it, it's well worth IT!!! Flash the ROM's kernel/modules again. Reboot. And hopefully it should be a-ok!
(cross fingers ...on both hands)!
-Lance
PS: Assuming it's fixed, I'm gonna edit the second post and reflag this thread as resolved. Will put what I did to get it fixed, including all necessary links and credits as expected. I know it's premature, but THANKS, I wouldn't have gotten even this far without you guys (and gals) on XDA!
PPS: Also chris.goodman's AnthraX Kernel thread was also quite informative. Mebbe I'll try a ROM that features AnthraX. Somehow, the thought of being over-clocked to ~1.52G sounds appealing!
Which is the best rom to go with?
I've downloaded _n0p_'s DSC v0.7 and Tenorntex's Longhorn 2.1 v2, seeing as these 2 were the newest and latest and had Android 2.3.3
Are there any other better rom's or has anyone tried the 2 I listed, if so whats the difference?
Thanks
Better is very vague when it comes to ROM's it all depends on what you want in a Rom. I have old Simple Streak 1.2. Yes there is newer ROM's out but this one works perfect for what I need. In my Case Stability.
DSC is the most actively developed/supported. Plenty stable for me. I don't think any of the earlier Froyo based ROMs are being developed further.
I meant as far as Stability, Performance and up to date, I don't care about the Stage UI and was gunna theme it myself or use SPB Shell 3D.
Could someone point me in the direction to an easy install rom?
I don't wanna install "these update pkg's" after renaming and then plug my phone into the pc and open cmd and then type this in on the pc. et cetera et cetera
I just wanna download a zip drag it to the card, bootup in safemode and install from sd card.
I'd consider doing all that work if I weren't testing out the device.
I won it off ebay, the guy replaced the screen and said it's been randomly rebooting ever since. But he never did a factory reset or new rom install ever since fixing the screen, so I just wanna simply install a rom and see if it works then go on from there.
Any help would be greatly appreciated.
n1nj4Lo said:
Could someone point me in the direction to an easy install rom?
I don't wanna install "these update pkg's" after renaming and then plug my phone into the pc and open cmd and then type this in on the pc. et cetera et cetera
I just wanna download a zip drag it to the card, bootup in safemode and install from sd card.
I'd consider doing all that work if I weren't testing out the device.
I won it off ebay, the guy replaced the screen and said it's been randomly rebooting ever since. But he never did a factory reset or new rom install ever since fixing the screen, so I just wanna simply install a rom and see if it works then go on from there.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Unfortunately I do not believe that anyone can change the way that the Streak works just so it is more convenient for you or so that you don't have to learn anything.
In the time you took to navigate to XDA and make your post you could have flashed a ROM onto your Streak - plugging it in and everything.
The only ROM you can install by just putting it on the SD Card is the same one that is currently on the Streak, if you don't mind holding down a couple of buttons and using recovery mode.
n1nj4Lo said:
Could someone point me in the direction to an easy install rom?
I don't wanna install "these update pkg's" after renaming and then plug my phone into the pc and open cmd and then type this in on the pc. et cetera et cetera
I just wanna download a zip drag it to the card, bootup in safemode and install from sd card.
I'd consider doing all that work if I weren't testing out the device.
I won it off ebay, the guy replaced the screen and said it's been randomly rebooting ever since. But he never did a factory reset or new rom install ever since fixing the screen, so I just wanna simply install a rom and see if it works then go on from there.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
If anyone is wondering why developers leave and give the site a bad reputation look no further. Someone with over 600 posts under his username should not be making noob posts like this one. With so many posts he knows how to use the search engine and the wiki, but I guess when it comes to our device using the search engine and the wiki is an inconvenience, along with renaming a file "update.pkg".
marvin02 said:
Unfortunately I do not believe that anyone can change the way that the Streak works just so it is more convenient for you or so that you don't have to learn anything.
In the time you took to navigate to XDA and make your post you could have flashed a ROM onto your Streak - plugging it in and everything.
The only ROM you can install by just putting it on the SD Card is the same one that is currently on the Streak, if you don't mind holding down a couple of buttons and using recovery mode.
Click to expand...
Click to collapse
So would that be this: Streak_407_20707_14.pkg ? According to the first post above me do I rename it?
Strephon Alkhalikoi said:
If anyone is wondering why developers leave and give the site a bad reputation look no further. Someone with over 600 posts under his username should not be making noob posts like this one. With so many posts he knows how to use the search engine and the wiki, but I guess when it comes to our device using the search engine and the wiki is an inconvenience, along with renaming a file "update.pkg".
Click to expand...
Click to collapse
Some people learn better through interaction where they can actually ask questions... I don't have over 600 posts so who are you talking about? Furthermore if you are talking about first thing I'd do is learn how to read mr wise guy, secondly!! You tell me how one is supposed to learn which rom is the best based on user reviews and opinions, where do I go to find that out and wheres the wiki on that, unless you expect people to read 200 and 300 page threads also? I have barely 150 posts and rarely post at all unless it is to ask questions or make requests. It's not like I have 600 posts and every single one of them are questions.
This is only my second time dealing with android and second time flashing android first time it was simply moving a zip to the sdcard and booting up into safe mode and selecting update through sdcard, so certainly I'd be baffled and have questions when one time it was so easy and the second time I've gotta jump through hoops and everything.
Lastly since WHEN Is asking a Question SOOOO wrong in the Dell Streak 5 Q&A Category???? It's not like I posted it in the wrong area or something, but ohhh no'es how dare n00b be confused and need a lil help/guidance of some experienced users, ohh mercy me the drama in that!!
Last time I checked that is what XDA is here for, for people to learn, not to be attacked by asshat trolls like you.
If anyone is wondering why XDA has a multitude more lurkers than posters look no further than to the hardass that is Strephon Alkhalikoi View Postwho can't stand to see a n00b in need of help!
Like this
Flashing/Updating
Installing a recovery
Download appropriate recovery to flash from Stock Recoveries or Custom recoveries
Enter fastboot mode on your phone
Flash recovery with fastboot: fastboot flash recovery <path to recovery.img>
After flashing is complete: fastboot reboot to reboot
Finished
If you are using a custom recovery see Disabling recovery overwrite in stock roms and follow the steps there to prevent the Streak from over writing the recovery. Re-install your custom recovery after following those steps.
Click to expand...
Click to collapse
BUT THE VERY FIRST THING THE WIKI SAYS IS To Stay AWAY From Fastboot, but this tells you to use Fastboot... So what gives and which is it? LoL
n1nj4Lo said:
. . . .
Like thisBUT THE VERY FIRST THING THE WIKI SAYS IS To Stay AWAY From Fastboot, but this tells you to use Fastboot... So what gives and which is it? LoL
Click to expand...
Click to collapse
I hope that you can actually read better than that. The wiki does not say to stay away from fastboot. It clearly states two commands that should not be used on the Streak. It goes onto give a number of examples of using fastboot.
I hope that you other 157 posts (as I wtite this) on XDA were not as tiresome or ill-informed as the ones you have posted here.
The information you need is here in the forums, available at the links in my signature, and on other forums. Please exercise some patience and read the info.
marvin02 said:
I hope that you can actually read better than that. The wiki does not say to stay away from fastboot. It clearly states two commands that should not be used on the Streak. It goes onto give a number of examples of using fastboot.
I hope that you other 157 posts (as I wtite this) on XDA were not as tiresome or ill-informed as the ones you have posted here.
The information you need is here in the forums, available at the links in my signature, and on other forums. Please exercise some patience and read the info.
Click to expand...
Click to collapse
Uhh yea sory... I forgot about the 2 options to stay away from, just the dangerous part stayed with me. LoL
Do I need to be at a certain android version or can I make a semi-major update leap?
Also it says
Installing a stock rom
Reinstalling a stock rom will wipe all data!
1. Download stock rom pkg and recovery to install
2. Copy pkg to sdcard and rename to update.pkg
3. Install matching stock recovery
4. Enter recovery mode
5. After recovery loads press Camera to begin process
6. Finished
Click to expand...
Click to collapse
Do I need the recovery.img as well? It said nothing about a img file or anything just said "matching stock recovery" so yea, is that the right thing?
_
First I'm gunna try factory reset and see if that fixes the random reboot problem, hopefully it does the seller said he just installed the new screen and never did anything except for just trying to powering it up, use normally and it would reboot suddenly.
WELL NO DUH, you need to restore everything back to default settings with a factory/hard reset. Thats like trying to install a video card or webcam and expecting it to work right away without installing the dirvers. - Hopefully!
Well it's only getting as far as the dell logo screen/splash screen. I've tried the entering safe mode but nothing yet, once it's powered on it just sits at that screen.
dsc is great and very stable if you dont mind the few following quirks.
1. google maps will always run in the background unless you freeze it. This will drain your battery quite quickly
2. Wifi might or might not be broken, if it is broken use wifi analyzer if not profit
the benefits of dsc?
fast
running GB instead of froyo
dpi change is awesome.
screen default orientation is awesome
stable other than those few bugs
Battery life was decent.
-------------
Im however just running 2.2 froyo on a stock rogers. The battery life is amazing on stock 2.2 (a whole day, and still have about 30% with heavy usage and constant 3g) and the wifi works fine. For me this is the most stable rom however it is a bit slow compared to DSC. This phone is used for work so it has to just.. work.
---------------
Havent really tried the other roms yet, but depending on what you want out of the phone you can try the DSC and see if you can live with these little quirks.
Yea I was leaning more towards DSC than Longhorn, it looks like it's updated more frequently too.
Bad & Good News
Turns out when the guy replaced the screen he fried the mobo... Me and a friend at a small local pc store tried everything from rooting with new rom to factory resets. Always had the same problem.
But the guy at the pc store sells phones also and said he'd give me $100.00 credit to a new factory refirbed, rooted and unlocked dell streak mini if I gave him the one we tried to repair.
Ok, so here's the thing, I have a phone that's stuck with HBOOT 1.5. I used the HTC unlock and got my phone on MIUI awhile back, but the thing is, now it's gotten a bit aged and I'm kind of tired of the ROM. It's been about 4 months since then and I don't remember how to switch back to sense (I was hoping to get onto 3.5 so that I can get HTC's free dropbox space lol). I'd like to try another AOSP ROM, but I know they're all pretty unstable at this point (someone correct me if I'm wrong).
Here's the real problem though, at this point, not really remembering how I even got this thing unlocked and running, I've been reading through the forums again trying to figure out how to switch back to sense, and I've just gotten entirely confused. I'm not new to rooting/ROMing, I'm just confused by all the loops you have to jump through with HBOOT 1.5. Could anyone provide a slightly simplified, possibly even unified, set of instructions or at least point me at the right how-tos in order?
Please? I love you guys
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
Sorry about that. I thought I had clicked Q&A when I came in, my bad xD
greatwithtoast said:
Ok, so here's the thing, I have a phone that's stuck with HBOOT 1.5. I used the HTC unlock and got my phone on MIUI awhile back, but the thing is, now it's gotten a bit aged and I'm kind of tired of the ROM. It's been about 4 months since then and I don't remember how to switch back to sense (I was hoping to get onto 3.5 so that I can get HTC's free dropbox space lol). I'd like to try another AOSP ROM, but I know they're all pretty unstable at this point (someone correct me if I'm wrong).
Here's the real problem though, at this point, not really remembering how I even got this thing unlocked and running, I've been reading through the forums again trying to figure out how to switch back to sense, and I've just gotten entirely confused. I'm not new to rooting/ROMing, I'm just confused by all the loops you have to jump through with HBOOT 1.5. Could anyone provide a slightly simplified, possibly even unified, set of instructions or at least point me at the right how-tos in order?
Please? I love you guys
Click to expand...
Click to collapse
there's 3 ways to flash ROMs correctly with 1.5:
1- use joekrims "flash image gui" app
2- use fastboot usb to boot recovery, then flash
3- use teamwin's new "htc dumlock" recovery tool
Thank you, but I actually was wondering if anyone could give me a bit more information than that. Let's go ahead and go back to assuming that I'm a complete noob who knows nothing other than what he just found from the first page of the forum search.
greatwithtoast said:
Thank you, but I actually was wondering if anyone could give me a bit more information than that. Let's go ahead and go back to assuming that I'm a complete noob who knows nothing other than what he just found from the first page of the forum search.
Click to expand...
Click to collapse
Fastboot method:
boot to bootloader > Select Fastboot (with your phone plugged into pc) > run cmd on computer > Change directory to where ever you tools for adb and recovery.img are (Im assuming you remember how to change directories through cmd if not goes like cd c:/(enter the folder here)) > Run fastboot command >>> Fastboot boot recovery.img > Wipe properly > Flash rom
Flash gui method:
run flash gui > select boot.img > run the program > reboot into recovery > flash rom > reboot and enjoy
Dont know the htc dumlock method yet but should be fairly simple also.
Well, a few things went wrong when I tried to install CM10 today. First, I rooted using Debugfs simple root. I then unlocked using the file on the Asus site. I then installed CWM through Rom Manager, and then wiped and installed CM10. I thought I had done a recovery, but it is no where to be found. So, now I'm stuck and can either go into CWM or I will get a black screen and it will sit there. I tried wiping and reinstalling same rom, but that is about all I can do. I haven't used ADB before so I just installed it and checked if it would see my device. It appears to see it when it gets to the black screen, but not when I'm in CWM. I'm a newb when it comes to this stuff, but never had problems getting CM10 on my atrix so i thought I would give it a shot. Anyone got any suggestions? I searched for about an hour for a solution and tried the IRC chat, but no luck. Do I have an expensive paper weight now?
larzred said:
Well, a few things went wrong when I tried to install CM10 today. First, I rooted using Debugfs simple root. I then unlocked using the file on the Asus site. I then installed CWM through Rom Manager, and then wiped and installed CM10. I thought I had done a recovery, but it is no where to be found. So, now I'm stuck and can either go into CWM or I will get a black screen and it will sit there. I tried wiping and reinstalling same rom, but that is about all I can do. I haven't used ADB before so I just installed it and checked if it would see my device. It appears to see it when it gets to the black screen, but not when I'm in CWM. I'm a newb when it comes to this stuff, but never had problems getting CM10 on my atrix so i thought I would give it a shot. Anyone got any suggestions? I searched for about an hour for a solution and tried the IRC chat, but no luck. Do I have an expensive paper weight now?
Click to expand...
Click to collapse
Yes you have a paper weight I'll give you $10 for it..... just kidding.... btw it aint bricked if you can get to cwm but thats another story..I will assume you have a windows 7 pc, for now at least.
First go here..http://forum.xda-developers.com/showthread.php?t=1426502 follow the instructions.... install universal naked drivers....
next go here.....http://forum.xda-developers.com/showthread.php?t=1774352 download and extract the file... you won't do the nvflash yet but it has a known good copy of adb in it....
next go here....http://forum.xda-developers.com/showthread.php?t=1615990 download twrp and follow the instructions to do a fastboot install..
At this point you should have a working twrp recovery, this is the one you should have had in the first place....
Now download a rom.... EOS JB or androwook will do.
Next now this is important....
Open the nvflash directory so you can see adb.exe, put the rom you downloaded into the folder at the same level (directory) as adb.exe now press and hold the shift button, right click (in the window where adb.exe is) and select open command prompt here.
Now type in the command prompt abd devices, you should see your transformer... if you do then type adb push /name of the rom/sdcard/ this will take about 5 minutes... for the name of the rom I usually right click and go to properties and copy the name.. in the command window you need to right click and paste (control v doesn't work) make sure you end the name of the rom with .zip.
Once that is done you should be able to go to install in twrp and your rom should install....
IF you have an external sd card, you can put the rom on it and insert it because twrp will read external cards and you don't need to do the adb thing.... let me know how it turns out.. even if you want to pm me..... good luck
Hey there,
I had the exact same issue. I too can fastboot to CWM but if I attempt to coldboot the OS I get the black screen of death. I managed to use the fastboot command to install the twrp to my prime. However, the Prime is not being recognized when I use "adb devices" in the commands, even though it successfully took the fastboot command that installed the twrp file. So I am stuck on the stage of trying to push the rom to my device. I know I am inputting the command successfully since I am getting an error: device not found on the return.
Any input would be greatly appreciated Gage. Thank you!
Update: I already had the CM10 nightly present on the device. So I selected to flash that, and it went through the normal processes. Wiped cache/dalvik at the end and rebooted device... am now again staring at black screen of death. It booted into the new TeamWin twrp recovery, which gave me a slight glimpse of hope...
I wish I could push the thanks button a thousand times! A few hours of working on these instructions (thanks to newbness and Windows 8), I finally have a working tablet again! You're the best Gage. Hunter, sorry I can't help, I used a Micro Sd instead of ADB.
Lazred if you would be willing to share your wisdom with me I would be most thankful, I would willingly run out and purchase a microsd card if it would mean the return of my beloved Prime =(
Funny that we had an issue with the same ROM (CM10 Nightlies). I tried reinstalling that several times with no avail. Since you can get into twrp, you should just be able to put that sd card into your computer (assuming you have an sd card reader) and load on another ROM (I used EOS 3 JB). Now, after you put that loaded micro sd into your tablet, you should be able to load up twrp, choose install, choose use external sd card, then pick the new rom to install and if you're lucky like me all your problems will be solved! Good luck!
Yea, ADB isn't working I had the same problem. Had to go get a micro sd card and use the latest TWRP. Thanks CM for the bum rom....
HunterofNittis said:
Hey there,
I had the exact same issue. I too can fastboot to CWM but if I attempt to coldboot the OS I get the black screen of death. I managed to use the fastboot command to install the twrp to my prime. However, the Prime is not being recognized when I use "adb devices" in the commands, even though it successfully took the fastboot command that installed the twrp file. So I am stuck on the stage of trying to push the rom to my device. I know I am inputting the command successfully since I am getting an error: device not found on the return.
Any input would be greatly appreciated Gage. Thank you!
Update: I already had the CM10 nightly present on the device. So I selected to flash that, and it went through the normal processes. Wiped cache/dalvik at the end and rebooted device... am now again staring at black screen of death. It booted into the new TeamWin twrp recovery, which gave me a slight glimpse of hope...
Click to expand...
Click to collapse
You do know that adb commands don't work from fastboot? So if you are trying them from the same place as where you installed twrp it is not going to work.
adb should work when you are inside twrp tho.
Have you tried installing the naked drivers and then going into twrp and trying adb devices?
flumpster said:
You do know that adb commands don't work from fastboot? So if you are trying them from the same place as where you installed twrp it is not going to work.
adb should work when you are inside twrp tho.
Have you tried installing the naked drivers and then going into twrp and trying adb devices?
Click to expand...
Click to collapse
Hi everyone I just wanted to provide an update. I can confirm that the CM nightly must have been bugged since it remains the only rom that continued to give me BlackSOD regardless of md5 checks, etc. I successfully flashed EOS from twrp. Booted fine, smooth as silk, all sorts of victory dances going on over here. In case anybody else stumbles upon this thread, I wanted to throw out a few more things elaborating upon the instructions of Gage, since for me at least the whole driver and push command thing was far more complicated than I would have wanted for anyone else.
When Gage says install the drivers, this proved very problematic for me. Thankfully there is a bundle out there, search the XDA forums for a file called adb-fastboot-win. This has your fastboot.exe in it. You are going to need this for step three. When you go to open the command window, shift clicking in the window in the directory file (folder) didn't work for me (win 7 ulti 64 bit). Instead, shift right click on the folder itself where your fastboot.exe and adb files are. That will yield your command window. Then follow the instructions as listed in the third thread provided by Gage. The fastboot command is quite simple.
Make sure you place your new twrp (Team Win Recovery Program) file in the same folder as your fastboot.exe, it does not actually have to be in the same folder as adb from what I have read and spoken with devs about, but fastboot.exe and adb should be in the same folder anyways. Make sure its in there, and use the command function to send it to the prime while its in usb fastboot.
I can confirm at this time that nobody seems to have an adb solution to this. Adb doesn't work in fastboot as flump pointed out, and adb wasnt functioning in twrp for me. Drivers were correctly installed, it could push to phone fine, issue was definitely with the Prime since it wouldn't show up under listed devices.
THE SOLUTION: As others have said, call a friend or go down to best buy (ugh overpriced) and get a measly 2gb micro sd card if you want the bare minimum and get the reader. Mount SD card in computer. Stick ZIPPED NEW ROM on sd card. Plug sd card into Prime. Boot into TWRP (just a reminder its power button and volume down, then press vol up when prompted) and select install, select button that says external sd, select zip, then select your GApps file, swipe to confirm flash, and pray to whatever higher power you believe in.
Hope this helps anyone else out there, and thanks so much to Gage and everyone else I consulted on the matter. I learned a lot during the process.