ok, I've looked everywhere else but I haven't been able to find the answer. My friend was trying to put gingerbread on his atrix 4g (att) and the battery died halfway through. Now we borrowed a charged battery from a friend and now when ever we turn it on it says
SVF 105:1:2
failed to boot 0x1000
then waits a few seconds then flashes "starting hv flash recovery" then turns off. The hv part might be wrong. But no matter what I press the device will not go into usb bootloader for me to put a new sbf on
any help would be much appreciated. Thank you for your time
so you can't get into fastboot mode either?
How were you installing gingerbread?
turl1 said:
How were you installing gingerbread?
Click to expand...
Click to collapse
well when my friend was doing it it was rsd lite 4.6 i think
lifetaker said:
well when my friend was doing it it was rsd lite 4.6 i think
Click to expand...
Click to collapse
if you can only get into NVFlash mode, then i'm pretty sure that you're not gonna be able to fix it. i don't believe we have the nvidia flashing tools needed to get past this option.
Alcapone263 said:
if you can only get into NVFlash mode, then i'm pretty sure that you're not gonna be able to fix it. i don't believe we have the nvidia flashing tools needed to get past this option.
Click to expand...
Click to collapse
so what your telling me, is that under no circumstance, at all. there is no way to ever fix this phone. ever, in a million years. there is no way to force the phone into bootloader?
yea you need to charge the battery outside the phone then check the dev section there is a program just fir your situation!
A soft brick, in this case, is when you make a bad edit to your framework files and the phone won't fully boot and starts flashing a red LED at you.
There is one catch, you only get about 1-2min to do all of this before the phone reboots on its own. If that happens, do SuperOneClick steps again and continue where you left off. Better yet, build a script to do it all for you 
Power off your device
Enter Fastboot:
Hold Volume down + power until you see Fastboot at the top left
Use volume down to scroll down to "Early USB Enumeration" (only shows one item at a time, if you pass it, keep going down, up selects)
Press Volume up to select
Wait for ADB to enable, run "Shell Root" from SuperOneClick, wait until it says you have root.
Enter adb shell from command line, You should have root(#) access:
adb shell
Mount the system directory as read/write:
mount -o rw,remount /dev/block/mmcblk0p12 /system
Make a new directory on /data for your recovery files: (sdcard wont be mounted yet)
mkdir /data/recover
Exit adb shell:
exit
Push your known working files to the new directory:
adb push /path/to/local/file.ext /data/recovery
Enter adb shell from command line:
adb shell
Copy your newly pushed recovery files to their proper location:
cp /data/recover/services.jar /system/framework
cp /data/recover/framework.jar /system/framework
cp /data/recover/famework-res.apk /system/framework
Reboot:
reboot now
ltdanno360 said:
yea you need to charge the battery outside the phone then check the dev section there is a program just fir your situation!
A soft brick, in this case, is when you make a bad edit to your framework files and the phone won't fully boot and starts flashing a red LED at you.
There is one catch, you only get about 1-2min to do all of this before the phone reboots on its own. If that happens, do SuperOneClick steps again and continue where you left off. Better yet, build a script to do it all for you 
Power off your device
Enter Fastboot:
Hold Volume down + power until you see Fastboot at the top left
Use volume down to scroll down to "Early USB Enumeration" (only shows one item at a time, if you pass it, keep going down, up selects)
Press Volume up to select
Wait for ADB to enable, run "Shell Root" from SuperOneClick, wait until it says you have root.
Enter adb shell from command line, You should have root(#) access:
adb shell
Mount the system directory as read/write:
mount -o rw,remount /dev/block/mmcblk0p12 /system
Make a new directory on /data for your recovery files: (sdcard wont be mounted yet)
mkdir /data/recover
Exit adb shell:
exit
Push your known working files to the new directory:
adb push /path/to/local/file.ext /data/recovery
Enter adb shell from command line:
adb shell
Copy your newly pushed recovery files to their proper location:
cp /data/recover/services.jar /system/framework
cp /data/recover/framework.jar /system/framework
cp /data/recover/famework-res.apk /system/framework
Reboot:
reboot now
Click to expand...
Click to collapse
wont go into fastboot or i would have used that already
also i have a video of the phone. but i dont have enough posts to post the link. dont get mad mods
watch?v=XuV5A6mH-Qw
of course just post this at the end of a youtube url
lifetaker said:
also i have a video of the phone. but i dont have enough posts to post the link. dont get mad mods
watch?v=XuV5A6mH-Qw
of course just post this at the end of a youtube url
Click to expand...
Click to collapse
no, this is a hard brick to your Atrix. it's a nice paperweight now.
did you attempt to flash a froyo .sbf on a gingerbread Atrix?
Alcapone263 said:
no, this is a hard brick to your Atrix. it's a nice paperweight now.
did you attempt to flash a froyo .sbf on a gingerbread Atrix?
Click to expand...
Click to collapse
Alcapone263 said:
no, this is a hard brick to your Atrix. it's a nice paperweight now.
did you attempt to flash a froyo .sbf on a gingerbread Atrix?
Click to expand...
Click to collapse
it was the other way around. but now i guess ill sell it on ebay for $200. its still in perfect condition. lets see what happens. thanks guys
lifetaker said:
it was the other way around. but now i guess ill sell it on ebay for $200. its still in perfect condition. lets see what happens. thanks guys
Click to expand...
Click to collapse
Why would you sell a broken phone on Ebay and claim it's in perfect condition?
Sent from my MB860 using xda premium
Hello all,
I have been trying to downgrade my Flyer (wi-fi Best Buy version) by using the procedure provided by our awesome helper and mentor, globatron. The procedure is titled as [Procedure]No HTC unlock HC-GB downgrade for official HC OTA and found at http://forum.xda-developers.com/showthread.php?t=1428104.
I have gone through all 13 pages on that thread to find out if anyone has a problem I am having. But it appears no one had the same problem. As a new user, I was not allowed to post a question on that particular thread. So here I am....
Here is the procedure/instruction from the posting I mentioned above.
Procedure
1. Check the version number for your gingerbread RUU
In my example I am using this RUU: RUU_Flyer_HTC_WWE_2.00.405.3_R_Radio_20.3501.30.08 9BU_3809.05.04.10_M_release_194964_signed.exe
The version is the part highlighted in red.
2. Boot your flyer up to android if it's not already on, with usb debugging enabled and connect it to the PC.
3. Run the following adb commands
adb push tacoroot.bin /data/local/
adb push misc_version /data/local/
adb shell chmod 755 /data/local/tacoroot.bin
adb shell chmod 755 /data/local/misc_version
adb shell /data/local/tacoroot.bin --setup
At this point your device will reboot to recovery
4. Simultaneously press Volume Up, Volume Down and Power
5. Reboot your device
6. Run the following command
adb shell /data/local/tacoroot.bin --root
* Your device will reboot, do not worry if it does not boot fully, it doesn't matter for this procedure, and it is a side effect of this root exploit.
7. Run the following command:
adb shell /data/local/misc_version -s 2.00.405.3
* Note that the number in RED is the version number retrieved in step 1.
8. Reboot to fastboot:
adb reboot bootloader
I could not move forward after 8, I will not post the steps from 9 to 11.
Here we go.... I have two troubles.
First, I am not sure of the timing of "pressing Volume Up, Volume, Down, and Power." Is it something I should do manually? If so, when should I do it. It seems like the Flyer automatically re-boots itself into "Recovery" without me forcing it.
As it is going into the "Recovery," there were two images popped up in a row. The first one looks like a SD disc, which moved quickly moved to the next image. The second image is a tablet with a red triangle, which has a exclamation sign in it.
THEN the procedure STOPS at the second image.
That is my first question. Does anyone have any idea of what's possibly going on?
My second starts here as well.
After not moving on, I decided to manually reboot the Flyer so I can move on to the Step 7.
Somehow I can pass the Step 7. But at Step 8, I got the message saying "Error: Device not found." So I tried "fastboot getvar cid" to see if the tablet is really not connected. But weirdly, the "fastboot getvar cid" worked. But I still get the same error message (device not found) whenever I run the code at step 8.
This is it. There are my two questions.
As I went through all 13 pages, many people were able to go through the procedure without any problem. Having those problem and taking considerable amount time to figure our what's going on and still not successful make me feel pretty stupid and extremely frustrated. Please someone put me out of this horrible misery.
I love my Flyer. But I am starting to understand why many of my friends paid a lot more $$$ to get their iPad.
Not sure what went wrong, but you could try doing step 8 manually. Hold volume down and power for roughly 10 seconds, you should get into the H-boot screen. Press the power button once on Fastboot ( its the first option) use the volume keys to navigate to "reboot bootlader" use power key to select it.
Thanks, but didn't work.
Havoc-X said:
Not sure what went wrong, but you could try doing step 8 manually. Hold volume down and power for roughly 10 seconds, you should get into the H-boot screen. Press the power button once on Fastboot ( its the first option) use the volume keys to navigate to "reboot bootlader" use power key to select it.
Click to expand...
Click to collapse
I tried it. But, I am still having that "error: device not found" message.
Thanks for your advice though. I clicked "Thanks."
still getting the same image
Havoc-X said:
Not sure what went wrong, but you could try doing step 8 manually. Hold volume down and power for roughly 10 seconds, you should get into the H-boot screen. Press the power button once on Fastboot ( its the first option) use the volume keys to navigate to "reboot bootlader" use power key to select it.
Click to expand...
Click to collapse
Somehow the thread doesn't allow me to edit my own reply.
Anyway, I still end up with the tablet image with the red triangle, which has a exclamation sign (!) in it. I was afraid of bricking my Flyer and stopped trying anything further.
Try with DEBUG turned OFF althow stated ON. Worked for me like that when i was runing revolutionary. I coudnt make it work then just out of curiositiy i switched and it worked.
jprednik said:
Try with DEBUG turned OFF althow stated ON. Worked for me like that when i was runing revolutionary. I coudnt make it work then just out of curiositiy i switched and it worked.
Click to expand...
Click to collapse
Thanks for the advice. I'll give it a shot and keep you posted. Thanks again.
jprednik said:
Try with DEBUG turned OFF althow stated ON. Worked for me like that when i was runing revolutionary. I coudnt make it work then just out of curiositiy i switched and it worked.
Click to expand...
Click to collapse
It didn't work for me.
I cannot get the access to the tablet. THANK YOU for your advice though!! Have a great day!!!
Hello. This is my 2nd post after here. I hope this will not bother anybody.
I have a situation. I did root my TF201 using CWM and virtuous_prime_s_9.4.2.21_v1 a month ago. Just now, I plan to sell my TF201. So, I go to the tablet setting and click at the reset data or something like that. I think it's just a normal data deletion process which is not effecting the rooted system. Unfortunately, after I reset / delete the data, the tablet is not going to boot. It just keep showing the CWM Recovery page with options to reboot the system, install zip from sdcard, wipe data, and so on. I selects to reboot the system, but nothing is happening. The tablet is turned off and turned back on with same display (CWM Recovery page).
What should i do?
titanbullet said:
Hello. This is my 2nd post after here. I hope this will not bother anybody.
I have a situation. I did root my TF201 using CWM and virtuous_prime_s_9.4.2.21_v1 a month ago. Just now, I plan to sell my TF201. So, I go to the tablet setting and click at the reset data or something like that. I think it's just a normal data deletion process which is not effecting the rooted system. Unfortunately, after I reset / delete the data, the tablet is not going to boot. It just keep showing the CWM Recovery page with options to reboot the system, install zip from sdcard, wipe data, and so on. I selects to reboot the system, but nothing is happening. The tablet is turned off and turned back on with same display (CWM Recovery page).
What should i do?
Click to expand...
Click to collapse
If you still have the virtuous prime file on there just.go to install zip and select it then reflash and youl be good to go. If not then you need to search on here for a program called knives and forks which is the easy way to install adb android debug bridge once installed download virtuous prime zip and place it in the same Rwhere you just installed adb then make sure you are in the cmw main screen and type adb push (filename) this will send the to tablet it may take up to 10 minutes and will just show a flashing cursor . Then flash.as normal. Sorry for spelling mistakes typing.g this on my phone and its being stupid
Uberjim said:
If you still have the virtuous prime file on there just.go to install zip and select it then reflash and youl be good to go. If not then you need to search on here for a program called knives and forks which is the easy way to install adb android debug bridge once installed download virtuous prime zip and place it in the same Rwhere you just installed adb then make sure you are in the cmw main screen and type adb push (filename) this will send the to tablet it may take up to 10 minutes and will just show a flashing cursor . Then flash.as normal. Sorry for spelling mistakes typing.g this on my phone and its being stupid
Click to expand...
Click to collapse
Thanks for the reply. I appreciate the info given. Will try to use the tool now since the rom file is no longer saved in the tablet.
Will update soon.
Thanks.
I'm just done installing the Knivesandforks on my win7. After that, the system automatically install the phyton. I dont know what its function, but as i follow this steps, i get error with cmd which shown as below:
Code:
c:\users\pc>adb reboot
error: device not found
i think i didn't miss any steps. Anybody here could help me with this?
Thanks in advance.
* my tablet is still in cmw main page and not showing anything even has been connected to the PC. i think that's the reason why the error occurs - device not found. anybody who could give some ideas on this will much appreciated.
You may need the fast boot drivers I wasn't sure if you would with being in cmw download those and extract them to the same folder as adb then load it up by using shift right mouse click run command and type and type adb devices if it shows up your good to go try the above steps again
titanbullet said:
Hello. This is my 2nd post after here. I hope this will not bother anybody.
I have a situation. I did root my TF201 using CWM and virtuous_prime_s_9.4.2.21_v1 a month ago. Just now, I plan to sell my TF201. So, I go to the tablet setting and click at the reset data or something like that. I think it's just a normal data deletion process which is not effecting the rooted system. Unfortunately, after I reset / delete the data, the tablet is not going to boot. It just keep showing the CWM Recovery page with options to reboot the system, install zip from sdcard, wipe data, and so on. I selects to reboot the system, but nothing is happening. The tablet is turned off and turned back on with same display (CWM Recovery page).
What should i do?
Click to expand...
Click to collapse
Recovery bootloop, see here, option 1a: http://forum.xda-developers.com/showthread.php?t=1514088
Use only Universal Naked Drivers (see related thread).
Sometimes even with proper drivers adb is a mess, then uninstall adb and search the net for a ready to use adb, there are some easy to find.
Uberjim said:
You may need the fast boot drivers I wasn't sure if you would with being in cmw download those and extract them to the same folder as adb then load it up by using shift right mouse click run command and type and type adb devices if it shows up your good to go try the above steps again
Click to expand...
Click to collapse
i did those steps again, but it seems like not helping. the script is only rebooting the tablet instead of giving me the option to flash the rom. i don't know if i did wrong. but as i know, i did as posted here.
* frust to see the cmw recovery for the whole day
Striatum_bdr said:
Recovery bootloop, see here, option 1a: http://forum.xda-developers.com/showthread.php?t=1514088
Use only Universal Naked Drivers (see related thread).
Sometimes even with proper drivers adb is a mess, then uninstall adb and search the net for a ready to use adb, there are some easy to find.
Click to expand...
Click to collapse
i did follow this tutorial
at first, install universal naked drivers - done
Now do the following:
Make sure your Prime is in Recovery mode (CWM) - YES
Open a cmd line on your pc - DONE
Type: "adb shell" - DONE
You should see a "#" now - YES
Once you have that "#", please type: dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1 and press [Enter] - Ok. This part was very difficult. I see the "#" but to type all those command, I can't. Why? Because the line in cmd instantly extended to a new line of command. I mean it just like I press the ENTER button. So, the line move to below and i can't finish typing all those command.
Now type: dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1 and press [Enter]
Exit the shell and reboot your Prime via CWM
It should not reboot to CWM automatically now. It either boots your ROM or is stuck at the splash screen. If it is stuck, boot to recovery and install any ROM you want.
Click to expand...
Click to collapse
titanbullet said:
i did follow this tutorial
at first, install universal naked drivers - done
Click to expand...
Click to collapse
Very strange, try to expand your command line window first. It doesn't matter if the text goes on following line, as long as you don't press Enter it's considerd as the same line. Try copy/paste instead ot typing.
Striatum_bdr said:
Very strange, try to expand your command line window first. It doesn't matter if the text goes on following line, as long as you don't press Enter it's considerd as the same line. Try copy/paste instead ot typing.
Click to expand...
Click to collapse
this is my first time, so i don't know if that was strange. ha ha. well, it's not about the command line which is extended or not. but the line itself creating a new line, as i said - just like i press the ENTER button.
i try to use copy-paste function (ctrl + c and ctrl + v). but i don't think it functions in cmd.
please help..
[Solved]
What i do?
I follow this step again
Installing the ADB again
And the most important thing is, pushing ROM into /sdcard should be like this:
Code:
adb push rom.zip /sdcard/rom.zip
And right-click copy paste function solving my strange cmd
Then i just follow the steps by installing the zipped rom thru cwm when my screen did not stuck at splash screens
Thanks for your kindness
My TF is now back to normal
THANKS!
Hello. I've looked all over the forums and was wondering if anyone has any info about rooting the Huawei Q M660. I've tried Doomlord, Superoneclick, Unlockroot, and z4root to no avail. There doesn't seem to be a forum for this phone and I was hoping I hadn't missed anything. Thanks in advance for any help that comes of this.
mendoozer666 said:
Hello. I've looked all over the forums and was wondering if anyone has any info about rooting the Huawei Q M660. I've tried Doomlord, Superoneclick, Unlockroot, and z4root to no avail. There doesn't seem to be a forum for this phone and I was hoping I hadn't missed anything. Thanks in advance for any help that comes of this.
Click to expand...
Click to collapse
http://redigua.com/how-to-root-huawei-ascend-q.html#.UM_dHG9ZWSp I found this method, but I was wondering if any tech savvy members think this is even possible. I only have the one phone, and don't want to kill it. so, any opinions? Thanks for helping!
How TO Root Huawei Ascend Q
Thursday, June 14, 2012, 14:06uncategorizedAdd a comment
This is an updated method on how to root your Huawei Ascend Q.
First, you need the file hboot_2.xx_soff-V8.9.zip, download it.
Unzip it into c:evoroot on your pc.
Second, put your Huawei Ascend Q into development mode by going to Settings->Applications->Development and turn USB debugging on.
Third, connect your Huawei Ascend Q to your computer and set your USB to Just charge.
Fourth, if you get errors with drivers, install their HTC drivers. (You can also install HTC Sync, but it is bulky!)
Fifth, open up a command prompt by typing cmd.
Sixth, type the following commands: (Or copy and paste, easier!)
cd evoroot
adb push root/unrevoked-forever.zip /sdcard/
adb push root/mtd-eng.img /sdcard/
adb push pc36img/PC36IMG-ENG.zip /sdcard/PC36IMG.zip
adb push pc36img/PC36IMG-MR.zip /sdcard/PC36IMG-MR.zip
adb push root/flash_image /data/local/
adb -d install -r root/z4root.apk
Seventh, go to your phone and launch Z4Root app. Then select temp root and wait until its done.
Eighth,go back to command prompt and type:
adb shell
su
If you get a pound(#) sign, that means you have temp root, which just gives you temporary root so we can now install permanent root.
Ninth, lets backup our WiMax 4G RSA just in case we lose it during installation of new ROMs.
Type:
Mkdir /sdcard/nandroid/RSA-PR-BACKUP
Cat /dev/mtd/mtd0 > /sdcard/nandroid/RSA-PR-BACKUP/wimax.img
busybox sed -n /BEGIN CERTIFICATE/,$p /dev/mtd/mtd0 > /sdcard/rsa_OEM.key
Tenth, go back to command prompt and type the following:
chmod 0755 /data/local/flash_image
./data/local/flash_image misc /sdcard/mtd-eng.img
sync
And reboot to bootloader mode by typing:
reboot bootloader
When bootloader mode starts up, it will look for PC36IMG.zip and after about 3 minutes ask you if you want to install PC36IMG.zip.
Say Yes by hitting the volume up button, it should now install the new zip file, should take about 10 minutes. Go grabs some coffee and come back.
Eleventh, reboot when its done by hitting the volume up button.
It will reboot into the OS and we dont want that so takes the battery out and puts it back in it. Then go back to the bootloader by hitting the power button while holding down the volume down button.
Choose Bootloader and wait until you get the triangle sign and type:
adb push recovery /
adb shell busybox Cinstall /sbin
adb shell nohup /sbin/recovery &
Go back to your Huawei Ascend Q and you should see green menus.
Choose install zip from sd card and choose unrevoked-forever.zip
After that installs, Choose MS-USB
Go to your computer and delete PC36IMG.zip, then rename PC36IMG-MR.zip to PC36IMG.zip.
Then power off your Huawei Ascend Q, power back on by pressing Power Button while holding down the Volume Down button, this should get you back into bootloader mode.
Simply wait and when it asks to install the update, hit the Volume Up button.
then reboot your Huawei Ascend Q, your device should now be rooted with Recovery menu then you can flash new ROMs for Huawei Ascend Q.
No luck
I've been attempting to root my Ascend Q as well, and I tried this method, and I couldn't get past "adb push root/flash_image /data/local/" due to "Permission Denied" but from what I understand Z4 can't root any phone past like 2.2 so I doubt the legitimacy of this tutorial, I don't know if I'm missing something or what, but I have a basic knowledge of rooting and I've found the recovery mode for the Ascend Q (Hold Power and Volume Up when your phone is off) but I'm not sure what to do with that.
Anyone can provide any insight on where to go from here?
I've put my phone in debugging and downloaded the drivers.
I'm also looking for a solution to root this phone. Anyone figured this out? Thank you.
I am still also in need of a root method for my Ascend m660, and would be willing to donate to anyone who successfully does this! ^_^
factualpuddle said:
I am still also in need of a root method for my Ascend m660, and would be willing to donate to anyone who successfully does this! ^_^
Click to expand...
Click to collapse
cydia impactor roots teh device
Sincere thanks Shabbypenguin and whomever you work with, if anyone, Yep. I'm rooted and Superusered and Busyboxed. Any word on a custom recovery yet?
im not overly a big fan of huawei, but a buddy of mine asked me to help him with the device. this weekend was my daughters birthday, ill hobble together recovery as best as i can this coming week.
edit: done
http://www.cricketusers.com/cricket-huawei-ascend-q-m660/85514-[oudhs]-oudhs-recovery-1-0-3-4-a.html
also requested official cwm support https://github.com/koush/ROMManagerManifest/pull/430 so that rom manager can be used with this device to flash recovery if you are rooted and lazy
RECOVERY FROM BOOT LOOP/BRICK
Most people use the term "bricked" improperly. A bricked phone means one thing: your phone won't turn on in any way, shape or form, and there's Probably nothing you can do to fix it. It is, for all intents and purposes, as useful as a brick. A phone stuck in a boot loop is not bricked, nor is a phone that boots straight into recovery mode. These are things you can usually fix, and they're a lot more common than a truly bricked phone. If your phone is actually bricked, you Probably won't be able to fix it yourself.
BOOTLOOP GUIDE
(#:1)
Start by removing the device's battery and wait for a few minute's before putting it back in your phone.
OR Switch off for non-removable battery phones for five to ten minutes so it can remove any charge that is left in the phone and to initiate a complete power-cycle once you insert the battery.
Now Boot the device into Recovery Mode by pressing and holding the relevant shortcut keys for your device. For instance, most Samsung devices can boot into Recovery Mode while pressing the key combination Volume Up, Home and Power (for tablets it is Volume Up and Power). If using a HTC phone, boot into HBOOT first by tapping Volume Down and Power button together and then browse to Recovery using Volume Up/ Down buttons. If you cant get it to boot in Recovery you can always use (ADB) and type in the command] > adb reboot recovery <--- Hit Enter now your Device will reboot into recovery mode. If your not familar with adb or even know what adb is there is a link on the bottom of this page for the sdk download and a gude on the adb.
(#:2)
Now browse and select the option Wipe Data/Factory Reset in Recovery Mode.Check if the device can now boot into the newly installed ROM or firmware. If not, then perform Wipe Cache Partition And Return to the main Recovery menu and reboot the device by choosing Reboot System Now option.After Flashing or Installing a New ROM and If the device is already rooted with ClockworkMod Recovery (CWM) installed, then do the following steps (1) Remove you'r battery and reinsert it after 30 seconds. (2) Boot the device into CWM Recovery by pressing and holding Volume Up, Home and Power buttons together. NOTE: The key combination may vary depending on your device model.So, CONFIRM BEFORE YOU PROCEED. (3) Now Go to Advanced option in Recovery menu and choose Wipe Dalvik Cache. Then perform Wipe/cache under Mounts & Storage. Reboot the device and check if the boot loop issue is resolved. If not repeat the above three steps, but perform both Wipe/data and Wipe/cache under Mounts & Storage before rebooting.
(#:3)
After Setting an Incorrect File Permission.The Android operating system (OS) works on file permissions and hence incorrectly set file permissions may permanently damage or soft brick your device. Here are some of the commonly used file permissions:- 644 (RW-R-R) - (this is most common system permission, it exists in /system/app, /system/framework, /system/etc, /system/lib and allot of separate files) - 755 (RWX-RX-RX) - (mainly used for /system/bin) - 777 (RWX-RWX-RWX) - (used for scripts inside /system/etc/init.d and busybox files)
To fix or reset any of these file permissions, do the following:Boot the device into CWM or TWRP recovery Go to Advanced option.Click Fix Permission and confirm the action. After Restoring a Backup.If the bootloop error occurs immediately after restoring a Nandroid Backup, follow the steps on -(#:2)- to fix it. If everything else fails, just try re installing the original ROM or flash the first official firmware.
Using ADB BY Samantha
DB can be used to access the phone while booting, be aware that some bootloops make it unable to use ADB since they do not go further then the manufacturer logo. (In new CWM versions it’s possible to use adb)
The only tricky part about using ADB with bootloops is that you have to do it on the right time, this is different from every device, but normally it’s after the manufacturer logo that the partitions get mounted. The easiest way to enter your phone in this part is using a batch script that monitors the state of your device and connects directly when possible.
I use this script for example, called ondemand.bat (requires adb.exe and the 2 dlls)
1 @ECHO off
2 cd /d %~dp0
3 echo.
4 echo Waiting for device…
5 adb wait-for-device
6 echo.
7 adb -d shell stop
8 adb push mycwmfix.zip /sdcard/mycwmfix.zip
9 adb reboot recovery
Linux Version (ondemand.sh):
1 #!/system/bin/sh
2 echo " "
3 echo "Wating for device..."
4 ./adb wait-for-device
5 echo " "
6 ./adb -d shell stop
7 ./adb push mycwmfix.zip /sdcard/mycwmfix.zip
8 ./adb reboot recovery
This script will wait for the device to become ready, when it’s ready it freeze the device, so the script has more time to push the file (instead of keep rebooting). Then it will push the specified cwmfix zip to your sdcard, and after that it will reboot in recovery so you can install the cwm fix you made. You can also make an batch script that pushes the files automatically to your phone, here is an example:
(1 @ECHO off
(2)cd /d %~dp0
(3)echo.
(4)echo Waiting for device...adb wait-for-device
(5)echo.
(6)adb -d shell stop
(7)adb -d shell su -c "mount -o remount rw /system"
(8)adb push framework-res.apk /system/framework/framework-res.apk
(9)adb -d shell chmod 644 /system/framework/framework-res.apk
(10)adb push SystemUI.apk /system/app/SystemUI.apk
(11)adb -d shell chmod 644 /system/app/SystemUI.apk
(12)adb reboot
(13)Linux version:
1#!/system/bin/sh
2echo " "
3echo "Waiting for device..."
4./adb wait-for-device
5echo " "
6./adb -d shell stop
7./adb -d shell su -c "mount -o remount rw /system"
8./adb push framework-res.apk /system/framework/framework-res.apk
9./adb -d shell chmod 644 /system/framework/framework-res.apk
10./adb push SystemUI.apk /system/app/SystemUI.apk
11./adb -d shell chmod 644 /system/app/SystemUI.apk
12./adb reboot
This script will wait for the device to become ready, when it’s ready it freeze the device, so the script has more time to push the file (instead of keep rebooting). Then it will push framework-res.apk and SystemUI.apk to the directory it belongs to, after that it changes the permissions of the files to RW-R-R (644) and then it will reboot.
Please note that on some devices the command “su -c” cannot be used after using the “stop” command, it gives an error then (Segmentation Fault).
What you can do to prevent this is adding “adb remount” just under the “adb wait-for-device” line, and remove the “adb -d shell su -c “mount -o remount rw /system” line.
Save the script and run it again.
For HTC Phones: HTC phones can flash stock ROMs, known as RUUs, right from the phone's bootloader. You'll need to Google around for your device's specific RUU file, but once you download it, save the ZIP file to your SD card, and rename it (to something like PG05IMG.zip—the download page for the RUU file should specify which filename is required), booting up your phone should automatically flash the stock ROM from HBOOT, HTC's bootloader. Video http://www.youtube.com/watch?feature=player_embedded&v=tE8BiIFUOpk
For Samsung Phones If you're using a Samsung Galaxy phone, you can use a tool called Odin to reflash an OPS file, which is a stock ROM that will return your phone to factory settings. You'll need a Windows machine and a copy of Odin, which you can find by Googling around the net (as its not an official tool) check out The Unlockr's guide to using Odin to familiarize yourself. You may need to Google around for your specific device's OPS file and instructions.
Video http://www.youtube.com/watch?feature=player_embedded&v=5s70dwNgdD8
Verizon Galaxy S3 Bootloop fix using Odin
The Verizon Galaxy S3 has to be the most problematic variant of the Galaxy S3. If the locked bootloader on it wasn’t enough, many users have seen their Verizon Galaxy S3 get bricked and stop booting after trying to flash a custom ROM.
To start off there will be a little bit of downloading
Samsung USB Driver V1.5.14.0 For Android Mobile Devices
ODIN
VRALEC.bootchain.tar.md5
BOOTLOADER-I535VRALF2-618049-REV09-user-low-ship.tar-2-.md5
stock.vzw_root66.
Now lets Start
Make sure phone is off. Boot into download mode. To do so, hold down the Volume Down, Home and then the Power buttons together until a Warning!! message is displayed on the screen. Here, press Volume Up to enter download mode. A green Android and the text Downloading will be displayed on the screen.
Now, open Odin by clicking on the Odin3 v3.07.exe file in the Odin307 folder which you obtained after extracting Odin307.zip
In Odin, click on the PDA button, then select the VRALEC.bootchain.tar.md5 file that you downloaded.
Important Untick every option under the “Option” section (on the top left of Odin), except F. Reset Time. Check the screenshot below for reference.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then, connect the phone to the computer with the USB cable and wait for Windows to finish installing drivers. Odin will say Added!! in the message box on the bottom left if the phone is detected successfully. If not, make sure the drivers are installed and also try using a different USB port – preferably a USB port on the back if using a desktop computer.
Click on Start to start flashing the VRALEC.bootchain.tar.md5 file on the phone.
Wait till flashing is complete and you get a PASS message in Odin. When that happens, disconnect the phone from the computer, but DON’T turn it off and let it stay in download mode. Also close Odin.
Reconnect your phone to the computer (while it is in download mode). Open Odin again.
This time, click the PDA button and select the BOOTLOADER_I535VRALF2_618049_REV09_user_low_ship.tar.md5 file that you download
Also, again untick every option except F. Reset Time in Odin. Then, click on the Start button to start flashing the BOOTLOADER_I535VRALF2_618049_REV09_user_low_ship.tar.md5 file on the phone.
When flashing is complete and you get a PASS message, disconnect the phone and close Odin. But keep the phone in download mode, don’t turn it off.
Open Odin again and also reconnect the phone to the computer.
Click the PDA file and select the stock.vzw_root66.tar file that you Downloaded
[Important] Select the following three options in Odin on the top left: Auto Reboot, F. Reset Time, Nand Erase All. Check the screenshot below for reference.
Click Start to start the flashing process. Once the flashing is complete and you get a PASS message, the phone will automatically reboot. Disconnect the phone from the computer.
The phone will still not boot up completely. Now, remove the battery on the phone, then re-insert it. Don’t turn it on.
Now, boot into recovery. To do so, press and hold the Volume Up + Home + Power buttons together till the screen turns on, then let the buttons go. The phone will boot into recovery in a few seconds. You will see a few error messages in recovery, which is normal.
In recovery, use the volume buttons to scroll up/down and the home button to select options.
Select wipe data/factory reset, then select Yes on next screen to confirm. Wait a while till the data wipe is complete (this will NOT delete your personal files on the SD cards).
Select wipe cache, confirm, then wait for cache wipe to be completed.
Then, select reboot system now to reboot the phone.
The phone will now boot up properly into Android and is fixed, and you will be able to use it now.
Your Verizon Galaxy S3 is now fixed, and saved you from sending it in for repair to Verizon. Do let me know how the procedure works!
HOW TO UNBRICK YOUR DEVICE
REQUIREMENTS TO UNBRICK YOUR PHONE
First install java on your pc if you haven’t java go to Java site and install it.
download one-click Unbrick tool
window users will need .rar/.zip extractor software , you can download free all in one 7zip extractor form here.
FOLLOW THESE INSTRUCTIONS CAREFULLY
1. Right-click on the One-Click.jar file, move down to option “7-zip” and then select “Extract to OneClick”.
2. Now you will get a ‘OneClick’ folder.
3. Now copy ‘OneClick.jar’ file and paste it into the ‘OneClickheimdalloneclickresourcesHeimdallPackage’ folder.
4. Right-click on ‘oneclickloader.exe’ file and choose ‘Run as Administrator’.
5. Proceed with the installation of Heimdall.
6. After the installation is complete, you will see the the One-Click UnBrick interface.
Connect the phone to computer via USB and click on “unsoft brick” button to recover your bricked android phone.
Factory Rom's
Factory Images for Nexus Devices
https://developers.google.com
SAMMOBILE
http://www.sammobile.com/
ROM DOWNLOADS FOR HTC
http://www.htc.com/us/support/rom-downloads.html
HTC UNLOCK BOOTLOADER
https://www.htcdev.com/
Motorola
https://motorola-global-portal.cust...e/bootloader/unlock-your-device-a/action/auth
UNLOCK YOUR Motorola BOOTLOADER
https://motorola-global-portal.cust...e/bootloader/unlock-your-device-a/action/auth
RE-LOCK YOUR Motorola BOOTLOADER AND FACTORY IMAGES FOR DEVELOPER EDITION DEVICES
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
Moto Support
https://motorola-global-portal.custhelp.com/app/home/
LG Software & tools Download
http://www.mylgphones.com/lg-software-tools-download
CLOCKWORKMOD RECOVERY & ROMS Phone Selection
http://www.clockworkmod.com/rommanager
TeamWin - TWRP
https://twrp.me/
ANDROID SDK
http://developer.android.com/sdk/index.html
ADB GUIDE
http://developer.android.com/tools/help/adb.html
Good job mate! I will be adding this to my help thread soon! :good:
immortalneo said:
Good job mate! I will be adding this to my help thread soon! :good:
Click to expand...
Click to collapse
Thank You Just updated
Help Please
I have a VIZIO VTAB1008 that is not turning on. when i plug it in the screen stays off and only the soft keys blink. i cant get into recovery and have no idea what to do.
Dose anyone know how to correct this problem?
or any programs that can help me recover it from a usb?
i am using windows 7 ulmimate 32-bit
DustinGrinder said:
I have a VIZIO VTAB1008 that is not turning on. when i plug it in the screen stays off and only the soft keys blink. i cant get into recovery and have no idea what to do.
Dose anyone know how to correct this problem?
or any programs that can help me recover it from a usb?
i am using windows 7 ulmimate 32-bit
Click to expand...
Click to collapse
How long have you had it? Is it rooted? And What happed before this happed?
You Can Try This
1. Before starting, make sure that the tablet is powered off. Not just in sleep mode. Now press & hold both the UP and DOWN volume buttons at the same time. You may find it easier to hold the tablet in the landscape position on a table or on your lap while you hold down both buttons.
2. Next press and hold the power button until the tablet buttons light up. It will take a minute to happen, but when they do immediately let go of the power button ONLY. Keep holding down both the UP and DOWN volume buttons. You only have a second to do this other wise the tablet will continue boot up as normal and you will have to start again from step one.
3. After a bit of holding down both volume keys the screen will show the Vizio logo. Then the logo will change to a TRIANGLE with an exclamation mark.
4. Now you can let go of the volume buttons.
5. Tap the home button to pop up the boot recovery menu. Follow the instructions to reset your tablet. Pressing the up/down volume buttons allow you to scroll up and down the list. A quick press on the power button will accept your selection.
6. Wait for the tablet to come up.
good luck. and post results
soft brick
keifus.rahn said:
RECOVERY FROM BOOT LOOP/BRICK
Most people use the term "bricked" improperly. A bricked phone means one thing: your phone won't turn on in any way, shape or form, and there's Probably nothing you can do to fix it. It is, for all intents and purposes, as useful as a brick. A phone stuck in a boot loop is not bricked, nor is a phone that boots straight into recovery mode. These are things you can usually fix, and they're a lot more common than a truly bricked phone. If your phone is actually bricked, you Probably won't be able to fix it yourself.
BOOTLOOP GUIDE
(#:1)
Start by removing the device's battery and wait for a few minute's before putting it back in your phone.
OR Switch off for non-removable battery phones for five to ten minutes so it can remove any charge that is left in the phone and to initiate a complete power-cycle once you insert the battery.
Now Boot the device into Recovery Mode by pressing and holding the relevant shortcut keys for your device. For instance, most Samsung devices can boot into Recovery Mode while pressing the key combination Volume Up, Home and Power (for tablets it is Volume Up and Power). If using a HTC phone, boot into HBOOT first by tapping Volume Down and Power button together and then browse to Recovery using Volume Up/ Down buttons. If you cant get it to boot in Recovery you can always use (ADB) and type in the command] > adb reboot recovery <--- Hit Enter now your Device will reboot into recovery mode. If your not familar with adb or even know what adb is there is a link on the bottom of this page for the sdk download and a gude on the adb.
(#:2)
Now browse and select the option Wipe Data/Factory Reset in Recovery Mode.Check if the device can now boot into the newly installed ROM or firmware. If not, then perform Wipe Cache Partition And Return to the main Recovery menu and reboot the device by choosing Reboot System Now option.After Flashing or Installing a New ROM and If the device is already rooted with ClockworkMod Recovery (CWM) installed, then do the following steps (1) Remove you'r battery and reinsert it after 30 seconds. (2) Boot the device into CWM Recovery by pressing and holding Volume Up, Home and Power buttons together. NOTE: The key combination may vary depending on your device model.So, CONFIRM BEFORE YOU PROCEED. (3) Now Go to Advanced option in Recovery menu and choose Wipe Dalvik Cache. Then perform Wipe/cache under Mounts & Storage. Reboot the device and check if the boot loop issue is resolved. If not repeat the above three steps, but perform both Wipe/data and Wipe/cache under Mounts & Storage before rebooting.
(#:3)
After Setting an Incorrect File Permission.The Android operating system (OS) works on file permissions and hence incorrectly set file permissions may permanently damage or soft brick your device. Here are some of the commonly used file permissions:- 644 (RW-R-R) - (this is most common system permission, it exists in /system/app, /system/framework, /system/etc, /system/lib and allot of separate files) - 755 (RWX-RX-RX) - (mainly used for /system/bin) - 777 (RWX-RWX-RWX) - (used for scripts inside /system/etc/init.d and busybox files)
To fix or reset any of these file permissions, do the following:Boot the device into CWM or TWRP recovery Go to Advanced option.Click Fix Permission and confirm the action. After Restoring a Backup.If the bootloop error occurs immediately after restoring a Nandroid Backup, follow the steps on -(#:2)- to fix it. If everything else fails, just try re installing the original ROM or flash the first official firmware.
Using ADB BY Samantha
DB can be used to access the phone while booting, be aware that some bootloops make it unable to use ADB since they do not go further then the manufacturer logo. (In new CWM versions it’s possible to use adb)
The only tricky part about using ADB with bootloops is that you have to do it on the right time, this is different from every device, but normally it’s after the manufacturer logo that the partitions get mounted. The easiest way to enter your phone in this part is using a batch script that monitors the state of your device and connects directly when possible.
I use this script for example, called ondemand.bat (requires adb.exe and the 2 dlls)
1 @ECHO off
2 cd /d %~dp0
3 echo.
4 echo Waiting for device…
5 adb wait-for-device
6 echo.
7 adb -d shell stop
8 adb push mycwmfix.zip /sdcard/mycwmfix.zip
9 adb reboot recovery
Linux Version (ondemand.sh):
1 #!/system/bin/sh
2 echo " "
3 echo "Wating for device..."
4 ./adb wait-for-device
5 echo " "
6 ./adb -d shell stop
7 ./adb push mycwmfix.zip /sdcard/mycwmfix.zip
8 ./adb reboot recovery
This script will wait for the device to become ready, when it’s ready it freeze the device, so the script has more time to push the file (instead of keep rebooting). Then it will push the specified cwmfix zip to your sdcard, and after that it will reboot in recovery so you can install the cwm fix you made. You can also make an batch script that pushes the files automatically to your phone, here is an example:
(1 @ECHO off
(2)cd /d %~dp0
(3)echo.
(4)echo Waiting for device...adb wait-for-device
(5)echo.
(6)adb -d shell stop
(7)adb -d shell su -c "mount -o remount rw /system"
(8)adb push framework-res.apk /system/framework/framework-res.apk
(9)adb -d shell chmod 644 /system/framework/framework-res.apk
(10)adb push SystemUI.apk /system/app/SystemUI.apk
(11)adb -d shell chmod 644 /system/app/SystemUI.apk
(12)adb reboot
(13)Linux version:
1#!/system/bin/sh
2echo " "
3echo "Waiting for device..."
4./adb wait-for-device
5echo " "
6./adb -d shell stop
7./adb -d shell su -c "mount -o remount rw /system"
8./adb push framework-res.apk /system/framework/framework-res.apk
9./adb -d shell chmod 644 /system/framework/framework-res.apk
10./adb push SystemUI.apk /system/app/SystemUI.apk
11./adb -d shell chmod 644 /system/app/SystemUI.apk
12./adb reboot
This script will wait for the device to become ready, when it’s ready it freeze the device, so the script has more time to push the file (instead of keep rebooting). Then it will push framework-res.apk and SystemUI.apk to the directory it belongs to, after that it changes the permissions of the files to RW-R-R (644) and then it will reboot.
Please note that on some devices the command “su -c” cannot be used after using the “stop” command, it gives an error then (Segmentation Fault).
What you can do to prevent this is adding “adb remount” just under the “adb wait-for-device” line, and remove the “adb -d shell su -c “mount -o remount rw /system” line.
Save the script and run it again.
For HTC Phones: HTC phones can flash stock ROMs, known as RUUs, right from the phone's bootloader. You'll need to Google around for your device's specific RUU file, but once you download it, save the ZIP file to your SD card, and rename it (to something like PG05IMG.zip—the download page for the RUU file should specify which filename is required), booting up your phone should automatically flash the stock ROM from HBOOT, HTC's bootloader. Video http://www.youtube.com/watch?feature=player_embedded&v=tE8BiIFUOpk
For Samsung Phones If you're using a Samsung Galaxy phone, you can use a tool called Odin to reflash an OPS file, which is a stock ROM that will return your phone to factory settings. You'll need a Windows machine and a copy of Odin, which you can find by Googling around the net (as its not an official tool) check out The Unlockr's guide to using Odin to familiarize yourself. You may need to Google around for your specific device's OPS file and instructions.
Video http://www.youtube.com/watch?feature=player_embedded&v=5s70dwNgdD8
Verizon Galaxy S3 Bootloop fix using Odin
The Verizon Galaxy S3 has to be the most problematic variant of the Galaxy S3. If the locked bootloader on it wasn’t enough, many users have seen their Verizon Galaxy S3 get bricked and stop booting after trying to flash a custom ROM.
To start off there will be a little bit of downloading
Samsung USB Driver V1.5.14.0 For Android Mobile Devices
ODIN
VRALEC.bootchain.tar.md5
BOOTLOADER-I535VRALF2-618049-REV09-user-low-ship.tar-2-.md5
stock.vzw_root66.
Now lets Start
Make sure phone is off. Boot into download mode. To do so, hold down the Volume Down, Home and then the Power buttons together until a Warning!! message is displayed on the screen. Here, press Volume Up to enter download mode. A green Android and the text Downloading will be displayed on the screen.
Now, open Odin by clicking on the Odin3 v3.07.exe file in the Odin307 folder which you obtained after extracting Odin307.zip
In Odin, click on the PDA button, then select the VRALEC.bootchain.tar.md5 file that you downloaded.
Important Untick every option under the “Option” section (on the top left of Odin), except F. Reset Time. Check the screenshot below for reference.
Then, connect the phone to the computer with the USB cable and wait for Windows to finish installing drivers. Odin will say Added!! in the message box on the bottom left if the phone is detected successfully. If not, make sure the drivers are installed and also try using a different USB port – preferably a USB port on the back if using a desktop computer.
Click on Start to start flashing the VRALEC.bootchain.tar.md5 file on the phone.
Wait till flashing is complete and you get a PASS message in Odin. When that happens, disconnect the phone from the computer, but DON’T turn it off and let it stay in download mode. Also close Odin.
Reconnect your phone to the computer (while it is in download mode). Open Odin again.
This time, click the PDA button and select the BOOTLOADER_I535VRALF2_618049_REV09_user_low_ship.tar.md5 file that you download
Also, again untick every option except F. Reset Time in Odin. Then, click on the Start button to start flashing the BOOTLOADER_I535VRALF2_618049_REV09_user_low_ship.tar.md5 file on the phone.
When flashing is complete and you get a PASS message, disconnect the phone and close Odin. But keep the phone in download mode, don’t turn it off.
Open Odin again and also reconnect the phone to the computer.
Click the PDA file and select the stock.vzw_root66.tar file that you Downloaded
[Important] Select the following three options in Odin on the top left: Auto Reboot, F. Reset Time, Nand Erase All. Check the screenshot below for reference.
Click Start to start the flashing process. Once the flashing is complete and you get a PASS message, the phone will automatically reboot. Disconnect the phone from the computer.
The phone will still not boot up completely. Now, remove the battery on the phone, then re-insert it. Don’t turn it on.
Now, boot into recovery. To do so, press and hold the Volume Up + Home + Power buttons together till the screen turns on, then let the buttons go. The phone will boot into recovery in a few seconds. You will see a few error messages in recovery, which is normal.
In recovery, use the volume buttons to scroll up/down and the home button to select options.
Select wipe data/factory reset, then select Yes on next screen to confirm. Wait a while till the data wipe is complete (this will NOT delete your personal files on the SD cards).
Select wipe cache, confirm, then wait for cache wipe to be completed.
Then, select reboot system now to reboot the phone.
The phone will now boot up properly into Android and is fixed, and you will be able to use it now.
Your Verizon Galaxy S3 is now fixed, and saved you from sending it in for repair to Verizon. Do let me know how the procedure works!
HOW TO UNBRICK YOUR DEVICE
REQUIREMENTS TO UNBRICK YOUR PHONE
First install java on your pc if you haven’t java go to Java site and install it.
download one-click Unbrick tool
window users will need .rar/.zip extractor software , you can download free all in one 7zip extractor form here.
FOLLOW THESE INSTRUCTIONS CAREFULLY
1. Right-click on the One-Click.jar file, move down to option “7-zip” and then select “Extract to OneClick”.
2. Now you will get a ‘OneClick’ folder.
3. Now copy ‘OneClick.jar’ file and paste it into the ‘OneClickheimdalloneclickresourcesHeimdallPackage’ folder.
4. Right-click on ‘oneclickloader.exe’ file and choose ‘Run as Administrator’.
5. Proceed with the installation of Heimdall.
6. After the installation is complete, you will see the the One-Click UnBrick interface.
Connect the phone to computer via USB and click on “unsoft brick” button to recover your bricked android phone.
DOWNLOAD LINKS
CLOCKWORKMOD RECOVERY & ROMS Phone Selection
http://www.clockworkmod.com/rommanager
ANDROID SDK
http://developer.android.com/sdk/index.html
ADB GUIDE
http://developer.android.com/tools/help/adb.html
CLOCKWORKMOD-HELIUM
http://http://www.clockworkmod.com/carbon
Click to expand...
Click to collapse
For samsung do you have to use the stock rom or after wipe can use a custom? I'm in a soft loop after rooting and then I forgot something and did a twrp restore after wipe. I really want to use jedi now but it seems like I hv to use stock rom n then re root ?
Cannot go into download mode or fastboot mode No access to recovery
I'm using Karbonn titanium s9 and had just caused bootlooop problem in my phone as i was attempting to intsall a custom rom..
I have no access to the recovery , my phone just go to the comapany logo and then reboot ...
plzzz tell me how to flash a fresh custom rom into it using computer....
please mention all keys for differnt modes..
Thanks in advance and wanted help as soon as possible becuase i have brought phone 5 days before a biricked it...
THanks.....☺
Lost Data Karbonn Titanium S9 Recovery
Karbonn Titanium S9 is an amazing gift of technology using which you can do lot more than just communicating. This Smartphone is developed on most popular and used operating system i.e. Android and built-in with fantastic features, which keeps you busy enjoying all time. But Karbonn Titanium S9 too has sinister sides as one might lose data from it due to some uncontrollable reasons. Since it’s not just a normal phone, it might contain large amount of your valuable data such as images, audios, videos, games, applications, documents, etc., and losing one of it might create panic. Relax..! Need not to panic, since Karbonn Titanium S9 recovery is possible with trustworthy recovery software.
It’s pretty common to suffer data loss from Smartphones, since it is an entirely unpredictable scenario. But one should also know about its causes so that he / she might avoid it in possible circumstance. Just go through the below section to know more about these scenarios:
Use of factory restore / reset option accidentally might invite the data loss
When SD card or any other memory card mounted on S9 phone gets corrupt or become inaccessible
Severe infection of spyware, malware and virus may lead to data loss
Abrupt switching off the Karbonn Titanium S9 numerous times might make few files go missing
Unintentional formatting, deleting of data by wrong touch
Unwanted changes after rooting Karbonn Titanium S9 may contribute to data crisis
What to? What not to?
Data recovery experts recommend you some tips and advice you certain things to stay away from in order to perform complete recovery of Karbonn Titanium S9 data. First let’s see what to do, when you come across data loss on your Karbonn Titanium S9.
Keep backup of the data and files that are important to you, so as to avert data disasters
Immediately discontinue the use of Karbonn Titanium S9 as soon as you come across data loss
Opt of reliable and safe recovery tool without wasting much of the time
Here are some things, which you need to avoid after facing loss of data:-
Do not even attempt tasks like rooting, formatting, etc., until you know the complete process
Do not add or edit data on your Karbonn Titanium S9 Smartphone
Do not carry out task like updating the software or version of phone
Well by following these tips you can avert data overwriting and increase the chances of safe and complete Karbonn Titanium S9 data recovery.
What’s next?
Next is Remo Recover..! Yes, it is a smart tool that is designed for Smartphone data recovery using which you can effectively recover Karbonn Titanium S9 data in few simple clicks on mouse button. Software is ahead of its competition as it is integrated with hi-tech data retrieval procedures and assists you to restore Karbonn Titanium S9 data from all severe data crisis. Remo Recover is pre-scanned for faulty and dangerous items and certified as absolutely safe and reliable to use.
Few striking attributes of Remo Recover..!
Makes an entire scan of both internal and external memory of phone and help you to retrieve lost data from Karbonn Titanium S9
Trouble free and easy to understand GUI helps a novice to execute Karbonn Titanium S9 recovery on its own
Its smart searching algorithms examines complete drive in just one scan
Tool has the caliber of recognizing Android application files with (.apk) and recovering it along with photo, video and audio file formats
Authorize you to sort recovered data after completion of lost data recovery from Karbonn Titanium S9
Prior look of recovered files can be seen using “preview” option.
You can perform lost data Karbonn Titanium S9 recovery on all types of Android version and from all Windows OS based computers
Step 1: Connect your Karbonn Titanium S9 to Windows computer using a USB cable and wait until connection gets established.
Figure A: Detecting Device
Step 2: Now Main screen gets open from were you can select either “Recover Deleted Files” or “Recover Lost Files” option as per your requirement.
Figure B: Main Screen
Step 3: Select Karbonn Titanium S9 drive and click “Next” button for software to begin scanning process.
http://www.remorecover.com/images/android/remorecover-android-select-physical-drive.jpg
Figure C: Select Karbonn Titanium S9 Drive
Step 4: Once Remo Recover completes the scanning process you can view list of recovered data/files in two types of view which are “File Type View” and “Data View”
Figure D: List of Recovered Data
Step 5: You can preview recovered data using Preview option and save it to any location.
Figure E: Preview Recovered Data
DOWNLOAD LINK http://www.remorecover.com/download/remorecover-android.exe
My phone is stuck in a boot loop after trying to update it. I only just bought it and cache wipes, factory reset don't work. For some reason it won't connect to the computer or kies even after reinstalling drivers and using multiple different usb ports. It was working fun before I updated it. Anyone have any ideas? I'm pretty desperate right now
help! for flashing ROM from similar device
hi @keifus.rahn,
I have got an MTK6589 16gb rom 1 gb ram 5.5 inch HD display karbonn s9 device. I have found that it is similar to star 7599 and alps n9202 in configuration. Problem is that I have bricked my phone 1 month earlier and since then have been trying to flash ROMS from devices like mentioned above.There is no official firmware for the device till now.Every time SP flash tool returns error and does not flash.
Is there any way I can alter these roms from other similar devices to make it flashable through SPTool on my device (example, like using similar kernel etc.).Porting would not help me as the phone is bricked.
Please help me as I could not get any help from anyone.I would be very grateful to you.
Other option
This thread was really helpful. I updated my ROM, running legacy AOSPA on Xperia S. Last update had me stuck on the manufacturer logo and I couldn't roll back to the previous ROM, CM wouldn't let me install older software. I tried the steps but it didn't work for me, finally decided to wipe system as a result and reinstall everything. This got it to work. I suppose my point is that sometimes it's best to format/wipe the system.
Master Limbe said:
This thread was really helpful. I updated my ROM, running legacy AOSPA on Xperia S. Last update had me stuck on the manufacturer logo and I couldn't roll back to the previous ROM, CM wouldn't let me install older software. I tried the steps but it didn't work for me, finally decided to wipe system as a result and reinstall everything. This got it to work. I suppose my point is that sometimes it's best to format/wipe the system.
Click to expand...
Click to collapse
I'm glad to hear that this thread helped you out. I do a full wipe every time i flash a new Rom and always remember to make a backup
Bootloop after repartition
I've a rooted ZTE V972M. I tried to increase internal storage following instructions in
"Re-Partition any MTK6589 Phone, Without A PC! (More /Data Storage!)"
When I reboot my phone, it stucks at logo screen.
What I've done trying to fix it:
1. Enter the recovery mode; it's a stock recovery (Android system recovery <3e>); wipe data/factory reset, wipe cache partition.
Result: still stuck at logo when rebooting.
2. Flash a stock ROM in recovery mode.
Result: Update aborted. In the log file, it says "failed to mount /cache (No such file or directory)" detailed in attached file. The stock rom I used is for ZTE LEO S1, while my phone is DTAC LION HD which is a house brand of my phone carrier. So, there may be also a problem of ROM signing.
3. I cannot use ADB or Fastboot because I didn't enable USB debugging (My phone's OS is android 4.2).
Please guide me to fix this problem.
Hi, sorry for reviving this topic, but I'm stuck in a bootloop on my Galaxy Note 10.1 2014 edition (SM-P605).
The problem is that the battery of my Note is built-in and can't be removed without some serious hardware modifications.
Also, when I try to shut it down (hold the Power button), it starts up on its own immediately afterwards...
And its battery is not going to run out soon at this pace. Anything I could do?
Need Help. 100% dont know what to do..
keifus.rahn said:
RECOVERY FROM BOOT LOOP/BRICK
Most people use the term "bricked" improperly. A bricked phone means one thing: your phone won't turn on in any way, shape or form, and there's Probably nothing you can do to fix it. It is, for all intents and purposes, as useful as a brick. A phone stuck in a boot loop is not bricked, nor is a phone that boots straight into recovery mode. These are things you can usually fix, and they're a lot more common than a truly bricked phone. If your phone is actually bricked, you Probably won't be able to fix it yourself.
BOOTLOOP GUIDE
(#:1)
Start by removing the device's battery and wait for a few minute's before putting it back in your phone.
OR Switch off for non-removable battery phones for five to ten minutes so it can remove any charge that is left in the phone and to initiate a complete power-cycle once you insert the battery.
Now Boot the device into Recovery Mode by pressing and holding the relevant shortcut keys for your device. For instance, most Samsung devices can boot into Recovery Mode while pressing the key combination Volume Up, Home and Power (for tablets it is Volume Up and Power). If using a HTC phone, boot into HBOOT first by tapping Volume Down and Power button together and then browse to Recovery using Volume Up/ Down buttons. If you cant get it to boot in Recovery you can always use (ADB) and type in the command] > adb reboot recovery <--- Hit Enter now your Device will reboot into recovery mode. If your not familar with adb or even know what adb is there is a link on the bottom of this page for the sdk download and a gude on the adb.
(#:2)
Now browse and select the option Wipe Data/Factory Reset in Recovery Mode.Check if the device can now boot into the newly installed ROM or firmware. If not, then perform Wipe Cache Partition And Return to the main Recovery menu and reboot the device by choosing Reboot System Now option.After Flashing or Installing a New ROM and If the device is already rooted with ClockworkMod Recovery (CWM) installed, then do the following steps (1) Remove you'r battery and reinsert it after 30 seconds. (2) Boot the device into CWM Recovery by pressing and holding Volume Up, Home and Power buttons together. NOTE: The key combination may vary depending on your device model.So, CONFIRM BEFORE YOU PROCEED. (3) Now Go to Advanced option in Recovery menu and choose Wipe Dalvik Cache. Then perform Wipe/cache under Mounts & Storage. Reboot the device and check if the boot loop issue is resolved. If not repeat the above three steps, but perform both Wipe/data and Wipe/cache under Mounts & Storage before rebooting.
(#:3)
After Setting an Incorrect File Permission.The Android operating system (OS) works on file permissions and hence incorrectly set file permissions may permanently damage or soft brick your device. Here are some of the commonly used file permissions:- 644 (RW-R-R) - (this is most common system permission, it exists in /system/app, /system/framework, /system/etc, /system/lib and allot of separate files) - 755 (RWX-RX-RX) - (mainly used for /system/bin) - 777 (RWX-RWX-RWX) - (used for scripts inside /system/etc/init.d and busybox files)
To fix or reset any of these file permissions, do the following:Boot the device into CWM or TWRP recovery Go to Advanced option.Click Fix Permission and confirm the action. After Restoring a Backup.If the bootloop error occurs immediately after restoring a Nandroid Backup, follow the steps on -(#:2)- to fix it. If everything else fails, just try re installing the original ROM or flash the first official firmware.
Using ADB BY Samantha
DB can be used to access the phone while booting, be aware that some bootloops make it unable to use ADB since they do not go further then the manufacturer logo. (In new CWM versions it’s possible to use adb)
The only tricky part about using ADB with bootloops is that you have to do it on the right time, this is different from every device, but normally it’s after the manufacturer logo that the partitions get mounted. The easiest way to enter your phone in this part is using a batch script that monitors the state of your device and connects directly when possible.
I use this script for example, called ondemand.bat (requires adb.exe and the 2 dlls)
1 @ECHO off
2 cd /d %~dp0
3 echo.
4 echo Waiting for device…
5 adb wait-for-device
6 echo.
7 adb -d shell stop
8 adb push mycwmfix.zip /sdcard/mycwmfix.zip
9 adb reboot recovery
Linux Version (ondemand.sh):
1 #!/system/bin/sh
2 echo " "
3 echo "Wating for device..."
4 ./adb wait-for-device
5 echo " "
6 ./adb -d shell stop
7 ./adb push mycwmfix.zip /sdcard/mycwmfix.zip
8 ./adb reboot recovery
This script will wait for the device to become ready, when it’s ready it freeze the device, so the script has more time to push the file (instead of keep rebooting). Then it will push the specified cwmfix zip to your sdcard, and after that it will reboot in recovery so you can install the cwm fix you made. You can also make an batch script that pushes the files automatically to your phone, here is an example:
(1 @ECHO off
(2)cd /d %~dp0
(3)echo.
(4)echo Waiting for device...adb wait-for-device
(5)echo.
(6)adb -d shell stop
(7)adb -d shell su -c "mount -o remount rw /system"
(8)adb push framework-res.apk /system/framework/framework-res.apk
(9)adb -d shell chmod 644 /system/framework/framework-res.apk
(10)adb push SystemUI.apk /system/app/SystemUI.apk
(11)adb -d shell chmod 644 /system/app/SystemUI.apk
(12)adb reboot
(13)Linux version:
1#!/system/bin/sh
2echo " "
3echo "Waiting for device..."
4./adb wait-for-device
5echo " "
6./adb -d shell stop
7./adb -d shell su -c "mount -o remount rw /system"
8./adb push framework-res.apk /system/framework/framework-res.apk
9./adb -d shell chmod 644 /system/framework/framework-res.apk
10./adb push SystemUI.apk /system/app/SystemUI.apk
11./adb -d shell chmod 644 /system/app/SystemUI.apk
12./adb reboot
This script will wait for the device to become ready, when it’s ready it freeze the device, so the script has more time to push the file (instead of keep rebooting). Then it will push framework-res.apk and SystemUI.apk to the directory it belongs to, after that it changes the permissions of the files to RW-R-R (644) and then it will reboot.
Please note that on some devices the command “su -c” cannot be used after using the “stop” command, it gives an error then (Segmentation Fault).
What you can do to prevent this is adding “adb remount” just under the “adb wait-for-device” line, and remove the “adb -d shell su -c “mount -o remount rw /system” line.
Save the script and run it again.
For HTC Phones: HTC phones can flash stock ROMs, known as RUUs, right from the phone's bootloader. You'll need to Google around for your device's specific RUU file, but once you download it, save the ZIP file to your SD card, and rename it (to something like PG05IMG.zip—the download page for the RUU file should specify which filename is required), booting up your phone should automatically flash the stock ROM from HBOOT, HTC's bootloader. Video http://www.youtube.com/watch?feature=player_embedded&v=tE8BiIFUOpk
For Samsung Phones If you're using a Samsung Galaxy phone, you can use a tool called Odin to reflash an OPS file, which is a stock ROM that will return your phone to factory settings. You'll need a Windows machine and a copy of Odin, which you can find by Googling around the net (as its not an official tool) check out The Unlockr's guide to using Odin to familiarize yourself. You may need to Google around for your specific device's OPS file and instructions.
Video http://www.youtube.com/watch?feature=player_embedded&v=5s70dwNgdD8
Verizon Galaxy S3 Bootloop fix using Odin
The Verizon Galaxy S3 has to be the most problematic variant of the Galaxy S3. If the locked bootloader on it wasn’t enough, many users have seen their Verizon Galaxy S3 get bricked and stop booting after trying to flash a custom ROM.
To start off there will be a little bit of downloading
Samsung USB Driver V1.5.14.0 For Android Mobile Devices
ODIN
VRALEC.bootchain.tar.md5
BOOTLOADER-I535VRALF2-618049-REV09-user-low-ship.tar-2-.md5
stock.vzw_root66.
Now lets Start
Make sure phone is off. Boot into download mode. To do so, hold down the Volume Down, Home and then the Power buttons together until a Warning!! message is displayed on the screen. Here, press Volume Up to enter download mode. A green Android and the text Downloading will be displayed on the screen.
Now, open Odin by clicking on the Odin3 v3.07.exe file in the Odin307 folder which you obtained after extracting Odin307.zip
In Odin, click on the PDA button, then select the VRALEC.bootchain.tar.md5 file that you downloaded.
Important Untick every option under the “Option” section (on the top left of Odin), except F. Reset Time. Check the screenshot below for reference.
Then, connect the phone to the computer with the USB cable and wait for Windows to finish installing drivers. Odin will say Added!! in the message box on the bottom left if the phone is detected successfully. If not, make sure the drivers are installed and also try using a different USB port – preferably a USB port on the back if using a desktop computer.
Click on Start to start flashing the VRALEC.bootchain.tar.md5 file on the phone.
Wait till flashing is complete and you get a PASS message in Odin. When that happens, disconnect the phone from the computer, but DON’T turn it off and let it stay in download mode. Also close Odin.
Reconnect your phone to the computer (while it is in download mode). Open Odin again.
This time, click the PDA button and select the BOOTLOADER_I535VRALF2_618049_REV09_user_low_ship.tar.md5 file that you download
Also, again untick every option except F. Reset Time in Odin. Then, click on the Start button to start flashing the BOOTLOADER_I535VRALF2_618049_REV09_user_low_ship.tar.md5 file on the phone.
When flashing is complete and you get a PASS message, disconnect the phone and close Odin. But keep the phone in download mode, don’t turn it off.
Open Odin again and also reconnect the phone to the computer.
Click the PDA file and select the stock.vzw_root66.tar file that you Downloaded
[Important] Select the following three options in Odin on the top left: Auto Reboot, F. Reset Time, Nand Erase All. Check the screenshot below for reference.
Click Start to start the flashing process. Once the flashing is complete and you get a PASS message, the phone will automatically reboot. Disconnect the phone from the computer.
The phone will still not boot up completely. Now, remove the battery on the phone, then re-insert it. Don’t turn it on.
Now, boot into recovery. To do so, press and hold the Volume Up + Home + Power buttons together till the screen turns on, then let the buttons go. The phone will boot into recovery in a few seconds. You will see a few error messages in recovery, which is normal.
In recovery, use the volume buttons to scroll up/down and the home button to select options.
Select wipe data/factory reset, then select Yes on next screen to confirm. Wait a while till the data wipe is complete (this will NOT delete your personal files on the SD cards).
Select wipe cache, confirm, then wait for cache wipe to be completed.
Then, select reboot system now to reboot the phone.
The phone will now boot up properly into Android and is fixed, and you will be able to use it now.
Your Verizon Galaxy S3 is now fixed, and saved you from sending it in for repair to Verizon. Do let me know how the procedure works!
HOW TO UNBRICK YOUR DEVICE
REQUIREMENTS TO UNBRICK YOUR PHONE
First install java on your pc if you haven’t java go to Java site and install it.
download one-click Unbrick tool
window users will need .rar/.zip extractor software , you can download free all in one 7zip extractor form here.
FOLLOW THESE INSTRUCTIONS CAREFULLY
1. Right-click on the One-Click.jar file, move down to option “7-zip” and then select “Extract to OneClick”.
2. Now you will get a ‘OneClick’ folder.
3. Now copy ‘OneClick.jar’ file and paste it into the ‘OneClickheimdalloneclickresourcesHeimdallPackage’ folder.
4. Right-click on ‘oneclickloader.exe’ file and choose ‘Run as Administrator’.
5. Proceed with the installation of Heimdall.
6. After the installation is complete, you will see the the One-Click UnBrick interface.
Connect the phone to computer via USB and click on “unsoft brick” button to recover your bricked android phone.
DOWNLOAD LINKS
CLOCKWORKMOD RECOVERY & ROMS Phone Selection
http://www.clockworkmod.com/rommanager
ANDROID SDK
http://developer.android.com/sdk/index.html
ADB GUIDE
http://developer.android.com/tools/help/adb.html
CLOCKWORKMOD-HELIUM
http://http://www.clockworkmod.com/carbon
Click to expand...
Click to collapse
Hello SIr, please help me with my Android Phone, its brand is not familliar to you.. but here it is.
Myphone Agua Hail
the problem is that, after I rooted my device is that, I cannot do Factory Reset anymore. And when I try to do the ff.
1. recovery mode, I cannot do recovery mode too,
What I do is, hold "down volume" and then click "power button" Together. Even I tested the volume up, and Vice Versa.. All that I research about recovery mode, is I'eve done, but none has work, Even the Boot Loop you teach others, I do that too, But it only open Normally and there is a Name that is SAFEMODE, SouthWest of the screen.
Please help me fix my beloved only One phone.
Summary of Problems:
Cannot get to Recovery mode with every reason. \\\\\ A T R O T N
Cannot do Factory Reset. ///// F E R O I G[/SIZE]
im new and have absolutely no clue how to use this site,lol sorry
okay im using lg optimus f6..i noob rooted it :/(rooted with out backing anything up) ive heard of hard bricks where the phone wont turn on,soft bricks where it gets stuck in boot loop or recovery mode..my problem is i installed a font that put me into boot loop,i master reset the phone and IT WORKED turned back on perfectly,until the screen went to sleep :| every time the screen turns off it boot loops..now since i can turn it on i know theres got to be a way to fix it please help someone
i have s2 gt-i9100g i am running on cm11 nightlies i tried flashing blazing kernel v7 when i reboot it says that i may have lost root access so i pressed to fix but it boots into recovery over and over please i need help
Poet432012 said:
okay im using lg optimus f6..i noob rooted it :/(rooted with out backing anything up) ive heard of hard bricks where the phone wont turn on,soft bricks where it gets stuck in boot loop or recovery mode..my problem is i installed a font that put me into boot loop,i master reset the phone and IT WORKED turned back on perfectly,until the screen went to sleep :| every time the screen turns off it boot loops..now since i can turn it on i know theres got to be a way to fix it please help someone
Click to expand...
Click to collapse
Can you list the fonts of your device? As your device is already rooted, go to /system/fonts folder and see if any system font is missing.
I am using Spice Mi-504 (MT6572) at present.
Thanks very much
Bootloop - looking for much needed help
keifus.rahn said:
I'm glad to hear that this thread helped you out. I do a full wipe every time i flash a new Rom and always remember to make a backup
Click to expand...
Click to collapse
Please help. I find your site and this noob's thread is so informative but I couldn't find a way to fix my boot loop. The XDA is full of dev tech jargon, and felt exhausted that I seek help finally here.
My xperia tab z (sgp321 with LTE+WIFI, European version) got into bootloop after flashing CWM 6.0.3.2 (TabZ_DooMLoRD_AdvStkKernel_FW-253-v01.img). The flashing went fine I was able to boot into recovery mode and made a backup. But after the backup is over, and rebooting it prompted Reboot > root access is missing. Root? I selected 'YES' thinking I could root the device. Then bootloop started. I followed all the steps in your thread, Factory reset, Wipe cache, Delvik cache, fix permission etc but still into bootloop.
The device is boot-loader unlocked. It was running KK 4.4.2. Not rooted. I have CM-11-20140723-Nightly-pollux.zip in the external SD card of which I was planning to flash using CWM recovery.
1. What options remain for me to get the device back into original state ? back into 4.4.2.
2. I was able to pass ADB calls. But now since into bootloop, how can I make fastboot/ADB calls to device consistently to do anything realted to reset, recover?
3. In addition to ADB/fastboot, I have Flashtool 0.9.16 by Androxyde with SGP321_10.4.1.B.0.101_CE.ftf stock firmware. Can I flash this Stock ROM while in bootloop ? How can flashtool help in this situation ?
4. The Tablet Z battery is built-in. Does it charge while in bootloop? How can I power-down/shutdown the device without restarting using CWM (it has only reboot option), so that I could fully charge the device ?
Any helpful advise is very much appreciated.
Thank you very much for great work you are doing and the very purpose for XDA - Knowledge Sharing.
---------- Post added at 11:04 AM ---------- Previous post was at 10:41 AM ----------
Master Limbe said:
This thread was really helpful. I updated my ROM, running legacy AOSPA on Xperia S. Last update had me stuck on the manufacturer logo and I couldn't roll back to the previous ROM, CM wouldn't let me install older software. I tried the steps but it didn't work for me, finally decided to wipe system as a result and reinstall everything. This got it to work. I suppose my point is that sometimes it's best to format/wipe the system.
Click to expand...
Click to collapse
Please, can you tell me what steps you made during recovery? My xperia tab z SGP321 (LTE+WIFI European version) is now into bootloop; it was unlocked but not rooted, has CWM 6.0.3.2 and I can boot into recovery mode. Please tell me where to start from ? Can I make ADB/fastboot calls without resolving bootloop or can I flash any stock ROMs using flash tool still with bootloop issue unfixed ? How Can I get the device back into work ?
Much appreciate your help. I have posted details in the same thread.
Thank you.