Related
So guys.
Here is my humble CWM recovery, tested on 7 inch. Nandroid backup seems to work and flashing also. External SD card is used for reading.
Mounting of card to USB is not working yet.
Colors are now really fixed, including refresh.
Select is also now fixed and short press is working.
I am not responsible if you make some bricks to build yourself a new house. Anyhow chances of bricking are quite low, worst case is that your recovery will not boot and that's it.
I suggest that you make backup of your recovery partition before you start with dd or whatever so that you can flash it back in case something is not ok.
To flash:
Code:
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot reboot
and
Code:
adb reboot recovery
to get to recovery
In the archive is my /device folder if someone wants to play some more.
I got the CM9 ICS booting into Launcher!!!
One more in for future needs.
Great to have mate, thanks a lot for your work.
I'll tell these guys you have a working version for rhe 7",
http://forum.xda-developers.com/showthread.php?t=1473555
How can I backup? what do i have to type?
Thanks for your work!
You can make backup for example like this and if something fails you can flash it back directly in fastboot.
Code:
adb shell
su
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18
jakaka said:
You can make backup for example like this and if something fails you can flash it back directly in fastboot.
Code:
adb shell
su
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18
Click to expand...
Click to collapse
That will actually write img's to the partitions.
Backup is done this way
Code:
dd if=/dev/block/mmcblk0p8 of=/sdcard/boot_backup.img
dd if=/dev/block/mmcblk0p18 of=/sdcard/recovery_backup.img
jakaka you have sources now on utkanos git. You can contact him if you need any help to make backup to internal sdcard work.
mobilx said:
That will actually write img's to the partitions.
Backup is done this way
Code:
dd if=/dev/block/mmcblk0p8 of=/sdcard/boot_backup.img
dd if=/dev/block/mmcblk0p18 of=/sdcard/recovery_backup.img
jakaka you have sources now on utkanos git. You can contact him if you need any help to make backup to internal sdcard work.
Click to expand...
Click to collapse
Sorry you are right with the backup, I wasn't looking.
mobilx said:
That will actually write img's to the partitions.
Backup is done this way
Code:
dd if=/dev/block/mmcblk0p8 of=/sdcard/boot_backup.img
dd if=/dev/block/mmcblk0p18 of=/sdcard/recovery_backup.img
jakaka you have sources now on utkanos git. You can contact him if you need any help to make backup to internal sdcard work.
Click to expand...
Click to collapse
Thanks!
Any progress on CM9?
Technically speaking You could probably contact MR Green from Cyanogen, He is in charge of the hp touchpad Which has the same qualcomm and adreno Chipset . Just an idea
Hi, I'm following your guide and the one in http://forum.xda-developers.com/showthread.php?t=1473555&page=1, but I seem to be stuck in the installation of CWM.
I succeded in rooting the Vodafone Smart Tab 10, as busybox tells so.
Then I issued this command:
C:\Users\...\android>fastboot flash recovery v10_cwmrecovery.img
sending 'recovery' (6214 KB)... OKAY
writing 'recovery'... OKAY
Rebooting the tablet in recovery mode always gets me to the Android System Recovery <3e>: wasn't I supposed to be shown the clockworkmod recovery system? If so, what am I doing wrong?
I also tried with Utkanos' v11a version, but with the same result...
Thanks to anyone who will help me
Bye
Marco
[SOLVED] I solved using the software downloaded from http://wwwen.zte.com.cn/endata/mobile/Italy/, as suggested here http://forum.xda-developers.com/showthread.php?t=1473555&page=59. Moreover, in that same thread (some days around the ones in page 59... ) I found a suggestion about removing some system files to avoid the loading of the stock kernel. I didn't do that, but in case anyone needs it, that could be another solution
I have problem with CWM v5.8.3.4, while i flash, restore, back, everything it still back to recovery mode, can`t do nothing.
CWM v5.8.3.4 -- Here is your problem, you used ROM manager to update recovery. There are red flags on this pretty much everywhere Dx
You've gotten into the bootloop, see my PERI tool (Link in sig) and try and run the bootloop-fix there, if you can get adb working. You can also try it manually (Again, adb permitting) in roach2010's recovery touch thread, he provides the fix there.
If you can't get adb working at all, you need to NvFlash back to stock, wheelie thread is again in my signature.
Good luck.
--
By the way, you can get back into Android by Cold-booting the system. Hold volume-down, then press power and keep holding volume-down till it boots. Don't press volume-up or anything else, that'll put you back into recovery.
I was tryin` but while i want to flash someting apx turning off and can`t do nothing :/ Erm, how to fix can`t use my tablet about 1 month
Hi,
have you tried coldbooting ?
Hold power and volume down. Should get you out of recovery.
Yes, i do mate, and can`t do nothing. It dont see sd card and tablet memory :/
Okay I have the same problem, i used the cursed Rom Manager and now im stuck in the endless boot cycle, I can cold boot and I have tried to flash roachs cwm but nothing. Ive read where roach gives a code that might fix it, but i have no ideal what to do with that code or how to use it, and i see where thing o doom said the fix is in his signature but im not having much luck with that either. If you could maybe explain to me how im supposed to use roaches code or post the link that explains it here, I would sure appreciate it. Thank you.
Sent from my Transformer TF101 using XDA Premium HD app
Any ideas please? :/
Start an adb shell session with your computer connected, or in a terminal app on your tf, then run roaches fix (type it in) to the terminal app/adb shell session.
"then run roaches fix" u mean write app/adb shell session ?
And now i got another problem:
"E: Can`t mount /sdcard/
Biggest problem for now, i can`t turn on debuging :/
okay I opened terminal emulator on my tablet and typed in roaches fix exactly like it says
adb shell dd if=/dev/block/mmcblk0p3
and this popped up
*daemon not running. starting it now on port 5038*
*daemon started successfully*
error: device not found
255 [email protected]:/ $
what am i doing wrong? thank you so much for your continued help
Ive also tryed the peri and easy recovery with no luck, I think my bigest problem is i dont understand the adb thing, ive tryed searching about it and im lost.
That's the wrong dd command, dd consists of an if=/ then an of=/
Try this.
adb kill-server
adb start-server
adb devices
(you should see the tf, if not, bad drivers/not working connection, fix that first)
adb shell
su (Grant superuser permissions, if you can, and you'll see a # sign)
dd if=/dev/zero of=/dev/block/mmcblk0p3
reboot
Then flash a new recovery by:
Download and extract recoveryblob from recovery.zip
adb kill-server
adb start-server
adb devices
adb push C:\path\to\recoveryblob /sdcard/
adb shell
su (you'll get # sign again)
dd if=/sdcard/recoveryblob of=/dev/block/mmcblk0p4
reboot
I have to thank you for your patience and continued help with my problem, but with that being said I must inform you that I am still completely lost. Im not a developer and I would not even consider myself remotely knowledgeable in the subject. I was just wanting a nice custom ROM and I had found one with cyanogen mod 9 but I messed up by using the Rom manager and now I'm screwed.
I can cold boot into my tablet, and on my tablet I have this computer emulator program, which i can type in the codes you mentioned, but I'm pretty sure that is not correct. what i need is a program like that on my computer, so far I found this link regarding adb, but I'm not sure if it is right direction.....
http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
if this is the wrong direction, can you please point me in the right direction? again I am sorry for my ignorance and when this is all done I will be sure to buy you a freaking case of beer. Thank you
You can run the adb commands on your TF using the emulator app, but you'll need to directly download the recoveryblob used to flash.
Open terminal and run roach's fix (except instead of typing adb shell, you just start from su, then run the dd command from there, since you're already in the tf's 'shell')
so
su
dd if of etc
reboot
Then you'll need to reflash a recovery, so download Team Rouge's Recovery.zip then use ES file explorer app (download that) to extract the file called 'recoveryblob'. Take that file called 'recoveryblob' then copy it out of the downloads folder (still using ES file explorer) hit the favorites button then hit /sdcard/ (You don't need a microSD card to do this, /sdcard/ [For whatever reason ..] is the Internal storage. [/removable/microSD/ is the external]) then paste the recoveryblob right in /sdcard/.
Open up the terminal emulator and run
su
dd if=/sdcard/recoveryblob/ of=/dev/block/mmcblk0p4
reboot
That should give you recovery! (Then you can reflash a ROM or do whatever you need/Enjoy not having to cold-boot everytime)
Sent from my Tf101atron9000 using XDA Premium HD
Im stuck w8ing for You at Skype: )
Thanks for your info. TF now up and running without the need to cold boot. For information, I did not use a Rom Manager to flash the rom, I used CWM to flash the Gummy Rom.
I finally got my tf101 fixed and I learned something new. I just wanted to thank Thing of Doom for all of the help he offered me and without ever asking anything in return. Thanks.....
If anyone wants to know, here's what I did to fix nefem's completely FOUBAR TF101g.
First I tried NvFlash, then right at the flashing stage realized it's a tf101g Sbkv3, so that was out X.x
Then I uninstalled all the drivers and reinstalled them with PERI, got ADB working through recovery.
I had him try and flash a .zip file for a new recovery so I could run Roach's fix, but for whatever reason the CWM wouldn't mount the Internal storage (mmcblk0p7 or /sdcard/) so I manually pushed the recoveryblob to /sdcard/ and it seemed to work, but when I ran dd if=/sdcard/recoveryblob of=/dev/block/mmcblk0p4 it couldn't mount and find it.
The next thing I tried since internal was acting funky was looking at the log, I noticed that the directory was /system/sbin so I just pushed the recovery to there, adb push recoveryblob /system/sbin, then ran the same dd command with that directory and it worked. Then I just ran roach's fix normally and rebooted, he had rouge recovery!
That was the first part, his internal was still borked for some reason and Rouge couldn't mount it.
I tried various ADB mounts and they all failed, so eventually he put a MicroSD into his phone (or something else) I placed the ARHD superswipe script and a ROM w/ Guevor's kernel on there, then since rouge reads external, superwipe was able to completely format internal storage. From there it was an easy wipe and flash. Once we got a working ROM on there, we noticed that it was still getting stuck at the Eee pad logo (He could cold-boot). So I figured that his bootloader was still messed up, so we took the latest Tf101G stock blob, used the handy Rayman's blob tools to pull out the EBT (bootloader partition) blob, then directly flashed that with dd again through adb: dd if=/sdcard/blob (Removed the EBT extension, important) of=/dev/block/mmcblk0p4
Reboot, and finally it was booting optimally!
It was a tad of trial and error (The internal storage thing really had me confuzzled) but it all got fixed up in the end.
Hope this helps someone somewhere
Thing O Doom said:
If anyone wants to know, here's what I did to fix nefem's completely FOUBAR TF101g.
First I tried NvFlash, then right at the flashing stage realized it's a tf101g Sbkv3, so that was out X.x
Then I uninstalled all the drivers and reinstalled them with PERI, got ADB working through recovery.
I had him try and flash a .zip file for a new recovery so I could run Roach's fix, but for whatever reason the CWM wouldn't mount the Internal storage (mmcblk0p7 or /sdcard/) so I manually pushed the recoveryblob to /sdcard/ and it seemed to work, but when I ran dd if=/sdcard/recoveryblob of=/dev/block/mmcblk0p4 it couldn't mount and find it.
The next thing I tried since internal was acting funky was looking at the log, I noticed that the directory was /system/sbin so I just pushed the recovery to there, adb push recoveryblob /system/sbin, then ran the same dd command with that directory and it worked. Then I just ran roach's fix normally and rebooted, he had rouge recovery!
That was the first part, his internal was still borked for some reason and Rouge couldn't mount it.
I tried various ADB mounts and they all failed, so eventually he put a MicroSD into his phone (or something else) I placed the ARHD superswipe script and a ROM w/ Guevor's kernel on there, then since rouge reads external, superwipe was able to completely format internal storage. From there it was an easy wipe and flash. Once we got a working ROM on there, we noticed that it was still getting stuck at the Eee pad logo (He could cold-boot). So I figured that his bootloader was still messed up, so we took the latest Tf101G stock blob, used the handy Rayman's blob tools to pull out the EBT (bootloader partition) blob, then directly flashed that with dd again through adb: dd if=/sdcard/blob (Removed the EBT extension, important) of=/dev/block/mmcblk0p4
Reboot, and finally it was booting optimally!
It was a tad of trial and error (The internal storage thing really had me confuzzled) but it all got fixed up in the end.
Hope this helps someone somewhere
Click to expand...
Click to collapse
I am having the same exact problem as him with the same amount of programming expertise....I was woundering if you could walk me through it personally as what you've typed above seems like it's in a different language. Thanks very much in advance.
datfinedude said:
I am having the same exact problem as him with the same amount of programming expertise....I was woundering if you could walk me through it personally as what you've typed above seems like it's in a different language. Thanks very much in advance.
Click to expand...
Click to collapse
Sure if you'd like.
My Skype name is Datfinedude
Sent from my Triumph using xda premium
ABOUT:
This tutorial explains how to use adb to flash the following items starting from a UCLB3 base w/ root.
- Custom kernel w/ CWM recovery
- Modified 3e recovery
- Custom firmware (ROMS)
- Busybox
These instructions will most likely work coming from other rooted Infuse firmwares, but were tested starting from my Odin UCLB3 Unbrick package with root.
ADB SETUP:
Download: adb.zip
Download: SAMSUNG_USB_Driver_for_Mobile_Phones.exe
Setup instructions are for Windows, but adb is also available for Linux and Mac.
a.) If necessary, uninstall any previous Kies or Samsung USB Driver installations, and install the Samsung USB driver from the above download link.
b.) Unzip contents of adb.zip and copy the folder contents to C:\Windows\
c.) If your phone is booted up and running, make sure you select USB debug mode in settings. ADB also works in CWM recovery, and in modified 3e recovery.
d.) To test your installation, open a command prompt (Press WINDOWS KEY + R - type cmd - press Enter).
Type:
Code:
adb devices
If all is working, you will see your device listed.
Some quick command tips:
To move a file from your computer to the phone, "push" it:
Code:
adb push myfile.zip /directory-on-phone/
Of course, you need to be in the computer directory for your file in the command line to push it to the phone.
To get a file from your phone onto your computer, "pull" it:
Code:
adb pull /sdcard/myfile.zip
To access a command prompt for the phone:
Code:
adb shell
Inside that shell, you can use unix commands from within the Android OS to manipulate your phone.
------------------------------------------------------------
INSTRUCTIONS FOR GINGERBREAD:
(Scroll down for ICS Instructions.)
------------------------------------------------------------
Instruction steps must be followed in order.
Step 1: Use adb to install a custom kernel
Download: flash_image.zip (Extract and use flash_image for instructions below.)
You'll also need a Gingerbread kernel zImage.
Code:
adb push flash_image /data/local/tmp/flash_image
adb push zImage /data/local/tmp/zImage
adb shell
$ su
# chmod 755 /data/local/tmp/flash_image
# chmod 755 /data/local/tmp/zImage
# /data/local/tmp/flash_image boot /data/local/tmp/zImage
# reboot recovery
Step 2: Use adb to install modified 3e recovery
Necessary for Step 3.
Download: 3e_recovery_no_sig_check.zip (Extract and use recovery for instructions below.)
Code:
adb remount
adb push recovery /system/bin/recovery
adb shell "chmod 755 /system/bin/recovery"
adb reboot recovery
Step 3: Use adb to install a custom firmware
This step uses the modified 3e recovery to flash unsigned firmware.
You'll need to download the zip file for the Gingerbread (or possibly Froyo) rom that you would like to flash. These instructions have been tested by flashing my Ethereal rom.
Replace YourFirmware.zip with the actual name of your rom zip.
Code:
adb push YourFirmware.zip /sdcard/
adb remount
adb shell
# echo "boot-recovery" > /cache/recovery/command
# echo "--update_package=SDCARD:YourFirmware.zip" >> /cache/recovery/command
# reboot recovery
Let firmware flash complete, and then type:
Code:
adb reboot
EXTRA: Use adb to install busybox
Download: Busybox-1.20.2.zip (Extract and use busybox for instructions below.)
Code:
adb remount
adb push busybox /system/xbin/busybox
adb shell
# chmod 755 /system/xbin/busybox
# ln -s /system/xbin/busybox /system/bin/busybox
# /system/xbin/busybox --install -s /system/xbin
# exit
----------------------------------------
INSTRUCTIONS FOR ICS:
----------------------------------------
STEP: Use adb to flash an ICS kernel; then use blue CWM recovery to install an ICS rom.
Download: flash_image.zip (Extract and use flash_image for instructions below.)
You'll also need an ICS kernel boot.img and it is recommended that you push an ICS rom zip to your sdcard. Once you are in blue CWM recovery, you won't be able to use adb to push anything else to the device.
Replace YourFirmware.zip with the actual name of your rom zip.
Code:
adb push YourFirmware.zip /sdcard/
adb push flash_image /data/local/tmp/flash_image
adb push boot.img /data/local/tmp/boot
adb shell
$ su
# chmod 755 /data/local/tmp/flash_image
# chmod 755 /data/local/tmp/boot
# /data/local/tmp/flash_image boot /data/local/tmp/boot
# reboot recovery
From here, just follow the normal instructions for flashing your ICS rom in blue recovery.
I'll add to these instructions as I find more for ICS, and as support increases for adb in the CWM recovery we're using in ICS roms. At this time, adb support isn't fully working in Infuse ICS CWM recoveries. If you use adb to get an ICS kernel / CWM recovery combination, just use the recovery menu to do anything else. If you need to get other files onto the device while in blue CWM recovery, go to mounts and storage, mount /sdcard/, and mount USB storage.
Hope this is useful to someone else. I mainly wanted to see how much could be done with just adb, and I learned quite a bit about how the phone works in the process.
Wow my friend...nice and thx for what you provide the Infuse Community.
It is people like you, why i stay!
very nice how-to!
bigjoe2675 said:
Wow my friend...nice and thx for what you provide the Infuse Community.
It is people like you, why i stay!
Click to expand...
Click to collapse
SiL3nTKiLL said:
very nice how-to!
Click to expand...
Click to collapse
Thanks fellas. And, by the way, I know that most general users aren't going to use adb to flash kernels and firmware. It's of course easier to use all of the Heimdall one-click and Odin tools that we have - as well as the Infuse Toolkit, Heimdall suite, SGS Kernel Flasher, and CWM recovery. So, for the person asking, "Why would someone still do this, when we have all of the tools that we have?" - this isn't for you.
I approached this from the standpoint of asking, "What if we didn't have access to all of the easy tools?".
At some point, if someone is having issues with Odin and Heimdall, or if they can't use their hardware buttons, maybe they will find this useful. I like to do things from the command line and not have to touch the phone while I'm working on development stuff - plus I type fast, and since I spent years in the command line on Slackware linux, prefer using unix commands. I'm actually faster at CLI stuff than with GUI stuff, plus I like the control that CLI gives you.
I had to help a forum member restore his phone over a remote tech support session using https://join.me/ . He claimed that he couldn't get Heimdall or Odin to recognize his phone. I was able to use adb to do things from his computer, which was helpful, since I couldn't see or directly use his phone. I had to ask him to do some things on the phone, so I later wanted to figure out how to do more using just adb. That's what this is all about. If I had to help someone over a remote session now, I could do most everything without them ever touching their phone.
First of all thank you very much for the guide, but I seem to be having a problem
Whenever I try this:
Code:
adb push YourFirmware.zip /sdcard/
adb remount
adb shell
# echo "boot-recovery" > /cache/recovery/command
# echo "--update_package=SDCARD:YourFirmware.zip" >> /cache/recovery/command
# reboot recovery
the first issue is the phone reboots but continues to system and not to recovery.
now if I manually make it boot recovery, CWM gives me an error that it couldn't mount: SDCARD:update.zip
the update.zip that I'm trying to flash is CM9 RC2, also tried other zip files and also failed.
what am I doing wrong ?!
Thanks in advance.
DeepUnknown said:
First of all thank you very much for the guide, but I seem to be having a problem
Whenever I try this:
Code:
adb push YourFirmware.zip /sdcard/
adb remount
adb shell
# echo "boot-recovery" > /cache/recovery/command
# echo "--update_package=SDCARD:YourFirmware.zip" >> /cache/recovery/command
# reboot recovery
the first issue is the phone reboots but continues to system and not to recovery.
now if I manually make it boot recovery, CWM gives me an error that it couldn't mount: SDCARD:update.zip
the update.zip that I'm trying to flash is CM9 RC2, also tried other zip files and also failed.
what am I doing wrong ?!
Thanks in advance.
Click to expand...
Click to collapse
If you follow the steps correctly from Gingerbread (including the step to install modified 3e recovery), and replace "YourFirmware.zip" with the name of your firmware, these adb commands use 3e recovery to flash firmware. These flashing instructions are not for CWM recovery, and the steps you are following aren't for flashing ICS from Gingerbread. Look further down in the first post for ICS adb instructions.
Sent from my SGH-I997 using Tapatalk 2
jscott30 said:
If you follow the steps correctly from Gingerbread (including the step to install modified 3e recovery), and replace "YourFirmware.zip" with the name of your firmware, these adb commands use 3e recovery to flash firmware. These flashing instructions are not for CWM recovery, and the steps you are following aren't for flashing ICS from Gingerbread. Look further down in the first post for ICS adb instructions.
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for clearing it up. The reason why I used that method is because I looked online and I found it on another forum and the post owner didn't mention anything about it should be used with GB.
infuse CM9 rainbows
I'm caught with a half-done CM9 install of the infuse upgraded from cm7.
Somehow I was able too boot once sucessfully into CM9 though with the initial rainbow screen, but now my device hangs in recovery which is also garbled. I've been searching all over for a nice thorough guide to getting this thing going again and your post here was the only one I found remotely applicable to my situation.
I've been trying your ADB instructions for flashing with ICS but I'm stuck at second step: where I only get: cannot stat "flash-image": no such file or directory.
Since I'm stuck in CWM recovery none of the other options seems to see my device, ie. Heimdall or Odin.
Is there a better solution out of my woes?
Excuse my noobiness.
By stucked at recovery you mean it always boots up into recovery (recovery bootloop)?
You should go back to ULCB3 stock, preferably using Jscott's "option C" and flash the GB bootloaders. Then proceed to installing CM9, and remember to do a double flash. (wipes, flash, reboot, phone hangs, boot into cwm with 3-finger combo, wipe and flash!)
This way you'll solve both the recovery bootloop and the rainbows, and bring you CM9
Sent from my sweet and buttery Infuse
andros11 said:
By stucked at recovery you mean it always boots up into recovery (recovery bootloop)?
You should go back to ULCB3 stock, preferably using Jscott's "option C" and flash the GB bootloaders. Then proceed to installing CM9, and remember to do a double flash. (wipes, flash, reboot, phone hangs, boot into cwm with 3-finger combo, wipe and flash!)
This way you'll solve both the recovery bootloop and the rainbows, and bring you CM9
Click to expand...
Click to collapse
Yes the problem right now is that the only understandable thing I get out of the phone is the samsung logo at boot.
I think it goes into recovery but I can't really tell because the screen is garbled. Also using "adb reboot download" seems to make no difference to Odin or Heimdall which both refuse to see the phone.
I would love to find out exactly which state the phone is in but my knowledge of adb isn't that great to say the least.
How do I flash bootloaders using adb only?
I totally appreciate your help Andros, totally out of luck with this so far.
The only way to flash bootloaders is in download mode using either odin or heimdall.
Adb reboot download should get you into download mode as long as you have adb access while on recovery. If not, get into download mode this way:
Take out battery, and put it back in.
Hold both vol+ & vol- (don't press power)
plug in usb cable to phone.
Once in download mode, your phone should be recognized by Odin. If not, try reinstalling the drivers using the ones in the iset thread.
There are many threads about this situation that should also help you out, just search around
Sent from my sweet and buttery Infuse
Okay, somehow I missed how to use the keys to enter download state.
In my mind using adb to enter download state should be the same as the keys but somehow that isn't the case.
Got the GB bootloaders installed and used an odin package and then redid the CM9 installation.
Sorry about spamming this thread, and thanks to andros for getting me going again.
Interesting, I also didn't know that could make a difference. Lesson learned lol
Glad you got it running again
Sent from my sweet and buttery Infuse
hi , i am having serious problem ,
my i997 was ok before after doing a mess , now its in 3e reocvery restarts in samsung logo comes to 3e recovery again and so on.....i did everything ,flashed with I997UCKH1 but all in vain .
Could somebody guide what to do ?
umairrashid1 said:
hi , i am having serious problem ,
my i997 was ok before after doing a mess , now its in 3e reocvery restarts in samsung logo comes to 3e recovery again and so on.....i did everything ,flashed with I997UCKH1 but all in vain .
Could somebody guide what to do ?
Click to expand...
Click to collapse
Use odin or heimdall to repartition back to uclb3 stock.
andros11 said:
Use odin or heimdall to repartition back to uclb3 stock.
Click to expand...
Click to collapse
i used heimdall ,it flashed successfully but still no result .
how to do he same using odin ?
could you please add more steps in order o recover the phone fully .
i am in a big problem .
hello guys
I want to delete cwm (v6.0.1.9) to install twrp (v2.5.0.0).can anyone help me?
how i can delete CWM?
nasiroddin said:
hello guys
I want to delete cwm (v6.0.1.9) to install twrp (v2.5.0.0).can anyone help me?
how i can delete CWM?
Click to expand...
Click to collapse
Whoa! You don't delete a recovery Just install TWRP and it will overwrite CWM.
Follow the instructions in the TWRP thread using goomanager or download the CORRECT version for your device form the teamwin web site and use the following from a PC
rename the downloaded file to twrp.blob and reboot to the bootloader / fastboot screen
Code:
fastboot -i 0x0B05 flash recovery twrp.blob
fastboot -i 0x0B05 reboot
or from a terminal emulator on the device:
Save it to the root of your /sdcard directly (internal memory only) and rename it to twrp.blob
Launch terminal emulator or connect to your computer and open an adb shell, then type the following:
Code:
su
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
Then reboot to complete installation.
sbdags said:
Whoa! You don't delete a recovery Just install TWRP and it will overwrite CWM.
Follow the instructions in the TWRP thread using goomanager or download the CORRECT version for your device form the teamwin web site and use the following from a PC
rename the downloaded file to twrp.blob and reboot to the bootloader / fastboot screen
Code:
fastboot -i 0x0B05 flash recovery twrp.blob
fastboot -i 0x0B05 reboot
or from a terminal emulator on the device:
Save it to the root of your /sdcard directly (internal memory only) and rename it to twrp.blob
Launch terminal emulator or connect to your computer and open an adb shell, then type the following:
Code:
su
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
Then reboot to complete installation.
Click to expand...
Click to collapse
thanks
now I install twrp and i want to update from jb 4.1 to jb 4.2 and i downloaded jb 4.2 frimware (WW_epad-user-10.6.1.14.8) from asus global site.can you help me how to update my tablet to this version?(my tablet is unlocked so suggest me a way that doesn't cause a (hard or soft) brick) thanks a lot
nasiroddin said:
thanks
now I install twrp and i want to update from jb 4.1 to jb 4.2 and i downloaded jb 4.2 frimware (WW_epad-user-10.6.1.14.8) from asus global site.can you help me how to update my tablet to this version?(my tablet is unlocked so suggest me a way that doesn't cause a (hard or soft) brick) thanks a lot
Click to expand...
Click to collapse
You can just flash the update file from TWRP. You will loose your custom recovery and root if you flash the stock rom. So you would have to re-install TWRP and root again.
If you come from any kind of custom rom it's highly recommended to do a clean install of the stock rom. Wipe everything, don't restore apps from a backup (their data should be ok to restore), install all your apps from the Play Store.
Sent from my DROID4 using Tapatalk 2
This will Wipe every thing on the internal storage SO BACKUP your stuff on the SD card and maybe the onto computer too
This is for the Google edition of the Galaxy S4
Go To setting / about phone /
Tap "Build Number" 7 times
Go back to Main Settings Menu and under now shown "Developer Options" enable "USB debugging"
Download this
http://developer.android.com/sdk/index.html#download
extract to the C drive in the folder adb (you can move it anywhere just adjust the path)
run "SDK Manager.exe"
in the extras select "Google USB Drivers"
click "Install 1 package" and accept license / Install
now go into the device manager on you PC and change the "Samsung ADB driver" to the
"Android Composite ADB Interface" located in this folder
C:\adb\sdk\extras\google\usb_driver
you will have to force that driver to install by selecting it
let it finish installing the drivers
then
unplug and then plug in the USB on the phone
your phone will ask you about "Allow USB debugging?"
check the box "always allow from this computer"
click OK on your phone
If this doesn't work the some thing is wrong with the drivers and reinstall the drivers make sure you select "Android Composite ADB Interface" and not "Android ADB Interface"
Now open up a command prompt (I did this as "run as administrator")
type "cd C:\adb\sdk\platform-tools" (or what ever the directory you extract your files)
enter this command
adb reboot bootloader <enter>
Once in bootloader,
In the command prompt type:
fastboot oem unlock <enter>
It will ask you to unlock you phone and this may void you warranty
Use the volume buttons to change to yes and the power button as enter
At this point everything gets wiped on your phone
The phone rebooted back into bootloader and it now said "bootloader=unlocked" and the bottom left of the screen
Reboot the phone and the unlock icon will appear on the 1st Google screen.
the phone will boot into android like it was new
I have not done any ODIN on my phone so i don't know how this affect it
I am trying to avoid ODIN and get the phone rooted and have a custom recovery on it.
I just did this on my phone and typed this up i think everything is accurate let me know if i need to adjust anything.
fyi the command "fastboot flash recovery recovery.img" don't work because the system is still secure boot enable.
Thanks and Questions
Thanks. Could you please tell where you found this info?
Also, I'm not that experienced and don't understand why this is necessary. Don't our GT-i9505G phones come with unlocked boot loader?
bsam55 said:
Thanks. Could you please tell where you found this info?
Also, I'm not that experienced and don't understand why this is necessary. Don't our GT-i9505G phones come with unlocked boot loader?
Click to expand...
Click to collapse
It still needs to perform fastboot oem unlock just like nexus device does
Sent using GT-i9505~
This is what i did on my galaxy nexus device (nexus 3) and my friend nexus one
I made this from my notes of the old devices
my experience is that i could mess up my phone and lock me out of it it, so i wanted to be sure i could fix it, that is why i did this
I did not try to use fastboot beforehand, so it could work.
but i have a feeling that the ODIN flash changed the bootloader (probably not)
but i have been screwed buy a odin flash messing with the bootloader on the vibrant( but for some reason there looked to be 3 bootloader on that device)
if some one want to try it
just put the ClockworkMod 6.0.3.3 recovery file the
C:\adb\sdk\platform-tools
adb reboot bootloader
fastboot boot recovery.img
this dose take 1 minute after the file is sent to reboot and load
I have tried TWRP but it don't load past the first screen.
This just boots into the file and doesn't change anything
access to the sd cards don't work
I am tempted to flash ClockworkMod but i would like to pull a copy of the recovery first.
BTW after paying $700 for a phone i want to be sure to be able to reinstall the OS, like on a PC.
warwolfx0 said:
This is what i did on my galaxy nexus device (nexus 3) and my friend nexus one
I made this from my notes of the old devices
my experience is that i could mess up my phone and lock me out of it it, so i wanted to be sure i could fix it, that is why i did this
I did not try to use fastboot beforehand, so it could work.
but i have a feeling that the ODIN flash changed the bootloader (probably not)
but i have been screwed buy a odin flash messing with the bootloader on the vibrant( but for some reason there looked to be 3 bootloader on that device)
if some one want to try it
just put the ClockworkMod 6.0.3.3 recovery file the
C:\adb\sdk\platform-tools
adb reboot bootloader
fastboot boot recovery.img
this dose take 1 minute after the file is sent to reboot and load
I have tried TWRP but it don't load past the first screen.
This just boots into the file and doesn't change anything
access to the sd cards don't work
I am tempted to flash ClockworkMod but i would like to pull a copy of the recovery first.
BTW after paying $700 for a phone i want to be sure to be able to reinstall the OS, like on a PC.
Click to expand...
Click to collapse
Maybe you can do a full dump for the community.
before you install custom recovery, I'd like to ask if you could do complete system dump of your device, including stock recovery (recovery.img), stock bootloader (boot.img) and system.img . It would be a big help to the community. You can do it simple after rooting with for example Motochopper exploit (described here http://whatswithtech.com/how-to-root-samsung-galaxy-s4/ )
Then something like this:
Code:
for gaining root access type: su
then:
copy BOOT -> dd if=/dev/block/mmcblk0p20 of=/sdcard/boot.img bs=4096
copy HIDDEN -> dd if=/dev/block/mmcblk0p27 of=/sdcard/hidden.img bs=4096
copy PARAM -> dd if=/dev/block/mmcblk0p19 of=/sdcard/param.bin bs=4096
copy RECOVERY -> dd if=/dev/block/mmcblk0p21 of=/sdcard/recovery.img bs=4096
copy SYSTEM -> dd if=/dev/block/mmcblk0p16 of=/sdcard/system.img bs=4096
Thanks a lot!
System Dump
Plus One on the system dump. There are a lot of knowledgeable people waiting to help as soon as they have this. I don't know enough to do it and did try CWM (which doesn't work, by the way.)
Hope you are able to help. Thanks
bmbm said:
before you install custom recovery, I'd like to ask if you could do complete system dump of your device, including stock recovery (recovery.img), stock bootloader (boot.img) and system.img . It would be a big help to the community. You can do it simple after rooting with for example Motochopper exploit (described here http://whatswithtech.com/how-to-root-samsung-galaxy-s4/ )
Then something like this:
Code:
for gaining root access type: su
then:
copy BOOT -> dd if=/dev/block/mmcblk0p20 of=/sdcard/boot.img bs=4096
copy HIDDEN -> dd if=/dev/block/mmcblk0p27 of=/sdcard/hidden.img bs=4096
copy PARAM -> dd if=/dev/block/mmcblk0p19 of=/sdcard/param.bin bs=4096
copy RECOVERY -> dd if=/dev/block/mmcblk0p21 of=/sdcard/recovery.img bs=4096
copy SYSTEM -> dd if=/dev/block/mmcblk0p16 of=/sdcard/system.img bs=4096
Thanks a lot!
Click to expand...
Click to collapse
cool thank i was looking for that info
Just i couldn't get su to work in adb
I have been able to get Supersu (also tried superuser) on the phone but it complains about the su binaries (busybox in superuser) not being installed i have tried to install it using the market app (which said i am rooted) but i get no popup on the system.
i might try a wipe to see if that fixed it. (i did flash root to the system so it should still be there after a wipe)
first root, then system dump
unless someone knows how to do a system dump without root? or temp root solution.
I will look into the motochopper later today
you don't need "su" to work in adb shell, if you run "adb root" and "adb remount" with a modified adbd binary (inside CWM for example) you will have root access.
pls try out this root zip I just made, maybe it will work
warwolfx0 said:
QUOTE]
DELETed
Click to expand...
Click to collapse
I have root
Thanks broodplank1337
download the root that "broodplank1337" made
and put it in "C:\adb\sdk\platform-tools" (this is my adb.exe folder)
Download ClockworkMod 6.0.3.3 NORMAL from below
http://forum.xda-developers.com/showthread.php?t=2359132&highlight=recovery
aka Miustone_CWM_flash-NORMAL.zip
extract the recovery.img to the folder "C:\adb\sdk\platform-tools"
Now open up a command prompt (I did this as "run as administrator")
type "cd C:\adb\sdk\platform-tools" (or what ever the directory you extract your files)
enter this command
adb reboot bootloader <enter>
Once in bootloader,
In the command prompt type:
fastboot boot recovery.img (this takes 1min to load after the file is sent)
This will boot into ClockworkMod
goto "install zip"
goto "install zip from sideload"
in the cmd type
adb sideload root.zip
This sends to the phone and write to the phones Rom.
Now reboot and we have root without ODIN on a I9505G
BTW my file was missing busybox in the xbin i was playing around with "CWM-SuperSU.zip" as a base
It is kind of late so i may have missed some things in this write up.
Now off to the system dump.
I will repost this later as a new post to keep this clean.
ok i had some issues with viewing the files on the phone
i moved them to the sdcard and then pulled them off the card on my pc using a "sd to usb"
dd if=/dev/block/mmcblk0p20 of=/storage/extSdCard/dump/boot.img bs=4096
dd if=/dev/block/mmcblk0p27 of=/storage/extSdCard/dump/hidden.img bs=4096
dd if=/dev/block/mmcblk0p19 of=/storage/extSdCard/dump/param.bin bs=4096
dd if=/dev/block/mmcblk0p21 of=/storage/extSdCard/dump/recovery.img bs=4096
dd if=/dev/block/mmcblk0p16 of=/storage/extSdCard/dump/system.img bs=4096
Is there any other mmcblk0p i should backup
and is there any issues with posting this info on this forum
so far this only has root
i did notice that clockworkmod did give me access to root but i couldn't find the sd card while fastbooting it.
I don't think that the whole bootloader is part of what i backup, I thought there was a sbl.bin that i need too.
warwolfx0 said:
ok i had some issues with viewing the files on the phone
i moved them to the sdcard and then pulled them off the card on my pc using a "sd to usb"
dd if=/dev/block/mmcblk0p20 of=/storage/extSdCard/dump/boot.img bs=4096
dd if=/dev/block/mmcblk0p27 of=/storage/extSdCard/dump/hidden.img bs=4096
dd if=/dev/block/mmcblk0p19 of=/storage/extSdCard/dump/param.bin bs=4096
dd if=/dev/block/mmcblk0p21 of=/storage/extSdCard/dump/recovery.img bs=4096
dd if=/dev/block/mmcblk0p16 of=/storage/extSdCard/dump/system.img bs=4096
Is there any other mmcblk0p i should backup
and is there any issues with posting this info on this forum
so far this only has root
i did notice that clockworkmod did give me access to root but i couldn't find the sd card while fastbooting it.
I don't think that the whole bootloader is part of what i backup, I thought there was a sbl.bin that i need too.
Click to expand...
Click to collapse
can you please upload your system dump , thank you mate
warwolfx0 said:
Thanks broodplank1337
download the root that "broodplank1337" made
and put it in "C:\adb\sdk\platform-tools" (this is my adb.exe folder)
Download ClockworkMod 6.0.3.3 NORMAL from below
http://forum.xda-developers.com/showthread.php?t=2359132&highlight=recovery
aka Miustone_CWM_flash-NORMAL.zip
extract the recovery.img to the folder "C:\adb\sdk\platform-tools"
Now open up a command prompt (I did this as "run as administrator")
type "cd C:\adb\sdk\platform-tools" (or what ever the directory you extract your files)
enter this command
adb reboot bootloader <enter>
Once in bootloader,
In the command prompt type:
fastboot boot recovery.img (this takes 1min to load after the file is sent)
This will boot into ClockworkMod
goto "install zip"
goto "install zip from sideload"
in the cmd type
adb sideload root.zip
This sends to the phone and write to the phones Rom.
Now reboot and we have root without ODIN on a I9505G
BTW my file was missing busybox in the xbin i was playing around with "CWM-SuperSU.zip" as a base
It is kind of late so i may have missed some things in this write up.
Now off to the system dump.
I will repost this later as a new post to keep this clean.
Click to expand...
Click to collapse
I maybe wrong in this, but I have played with fastboot on my ex HTC device. the proper command to flash recovery is
Code:
fastboot flash recovery recovery.img
the proper command to flash kernel is
Code:
fastboot flash boot boot.img
with
Code:
fastboot boot recovery.img
, the recovery isn't permanent. it will be only be there for the current session. after rebooting, the stock recovery will overwrite the custom recovery. the same goes to kernel.
Sent from my GT-I9505 using Tapatalk 2
warwolfx0 said:
ok i had some issues with viewing the files on the phone
i moved them to the sdcard and then pulled them off the card on my pc using a "sd to usb"
dd if=/dev/block/mmcblk0p20 of=/storage/extSdCard/dump/boot.img bs=4096
dd if=/dev/block/mmcblk0p27 of=/storage/extSdCard/dump/hidden.img bs=4096
dd if=/dev/block/mmcblk0p19 of=/storage/extSdCard/dump/param.bin bs=4096
dd if=/dev/block/mmcblk0p21 of=/storage/extSdCard/dump/recovery.img bs=4096
dd if=/dev/block/mmcblk0p16 of=/storage/extSdCard/dump/system.img bs=4096
Is there any other mmcblk0p i should backup
and is there any issues with posting this info on this forum
so far this only has root
i did notice that clockworkmod did give me access to root but i couldn't find the sd card while fastbooting it.
I don't think that the whole bootloader is part of what i backup, I thought there was a sbl.bin that i need too.
Click to expand...
Click to collapse
NONE of this would pull anything of relation from the I9505G (except System - mmcblk0p16) as our partitions layout is completely different. And more so, it would softbrick your 9505 if you tried flashing.
Check out here - http://forum.xda-developers.com/showthread.php?t=2360346 - for a system dump from the i9505G. It has SYSTEM/BOOT/RECOVERY. Param and Hidden are both empty on our phones. This has already been used a couple times to cook roms for other S4 devices.
donovanbrock said:
NONE of this would pull anything of relation from the I9505G (except System - mmcblk0p16) as our partitions layout is completely different. And more so, it would softbrick your 9505 if you tried flashing.
Check out here - http://forum.xda-developers.com/showthread.php?t=2360346 - for a system dump from the i9505G. It has SYSTEM/BOOT/RECOVERY. Param and Hidden are both empty on our phones. This has already been used a couple times to cook roms for other S4 devices.
Click to expand...
Click to collapse
Since my backup might mess people up i am not going to post it.
but as a backup i will make a full backup of all the mmcblk0pxx file
dd if=/dev/block/mmcblk0pxx of=/storage/extSdCard/dump/mmcblk0pxx.img bs=4096
i think there is like 20 files
Those with a real I9505G google edition samsung, do u have an option in settings to always have the lightkeys light up when screen is on? The menu and the back key, that light up.
hmmm followed step bye step but phones boot loader is still locked
i do have Super User access tho
edit: fail on my part. everything worked smoothly! thanks man!
Hello. Please help me. Can I flash stock ROM GT-I9005 on my Google Edition phone GT-I9005G? Thank for answer
SnegovikRZN said:
Hello. Please help me. Can I flash stock ROM GT-I9005 on my Google Edition phone GT-I9005G? Thank for answer
Click to expand...
Click to collapse
no