Database Develop

How to flash stock images.

this guide is for those who still have Clockwork Mod Recovery still on device you can thank bogdi1988 for his work and orginal guide here :
http://forum.xda-developers.com/showpost.php?p=12185475&postcount=76
BUT THIS MAY WORK FOR OTHERS IF YOU KNOW HOW TO MOUNT SYSTEM AND DATA AND THOSE THINGS FROM ADB
but to simplify I did this :
stock images
recovery.img
http://dl.dropbox.com/u/2252176/recovery.img
boot.img
http://dl.dropbox.com/u/2252176/boot.img
Once in recovery mount everything you can system , data , cache , everyrthing besides sd card
then go into command prompt and type adb shell make sure its working if you still have root it will show # if not it will show $ I believe no biggie as long as it picks up in shell.
then type : flash_image /dev/block/mmcblk3p2 /sdcard/boot_orig.img
then type : flash_image /dev/block/mmcblk3p1 /sdcard/recovery_orig.img
select reboot from the recovery. now it will reboot and it will format misc and it will reboot again.
bogdi1988 suggest flash all images over again in fastboot
in this order
system.img
recovery.img
boot.img
thanks go to everyone who has a dell streak 7 that was willing to try all these hacks and risking your devices for the greater good of the streak
P.S. I will post system.img in a second
Also for fastboot help thank bogdi1988 again heres his post that helped me
http://forum.xda-developers.com/showpost.php?p=11929063&postcount=23

I have read and tried everything
I attempted the adb method but can't get into fastboot... I believe I got the adb commands correct and I don't get an error but my the restore is not taking... at the reboot it goes right back into CWM 3.0.2.0 here's my adb shell read out...
C:\android\platform-tools>adb shell
~ #
C:\android\platform-tools>adb shell
~ # flash_image /dev/block/mmcblk3p2/sdcard/boot_orig.img
flash_image /dev/block/mmcblk3p2/sdcard/boot_orig.img
usage: flash_image partition file.img
~ # flash_image /dev/block/mmcblk3p1/sdcard/recovery_orig.img
flash_image /dev/block/mmcblk3p1/sdcard/recovery_orig.img
usage: flash_image partition file.img
~ #
I don't know what else to do, I can't find a thread that stays on track long enough to follow this issue all the way thru... please help... I have read and tried everything, i can't find a clear set of alternatives... am i missing a step?

ya, i'm stuck in the same situation. I either get a "error -1" or it says "usage: flash_image partition file.img"
does getting "usage: flash_image partition file.img" mean the file was successfully flashed?

dfspot said:
I attempted the adb method but can't get into fastboot... I believe I got the adb commands correct and I don't get an error but my the restore is not taking... at the reboot it goes right back into CWM 3.0.2.0 here's my adb shell read out...
C:\android\platform-tools>adb shell
~ #
C:\android\platform-tools>adb shell
~ # flash_image /dev/block/mmcblk3p2/sdcard/boot_orig.img
flash_image /dev/block/mmcblk3p2/sdcard/boot_orig.img
usage: flash_image partition file.img
~ # flash_image /dev/block/mmcblk3p1/sdcard/recovery_orig.img
flash_image /dev/block/mmcblk3p1/sdcard/recovery_orig.img
usage: flash_image partition file.img
~ #
I don't know what else to do, I can't find a thread that stays on track long enough to follow this issue all the way thru... please help... I have read and tried everything, i can't find a clear set of alternatives... am i missing a step?
Click to expand...
Click to collapse
You are missing the space between mmcblk3pX and /sdcard.

ok, thats what i thought. when i do it the other way i get the "failed with Error: -1" any ideas on that. also if i send it back to t-mobile under the warranty, they won't send it back as damaged since i had CMW installed o it will they?

thatruth132 said:
this guide is for those who still have Clockwork Mod Recovery still on device you can thank bogdi1988 for his work and orginal guide here :
http://forum.xda-developers.com/showpost.php?p=12185475&postcount=76
BUT THIS MAY WORK FOR OTHERS IF YOU KNOW HOW TO MOUNT SYSTEM AND DATA AND THOSE THINGS FROM ADB
but to simplify I did this :
stock images
recovery.img
http://dl.dropbox.com/u/2252176/recovery.img
boot.img
http://dl.dropbox.com/u/2252176/boot.img
Once in recovery mount everything you can system , data , cache , everyrthing besides sd card
then go into command prompt and type adb shell make sure its working if you still have root it will show # if not it will show $ I believe no biggie as long as it picks up in shell.
then type : flash_image /dev/block/mmcblk3p2 /sdcard/boot_orig.img
then type : flash_image /dev/block/mmcblk3p1 /sdcard/recovery_orig.img
select reboot from the recovery. now it will reboot and it will format misc and it will reboot again.
bogdi1988 suggest flash all images over again in fastboot
in this order
system.img
recovery.img
boot.img
thanks go to everyone who has a dell streak 7 that was willing to try all these hacks and risking your devices for the greater good of the streak
P.S. I will post system.img in a second
Also for fastboot help thank bogdi1988 again heres his post that helped me
http://forum.xda-developers.com/showpost.php?p=11929063&postcount=23
Click to expand...
Click to collapse
great how to

white99 said:
ok, thats what i thought. when i do it the other way i get the "failed with Error: -1" any ideas on that. also if i send it back to t-mobile under the warranty, they won't send it back as damaged since i had CMW installed o it will they?
Click to expand...
Click to collapse
humz mine wont flash at all

Guys,
If someone can help people struck here like me, it would be great.. i get the same -1 error message... when i run the second command. the first one passes through and i get a # for flash_image /dev/block/mmcblk3p2 /sdcard/boot_orig.img.
When we downloaded the file boot.img, how would boot_orig.img work? am i missing something?
The second command throws me an error..
Guys really waiting for help... bricked my streak in hours after i brought it..

where are you at in la

