Related
I have a T-Mo G1 that had CM 4.1.11.1 on it and I was looking to upgrade to the newest stable, 4.2.1, using CM recovery 1.4. Something went wrong while upgrading so I decided to unroot the phone. I've read many guides on rooting and unrooting, but something just doesnt seem right to me.
1. When I return to rC29 should Telnet be downloading automatically? Does this mean I still have stored info somewhere in there?
2. When performing tasks in CM 1.4, such as flashing, it prompts me to reboot so I do it. Should I be returned to the recovery screen again after boot every time? I don't remember this happening before...
3. Which update.zip do I use when unrooting, the 177kb (droids on skateboards) or 205kb (red, green, blue, white) file?
4. Can someone give me a guide to unroot and fully wipe with CM 1.4?
Any help is appreciated, thanks alot.
I'll give you the steps to unroot which should answer your questions
1) Flash the stock SPL (the tri colour one). If you have 1.33.2005 (AKA Danger) SPL and you do downgrade to 1.1/RCx YOU WILL BRICK.
2) Flash the RC29 DREAIMG.nbh from the SPL - boot in to it by holding power and camera (it should be tricolour). Telnet should not magically be there, even if it was, doesn't matter
3) Put a recovery image of your choice on the root of the sdcard as 'recovery.img'
4) Flash the recovery image
1. Download recovery.img and copy it to your SD card (see the previous instructions on how to copy from your computer to your Phone's SD card).
2. Download the Hard SPL and copy the zip file to the SD card.
3. All files must be on the root of your SD card.
4. Restart your phone. Wait for your phone to start up fully and show the home screen.
5. After your phone starts up, hit the enter key twice, type "telnetd" and press enter. (Yes, it will start up a contact search, don't worry. Just type it.)
6. Download an Android "Telnet" application from the Market and connect to localhost.
7. If you connect successfully, you will have a root prompt "#".
8. Type the following into Telnet (these commands will give you root access easier in the future):
* mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
* cd sdcard
* flash_image recovery recovery.img
* cat recovery.img > /system/recovery.img
Click to expand...
Click to collapse
After that you can flash the 26I radio then a 1.5/1.6 ROM.
only way i found to unroot completely.. is to go bac thru the unroot process.. then update with an ota.. to remove all root...
unroot g1: http://theunlockr.com/2009/07/05/how-to-unroot-your-t-mobile-g1/
unroot mt3g: http://theunlockr.com/2009/08/22/how-to-unroot-your-mytouch-3g/
*Double post fail*
mrnv45 said:
only way i found to unroot completely.. is to go bac thru the unroot process.. then update with an ota.. to remove all root...
unroot g1: http://theunlockr.com/2009/07/05/how-to-unroot-your-t-mobile-g1/
unroot mt3g: http://theunlockr.com/2009/08/22/how-to-unroot-your-mytouch-3g/
Click to expand...
Click to collapse
He wants to re-root I believe, so not point updating.
RC29 and RC7 aren't root enabled ROMs, they just have security flaws which can be exploited to flash root enabled ROMs. Updating doesn't matter...
Thanks for your help, I'll be able to try this in about a half hour, will report back. As you said after step 4, I will need to flash a "26I" radio?
Had to install Telnet manually. Good to see a sign of normalcy here.
Flashing 26I Radio, HTC Recovery 1.6, and CM 4.2.1. Flash Radio, reboot, HTC, no reboot, CM 4.2.1, reboot. Right?
Tried the above, also tried with a reboot in between the HTC flash and CM 4.2.1 flash, stuck at G1 screen.
I'm still stuck at the G1 screen.
Probably be me next.
Finding myself having to do the same thing, somehow doing the CM 4.2.1.? whatever the last one was. I managed to lose root, be really nice to have a second card right now having to move 8 gigs off and repartition it to make it see the R29 image so i get to do literally everything all over again.
As someone once said, Ah Linux! Its Free! assuming your time is worth nothing. So true, lol. well ill be even better once it all works, if i can figure out what it takes to make it all work ill come back and try to help you out. Looks like mine wont see the image cause of my multi-partitioned microSD card. Not sure if yours is like that too or not, something to think about.
virtually painless
Kind of like virtual reality i guess?
Only gotcha i found in going back and reinstalling the RC29 image back on to be able to reclaim root was that my SD card having being partitioned. would cause it to fail. I would hit the tri-color screen, see a real quick gray flash and a message that vanished as quick as it popped up and then i would be stuck back on the colored screen.
So, i backed up the whole card, followed by
removing all data from the card. then running fdisk /dev/sdg. deleting the 3 partitions, writing a filesystem to the root of the disk via mkfs.vfat /dev/sdg , copying the 5 required files over and proceeding to get root and then recreating the paritions and copying data back over.
Back up and running.
mrnv45 said:
only way i found to unroot completely.. is to go bac thru the unroot process.. then update with an ota.. to remove all root...
unroot g1: http://theunlockr.com/2009/07/05/how-to-unroot-your-t-mobile-g1/
unroot mt3g: http://theunlockr.com/2009/08/22/how-to-unroot-your-mytouch-3g/
Click to expand...
Click to collapse
Thanks XDA - have to do a TMo warranty exchange and this helps greatly.
Hey folks,
I have a couple of question before rooting, i was going to use regaw_leinad 2.1 guide unless anyone has a better suggestion ?
1. By rooting my phone am I removing the standard ROM or just making it that I can edit it?
2. How does one install a new ROM for example the ALOYSIUS 2.1 looks great but i haven't a clue what to do?
Any help is much appreciated
thatenglishguy said:
I have a couple of question before rooting, i was going to use regaw_leinad 2.1 guide unless anyone has a better suggestion ?
Click to expand...
Click to collapse
Yeah, that's what I do.
thatenglishguy said:
1. By rooting my phone am I removing the standard ROM or just making it that I can edit it?
Click to expand...
Click to collapse
There are 2 parts to what you are doing. You are gaining root access, and then you are using that access the write a new recovery image to your phone. You may keep the standard ROM.
thatenglishguy said:
2. How does one install a new ROM for example the ALOYSIUS 2.1 looks great but i haven't a clue what to do?
Click to expand...
Click to collapse
You install new ROMs using the recovery image you installed while rooting your phone. Copy the .zip file(s) for the ROM you want to flash to the root directory of your sdcard. Boot to recovery by holding the HOME key while you press the power button. In recovery, you have the option to backup your existing ROM and to install a new one.
Thanks
Awesome, thank you v much indeed.
I have rooted my phone with Regaw's instructions, and it was very straight-forward.
1.) When you root your phone, you have a special recovery image that you can boot the phone into, and basically back up/restore your phone in case you decide to flash different roms and didn't like it, or you screwed up somewhere along the way. You can toggle the usb function, meaning you can use a terminal emulator (command prompt for windows) and move files between your pc and the phone while in recovery. You can theme your phone, can remove unwanted apps, use apps from the market that require you to have root access.
The simplest reason; to have full control of your phone.
2.) When you aquire root on your phone and able to boot into recovery and such, you can take the zip file that the rom was created in, and transfer it to the root of your sd card. Then you can either A) Open the command prompt, type in adb shell then type in reboot recovery while the phone is plugged in with the pc. The phone will reboot into recovery. B) Just power off the phone completely, then press and hold the home key and turn the phone on until you get to the recovery screen. From there you will need to backup your phone if you haven't already. Select backup/restore, then select nand backup. It will take a few minutes for this process to complete. When finished, you can go back to the main screen, and select wipe. Then select wipe data/factory reset. Press the home key to confirm. Go back and select wipe Dalvik-cache.
When done, go back to the main screen and select flash zip from sdcard. Scroll to the rom that you put in and select it. It should take a couple minutes to flash the new rom on your phone. When it's finished, you need to reboot your phone. The reboot process will take about 5-10 minutes depending on the type of rom that you flashed.
A few tips:
*Once you root, you have voided your warranty for the phone. But have no fear! Make sure you save your sdcard to your PC and run the RUU before bringing the phone for service if you need to. When service is done, you may transfer your sdcard contents from the pc back to your phone, do a quick root, and you are good to go.
*When wiping, your phone will be factory reset, meaning you have to sign into google again, redownload all your apps from the market if you have any.
*If you do like the rom of your choice, try to tweak it out the best you can, then do a nandroid (backup your phone) just in case you flash another rom. If you flash a second or third rom or whatever and didnt like it, you may do a restore on your phone, and all your info will be saved from the last nandroid you made. Be careful on how many nandroid you do. It takes up space on your sdcard. You may rename your nandroids, and remove the ones you don't want.
*The battery may get hot when flashing roms. This is normal, just try not to over do it.
*This Hero CDMA forum is now your best friend. Read and search, read and search before posting a question. Not that we don't mind answering questions, but if it has been asked 50 times, some people will give you snarky comments.
Good luck!
thanks , one more thing
Very helpful and I have successfully rooted my Hero !
Now regarding the new ROM I have downloaded the Zip file do I just copy the whole thing onto my phones sd card? If so where into the Nandroid folder?
Or do I run it using CMD from my laptop and if so know of any guides on how?
Thanks again, muchly appreciated
MB
Easiest way is you mount your phone to pc via usb, and just drop the zip file onto the root of your sdcard. Do not place the zip file anywhere else, or in any folder, just in the sdcard itself. Remount the phone, reboot into recovery, and select flash zip. Your rom should be in there to flash.
A wise man once said, "You've taken your first step into a larger world."
So happy you guys were nice with helping him. I'm finally making my switch to Android (in 3.5hrs). I can't wait to get home and root and figure it all out. Seems a TAD more difficult than it was with WinMo. There's SOOOOOO much info here, it's difficult to figure out WHERE start. But this thread helped at least figure out WHICH guide to follow initially.
Hi,
I read everything i could find and I still can't get anything to work properly on the phone.
Is there even a milestone wiki so i know which version my phone is?
I got the open recovery thing to work once, but i can't get it to work again, it keeps saying I have a cache error. what do i do?
also, when I install app2card, it totally ruins my phone, is that app meant for my phone?
I tried to install app2sd, but it keeps saying busy box permission failed something.
I got my phone thru ebay, how can i check the region?
I just know I have an unbranded milestone.
I google all these questions and nothing helpful comes up.
Can somone please tell me how to get into recover again?
Do i need to reflash it?
I only got into it once and installed the zip.
but when i try to run the zip again, i get an error.
If you have nandroid file in your sdcard,you can copy and paste (anything that is important to you) to your PC.
1. Take out your sdcard and pluck it to your PC if your Milestone cannot switch ON
2. Format your sdcard via PC
3. Extract G.O.T OpenRecovery v2.00 or Androidiani OpenRecovery 3.3 to the root of
your sdcard. (you'll see OpenRecovery folder and update.zip) Put the sdcard to your
Milestone and enter bootloader.(Press and hold volume up+camera key & power ON)
4. Open RSDlite and connect to your Milestone. Flash sbf to your Milestone,stock ROM
or 2.2.1 G.O.T beta version
Guide -> http://forum.xda-developers.com/showthread.php?t=696845
5. Your Milestone will be switch ON after flashing sbf is done. Turn it OFF and enter
into recovery. Press X button and power ON. Once you see the triangle and '!',
press volume up and camera key.
6. You'll see Recovery 2e, all letters in blue, select update and the rest is your choice.
You can nandroid backup if your Milestone works as before and restore your previous nandroid that you copy to your PC.
Yes i did that the first time and it worked.
but how can i get into it again to make a backup?
thanks
You mean you still can't get into the recovery mode after formatting your sdcard? Even with the button combination:
PRESS AND HOLD 'X' AND POWER ON THE PHONE, LET GO ONLY AFTER YOU SEE THE TRIANGLE AND '!' MARK ???
I get to the triangle.
and it get to the recover menu. but when i press install the zip again.
an error message pops up.
do i need to redo step 3 and 4 everytime i want to go into recovery menu?
what open recovery u r using? GOT or androidiani?
if its GOT then try switchin to androidiani to check if the problem presist, vice versa.
report back here if there is any improvement.
one more question:
when u enter the bootloader menu (pressing the up dpad and power key) wat bootloader version it states there?
Thanks
I'll try it out tonight been a bit busy this week.
does Flash sbf do anything to my system?
for example, will i need to reflash my current rom after doing Flash sbf?
I know for the x10 mini pro, after doing update.zip i will need to reflash the rom.
is it the same for milestone?
I still can't get it to work.
here are my steps.
My phone is already rooted.
and I already flashed the Recovery-Only SBF when i installed the new rom. (do i need to redo this step? Maybe I'm using an outdated version?)
Can someone link me to the file if there is a better one, all the links are dead.
I am using this version: vulnerable_recovery_only_RAMDLD90_78
I downloaded this:
http://groupoften.wordpress.com/2010/10/22/new-g-o-t-openrecovery-v2-01-launched/
I put the files on the root of my SD:
OpenRecovery
OpenRecovery-CFG (do i need this?)
update.zip
I press the Up dpad and power, I get the triangle thing.
I press the install.zip and still cache error?
E:can't open /ache/recovery/command
I don't get what the readme in the GOT is telling me to do.
it says:
create a folder in /OpenRecovery/recoveries ( for example "My_OR_MOD" i don't use space in folder name, to avoid problems)
does that mean I make a copy of the "openrecovery" folder and put it back inside the "openrecovery" folder? that means every thing will be duplicated? is this correct?
thanks
I would try the androidiani, but i can not find the english guide.
Edit:
just tried androidiani, and I'm still getting E:can't open /ache/recovery/command
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
So I brought myself in a bad situation.
Here's a video showing what the phone does and me trying to get into CWM:
http ://www .youtube. com/watch?v=5F2Gg_eU7Yw
I was trying to root my sony xperia z1 compact using this guide: http ://techglen. com/2014/02/05/root-xperia-z1-compact-d5503-4-3-14-2-a-1-114-official-firmware/
Following the steps it asked me to CWM 6 using this guide: http ://techglen. com/2014/02/05/install-cwm-6-on-xperia-z1-compact-d5503-4-3-14-2-a-1-114-official-firmware/2
I checked firmware and version of my phone and everything was correct.
I must admit I have no clue as to what I'm doing but I'm normally ok with tech stuff and the guide seemed detailed and trust worthy so I thought I could do it following the guide.
I got the bootloading unlocked just fine and started to install CWM. I made it this far:
- After downloading CWM kernel zip (Its not the actual name of file, just a reference name), place it in internal or external SD Card of your smartphone
- Now extract CWM kernel zip on your PC’s desktop and copy boot.img
- Paste this file inside the folder where you have installed Minimal ADB and Fastboot
- Now turn off your smartphones completely
- Plug in mobile’s USB in cable in PC port only
- Hold Volume up button and plug in USB cable in mobile’s port
- LED will turn blue (If it does not remain blue for long, then read Optional part in bootloader unlocking method explained above
- Once you are successfully in fastboot mode, then you can continue
- Now type Fastboot flash boot boot.img and press Enter
- It will flash boot.img file on your device
- Now unplug the device and boot it up
- As soon as you see purple colored LED, start pressing volume up and down buttons repeatedly, until you are in CWM mode
- In CWM Mode, select “Install Zip”
Click to expand...
Click to collapse
I downloaded CWM .img file, placed it in my ADB folder and placed a copy on my phone. Using ADB I flashed the CWM .img (bolded step), unplugged the phone and the CWM screen came up and I was able to navigate using the volume buttons. So far so good.
At this point I realized that the CWM .img file I had downloaded and placed on my phone was not a zip file and I couldn't find it. So I hit reboot to boot up my phone normally so I could place the .img packed as a .zip file on the phone. Some error message came up, but I didn't manage to read it but caught something saying root I think.
As it rebooted the sony logo came up but then the purple led turned on and it seemed to boot into CWM again. A brief screen explaining how to navigate came up as you see in the video below (but with no menu options to actually navigate) before it rebooted and repeated.
I can still use ADB and fastboot, but I can't get into CWM and I can't boot normally.
Edit: Just tried "adb devices" and it says "list of devices attached" and then it's just blank. I can't push files onto the phone (error: device not found) but I can still reboot the device fusing fastboot and there's no error when I try and reflash cwm. Reading up on this it would seem that usb debugging has somehow been turned back on so adb can't acces the phone but fastboot can. Any way to turn on usb debugging through fastboot?
I tried a forced shutdown using the off button next to the sim card but it didn't help.
The phone is not recognized by my computer so I can't place or delete files from it.
Here's a video showing what the phone does and me trying to get into CWM:
http ://www .youtube. com/watch?v=5F2Gg_eU7Yw
If I don't press the volume button it will just keep looping in the sony logo and purple led light.
What I want to do is get back to a normal boot, remove the CWM .img file and put the .img file packed as .zip file onto the phone and retry the process.
I have googled a lot of options, but most results are a year old and I hardly understand half of what is being suggested. If anyone could please walk me through the process in a language that a total idiot can understand I would be so grateful and hopefully get my sleep back.
ravneravn said:
So I brought myself in a bad situation.
Here's a video showing what the phone does and me trying to get into CWM:
http ://www .youtube. com/watch?v=5F2Gg_eU7Yw
I was trying to root my sony xperia z1 compact using this guide: http ://techglen. com/2014/02/05/root-xperia-z1-compact-d5503-4-3-14-2-a-1-114-official-firmware/
Following the steps it asked me to CWM 6 using this guide: http ://techglen. com/2014/02/05/install-cwm-6-on-xperia-z1-compact-d5503-4-3-14-2-a-1-114-official-firmware/2
I checked firmware and version of my phone and everything was correct.
I must admit I have no clue as to what I'm doing but I'm normally ok with tech stuff and the guide seemed detailed and trust worthy so I thought I could do it following the guide.
I got the bootloading unlocked just fine and started to install CWM. I made it this far:
I downloaded CWM .img file, placed it in my ADB folder and placed a copy on my phone. Using ADB I flashed the CWM .img (bolded step), unplugged the phone and the CWM screen came up and I was able to navigate using the volume buttons. So far so good.
At this point I realized that the CWM .img file I had downloaded and placed on my phone was not a zip file and I couldn't find it. So I hit reboot to boot up my phone normally so I could place the .img packed as a .zip file on the phone. Some error message came up, but I didn't manage to read it but caught something saying root I think.
As it rebooted the sony logo came up but then the purple led turned on and it seemed to boot into CWM again. A brief screen explaining how to navigate came up as you see in the video below (but with no menu options to actually navigate) before it rebooted and repeated.
I can still use ADB and fastboot, but I can't get into CWM and I can't boot normally.
Edit: Just tried "adb devices" and it says "list of devices attached" and then it's just blank. I can't push files onto the phone (error: device not found) but I can still reboot the device fusing fastboot and there's no error when I try and reflash cwm. Reading up on this it would seem that usb debugging has somehow been turned back on so adb can't acces the phone but fastboot can. Any way to turn on usb debugging through fastboot?
I tried a forced shutdown using the off button next to the sim card but it didn't help.
The phone is not recognized by my computer so I can't place or delete files from it.
Here's a video showing what the phone does and me trying to get into CWM:
http ://www .youtube. com/watch?v=5F2Gg_eU7Yw
If I don't press the volume button it will just keep looping in the sony logo and purple led light.
What I want to do is get back to a normal boot, remove the CWM .img file and put the .img file packed as .zip file onto the phone and retry the process.
I have googled a lot of options, but most results are a year old and I hardly understand half of what is being suggested. If anyone could please walk me through the process in a language that a total idiot can understand I would be so grateful and hopefully get my sleep back.
Click to expand...
Click to collapse
I hope you made a backup of your phone.
It may be worth wiping everything and flashing the Z1 stock firmware on to your phone. Stock firmwares can be found relatively easily by using Google. There are also lots of different video tutorials on YouTube on how to how to revert back to stock firmware and on how you can escape bootloops. Try this: www. youtube. com/watch?v=j4gm9VeQCHA
You're on the wrong forum, this one is for Xperia Z, for Xperia Z1 Compact go here:
http://forum.xda-developers.com/sony-xperia-z1-compact