Related
I see often in the forums the questions of newbies about flashing a new stock or custom ROM. What steps are needed to be safe, how to backup data, …..
I created a short tutorial with links to some essential tools named "Steps to flash a new ROM"
It describes the 4 steps you need to know before flashing a new ROM:
1) Backup your system
2) Backup your applications
3) Different ways to flash a ROM
4) How to restore if something goes wrong
Hope it helps some forum members.
Hi folks. I have tried the Odin process three times to try to get CWM functioning on my I/O tab with no luck.
The actual Odin process seems to work fine; however, when I reboot the tab to enter recovery mode; I never get the recovery option. I only have the USB symbol and the downloading option. Also, in the upper left corner, I have:
Fastboot USB download protocol
bootloader version unknown
baseband version %s
serial number:
lock state unlocked
What am i missing? Can the I/O tab use CWM?
Thanks!!
I had the same thing, but when I am trying to root the device it just lock on boot screen. I am not a dummy but something is wrong where several users have diffrent symptoms. I would wait until further development is done. This is still a little shaky.
Odin CWM doesn't work for some reasons ..
Use this post to get rooted
http://forum.xda-developers.com/showpost.php?p=15735928&postcount=2
Follow the instructions carefully !!
Download CWM and do an Install on CWM (it will install 4.0.0.4)
copy the required files to the root directory /sdcard/ (main directory if you don't know)
-Get the roms from HERE
-Get the su_busybox_misc-sam_tab_10.1-051511 HERE
Flash in the ROM 1st .. the apply the SU update (in RECOVERYMOD BEFORE you reboot)
Data / wipe
THEN REBOOT
I missed that 2nd update zip .. and trust me its a pain to get it rooted after that ..
The same procedure will not work again once you're on TW3.1 rom .. you will need an image of the system files and NVflash now..
BTW if you can do NVflash .. then I can send you the image files for 3.1TW rooted ..
fgarcia25 said:
I had the same thing, but when I am trying to root the device it just lock on boot screen. I am not a dummy but something is wrong where several users have diffrent symptoms. I would wait until further development is done. This is still a little shaky.
Click to expand...
Click to collapse
Ha .. I have 3 IO to play with (from friends)..
1st one is rooted out of the box ..
2nd one cannot communicate on FASTBOOT
3rd one does everything nicely (thats the one I had the image extracted with NVFlash)
I'll say it nicely before someone comes to say it rudely, this probably belongs in a general section rather than the development section (that is, until you develop a method to get around the restriction you've found )
Workaround method
http://forum.xda-developers.com/showpost.php?p=16196597&postcount=3
Plus I have the images to go with in case you brick yours
bill.allrobots.org said:
I'll say it nicely before someone comes to say it rudely, this probably belongs in a general section rather than the development section (that is, until you develop a method to get around the restriction you've found )
Click to expand...
Click to collapse
If you have fastboot working, then rooting is as simply as 'fastboot boot [cwm recovery filename].img'
I spent a long time getting fastboot to work, but the only fix was to finally download PDANET software to my PC and install it while it was connected to my tab. After that I got fastboot working.
Fastboot made the rooting process 100% easier. You can root any stock ROM with it and not have to reflash to 3.0.1.
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums and Read THIS
Moving to General
I had the same problem with my I/O. I finally got a recovery option. What I did was flash the Euro version of TW located in the development section (which is buggy as ****).. After that I Installed CWM and flashed pershoot's root tools. Then I flashed the latest TW Rom. Everything is running smoothly, despite the samsung apps fc. Be weary of the disclaimers located on all the sections I have suggested. All of these steps are at your own risk...
Odin worked on my I/O tab after i put TW on it. I had to boot the tab into CWM via fastboot from a mac
I can't post in the development forums so I figured I would ask here:
I understand how to use adb and fastboot, etc.. What I am missing is with the new ICS ROM it states that I must "fastboot flash system system.img"; however none of the ICS zip file I have seen come with a system.img file (just the boot.img).
Am I missing something? Any help would be greatly appreciated..
I used the version available on Rootzwiki... not sure if thats the answer you wanted. I'm running 4.0.3 ICS on my wifi XOOM OC to 1.54. No FC's, reboots or anything of the sort. You'll need to be sure that you have su-install.zip, and other img files needed. As I said, you'll find them all on the rootzwiki website under xoom hope this helps, if not good luck.
You are talking about two different things here. I don't know where to start here you're all mixed up. There are several ways to flash a ROM, you can fastboot flash the .img files such as what you are referencing to. Or you can flash an update .zip file from recovery. The way you flash the ROM depends on the source, if its a bunch of *.img files you use fastboot, if it's a *.zip file you use recovery. Just follow the directions given for installation that are provided with the ROM you are downloading.
sboehler said:
I can't post in the development forums so I figured I would ask here:
I understand how to use adb and fastboot, etc.. What I am missing is with the new ICS ROM it states that I must "fastboot flash system system.img"; however none of the ICS zip file I have seen come with a system.img file (just the boot.img).
Am I missing something? Any help would be greatly appreciated..
Click to expand...
Click to collapse
Hello, and welcome to XDA! =] Anyways on with your question. There are two ways to flash a ROM to your xoom. One being fastboot/adb, where you use the command line on your computer to send commands to your device and make it do stuff. This is where you use system.img, boot.img, recovery.img.
The second, is CWM (ClockWorkMod recovery) This, as far as im aware, is the most common way. This is where the .zip's come in. Because you take the .zip you put it on your external SD card. boot into recovery (after flashing CWM of course) and flash the rom. CWM is nice because you can also make a 100% snapshot of your internal memory state via making a nanodroid back up. That way if anything messes up you have a 100% backup you can restore at anytime if you need it.
In a nutshell, You use *.img files with fastboot and .zip files with CWM.
Anyways. If you're new to rooting. Please check out these two threads, They'll help you get started. =]
Xoom Heaven: Root+Non Root Users Are Welcome!
[Guide] Setting up and using adb/fastboot-unlock, flash custom recovery & root
The second guide I did use to flash my own zoom so I can assure you it does work.
Hi there,
I recently got a Note from work, coming from two years of a Galaxy S, I understood most of the "scene" for the Note, but learned new stuff such as the dreaded 0x19 eMMC bug and Yellow Triangle (counter) when flashing via ODIN. Those things were new to me until now.
So, last night, I've spent it whole (from 2 AM to 7 AM) trying to make this work, figuring out a safe way to wipe a ICS that was filled with unsuccessful roots and left overs from previous flash. After searching, reading a lot, understanding and connected all together logically, I did it this way. Here it goes, hope it helps, since I've seen a lot of people having trouble to root this.
The premise is to start fresh with a wiped phone and go as straight as possible to ICS LQ3. If you don't want to wipe, you could avoid those steps and work around them. I wanted to share what I did so others could do it easier.
All these steps are just because LQ3 is too big to directly root (0 MB left in ROM, acording to Titanium Backup), so you have to work your way towards that.
Let's begin:
1) Flash N7000XXLC1_N7000OXALC1 Open Europe WIPE, Pre Rooted from this thread from bodivas via ODIN PC. Look for "LC1" and download it from HotFile.
What this achieves is to go back to a safe GB stock ROM & Kernel where you can safely wipe the phone via Recovery, plus it's a wipe ROM that'll do that too just when installed. This wont give you the yellow triangle or increase your custom flash counter, so don't worry.
2) Configure Play Store to download or side load the Mobile ODIN from ChainFire. I think you'll need the paid version, since I'm using the EverRoot option here, available only there.
3) Flash N7000XXLQ3 from this thread by dr.ketan or directly from SamMobile.com with Mobile ODIN with settings: Enable EverRoot, Inject Superuser (SuperSU), Inject Mobile ODIN and (optionally) Wipe data and cache and Wipe Dalvik cache for a "cleaner" migration to that new LQ3
* I've noticed that sometimes, after wiping data with Mobile Odin, you might get the "null null" error when typing with the keyboard, since it messes the CSC. What you have to do is reflash CSC (called "Cache" in Mobile Odin) without wiping again
This will flash the new LQ3 version while mantaining a partial root from the previous firmware.
4) Now if you go and open SuperSU it would say that there's a problem with the SU binary and can't be solved. What this means is that there's 0 space left in the ROM for it to update, so we need to solve this.
What you have to do is get Titanium Backup or a similar app to remove some system app and make space. What I've chosen to delete is "Setup Wizard 1.3" that is the wizard you first saw when you flashed your new firmware, so surely you won't be needing it again. It frees about 2 MB of space, but you could be deleting any other app instead of that one if you wanted.
5) Flash CF-Root-SGN_XX_SEB_LQ3-v5.6-CWM5 from this thread from ChainFire, or any other kernel of your choice, to install CWM and the latest SuperSU.
6) When the phone starts again, open SuperSU and it wil prompt it to update the binary.
Voilá! Everything is done: now you are in LQ3 with full root, SuperSU correctly working and with CWM installed. From now on, any new firmware that has a fully loaded ROM should work the same way to root.
Enjoy and hope this helped somebody out there Any questions, please let me know.
Regards,
Or http://forum.xda-developers.com/showthread.php?t=1647148. I tried it in lq3.
That obviously didn't work, was the first thing to try and there was not enough space for the Binaries to install, so at best you get a partial root, as worst (me) get no root at all and no chance to free any space for further rooting
Why not flashing CSC, CF-Kernel and LQ3 simultaneously? I did this and didn't need to inject or delete something. Just a sidenote
You could combine those flashes, that's correct, but what I wrote was what I did, each step producing one result in order to be able to trace the errors and know (if something) was working incorrectly or producing good results, and be able to pinpoint what it was.
I thought of this after several tries of other methods that failed, so this is a step by step (as title says) to root it, for people who stumbles upon the same problems I and many other have.
Partial Root?
There is not such thing as partial root. In the event that you have trouble pasting into /system, you have a corrupted /system partition. (not partial root)
To fix it:
Connect your phone to the computer via usb.
Ensure that your phone is recognized by ADB in command prompt by typing adb devices (ADB should respond with your device info)
Enter adb shell
Then enter the following syntax in adb shell:
#dd if=/dev/zero of=/dev/block/mmcblk0p9 bs=1M count=1
*ensure there is no typos when inputting code as it could cause damage to the device.
Reboot your device into CWM (make sure you are on a safe kernel/recovery!, preferably Abyss 4.2)
Now format /system under Mounts and Storage (/system will not mount automatically which will allow you to format your corrupted /system partition properly.)
Then perform Full Wipe (Factory Reset, Wipe Cache, Wipe Dalvik Cash)
Flash your desired Rom (let it settle) and you will be able to edit your /system again!!!
**** This info was provided by Entropy somewhere on the forum *****
Thanks for your comments,
By partial root I meant that root could be achieved but the SuperSU apk would give the error because of the lack of space. Maybe the term used wasn't the best
Dan_Aykroyd said:
That obviously didn't work, was the first thing to try and there was not enough space for the Binaries to install, so at best you get a partial root, as worst (me) get no root at all and no chance to free any space for further rooting
Click to expand...
Click to collapse
someone else figured the same thing as mentioned here:
http://forum.xda-developers.com/showpost.php?p=27527694&postcount=1811
which lead to this advise from the wise old Dr...
http://forum.xda-developers.com/showpost.php?p=27532325&postcount=1813
which in turn lead to this but some kind soul
http://forum.xda-developers.com/showpost.php?p=27533257&postcount=1814
Ok. I had DDLB2,
Downloaded XXLQ3 - Flashed over PC odin
Downloaded Chainfire CF-ROOT LQ3 Kernel from the Thread
Flashed that over PC Odin as well
Switched ON the Phone
Downloaded Triangle Away, Said it needed a Support file, Downloaded it,
- Rebooted in a special mode, Cleared status.
Switched ON phone, did a Factory Reset.
So far Everything is Good, and I have Root Access as well.
I have edited post and added modded SuperSu busybox installer
Read This
http://forum.xda-developers.com/showpost.php?p=26455511&postcount=2475
(edited at end of rooting instruction)
dr.ketan said:
I have edited post and added modded SuperSu busybox installer
Read This
http://forum.xda-developers.com/showpost.php?p=26455511&postcount=2475
(edited at end of rooting instruction)
Click to expand...
Click to collapse
Was post #3 of that thread also updated Dr.?
The reason I asked was that there was no msg in the post #3 mentioning a
18june12 update.
Thanks
i hav updated at two place, bith place i hav mentioned date. rest are old.
Sent from my GT-N7000 using xda premium
dr.ketan said:
I have edited post and added modded SuperSu busybox installer
Read This
http://forum.xda-developers.com/showpost.php?p=26455511&postcount=2475
(edited at end of rooting instruction)
Click to expand...
Click to collapse
I've saw the SuperSU Market update today, saw the "Fix some installation problems" log and wondered if it was related to this.
I don't need to try it now again, but I'm glad this was worked out. Hopefully it installs OK now but, what does it do to free space?
what i underatand by reading script
it moves google map and youtube before installing su binarry, then again it replaces map n youtue, now if space will remain low, map or youtube or both won't get install, then you can install it from market.
Sent from my GT-N7000 using xda premium
Before you do anything else, make a backup. do it now.
don't even read anything else until you've done that.
seriously. stop reading. make a back up. you reading this means you're getting ready to start flashing things when you don't know if it will work.
download the modified script OTA for 38R from
here
courtesy jaggy
download
CMKeyguard.apk
from
http://s000.tinyupload.com/?file_id=06718662084607714036
(thanks to ethanmars)
and follow the instructions on the side of the download page
after you follow the instructions regarding cmkeyguard, as written on it's download page from the link i provided,
reboot into recovery
flash the modified script OTA for 38R
at this point, i flashed a superuser zip (i use supersu, but superuser would probably work. i flashed this 'just in case'. i don't know if it works if you do not flash it)
i also flashed the 61 gold AK kernel for the 11S here
AK is a great developer. probably the most responsive one from whom i've heard this dude
anyway, that worked. before trying to flash 38R, i was running 33R with ak, and a modified lockscreen using this method thanks to this guy.
happy hunting.
this worked for me.
this worked after other methods would fail. i had to go through multiple restores.
my problem was that i was running the 'custom' slide screen on stock 11s, but modified as per
this thread
by this guy
i had been getting multiple 'cmlockscreen' failures, preventing it from booting properly.
Damnnnnnn i did not realise your thread.... I did a clean flash of 38R instead..... But still great work for putting this up!
After a half day war with this update yesterday, i've succeded by doing almost the same you say. by the way, thanks for the tips.
after 2 hours try fixing yesterday, I found the solution thanks to Vomer post, flashing throught fastboot the system, boot and twrp img... :angel:
timothydonohue said:
Before you do anything else, make a backup. do it now.
don't even read anything else until you've done that.
seriously. stop reading. make a back up. you reading this means you're getting ready to start flashing things when you don't know if it will work.
download the modified script OTA for 38R from
here
courtesy jaggy
download
CMKeyguard.apk
from
http://s000.tinyupload.com/?file_id=06718662084607714036
(thanks to ethanmars)
and follow the instructions on the side of the download page
after you follow the instructions regarding cmkeyguard, as written on it's download page from the link i provided,
reboot into recovery
flash the modified script OTA for 38R
at this point, i flashed a superuser zip (i use supersu, but superuser would probably work. i flashed this 'just in case'. i don't know if it works if you do not flash it)
i also flashed the 61 gold AK kernel for the 11S here
AK is a great developer. probably the most responsive one from whom i've heard this dude
anyway, that worked. before trying to flash 38R, i was running 33R with ak, and a modified lockscreen using this method thanks to this guy.
happy hunting.
this worked for me.
this worked after other methods would fail. i had to go through multiple restores.
my problem was that i was running the 'custom' slide screen on stock 11s, but modified as per
this thread
by this guy
i had been getting multiple 'cmlockscreen' failures, preventing it from booting properly.
Click to expand...
Click to collapse
Hi there! Today i had the OTA finally on my way but i had the modified lockscreen. I then came across your post and i tried to follow your step but with no luck:
1) the link to the OTA are just member profile but i think i can find the modified ones in the "official" thread in here
2)when i tried to perform the action listed in the page you linked to the CMkeyguard.apk i cannot delete the apk from my phone and i don't know how to do it from the PC. I tried then to flash it with the .zip provided by NunHugger (the creator of the modified lockscreen) but still no luck with the original update.
there is a way to perform the ota directly from the updater on the phone or i have to do it from the TWRP with the modified one only?
Also, reading through the thread of the lockscreen, i've read that i can perform a flash of boot.img... question is where to find it?
EDIT: I found the boot.img into the toolkit, so if i perform a flash it should be all back to normal without loosing any data, am i right?
Thank you!
FatPiNi said:
Hi there! Today i had the OTA finally on my way but i had the modified lockscreen. I then came across your post and i tried to follow your step but with no luck:
1) the link to the OTA are just member profile but i think i can find the modified ones in the "official" thread in here
2)when i tried to perform the action listed in the page you linked to the CMkeyguard.apk i cannot delete the apk from my phone and i don't know how to do it from the PC. I tried then to flash it with the .zip provided by NunHugger (the creator of the modified lockscreen) but still no luck with the original update.
there is a way to perform the ota directly from the updater on the phone or i have to do it from the TWRP with the modified one only?
Also, reading through the thread of the lockscreen, i've read that i can perform a flash of boot.img... question is where to find it?
EDIT: I found the boot.img into the toolkit, so if i perform a flash it should be all back to normal without loosing any data, am i right?
Thank you!
Click to expand...
Click to collapse
ah, you're right. i fixed my link to the post with the modified script.
in order to delete the file cmkeyguard.apk, you need a file browswer with root access. i use es file explorer (among others).