Related
Alright, I tried flashing to Cyanogen's latest rom from a hero I had for a while (I wanted speed and missed long battery life) so I download the OTA file I was supposed to then flashed it and flashed cyanogenmod right after that like I was suppose to. I had problems where it was force closing every second and a question mark came over the battery, weird. So I wiped redownloaded then checked MD5 and then reflashed but I forgot to do cyanogen (I blame hulu for having me lose track and forget I didn't flash cyanogen) and then it boots and I was watching hulu some more soon to realize I don't have Super user or any apps that come with CM I figured I could go into recovery and flash CM, no its a completly different recovery. I tried fastboot to rewrite RA recovery and it said it worked and I reboot but its still the very limited and horrible recovery which isn't capable of flashing different roms. I tried update.zip (renaming CM). I'm almost at the point where I'm going to downgrade and re-root but I don't have data and I need to log in to google using data.. So anyone here have any ideas on how I can recovery my SU?
Recovery Trouble
CrazyEye said:
Alright, I tried flashing to Cyanogen's latest rom from a hero I had for a while (I wanted speed and missed long battery life) so I download the OTA file I was supposed to then flashed it and flashed cyanogenmod right after that like I was suppose to. I had problems where it was force closing every second and a question mark came over the battery, weird. So I wiped redownloaded then checked MD5 and then reflashed but I forgot to do cyanogen (I blame hulu for having me lose track and forget I didn't flash cyanogen) and then it boots and I was watching hulu some more soon to realize I don't have Super user or any apps that come with CM I figured I could go into recovery and flash CM, no its a completly different recovery. I tried fastboot to rewrite RA recovery and it said it worked and I reboot but its still the very limited and horrible recovery which isn't capable of flashing different roms. I tried update.zip (renaming CM). I'm almost at the point where I'm going to downgrade and re-root but I don't have data and I need to log in to google using data.. So anyone here have any ideas on how I can recovery my SU?
Click to expand...
Click to collapse
first .. try not to start threads like this .. there is a Q&A thread already and many many CM threads to post questions
second .. if /system/recovery.img exists it will try to flash it upon reboot .. so copy the RA recovery to /system/recovery.img and see it that does the trick for you .. i had a similar problem once and fixed it in this way
LucidREM said:
first .. try not to start threads like this .. there is a Q&A thread already and many many CM threads to post questions
second .. if /system/recovery.img exists it will try to flash it upon reboot .. so copy the RA recovery to /system/recovery.img and see it that does the trick for you .. i had a similar problem once and fixed it in this way
Click to expand...
Click to collapse
I tried to push and this is what happened
Code:
C:\>adb push recovery.img /system/
failed to copy 'recovery.img' to '/system//recovery.img': Read-only file system
I've never tried adb push for anything I usually used DroidExplorer but nothing showed in it.
You have to mount the file system as read/write, search for the command.
You have to do adb remount first, it will mount /system for read/write access
Actually, he's supposed to adb root first and then adb remount. That's the way it works with the stock 1dp1 image. I told cyanogen that suggesting flashing either of those images was a mistake, many people bound to get it wrong. Easier to just fastboot flash system.img then fastboot reboot -w. The system won't boot right because of the incompatible boot.img, that's a good thing, then you can 3-finger reboot and then flash cm through recovery. Since the only things cm script copies are in /system, that's all you need.
jubeh said:
Actually, he's supposed to adb root first and then adb remount. That's the way it works with the stock 1dp1 image. I told cyanogen that suggesting flashing either of those images was a mistake, many people bound to get it wrong. Easier to just fastboot flash system.img then fastboot reboot -w. The system won't boot right because of the incompatible boot.img, that's a good thing, then you can 3-finger reboot and then flash cm through recovery. Since the only things cm script copies are in /system, that's all you need.
Click to expand...
Click to collapse
Oh well I've never had the problem so I've never lost root. At least it's not some ridiculously complicated process where you have to spin around 43 times while singing the Dora the Explorer song...backwards, and while gargling orange juice.
Thanks everyone, after messing around with adb push and fastboot I got the RA recovery image loaded and it works now, so thank you to everything who helped me and to the extremely rude person, no one likes you.
So once again thank you!
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 I am a newbie here and I have a Nexus one.
After unlock and rooted, i tried to enter the recovery mode. But I encounter problem. I cannot get into the green recovery mode. Instead I got an exclamation mark (!) warning with a little android standing on side of the mark. Can anybody tell me what I did wrong?
Thank you,
Jack
Did you flash amon-RA-1.7.0 yet?
You didn't install a custom recovery image. See the rooting guide here and it tells you how to do that.
No.. I only unlocked and rooted.
But I am not sure if my phone is rooted because it doesn't indicate that the phone is rooted after i run the superboot.bat file. The command prompt only came up for a sec and then gone.
When I open my phone. It is just like a new Nexus One. Except for unlocked sign when I boot up.
Thanks for the help
Jack
It's unlocked, now flash the recovery image, back-up, then wipe and flash Rom.
evilkorn said:
You didn't install a custom recovery image. See the rooting guide here and it tells you how to do that.
Click to expand...
Click to collapse
I followed the instruction here.. it didn't say I have to install a custom recovery image. Can you show me where? Thanks
***Informative Links*** - Read before clicking "New Thread"
http://forum.xda-developers.com/showthread.php?t=618768
Root the Nexus with ROM Links *Updated*
http://forum.xda-developers.com/showthread.php?t=612858
7. Flash Amons RA Recovery Image from here
Hi, thanks for the tip
I was able to boot into the recovery image and do a back up from there.
Now I am trying to flash the image into my Nexus one. But when I type fastboot-windows flash ... it says unknown partition and cannot recognize the file name..
can you please help again? thanks.
The terminal method from the phone is probably easier for you to do.
Most likely you didn't cd to the correct directory where the file is from command prompt. Give us a picture of what you did and the error and the steps you took to get to the point you are at because the guide and programs work.
hi.. i spent a lot of time reading and trying.. finally this is what i did to make it work
Step 1. fastboot-windows boot recover image file <-- this is how to got into recovery mode and back up
Step 2. fastboot-windows flash recovery recovery.image.file.name <-- this replace my original recovery flash and the little annoy android man is gone
I did backup again after Step 2. By now I think I realize that Step 1 is the same as Step 2. But no harm backing up two times..
I then installed a new rom into my N1.. everything looks fine now.. i will go ahead and try out some features..
Thank you for all the advices
Device Details:
Carrier: Sprint
Android OS: 1.5 (Cupcake)
Bootloader details:
Hero XC
HBOOT-1.41.0000 (HERO20000)
MICROP-0110
TOUCH PANEL-SYN0104
RADIO-1.04.01.09.21
Sep 1 2009, 19:18:45
Right now I am tinkering with the Linux kernel for the HTC Hero. I am able to build the kernel source from the HTC website and have access to root on the device. However when attempting to flash the zimage using fastboot it gives the error "(Remote: not allowed)"
While searching through the forums I have found that there are additional steps that needed to be done to fully root the device. I have followed the instructions on the following thread.
http://forum.xda-developers.com/showthread.php?t=583291
After flashing the recovery image and sending the command to reboot into recovery mode, the device will start up at the HTC splash screen and will not continue further for upwards of 15 minutes (I have not tried waiting much longer)
I have also attempted the flashrec method outlined here.
http://forum.xda-developers.com/showthread.php?t=603052
Recovery mode yields the same results when booting into recovery mode from shell or from hboot's home button. Has anybody ran into this problem and found a solution? If so, please provide direction.
do u realize the methods u are using are over a year old.
just had to put that out there...
dlongestopp said:
Device Details:
Carrier: Sprint
Android OS: 1.5 (Cupcake)
Bootloader details:
Hero XC
HBOOT-1.41.0000 (HERO20000)
MICROP-0110
TOUCH PANEL-SYN0104
RADIO-1.04.01.09.21
Sep 1 2009, 19:18:45
Right now I am tinkering with the Linux kernel for the HTC Hero. I am able to build the kernel source from the HTC website and have access to root on the device. However when attempting to flash the zimage using fastboot it gives the error "(Remote: not allowed)"
While searching through the forums I have found that there are additional steps that needed to be done to fully root the device. I have followed the instructions on the following thread.
http://forum.xda-developers.com/showthread.php?t=583291
After flashing the recovery image and sending the command to reboot into recovery mode, the device will start up at the HTC splash screen and will not continue further for upwards of 15 minutes (I have not tried waiting much longer)
I have also attempted the flashrec method outlined here.
http://forum.xda-developers.com/showthread.php?t=603052
Recovery mode yields the same results when booting into recovery mode from shell or from hboot's home button. Has anybody ran into this problem and found a solution? If so, please provide direction.
Click to expand...
Click to collapse
go to the search box at the top of the paige and put in
"z4root apk for hero cdma" and use it
oostah said:
go to the search box at the top of the paige and put in
"z4root apk for hero cdma" and use it
Click to expand...
Click to collapse
Thank you for the response. Currently my device is running Android 1.5 so it cannot install this. I will try updating the OS in order to install it.
well, my best advice is this: hopefully you can run an RUU.exe while connected to fastboot. Follow the logical links in my links thread listed below, once you have RUU'ed to android 2.1, then root by whatever method you wish from my thread, hope this helps.
http://forum.xda-developers.com/showthread.php?t=1063843
EDIT: you may also be able to update officially from www.htc.com/support
EDIT 2: there are also links there to unlock the nand and bootloader AKA "s-off" so that you can fastboot flash your kernel. But look around in the development section, A LOT has happended since 1.5 lmao. Like custom fast kernels and nice ROMs and such.
il Duce said:
well, my best advice is this: hopefully you can run an RUU.exe while connected to fastboot. Follow the logical links in my links thread listed below, once you have RUU'ed to android 2.1, then root by whatever method you wish from my thread, hope this helps.
http://forum.xda-developers.com/showthread.php?t=1063843
EDIT: you may also be able to update officially from www.htc.com/support
EDIT 2: there are also links there to unlock the nand and bootloader AKA "s-off" so that you can fastboot flash your kernel. But look around in the development section, A LOT has happended since 1.5 lmao. Like custom fast kernels and nice ROMs and such.
Click to expand...
Click to collapse
Thanks for your suggestion
I didn't realize there was an official 2.1 update until now since there was no over-the-air update for this device.
dlongestopp said:
Thanks for your suggestion
I didn't realize there was an official 2.1 update until now since there was no over-the-air update for this device.
Click to expand...
Click to collapse
Holy crap lol. I think the update to 2.1 was in august or something, wow. How did you not know? I would think sprint would have told you at some point in an email or text or if you ever called them for tech help. Anyway, yeah hunt around those links, ask questions back in here if you need help.
once u get everything going this thread will be your best friend and be sure to thx duce for it.
http://forum.xda-developers.com/showthread.php?t=1063843
il Duce said:
Holy crap lol. I think the update to 2.1 was in august or something, wow. How did you not know? I would think sprint would have told you at some point in an email or text or if you ever called them for tech help. Anyway, yeah hunt around those links, ask questions back in here if you need help.
Click to expand...
Click to collapse
Thanks for the assistance. I have updated my Hero to the official 2.1, then attempted rooting with z4root. It would freeze at the reboot screen for about 10 minutes, yet still rooted the phone (except the recovery partition)
I had tried using fastboot to load my own zImage, but it would continue giving me the "Remote: not allowed" error. After that, I unrooted through z4root to undo my changes and used RegawMOD Hero Rooter v1.3 which installed clockworkmod as the recovery partition. (http://forum.xda-developers.com/showthread.php?t=909258 )
Once I had done this, I was able to boot into the recovery partition and use the unrevoked-forever boot to have hboot turn to "S-OFF" ( http://forum.xda-developers.com/showthread.php?t=759955 ) which seemed to work. However, when runnning
Code:
fastboot flash image zimage zImage
It gives me the same Remote: not allowed. I saw a post for using fastboot without s-off by booting into RUU mode, however it would not recognize the zimage partition.
Do you have any more suggestions?
I really appreciate your assistance
dlongestopp said:
Thanks for the assistance. I have updated my Hero to the official 2.1, then attempted rooting with z4root. It would freeze at the reboot screen for about 10 minutes, yet still rooted the phone (except the recovery partition)
I had tried using fastboot to load my own zImage, but it would continue giving me the "Remote: not allowed" error. After that, I unrooted through z4root to undo my changes and used RegawMOD Hero Rooter v1.3 which installed clockworkmod as the recovery partition. (http://forum.xda-developers.com/showthread.php?t=909258 )
Once I had done this, I was able to boot into the recovery partition and use the unrevoked-forever boot to have hboot turn to "S-OFF" ( http://forum.xda-developers.com/showthread.php?t=759955 ) which seemed to work. However, when runnning
Code:
fastboot flash image zimage zImage
It gives me the same Remote: not allowed. I saw a post for using fastboot without s-off by booting into RUU mode, however it would not recognize the zimage partition.
Do you have any more suggestions?
I really appreciate your assistance
Click to expand...
Click to collapse
regaws s-off allows flashing HERCIMG.zip to any partition, in your case the boot.img. The ohter s-off method by darch allows fastboot commands. You should read up on regaws way. All you need is a zip that contains a boot.img and an android-info.txt. If you wish to flash darchs s-off methos over top of regaws you CAN do that, I did that myself. That way you can use whatever method you wish. There are links in my links thread. Good luck.
il Duce said:
regaws s-off allows flashing HERCIMG.zip to any partition, in your case the boot.img. The ohter s-off method by darch allows fastboot commands. You should read up on regaws way. All you need is a zip that contains a boot.img and an android-info.txt. If you wish to flash darchs s-off methos over top of regaws you CAN do that, I did that myself. That way you can use whatever method you wish. There are links in my links thread. Good luck.
Click to expand...
Click to collapse
Thanks again I used regaw's method to overwrite the recovery partition (http://forum.xda-developers.com/showthread.php?t=694572 ) afterwards used the new recovery partition to flash the hboot ( http://forum.xda-developers.com/showthread.php?t=765237 )
I can now flash using fastboot.
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...