I need a little bit of help for an ex-ipohone user
Hey guys sorry to ask u a noob question, but can anyone give me an ideea how to remove/unistall CWM Recovery so i can send back my Streak 7 for repair? I have installed CWM thru fastboot an i am currently on stock 2.2.2 rom. Or if there is a thread that i didnt find please a little help would be much apreciated.

i have figured it out eventualy after 20 hrs of brain scratching ived used NVflash and worked fast and easy

thatruth132 said:
this guide is for those who still have Clockwork Mod Recovery still on device you can thank bogdi1988 for his work and orginal guide here :
http://forum.xda-developers.com/showpost.php?p=12185475&postcount=76
BUT THIS MAY WORK FOR OTHERS IF YOU KNOW HOW TO MOUNT SYSTEM AND DATA AND THOSE THINGS FROM ADB
but to simplify I did this :
stock images
recovery.img
http://dl.dropbox.com/u/2252176/recovery.img
boot.img
http://dl.dropbox.com/u/2252176/boot.img
Once in recovery mount everything you can system , data , cache , everyrthing besides sd card
then go into command prompt and type adb shell make sure its working if you still have root it will show # if not it will show $ I believe no biggie as long as it picks up in shell.
then type : flash_image /dev/block/mmcblk3p2 /sdcard/boot_orig.img
then type : flash_image /dev/block/mmcblk3p1 /sdcard/recovery_orig.img
select reboot from the recovery. now it will reboot and it will format misc and it will reboot again.
bogdi1988 suggest flash all images over again in fastboot
in this order
system.img
recovery.img
boot.img
thanks go to everyone who has a dell streak 7 that was willing to try all these hacks and risking your devices for the greater good of the streak
P.S. I will post system.img in a second
Also for fastboot help thank bogdi1988 again heres his post that helped me
http://forum.xda-developers.com/showpost.php?p=11929063&postcount=23
Click to expand...
Click to collapse
OMFG I would so kiss you right now. I was stuck where I could only load up CWR and nothing else was working. You are my hero. *sigh*

No biggie just hit that thanks.button
Sent from my Dell Streak 7 using XDA Premium App

The links are down, any mirrors?

Same need files links re not working

IMG Reposted?
Hi Folks,
A couple of people have posted that the boot, recovery, and system image links respond with a "404 not found" error. This is still the case.
I recall reading somewhere else that the images may still live on the SD card on the device. If this is true does someone know where in the file structure they may be?
If not, does anyone know where to obtain the images?
Currently I'm in CWM reboot hades on my Dell Streak 7. Tried the Dell OTA update for Honeycomb...didn't know that was a BAD thing until it was too late.
I've tried flashing boot and recovery images from a backup I'd made earlier, but no luck, so thatruth's excellent guide here: http://forum.xda-developers.com/show....php?t=1006829 doesn't help much...unless I can get the recovery and boot images.
So to reiterate:
I can get to CWM and clear the caches and flash a recovery.
I can communicate with the device via ADB and have flashed it with the backup images.
I can mount the internal SD card via CWM and my pc.
After flashing with the backup images, Fastboot still does not recognize that the device is connected, and the device does not apper to go through the 'format steps'.
Cheers,
L2

Found 'lightly modified' roms (thank you DJ Steve!) for a T-Mobile streak on another XDA thread. Flashed using adb, and tadaaaa, it booted! sliiiight problem. Will not boot into recovery and no wireless.
Managed to install rom manager (AKA ClockWorkMod) via ADB but CWM wan't an internet connection to install the recovery rom. grrrrr.
One of the other modifications (aside from root) by DJ Steve is the installation of 'BusyBox', This actually seems to complicate things for me because I don't really know how to issue ADB commands from the BusyBox shell. I get a lot of 'invalid command' and the like... I was able to install CWM OUTSIDE the adb shell (adb install rommanager) but once I'm in the shell (adb shell)I don't know how to issue the proper commands.
What I want to do is either remove busybox, or use ADB inside busybox to flash the CWM recovery rom, then flash my backup roms. (and hopefully return to full functionality.)
Any suggestions on how to use ADB commands inside of busy box to flash a rom?

Can anyone upload the stock rom images? I need to flash back to stock :\

How to restore your DS7

