Database Info

[Q] Phone stuck in boot loop - trying to update from fastboot. help needed!

Hi,
Last Friday I turned my phone off and when I turned it back on it got stuck on the loading screen and has been like that since.
I tried removing the battery loads, with no joy. I tried factory reset and clearing cache through the recovery menu, still nothing. So now I want to flash it but I'm having trouble.
I can't get the phone to boot so can't use adb to push a file to the sdcard and I'm stuck with fastboot commands (which I'm not that familiar with other than what I've found on here!). I downloaded the OTA update (from links found in these forums) for my phone to take it to 4.0.3 as I thought it was worth doing. I renamed it to update.zip but when I try the command "fastboot update update.zip" I get the message:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
I then tried the full ROM from this thread: http://forum.xda-developers.com/showthread.php?t=1063664
but got the same message.
I don't know what these missing files are, or if I can create them myself! I've found other threads where people said they used replacements found elsewhere but I don't know where to find them!!
I can't find a way to get the update file onto the sdcard so can't use that recovery option.
I'd rather not have to send it back to samsung as that takes two weeks and I'm pretty sure they'd just flash it anyway!
I have the Nexus S still with stock ROM (2.3.6) and unrooted.
Any help will be greatly appreciated!! Ideally I'd like a way to transfer the update file to the sdcard and recover using the phone recovery. Failing that, I'd like to flash it using fastboot.
cheers

First you need to download this : http://www.4shared.com/zip/2L09-JyW/Root_Nexus_S.html
Just unpack , connect your phone and click run.bat....
After that you need : remove install-recovery.sh just in .....
run in windows-> Start->at the search bar write cmd and navigate into your android sdk is installed
For me :
C:/"Programs and Files (x86)"/Android/android-sdk/tools/>adb shell
# rm /system/etc/install-recovery.sh
#exit
or with Root Explorer into system/etc/install-recovery.sh just renam it (ex. : .sh.old)

thanks for the reply.
What will this do exactly?
I thought adb commands only worked when the phone was booted up?

just had a look at the bat. So it seems this will wipe and root the phone adding superuser privelages?
Is this the only way I can get it working again and once I've done this, how do I undo it as to get the stock version of ICS do I not need to be unrooted or will flashing the stock version from the link in my OP automatically unroot the phone and replace the recovery image etc?
thanks again for your help - I'm a bit of a noob when it comes to rooting and ROMs!

Forgot to say, I have GT-i9020 model if it makes any difference.

Skyap said:
Forgot to say, I have GT-i9020 model if it makes any difference.
Click to expand...
Click to collapse
My tools will root your device and installed CWM ...after that you can do anything you want....

I'm now rooted and have cwm recovery. Had some issues transferring files to the sdcard but seem to have moved a couple of files, but when I try to update using them I get...
Finding update package...
Opening update package...
E:Can't open /sdcard/name-of-file.zip
(bad)
Installation aborted.
I get this whether its the full stock ROMs found on here or the update only packages found on here.
Any ideas?

Skyap said:
I'm now rooted and have cwm recovery. Had some issues transferring files to the sdcard but seem to have moved a couple of files, but when I try to update using them I get...
Finding update package...
Opening update package...
E:Can't open /sdcard/name-of-file.zip
(bad)
Installation aborted.
I get this whether its the full stock ROMs found on here or the update only packages found on here.
Any ideas?
Click to expand...
Click to collapse
Trying to mount sdcard into CWM and see what happens.
---------- Post added at 07:37 PM ---------- Previous post was at 07:34 PM ----------
Reboot into recovery.
Go into "mounts and storage"
Select "mount sdcard"
Select "mount USB storage"
Shortly after your SD Card will be mounted on your computer.

please help my sh-12c stuck in boot
hi my sh-12c stuck in boot wont open could you hrelp me to guide ?
i enable su and and i change permission in settings thats all in hope if morelocal2 works but it doesnt work and was not problem to use but , i restart in hope if it work , but it stuck in the boot logo Auuos moving any way to restore ?

