If you like that I'm doing this, then a thanks is cool, PLEASE DONATE, TIME OR MONEY BUT GIVE SOMETHING TO THESE DEVS!
http://tabletroms.com/forums/showthread.php?356-Honeycomb-on-the-Adam-(Updated)
New - No more partition editing required!
HC16JUN2011
HD Video
-Changelog
Like with any rom, YOU MUST WIPE CACHE, SYSTEM AND DATA, this rom especially, the is a pre alpha and has issues with cache, if you don't clear your info every time you will run into problems. I also clear Dalvik Cache and Battery Stats.
Old info on how to partition
STEP 1 – You need the new NVFlash click here for the unpartitioned onces(may need these)
NVflash edit- pretty simple you need to change the android fastboot full, you'll find that file towards the top of the nvflash folder or you can download my premade ones: (BUT I DIDN'T FORCE YOU TO DOWNLOAD THESE, IF YOU BRICK YOUR DEVICE BY USING THESE THEN YOU BRICKED IT NOT ME, YOU HAVE BEEN WARNED)
Sorry about the mega upload, working on getting my server up, also CWM is untested, it had some problems but I believe that was due to file size.
Clockwork Mod folder
Stock Recovery Folder
The section your looking for looks like this
[partition]
name=APP
id=9
type=data
allocation_policy=sequential
filesystem_type=yaffs2
size=209715200 <---(here is the money)
file_system_attribute=0
partition_attribute=0
allocation_attribute=0x10
percent_reserved=0
filename=system.img
minus the arrow and the here is the money you'll find the size listed as 209715200, you need to change that to 536870912, once you save go to here to setup your APX drivers and prepare to flash according to the link
STEP 1.1 – THIS IS FOR CLOCKWORK MOD RECOVERY ONLY Download Here
Make a copy of your nvflash folder, I name it PIXEL QI CW Mod
STEP 1.2 – THIS IS FOR CLOCKWORK MOD RECOVERY ONLY
Thank you darknao
Quick & Dirty method :
Extract the recovery.img from the clockwork.zip, and copy it to the nvflash folder(replace the original one).
Step 2
You need then to put your device into force recovery mode, so turn off your device, then power it on while holding the power + the volume down button till a orange and a yellow lite light up.
Step 3
Run the download.bat file described in the nvflash or unbrick your adam thread - now you can change the file name of the rom to update.zip and flash freely!
Reserved for other usage
Any idea when we'll get gapps working? Or you just linking to what they have done? Thanks for working to spread the word.
Amon Darthir said:
Any idea when we'll get gapps working? Or you just linking to what they have done? Thanks for working to spread the word.
Click to expand...
Click to collapse
Gapps are included however this build didn't have them, they had alot of problems with the sync feature, but in theory you should be able to use the latest gingerbread gapps, I will test that right now.
-OK I tested it out, the google setup frooze up on me, after restarting I was able to get into the initial setup, but I have the wifi only model, so I'm going to look into the gapp issue, see if I can find a way around.
-Tried a couple more copies of gapps including a HC edit for the nook sdk HC-- I would press more into this but with the rate of the updates I think its kinda pointless, for now Im going to adb push the market and see what I can get working, hopefully not in-vain since MrGuy and DJSteve move so fast with the updates.
after you use nvflash it will start to boot.. (this would be before flashing update zip) so should I power it down while its booting that first time in order to reboot to recovery and flash the zip?
I do but you don't have to if you use clockwork mod, it doesn't really matter, since you will be building your Dalvik cache once you install your rom.
$ ./download.sh
./nvflash: ./nvflash: cannot execute binary file
can anyone help me with this error i am getting when trying to run the downlaod script
jakobdroid said:
$ ./download.sh
./nvflash: ./nvflash: cannot execute binary file
can anyone help me with this error i am getting when trying to run the downlaod script
Click to expand...
Click to collapse
what operating system do you have? Is your adam in apx mode, and did you edit the android fastboot already? is it still a .bat file
osx, i already changed the file. what is apx mode? my adam has CWM on it, i understand that i am not supposed to have it for this HC rom. can i use the recovery image in the nvflash folder?
jakobdroid said:
osx, i already changed the file. what is apx mode? my adam has CWM on it, i understand that i am not supposed to have it for this HC rom. can i use the recovery image in the nvflash folder?
Click to expand...
Click to collapse
APX is the force recovery, the drivers are included with the NVflash, you must put your device into force recovery, with your device off you press volume down + power till you get your two lights to light up by the power cord, it'll be red and yellow, this is force recovery mode, I am using CW with it and I have listed above how to flash the CW with the increased partition. If you can't figure it out I will be adding the NVflash files with CW mode and non CW mode with the partition edits tonight. I will be turning the change log into a FAQ as well.
Just flashed the ROM and it is awesome. I was just wondering how to get a file managers working. I can't see my sd card. But otherwise, its amazing that honeycomb is up so fast.
okay my adam is in apx mode, i did your steps for using CWM, but im still getting the error:
./nvflash: ./nvflash: cannot execute binary file
i used chmod on the download.sh file, as well as nvflash. any idea whats going wrong?
jakobdroid said:
okay my adam is in apx mode, i did your steps for using CWM, but im still getting the error:
./nvflash: ./nvflash: cannot execute binary file
i used chmod on the download.sh file, as well as nvflash. any idea whats going wrong?
Click to expand...
Click to collapse
I'm downloading the file now, working on military lines so its slow to download but that way I can get a better idea of whats going on, also whats your operating system.
jakobdroid said:
okay my adam is in apx mode, i did your steps for using CWM, but im still getting the error:
./nvflash: ./nvflash: cannot execute binary file
i used chmod on the download.sh file, as well as nvflash. any idea whats going wrong?
Click to expand...
Click to collapse
Sounds like you're using linux like me. Are you on ubuntu. Cause I tried and tried and even with chmod and sudo and still got the same error. Consider this post though from: http://notioninkhacks.com/forums/viewtopic.php?f=90&t=1651&start=30
Hey gibson, thanks heaps for that! Actually, yourncomment before asking which folder I was in did it. Very strange, I had to run the commands from 2 folders above the extracted one, then symlink all the other files into the folder I was running from. Will post more later for people who run into similar issues, likely over at the unbricking thread. For now I've got a dualboot setup, and am running a minimal natty rootstock. I tried using the full omap4 image (ubuntu's default arm), but could only get it booting with lots of errors and no gui. Will be aiming to install the netbook desktop (unity 2d) in the next few days.
Re the post above, rayman's boot image already includes the kernel, so it's not needed in the rootstock command. Re the other options, probably will work, but remember rootstock is limited in what you can build... I.e., unless you have heaps of physical ram, you will probably only be able to build a few packages. Head over to xda, and the ubuntu on adam thread there for more info. We have experimented a lot with rootstock builds, and some of that might be useful.
Has anyone tried raymans boot.img with a natty rootstock? Did it work, and has anyone gotten a 2d unity gui up and running? My minimal natty rootstock boots fine, though I notice a few errors. Not sure if they are problematic or not. In any case, the build I made seems to be missing some important wireless tools, so I will likely rebuild it again with them in it soon. Am I likely to run into any problems using rayman's boot image, and steveh's kernel, with a natty build? Happy to post up my work if I get anything decent. Cheers.
osx 10.6.6, thank you!
jakobdroid said:
okay my adam is in apx mode, i did your steps for using CWM, but im still getting the error:
./nvflash: ./nvflash: cannot execute binary file
i used chmod on the download.sh file, as well as nvflash. any idea whats going wrong?
Click to expand...
Click to collapse
Also consider this: http://forum.xda-developers.com/archive/index.php/t-895388.html
Saved me some time thank you...
daiuton said:
Saved me some time thank you...
Click to expand...
Click to collapse
Don't know if the problem is solved yet but that doesn't take away from this honeycomb coolness. So happy to have so much use out of this Adam. Thanks.
that really didnt help, thanks though. i guess i will instal ubuntu in parallels and give it a shot...
Two problems here:
-How can i mount the adam with the computer? To move next updates and update in the next releases
-There is any gapps working (market,etc...)?
Related
there are a number of problems with the recovery in the just leaked
Froyo ROM.
1. signature checking
2. passing API version 3 to the updater binary
3. forced wipe after installing an update.zip
the attached zip has a 3e recovery modified to disable signature checking
report API version 2 for backwards compatibility with clockwork mod recovery
and disable the forced wipe after installing any update.
I don't know of any reason to run this version over 2e but it
might be useful to someone.
Installing:
1. turn on USB debugging
2. plug into computer
3. run script and follow on screen prompts.
UPDATED 01/23/2011
fixed path error when space in user name
UPDATED 01/22/2011
compressed the rageagainstthecage resource to prevent anti-virus detection
new anti-virus report
http://virscan.org/report/8e83f338fd7b8631c6b0bc0679efbd29.html
the /system file system is full on the newer ROM's
use the attached update.zip to root then install clockwork
Nice
Sent from my SGH-T959 using XDA App
ummmm... what attached zip?
kuhan said:
ummmm... what attached zip?
Click to expand...
Click to collapse
forgot to upload it.
kuhan said:
ummmm... what attached zip?
Click to expand...
Click to collapse
The one attached to the message(?)
fearmonkey said:
The one attached to the message(?)
Click to expand...
Click to collapse
yeah, he attached it after that post lol
how do you use this?
ok i wil bite. how do you use/flash this it cw is not accesible?
rename to update.zip i assume...... i mean thats how u flash everythign thats zip file if u cant get into clockwork.....
you cant flash this you will have to put the files on the internal sdcard
then use root explorer or adb to move the files into place, recovery goes to
/system/bin and the keys to /efs, update.zip is the clockwork recovery and
stays on the sdcard.
when you boot into recovery and choose re-install packages clockwork will
be able to do its thing.
I do like the sig verification but it's a PITA and may disable it, this is a temp
fix until I can finish hacking on recovery there is very little clues as to where
the functions are so it may be a few days.
forgot to mention to you also have to remount /system rw
mount -o rw,remount /dev/block/stl9 /system
Be-ware. Doing so on the ODIN 2E version will break Recovery all together.
Fine to replace on the Stock 2.2 ..
Ps.
Another Awesome Job untermensch
Not to sound like a total noob, but what benefit does this have over the current 2e recovery?
option94 said:
Not to sound like a total noob, but what benefit does this have over the current 2e recovery?
Click to expand...
Click to collapse
I haven't tried just replacing 3e with 2e, I doubt there is any advantage to
3e, to us anyway. but it is always worth while to find ways around these
things.
EDIT:
just replacing 3e with 2e did not work cant find the update.zip
Im suprised more people havent commented. I downloaded the first Stock version of JK2 and i tether so redownloading is not really what i wanted to do...plus i have a Mac so Id have to borrow my buddys pc again...anyway
This workedvgreat! For thise who might need it:
Place all files on the root of SD internal memory card
Copy keys file to /efs
Copy recovery file to /system/bin/ (backup old on first)
Leave all other files on SD internal
Reboot into stock recovery and select Reinstall Packages
itll do its thing and reboot into stock recovery again. From there youre set...just select reinstall packages each time.
Youre a life saver...thank you sir!
TJD319 said:
Im suprised more people havent commented. I downloaded the first Stock version of JK2 and i tether so redownloading is not really what i wanted to do...plus i have a Mac so Id have to borrow my buddys pc again...anyway
This workedvgreat! For thise who might need it:
Place all files on the root of SD internal memory card
Copy keys file to /efs
Copy recovery file to /system/bin/ (backup old on first)
Leave all other files on SD internal
Reboot into stock recovery and select Reinstall Packages
itll do its thing and reboot into stock recovery again. From there youre set...just select reinstall packages each time.
Youre a life saver...thank you sir!
Click to expand...
Click to collapse
thanks...
just updated the first post with a new version.
whats new
Code:
dissables forced post install wipe, dissables signature checking, and reports
API version 2 for backwards compatability with clockwork mod recovery.
Thanks man i rreally appreciate this like i said before. Working perfect snd no issues. Loving being able to CWM again ha. Anyway thank you again sir keep it up!
TJD319 said:
Im suprised more people havent commented. I downloaded the first Stock version of JK2 and i tether so redownloading is not really what i wanted to do...plus i have a Mac so Id have to borrow my buddys pc again...anyway
This workedvgreat! For thise who might need it:
Place all files on the root of SD internal memory card
Copy keys file to /efs
Copy recovery file to /system/bin/ (backup old on first)
Leave all other files on SD internal
Reboot into stock recovery and select Reinstall Packages
itll do its thing and reboot into stock recovery again. From there youre set...just select reinstall packages each time.
Youre a life saver...thank you sir!
Click to expand...
Click to collapse
Thanks untermensch for your work and thanks to the TJD319 for the clear step by step instructions.
Getting can't mount partition after I select a zip file to flash. I can get to cwr fine and it sees the sdcard (internal) fine since I can navigate and select the file I want. The error comes when I try flash. All the files in the zip are in the root of the sd internal, except for recovery and keys that are in the directory /system/bin and /efs respectively. Any advice?
untermensch said:
thanks...
just updated the first post with a new version.
whats new
Code:
dissables forced post install wipe, dissables signature checking, and reports
API version 2 for backwards compatability with clockwork mod recovery.
Click to expand...
Click to collapse
I personally want to say Thanks for Working on this... I Honestly like this version better than the 2e due to being able to wipe the SD-card now..
Thanks for everything.
eugene373 said:
I personally want to say Thanks for Working on this... I Honestly like this version better than the 2e due to being able to wipe the SD-card now..
Thanks for everything.
Click to expand...
Click to collapse
Thanks for the support Eugene....
updated the no sig check version again, too fix the issue that even though the key
is never used, recovery still looked for the existence of the file and would error out if not found.
untermensch said:
Thanks for the support Eugene....
updated the no sig check version again, too fix the issue that even though the key
is never used, recovery still looked for the existence of the file and would error out if not found.
Click to expand...
Click to collapse
Yo man i really appreciate your work. Froyos been great to me Stock 2.2 and this is perfect man. Working flawlessly for me and Im just happy to be able to nandroid.
Here's a guide on how to restore to stock using the FXZ for OS X/Linux users.
1. Download one of the following fastboot binaries: fastboot-OSX or fastboot-linux and rename it to just "fastboot"
2. Download the FXZ and untar it anywhere.
3. Plug in your phone to your computer (preferably a back USB port if you're on a desktop, don't use a front USB port if possible) and shut it down (leave it plugged in).
4. Hold down the vol-down button on the rocker and boot the phone up, it should boot into AP Fastboot Flash Mode and it should say "OK to Program".
5. Run the following commands in terminal
Code:
./path/to/fastboot flash system /path/to/system.img
./path/to/fastboot flash boot /path/to/boot.img
./path/to/fastboot flash recovery /path/to/recovery.img
./path/to/fastboot -w
6. Shut off the phone by pressing the power button.
7. Boot back up and you should be back to stock!
Thanks for posting this for us linux users. Hopefully I won't have to use it any time soon haha
I keep gettiing permission denied when entering the first command. Any suggestions? Thanks
Will this run without a Bionic attached? I'm just trying to get everything set up and run it to make sure it starts...
dscottjr81 said:
I keep gettiing permission denied when entering the first command ./fastboot flash system system.img. Any suggestions? Thanks
Click to expand...
Click to collapse
BUMP...........
have you tried sudo?
Has anyone had any success with this yet?
1KDS said:
Has anyone had any success with this yet?
Click to expand...
Click to collapse
I am doing it right now. There are some issues. Without sudo, you'll get permission denied. With sudo, you'll get "./fastboot: command not found". After changing fastboot to be executable without sudo, you'll get "./fastboot: cannot execute binary file". With sudo, you'll get "./fastboot: 3: Syntax error: "(" unexpected"...so short story, this does not work properly yet
---------- Post added at 03:37 PM ---------- Previous post was at 03:24 PM ----------
1KDS said:
Has anyone had any success with this yet?
Click to expand...
Click to collapse
Go here: http://forum.xda-developers.com/showthread.php?t=1279825
There is a one click Linux/Mac return to stock and root method there and it works. Hope that helps. It is extremely easy!
Bionic Restorer for Linux/Mac
OK, I'm finished with the new MotoRooter for Mac/Linux - naming it BionicRestorer because it's completely different. Right now it's in my Dropbox Folder, still no where to put it - lol.
Here's the link to BionicRestorer.zip
For Mac and Linux people - it's BionicRestorer v1.0
A way to flashboot restore your Bionic to 5.5.893
Download it, unzip it, cd into the BionicRestorer directory and type ./BionicRestorer.sh to run it. Mac folks can double click on the Mac-BionicRestorer.command file in that directory.
Linux People - this is solid, I've run it on LinuxMint (Ubuntu) and Scientific Linux (Redhat) and it worked everytime without a glitch.
Mac People - This is tempermental on the Mac, I've tried it on 3 different
Mac's and it worked sporadically on a Macbook Air running 10.7.2, didn't work on the iMac at all running 10.7.2,
and worked consistently on a Macbook running 10.6.8. Use at your OWN RISK!!!! If it hangs, all I
can is - try it again, or, run Linux, or, use RSDlite on Windows.
I can say that it worked consistently on a Macbook running 10.6.8
Option 3 (restore system, boot, recovery seems to work well on a Mac, but,
NOTE that these files are from v5.5.893! If you select option 3 you had better have flashed or updated to that version perviously, or, it will most likely bootloop when it finishes.
Note - This does NOT contain the actual files needed for flashing,
just the brains to flash them. You will need to download the zipfile
VRZ_XT875_5.5.893.XT875.Verizon.en.US_CFC_01.xml.zip from
http://rootzwiki.com...893-fxz-leaked/
then unzip it into the BionicRestorer directory.
Once it is extracted there should be a directory named:
VRZ_XT875_5.5.893.XT875.Verizon.en.US_CFC_01.xml
which contains all the files needed to do a flash restore.
And the menu looks like this:
BionicRestorer.sh (1.0) by crpeck
1. Restore a Bionic to 5.5.893 - NOT FOR 5.9.901 BIONICS!
-restores EVERYTHING to official 5.5.893
-wipes data
2. Restore a 5.9.901 Bionic to 5.5.893
-restores EVERYTHING EXCEPT for the cdt.bin to 5.5.893
-cdt.bin is restored using the 5.9.901 file
-wipes data
** YOU SHOULD ONLY USE THIS IF YOU ARE OR HAVE BEEN ON 5.9.901 **
3. Minimal Restore of system, boot, and recovery only
-restores ONLY the system,boot and recovery to official 5.5.893,
4. Root and ForeverRoot a non-rooted Bionic
-roots and installs the ForeverRoot hack
5. Copy 5.9.901 update file to sdcard
-this copies the unoffical 5.9.901 update file to your sdcard
chances are, your Bionic will bug you to do an update when it see's it
there, you can usually force it via the 'Check for Updates' screen.
6. Verify MD5sums of the flash image files (you should do this at least once)
7. Help - More detailed Information
q. Quit
NOTE: Selections 1-3 do NOT root the phone! Run 4 after running them.
By Your Command (1-7,q):
I took the .xml file from the VRZ_XT875_5.5.893.XT875.Verizon.en.US_CFC_01.xml.zip and re-wrote it into shell scripts (i also took out the piece in there that erases the internal sdcard - who wants to lose that - lol). There is a considerably amount of error-checking as well, but, I'm sure I missed something (which will result in v 1.1).
I encourage you to look through the scripts, feel free to modify and make it better! This may be the last release of this from me, as work is replacing my Bionic with a gnex in the near future - gonna miss the Bionic, it's been a fun learning tool.
Enjoy....
Oh - look at the 00_README_1ST.txt file - it's similar to this writeup, and, select the help option for more detailed information.
I've have to give this a try. I keep forgetting I have Ubuntu(dual-boot) on this thing. Heh
i'm running SafeStrap 3.11 and wiped my safe partition in a late night flashing frenzy. is it possible to flash certain partition images to restore the stock ROM without loosing SafeStrap?
mechanizedmedic said:
i'm running SafeStrap 3.11 and wiped my safe partition in a late night flashing frenzy. is it possible to flash certain partition images to restore the stock ROM without loosing SafeStrap?
Click to expand...
Click to collapse
Flash system.IMG
fastboot flash system /path/to/system.img
fastboot flash boot path/to/boot.img
Any other partition you might want to flash flashing recovery partition will erase safe strap might lose safestrP after flashing system you will lose root regardless
If followed correctly, this a bulletproof method (reposted from our work at Rootzwiki) of returning any image to a true 5.5.886 stock and then applying the OTA update.
Commands/Screenshots
Moto-Fastboot Commands
Root Commands
Boot Mod Commands
***All the files you must have in one folder - Full Package from below***
Necessary Resources
Motorola Drivers v5.4.0 (32-bit) or Motorola Drivers v5.4.0 (64-bit)
5.5.886 Radios (radio.zip)
Full Package of All Other Files You Will Need: Link 1 or Link 2
Optional Resources
5.5.886 Boot Mod
5.5.886 FXZ Restore File
Motorola Fastboot
Root and Forever Root Files
ADB-Fastboot Files
5.5.893 OTA Update
RSDLite v5.6
Fastboot Mode
Make sure the phone is off
Hold down the Volume Down + Volume Up buttons and press the Power button
When the choices appears, press Volume Down twice, till "AP Fastboot" is selected
Press Volume Up to select
Recovery Mode
Make sure the phone is off
Hold down the Volume Down + Volume Up buttons and press the Power button
When the choices appears, press Volume Down once, till "Recovery" is selected
Press Volume Up to select
When the icon with the android and exclamation appear press both Volume Up and Volume Down at the same time to enter the recovery
Step-by-step Process
Download the 3 files under "Necessary Resources"
Install the appropriate Motorola drivers for your operating system
Place the radio.zip file on the root of your SD card (not internal storage)
Unpack the full package of files to one folder on your computer
Turn off your phone completely
Start into Fastboot Mode (listed above)
Connect your phone to your PC with the USB cable and let it install the drivers for your device
After the drivers are done installing, open a command prompt in the folder where you unzipped the full package to
Using the Moto-Fastboot Commands screenshot from above follow each one step by step until you are done
When you have finished, disconnect your USB cable and press the Power button once to turn it off
Start into Recovery Mode (listed above)
Highlight "wipe cache partition" and press the Power button to select it
When it has completed, pull the battery out of your phone and then put it back in
Start into Recovery Mode again
Highlight "apply update from sdcard" and press the Power button to select it
Highlight the "radio.zip" file on your SD card and press the Power button to select it
When it has completed, highlight "reboot system now" and press the Power button to select it
When the device reboots into the OS waited 1 minute for it to load everything in the background
Follow the prompt but don't sign into anything, just get to the homescreen
When at the homescreen, connect your USB cable and then from the pull down menu select "USB connection", then select "Charge Only" and hit OK
Go into Settings -> Applications and enable Unknown Sources and hit OK
Go into Development and enable USB Debugging and hit OK
Back out to Settings -> Battery & data manager -> Battery mode and select Performance mode
Power off your phone and then power it back on normally
Open a command prompt in the folder where you unzipped the full package to
Using the Root Commands screenshot from above follow each one step by step until you are done
Power off your phone and then power it back on normally
Open a command prompt in the folder where you unzipped the full package to
Using the Boot Mod Commands screenshot from above follow each one step by step until you are done
***When a Superuser prompt appears on your phone after the last command, quickly select Allow and make sure you do NOT reboot your phone***
When it has finished, connect your phone to your 3G/4G or a WiFi connection
Go into Settings -> About phone and select System updates
When the prompt comes up, press Setup
Place a check in "I agree to the Motorola Terms of Service" and then press Next
When the update prompt comes up, press Download
Wait for the update to download
When the update prompt comes up, press Install Now
Let update reboot to recovery and install itself
***Your phone may appear as if it is completely off for a little while but leave it be it will turn itself on and continue***
Let the update finish and then it will reboot back into your system
Congratulations! You now have the official 5.5.893 update installed and are back on the official OTA path and forever rooted
Credit to all developers of the zergRush exploit, to realbbb (from Rootswiki) for discovering the Boot Mod, and anyone else who participated in making this all possible.
I have edited the instructions to make things easier. I have included the entire package of all the files you will need under "Necessary Resources".
The official fully detailed guide is now up. Please feel free to comment if you have any questions, concerns, or need help.
The steps can be made even simpler actually.
The radio flash is unnecessary and all that is required is moto-fastboot of the system.img, grfs.img and preinstall.img and then boot, root and DD the .886 boot.img and then the 5.5.893 will succeed.
You can keep data and avoid all those extra steps too!
Hey guys I got a little problem, unfortunatly you guys have generated so much traffic on my Dropbox account that they suspended it for 3 days. I'm going to ask if any of you guys have the full package file to please upload somewhere for a few days and post a link here until my account has been unfrozen. In the mean time you guys can use the optional files to recreate that package listed in the 4th screenshot. I greatly apologize for this inconvinience.
cellzealot said:
The steps can be made even simpler actually.
The radio flash is unnecessary and all that is required is moto-fastboot of the system.img, grfs.img and preinstall.img and then boot, root and DD the .886 boot.img and then the 5.5.893 will succeed.
You can keep data and avoid all those extra steps too!
Click to expand...
Click to collapse
Noob question ... what does "DD" mean?
I'm going to let the process (OP or the one quoted) shake out over the next few days before I even consider going forward. I definitely would love to maintain data.
GertBFrobe said:
Noob question ... what does "DD" mean?
I'm going to let the process (OP or the one quoted) shake out over the next few days before I even consider going forward. I definitely would love to maintain data.
Click to expand...
Click to collapse
dd=raw image
i think or at least it does to me being in computer forensics
---------- Post added at 05:06 PM ---------- Previous post was at 05:04 PM ----------
someone please share a working link for those files.
As soon as your account becomes unfrozen I'll download the "full files package" and try to upload to Megaupload or something like it to have them permanently downloadable.
The steps can be made even simpler actually.
The radio flash is unnecessary and all that is required is moto-fastboot of the system.img, grfs.img and preinstall.img and then boot, root and DD the .886 boot.img and then the 5.5.893 will succeed.
You can keep data and avoid all those extra steps too!
Click to expand...
Click to collapse
Also, I too would like to keep my data and would like to do the simpler way. please clarify what DD means in the above post?
Ok, since nobody can download the full package from the OP, I won't feel so badly about hijacking his thread with different information.
This method is overly complicated and includes many redundant and unnecessary steps. A lot more info about this procedure has been developed since the OP made this guide and the process has been accomplished in several different ways at this point, including RSD lite using modified .xml files and a limited set of images.
dd is a command in Linux to make a direct digital copy of a file or partition, a raw image as stated above. One of the required steps which is part of the streamlined process, is to use a .bat file created by a user to dd the .886 boot.img to the phone after having flashed the system.img, preinstall.img and grfs.img from the FXZ and then rooting it again. This is the part that actually fixes the boot.img so that the update.zip will pass it's assert check for mtd/boot and flash the 5.5.893 update successfully.
This is despite the fact that manually copying the boot.img like this will fail to boot because it is not a signed image. The image is in fact an exact copy so the update.zip accepts it and patches it as per the updater-script.
That is the crux of the fix. All the rest is not needed. The radio does not need to be reverted because the update.zip does not assert the radio version at all.
All of the other pieces being flashed and reflashed is redundant and wiping data is not required at all and makes the rerooting and running the boot mod that much quicker and easier because you are already setup and have USB debugging checked etc. To say nothing of saving the time to resetup the device after a wipe.
I will also add that P3Droid has created a scripted method with all files included and options for loading 5.5.893 and then 5.9.901 if desired. This includes flashing the 3 images with moto=fastboot, the rooting and dd of the boot.img and then reboots into recovery where the only user input needed is to select the update.zip and run it and reboot.
This method will be released on MDW very soon.
I don't want to steal the thunder from the OP, as he was involved in the process much earlier than was I. I came in after success had been established and P3Droid and I saw the extraneous steps and both completed this simpler method with the reduced steps successfully last night.
We take no credit for the development of the method, which involved a large number of people contributing over several days of hashing out the details.
We just took the fat out and made sure it worked as we understood it should.
So I think that I will do this. Lets says I get to 5.893, install safestrap, and on my non safe 'strap' ie, my daily driver, I restore a nandroid backup of the ROM I am running now (eclipsev 2.0, 5.7.893), Will this work? And theoretically I will have the same system I do now, but with 5.5.893/new radio/kernal/on the update path... That all sound about right and doable?
Sent from my DROID BIONIC using xda premium
You cant use safestrap with this because it modifies the preinstall partition.
It won't matter anyway because you have to be completely stock with just root and the steps require will do all of that and remove Safestrap anyway when you flash the stock images. The update.zips are run from stock recovery and the only reason root is required is to dd the boot.img because that operation needs root in adb shell.
So, whatever ROM your are on is immaterial and this will revert you to 5.5.886 and then forwards to 5.5.893 and 5.9.901 as a last option, all the while keeping root by 4everoot.
If you do go to .901 then you have to do extra steps to have any custom ROMs work with the new radio. I am sure the ROM devs will progress rapidly with these new requirements as they have already, but I will not comment nor advise regarding any custom ROMS because I don't use them myself.
cellzealot,
Thank you for all the time you have contributed to participating in the work of this method. I appreciate your continued effort in order to slim down and automate the steps I have listed. I do encourage anyone interested to feel free to use this method instead of mine. However for those who are more interested to take the manual route and prefer to be in full control of what's going on with your device (maybe learn a few things along the way too), I will be keeping this method up and hopefully my Dropbox account will be unfrozen in a few days so the full package can be downloaded again. In the mean while, if anyone still has this file please PM me a link when you can upload it elsewhere and I will have it updated.
Thanks again,
Open1Your1Eyes0
EDIT: FYI, for all those you who want to keep their data just skip the last command in the Moto-Fastboot commands screenshot. The command is "moto-fastboot -w". Skipping this will leave your data intact. However, note that because everyone's data is different, I cannot guarantee this will work for everyone so please note that it is no longer considered "bulletproof" in this case although most likely should work.
cellzealot said:
You cant use safestrap with this because it modifies the preinstall partition.
It won't matter anyway because you have to be completely stock with just root and the steps require will do all of that and remove Safestrap anyway when you flash the stock images. The update.zips are run from stock recovery and the only reason root is required is to dd the boot.img because that operation needs root in adb shell.
So, whatever ROM your are on is immaterial and this will revert you to 5.5.886 and then forwards to 5.5.893 and 5.9.901 as a last option, all the while keeping root by 4everoot.
If you do go to .901 then you have to do extra steps to have any custom ROMs work with the new radio. I am sure the ROM devs will progress rapidly with these new requirements as they have already, but I will not comment nor advise regarding any custom ROMS because I don't use them myself.
Click to expand...
Click to collapse
So are you saying you can't do this to get back on the path and then install safestrap? Maybe i am not understanding something somewhere but i would think you could do this then use safestrap to install a custom rom then when a new update comes from verizon just switch back over to update then if you want go back to your safestrap just go back over. can someone explain this?
Let me clarify your clarification on clarifying what it is I want clarified.
I understand safe strap, as with everything else goes kaputski when doing this as our phone will go back to a stock system. I don't want to try to do this IN safestrap, rather:
1.make a nandroid of current eclipse ROM.
2.use this method to get back to the ota path and a stock phone (5.5.893)
2.5 make nandroid of stock system
3.Install safestrap
4. Restore eclipse nandroid/backup
5.install super cool ics alpha 42 on safe system
6. Rejoice with a cookie, knowing that now I have the radio/kernel back to upgrade path
7. New update comes out, restore nandroid of stock system.. On UN safe system
8. Accept ota
9.rinse
10. Lather
11.repeat
12. Enjoy another one of those cookies
Does this sound feasible? Or not so much.
Thank you Happy Festivus
Sent from my DROID BIONIC using xda premium
ticrandall said:
Let me clarify your clarification on clarifying what it is I want clarified.
I understand safe strap, as with everything else goes kaputski when doing this as our phone will go back to a stock system. I don't want to try to do this IN safestrap, rather:
1.make a nandroid of current eclipse ROM.
2.use this method to get back to the ota path and a stock phone (5.5.893)
2.5 make nandroid of stock system
3.Install safestrap
4. Restore eclipse nandroid/backup
5.install super cool ics alpha 42 on safe system
6. Rejoice with a cookie, knowing that now I have the radio/kernel back to upgrade path
7. New update comes out, restore nandroid of stock system.. On UN safe system
8. Accept ota
9.rinse
10. Lather
11.repeat
12. Enjoy another one of those cookies
Does this sound feasible? Or not so much.
Thank you Happy Festivus
Sent from my DROID BIONIC using xda premium
Click to expand...
Click to collapse
Wonderfully explained! Thank you
cellzealot said:
Ok, since nobody can download the full package from the OP, I won't feel so badly about hijacking his thread with different information.
This method is overly complicated and includes many redundant and unnecessary steps. A lot more info about this procedure has been developed since the OP made this guide and the process has been accomplished in several different ways at this point, including RSD lite using modified .xml files and a limited set of images.
dd is a command in Linux to make a direct digital copy of a file or partition, a raw image as stated above. One of the required steps which is part of the streamlined process, is to use a .bat file created by a user to dd the .886 boot.img to the phone after having flashed the system.img, preinstall.img and grfs.img from the FXZ and then rooting it again. This is the part that actually fixes the boot.img so that the update.zip will pass it's assert check for mtd/boot and flash the 5.5.893 update successfully.
This is despite the fact that manually copying the boot.img like this will fail to boot because it is not a signed image. The image is in fact an exact copy so the update.zip accepts it and patches it as per the updater-script.
That is the crux of the fix. All the rest is not needed. The radio does not need to be reverted because the update.zip does not assert the radio version at all.
All of the other pieces being flashed and reflashed is redundant and wiping data is not required at all and makes the rerooting and running the boot mod that much quicker and easier because you are already setup and have USB debugging checked etc. To say nothing of saving the time to resetup the device after a wipe.
I will also add that P3Droid has created a scripted method with all files included and options for loading 5.5.893 and then 5.9.901 if desired. This includes flashing the 3 images with moto=fastboot, the rooting and dd of the boot.img and then reboots into recovery where the only user input needed is to select the update.zip and run it and reboot.
This method will be released on MDW very soon.
I don't want to steal the thunder from the OP, as he was involved in the process much earlier than was I. I came in after success had been established and P3Droid and I saw the extraneous steps and both completed this simpler method with the reduced steps successfully last night.
We take no credit for the development of the method, which involved a large number of people contributing over several days of hashing out the details.
We just took the fat out and made sure it worked as we understood it should.
Click to expand...
Click to collapse
And this is exactly as it should be.
I was one of the first to try the method out, and my set of steps was a lot simpler, as I had not hacked my webtop, and neither had I removed any apps from the system area either. All I did the was revert to stock rooted 43v3r r00ted system with r3l34s3d r00t, revert radio, dd kernel, then flash ota.
Now that you guys have stepped in and cut the fat out, I think a lot of people are going to be much happier with the whole process, happier and more comfortable, which is a major factor with this sort of thing.
Thanks again, cz, p3 and anyone else refining the process, and especially thanks to 0 open for detailing the steps in the beginning, and a huge thanks to real BBB for providing me with the files to dd the kernel when I started doing all this.
This is why I love my bionic and Android in general - you guys rock!
Sent from my DROID BIONIC using Tapatalk
This makes me happy to see this. I was worried about getting back on the upgrade path. Thank you to all those involved in this!
Hey guys,
So I'm finally home and now had a chance to access my files. I'm choosing to forget about Dropbox because I cannot wait for them any longer since I've been getting a lot of PM's requesting this file. I have edited the OP and all file links are updated and working. The full package has been moved to MegaUpload instead. Anyone who was waiting before the method is now fully working and ready for use. As always please feel free to comment if you need any help or have any questions. Thank you for your patience and once again I apologize for the delay.
Thank you,
Open1Your1Eyes0
If this doesnt work for anyone or the instructions seem to insane, p3's new OTA fixer program works like a charm.
TheMuffStuff said:
If this doesnt work for anyone or the instructions seem to insane, p3's new OTA fixer program works like a charm.
Click to expand...
Click to collapse
Where can this be found? I haven't been able to locate a link for it.
Edit: Appears to be here: http://www.droidforums.net/forum/dr...ates-your-modified-motorola-droid-bionic.html
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?
hi,
so heres the deal,
before oem unlocking,installing twrp, installing modify rom. (with out ads)
i did a backup of my phone via recovery mode.
it created 6 files userdata_xxxx_xxxx.backup (.backup 0 to 6) in total of 11.4GB , i have tried to see if its a tar file, i tried to open it with 7zip and tried to dd the first 512bytes , nothing worked.
i would like to know how can i extract / view /open these backups that i made to restore some pictues, since twrp wont recognize the backup that i've made with the stock recovery , i dont want to erase the files and data that i have at the moment so i would not restore it right into the phone , so manual way is only way.
i am on win10 and linux
after omit all the packages as one
doing file gave me this userdata_xxxx_xxxx.backup: Linux rev 1.0 ext4 filesystem data, UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b (needs journal recovery) (errors) (extents) (large files)
trying to mount with mount -t ext4 -o loop,rw userdata_xxxx_xxxx.backup "tmp" gave me an empty result "empty thumb drive"
help will be appreciate thanks alot!
doesitburn said:
hi,
so heres the deal,
before oem unlocking,installing twrp, installing modify rom. (with out ads)
i did a backup of my phone via recovery mode.
it created 6 files userdata_xxxx_xxxx.backup (.backup 0 to 6) in total of 11.4GB , i have tried to see if its a tar file, i tried to open it with 7zip and tried to dd the first 512bytes , nothing worked.
i would like to know how can i extract / view /open these backups that i made to restore some pictues, since twrp wont recognize the backup that i've made with the stock recovery , i dont want to erase the files and data that i have at the moment so i would not restore it right into the phone , so manual way is only way.
i am on win10 and linux
after omit all the packages as one
doing file gave me this userdata_xxxx_xxxx.backup: Linux rev 1.0 ext4 filesystem data, UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b (needs journal recovery) (errors) (extents) (large files)
trying to mount with mount -t ext4 -o loop,rw userdata_xxxx_xxxx.backup "tmp" gave me an empty result "empty thumb drive"
help will be appreciate thanks alot!
Click to expand...
Click to collapse
read through this thread.
https://forum.xda-developers.com/showthread.php?t=2528969
it covers this situation. There is a script to automate this on post 17, I have not tried, but comments show it works
mrmazak said:
read through this thread.
https://forum.xda-developers.com/showthread.php?t=2528969
it covers this situation. There is a script to automate this on post 17, I have not tried, but comments show it works
Click to expand...
Click to collapse
i have followed this before opening a thread, it did not work for me,
when using the bash script omit all the backup files to one and then tried mount it. problem is i let it ran 8h+ and it filled up my whole hdd when trying to mount it .
so it did not help me :s
doesitburn said:
i have followed this before opening a thread, it did not work for me,
when using the bash script omit all the backup files to one and then tried mount it. problem is i let it ran 8h+ and it filled up my whole hdd when trying to mount it .
so it did not help me :s
Click to expand...
Click to collapse
I know you said you have data currently on phone you dont want to loose. But it seems it might be easier to make twrp backup of phone now. then put factory recovery on and restore that back up you have from before , save off it what you wanted, then put twrp back and restore the twrp backup.
where do i get the factory recovery img ?
also thats sound alot more easier to extract/view the data instead of removing everything that i have now :S
when using file the output is that
userdata_xxxx_xxxx.backup: Linux rev 1.0 ext4 filesystem data, UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b (needs journal recovery) (errors) (extents) (large files)
this file was made by the bash script bckp2cwm.sh
doesitburn said:
where do i get the factory recovery img ?
also thats sound alot more easier to extract/view the data instead of removing everything that i have now :S
when using file the output is that
userdata_xxxx_xxxx.backup: Linux rev 1.0 ext4 filesystem data, UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b (needs journal recovery) (errors) (extents) (large files)
this file was made by the bash script bckp2cwm.sh
Click to expand...
Click to collapse
Of course it sounds easier to just mount the backup and browse for the files. But you are not able to do it, so not an option.
I have the stock recovery , will post a link when I get home tonight, if still needed by then
mrmazak said:
Of course it sounds easier to just mount the backup and browse for the files. But you are not able to do it, so not an option.
I have the stock recovery , will post a link when I get home tonight, if still needed by then
Click to expand...
Click to collapse
well i have tried another alternative such a recovery program such r studio, it worked to recover some pictures but not all of them and it was quiet messy i guess i will do a recovery with the stock img that u will provide
thanks alot <3
i am on 7.4.2 modified firmware , does it matter? or stock recovery will work even if its from another version
ii found this http://rootjunkysdl.com/files/Blu R1 HD Amazon/Firmware/SP_Flash_Tool_BLU_R0010UU_V6.5_Firmware.zip will it work with his recovery even tho its 6.5 ?
i will wait for ur stock recovery
doesitburn said:
well i have tried another alternative such a recovery program such r studio, it worked to recover some pictures but not all of them and it was quiet messy i guess i will do a recovery with the stock img that u will provide
thanks alot <3
i am on 7.4.2 modified firmware , does it matter? or stock recovery will work even if its from another version
ii found this http://rootjunkysdl.com/files/Blu R1 HD Amazon/Firmware/SP_Flash_Tool_BLU_R0010UU_V6.5_Firmware.zip will it work with his recovery even tho its 6.5 ?
i will wait for ur stock recovery
Click to expand...
Click to collapse
that one should be ok. but large download for only small needed file.
here is recovery from 6.1
unzip it and use "fastboot boot" to test boot it. should also be able to use it for restore without flashing it.
mrmazak said:
that one should be ok. but large download for only small needed file.
here is recovery from 6.1
unzip it and use "fastboot boot" to test boot it. should also be able to use it for restore without flashing it.
Click to expand...
Click to collapse
thanks alot
u mention i can use that recovery with out flashing it ? how can i do that ?
i was about to use SP FLASH, if its possible without whats good
(also if i cant use ur way to use it with out flashing it, dont i need a scatter file ?)
doesitburn said:
thanks alot
u mention i can use that recovery with out flashing it ? how can i do that ?
i was about to use SP FLASH, if its possible without whats good
(also if i cant use ur way to use it with out flashing it, dont i need a scatter file ?)
Click to expand...
Click to collapse
use fastboot.
power off phone. Power on while holding volume up.
you get a boot menu
use volume to select fastboot, power to select
connect phone to usb. Open terminal window , verify connected to phone, and confirm drivers, type "fastboot devices"
as long as connection return with "fastboot" and your "serial number" it is working.
type "fastboot boot ENTER FILE NAME AND LOCATION OF DOWNLOADED RECOVERY"
mrmazak said:
use fastboot.
power off phone. Power on while holding volume up.
you get a boot menu
use volume to select fastboot, power to select
connect phone to usb. Open terminal window , verify connected to phone, and confirm drivers, type "fastboot devices"
as long as connection return with "fastboot" and your "serial number" it is working.
type "fastboot boot ENTER FILE NAME AND LOCATION OF DOWNLOADED RECOVERY"
Click to expand...
Click to collapse
ok so for that matter
fastboot boot c:\downloads\recovery.img
that it ? sweet thanks alot.
learning something new every day