This may void your warranty, cost you your soul, and cause your spouse to leave you - ALL OF WHICH I AM NOT RESPONSIBLE FOR!
So, if it's because you screwed up flashing something, bricked your tablet with an OTA update after you installed CWM, or whatever, this is how you get it back to its outta-da-box shape!
(Please note, this assumes you have both installed CWM on your DS7 AND have installed the latest SDK on your computer).
1. Download the three attached .img files
2. Boot into CWM (since there really isn't anything else you can do)
3. In CWM, mount your SD card (so that you can view files via USB)
4. Plug in your DS7 to your computer, and copy the three .img files to the root of your SD card
5. Unmount your SD card, but leave the USB cable plugged into computer
6. Mount as many things as you can (ie system, boot, etc)
7. Open up command prompt, and navigate to your Android/tools folder, and type "adb devices"
8. There should be a number that shows up, or a "?" - either at this point is fine
9. Type the following command:
Code:
adb shell
a hash tag should show up that looks like this:
Code:
#~
10. Now, type the follow two commands one at a time:
Code:
flash_image /dev/block/mmcblk3p2 /sdcard/boot_orig.img
flash_image /dev/block/mmcblk3p1 /sdcard/recovery_orig.img
11. now, select "reboot" from DWM to reboot your device. It should boot and say something like "Formating Misc", and then it will reboot repeatedly
12. Use something small to push the RESET button on the DS7 (it's next to the SD card slot)
Your screen should go blank
13. Now, press and hold both the POWER button and the VOLUME - button until the screen comes on saying that the "fastboot downloader" is booted
14. Copy the three .img files into the your Android/tools folder
15. Now type the following code:
Code:
fastboot devices
16. There should be a number that shows up, or a "?" - either at this point is fine once again
17. Now type the following commands one at a time. The first will take a while to complete - this is okay:
Code:
fastboot flash system system_orig.img
fastboot flash recovery recovery_orig.img
fastboot flash boot boot_orig.img
Now, if after every command a "finished." is given, along with the total time each command took, you may continue.
18. You may now type the triumphant command:
Code:
fastboot reboot
Which will reboot your device.
Give it a little bit to boot, but when all is done you should see the original T-Mobile boot animation and everything.
Special thanks to DJ_Steve, bogdi1988, and [email protected] for all your help!
Needed files:
system_orig.img
recovery_orig.img
boot_orig.img
[Edit]
For those users who need the original "flash_image.zip" file, I have uploaded it and it is available here.
PS: As an added note: **** you Koush! From all of the DS7 community!

Just what was needed
sent from somewhere

thanks but if you would of search there was a thread made already but i am sure the more the marrier

mooch777 said:
This may void your warranty, cost you your soul, and cause your spouse to leave you - ALL OF WHICH I AM NOT RESPONSIBLE FOR!
So, if it's because you screwed up flashing something, bricked your tablet with an OTA update after you installed CWM, or whatever, this is how you get it back to its outta-da-box shape!
(Please note, this assumes you have both installed CWM on your DS7 AND have installed the latest SDK on your computer).
1. Download the three attached .img files
2. Boot into CWM (since there really isn't anything else you can do)
3. In CWM, mount your SD card (so that you can view files via USB)
4. Plug in your DS7 to your computer, and copy the three .img files to the root of your SD card
5. Unmount your SD card, but leave the USB cable plugged into computer
6. Mount as many things as you can (ie system, boot, etc)
7. Open up command prompt, and navigate to your Android/tools folder, and type "adb devices"
8. There should be a number that shows up, or a "?" - either at this point is fine
9. Type the following command:
Code:
adb shell
a hash tag should show up that looks like this:
Code:
#~
10. Now, type the follow two commands one at a time:
Code:
flash_image /dev/block/mmcblk3p2 /sdcard/boot_orig.img
flash_image /dev/block/mmcblk3p1 /sdcard/recovery_orig.img
11. now, select "reboot" from DWM to reboot your device. It should boot and say something like "Formating Misc", and then it will reboot repeatedly
12. Use something small to push the RESET button on the DS7 (it's next to the SD card slot)
Your screen should go blank
13. Now, press and hold both the POWER button and the VOLUME - button until the screen comes on saying that the "fastboot downloader" is booted
14. Copy the three .img files into the your Android/tools folder
15. Now type the following code:
Code:
fastboot devices
16. There should be a number that shows up, or a "?" - either at this point is fine once again
17. Now type the following commands one at a time. The first will take a while to complete - this is okay:
Code:
fastboot flash system system_orig.img
fastboot flash recovery recovery_orig.img
fastboot flash boot boot_orig.img
Now, if after every command a "finished." is given, along with the total time each command took, you may continue.
18. You may now type the triumphant command:
Code:
fastboot reboot
Which will reboot your device.
Give it a little bit to boot, but when all is done you should see the original T-Mobile boot animation and everything.
Special thanks to DJ_Steve, bogdi1988, and [email protected] for all your help!
Needed files:
system_orig.img
recovery_orig.img
boot_orig.img
PS: As an added note: **** you Koush! From all of the DS7 community!
Click to expand...
Click to collapse
Thanked using the Thanks button and Thanks for your post!
Just to remind me a little as I may miss something,
why we **** Koush? It is not his fault that we stuck at CWM, or is it????

jiwengang said:
Thanked using the Thanks button and Thanks for your post!
Just to remind me a little as I may miss something,
why we **** Koush? It is not his fault that we stuck at CWM, or is it????
Click to expand...
Click to collapse
No its not his fault.. people shouldn't have tried to install the ota update while having cwr installed.. instead should have waited for a zip of the update that hell posted on behalf of did steve. As I have said if you have cwr you really can't get ota updates and install them the normal way. If the update was an update.zip you could flash through cwr but dell uses pgk files not zip.. so the only way to update is to wait for a dev to release a flashable cwr zip fike
Sent from my HTC Glacier using XDA App

The reason I made this post was so that we could have one concise, iD10t proof solution for people who were dumb like me. There's other posts, but you have to go back and forth to get the solution.
And the "Koush-****ing" was because of his unannounced abandonment of his projects, and those he was working with.
And thank you for the kind thanks!
Sent from my Dell Streak 7 using XDA App

mooch777 said:
The reason I made this post was so that we could have one concise, iD10t proof solution for people who were dumb like me. There's other posts, but you have to go back and forth to get the solution.
And the "Koush-****ing" was because of his unannounced abandonment of his projects, and those he was working with.
And thank you for the kind thanks!
Sent from my Dell Streak 7 using XDA App
Click to expand...
Click to collapse
Did he retire completely?

graffixnyc said:
Did he retire completely?
Click to expand...
Click to collapse
Think so!
From my CM7 UrBan Glacier

Hi,
I am the situation described above as I tried the OTA and am now stuck in CWR.
I followed the directions putting the 3 files on the root of my DS7 and am stuck at the following:
~ # flash_image /dev/block/mmcblk3p2 /sdcard/boot_orig.img
flash_image /dev/block/mmcblk3p2 /sdcard/boot_orig.img
failed with error: -1
~ #
Any ideas.....?
Thanks
SkI

Error 1
Error 1 means that the file is not where it is supposed to be. In this case on the SD card. Check and make sure that you have the right file, with the right file name on the root of your SD card and try again!
Good Luck

What does
"Error scanning partitions" means?...

jiwengang said:
What does
"Error scanning partitions" means?...
Click to expand...
Click to collapse
nvm, it is solved. don't use your own flash_image. use the stock one.

dj_ski69 said:
Hi,
I am the situation described above as I tried the OTA and am now stuck in CWR.
I followed the directions putting the 3 files on the root of my DS7 and am stuck at the following:
~ # flash_image /dev/block/mmcblk3p2 /sdcard/boot_orig.img
flash_image /dev/block/mmcblk3p2 /sdcard/boot_orig.img
failed with error: -1
~ #
Click to expand...
Click to collapse
+1 same here...
I find that at step 3... I mount sdcard... it shows on PC... I copy the 3 files to drive... unmount sdcard... mount everything else... run the other commands then get error... when I repeat the process I notice the files I copied are not there... ?
so I tried to adb push the files... they say they went thru correctly... but still get the same result as above...
any ideas?

dfspot said:
+1 same here...
I find that at step 3... I mount sdcard... it shows on PC... I copy the 3 files to drive... unmount sdcard... mount everything else... run the other commands then get error... when I repeat the process I notice the files I copied are not there... ?
so I tried to adb push the files... they say they went thru correctly... but still get the same result as above...
any ideas?
Click to expand...
Click to collapse
when you adp push to sdcard, make sure you mounted it already.
after that , it always help to adb shell ls /sdcard to make sure all files are there.
then you go to adb shell,
use the stock flash_image to flash. remember point to the path to flash_image
eg. flash_image /dev/block/mmcblk3p2 /sdcard/boot_orig.img

my understanding, if you don't mount sdcard, you canot see your sdcard FROM the tablet's perspective.
I mean, for table's flash_image to work, it has to be able to access its drive, in this case, is sdcard 's content.
so did you try leave sdcard mount and do the command above?

Hey Team...
can someone help me find the stock flash_image plz.....

I soooooooooooooo happy I was able to fix my Streak 7......yahooooooooo
I was missing the correct flash_image file which i took from the Galaxy Tab flash_image which is the same for the Dell and follow the direction and I now up again.......
Thanks guys

chris73 said:
I soooooooooooooo happy I was able to fix my Streak 7......yahooooooooo
I was missing the correct flash_image file which i took from the Galaxy Tab flash_image which is the same for the Dell and follow the direction and I now up again.......
Thanks guys
Click to expand...
Click to collapse
What command did you do.
Sent from my HTC Glacier using XDA App

chris73 said:
I soooooooooooooo happy I was able to fix my Streak 7......yahooooooooo
I was missing the correct flash_image file which i took from the Galaxy Tab flash_image which is the same for the Dell and follow the direction and I now up again.......
Thanks guys
Click to expand...
Click to collapse
do I need to push flash_image to my tablet?

If I remember correctly it needs to be in the nvflash folder
Sent from my Dell Streak 7 using XDA Premium App

[boot.img] obsolete please lock

Hi all. Quick notice:
Usual disclaimers apply.
This is an Unsecure boot.img I made for Android 4.2 on the Nexus 4.
Okay cool... but what is an insecure boot.img?
An insecure boot.img allows the device to be booted with permissions to be mounted as root. This is a way of being able to push SuperSU/Superuser.apk to /system/app and the Su Binaries to /bin
adb shell
su
mount -o remount,rw /system
exit​
See more here: External Link
_____________________________________________________________________________________________________________
To use this you must be unlocked, not familar with unlocking a Nexus device? Easy. In fastboot mode type "fastboot oem unlock" this wipes all data on the device (virtual sd included).
A nice article regarding this thread was published here: http://www.addictivetips.com/android/root-google-nexus-4-install-clockworkmod-recovery/
To boot this boot.img:
must be in the platform-tools folder in the android-sdk
must be in fastboot mode (power+vol-)
First use: fastboot boot "boot.img" (no ")
Why boot? I have not tested this image as I don't have a Nexus 4 as of yet.**
**Some users report flashing the image makes the phone in need of a fastboot stock flashing session, stick to booting for now.​
Thank you for helping!
-fkrone
-Ranguvar
-USSENTERNCC1701E
This is mainly for development purposes to obtain root on this device, it will be an easier process when a recovery is published and you can flash a su.zip. (see attached)
DOWNLOAD HERE: http://www.androidfilehost.com/?fid=9390169635556426389
Note, this is in Nexus 7 folder as Nexus 4 does not have its own atm.​
Click to expand...
Click to collapse
Please Lock!

Placeholder reserve

Harry GT-S5830 said:
Anyone able to get me recovery.fstab from recovery image and ill try make a cwm6 touch recovery for us.
I wouldn't be lazy and do it myself but PC is off
Sent from a phone
Click to expand...
Click to collapse
sgs2ext4 doesn't work on the recovery.img and the image isn't mountable by itself in Windows.
Too lazy to reboot into Linux, for now.. any other way to crack it open?

Ranguvar said:
sgs2ext4 doesn't work on the recovery.img and the image isn't mountable by itself in Windows.
Too lazy to reboot into Linux, for now.. any other way to crack it open?
Click to expand...
Click to collapse
Pull it apart in hex editor
Sent from my HTC Explorer A310e using xda app-developers app

Harry GT-S5830 said:
Anyone able to get me recovery.fstab from recovery image and ill try make a cwm6 touch recovery for us.
Sent from a phone
Click to expand...
Click to collapse
I've got the recovery.img, can I get the .fstab out without loop mounting? I don't have a linux machine set up right now.

USSENTERNCC1701E said:
I've got the recovery.img, can I get the .fstab out without loop mounting? I don't have a linux machine set up right now.
Click to expand...
Click to collapse
Old fashioned HxD
See here: http://forum.xda-developers.com/showthread.php?t=443994
I could probably do it without this, but it probably wouldn't mount data/media (what emulates the SD) so it would be relatively useless as that's where zips are
Also this might prove useful: http://forum.xda-developers.com/showthread.php?t=1494036 (requires Cygwin or Linux environment)

Harry GT-S5830 said:
Old fashioned HxD
See here: http://forum.xda-developers.com/showthread.php?t=443994
Click to expand...
Click to collapse
Hell, I wouldn't trust myself to rip it out with a hex editor. I'm setting up a VM right now, but I could just upload the recovery.img for you. I pulled it out of the stock image that google uploaded today.

USSENTERNCC1701E said:
Hell, I wouldn't trust myself to rip it out with a hex editor. I'm setting up a VM right now, but I could just upload the recovery.img for you. I pulled it out of the stock image that google uploaded today.
Click to expand...
Click to collapse
Cheers, that's where I had mine but I corrupted it :/ ill try pull it apart on the 600MHz wonder pico
Or perhaps not... 3.2" is too small for hex

Harry GT-S5830 said:
Cheers, that's where I had mine but I corrupted it :/ ill try pull it apart on the 600MHz wonder pico
Or perhaps not... 3.2" is too small for hex
Click to expand...
Click to collapse
Lol, I'm having a hell of a time getting Slax as a cooperative VM, might have to go all out with ubuntu

Got it!
Thanks for the tutorials. It was just fun to to something short after midnight (Germany). I was a little bit bored Would be nice if you can mention me in the people helped to create this recovery
http://www.mediafire.com/?mlv72phch1tgd5y Mediafire-Mirror

Dammit, beat me to it!
Serves me right for making dinner first
http://ompldr.org/vZ2ExYQ/recovery.fstab

Can i ask something as a future buyer of nexus 4 and older user of another phone...the fastboot is the "bootloader" (pink screen on my older phone) the state of the phone where i can connect it to my computer and see the folder containing the recovery.img boot.img...etc???

pikachukaki said:
Can i ask something as a future buyer of nexus 4 and older user of another phone...the fastboot is the "bootloader" (pink screen on my older phone) the state of the phone where i can connect it to my computer and see the folder containing the recovery.img boot.img...etc???
Click to expand...
Click to collapse
That's not quite how it works. These .img files we are talking about are pictures of the stock version of those paritions. Try reading this article for an explanation of Android partitioning.
There is also a great graphic here. The site is in Spanish, I haven't used Google to translate it, but the picture there is in English. Take your time with it, there's a lot of info there.

To get into Fastboot mode, do you just hold the volume down button while powering on? Never used a Nexus device before. Have been strictly on HTC up until now. I'm picking up my Nexus 4 in the morning and don't mind trying, as long as there's a way to undo anything in case something goes wrong.

Stryder5 said:
To get into Fastboot mode, do you just hold the volume down button while powering on? Never used a Nexus device before. Have been strictly on HTC up until now. I'm picking up my Nexus 4 in the morning and don't mind trying, as long as there's a way to undo anything in case something goes wrong.
Click to expand...
Click to collapse
Or you can enable adb and
Code:
adb reboot bootloader
The command
Code:
fastboot boot boot.img
is temporary. All it does is boot, one time only, the image you specify. Once you've mounted system as rw however, everything you do in /system before rebooting is permanent.

USSENTERNCC1701E said:
Or you can enable adb and
Code:
adb reboot bootloader
The command
Code:
fastboot boot boot.img
is temporary. All it does is boot, one time only, the image you specify. Once you've mounted system as rw however, everything you do in /system before rebooting is permanent.
Click to expand...
Click to collapse
So does adding the su binaries and the superuser apk give you permanent root after this then?
And exactly what binaries are needed to gain root? I've never gained root using that method before so am a little unfamiliar in this territory.

Stryder5 said:
So does adding the su binaries and the superuser apk give you permanent root after this then?
And exactly what binaries are needed to gain root? I've never gained root using that method before so am a little unfamiliar in this territory.
Click to expand...
Click to collapse
Woops, wrong thread.
Yes, if you push the su binary from a superuser flashable zip to /system/bin/ and chmod 0655, plus the superuser apk, you will have permanent root after.
Also, there is a recovery.img now, so you can test that out, if it works, flash it from fastboot, then flash a superuser zip from that recovery.

Thank you for getting it (recovery.fstab), looks like someone beat me to it though!
Sorry for late response I have to sleep as I'm in last school year
Ill cook up a recovery just to make your efforts worthwhile
It's in OP, its probably 99.9% the same as the other guys so i'm not going to make duplicate thread, use who evers recovery you wish.
____________________________________________________________________________________________________________________________________
Reason I say fastboot boot first is because it allows you to boot the image without permanently (well, unless you flash another over) flashing a partition without knowing it works.

Booted fine when I ran fastboot boot boot.img, but when I actually flashed it, it's giving me a boot loop now Booting back into fastboot shows secure boot still enabled. Any suggestions? Or do you have the original bootloader image?

Stryder5 said:
Booted fine when I ran fastboot boot boot.img, but when I actually flashed it, it's giving me a boot loop now Booting back into fastboot shows secure boot still enabled. Any suggestions? Or do you have the original bootloader image?
Click to expand...
Click to collapse
Not at my comp now or I'd upload it, bit of you rip open the fa Tory image from the Google servers you should find it
---------- Post added at 02:44 PM ---------- Previous post was at 02:43 PM ----------
On a side note, what possessed you to do that?

FireTV Boot Menu 1.0

This is a boot menu that will allow you to select if you want to boot a kernel or reboot in to recovery. I highly recommend everyone install this so you always have a way to boot in to recovery in case of problems. Just like recovery, it will sit at a black screen for an abnormal amount of time before showing. It's something like 20 seconds. But once it shows, you will have 5 seconds to make a selection. It defaults to booting the kernel, but you can use the up down keys to change the selection. Once it hits 0, it will do whatever option is selected. You can also hit enter and it will do that right away.
Right now, this is a very rough version 1.0. I plan to add some more features to it and would like to hear feedback from people to see what they think about it.
As usual, this WILL void your warranty and I am NOT responsible for anything you do with this. Installing it properly won't brick your Fire TV. Of course, this requires root and unlock.
Installation
Install CWM version 6.0.5.1.4 or higher. You MUST VERIFY CWM is at least 6.0.5.1.4 and it works BEFORE proceeding. You WILL BRICK your Fire TV if you are not properly unlocked, and verifying 6.0.5.1.4 or higher is working will do that.
For the following instructions, replace bootmenu.img with whatever filename you downloaded from this post, for example firetv-bootmenu-1.0.img. Copy bootmenu.img to /sdcard (via adb or whatever). Then from adb shell run this: DO NOT COPY PASTE THE WHOLE THING, DO EACH COMMAND ONE AT A TIME.
Code:
su
mount -o remount,rw /system
mkdir /system/boot
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/system/boot/boot.img
mount -o remount,ro /system
dd if=/sdcard/bootmenu.img of=/dev/block/platform/msm_sdcc.1/by-name/boot
Once you have verified it is working, you can replace /system/boot/boot.img with whatever kernel you want. Whether it be the overclocked kernel, or a Fedora kernel, or something else. And you never have to worry about bricking or getting back in to recovery.
Notes
Flashing anything that updates boot.img will cause you to loose bootmenu support. All pre-rooted roms 51.1.4.0 and lower will do this. Anything past 51.1.4.0 will only support booting their kernels through this method. When flashing 51.1.4.0 or lower when using bootmenu, you must repeat the entire bootmenu installation procedure because those roms will overwrite the bootmenu.
Changelog and Downloads:
Nov 15, 2014 - 1.0 (md5sum: a8a3c28baafe43f354d92e6cc8b392d3)

Hmm, tried this and didn't seem to do anything. It did sit at the black screen for a while but then no boot menu comes up. Tried rebooting normally and to recovery but either way no boot menu come up, just boots straight to recovery or to XBMC (I've set XBMC as my launcher).
I'm using your 6.0.5.1.4a recovery, bootloader partially unlocked etc.

AQKhanTheOne said:
Hmm, tried this and didn't seem to do anything. It did sit at the black screen for a while but then no boot menu comes up. Tried rebooting normally and to recovery but either way no boot menu come up, just boots straight to recovery or to XBMC (I've set XBMC as my launcher).
I'm using your 6.0.5.1.4a recovery, bootloader partially unlocked etc.
Click to expand...
Click to collapse
It's completely blank? I timed from 'adb reboot' to when the menu showed up and it was 24 seconds. Then you should see *something* on the screen, and then 5 seconds later it should reboot the firetv and then the kernel should start loading. 25 seconds after adb reboot, try hitting the down arrow and then waiting a few seconds. It should boot into recovery. Does that work? Also, are you using overscan in recovery?

Yes completely blank. Actually it only sat at the blank/black screen the first time it rebooted after the install. After that each reboot to either recovery or to XBMC does not result in the long blank screen at all. Though there is the briefest lightening of the screen right before the white amazon logo comes up. And no, I'm not using overscan. The result of the install is below if that helps. It's likely I've made a mistake.
Code:
[email protected]:/ $ su
mount -o remount,rw /system
mkdir /system/boot
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/system/boot/boot.img
smount -o remount,ro /system
u
dd if=/sdcard/bootmenu.img of=/dev/block/platform/msm_sdcc.1/by-name/bootmount -
o remount,rw /system
mkdir /system/boot
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/system/boot/boot.img
mount -o remount,ro /system
[email protected]:/ # mount -o remount,rw /system
[email protected]:/ # mkdir /system/boot
dcc.1/by-name/boot of=/system/boot/boot.img <
20480+0 records in
20480+0 records out
10485760 bytes transferred in 1.939 secs (5407818 bytes/sec)
[email protected]:/ # mount -o remount,ro /system
[email protected]:/ # exit

AQKhanTheOne said:
Yes completely blank. Actually it only sat at the blank/black screen the first time it rebooted after the install. After that each reboot to either recovery or to XBMC does not result in the long blank screen at all. Though there is the briefest lightening of the screen right before the white amazon logo comes up.
Click to expand...
Click to collapse
Well it has no effect on recovery, just the main system. It should do it every time. Not quite sure why you aren't seeing it though.

rbox said:
Well it has no effect on recovery, just the main system. It should do it every time. Not quite sure why you aren't seeing it though.
Click to expand...
Click to collapse
I did rename the downloaded file to bootmenu.img to avoid having to change the name in the shell command. Don't know if that makes a difference.

AQKhanTheOne said:
I did rename the downloaded file to bootmenu.img to avoid having to change the name in the shell command. Don't know if that makes a difference.
Click to expand...
Click to collapse
No, the name doesn't matter. Try this version. It should have a solid blue background to start and then if you hit the down arrow it'll switch to red. Blue will boot the kernel, red will boot recovery.
EDIT: Okay. I reread your post and saw you included the output from the shell. Don't copy paste it all at once. Do the commands one at a time.

rbox said:
No, the name doesn't matter. Try this version. It should have a solid blue background to start and then if you hit the down arrow it'll switch to red. Blue will boot the kernel, red will boot recovery.
EDIT: Okay. I reread your post and saw you included the output from the shell. Don't copy paste it all at once. Do the commands one at a time.
Click to expand...
Click to collapse
Okay, that did the trick! Now I get the colorful Rbox's Boot Menu with two options, Boot Kernal and Boot to recovery.
Thanks as always for all your great work!

Well this looks like its going to be handy.
In with no issues Rbox and countdown
Idea: Press and hold key on the remote or keyboard to get to boot-menu (unsure if this can be done)
Press nothing boots to FTV
Thanks

Works perfect here, the remote doesnt work tho right? need to use a keyboard?

nhumber said:
Works perfect here, the remote doesnt work tho right? need to use a keyboard?
Click to expand...
Click to collapse
Yeah. Just like recovery it needs the keyboard.

works great , thank you for all your efforts

rbox said:
Yeah. Just like recovery it needs the keyboard.
Click to expand...
Click to collapse
Thanks a lot rbox. This works as described though I am not sure at this point what to do with it. I just installed it as you said it would be useful

heyredy141 said:
Thanks a lot rbox. This works as described though I am not sure at this point what to do with it. I just installed it as you said it would be useful
Click to expand...
Click to collapse
My main goal with it was to always be able to get to recovery. Secondary goal is to easily use alternate kernels without risk of not being able to get back to recovery. Which really gets back to the main goal. A side effect is that people can load fedora kernels easy without having to screw around with their partitions.

Im trying to wrap my head around how this works.. I get what we are doing, but wont flashing something (ie anything with a boot.img) with CWM overwrite the bootmenu?

mastafunk said:
Im trying to wrap my head around how this works.. I get what we are doing, but wont flashing something (ie anything with a boot.img) with CWM overwrite the bootmenu?
Click to expand...
Click to collapse
That's very much correct. I think I'm going to make all my future prerooted images put their boot.img in /system/boot and not flash it to the boot partition.

rbox said:
That's very much correct. I think I'm going to make all my future prerooted images put their boot.img in /system/boot and not flash it to the boot partition.
Click to expand...
Click to collapse
Thanks for your quick reply. Glad I'm on the same page .. I'm working on a custom ROM and was thinking that was something i would address the same way but then thought for a sec maybe you had moded the newer cwm to just do that instead of flashing the boot.img.
EDIT
might want to put some more thought into doing that for the newer pre-roots as someone may flash back to an older one then flash forward and screw themselves.. maybe include some sort of checking in cwm? And maybe include a warning in the OP if they flash any pre-root they loose the safetynet of the bootmenu.img until applied again.

Worked great for me. Thanks rbox for all of the support you've given this device!

so I ran the first commands and it looks like I have boot.img in /system:
[email protected]:/system/boot # ls -l
ls -l
-rw------- root root 1675264 2014-11-21 18:19 boot.img
My concern is that I don't have any free space in system at all:
/system 756M 756M 0K 4096
is this normal to be this tight on the 51.1.4.0 prerooted rom?
I have even removed WhisperplayCore.apk when I was trying to get the chromecast receiver app working (sadly looks like that's fruitless at this point, but that's a separate topic)
I haven't copied the bootmenu image over just incase there is an issue with that boot.img that may not have been a full copy or something. Just trying to be extra careful.

One tiny suggestion: Change the wording in your post "When flashing 51.1.4.0 or lower when using bootmenu, you must reflash bootmenu." to "When flashing 51.1.4.0 or lower when using bootmenu, you must repeat the entire bootmenu installation procedure."
The reason: After setting up bootmenu on my test device, I realized it was on 51.1.3.0 when I thought it was on 51.1.4.0. I installed 51.1.4.0 then re-read your note to "reflash bootmenu". I thought "ah simple, i'll just re-run the last dd step since everything is still in place." Of course, I forgot that installing 51.1.4.0 wiped out /system/boot/boot.img so when I put bootmenu in place I no longer had a stock boot image on the box. It was a simple fix (I just used bootmenu to get into recovery and reinstalled 51.1.4.0), but probably best to be explicit with the above sentence.

[Q] Repacking Boot Image for P7-L00

Hi,
I am trying to build a custom boot image to get rid of the immutable files of my P7-L00.
Specifically I haved done this : At a specific point in the boot process the rc scripts execute the set_immutable command with a 1 parameters that sets the immutable bits in all the files mentioned in the set_immutable.list file. If this command is changed to a 0 it clears the immutable bit for all the files. I have buit the custom ramfs necesary for this but when I repack the boot image it will not boot.
I am using the following command for mkbootimg ....
mkbootimg --kernel mykernel.img --ramdisk ramdisk.cpio.gz --ramdisk_offset 0x04000000 --base 0x07000000 --cmdline "k3v2mem k3v2_ion=1 vmalloc=448M maxcpus=4 initcall_debug=n" -o newimg.img
The resulting first page looks ok, it has the same offsets as my original working boot image, but as I mentioned before, it does not boot, but just cycles back to fastboot mode after about 1 minute.
Any help will be appreciated,
Thanks

The most probable that there's a problem with permissions.
Make
Code:
chown 0:0 init.rc
chmod 750 init.rc
before packing ramdisk.

Kostyan_nsk said:
The most probable that there's a problem with permissions.
Make
Code:
chown 0:0 init.rc
chmod 750 init.rc
before packing ramdisk.
Click to expand...
Click to collapse
Thanks a lot ! .... I had not checked the user/groups for the extracted files ...

gguemez said:
Hi,
I am trying to build a custom boot image to get rid of the immutable files of my P7-L00.
Specifically I haved done this : At a specific point in the boot process the rc scripts execute the set_immutable command with a 1 parameters that sets the immutable bits in all the files mentioned in the set_immutable.list file. If this command is changed to a 0 it clears the immutable bit for all the files. I have buit the custom ramfs necesary for this but when I repack the boot image it will not boot.
I am using the following command for mkbootimg ....
mkbootimg --kernel mykernel.img --ramdisk ramdisk.cpio.gz --ramdisk_offset 0x04000000 --base 0x07000000 --cmdline "k3v2mem k3v2_ion=1 vmalloc=448M maxcpus=4 initcall_debug=n" -o newimg.img
The resulting first page looks ok, it has the same offsets as my original working boot image, but as I mentioned before, it does not boot, but just cycles back to fastboot mode after about 1 minute.
Any help will be appreciated,
Thanks
Click to expand...
Click to collapse
I suggest, use kitchen.

gguemez said:
Hi,
I am trying to build a custom boot image to get rid of the immutable files of my P7-L00.
Specifically I haved done this : At a specific point in the boot process the rc scripts execute the set_immutable command with a 1 parameters that sets the immutable bits in all the files mentioned in the set_immutable.list file. If this command is changed to a 0 it clears the immutable bit for all the files. I have buit the custom ramfs necesary for this but when I repack the boot image it will not boot.
I am using the following command for mkbootimg ....
mkbootimg --kernel mykernel.img --ramdisk ramdisk.cpio.gz --ramdisk_offset 0x04000000 --base 0x07000000 --cmdline "k3v2mem k3v2_ion=1 vmalloc=448M maxcpus=4 initcall_debug=n" -o newimg.img
The resulting first page looks ok, it has the same offsets as my original working boot image, but as I mentioned before, it does not boot, but just cycles back to fastboot mode after about 1 minute.
Any help will be appreciated,
Thanks
Click to expand...
Click to collapse
You are correct in saying that modifying the setimmutable binary flag from 1 to 0 in the boot image solves the set_immutable.list problem referred to many times in various posts in this forum..
I have a P7-L07 emui2.3 B125 and a P7-L10 emui3.0 B609. I had no trouble modifying the boot.img for the L07 using
linux-kernelkitchen-0.002 under xubuntu. The L10 is a different story but the main problem is faulty flash memory.
At any rate, you don't really need to worry about the boot.img file at all. A simple and easy work around is to replace the file set_immutable.list with another empty file of the same name. This works quite well on my L10. I used the file manager FX to achieve this. As long as you have root access and can change file permissions correctly this method will work for you.

arthios said:
You are correct in saying that modifying the setimmutable binary flag from 1 to 0 in the boot image solves the set_immutable.list problem referred to many times in various posts in this forum..
I have a P7-L07 emui2.3 B125 and a P7-L10 emui3.0 B609. I had no trouble modifying the boot.img for the L07 using
linux-kernelkitchen-0.002 under xubuntu. The L10 is a different story but the main problem is faulty flash memory.
At any rate, you don't really need to worry about the boot.img file at all. A simple and easy work around is to replace the file set_immutable.list with another empty file of the same name. This works quite well on my L10. I used the file manager FX to achieve this. As long as you have root access and can change file permissions correctly this method will work for you.
Click to expand...
Click to collapse
Thank your for the info. In the P7-L00 with a KingUser Root I could not change the set_immutable.list to anything. Any attempt to modify the file, replace or change the permissions would fail, since the immutable bit was set.
Having fixed the problem I mentioned above I now find myself with the situation that if I change some, I can't say all files, in the system directory the phone reboot immediately. I dont know if this is due to the "partial" root some people say kinguser provides or to some other issue.
I will keep playing around, thanks for the help.

gguemez said:
Thank your for the info. In the P7-L00 with a KingUser Root I could not change the set_immutable.list to anything. Any attempt to modify the file, replace or change the permissions would fail, since the immutable bit was set.
Having fixed the problem I mentioned above I now find myself with the situation that if I change some, I can't say all files, in the system directory the phone reboot immediately. I dont know if this is due to the "partial" root some people say kinguser provides or to some other issue.
I will keep playing around, thanks for the help.
Click to expand...
Click to collapse
changing the 1 to 0 of set_immutable in rc won't work. i already tried that thing. i used 609 boot.img, unpack and repack it successfully but it wont work.

majcomtech said:
changing the 1 to 0 of set_immutable in rc won't work. i already tried that thing. i used 609 boot.img, unpack and repack it successfully but it wont work.
Click to expand...
Click to collapse
Thanks, do you also get the same effect of an immediate reboot when you modify system files? That is what I am really after, since I can't change anything I can't even update the SU or change any files ...

gguemez said:
Thanks, do you also get the same effect of an immediate reboot when you modify system files? That is what I am really after, since I can't change anything I can't even update the SU or change any files ...
Click to expand...
Click to collapse
if you want full root, i already made tut for that. http://forum.xda-developers.com/ascend-p7/general/rooted-p7-l10-609-t3003605

majcomtech said:
changing the 1 to 0 of set_immutable in rc won't work. i already tried that thing. i used 609 boot.img, unpack and repack it successfully but it wont work.
Click to expand...
Click to collapse
Thanks, I have tried this but in my case it has not worked. Everytime I reboot the phone the files are all back, as if there is a backup partition or something. I an now trying to do this via a UPDATE with CWM...
Thanks again.

gguemez said:
Thanks, I have tried this but in my case it has not worked. Everytime I reboot the phone the files are all back, as if there is a backup partition or something. I an now trying to do this via a UPDATE with CWM...
Thanks again.
Click to expand...
Click to collapse
I expect you are quite fed up by now and I offer my commiserations. There may be however be another solution to your problem. Have you considered downloading a custom ROM for your L00 created (say) by KangVIP or Killprocess, and then extracting the boot image from the zip file and flashing that? These boot images have the set_immutable flag set to 0. As I recall, the ROMs from KangVIP are password protected so a Killprocess ROM or one from someone else might be better. If you do decide to try this out, make sure the build number of the downloaded ROM is similar to yours. The boot images differ between emui2.3 and emui3.0. Good luck!

gguemez said:
Thanks, I have tried this but in my case it has not worked. Everytime I reboot the phone the files are all back, as if there is a backup partition or something.
Click to expand...
Click to collapse
Seems like you have locked bootloader.

Kostyan_nsk said:
Seems like you have locked bootloader.
Click to expand...
Click to collapse
No, the bootloader is unlocked. I can change the boot partition at will, I have many times letf it unbootable and restored it with no problem. I will try to do something via the recovery parition but, the only one I have found that worked in my phone, always gives me errors when running my scripts (so I am obviously doing something wrong).
I got to the point of sending a script that says ... ui_print ("Hello World"); ... but that gives me an error too!
I will keep trying to figure this out, thanks for your help.
Guillermo

What value has "fblock=" parameter in "/proc/cmdline"?