So I tried rooting my girlfriend's G1 and it didn't workout so well, so now I'm trying to fix it for her (I feel terrible, my poor android friend.. I mean my poor girlfriend!) . I rooted it and it was working find, but I wanted to flash a ROM on there. I tried flashing CM5 following the directions on the wiki. I made sure I installed Amon_Ra's recovery and did a nandroid backup. Then I flashed the DangerSPL. 2 things then happened, when I tried starting up the phone it would just hang on the "G1" startup screen until I pulled the battery, and when I went back into recover it switched back to the old recovery I had after root (JFv1.42). So I can't go back. But when I go into Fastboot, the HBOOT is at 1.33-2005, which indicated the DangerSPL was flashed correctly. So should I flash CM5( or 6 or 7) now? I just don't wanna get the phone to a point where it's unusable (unless it is already) =/ Can you guys help me out?
If you can go to hboot, everything should be fine. Check again, that you have a 2.x or 3.x radio installed (should be the case, because otherwise I doubt you would be able to go to hboot).
If this is the case, you can flash what you want. Probably I would flash Amon-RA recovery first
Code:
fastboot flash recovery <amon-ra.img>
To be sure, that you have a clean phone, I would do an
Code:
fastboot erase system -w
Then you can boot into recovery and flash the ROM you like.
Your girlfriend G1 still fine.
The CM5 that you have flashed is not compatible with the SPL(HBOOT)/radio combination. (to my understanding) That is why it gets stuck at G1 screen (that had happens to me).
For G1, you can only flash up to CM 6.1 (to my knowledge), Cyanogenmod 7 will not (according to the DEV) works on G1.
You can try other ROM, recommending ezGengerbread, or Gingerbread Yoshi, and also my favorite (I am currently using it.) SuperAosp DM 2.8.2.
You will need to use 2708 SP and 13d radio for the newer ROM.
First load the radio, then the SPL. After both have been flashed (you can check it in the fastboot mode) then flash the ROM that you want.
AndDiSa said:
If you can go to hboot, everything should be fine. Check again, that you have a 2.x or 3.x radio installed (should be the case, because otherwise I doubt you would be able to go to hboot).
If this is the case, you can flash what you want. Probably I would flash Amon-RA recovery first
Code:
fastboot flash recovery <amon-ra.img>
To be sure, that you have a clean phone, I would do an
Code:
fastboot erase system -w
Then you can boot into recovery and flash the ROM you like.
Click to expand...
Click to collapse
Where do I put in these commands?
Vulf said:
Where do I put in these commands?
Click to expand...
Click to collapse
You have to connect the G1 to the PC and run ADB. Then flash it using the command line indicated.
BeenAndroidized said:
You have to connect the G1 to the PC and run ADB. Then flash it using the command line indicated.
Click to expand...
Click to collapse
No, it's not adb, it's fastboot, a different program, but you are right, it's a program that runs on your PC. You have to make sure to have fastboot installed. Then open a command window and enter the commands above having your G1 connected to your PC and beeing in fastboot mode (boot with back + power).
@ AndDiSa - Sorry for the short explaination, I should have explain in more detail.
Alright. I'm on Ubuntu so I'll let you know how it goes. I'm gonna install SDK/ADB/Fastboot now
Vulf said:
Alright. I'm on Ubuntu so I'll let you know how it goes. I'm gonna install SDK/ADB/Fastboot now
Click to expand...
Click to collapse
Have fun.
So a problem with flashing amon ra's recovery. My fastboot (or adb) aren't recognizing my G1, but they recognize my EVO, which is strange since they're both HTC..
Vulf said:
So a problem with flashing amon ra's recovery. My fastboot (or adb) aren't recognizing my G1, but they recognize my EVO, which is strange since they're both HTC..
Click to expand...
Click to collapse
Hmm, someone post an instruction in one of the forum that I saw yesterday. Not sure which one. It would fix the problem you are having with not see your G1 on ubuntu..
You can solved your problem with unroot like me.even my g1 lost function home & call button.
Sent from my T-Mobile G1 using XDA App
Related
Hello all.... I am working on a group project where we will be using a dev G1. The phone was shipped to a another group member and before I can get my hands on it, he decided to upgrade the firmware from 1.0 to 1.6, having very little knowledge of android beforehand and therefore he cant really tell me what exactly he did either. He followed the directions on the HTC website. As far as i can tell, I do have the 26I radio, engineering SPL and 1.6 installed currently, not sure about the recovery though (i.e. stock 1.0 or 1.6). When I got the phone, root access was gone but followed some simple steps on this website to regain it. By way of typing in "su" in terminal emulator and in ADB shell, I now also have su. However I still cant flash anything. When trying to flash cm 4.2.5 in the recovery, the system verifies it and then aborts installation. I then tried to install the Amon-RA recovery to no avail. Tried fastboot, ADP, terminal, im not sure how to access the /data/ partition on the phone and there is no option for acessing the console in the recovery menu. Installing through ADB dosnt work, no test-keys in current recovery. In fastboot it says "okay" for both sending and writing the recovery but rebooting into recovery shows that it didnt work. In terminal it says "flash_image: not found". I'm kinda lost and need some help....
All I need is cm4.2.5 on the phone with root.
Thanks in advance.....
Edit: I triple and quadruple checked the name of the recovery image when trying to install through terminal. I'm pretty sure it cant find the command "flash_image" and not the file itself. Just wanted to clarify...
You could try downgrading to RC29: http://wiki.cyanogenmod.com/index.p...ngrading_to_RC29_.28US.29_or_RC7_.28Europe.29
halr9000 said:
You could try downgrading to RC29: http://wiki.cyanogenmod.com/index.p...ngrading_to_RC29_.28US.29_or_RC7_.28Europe.29
Click to expand...
Click to collapse
Tried that, already... That method only works for the stock T-Mobile G1's which have a different SPL. The Dev G1's come with engineering SPL and I have no idea how to flash the .nbh image from that. All it does I think is enable Fastboot, I cant get it to do anything else.
This fails?
fastboot flash recovery recovery.img
Nope... No luck, it says:
sending 'recovery' <4456kb>.... OKAY
writing 'recovery' <4456kb>.... OKAY
and then I reboot using "fastboot reboot", wait till the homescreen loads, and then go back into recovery and it still shoes the the triangle and the !.....
Bump...
Anyone?? Right now we just have a reallly expensive paper-weight in our hands ANY help/thoughts/comments would be very appreciated...
This thread is meaningless since there is NO SUCH THING as a "DEV G1".
alilbitanuthin said:
Hello all.... I am working on a group project where we will be using a dev G1. The phone was shipped to a another group member and before I can get my hands on it, he decided to upgrade the firmware from 1.0 to 1.6, having very little knowledge of android beforehand and therefore he cant really tell me what exactly he did either. He followed the directions on the HTC website. As far as i can tell, I do have the 26I radio, engineering SPL and 1.6 installed currently, not sure about the recovery though (i.e. stock 1.0 or 1.6). When I got the phone, root access was gone but followed some simple steps on this website to regain it. By way of typing in "su" in terminal emulator and in ADB shell, I now also have su. However I still cant flash anything. When trying to flash cm 4.2.5 in the recovery, the system verifies it and then aborts installation. I then tried to install the Amon-RA recovery to no avail. Tried fastboot, ADP, terminal, im not sure how to access the /data/ partition on the phone and there is no option for acessing the console in the recovery menu. Installing through ADB dosnt work, no test-keys in current recovery. In fastboot it says "okay" for both sending and writing the recovery but rebooting into recovery shows that it didnt work. In terminal it says "flash_image: not found". I'm kinda lost and need some help....
All I need is cm4.2.5 on the phone with root.
Thanks in advance.....
Edit: I triple and quadruple checked the name of the recovery image when trying to install through terminal. I'm pretty sure it cant find the command "flash_image" and not the file itself. Just wanted to clarify...
Click to expand...
Click to collapse
Pretty sure there is...
http://developer.htc.com/adp.html
Bump...
anyone?
alilbitanuthin said:
Pretty sure there is...
http://developer.htc.com/adp.html
Click to expand...
Click to collapse
Do you see ANYTHING on there that says "G1"?
Answer: No you definitely do NOT.
If I remember correctly, after you use fastboot to flash the new recovery image, you can't let the phone reboot or it will overwrite the recovery with the stock recovery image
The solution would be to use fastboot to flash either Cyanogen's or Amon_RA's recovery image, and be quick here, but when you send the fastboot reboot command be holding down the home button on the phone so it will boot to the custom recovery image
lbcoder said:
Do you see ANYTHING on there that says "G1"?
Answer: No you definitely do NOT.
Click to expand...
Click to collapse
lol, no need to nitpick, about the name no less. Thats the least of my worries
As long as you get the message across...
jackslim said:
If I remember correctly, after you use fastboot to flash the new recovery image, you can't let the phone reboot or it will overwrite the recovery with the stock recovery image
The solution would be to use fastboot to flash either Cyanogen's or Amon_RA's recovery image, and be quick here, but when you send the fastboot reboot command be holding down the home button on the phone so it will boot to the custom recovery image
Click to expand...
Click to collapse
That maybe it I'll give it a try as soon as I get back home. Thanks a lot for the help!!
Thanks a lot jackslim, finally got it to work!
Hi there,
I've just installed CM 6.1.1 via Amon Ra's recovery. CyanogenMod is pretty damn good I must say. At any rate, I got interested in the ClockWork ROM manager app and decided to give it a try. Seemed to install OK from the first menu item but (foolishly foolish now it seems) I didn't do anything to remove Amon Ra's original recovery before installing via the menu.
At any rate, any of the options I choose from the Flash ClockworkMod Recovery to require a reboot into the recovery don't work. "Reboot into recovery" and "backup current ROM" reboot and intitally give me the regular Nexus One splash (with unlock icon) then go to a black screen. I can still get to the regular bootloader screen by holding the trackball and pressing power but going to HBOOT gives me a blackscreen on reboot too.
I've given the forums a pretty good trawl but haven't found any answers so far. I wondered about flashing back to a stock bootloader but haven't found any instructions that don't also require flashing back to the stock ROM also.
Can anyone tell me how to flash the bootloader properly/fully (with ClockWork) given the fact that I appear to have broken it. Any help would be greatly appreciated - I really like the idea of being able to use the ClockWork ROM manager!
Use fastboot to flash an SLCD compatible recovery.
Blackscreen means that the SLCD driver is missing and cannot correctly display the recovery.
The compatible recoveries are Amon_ra 1.9 alpha and above and only the latest clockworkmod recovery (which is only available through a certain menu in the ROM Manager app)
Wrong forum bud but here you go:
1) Download this
2) Reboot to bootloader (Open up a cmd window in your sdk/tools/ folder and type 'adb reboot bootloader')
3) Copy recovery-clockwork-2.5.1.0-passion.img to the tools folder.
4) Verify fastboot recognises your device: 'fastboot devices'
5) Issue command 'fastboot flash recovery recovery-clockwork-2.5.1.0-passion.img'
6) Finally reboot using 'fastboot reboot'
You should then be able to use ROM manager just fine
Edit: Or follow the above post using the Rom manager gui.
Wrong forum! Doh! Apologies. Just noticed I'm now listed below this thread: "Thread DELETED/Locked??? >>>> This is DEVELOPMENT section not Q&A/General!!!! <<<<" Hope I don't get whacked with the ban hammer.
Thanks for the amazingly fast replies guys. Tried flashing the clockwork .img file (not using adb but linux-fastboot seems to work OK on my Ubuntu install) and rebooted from the bootloader with the HBOOT - recovery option and tried fasboot-linux reboot from terminal. Still getting a black screen. Same with reinstalling Clockwork recovery from the GUI. Hmmmm.
Incidentally, is there anyway to tell from the bootloader screen what recovery flashes are installed?
LargePiece said:
Wrong forum! Doh! Apologies. Just noticed I'm now listed below this thread: "Thread DELETED/Locked??? >>>> This is DEVELOPMENT section not Q&A/General!!!! <<<<" Hope I don't get whacked with the ban hammer.
Thanks for the amazingly fast replies guys. Tried flashing the clockwork .img file (not using adb but linux-fastboot seems to work OK on my Ubuntu install) and rebooted from the bootloader with the HBOOT - recovery option and tried fasboot-linux reboot from terminal. Still getting a black screen. Same with reinstalling Clockwork recovery from the GUI. Hmmmm.
Incidentally, is there anyway to tell from the bootloader screen what recovery flashes are installed?
Click to expand...
Click to collapse
Oh wait, your HBOOT is black or your recovery? Try a direct "reboot recovery" command from your terminal to see if the recovery now works...
If it's only the hboot, you should be able to flash the 0.35 hboot which supports SLCD
or fastboot oem rebootRUU - if your device's bootloader is unlocked, else be aware that any fastboot command will unlock it, even if you don't apply the oem unlock.
Only clockwork 2.5.1.1 and above, our Amon 1.9 and above is compatible.
Open ROM Manager, and flash a newer version. The option is under All Clockwork Recoveries, at the bottom of the initial page...
Sent from my Nexus One using XDA App
RunTimeWorld said:
or fastboot oem rebootRUU - if your device's bootloader is unlocked, else be aware that any fastboot command will unlock it, even if you don't apply the oem unlock.
Click to expand...
Click to collapse
What?!
Was this added at the same time as the laser beam?
Sent from my Nexus One using XDA App
RunTimeWorld said:
or fastboot oem rebootRUU - if your device's bootloader is unlocked, else be aware that any fastboot command will unlock it, even if you don't apply the oem unlock.
Click to expand...
Click to collapse
Utter crap.
Righto so I've already flashed to the latest version of clockwork (from the GUI) which is where things started getting funky. When I get back to my laptop ill try rebooting into recovery instead of using hboot. And perhaps try flashing to hboot 3.5 if you guys think this might help. I do still get a blackscreen from using the reboot into recovery option from theROM manager GUI.
EDIT: Oh cool. Just read your post more carefully danger-rat. Went to 2.5.1.1 of clockwork and I'm all sorted when booting into recovery from the GUI. Not sure about hboot but I guess if its working from the GUI its all good. ') Thanks for the help people.
EDIT EDIT: I really should try things before posting, anyways hboot works good too now! Niiiiice.
I am stuck without recovery i accidently lost it while trying to flash another recovery..now my phone doesnt boot..so is there any other way to flash recovery without rooting again..i tried flashing it via fastboot but im using hboot 1.33.001d so cant flash anything there...as the verification fails..can does anybody have an idea how to skip the signature verification..
As written in this thread you can flash the
orange-xxx.nbh via fastboot, then boot the rom and you have a full engineering SPL installed. From there you can continue as you want, i.e. flashing new recovery, new SPL, new rom, etc.
which firmware will i get after flashing this..and fyi i am using g1 us version..
I just thought of one other thing to try first. Install Android Commander on your PC. I have successfully reflashed Amon RA recovery with the new radio/SPL from there - there's an option to flash a recovery from your hard drive.
http://androidcommander.com
Failing that, you'll need to start with the nbh, then flash radio/spl/recovery using the instructions provided by Ezterry for installing the radio/spl.
Khizzer said:
which firmware will i get after flashing this..and fyi i am using g1 us version..
Click to expand...
Click to collapse
It's a frensh one, but you will not boot into it, because you'll boot directly into bootloader/fastboot. It's only needed for the engineering spl.
Sent from my Gingerbread on Dream using XDA App
all you do is flash the orange nbh so than you can wipe recovery and flash new one... than you want to flash your radio(2708/2825) than flash spl pretty simple and very convenient lol was in same situation couple days ago
sisterchick said:
I just thought of one other thing to try first. Install Android Commander on your PC. I have successfully reflashed Amon RA recovery with the new radio/SPL from there - there's an option to flash a recovery from your hard drive.
http://androidcommander.com
Failing that, you'll need to start with the nbh, then flash radio/spl/recovery using the instructions provided by Ezterry for installing the radio/spl.
Click to expand...
Click to collapse
i already have it but it does recognize our device if it is on i tried this procedure but of no luck so im back to the nbh method..
does the nbh flashing take a long time...
na it doesn't take long at all it really easy.... you are doing the orange nbh right?
do you have fastboot drivers set up? because you need those... lol
can you still boot up your phone? cuz if you can, what you do is go to rom manager and flash the CWM recovery from that
ldrifta said:
na it doesn't take long at all it really easy.... you are doing the orange nbh right?
Click to expand...
Click to collapse
yeah its about half an hour and its not yet over yes i am doing orange nbh..
bluizzo said:
can you still boot up your phone? cuz if you can, what you do is go to rom manager and flash the CWM recovery from that
Click to expand...
Click to collapse
no my phone doesnt boot up..
ldrifta said:
do you have fastboot drivers set up? because you need those... lol
Click to expand...
Click to collapse
no idea about the fastboot drivers i just diconnected usb and now cmd says that status read failed <too many links>>
so you dont know if you have fastboot setup on your pc...?
yeah i think so but i use android commander and everything via usb..
and yes it was about 30 mins i waited nothing happened..
it says verification failed i attached an image of that
ok power off the device and reboot to fastboot mode, rename the orange file you have located in the sdk/tools folder to 'orange.nbh' now get to the fastboot cmd and type 'fastboot flash nbh orange.nbh' tell me what happens after that?
DJ Steve ported CWM 4.0.1.4 with the release of 507.
Requirements:
Stock 5xx based rom [Honeystreak is not supported!]
Ability to enter fastboot mode: Fastboot+ADB.zip
Battery with 60% or greater charge
Basic understanding of the command line
Install Instructions:
Download recovery.img
flash the recovery with "fastboot flash recovery recovery.img"
Finished
Credits:
DJ_Steve for porting it
Koush for creating clockwork mod
I take no credit beyond this basic guide
Notice:
The Streak 7 with HC might now detect the driver properly, if it doesnt you must force install it using the "Android ADB Interface" from the list of available drivers
Will not work on 2.2.x, you must use CWM 3.0 for that.
Do not attempt to wipe data from within CWM, it will likely case a boot loop afterwards.
Thank you!!
Can I just push this recovery to my recovery partition within 3.2?
Im having issues having my PC at work recognize the fastboot device, and installing the drivers.
I am on xp..
TIA!
'error: cannot load 'recovery.img'
I got fastboot going fine, commands like 'fastboot reboot' are working.
However just above when I use your line to flash recovery, any ideas on what it might be!?
Uploaded new version of fastboot+adb.zip hopefully it has the correct IDs so you dont have to force install it.
Are you sure you downloaded the image correctly, and did you name it correctly when using fastboot
Yeah I was making a repeated typo when pointing fastboot to the recovery but its all working now, thanks a lot.
Clockwork mod (cool blue writing) and rooted all within a few days, good work and thanks to all involved.
FWIW I tried this on the T-MO stock 2.2.2 ROM. The install went fine, I copied S7-4.0.1.4.img to recovery.img and ran the fastboot command with no problems.
I power up the Dell Streak 7 while holding power and the up volume key, and get the menu as expected. I Select "Software Upgrade via update.pkg on SD Card", and the message "Booting recovery kernel image" is displayed.
At this point the machine seems to be frozen. I can reset with a paper clip, and reboot the machine into 2.2.2 just fine, but if I cannot resolve why it does not show the clockwordmod menu, then I guess it is back to NVFLASH.
So what am I doing wrong? do I need an SD card in the device with an update.pkg on the card? Or is there something else?
Oh that was a strong possibility.
CWM 4.0 uses the 507 kernel as a base. 507 will not boot without updating the bootloaders.
So that means CWM 4.0 wouldnt be able to boot unless you had 50x installed.
TheManii said:
Oh that was a strong possibility.
CWM 4.0 uses the 507 kernel as a base. 507 will not boot without updating the bootloaders.
So that means CWM 4.0 wouldnt be able to boot unless you had 50x installed.
Click to expand...
Click to collapse
Probably a good idea then to remove that "Assumed to work on 2.2.2" phrase then from your first append.
So I guess it is NVFLASH time ... Or could I somehow flash back only the original recovery.img using fastboot somehow?
Post updated, i needed someone to actually confirm that it didnt work as i dont have access to a s7
dblml320 said:
Probably a good idea then to remove that "Assumed to work on 2.2.2" phrase then from your first append.
So I guess it is NVFLASH time ... Or could I somehow flash back only the original recovery.img using fastboot somehow?
Click to expand...
Click to collapse
I posted over at TabletRoms yesterday that the new recovery did not work with Froyo 2.2.2.
To answer your question, all you have to do is fastboot flash the old CWM recovery, version 3xx something I think it is.
"waiting for device " and nothing happen !!! what should i do? i can not install driver using files in : Fastboot+ADB\Win32\Streak 5+Streak 7+Venue\Win7 !
cdzo72 said:
I posted over at TabletRoms yesterday that the new recovery did not work with Froyo 2.2.2.
To answer your question, all you have to do is fastboot flash the old CWM recovery, version 3xx something I think it is.
Click to expand...
Click to collapse
Like he said if you flashed it on a s7 that's still on 2.2.x just reflash with the CWM 3.0 one and that one will work fine on 2.2.x
Is there another way to root stock 3.2?
I am getting this error in fastboot...
"Flashing StorMgr partition recovery
Read after write verify partition recovery"
Not the stock one, as no other rooting tools work on it.
Ways to get around it include: using a pre-rooted rom or using a custom rom (which are normally pre-rooted)
Something may be wrong with your device/install if that is coming up. Or possibly your download was bad, try re-downloading it.
I tried re-downloading didn't work, I have stock rom, I don't think I can install a custom or pre-rooted rom without installing CWM?
You can with nvflash, as honeystreak is ment to be installed with nvflash then updated with the bundled CWM, which is prerooted
Whichever method you decide is up to you, as I cannot formally recommend that one method is better then the other.
thesmacker11 said:
Is there another way to root stock 3.2?
I am getting this error in fastboot...
"Flashing StorMgr partition recovery
Read after write verify partition recovery"
Click to expand...
Click to collapse
Well just as an update I tried this on a windows xp, windows 7 32bit, windows 7 64bit computer, and redownloaded that file each time and it still does the same thing on my device.
It's likely your device itself that's the issue then, I cant be more specific as I dont own a S7
I'm not sure if I should be asking questions here or over in another forum. Figure I'll start here...
I was sorely missing app2sd in honeycomb so went to use and install Link2SD figuring I'd use that. But it doesn't seem to see the second partition I've made on my SDHC card. I can mount the card on Mac OS and Linux and both mount the two partitions on the card so I feel pretty sure I formatted the card correctly. I saw some comment about a change in the way CW mounts things and it causing troubles in the Link2SD thread but I don't understand enough about the magic of Android and how it mounts discs, although I know it had Linux roots, so the comments in that thread weren't clear to me what I can do to get Link2SD working or for that matter even start to gather info to try to figure out what's wrong. Can anyone help me out or point me to a thread that can get me started in figuring out what's going wrong?
Sent from my HTC Flyer P512 using Tapatalk
ok so i installed the drivers for fastboot and i can enter fast boot , but how can i push the file? soory im a newb with the streak.
My question is similar to 'nikpmr's troubles but different enough I think they deserve a separate post.
The Problem as UnderstoodI was trying to root my device following the guide at this website. It's so simple it's a wonder I messed up. I think my failure was that I thought the drivers installed when I connected the phone were enough so I skipped that step. Then when running fastboot flash recovery.img the install failed. So I saw on some forum that it was supposed to be fastboot flash boot recovery.img of course now I know if anything it ought to have been "recovery" not "boot".
What I've Tried & Partial SolutionAt first I was just stuck in a boot loop and selecting "sideload" from the CWM recovery failed to allow me to connect with ADB or fastboot. i.e. Running "fastboot devices" and "adb devices" both returned as having no devices connected to my computer. So I installed the HTC Sync and promptly uninstalled the non driver parts of the app. Then I installed USBdeview and used it to uninstall all the USB devices associated with my HTC First. After doing that I learned booting into HBOOT allowed me to connect to the computer using fastboot and after then booting to the CWM Recovery I was able to connect using ADB to do a sideload. So I guess I'm about halfway there. Unfortunately after looking up the newest RUU and attempting to sideload it using "adb sideload OTA_MYST_UL_1.08.502.1-1.08.502.4.zip" the sideload failed. After selecting "- install zip from sideload" I get a message twice of "failed to open driver control: No such file or directory". It also failed when I attempted it with a similar fastboot command. So from all that I surmise my ROM is ruined and just needs to be replaced.
QuestionSo how do I go about replacing this ROM and boot partition? And, which ROM should I use? Is the one I got from the RUU site suitable? And what about the radio? I just need my phone to work. I can worry about rooting later. At this point I think I know what's happened but I don't know where to begin reading to figure out how to fix it myself.
Thanks for reading,
Relevant HBOOT text:
Code:
*** TAMPERED ***
*** UNLOCKED ***
MYSTUL PVT SHIP S-ON RL
HBOOT-2.00.0000
RADIO-1.15.40.00.13_2
OpenDSP-v9.2.0268.1214
eMMC-boot
Mar 22 2013,21:29:50:1682
1. you had to type in fastboot flash recovery recovery.img NOT fastboot flash boot recovery.img
Well there was an actual all in 1 tool to get cwm/twrp & root with a click for this specific device somewhere around these threads.
1) what exactly is the problem? (Sorry it was just so many words)
I don't think side loading the RUU would work bc I haven't heard its possible to flash it in the phone itself.
2) why don't you just sideload an existing pre-rooted ROM instead of the RUU file?
3) I see you're s-on, did you try flashing just the boot.IMG from the ROM you've got on it?
BTW I've only had luck with twrp on having it successfully detected when wanting to sideload
abrahammmmmmm_ said:
Well there was an actual all in 1 tool to get cwm/twrp & root with a click for this specific device somewhere around these threads.
1) what exactly is the problem? (Sorry it was just so many words)
I don't think side loading the RUU would work bc I haven't heard its possible to flash it in the phone itself.
2) why don't you just sideload an existing pre-rooted ROM instead of the RUU file?
3) I see you're s-on, did you try flashing just the boot.IMG from the ROM you've got on it?
BTW I've only had luck with twrp on having it successfully detected when wanting to sideload
Click to expand...
Click to collapse
1) The issue is I did "fastboot flash boot recovery.img" rather than "fastboot flash recovery.img" now I don't seem to have a boot mount point.
2) That sounds best. I didn't realize the RUU want a flashable ROM. More I just have to find the updated stable stock ROM.
3) I didn't have a ROM on it. I was just trying to root stock. Seems like I'm pretty close once I find that ROM.
Thanks y'all! Between your answers I think I have enough to go on. Feel free to point me to your preferred stable ROM. I'm content with stock but it would be nice to have Tiranium BU.
bnjo said:
1) The issue is I did "fastboot flash boot recovery.img" rather than "fastboot flash recovery.img" now I don't seem to have a boot mount point.
2) That sounds best. I didn't realize the RUU want a flashable ROM. More I just have to find the updated stable stock ROM.
3) I didn't have a ROM on it. I was just trying to root stock. Seems like I'm pretty close once I find that ROM.
Thanks y'all! Between your answers I think I have enough to go on. Feel free to point me to your preferred stable ROM. I'm content with stock but it would be nice to have Tiranium BU.
Click to expand...
Click to collapse
Right now our most stable stock ROM is our rooted stock ROM
http://forum.xda-developers.com/showthread.php?t=2287811
We currently have 2 very able recognized devs working on CyanogenMod. You can expect something new in the near future but until then what I've showed you is the best.
Have any problems just come back to the thread
Success!
abrahammmmmmm_ said:
Right now our most stable stock ROM is our rooted stock ROM
http://forum.xda-developers.com/showthread.php?t=2287811
We currently have 2 very able recognized devs working on CyanogenMod. You can expect something new in the near future but until then what I've showed you is the best.
Have any problems just come back to the thread
Click to expand...
Click to collapse
Thanks guys I know I always like to know when something I said was successful in helping someone. I just wanted yall to know after sideloading the most recent Odexed ROM then pushing it to memory after it wouldn't boot I succeeded after taking abrahammmmmm's advice of flashing the boot.img from HBOOT. After a longer boot than I'm used to I was able to get into my phone again. I wasn't able to use my TitaniumBU to restore but that just meant I had to spend a few minutes selecting apps to install.. And restoring a data backup for the only important app that doesn't keep the primary data off the phone.
Thanks again!
tl;dr Flashing the Odexed ROM boot.img fixed my issues. Thx!
bnjo said:
Thanks guys I know I always like to know when something I said was successful in helping someone. I just wanted yall to know after sideloading the most recent Odexed ROM then pushing it to memory after it wouldn't boot I succeeded after taking abrahammmmmm's advice of flashing the boot.img from HBOOT. After a longer boot than I'm used to I was able to get into my phone again. I wasn't able to use my TitaniumBU to restore but that just meant I had to spend a few minutes selecting apps to install.. And restoring a data backup for the only important app that doesn't keep the primary data off the phone.
Thanks again!
tl;dr Flashing the Odexed ROM boot.img fixed my issues. Thx!
Click to expand...
Click to collapse
Great! glad to hear I could help. Yes it's always nice knowing when something I've said has helped someone in any way
bnjo said:
Thanks guys I know I always like to know when something I said was successful in helping someone. I just wanted yall to know after sideloading the most recent Odexed ROM then pushing it to memory after it wouldn't boot I succeeded after taking abrahammmmmm's advice of flashing the boot.img from HBOOT. After a longer boot than I'm used to I was able to get into my phone again. I wasn't able to use my TitaniumBU to restore but that just meant I had to spend a few minutes selecting apps to install.. And restoring a data backup for the only important app that doesn't keep the primary data off the phone.
Thanks again!
tl;dr Flashing the Odexed ROM boot.img fixed my issues. Thx!
Click to expand...
Click to collapse
i think what happened, when you typed in "fastboot flash boot recovery.img" is this
boot, is also known as kernel in aosp and rom building terms, because if you look inside a rom.zip, you will see that the kernel is the boot.img
so what happened is you flashed a recovery as kernel, and duh it wont boot cause if the kernel doesnt work, the os doesnt either
so what YOU did is you simply reflashed the stock kernel, usually after changing a kernel, it takes a while to boot cause...well you get it right?
the kernel is what android is based off of, kind of like ubuntu, its a linux os based on the original linux kernel.
russian392 said:
usually after changing a kernel, it takes a while to boot cause...well you get it right?
Click to expand...
Click to collapse
Yes I get it.
russian392 said:
i think what happened, when you typed in "fastboot flash boot recovery.img" is this
boot, is also known as kernel in aosp and rom building terms, because if you look inside a rom.zip, you will see that the kernel is the boot.img
so what happened is you flashed a recovery as kernel, and duh it wont boot cause if the kernel doesnt work, the os doesnt either
so what YOU did is you simply reflashed the stock kernel, usually after changing a kernel, it takes a while to boot cause...well you get it right?
the kernel is what android is based off of, kind of like ubuntu, its a linux os based on the original linux kernel.
Click to expand...
Click to collapse
That's what I thought happened. If I had stopped to read the help on fastboot before running "fastboot flash boot recovery.img" I wouldn't have made that mistake because I would have seen I wanted to flash recovery. One thing I *did not* know, which I'm glad to know, was that the boot.img contains the kernal. I was thinking Android was more similar to IBM style PCs than it is and therefore the boot.img was analogous to a bootloader like grub or lilo.
So the one thing I don't get is how is partitioning done? I take it Androids have some reserved partition for boot and the boot.img takes care of all system partitioning and mounts /sdcard/ for everything else. i.e. userland; appdata, media, and files. Am I guessing correctly?
bnjo said:
So the one thing I don't get is how is partitioning done? I take it Androids have some reserved partition for boot and the boot.img takes care of all system partitioning and mounts /sdcard/ for everything else. i.e. userland; appdata, media, and files. Am I guessing correctly?
Click to expand...
Click to collapse
in a nutshell yes, the boot.img uses the fstab
btw 10 posts you'll be "verified"
So the one thing I don't get is how is partitioning done? I take it Androids have some reserved partition for boot and the boot.img takes care of all system partitioning and mounts /sdcard/ for everything else. i.e. userland; appdata, media, and files. Am I guessing correctly?
Click to expand...
Click to collapse
Yep that's correct.
The name correlation is booting up requires kernel there for kernel is called beet.IMG
Thing about custom kernels, they aren't like that and simply contain modded files and pretty much an in packaged kernel.
Sent from my HTC first using xda app-developers app
stock recovery
please can anyone send me the stock recovery.img
when i try to get it from RUU it says archive is corrupted
astrit1995 said:
please can anyone send me the stock recovery.img
when i try to get it from RUU it says archive is corrupted
Click to expand...
Click to collapse
here:
http://androidfiles.org/getdownload.php?file=MystUL/Stock_Roms/stockrecovery.img
if you help, press thanks!!
Serupo said:
here:
http://androidfiles.org/getdownload.php?file=MystUL/Stock_Roms/stockrecovery.img
if you help, press thanks!!
Click to expand...
Click to collapse
Thank you for your help,i solved my problem yesterday but i think im gona need this sometime...