[Q] Unable to root device after unbrickin (actual versio v21e)

Hello ppl.
First of all i have to say that this is my first post but i've been reading this forum for a quite long time and you guys rock!
Well let's get to the problem i'm facing.
I have an P920H from Brazil and i've rooted it with mastermind method (dunno if that's the exactly name, but it's master something, sorry )
No problem with that, all worked flawlessly.
Then i decided to flash Prometheus custom rom and kernel v21 version
No problem with that either, all good to go.
But the thing is that i realized that i flashed the wrong baseband (didn't read about it to be honest.. guess i should have flashed 1.5 [based on v20 and not 1.5+]. ok i'm a dumbass) and then i got no signal from my operator.
After that i tried to restore a backup that i had made with rom manager... an error ocurred and my phone bricked, got stuck on LG logo.
And then, after reading tons of topics I could restore it and made it boot.
That's when my problem came.
My phone still is using prometheus kernel i guess, and is on v21e (originally was on v20a).
Master method and superone click just can't root it and I cant install another firmware over it. It just warns about errors and said it can't find SU bla bla.
What do you guys think I should do? I want to go back to my original firmware or install the correct custom rom but can't get root.
Thanks in advance.

Dan Rosenberg to the rescue... Thanks Dan!
To make it short try using Megatron Root by Dan Rosenberg (thanks Dan) which is designed for v21e. A link you can find it here or search the Optimus 3D forums (or LG Thrill). Hope that helps. It worked for me, using now WaterBear Rom on v21e

thanks man, will give it a try on that link.
I dunno if i had an previous version of that (magatron root) but I've tried it with no luck. Perhaps I did something wrong.
Anyway thanks :good:

perna84 said:
thanks man, will give it a try on that link.
I dunno if i had an previous version of that (magatron root) but I've tried it with no luck. Perhaps I did something wrong.
Anyway thanks :good:
Click to expand...
Click to collapse
U can root 100% with megatron. At least i did it 20+ times cause returning to stock kdz so often

Sorry for that small help first...
perna84 said:
thanks man, will give it a try on that link.
I dunno if i had an previous version of that (magatron root) but I've tried it with no luck. Perhaps I did something wrong.
Anyway thanks :good:
Click to expand...
Click to collapse
I forgot to put my posts where I was asking for help.
Anyway... go to http://forum.xda-developers.com/showthread.php?p=27380826#post27380826 and see post number 142 to 145, especially last one cause I've used that link to download Megatron Root. And it worked.
Just be patient, read all about it and try it again. Good luck

