I flashed 2.3.4 pudding preroot and looked through all my apps and do not have root and/or root permissions. I installed superuser with apk (of course that wouldnt work) but the rom itself is supposed to come packed with SU. Any ideas? I didnt clean wipe my phone during the flash and I am still running phone with all old apps/unchanged features from before the flash.
Is there anything I missed to get Root permissions onto phone? Ie running code or something else?
Does no one really know... ? I mean wow. :x
eval- said:
Hi guys.. here is a useful little /preinstall for you (attached)
Put phone in fastboot mode, then:
Code:
fastboot flash preinstall preinstall.img
fastboot reboot
(older versions maybe need "fastboot -i 0x22b8")
after fastboot & reboot, type in adb ("adb shell") or terminal emulator, exactly:
Code:
/preinstall/dosu
/bin/mount -o remount,rw /system
cp /preinstall/su /system/bin/
chmod 6755 /system/bin/su
PATH=/system/bin:$PATH pm install /preinstall/Superuser.apk
The last step is optional (and next-to-last *should* be unnecessary), as you can install Superuser however you like. In fact, if you've installed it, simply typing "/preinstall/su" is another way to root, and you could then mount /system read-write and copy it into /system/bin.
Many thanks to Brandon & The2d for brainstorming this out in a crazy "there's no way it could be possible" rooting session. There were a lot of harder ways... who knew we'd be so lucky! And thanks to Edgan for the great "dosu" =)
You can find fastboot here: http://forum.xda-developers.com/showthread.php?t=1138092
And the preinstall.img file here: http://forum.xda-developers.com/attachment.php?attachmentid=652327&d=1310460219
Click to expand...
Click to collapse
IMO, this is the easiest way to root. If you get an error with the /preinstall/dosu command, just keep going through with the rest like normal and it should work.
If your not bent on having stock gingerbread, then flash Piecrust or alien 3. they are prerooted and optimized.
Alien 3 would be your best bet. Just flash the alien 3 rom and your set. It is stock for the most part and removes some un-necessary bloat which you can get back from the bloat.zip if you want. If you want a new look then flash the alien 3 theme as well. WAAAAY better than stock theme IMO. Not overly flashy and gives the device a up to date look. Motorola needs to work on there GUI a little harder.
Stephen Who said:
I flashed 2.3.4 pudding preroot and looked through all my apps and do not have root and/or root permissions. I installed superuser with apk (of course that wouldnt work) but the rom itself is supposed to come packed with SU. Any ideas? I didnt clean wipe my phone during the flash and I am still running phone with all old apps/unchanged features from before the flash.
Is there anything I missed to get Root permissions onto phone? Ie running code or something else?
Click to expand...
Click to collapse
I had the same issue doing my bros phone, got fed up and put alien on it, then he came back and wanted the alien theme lol. Superuser beta 3 pre-installed into ROM
i love you
Originally Posted by eval- View Post
Hi guys.. here is a useful little /preinstall for you (attached)
Put phone in fastboot mode, then:
Code:
fastboot flash preinstall preinstall.img
fastboot reboot
(older versions maybe need "fastboot -i 0x22b8")
after fastboot & reboot, type in adb ("adb shell") or terminal emulator, exactly:
Code:
/preinstall/dosu
/bin/mount -o remount,rw /system
cp /preinstall/su /system/bin/
chmod 6755 /system/bin/su
PATH=/system/bin:$PATH pm install /preinstall/Superuser.apk
The last step is optional (and next-to-last *should* be unnecessary), as you can install Superuser however you like. In fact, if you've installed it, simply typing "/preinstall/su" is another way to root, and you could then mount /system read-write and copy it into /system/bin.
Many thanks to Brandon & The2d for brainstorming this out in a crazy "there's no way it could be possible" rooting session. There were a lot of harder ways... who knew we'd be so lucky! And thanks to Edgan for the great "dosu" =)
You can find fastboot here: http://forum.xda-developers.com/show....php?t=1138092
And the preinstall.img file here: http://forum.xda-developers.com/atta...7&d=1310460219
this worked for me i have been looking up 100 different things thanks so much:laugh::laugh::laugh::laugh:
Related
I have a moto droid, rooted mine the normal way with update.zip and adb but my mom has a eris and wants wifi tether and a faster rom with working youtube app
Can i just download the rooting file update her phone then download rom manager to install recovery image? i dont feel like setting up adb on her computer. i want to flash it to the newest ota rooted rom that is on this site.
bL33d said:
I have a moto droid, rooted mine the normal way with update.zip and adb but my mom has a eris and wants wifi tether and a faster rom with working youtube app
Can i just download the rooting file update her phone then download rom manager to install recovery image? i dont feel like setting up adb on her computer. i want to flash it to the newest ota rooted rom that is on this site.
Click to expand...
Click to collapse
Sure, put your sdcard in your computer, or connect it to your computer with the USB cable and mount the sdcard. Download the PB00IMG.zip with root, flash_image, and recovery.img. Shut the phone down, and then do the VOL DOWN+Power ON to flash PB00IMG to the phone. Once done flashing, go in to the android market and download a terminal emulator. Type these commands:
su
after su, phone should change from sh-3.2$ to sh 3.2#
mount -o rw,remount /dev/block/mtdblock3 /system
cp /sdcard/flash_image /system/bin
chmod 755 /system/bin/flash_image
flash_image recovery /sdcard/recovery.img
If you do that, it should allow you to do it without adb on the computer. Just remember to type the 5 commands in the terminal emulator.
I just talked to devs and they told me that It can be done, Just download the rom Manager and install the recovery from there without using adb at all.
You just have to install the root rom first, then you should be able to use the rom manager to install the recovery img, which in my opinion the clockworkmod recovery is a lot better than the RA recovery which is listed in the rom.
thanks guys seemed like it was doable but wanted to double check here first.
Okay, I seriously had enough of people saying is this AmonRa or whatsoever. I Derived both files from here and decided to make those instructions/script easier for you to understand. This recovery covers most basic needs (wipe,backup,restore,flash etc.) , so if you are going to keep complaining about my thread title/contents, I'll be glad to remove this thread and leave you people to figure out how to install custom recovery
WARNING : Only for P500....
Many people tried installing custom recovery, but ended up hard resetting your phone wondering WTF went wrong right? Like you people I ended up resetting 4 times =.=ll so..now I've succeeded, I'm just gonna share how its done!
==============================================================
Files Needed :
recovery-RA-thunderg-2.2.1-GNM.img.zip
flash_image.zip
(Both downloadable from below)
==============================================================
The files preparation process:
1)Download both of them into your pc
2)extract both of them out.
3)Get the contents of both extracted folders and copy into the root of your sd card.
============================================================
The Actual Installation Process
1)Use either adb shell or Terminal Emulator(from the market) to install it
2)Enter the script below.
Code:
1.su
2.mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
3.cat /sdcard/flash_image > /system/bin/flash_image
4.chmod 755 /system/bin/flash_image
5.mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
6.flash_image recovery /sdcard/recovery-RA-thunderg-2.2.1-GNM.img
3)If you have error for step 5. stating /system/etc/install-recovery.sh : file not found, do not panic, just move on to the next step.
4)If you have error for flash_image : 1:")" unexpected, make sure flash_image is a file, not an folder.
============================================================
Testing it Out.
1)If you only had the error for step 5 from all of the above and nothing else. Pray hard and type in : reboot recovery into your adb shell or terminal emulator.
2)If you had errors from steps other from step 5, go look at it again and think. DO NOT TAKE THE RISK!
3)I'm still a newbie coder so this thread may not be good but I derived the files from here but I wanted to make it less confusing for you people so if there is anything missing/wrong/you don't know/you wanna ask, just post a reply!
=============================================================
Basic Key mappings for Custom Recovery:
menu > select
vol+ > up
vol- > down
back > back
Rest can be found here
FOR PEOPLE WHO THINKS THIS IS STOCK RECOVERY, IT IS NOT. IT ALLOWS FLASHING.
Nice Thread .....nut der r many threads same ...rite??? but i liked....i voted u !!1
Thaannkksss.....There are many threads, but most of which give confusing instructions that clearly do not work with idiots like me XP
amosng1 said:
Thaannkksss.....There are many threads, but most of which give confusing instructions that clearly do not work with idiots like me XP
Click to expand...
Click to collapse
rite.....depends upon person whos reading...
virusshah1997 said:
rite.....depends upon person whos reading...
Click to expand...
Click to collapse
True, thats preettty much why it has a unique title
Am running on stock 2.2.2 and rooted using GingerBreak. Whenever I try entering commands on Terminal Emulator it says Access Denied. Help!
bindaasathar said:
Am running on stock 2.2.2 and rooted using GingerBreak. Whenever I try entering commands on Terminal Emulator it says Access Denied. Help!
Click to expand...
Click to collapse
Hmm? Give more specific details. But try and see if you have root. If you have root but still says Access Denied, try typing su first?
amosng1 said:
Hmm? Give more specific details. But try and see if you have root. If you have root but still says Access Denied, try typing su first?
Click to expand...
Click to collapse
it says with I type in su the terminal emulator. My device is perfectly rooted since all other applications which require root access seem to work.
Thanks this is such a good info!
bindaasathar said:
it says with I type in su the terminal emulator. My device is perfectly rooted since all other applications which require root access seem to work.
Click to expand...
Click to collapse
No offense but what is "it says with i type...."
I kinda do not understand.
daniequy said:
Thanks this is such a good info!
Click to expand...
Click to collapse
Thank you.....maybe you could do me a favor and press that thank button
amosng1 said:
No offense but what is "it says with i type...."
I kinda do not understand.
Click to expand...
Click to collapse
If you had Superuser, did you allow terminal emulator to access root functions?
-a thought i have thought-
The sooner you reply, the faster i can get you a answer!
I got the following error in the last step 6:
Code:
# flash_image recovery /sdcard/recovery-RA-thunderg-2.2.1-GNM.img
flash_image recovery /sdcard/recovery-RA-thunderg-2.2.1-GNM.img
mtd: read error at 0x00000000 (Out of memory)
mtd: read error at 0x00020000 (Out of memory)
mtd: read error at 0x00040000 (Out of memory)
I'm going to try to search for this issue but meanwhile if anyone knows what to do about this please let me know. I'll update a link here in case I find the solution.
Edit: This problem is fixed!!
If you get the out of memory error you need to type:
Code:
mount -o remount,ro -t yaffs2 /dev/block/mtdblock1 /system
Reference: I got this from this link here in section 3.
amosng1, If you think other people might also experience the same issue then it would be great if you could precede Step 6 with the code above.
This worked perfectly fine for my LGP500 model! I booted into recovery.
ROM: Stock GB 2.3.3.
Kernel: Stock kernel (will update this detail on robooting my phone)
Rooted: Using SuperOneClick method with npeuter
Thanks a lot for your guide matey!
I, have already made a, thread for recovery with terminal emulater
http://forum.xda-developers.com/showthread.php?t=2003080
androidisfuture said:
I, have already made a, thread for recovery with terminal emulater
http://forum.xda-developers.com/showthread.php?t=2003080
Click to expand...
Click to collapse
Okay, I had used the adb shell actually. I've been more comfortable with this. Maybe I'll try out the terminal one sometime too.
Sent from my LG-P500 using xda app-developers app
Sorry, after each command what key i press to work? Or after step, how to work this command?
1.su
2.mount-o remount, rw-t YAFFS2 / dev/block/mtdblock1 / sistema
3.cat / sdcard / flash_image> / system / bin / flash_image
4.chmod 755 / system / bin / flash_image
5.mv / sistema / etc / install-recovery.sh / sistema / etc / install-recovery.sh.bak
6.flash_image recuperação / sdcard/recovery-RA-thunderg-2.2.1-GNM.img
One of the easiest how-to's I have come across
amosng1 said:
Okay, I seriously had enough of people saying is this AmonRa or whatsoever. I Derived both files from here and decided to make those instructions/script easier for you to understand. This recovery covers most basic needs (wipe,backup,restore,flash etc.) , so if you are going to keep complaining about my thread title/contents, I'll be glad to remove this thread and leave you people to figure out how to install custom recovery
WARNING : Only for P500....
Many people tried installing custom recovery, but ended up hard resetting your phone wondering WTF went wrong right? Like you people I ended up resetting 4 times =.=ll so..now I've succeeded, I'm just gonna share how its done!
==============================================================
Files Needed :
recovery-RA-thunderg-2.2.1-GNM.img.zip
flash_image.zip
(Both downloadable from below)
==============================================================
The files preparation process:
1)Download both of them into your pc
2)extract both of them out.
3)Get the contents of both extracted folders and copy into the root of your sd card.
============================================================
The Actual Installation Process
1)Use either adb shell or Terminal Emulator(from the market) to install it
2)Enter the script below.
Code:
1.su
2.mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
3.cat /sdcard/flash_image > /system/bin/flash_image
4.chmod 755 /system/bin/flash_image
5.mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
6.flash_image recovery /sdcard/recovery-RA-thunderg-2.2.1-GNM.img
3)If you have error for step 5. stating /system/etc/install-recovery.sh : file not found, do not panic, just move on to the next step.
4)If you have error for flash_image : 1:")" unexpected, make sure flash_image is a file, not an folder.
============================================================
Testing it Out.
1)If you only had the error for step 5 from all of the above and nothing else. Pray hard and type in : reboot recovery into your adb shell or terminal emulator.
2)If you had errors from steps other from step 5, go look at it again and think. DO NOT TAKE THE RISK!
3)I'm still a newbie coder so this thread may not be good but I derived the files from here but I wanted to make it less confusing for you people so if there is anything missing/wrong/you don't know/you wanna ask, just post a reply!
=============================================================
Basic Key mappings for Custom Recovery:
menu > select
vol+ > up
vol- > down
back > back
Rest can be found here
FOR PEOPLE WHO THINKS THIS IS STOCK RECOVERY, IT IS NOT. IT ALLOWS FLASHING.
Click to expand...
Click to collapse
Worked perfectly had only the step 5 error 'no such file or directory' everything else worked and I was able to boot into the custom recovery no problem. Thanks
Can someone knowledgeable please submit a detailed post, which instructs how to remove any files added during the Root Process, as well as any other file permission changes or modifications of any other type?
I see many half assed posts in these forums made by unqualified members, which are nothing but a waste of time and clutter this great resource. I would appreciate it if this post could be addressed by those who truly understand this process.
The file that was used to Root the SCH-i905 from Verizon was the one attached to this post.
Thanks in advance! This could be a great learning tool if answered properly.
Can some one please respond? Or is it that everyone is too scared to post helpful information?
Well, since no one was of any assistance, I was forced to piece together information and come to an understanding of how this works, and how to fully reverse what was done by this Root Update.
To begin, I would like to mention, that removing Superuser.apk from the /system/app folder, along with 'su' from the /system/bin folder, will negate your Root Access, and put you back to your default levels of access. This will prevent Mobile Device Management Solutions, such as AirWatch, Zenprise, or MobileIron from detecting your device as being compromised.
I was not successful in removing these two files via the ADB shell, however I was successful when using a Terminal Emulator App on the Device itself.
1.) I began by installing a free Terminal Emulator from the Android Market.
2.) Launched the Terminal Emulator and typed 'su' , then pressed Enter to gain Root Shell Privileges.
3.) From the Root Shell, I typed the following commands to remount the '/System' Directory to gain Read/Write Access.
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
4.) I typed the following commands to remove 'Superuser.apk' and 'su'.
cd /system/app
rm Superuser.apk
cd /system/bin
rm su
5.) Type the following command to remount the '/System' Directory back to Read Only.
mount -o ro,remount -t yaffs2 /dev/block/mtdblock3 /system
6.) Sync your device with Google under Settings / Accounts & Sync.
7.) Reboot your device, and you are good to go.
It might be a good practice to perform a Factory Reset on your device after doing this, however this is not completely necessary. I tested the Air-Watch Agent installation after performing the procedure mentioned above, and the Air-Watch console no longer detected my device as being compromised.
I will add that on my sch-i905 I found the bin directory under system not under system/app. For me, replacing cd /system/app/bin with cd /system/bin did the trick but the rest worked a treat - thanks for the post!
Thanks for pointing out my typo. I corrected the path in my Post.
Thanks for this.
Does this restore the stock recovery that was replaced with Clockwork when the kernel.zip and recovery.zip files were flashed to obtain root? I do not totally understand the relationship between Superuser and CWR. I found a reference to a flashable stock recovery in post 14 here http://forum.xda-developers.com/showthread.php?t=1205639&page=2 , but I'm unclear on the instructions.
I'm trying to understand how, if possible, to return my VZW LTE Tab to out-of-the-box stock, if desired.
Rooted: Droid Incredible / Droid X / Thunderbolt / 3G-4G Xoom / Galaxy Tab 10.1 LTE
I have the Superuser icon showing up in my apps folder, but I don't appear to have root access. I can't su in the terminal emulator nor can I load apps that require root access. I also tried removing the Superuser.apk via a file manager with no luck.
Any idea how to remove this thing if I don't actually have root access?
---------- Post added at 09:25 PM ---------- Previous post was at 09:10 PM ----------
OK, I rooted again and fixed whatever was broken. Then I was able to apply these commands to unroot the device.
Thank you!
tbcpn said:
Thanks for this.
Does this restore the stock recovery that was replaced with Clockwork when the kernel.zip and recovery.zip files were flashed to obtain root? I do not totally understand the relationship between Superuser and CWR. I found a reference to a flashable stock recovery in post 14 here http://forum.xda-developers.com/showthread.php?t=1205639&page=2 , but I'm unclear on the instructions.
I'm trying to understand how, if possible, to return my VZW LTE Tab to out-of-the-box stock, if desired.
Rooted: Droid Incredible / Droid X / Thunderbolt / 3G-4G Xoom / Galaxy Tab 10.1 LTE
Click to expand...
Click to collapse
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
Stock Recovery isn't required to Root the device. However, if you wish to install CWM via ROM Manager from the Android Market, Root Permissions are required.
If you use an ODIN Flash of CWM, there is no need for Root Permissions because you are flashing via ODIN.
The stock recovery zip file that you referenced in the other post should be fine.
Just use ODIN to Flash back to Stock Recovery and use the process that I mentioned to remove Root Permissions and Super User, and you should be all set to return your device after a Factory Wipe.
Cheers!
~Scott~ said:
I have the Superuser icon showing up in my apps folder, but I don't appear to have root access. I can't su in the terminal emulator nor can I load apps that require root access. I also tried removing the Superuser.apk via a file manager with no luck.
Any idea how to remove this thing if I don't actually have root access?
---------- Post added at 09:25 PM ---------- Previous post was at 09:10 PM ----------
OK, I rooted again and fixed whatever was broken. Then I was able to apply these commands to unroot the device.
Thank you!
Click to expand...
Click to collapse
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
Scott,
I'm sorry for just seeing your post. I'm sure that you figured it out by now. You need to gain Root Access to your device again to remove Super User. You are in a Catch22.
If you are using an SCH-I905, Root your device, then download Script Manager from the Android Market.
Run this very simple Bash Script that I wrote to remove Root and Super User.
Paste this into notepad and save it as Unroot.sh then run with Script Manager.
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/app
rm Superuser.apk
cd /system/bin
rm su
mount -o ro,remount -t yaffs2 /dev/block/mtdblock3 /system
Be sure to run the Script as Root from within Script Manager. The app will kind of freeze up as soon as it runs, which is normal. This will certainly take care of your problem.
Thanks for your post of stockrec in a different post. You saved me a month ago with that one.
Cheers!
Will Samsung know if I rooted my GT 10.1 LTE after using these commands, and sending in for warranty?
Does anyone know how often airwatch checks for the root? anyway to bypass the checks?
Is this the same for the US Cellular 4G Tablet? I have been reading and all that I have found was WiFi only files. Which if I were to root with those I lose the 4G radio.
Perfect.. Just what I need. Thanks
Hello, I got the ATRIX on Bell and I tried rooting it yesterday...I don't know if it worked but when I installed Superuser I couldn't access any applications from it. So I took it as if it didn't work and Factory Reset everything (I haven't installed any ROMS or anything else) I followed these steps I found on the AndroidForums
#4. Open a command prompt on your computer (Windows logo key + R, type cmd) and go to that directory (should be c:/moto-fastboot-win32)
#5. Type the following commands one by one:
Code:
moto-fastboot.exe flash preinstall preinstall.img
moto-fastboot.exe reboot
Your phone will reboot, when it is up and running again, type the following into the command prompt.
Code:
adb shell
/preinstall/dosu
/bin/mount -o remount,rw /system
cp /preinstall/su /system/bin/
chmod 6755 /system/bin/su
It comes with a superuser apk in the files and that post, but I recommend you install superuser from the android market.
Click to expand...
Click to collapse
So now I was wondering if I try to root it again will it brick the phone? I'm running on Gingerbread 2.3.4. Would superoneclick work with this?
Thanks (I tried to look for similar threads but couldn't find any, sorry for double posts)
** ADMINS/MODS, if your going to delete this thread, if you dont' mind please advising me on the correct way to post this or correct place, Thanks **
******************************************************
QUESTION: How can I create a update.zip (i.e., PG05IMG.zip) for the thunderbolt and then flash it with fastboot or in bootloader.
ANSWER: Flash a rom on your phone and then using adb
adb shell dd if=/dev/block/mmcblk0p25 of=/sdcard/system.img
Make a zip folder and put in it system.img along with boot.img from the
rom zip and whatever other partitions you want, perhaps a radio
mdm9k.img and radio.img along with a recovery.img and you can
make your own little custom rom to be flashed with fastboot or as an
update, then you can either put it on the sd card as an PG05IMG.zip and do
a bootloader update (s-off only) or fastboot flash zip (zipname.zip)
for eng-hboot only... really cool.
******************************************************
******************************************************
******************************************************
******************************************************************************************************************************************************************
1. Ok I've been trying dilligently in the past to do 2 things. I want to create my own SYSTEM.img from the roms i'm making so I can create PG05IMG's instead of .zips to flash, that way i can include the radio etc., this is for learning purposes (PLEASE DO NOT SUGGEST WELL KNOWN METHODS OR SIMPLY QUESTION WHY IM DOING THIS UNLESS ITS INVOLVED IN THE SOLUTION PROCESS.)
I have tried several different methods for backing up my system.img etc., I need someone to help me with this, and I'm willing to donate to get this done.
2. Secondly, I need to figure out a way to flash roms from command line using adb while the phone is in recovery, I don't have any problem flashing roms with fastboot if someone can show me or explain how to make the system.img actually work.
Already tried this:
Code:
adb push C:\ROM.zip /data/
adb shell
recovery --update_package=DATA:ROM.zip
This would simply make the thunderbolt go to an exclamation point and do nothing.
I was however able to get this to work on the same version of recovery 5.0.2.1 on a Nexus S I9020T, but not on the Thunderbolt ADR6400L.
Simple anlysis of questions
1. How can I turn a rom.zip (system folder) into a (system.img) "fastboot flashable"
2. How can I take a rom.zip and flash it in recovery using adb
Donation negotiable, and I appreciate any time/clues/answers/suggestions, but I really need to figure this out.
Hi there,
I have a plan in the works already since the beginning of last month. I call it CASUAL. Cross-platform Adb Scripting, Unified Android Loader. Its purpose is to do exactly what you wish. This is a project I intend to begin work on next month. I've set up a repository for the work and I will begin soon. Basically, it will do exactly what you want.
Edit: I do not intend on rushing for the bounty. My goal is to do it right. If someone wishes to rush it, go ahead and collect the bounty. My goal is to provide something which will create an infrastructure contained within a single cross-platform java file. I've got most of the heavy lifting already done from my Heimdall one-click project. However, in order to complete the job, it seems that I must reformat my desktop because my IDEs are acting wonkey.
AdamOutler said:
Hi there,
I have a plan in the works already since the beginning of last month. I call it CASUAL. Cross-platform Adb Scripting, Unified Android Loader. Its purpose is to do exactly what you wish. This is a project I intend to begin work on next month. I've set up a repository for the work and I will begin soon. Basically, it will do exactly what you want.
Edit: I do not intend on rushing for the bounty. My goal is to do it right. If someone wishes to rush it, go ahead and collect the bounty. My goal is to provide something which will create an infrastructure contained within a single cross-platform java file. I've got most of the heavy lifting already done from my Heimdall one-click project. However, in order to complete the job, it seems that I must reformat my desktop because my IDEs are acting wonkey.
Click to expand...
Click to collapse
Adam thanks for your response, really great to hear and the fact that your not rushing for money is great too I understand. But hey, without regard to the cross platform ADB rom flasher, can you just point me in the right direction as far as where to go to learn how to say, "make a system.img of a rom" so I can fastboot flash it..
Like so I can take a rom zip and be able to turn it into a system image that is fastboot flashable on the thunderbolt... at that point i can just manually flash the boot.img and radio and i'm good to go.
So if i can just figure out how to do that one little thing that would be huge and much appreciated... thanks so much man. I will gladly donate for an answer to this question.
halfcab123 said:
Adam thanks for your response, really great to hear and the fact that your not rushing for money is great too I understand. But hey, without regard to the cross platform ADB rom flasher, can you just point me in the right direction as far as where to go to learn how to say, "make a system.img of a rom" so I can fastboot flash it..
Like so I can take a rom zip and be able to turn it into a system image that is fastboot flashable on the thunderbolt... at that point i can just manually flash the boot.img and radio and i'm good to go.
So if i can just figure out how to do that one little thing that would be huge and much appreciated... thanks so much man. I will gladly donate for an answer to this question.
Click to expand...
Click to collapse
Generally, to flash a ROM, you type:
Code:
adb reboot bootloader
then on your desktop you use fastboot and type
Code:
fastboot oem unlock
fastboot flash your partition your file...
I'd follow this guide to get S-OFF: http://forum.xda-developers.com/showthread.php?t=1310014 then find your neato-bandito rom from this forum: http://forum.xda-developers.com/forumdisplay.php?f=943 and flash it.
AdamOutler said:
Generally, to flash a ROM, you type:
Code:
adb reboot bootloader
then on your desktop you use fastboot and type
Code:
fastboot oem unlock
fastboot flash your partition your file...
I'd follow this guide to get S-OFF: http://forum.xda-developers.com/showthread.php?t=1310014 then find your neato-bandito rom from this forum: http://forum.xda-developers.com/forumdisplay.php?f=943 and flash it.
Click to expand...
Click to collapse
Thanks Adam, but, I already know how to flash partitions in fastboot, but what i need to know is how to "make" partitions. as in like, take a system folder and turn it in to a system.img so i can fastboot flash system system.img
Please please need to know thanks
halfcab123 said:
Thanks Adam, but, I already know how to flash partitions in fastboot, but what i need to know is how to "make" partitions. as in like, take a system folder and turn it in to a system.img so i can fastboot flash system system.img
Please please need to know thanks
Click to expand...
Click to collapse
That's not overly hard to do. There's a guide I think on the cyanogen website for how to do it. Basically you use the "dd" tool in linux.
yareally said:
That's not overly hard to do. There's a guide I think on the cyanogen website for how to do it. Basically you use the "dd" tool in linux.
Click to expand...
Click to collapse
Dude please, can you walk me through it, like I said I'll donate. Or alteast give me a link to where its at, then i'll turn this post into a how to for noobs. I learn at 300,000,000 m/s^2
halfcab123 said:
Dude please, can you walk me through it, like I said I'll donate. Or alteast give me a link to where its at, then i'll turn this post into a how to for noobs. I learn at 300,000,000 m/s^2
Click to expand...
Click to collapse
It looks like there's a stupidly large amount of partitions on the Thunderbolt. if you can do this:
Code:
adb shell mount
and get the partition information, I can tell you how to do a backup and restore.
it will be something like this.. this gets run once to get a temporary storage area on the /sdcard
Code:
adb shell mkdir /sdcard/mybackup
Code:
mkdir /PATH/TO/YOUR/DESKTOP/backup
adb shell dd if=/dev/block/mmcblk0p25 of=/sdcard/mybackup/system.img
adb pull /sdcard/mybackup/system.img /PATH/TO/YOUR/DESKTOP/backup/system.img
These commands do: make a new folder for working on your desktop. direct disk backup of mmcblk0p25 (SYSTEM partition). Pull the system.img to your working folder on your desktop.
If you have your image on a Linux or Mac desktop, you can mount it like this..
Code:
cd /PATH/TO/YOUR/DESKTOP/backup
mkdir MountFolder
sudo mount ./system.img ./MountFolder
#if this doesnt work, then do this
sudo mont -o loop -t ext3 ./system.img ./MountFolder
you can make changes to the system which has been mounted onto your computer. Then unmount it and push it back to your device.
to unmount and flash it back you do this:
Code:
sudo umount ./MountFolder
adb push /PATH/TO/YOUR/DESKTOP/backup/system.img /sdcard/mybackup/system.img
adb shell dd if=/sdcard/mybackup/system.img of=/dev/block/mmcblk0p25
This pushes your backup to your device, then does a direct disk write of the image file to the disk partition
↑ last poster pretty much sums it up in detail
AdamOutler said:
It looks like there's a stupidly large amount of partitions on the Thunderbolt. if you can do this:
Code:
adb shell mount
and get the partition information, I can tell you how to do a backup and restore.
it will be something like this.. this gets run once to get a temporary storage area on the /sdcard
Code:
adb shell mkdir /sdcard/mybackup
Code:
mkdir /PATH/TO/YOUR/DESKTOP/backup
adb shell dd if=/dev/block/mmcblk0p25 of=/sdcard/mybackup/system.img
adb pull /sdcard/mybackup/system.img /PATH/TO/YOUR/DESKTOP/backup/system.img
These commands do: make a new folder for working on your desktop. direct disk backup of mmcblk0p25 (SYSTEM partition). Pull the system.img to your working folder on your desktop.
If you have your image on a Linux or Mac desktop, you can mount it like this..
Code:
cd /PATH/TO/YOUR/DESKTOP/backup
mkdir MountFolder
sudo mount ./system.img ./MountFolder
#if this doesnt work, then do this
sudo mont -o loop -t ext3 ./system.img ./MountFolder
you can make changes to the system which has been mounted onto your computer. Then unmount it and push it back to your device.
to unmount and flash it back you do this:
Code:
sudo umount ./MountFolder
adb push /PATH/TO/YOUR/DESKTOP/backup/system.img /sdcard/mybackup/system.img
adb shell dd if=/sdcard/mybackup/system.img of=/dev/block/mmcblk0p25
This pushes your backup to your device, then does a direct disk write of the image file to the disk partition
Click to expand...
Click to collapse
This is very informative and I actually realized something that I think will definitely help me, however its kinda not really the answer to my question.. and at the same time it is kind of another solution to the question that I asked.
What I asked was how to turn the system folder from a *.zip "rom" into a system.img that was fastboot flashable
You basically told me how to make a backup of the system, modify, and flash back to my phone.... which is interesting...
Basically what I take from this, please let me know if i'm on the right track here:
If the goal is to flash a rom on an htcdev unlocked phone one would:
(assuming system.img already created from backup, flashing to another phone)
Code:
adb reboot recovery
adb shell dd if=/dev/zero of=/dev/block/mmcblk0p6 (data wipe)
adb shell mount /sdcard/
adb shell dd if=/sdcard/system.img of=/dev/block/mmcblk0p25
adb reboot bootloader
fastboot erase cache
fastboot flash boot boot.img
fastboot reboot
After trying this, I was both unable to mount sd card for some odd reason
using adb shell mount /sdcard/ and I was also unable to wipe data
at partition mmcblk0p6 with /dev/zero it just hung for 4 minutes.. does it take longer ? I ended it.
My only other option that I can think of is to downgrade the thunderbolt and run revo to get s-off and then make a PG05IMG.zip with a custom system.img and boot.img and flash it as a PG05IMG.zip in bootloader... so coming from this direction which seems to be much much easier, if I say took a PG05IMG for the MR4 (2.11.605.9) replaced the hboot with an eng-hboot, replaced the system.img and the boot.img would it work ??? I'm going to try it lol, probably going to be an epic fail.. any comments appreciated.
UPDATE: after posting this I realized that with a revolutionary s-off, the hboot is protected from being updated with an RUU, in bootloader so I would not have to worry about replacing the HBOOT, the only reason I even mentioned it was because I know that the hboot in the official MR4 RUU is the dev method supported hboot and would probably throw a security warning after flashing... etc., once again any help is great.
There is no direct 1:1 way to convert. However, you can use the update script in the Meta folder as a guide. It will have information to copy files into the system folder and applysymlinks. The commands used by recovery all have a Linux equal.
Delete = rm
Delete recursive = rm -rf
symlink = ln -s
copy = cp
These are android recovery commands which must be translated to their Linux shell equivalants.
AdamOutler said:
There is no direct 1:1 way to convert. However, you can use the update script in the Meta folder as a guide. It will have information to copy files into the system folder and applysymlinks. The commands used by recovery all have a Linux equal.
Delete = rm
Delete recursive = rm -rf
symlink = ln -s
copy = cp
These are android recovery commands which must be translated to their Linux shell equivalants.
Click to expand...
Click to collapse
what if i just straight take the system.img and boot.img and throw them in a PG05IMG.zip and use bootloader to update, will that work ?
halfcab123 said:
what if i just straight take the system.img and boot.img and throw them in a PG05IMG.zip and use bootloader to update, will that work ?
Click to expand...
Click to collapse
I don't know what a pg05img is. However, with samsung devices, we use dd'd system images to flash with Odin. Odin works sorta like fastboot. I don't know if that will help you because I generally use Samsung devices and Samsung does things differently than the rest of Android. From what I understand, fastboot flashing is similar, but I don't know if you can DD an image from a device and just fastboot flash it back onto a device. You can do this with Odin. I don't think there are provisions for flashing images in recovery directly. They DO have executables encorperated within zip files for flashing modems and bootloaders. Before trying a non-standard flashing method, you need to do some reading. It can be risky.
AdamOutler said:
I don't know what a pg05img is. However, with samsung devices, we use dd'd system images to flash with Odin. Odin works sorta like fastboot. I don't know if that will help you because I generally use Samsung devices and Samsung does things differently than the rest of Android. From what I understand, fastboot flashing is similar, but I don't know if you can DD an image from a device and just fastboot flash it back onto a device. You can do this with Odin. I don't think there are provisions for flashing images in recovery directly. They DO have executables encorperated within zip files for flashing modems and bootloaders. Before trying a non-standard flashing method, you need to do some reading. It can be risky.
Click to expand...
Click to collapse
I just made my own PG05IMG.zip and updated in bootloader and it booted into a custom rom, and this is after i erased userdata, cache, system, so i know it works, i even
fastboot oem rebootRUU
fastboot flash zip "customzip.zip"
and that worked too, so stoked man, I can't believe I finally figured it out.
As soon as you told me the mmcblk0p25 could be backed up, it clicked, funny thing is I knew that but I guess I just didn't think it was that simple.