Database Info

[Q] HELP!!!

Ok, I think I totaly screwed up my captivate. I was trying to update to froyo 2.2 using the Odin one click method, but that didn't work, so instead I tried to instal it by following this guide on youtube (can't post link - new user)
after I did the adb reboot recovery my phone went to the recovery screen. heres what all it says:
update media, please wait...
update media, finished
#MANUA MODE#
--applying muti-csc...
installing muti0csc
mps_dat val:SER
copy_multi_carrier from: SER
multicsc : can not acces to /system/csc/SER/system/
copy_common_data
I tried to select any of the options in recovery mode, update, fatory reset, etc, but I can't select it. I know you're suposed to use the power button to select, but it does nothing. I think its because of the firmware shown on that website, where you would typically use a home key to select.
Please help! I've been working on this thing for hours and I'm completely lost! Is there anything I can do to fix it, or is it totally bricked?

ok my phones now restarted, and its running froyo 2.2, however its turning the wrong orentation and I'm note sure if I can use restart recovery. I just want to put this thing back to factory software!

use the odin 1 click for stock firmware and to update you dont go into recovery you go into download mode

Thanks! I got it back up and running now. In the progress of restoring my backups. Man after this mess, I'm just going to wait for froyo 2.2 to come out...

[HowTo]THE guide to restoring your Milestone 2

This is my tutorial on restoring the Milestone 2. It is more advanced than the other ones out there so I thought hey, let's tell the community. If you don't understand something please reply in this thread and don't PM me.
1. Install RSD Lite 4.9
2. Download and extract The right SBF restore file
3. Plug in your phone. Power it off and hold CAMERA + VOL DOWN
4. On the PC launch RSD Lite, Click on the [...] to the right of filename, browse for the .sbf file you have just extracted.
5. Click on Start
6. In normal cases the phone should boot up now. If you are SURE it doesn't, which is when it tells you to boot up the phone manually follow the next steps.
7. Unplug the phone and pull out the battery.
8. Slide out your keyboard and hold the X button, insert your battery and power it up while still holding the X button.
9. A screen with an exclamation mark pops up, press the @ button on the keyboard to open the recovery menu.
10. Use either the arrows on the keyboard or the VOL UP / VOL DOWN buttons to navigate up and down. Go down to wipe data/factory reset.
11. It will hang at some times but in the end it will say it's done. Hop over to reboot system now and reboot.
Congrats, if the problem was software-based, your phone will boot now!

What if the process doesn't even start? I put my phone in the bootloader mode, plug it in, start up RSD Lite, searh for the sbf on the disk, hit start and then the image starts to unpack from the sbf. So far so good, but when it comes to flashing that image to phone I get an error saying flash failed (in fact it didn' do literally anything to the phone) and displaying info that the phone got a reboot command but didn't respond to it. I tried doing this from booted up android but no luck whatsoever. When I get back home I'll update the post with an error code, maybe you can tell me how the hell I can get my phone to flash sbf seamlessly.
Sent from my Milestone 2

[email protected] said:
What if the process doesn't even start? I put my phone in the bootloader mode, plug it in, start up RSD Lite, searh for the sbf on the disk, hit start and then the image starts to unpack from the sbf. So far so good, but when it comes to flashing that image to phone I get an error saying flash failed (in fact it didn' do literally anything to the phone) and displaying info that the phone got a reboot command but didn't respond to it. I tried doing this from booted up android but no luck whatsoever. When I get back home I'll update the post with an error code, maybe you can tell me how the hell I can get my phone to flash sbf seamlessly.
Sent from my Milestone 2
Click to expand...
Click to collapse
I know it's a bit extreme to do, but it might help for you. Try installing ubuntu or wubi, then use sbf_flash on ubuntu. It takes some time, but if you REALLY need to SBF you should give it a try. Usage is:
chmod 777 sbf_flash
./sbf_flash /path/to/sbf/file

I have no knowledge of ubuntu, but I stomped on the same advice as you have mentioned, before. But I didn't quite understand it clearly. I happened to have a ubuntu live 'cd' on my usb flash drive, I have the needed sbf from the links found in the topic of this forum, but is it all that I need, or am I missing something? Is that command you mentioned is everything I need to run?
Sent from my Milestone 2

[email protected] said:
I have no knowledge of ubuntu, but I stomped on the same advice as you have mentioned, before. But I didn't quite understand it clearly. I happened to have a ubuntu live 'cd' on my usb flash drive, I have the needed sbf from the links found in the topic of this forum, but is it all that I need, or am I missing something? Is that command you mentioned is everything I need to run?
Sent from my Milestone 2
Click to expand...
Click to collapse
You first need to download sbf_flash and extract it to your user directory (the one with downloads, desktop folders). Then open up terminal and execute those commands

What firmware is that file?
I have a copy of MILS2_U6_2.2.19_SIGNED_USAMILESTONE2B1B80VF00B.0R_USXMILE20VFAU_P032_A012_M005_HWp2a_Service1FF.sbf.gz , but don't know if it would be good to flash.

Your firmware is for the Vodafone Australia Milestone 2.
The one in Mikevhl's post is the UK Firmware.

Mikevhl said:
I know it's a bit extreme to do, but it might help for you. Try installing ubuntu or wubi, then use sbf_flash on ubuntu. It takes some time, but if you REALLY need to SBF you should give it a try. Usage is:
chmod 777 sbf_flash
./sbf_flash /path/to/sbf/file
Click to expand...
Click to collapse
Thanks for your advice, I managed to flash the sbf under ubuntu Now at least I know the way to do it 100%-proof

I did a "format system" in the CMW as I have recovered by this method?