BigBadSheep said:
I forgot to put my posts where I was asking for help.
Anyway... go to http://forum.xda-developers.com/showthread.php?p=27380826#post27380826 and see post number 142 to 145, especially last one cause I've used that link to download Megatron Root. And it worked.
Just be patient, read all about it and try it again. Good luck
Click to expand...
Click to collapse
Still got no sucess
This is what i got with megatron method...
[*]
[*] Megatron: LG Optimus 3D/Thrill Root Exploit (Wind
[*] by Dan Rosenberg (@djrbliss)
[*]
[*] Before continuing, ensure USB debugging is enable
[*] have the latest LG drivers installed, and that yo
[*] is connected via USB.
[*]
[*] Press enter to root your phone...
Pressione qualquer tecla para continuar. . .
[*]
[*] Waiting for device...
* daemon not running. starting it now *
* daemon started successfully *
[*] Device found.
[*] Deploying payload...
1531 KB/s (564396 bytes in 0.360s)
pkg: /data/local/tmp/evil.apk
Success
[*] Owning phone...
run-as: Package 'com.ti.fmrxapp' is unknown
[*] Rebooting device...
[*] Waiting for phone to reboot.
[*] Writing to block device...
4 KB/s (4322 bytes in 1.000s)
[-] Failed to open block device.
[*] Pushing root tools to device...
2183 KB/s (22364 bytes in 0.010s)
2377 KB/s (843503 bytes in 0.346s)
[*] Rebooting device again...
[*] Waiting for phone to reboot.
[*] Getting root...
run-as: Package 'com.ti.fmrxapp' is unknown
run-as: Package 'com.ti.fmrxapp' is unknown
run-as: Package 'com.ti.fmrxapp' is unknown
run-as: Package 'com.ti.fmrxapp' is unknown
run-as: Package 'com.ti.fmrxapp' is unknown
run-as: Package 'com.ti.fmrxapp' is unknown
run-as: Package 'com.ti.fmrxapp' is unknown
[*] Cleaning up...
run-as: Package 'com.ti.fmrxapp' is unknown
su: permission denied
su: permission denied
Success
[*] Rebooting...
[*] Exploit complete!
[*] Press any key to exit.
Pressione qualquer tecla para continuar. . .
Ideas?

try reflashing kdz and start completely over
Sent from my LG-P920 using xda app-developers app

[SOLVED]
Thanks guys! Solved my problem
Here is how
First ive tried the method above and it didnt work, actually i was still with the same firmware version (21e)
So no good.
(Btw i`m running Windows 7 64 bits on bootcamp, but it should work for Windows 7 in general)
The solution is quite simple, right click ond adb.exe and under preferences set it to compatibility mode Windows XP and check run as administrator.
then execute the bat file as administrator also and you should be rooting just fine.

In other posts that you ask for help...
perna84 said:
Thanks guys! Solved my problem
Here is how
First ive tried the method above and it didnt work, actually i was still with the same firmware version (21e)
So no good.
(Btw i`m running Windows 7 64 bits on bootcamp, but it should work for Windows 7 in general)
The solution is quite simple, right click ond adb.exe and under preferences set it to compatibility mode Windows XP and check run as administrator.
then execute the bat file as administrator also and you should be rooting just fine.
Click to expand...
Click to collapse
...Please give all the infos, even those that you consider not important. In that way you could find help fast. Anyway, glad to hear that you solved it.

perna84 said:
Thanks guys! Solved my problem
Here is how
First ive tried the method above and it didnt work, actually i was still with the same firmware version (21e)
So no good.
(Btw i`m running Windows 7 64 bits on bootcamp, but it should work for Windows 7 in general)
The solution is quite simple, right click ond adb.exe and under preferences set it to compatibility mode Windows XP and check run as administrator.
then execute the bat file as administrator also and you should be rooting just fine.
Click to expand...
Click to collapse
Had this issue myself I wanted to help you but i forgot how I solved it... after I read this post I remembered
Sent from my LG-P925 using xda app-developers app

[Q] Rooting with OSX

Im Looking to root my Verizon GS3. only catch is im using OSX, OSX doesn't seem to be highly supported in the android realm. I found a thread on androidcentral about 'mac-root-tool-s3-casual-verizon-s3'
so my question is since that thread seems a bit dead, is will this work with build, VRALHE?

(For Mac/Linux/*Windows) How to install Adam Outler's Casual for Rooting/Unlocking Bootloader/CWM recovery
*This method does not work for VRBLI5/J1/K1 JellyBean
* I have successfully installed and ran Casual on Windows 7, but I recomend Windows users refer to section 1 of my guide
*More Information on Casual can be found HERE
Step 1: Download and install these files to your pc:
Samsung driver- http://tinyw.in/Fdoz
Adam Outler's Casual- http://d-h.st/ypJ
Java JDK-http://www.oracle.com/technetwork/java/javase/downloads/jdk-7u4-downloads-1591156.html(Should only be needed for windows users)
Step 2: On your device, Make sure USB Debugging(settings/developer options/usb debugging) and Install of Unknown Sources(settings/security/unknown source) is checked.(Also, make sure there are no other android devices, emulators, or any tethering programs running!!).
Step 3: Open the Casual file you downloaded in step1. you should here a voice say "casual", then the program should open.
Step 4: While fully booted up into android, connect the pc to the device using the oem usb cable. Casual should come up in green letters saying "device connected".
Step 5: Congrats, you are now ready to flash away.
Step 6: If you are not currently rooted, then flash DebugFSroot first, DO IT!
Step 7: Next flash unsecure aboot to unlock bootloader, DO IT!
Step 8: Finally flash ClockWork Mod Recovery(it should be version cwm 6.0.1), DO IT!

It works!
Everything works fine! i was able to root, i used EZ-unlock from the play store instead, but i was able to Load CM10 successfully onto it.
Thanks!

I wish I saw this post earlier

Replacement Phone
So are we sure that Casual still works for the "VRALHE" update? I just got a replacement phone today that ran this version and I'm not having any luck. I ran Casual on my phone when it first came out without a hitch. This time around it just gets stuck on: "Copying Su:" any ideas?
Edit: After a couple of restarts I made it past that stage and I'm faced with an error at the end...
"tep 1 - Setup...
Copying files:
Copying su:1147 KB/s (380532 bytes in 0.323s)
Copying debugfs:987 KB/s (1862336 bytes in 1.841s)
Copying debugfsinput:44 KB/s (144 bytes in 0.003s)
...done copying files.
Linking /system to tmp...
...done linking /system
Rebooting...
Step 2 - Rooting...* daemon not running. starting it now on port 5037 *
* daemon started successfully *
debugfs 1.42 (29-Nov-2011)
debugfs: debugfs: rm: File not found by ext2_lookup while trying to resolve filename
debugfs: debugfs: debugfs:
debugfs: Allocated inode: 2144
debugfs: debugfs: debugfs: debugfs:
Cleaning up...
Restoring tmp...
...done restoring tmp
Removing files...protocol failureerror: device not found
done. "

sspediacci said:
So are we sure that Casual still works for the "VRALHE" update? I just got a replacement phone today that ran this version and I'm not having any luck. I ran Casual on my phone when it first came out without a hitch. This time around it just gets stuck on: "Copying Su:" any ideas?
Edit: After a couple of restarts I made it past that stage and I'm faced with an error at the end...
"tep 1 - Setup...
Copying files:
Copying su:1147 KB/s (380532 bytes in 0.323s)
Copying debugfs:987 KB/s (1862336 bytes in 1.841s)
Copying debugfsinput:44 KB/s (144 bytes in 0.003s)
...done copying files.
Linking /system to tmp...
...done linking /system
Rebooting...
Step 2 - Rooting...* daemon not running. starting it now on port 5037 *
* daemon started successfully *
debugfs 1.42 (29-Nov-2011)
debugfs: debugfs: rm: File not found by ext2_lookup while trying to resolve filename
debugfs: debugfs: debugfs:
debugfs: Allocated inode: 2144
debugfs: debugfs: debugfs: debugfs:
Cleaning up...
Restoring tmp...
...done restoring tmp
Removing files...protocol failureerror: device not found
done. "
Click to expand...
Click to collapse
I don't know why this worked or why I thought of it, but I installed Samsung Kies and restarted my computer just for ****s and giggles. After that it rooted, flashed the unsecure bootloader, and flash CWM without a hitch.

droidstyle said:
(For Mac/Linux/*Windows) How to install Adam Outler's Casual for Rooting/Unlocking Bootloader/CWM recovery
*This method does not work for VRBLI5/J1/K1 JellyBean
* I have successfully installed and ran Casual on Windows 7, but I recomend Windows users refer to section 1 of my guide
*More Information on Casual can be found HERE
Step 1: Download and install these files to your pc:
Samsung driver- http://tinyw.in/Fdoz
Adam Outler's Casual- http://d-h.st/ypJ
Java JDK-http://www.oracle.com/technetwork/java/javase/downloads/jdk-7u4-downloads-1591156.html(Should only be needed for windows users)
Step 2: On your device, Make sure USB Debugging(settings/developer options/usb debugging) and Install of Unknown Sources(settings/security/unknown source) is checked.(Also, make sure there are no other android devices, emulators, or any tethering programs running!!).
Step 3: Open the Casual file you downloaded in step1. you should here a voice say "casual", then the program should open.
Step 4: While fully booted up into android, connect the pc to the device using the oem usb cable. Casual should come up in green letters saying "device connected".
Step 5: Congrats, you are now ready to flash away.
Step 6: If you are not currently rooted, then flash DebugFSroot first, DO IT!
Step 7: Next flash unsecure aboot to unlock bootloader, DO IT!
Step 8: Finally flash ClockWork Mod Recovery(it should be version cwm 6.0.1), DO IT!
Click to expand...
Click to collapse
when i download first link it downloads a windows file that doesnt open on mac
i know old thread but if some one can point me into the direction of a new thread or answers for a mac that would be great

You don't need the drivers for Mac. I think you will have to downgrade your software to stock ICS in order to root with your Mac using Casuals.

HHF2 said:
You don't need the drivers for Mac. I think you will have to downgrade your software to stock ICS in order to root with your Mac using Casuals.
Click to expand...
Click to collapse
And is there a download for that? You'll have to excuse my ignorance, I haven't had an android phone since the htc evo was out. I have been on iPhone. But trying to maybe go back to android with s3

I *THINK* that Casual works for the verizon galaxy sIII again... anybody try it yet?

[Q] Problems Rooting Verizon Razr XT912 4.1.2

I have been trying to root my Verizon Razr XT912 running Device Software Version: 98.72.16.XT912.Verizon.en.US with the only tool I can find to use on mac (DROID_RAZR_Utility_Jellybean_XT912_WinMacLin) and I keep getting the following error. I am not sure what I am doing wrong and this seems like the most knowledgable forum. Can anyone guide me in the right direction? Is it my phone, my OS, my connection? I am pretty certain I followed all the steps exactly and I've searched through all the threads on the forum and most of them say something to the effect of "...then I tried again and it worked". Well I've tried about 15 times over the course of two weeks and nothing worked, I hate to admit defeat... but I need some help. Thanks in advance.
[*] Phase three (this will take a minute)...
failed on '/data/logger' - Permission denied
mkdir failed for /data/logger, File exists
Unable to chmod /data/logger: Operation not permitted
link failed File exists
[*] Rebooting device...
[*] Waiting for phone to reboot.
[*] Phase four...
2254 KB/s (543080 bytes in 0.235s)
2961 KB/s (1867568 bytes in 0.615s)
2933 KB/s (476557 bytes in 0.158s)
1841 KB/s (63838 bytes in 0.033s)
[*] Cleaning up...
/system/bin/sh: su: not found
[*] Rebooting...
[*] Exploit complete!

Here's what worked for me
I was having the exact same problem until I ran across this in another forum:
Windows-
-Download the zip file and extract.
-Connect device via USB (Make sure you have the current Moto drivers FIRST!)
-Make sure USB Debug is on
-Make sure you have Smart Actions fully installed, unfrozen and unmodified
-Make sure the phone IS NOT in mass storage mode
-Double click run.bat
For some reason, that fifth line is not included in the batch file's instructions. Once I knew to change from mass storage to camera mode, all went well!

[Q] complete reformat and start over

After several ROM installs and getting to bricking, I ended up with folders with names like "0" and "obb". Is there a way to reformat the internal storage and get back the beginning? Currently using KATKISS.
I wanted to put Ubuntu on but "failed" in TRWP when installing the zip.

aknisley said:
After several ROM installs and getting to bricking, I ended up with folders with names like "0" and "obb". Is there a way to reformat the internal storage and get back the beginning? Currently using KATKISS.
I wanted to put Ubuntu on but "failed" in TRWP when installing the zip.
Click to expand...
Click to collapse
0 is for internal storage
Obb is app data folder
we can format 0
but I will only delete data of apps
install different ROM.
press thanks if I helped you.

aknisley said:
After several ROM installs and getting to bricking, I ended up with folders with names like "0" and "obb". Is there a way to reformat the internal storage and get back the beginning? Currently using KATKISS.
I wanted to put Ubuntu on but "failed" in TRWP when installing the zip.
Click to expand...
Click to collapse
why not just return to stock and begin again.
follow this: http://www.transformerforums.com/forum/asus-transformer-tf101-development/31919-frederuco-s-guide-flash-tf101-back-stock.html

barkeater said:
why not just return to stock and begin again.
follow this: http://www.transformerforums.com/forum/asus-transformer-tf101-development/31919-frederuco-s-guide-flash-tf101-back-stock.html
Click to expand...
Click to collapse
Well, I cannot, because I cannot flash TWRP. TO follow the recipe, It calls for TWRP and all I have is CWM. Try as I might, I cannot install TWRP. I tried via ZIP and also from blob. Nothing. As I write this, I am trying to go back to stock via CWM. It is taking a while, so it may work. As of now, I have been able to re-flash CM10_Nightly, but when I try ano other ROM, it boot loops. I may have really hosed it, now, though. We shall see. I am not averse to NVFlashing it , but have not yet found instructions to do that under Linux. I do not have a Windows computer and most of them call for it.

In case it saves someone else's bacon, I thought I'd post my findings.
I rebooted into windows and tried the 'one click transformer root' tool. It runs and then tells me that it cannot deal with my tablet as it is not running ICS. I tried another one called which is supposed to return to stock called EasyFlasher 0.83. It acted like it installed the stock image, but did not do anything. It would always reboot to CWM.
In CWM., I could wipe and flash an image, but it would never boot. Just bootloop. I had CM10 on the tablet and am guessing that the install was not quite kosher. I could not install any other recovery image, either.
To solve it, I downloaded the blob tools
Blob Tools
I already had wheelie since I used the CM page to install it
CM10 install
I unpacked the image by first unzipping the zip from asus. IN it was a file called 'blob'. I then unpacked it:
Code:
./blobunpack latest/blob
it created 4 files called blob.APP, blob.EBT, blob.LNX and blob.SOS
We want the blob.SOS file. I put it in the wheelie directory and modified the commands I used to initially install the CWM recovery:
Code:
# ./wheelie -1 -o 0x300d8011 --bl bootloader.bin -c transformer.bct
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Using SBK type 1.
Using bootloader: 'bootloader.bin'.
Using BCT: 'transformer.bct'.
----------------------------------------
[=] Chip UID: 0x370018042607097
[=] RCM Version: 0x20001
[=] CPU Model: Tegra 2
[=] Secure Boot Key Set: Yes
[+] Sending BCT
Sending file: 100 %
[+] Sending ODMData 0x300D8011
[+] Sending bootloader...
Sending file: 100 %
[!] Done - your device should now be ready for nvflash
# ./nvflash -r --download 5 blob.SOS
Nvflash started
[resume mode]
sending file: blob.SOS
\ 4284416/4284416 bytes sent
blob.SOS sent successfully
# ./nvflash -r --go
Nvflash started
[resume mode]
My zip file was in the root of the SD card, so it immediately reflashed itself after it rebooted. Finally!

congrats!
Yeah, I have no experience with cwm or any other os other than Windows. Glad you got it sorted. Happy Holidays!

barkeater said:
congrats!
Yeah, I have no experience with cwm or any other os other than Windows. Glad you got it sorted. Happy Holidays!
Click to expand...
Click to collapse
Like I said, though, I could not get it to do anything in Windows or Linux. I think it was a permissions problem or a directory structure which was incorrect. Regardless, this worked and i was able to root it using one click root. I was unable to flash the twrp recovery by the preferred method and had to first 'fix sdcard write permissions' from the twrp app. Then the app would not flash it. So i used dd via adb and got it. I have flashed katkiss and am trying it out. I feel as though i have been released from cwm/cm10 hell, finally.