brenopapito said:
I did a "format system" in the CMW as I have recovered by this method?
Click to expand...
Click to collapse
YES IT WORKS!
But I had to hold CAMERA + VOL UP before plugging in the usb.

Is there a way to restore to the factory default ROM, but still keep my SMS'es/Text messages?
I'm not sure if an MMS issue I'm having is related to the ROM I'm using (Argen2Stone) so want to put the official one back on, but keep all my recent SMS'es...(and preferably all installed apps, etc etc., but SMS'es most important).

cobo_ said:
Is there a way to restore to the factory default ROM, but still keep my SMS'es/Text messages?
I'm not sure if an MMS issue I'm having is related to the ROM I'm using (Argen2Stone) so want to put the official one back on, but keep all my recent SMS'es...(and preferably all installed apps, etc etc., but SMS'es most important).
Click to expand...
Click to collapse
you can back up your text messages using SMS Backup & Restore (available for free from the market place). save the backup file to your SD card, and once your ROM is restored, you can restore your messages using the restore button on that same program. (of course you need to reinstall SMS Backup & Restore in order to be able to restore the previously backed up file)

cobo_ said:
Is there a way to restore to the factory default ROM, but still keep my SMS'es/Text messages?
I'm not sure if an MMS issue I'm having is related to the ROM I'm using (Argen2Stone) so want to put the official one back on, but keep all my recent SMS'es...(and preferably all installed apps, etc etc., but SMS'es most important).
Click to expand...
Click to collapse
You could try to make a nandroid backup, flash another SBF and restore just data of the nandroid backup

cobo_ said:
Is there a way to restore to the factory default ROM, but still keep my SMS'es/Text messages?
I'm not sure if an MMS issue I'm having is related to the ROM I'm using (Argen2Stone) so want to put the official one back on, but keep all my recent SMS'es...(and preferably all installed apps, etc etc., but SMS'es most important).
Click to expand...
Click to collapse
or use titanium backup

Sbf flashes do not wipe /data. Therefore you could just sbf restore and all apps and text messages will be kept.

i used sbf_flash in opensuse. it detected my phone as droid x. everything was done. it said rebooting. but my phone didn't reboot. i only see a gray screen. what can i do now?

handsomeboy1702 said:
i used sbf_flash in opensuse. it detected my phone as droid x. everything was done. it said rebooting. but my phone didn't reboot. i only see a gray screen. what can i do now?
Click to expand...
Click to collapse
I use SBF_flash too on Ubuntu. Try pulling your battery and booting up. If it doesn't work, try booting up by holding VOL DOWN+CAM to get into bootloader mode and start over

Mikevhl said:
I use SBF_flash too on Ubuntu. Try pulling your battery and booting up. If it doesn't work, try booting up by holding VOL DOWN+CAM to get into bootloader mode and start over
Click to expand...
Click to collapse
i'd tried it again and again without success. then i finally managed to flash it using windows 7 with this little trick http://goo.gl/QeH5n

Thanks guys, I'll give 'em a try and see how it goes

Thanks to agent008my, DeadSix17, handsomeboy1702 and Mikevhl for the helpful suggestions and info
I ended up trying a restore from CWM (backed-up first!) of my very first backup prior to any ROMs etc and just restoring the system only.
This seems to have worked a treat! As I now have the stock ROM and all my apps/sms'es/phone logs etc still in place before I did the system-only restore!
Exactly what I wanted and so easy!
Many thanks guys and huge thanks to the CWM peoples as that thing is amazing.

Motorola Razr HD LTE XT925 4.1.2 boot loop

I'm stumped with this issue of my Motorola Razr HD LTE XT925 Rogers version 4.1.2 being in a boot loop. It started when I did a factory reset to try and fix some camera issues that I was having it started up with the Motorola red M icon then went to proceed with the factory reset with the android icon with the spinning blue object then restarts and just does a loop I have tried some steps that I found that I will list but all are unsuccessful and I did try them several times. It is stock firmware but was rooted with one click rooting program can't remember the name I did nothing else to the firmware.
Power + volume down for 10 seconds (simulates a battery pull)
Stock recovery tried wiping data and cache and then rebooting
Tried to use the boot menu normal start up and factory options
I did however get it to boot to the Rogers logo screen once but it just froze and had to restart it
I am currently trying get ADB tool to installed and get it working to see my phone as well as RDS Lite 6.1.6 it wont show any info about the phone but when in fastboot mode RDS Lite see it as connected in fastboot but no info about the phone shows up in the top left box as it has shown before also tried Super ADB Tool it show nothing at all I will continue to try and get the tools working.
Any help in getting the phone to boot normally is greatly appreciated.

I was also wondering if any body knows a good way to completely wipe the razr XT925 and restore the stock firmware that would also help.

OK so I have ADB installed and working I think put my XT925 in fast boot mode then I put in code adb devices in to the windows command console but show nothing listed and my phone says it is in fastboot mode and usb is connected and windows sees it as well but not ADB. There is no errors ether I am so confused as to why ADB and RSD show no info about my phone? I will see if its any of my drivers that are missing.
I went ahead and tried to flash my phone with RSD lite 6.1.6 with no luck the boot loop is preventing it from proceeding with the flash is this just a lost cause and there is no fix for it. The only thing I can think of is that I have to unlock the boot loader is that even an option when I can't even get boot into android? Any one got any ideas?

I was messing a round with my phone and try to get it working with any of the tools and had turned of the phone to stop it from constantly showing the red M icon and the android icon with the blue spinning object over and over but still had the phone plugged in to the computer and was looking in device manger in windows and seen this QHUSB_DLOAD with no drivers for it and looked at the VID & PID ids (USB\VID_05C6&PID_9008
) and searched for drivers thinking that is what is missing for my phone as I have never see it before and it is Qualcomm modem flashing port I don't know what to do did really mess up my phone by just doing a factory restore?
Some help or clarification would help a lot now as it is a bit troubling that I am unable to fix the Motorola Razr XT925 and might be bricked just by doing a factory restore. :silly:

OK I am getting desperate here I will do anything to stop it from looping I have even tried house of motos way just the same thing still if I can stop it from looping I can get it to work but does anyone knows a way to wipe the phone completely or stop it from this infuriating loop???
Just as a side note I found that forcing it in to normal start up with the wall charger plugged in it will charge when done then it will show the rogers logo like its booting but does nothing.

I have searched the forms and google now for 2 days about any way to fix the boot loop but all just say to do things that I have tried many different ways many times and the tools don't work or will work like RDS but it is unable to continue do to the loop of it doing a factory restore then restarts.
If any body has any ideas at all or can at least point me in the right direction would be a life saver I will even jtag the phone if i have to, if even that's possible

Have you booted into fastboot mode?
Have tried to rsd to stock from fastboot?

Darbness said:
Have you booted into fastboot mode?
Have tried to rsd to stock from fastboot?
Click to expand...
Click to collapse
Thanks for the reply, I have gone into fastboot mode and used RSD to try and flash the stock rom but when it restarts the phone its unable to countiue becuse it is uable to get past the bootloop

If your phone is bootloader locked you can always take it back to the carrier, that's it if you have guarantee. I suggest you try a earlier version of RSD lite, 6.1.4 for example, and see how it goes.
Sent from my RAZR HD using xda app-developers app

Hydr0id said:
If your phone is bootloader locked you can always take it back to the carrier, that's it if you have guarantee. I suggest you try a earlier version of RSD lite, 6.1.4 for example, and see how it goes.
Sent from my RAZR HD using xda app-developers app
Click to expand...
Click to collapse
OK, not able to take it to Rogers some issues with doing that but will try RSD lite 6.1.4 besides that no other ways?

I had the same issue yesterday. Received a phone call and my phone shut off and started looping on the red M logo, but no further. I did everything in my power to get RSD Lite and ADB to recognize my phone in fastboot mode. Nothing. Then, I moved the USB port to another port on my laptop, and viola, RSD Lite picked it up, but ADB never did. Using the stock firmware available for my 926, I was able to revert back to the latest version of JB for my phone. I did also have to run RSD Lite in *administrator mode* in order to get success. Hope any of these tips helps you out.
Also, even though I was successful in flashing, I was still in loop mode until... I had to wait for the battery to die and the phone to shut all the way off. Then after powering up, it came up. I tried the volume down + power key, but it would only reset the phone, it would not completely power it off like it needed. This is not something I have seen on any forum anywhere, so hopefully it helps.

xaneth said:
I had the same issue yesterday. Received a phone call and my phone shut off and started looping on the red M logo, but no further. I did everything in my power to get RSD Lite and ADB to recognize my phone in fastboot mode. Nothing. Then, I moved the USB port to another port on my laptop, and viola, RSD Lite picked it up, but ADB never did. Using the stock firmware available for my 926, I was able to revert back to the latest version of JB for my phone. I did also have to run RSD Lite in *administrator mode* in order to get success. Hope any of these tips helps you out.
Also, even though I was successful in flashing, I was still in loop mode until... I had to wait for the battery to die and the phone to shut all the way off. Then after powering up, it came up. I tried the volume down + power key, but it would only reset the phone, it would not completely power it off like it needed. This is not something I have seen on any forum anywhere, so hopefully it helps.
Click to expand...
Click to collapse
Thanks for the reply, I was thinking along the same lines as that but trying it on a freshly installed windows plus on different computer and just have RSD lite 6.0 and my Motorola drivers for my phone installed. I was thinking that it was my current motherboard that has a Intel usb 3.0 controller on it and my old motherboard did not as I manually updated my phone from 4.0.4 to 4.1.2 before on my old motherboard and had no issues and will fallow the instructions to the letter and will triple check as well. I will see how this goes and hope it works as its my last option to get it working.

OK so trying to reflash the phone from a different computer with a fresh install of windows buy did not work.
I was looking though the options in the android system recovery menu and two options stood out are:
apply update from external storage
and
apply update from ADB (wont work as ADB does not see the phone)
would doing an update with an SD card with the firmware on it work or is it for some other purpose?

osalot said:
OK so trying to reflash the phone from a different computer with a fresh install of windows buy did not work.
I was looking though the options in the android system recovery menu and two options stood out are:
apply update from external storage
and
apply update from ADB (wont work as ADB does not see the phone)
would doing an update with an SD card with the firmware on it work or is it for some other purpose?
Click to expand...
Click to collapse
I'm not sure, never flashed that way. If it isn't too much to ask, can you tell me the process you are following to flash the stock rom step by step?, to see if I can somehow help you out, it's really odd It doesn't work.
Sent from my RAZR HD using Tapatalk

Hydr0id said:
I'm not sure, never flashed that way. If it isn't too much to ask, can you tell me the process you are following to flash the stock rom step by step?, to see if I can somehow help you out, it's really odd It doesn't work.
Sent from my RAZR HD using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply, The steps I take to flash my phone is to first put my phone in to fast boot mode then connect my phone to the back of my pc then start up RSD Lite and add the latest firmware for my XT925 in RSD then let it load the firmware and it restarts the phone. it starts up to the non animated red M icon then the android with the spinning blue object in its chest comes up but then shuts off and restarts and have left it for several hours until it died and had to recharge it up.If I can I will post a video of how I flash it and what the phone does.
also is it normal for RSD Lite not to show the imei number of the phone or any thing about it in the top left box (Device properties) when you click on the modal?, all I get is N/A in Device properties box.

Yes, that is completely normal, that only appears when the flash is succesful and you get past the "select language" screen, but seeing that you're stuck in the M logo means that you haven't got there yet, in the mean time it will still appear no imei and no info.
Sent from my RAZR HD using xda app-developers app
---------- Post added at 04:08 PM ---------- Previous post was at 04:01 PM ----------
Here, try this: http://www.android.gs/unroot-droid-razr-hd-xt926-downgrade-stock-firmware/
The RSD process following the exact same instructions found there on a Windows with USB 2.0, and it is preferred you use RSD 6.1.4 (if you don't have it I can post it here if you want)
Your build to flash is found here: http://sbf.droid-developers.org/
Search for the one the phone brought when it was just bought, it has to be from your carrier.
Btw: did the flashing gives you any errors at all or not? Also, do you have bootloader unlocked? Just some details I'm curious, but seeing your phone does finish the process and restarts means it probably doesn't get any errors, anyway I'm just curious.
Sent from my RAZR HD using xda app-developers app

Hydr0id said:
Yes, that is completely normal, that only appears when the flash is succesful and you get past the "select language" screen, but seeing that you're stuck in the M logo means that you haven't got there yet, in the mean time it will still appear no imei and no info.
Sent from my RAZR HD using xda app-developers app
---------- Post added at 04:08 PM ---------- Previous post was at 04:01 PM ----------
Here, try this: http://www.android.gs/unroot-droid-razr-hd-xt926-downgrade-stock-firmware/
The RSD process following the exact same instructions found there on a Windows with USB 2.0, and it is preferred you use RSD 6.1.4 (if you don't have it I can post it here if you want)
Your build to flash is found here: http://sbf.droid-developers.org/
Search for the one the phone brought when it was just bought, it has to be from your carrier.
Btw: did the flashing gives you any errors at all or not? Also, do you have bootloader unlocked? Just some details I'm curious, but seeing your phone does finish the process and restarts means it probably doesn't get any errors, anyway I'm just curious.
Sent from my RAZR HD using xda app-developers app
Click to expand...
Click to collapse
thanks for the reply, I have just tried the the steps in the link you provided and I used RSD lite 6.1.4 and got the 4.0.4 Rogers firmware for my XT925 that it originally came with and waited an hour but just did the same thing, I don't get any errors when flashing although RSD displays to start the phone up manually and I have a locked boot loader (Device is LOCKED: Status Code: 0) I can how ever get it to go to the animated red M icon and then the rogers logo by selecting normal power up from the boot menu but doesn't boot in to android.

osalot said:
I was also wondering if any body knows a good way to completely wipe the razr XT925 and restore the stock firmware that would also help.
Click to expand...
Click to collapse
http://theunlockr.com/2012/01/24/how-to-restore-the-motorola-droid-razr-using-fastboot-files/

Ok, so I think I maybe doing something incorrectly so I will put all the steps I did to reflash my phone and will add some pics and a video if possible.It took me a few days to get another phone to use for vids and pics the phone I used to for video and pics Samsung Captivate, unbrickable ya can't kill it.
1. I have installed RSD Lite 6.1.4
2. Installed the latest Motorola drivers by down loading the Motorola Device Manager
3. Down loaded the firmware for my phone android 4.1.2 full file name ---> 9.8.2Q-8-XT925_VQL-12.2_CANADA_VANQJBLTEFRCI_P004_CFC_fb.xml.zip
4. Put my phone in fast boot mode then connected my phone to my netbook on the side or on the back usb 2.0 port on the PC with the original Motorola usb phone cable tried both to be sure
5. Started up RSD Lite 6.1.4 and load the firmware and selected Decompress only
6. Checked RSD Lite to make sure my phone is connected and showing up and RSD Lite shows (Fastboot VQUISH_U S USB N/A Connected)
7. I then selected start button on RSD Lite and it flashed the firmware with out issues or errors
8. phone restarts fine from fastboot left it for 1:30 RSD displays to reboot the phone manually but the phone does not do anything else but reboot constantly left the phone doing that until it ran out of battery
Pic of XT925 in fastboot mode not connected
Pic of RSD with phone connected in fastboot mode ready to be flashed
Video of phone restarting after being flashed and looping (click the link below)
http://s1295.photobucket.com/user/Osalot-Ruin/media/RSDandphonevideoCapture_zpsff85211b.mp4.html
Pic of RSD after leaving the phone for 1 hour and 30 minutes

In the steps I don't see the XML file editing, did you deleted the getvar line in the XML file?
Sent from my RAZR HD using XDA Free mobile app

[Q] HKC P776A Android tablet stuck in twrp/cwm bootloop

Ok I finally got this tablet rooted using some chinese oneclick root tool worked great do to it was the only kit that was able to root it and i installed supersu apk to replace to chinese version worked and i went to update supersu and hit the twrp (not knowing what it was at the tim stupid right i know lol) and now it is stuck in the twrp/cwm bootloop and i cant get into recovery mode when i try it says updating img blah blah and restarts back into the bootloop. It is running 4.1.1 JB and has a micro sd card slot.There is a pic in the atachment because i dont know how to upload it to this post but it is just a pic no "extras" are included no viruses maleware ect just a pic

parkourgamer said:
Ok I finally got this tablet rooted using some chinese oneclick root tool worked great do to it was the only kit that was able to root it and i installed supersu apk to replace to chinese version worked and i went to update supersu and hit the twrp (not knowing what it was at the tim stupid right i know lol) and now it is stuck in the twrp/cwm bootloop and i cant get into recovery mode when i try it says updating img blah blah and restarts back into the bootloop. It is running 4.1.1 JB and has a micro sd card slot.There is a pic in the atachment because i dont know how to upload it to this post but it is just a pic no "extras" are included no viruses maleware ect just a pic
Click to expand...
Click to collapse
Super old I know but my kids tablet is doing this now. Did you ever find a fix?

KilluminatiStyle said:
Super old I know but my kids tablet is doing this now. Did you ever find a fix?
Click to expand...
Click to collapse
Pro tip: Don't bumb old threads like this. You might not even have similar problems. Instead create a new thread regdaring your issue.
Now, post your tablet info HERE:
Root staus?
Can you boot in recovery? If yes what recovery do you have?
Tablet model
Android version
What happened
What have tried to fix it

janekmuric said:
Pro tip: Don't bumb old threads like this. You might not even have similar problems. Instead create a new thread regdaring your issue.
Now, post your tablet info HERE:
Root staus?
Can you boot in recovery? If yes what recovery do you have?
Tablet model
Android version
What happened
What have tried to fix it
Click to expand...
Click to collapse
Root Status = ROOTED
I cannot boot into recovery mode (but when i try i get this, look in pic 2&3)
Tablet Type = HKC (NOT HTC) p776a
ANDROID Version I think (98% shure) is 4.1.1 beta JB
What happened = A few years ago 2013 i think a got this tablet then i learned about rooting, roms, and such so i spent the next year or two trying to root the tablet. I finally got it rooted with a chinese root program and all was well (i don't remember the name of the program) then there was a update for su and i pressed the twrp/cwm mode on accident (I think I was talking to someone at the time) and now it does what is shown in the image 1 it is on some boot loop. When I try to access the hboot menu it does what is shown in these images 2&3. Also my tablet has a MicroSD card slot and the battery can not be taken out. the regular bootloop picture is image file 1 that is what it looks like when it does its continuous bootloop and P.S. the tablet turns off and on automatically during the bootloop. To try and fix it i have let it do its bootloop for hours on end turn it on and off tried looking for a compatible rom (to no avail) and let the battery completely die that is about it.

parkourgamer said:
Root Status = ROOTED
I cannot boot into recovery mode (but when i try i get this, look in pic 2&3)
Tablet Type = HKC (NOT HTC) p776a
ANDROID Version I think (98% shure) is 4.1.1 beta JB
What happened = A few years ago 2013 i think a got this tablet then i learned about rooting, roms, and such so i spent the next year or two trying to root the tablet. I finally got it rooted with a chinese root program and all was well (i don't remember the name of the program) then there was a update for su and i pressed the twrp/cwm mode on accident (I think I was talking to someone at the time) and now it does what is shown in the image 1 it is on some boot loop. When I try to access the hboot menu it does what is shown in these images 2&3. Also my tablet has a MicroSD card slot and the battery can not be taken out. the regular bootloop picture is image file 1 that is what it looks like when it does its continuous bootloop and P.S. the tablet turns off and on automatically during the bootloop. To try and fix it i have let it do its bootloop for hours on end turn it on and off tried looking for a compatible rom (to no avail) and let the battery completely die that is about it.
Click to expand...
Click to collapse
Okay. Just a few more questions.
Does your tablet boot into recovery (picture 1) even if you try to boot normally? (fastboot maybe)
Can you boot into anything else other than recovery? (try different button combinations)
Does ADB recognise your tablet when it's in recovery mode? (if you don't know about this, just post your computer OS and if you have ADB/Fastboot drivers installed on your PC)
If the anwser the the first question is no:
Does ADB recognise the device while it's in the bootloop.

janekmuric said:
Okay. Just a few more questions.
Does your tablet boot into recovery (picture 1) even if you try to boot normally? (fastboot maybe)
Can you boot into anything else other than recovery? (try different button combinations)
Does ADB recognise your tablet when it's in recovery mode? (if you don't know about this, just post your computer OS and if you have ADB/Fastboot drivers installed on your PC)
If the anwser the the first question is no:
Does ADB recognise the device while it's in the bootloop.
Click to expand...
Click to collapse
sorry, i forgot to clarify the hboot. it pops up the "words" or whatever then automatically reboots there is no way to select options or keep the device on so i cant use fastboot unless there is a way i dont know of. P.S. the tablet restarts automatically so it is on for like 25 maybe 30 seconds then shuts off then turns back on and repeats till the battery is dead. My thought originally to fix it was to get a rom put it on the sdcard and see if that works but the manufacture does not supply the rom for my model only the p771a. and the only physical buttons are the home, power, the pinhole reset button, the volume and such buttons are virtual on the screen when it is fully on. And picture 1 i dont fully know what that screen symbol is the hboot one is similar but not that but yes it does but to picture 1 nomadder what i do even if i try to get to hboot menu. Sorry if this is a "little" scattered having explaining it. If it would help i can make a video and rar it and upload it here.

parkourgamer said:
sorry, i forgot to clarify the hboot. it pops up the "words" or whatever then automatically reboots there is no way to select options or keep the device on so i cant use fastboot unless there is a way i dont know of. P.S. the tablet restarts automatically so it is on for like 25 maybe 30 seconds then shuts off then turns back on and repeats till the battery is dead. My thought originally to fix it was to get a rom put it on the sdcard and see if that works but the manufacture does not supply the rom for my model only the p771a. and the only physical buttons are the home, power, the pinhole reset button, the volume and such buttons are virtual on the screen when it is fully on. And picture 1 i dont fully know what that screen symbol is the hboot one is similar but not that but yes it does but to picture 1 nomadder what i do even if i try to get to hboot menu. Sorry if this is a "little" scattered having explaining it. If it would help i can make a video and rar it and upload it here.
Click to expand...
Click to collapse
here is the video

parkourgamer said:
sorry, i forgot to clarify the hboot. it pops up the "words" or whatever then automatically reboots there is no way to select options or keep the device on so i cant use fastboot unless there is a way i dont know of. P.S. the tablet restarts automatically so it is on for like 25 maybe 30 seconds then shuts off then turns back on and repeats till the battery is dead. My thought originally to fix it was to get a rom put it on the sdcard and see if that works but the manufacture does not supply the rom for my model only the p771a. and the only physical buttons are the home, power, the pinhole reset button, the volume and such buttons are virtual on the screen when it is fully on. And picture 1 i dont fully know what that screen symbol is the hboot one is similar but not that but yes it does but to picture 1 nomadder what i do even if i try to get to hboot menu. Sorry if this is a "little" scattered having explaining it. If it would help i can make a video and rar it and upload it here.
Click to expand...
Click to collapse
1. Download fixcache.bat.zip on your computer. Extract cachefix.bat from the file.
2. Run it. It should say just "Waiting for device..."
3. Now reset your tablet with the reset button and QUICKLY plug it into the computer and wait a few minutes.
Now try to get to that text in picture 1 and tell me what happends.
Also post the text you see on the computer from the file I sent you.
Tell me if

janekmuric said:
1. Download fixcache.bat.zip on your computer. Extract cachefix.bat from the file.
2. Run it. It should say just "Waiting for device..."
3. Now reset your tablet with the reset button and QUICKLY plug it into the computer and wait a few minutes.
Now try to get to that text in picture 1 and tell me what happends.
Also post the text you see on the computer from the file I sent you.
Tell me if
Click to expand...
Click to collapse
this is what happens to the .bat fikle when i open it

parkourgamer said:
this is what happens to the .bat fikle when i open it
Click to expand...
Click to collapse
also would there be any way to pop the hood and flip a switch to reset it like on a pc tower?

parkourgamer said:
also would there be any way to pop the hood and flip a switch to reset it like on a pc tower?
Click to expand...
Click to collapse
Umm, you said there is a reset button on the tablet so pressing that would probably reset it.
The error you are getting is because adb is not installed on your PC. Use this simple adb installer to instal adb. When installing just press yes to everything. MAKE SURE THE PHONE IS PLUGGED IN THE COMPUTER WHILE INSTALLING AND THAT IT'S ON!
Now run the file again.
If you want you can add me on Skype: janekmuric
---------- Post added at 13:51 ---------- Previous post was at 13:26 ----------
If you want to know what is happening:
You are in what's called a recovery bootloop. It's when you can't get out of the recovery. What is happening in this case is that Superuser app tried to install it's binaries via recovery. Because some people don't know how to install binaries manually, the app puts a file on the cache partition so the recovery automaticly installs the zip upon booting. Now, this would be good so you don't mess up your device, but the zip file it's trying to install is faulty so it just breaks the device.
My attept at fixing this is to delete the /cache/recovery folder so it doesn't just install the file, and instead boots into a working recovery.

janekmuric said:
Umm, you said there is a reset button on the tablet so pressing that would probably reset it.
The error you are getting is because adb is not installed on your PC. Use this simple adb installer to instal adb. When installing just press yes to everything. MAKE SURE THE PHONE IS PLUGGED IN THE COMPUTER WHILE INSTALLING AND THAT IT'S ON!
Now run the file again.
If you want you can add me on Skype: janekmuric
---------- Post added at 13:51 ---------- Previous post was at 13:26 ----------
If you want to know what is happening:
You are in what's called a recovery bootloop. It's when you can't get out of the recovery. What is happening in this case is that Superuser app tried to install it's binaries via recovery. Because some people don't know how to install binaries manually, the app puts a file on the cache partition so the recovery automaticly installs the zip upon booting. Now, this would be good so you don't mess up your device, but the zip file it's trying to install is faulty so it just breaks the device.
My attept at fixing this is to delete the /cache/recovery folder so it doesn't just install the file, and instead boots into a working recovery.
Click to expand...
Click to collapse
That would be great but i cant keep my tablet on for more than like 30 seconds before it auto shuts off and it automatically tries to go into recovery when i add power to the device it wont just boot to the OS

parkourgamer said:
That would be great but i cant keep my tablet on for more than like 30 seconds before it auto shuts off and it automatically tries to go into recovery when i add power to the device it wont just boot to the OS
Click to expand...
Click to collapse
30 seconds is more than enough. Especally with an automated script like the one I sent you.
The first thing we have to do to fix your tablet is to establish a working ADB connection. Use the ADB installer i sent you. And look up on how to install Google USB driver for ADB.

janekmuric said:
30 seconds is more than enough. Especally with an automated script like the one I sent you.
The first thing we have to do to fix your tablet is to establish a working ADB connection. Use the ADB installer i sent you. And look up on how to install Google USB driver for ADB.
Click to expand...
Click to collapse
ok will try

Bricked when returning to stock (No command)

Hey guys,
decided to flash the latest DBT Firmware via Odin to get back to stock completely. (G930FXXU3ESA3)
After flashing the firmware through Odin the phone reboots and then installs an update and erases data (blue background).
After a second reboot I end up with a blue screen and the simple error: "No command".
I can not get into recovery, as I end up with the same error message wether booting into recovery or the system.
I CAN however get into downloadmode and flash twrp, after that I can boot into system but I want to keep the whole system vanilla, without TWRP.
Installing TWRP keeps the device encrypted, no matter what. I can wipe, then install no-verity-encrypt and as soon as I reboot the device is encrypted again.
Ive tried: Different Firmware Version (December 2018), 3 different cables, different odin versions.
Edit: attached an Image of the message that Pops up after about 30sec on the no command screen.

Ok, so your device will take UK Unbranded BTU firmware. You can get it from a few sources and even direct from Samsung servers with Samtool.
Forget all that flashing TWRP and non verify nonsense, if you can get into download mode you can flash firmware, obviously make sure the firmware downloaded is not corrupt etc.
I've used Odin V10 -13 to flash BTU and every version flashed it correctly. Sometimes you do get that "installing update" and then "erasing" but that's fine just leave the phone for a few minutes it should eventually reboot normally.

FLASH No verity.zip
VIA TWRP
https://forum.xda-developers.com/attachment.php?attachmentid=4490455&d=1525176288

cooltt said:
Ok, so your device will take UK Unbranded BTU firmware. You can get it from a few sources and even direct from Samsung servers with Samtool.
Forget all that flashing TWRP and non verify nonsense, if you can get into download mode you can flash firmware, obviously make sure the firmware downloaded is not corrupt etc.
I've used Odin V10 -13 to flash BTU and every version flashed it correctly. Sometimes you do get that "installing update" and then "erasing" but that's fine just leave the phone for a few minutes it should eventually reboot normally.
Click to expand...
Click to collapse
Just tried the latest BTU with Odin 3.13.1, same problem. Its reboots into the blue screen, applying system update to about 32% and then switches to "Erasing". After about 1min it reboots, shows "Installing System update" for a second and I end up with "No command" again. And from there on it just constantly reboots into the "No command" screen.
This seems like the same problem. I can not enter stock recovery to wipe though...
Things ive tried so far:
- Different firmware Versions (all oreo since downgrading is impossible)
- Formating with pit files
- Different Odin Versions
- Unplugging and replugging the battery
- Installing TWRP, wiping data and then installing stock recovery through TWRP

Did u try in Odin nand erase and repatition option? If not try it ( make sure u have pit file extracted or downloaded from the net)

Scorpionea said:
Did u try in Odin nand erase and repatition option? If not try it ( make sure u have pit file extracted or downloaded from the net)
Click to expand...
Click to collapse
Did a efs backup through TWRP just in case, then flashed the latest DBT firmware with nand erase -> still the same problem.
I can only guess that this was caused by using a backup from another phone back when Oreo came out, this probably messed something up really badly. Very weird, im kinda lost.

Killuminati91 said:
Just tried the latest BTU with Odin 3.13.1, same problem. Its reboots into the blue screen, applying system update to about 32% and then switches to "Erasing". After about 1min it reboots, shows "Installing System update" for a second and I end up with "No command" again. And from there on it just constantly reboots into the "No command" screen.
This seems like the same problem. I can not enter stock recovery to wipe though...
Things ive tried so far:
- Different firmware Versions (all oreo since downgrading is impossible)
- Formating with pit files
- Different Odin Versions
- Unplugging and replugging the battery
- Installing TWRP, wiping data and then installing stock recovery through TWRP
Click to expand...
Click to collapse
Ok, from the no command screen do the following.
Hold power until phone switches off, then press power+home+volume up. The phone should now boot into original recovery screen. Select "wipe/factory reset" and then reboot device. Job done.

cooltt said:
Ok, from the no command screen do the following.
Hold power until phone switches off, then press power+home+volume up. The phone should now boot into original recovery screen. Select "wipe/factory reset" and then reboot device. Job done.
Click to expand...
Click to collapse
Tried that, recovery is simply not working. If I hold vol - + power + home to restart and switch immediatly to vol + I boot into the usual blue screen with No command. I even tried unplugging the battery to shut off the phone and boot into recovery from there but that is not working either. Sorry should have stated that more clearly.
If I flash TWRP however, I can easily boot into TWRP with the recovery button combo.

Killuminati91 said:
Tried that, recovery is simply not working. If I hold vol - + power + home to restart and switch immediatly to vol + I boot into the usual blue screen with No command. I even tried unplugging the battery to shut off the phone and boot into recovery from there but that is not working either. Sorry should have stated that more clearly.
If I flash TWRP however, I can easily boot into TWRP with the recovery button combo.
Click to expand...
Click to collapse
Ok it's a tricky one so one more thing I would suggest is download and install Samsung smart switch on your PC, place the phone in download mode plug it into lap top and choose emergency software recovery in smart switch
Edit. I just remembered before that try this button combo from the no command screen volume up+volume down+power.

cooltt said:
Ok it's a tricky one so one more thing I would suggest is download and install Samsung smart switch on your PC, place the phone in download mode plug it into lap top and choose emergency software recovery in smart switch
Edit. I just remembered before that try this button combo from the no command screen volume up+volume down+power.
Click to expand...
Click to collapse
Hmmh. Searched a lot for the version that still supported emergency recovery. (which seems to be 4.0). If I go into download mode, start smartswitch and try to use emergency recovery there is nothing for me to select.
Volume up + down and power gives me the terminal like look which I attached in the first post with all those error messages.

Killuminati91 said:
Hmmh. Searched a lot for the version that still supported emergency recovery. (which seems to be 4.0). If I go into download mode, start smartswitch and try to use emergency recovery there is nothing for me to select.
Volume up + down and power gives me the terminal like look which I attached in the first post with all those error messages.
Click to expand...
Click to collapse
The EFS partition is corrupt or blank, it's the only logical explanation but the TWRP back up should solve that, without looking at it my self and running some commands i cant help your further.

cooltt said:
The EFS partition is corrupt or blank, it's the only logical explanation but the TWRP back up should solve that, without looking at it my self and running some commands i cant help your further.
Click to expand...
Click to collapse
TWRP backup was created after I ran into problems though. Ive checked some more things and it seems like the serial number that is displayed (in combination rom and or Z3X) is not the same SN that is printed on the back of the phone. Could this be related? And how would I go about changing it back to the one on the sticker? The IMEI is correct.
Had someone who was more into the whole thing contact me here but when I wanted to "donate" only half of what he was asking he refused to help me.

Killuminati91 said:
TWRP backup was created after I ran into problems though. Ive checked some more things and it seems like the serial number that is displayed (in combination rom and or Z3X) is not the same SN that is printed on the back of the phone. Could this be related? And how would I go about changing it back to the one on the sticker? The IMEI is correct.
Had someone who was more into the whole thing contact me here but when I wanted to "donate" only half of what he was asking he refused to help me.
Click to expand...
Click to collapse
Thats because he's a scammer. Never donate to get your phone fixed! Donate to Rom developers and things you like but never to get the phone fixed, they're usually lying.
The serial number should be the same ON the phone as displayed IN phone. Tell me the story about the phone, how did you get it? what region? where are you? what firmware was installed? Can you still flash a ROM with TWRP? Can you check OEM unlock?
---------- Post added at 04:53 PM ---------- Previous post was at 04:51 PM ----------
nmnmnmnmnmnmnmnmnm

Pretty sure he was just trying to remote repair for a price, which is not allowed on XDA. Would obviously donated on my own if he actually fixed it.
Bought the phone unlocked directly from a provider (simply - germany - dbt - g930f) back in 2016. Tripped kn0x after a few months, installed a few custom roms until Oreo came out.
This is where I messed up I think: I used a TWRP backup from someone else that he had shared here on XDA, which probably included his /efs too.
Since then I had constant connection problems, weak internet connection, dropped calls and so on.
Broke my screen and then decided to repair it myself. Bought a new frame, screen, battery, usb-port, earpiece and vibrator - managed to assemble all of that.
I can install all latest official firmwares (bootloader 3) through Odin. If I leave it at that I have no recovery and end up with the initially shown screen and "No command".
If i install TWRP from there and simply root with magisk or apply dm-verity-fix I can boot into the stock firmware with everything working.
I can also install ROMs. Just going completely vanilla is not possible anymore. OEM Unlock is checked, USB debugging works.
Edit: What is also astounding: If I flash version DBT-G930FXXS3ERHD-20180918145033 (oldest possible Oreo Version) I can enter recovery and do a factory reset and wipe cache.
If I do that however I am stuck at the Galaxy S7 Logo, not even bootlooping.

Killuminati91 said:
This is where I messed up I think: I used a TWRP backup from someone else that he had shared here on XDA, which probably included his /efs too.
Click to expand...
Click to collapse
awww.....come on man you should have said this at the start! Of course you can't use someone else's EFS data, it's unique to your handset. Custom Rom's patch some but not all EFS data that's why they work and in your case that's why Stock firmware isn't going too.
Anyway if this is the problem (and i suspect it is) there is only one way to fix it with Octopus box which can write all the important info back onto the EFS. Your IMEI, Serial, Mac address etc. Odin reads the info from the EFS prior to nand write start, if the phone serials don't match it will always fail at some point.
You can install a custom via twrp but it will not work correctly due to EFS data miss match. Octopus box is your answer.

cooltt said:
awww.....come on man you should have said this at the start! Of course you can't use someone else's EFS data, it's unique to your handset. Custom Rom's patch some but not all EFS data that's why they work and in your case that's why Stock firmware isn't going too.
Anyway if this is the problem (and i suspect it is) there is only one way to fix it with Octopus box which can write all the important info back onto the EFS. Your IMEI, Serial, Mac address etc. Odin reads the info from the EFS prior to nand write start, if the phone serials don't match it will always fail at some point.
You can install a custom via twrp but it will not work correctly due to EFS data miss match. Octopus box is your answer.
Click to expand...
Click to collapse
Dang it. Thank you! Off to find someone who can do this via remote access or in Berlin.

Same situation right now with my S7. Damn.

Hi everyone. Did you guys find any way to resolve this issue? i have exactly the same issue here.. but in my case i cannot use twrp cuz i never installed it before... the issue happened right after i tried to enter the recovery mode by pressing the buttons...
my wife's galaxy s7 touch screen was acting weird and i tried to get into the recovey mode..which is pretty muh easy to do... but once i tried the no command msg came up and now i have exatly the same case as the guy that opened this thread....also done everything hes done....any clue about this anyone?
id appreciate some help..
thanks in advance
Diego Boffa

Anyone?

I have exactly the same error with "fail to open recovery_cause(No such file or directory)#
My Tablet is now stuck with a blue "android dead" screen saying "No command".
My history to disaster:
- i've recovered a "broken" Samsung Tablet (sm-T585) with corrupted file system via
* Download Mode works -> TWRP install -> Mount option -> use ADB to recreate EFS partition -> re-flash stock image (android 8) with odin
- device works fine
- then i've noticed it can only be used with a certain cell provider (o2)
- then i've tried to flash an older version of the stock rom (android 7) due some problems in Android 8 (often some slow downs while operating)
- this doesn't work, the flash don't start
- therefore nothing should be happend, or?
- then i've can't get anymore in the stock recovery to wipe all data
...therefore the mess began:
* i can't flash TWRP anymore
* i can't flash stock recovery anymore
* i only can get into download mode
* i can only flash a certain rom type successfully (green PASS within odin), but with the final stuck with boot loop, with the mentioned blue screen
* other rom version can't flashed
I hopefully ask you guys here, if anyone can help me?
Any help would be very appreciated ...