Database Info

[SOLVED/Tutorial]No boot/Recovery mode only fastboot situation!

I'm stuck at the very first image that appears on Orange Boston and i can't boot normally and i can't enter recovery mode either :|.
I flashed Cyanogen mod 6.1.0 RC4 this morning.Everything went well till i installed Adobe Flash Player 10.1.I rebooted my phone i realised that my wireless couldn't find my wi-fi network that was right next to the phone .The phone was laggier to.Then i turned it off.And wen i turned it back it would be stuck.And even the recovery mode is stuck before it even starts up (.
With my luck in life i doubt they would believe me with a lame excuse at Orange.If any of you know a good way to start at least the recovery mode so i can back-up my previous rom them please help.I'm very Desperate i tried a lot of things.

B42iso said:
I'm stuck at the very first image that appears on Orange Boston and i can't boot normally and i can't enter recovery mode either :|.
I flashed Cyanogen mod 6.1.0 RC4 this morning.Everything went well till i installed Adobe Flash Player 10.1.I rebooted my phone i realised that my wireless couldn't find my wi-fi network that was right next to the phone .The phone was laggier to.Then i turned it off.And wen i turned it back it would be stuck.And even the recovery mode is stuck before it even starts up (.
With my luck in life i doubt they would believe me with a lame excuse at Orange.If any of you know a good way to start at least the recovery mode so i can back-up my previous rom them please help.I'm very Desperate i tried a lot of things.
Click to expand...
Click to collapse
what kind of phone and recovery image do you have? I'll try to help, but just out of curiosity, did you post this in YOUR phone's forum Q&A section?

It's Gigabyte Codfish and it's named Orange Boston.It has alot of names around the world like 20 or 30 :|.The Recovery image is the latest Clockworkmod Recovery since i had to use it for Cyanogen.
Sadly my Phones not listed anywhere in the forum.
The thing is everything started to lag and my wi-fi started malfunctioning after I installed Adobe Flash Player 10.1 and after 1 Reboot and 1 power-off then turn-ons it stopped.
My phone has 2 boot images.The first one's with orange sqares and the second one is the Orange Logo/Cyanogenmod Logo depending on what i flashed,but it stops at the first one with the orange squares.
This happens at the Recovery mode to.If i could at least start the recovery mod i would re-flash my old os and then fix the rest of the problems.

B42iso said:
It's Gigabyte Codfish and it's named Orange Boston.It has alot of names around the world like 20 or 30 :|.The Recovery image is the latest Clockworkmod Recovery since i had to use it for Cyanogen.
Sadly my Phones not listed anywhere in the forum.
The thing is everything started to lag and my wi-fi started malfunctioning after I installed Adobe Flash Player 10.1 and after 1 Reboot and 1 power-off then turn-ons it stopped.
My phone has 2 boot images.The first one's with orange sqares and the second one is the Orange Logo/Cyanogenmod Logo depending on what i flashed,but it stops at the first one with the orange squares.
This happens at the Recovery mode to.If i could at least start the recovery mod i would re-flash my old os and then fix the rest of the problems.
Click to expand...
Click to collapse
ok, so firstly (and don't be offended) you should never ever ever flash a rom that isn't supported in a forum for your phone! second, try holding volume down and power and see if you get the bootloader/fastboot and pm me/reply here again. third, why did you flash rc4 (not yet "stable") and WHAT PHONE IS IT FOR?

Nothing happens and it says nothing at startup so Volume down + power isn't the right one for mine.I know the recovery mode (camera button+volume up+power) and something i'm not sure what it is but it says exit ftm mode (camera buton+volume down+power).
Well i used rom manager and it's for my phone the Z71 phone models that includes mine too.exit FTM mode does the same thing it shows the same image at the start and only writes a little text at the top left saying "exit FTM mode".
I'm not offended I'm really angry at myself so np.And RC4 is way more stable then RC1 cause RC1 drained my battery very fast.Adobe FLash player 10.1 has to be the culprit.My phone started to act strange only after i installed it.Before it worked like a miracle with RC4.Maybe another method would be to reset the apps in the internal memory but i guess that requieres recovery mode too...

I got it!The fastboot mode for me is Volume down+End Call+Power.
It's showing the same image at the beggining BUT the usb is recognised .This means with some Command Prompt magic we might be able to restore the previous Clockwork mod recovery cause the original does not have any special options and i can't really use my backup.
It's night time here I'll await your reply,I'll be here after school.This could help alot of people cause i heard about this kind of problem before but no explanation was given on how to solve it.

B42iso said:
I got it!The fastboot mode for me is Volume down+End Call+Power.
It's showing the same image at the beggining BUT the usb is recognised .This means with some Command Prompt magic we might be able to restore the previous Clockwork mod recovery cause the original does not have any special options and i can't really use my backup.
It's night time here I'll await your reply,I'll be here after school.This could help alot of people cause i heard about this kind of problem before but no explanation was given on how to solve it.
Click to expand...
Click to collapse
well, that's good. just to clarify, you have gained access to fastboot right?
also, you never answered what phone the rc4 you flashed was for, so, what phone was it for?
here is a link to adb (command prompt) - which is again for cdma hero's, so the guide may be off a little, but see if it helps... http://forum.xda-developers.com/showthread.php?t=690362

I said it's for Z71 phone types.It's a group of .... how do i say....no name phones or not so famous phones that includes mine to.Rom Manager automatically downloads the right version for my phone.I already looked up what's "Z71 phones" on the cyanogen forums. I'm not sure if fastboot works properly i've never seen it before on this phone,but the usb cable is recognised and that means it has to work.I'll look at the guide now...

I plugged in the device in to a fresh laptop withouth drivers.It said "Android Sooner Single ADB Interface".On my pc it's recognised cause i had the software tools programe installed when i made the official update and it installed the drivers by itself.
I'm still trying to get adb list my device cause it's not appearing .Probably wrong drivers?
Edit: Beside this tutorial you gave me looks like one that works with a normal working phone.There's a part that asks fo USB Debugging enabled.It was enabled before it crashed and never started again but i doubt it counts now.
Edit: Never mind i'm stupid it's right under the first post .
God my phone scared the crap out of me :|.After playing with fastboot and trying to get is listed in adb devices,which is stupid cause i had to type fastboot devices instead.I plugged it out for a little time it turned off and id didn't show a thing after i plugged it back now it's frozen with a dark orange low battery icon.It's probably dead low.I'll wait for it.Ps: I've never seen that battery icon :| so i pray it's not another nuisance problem to deal with.
Edit:Now that i think of it.... it was around 35% battery and after the incident i used it un-plugged to trying to get something started.
Here's the real guide by the same guy for fastboot: http://forum.xda-developers.com/showthread.php?t=532719.

YEEEEYYYY!!!!
Rejoice Brothers and Sisters.Thx to GOD, il Duce's support with help and for giving me strenght to not be depressed i made it .
Ok so I entered Fastboot mode and started command prompt.Connected my device to my pc and i showed command prompt the directory of adb for me it was
"B:\android-sdk-windows\tools" i copied from my sd card my nandroid backup files for my old ROM and i put them inside the tools folder.Then i did the following in Command Prompt:
these should take some time and you have to do them 1 by 1
fastboot erase boot
fastboot erase recovery
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash userdata data.img
fastboot flash recovery recovery.img
fastboot reboot
After reboot don't be scared like i was :| it's only stuck for a litle time because it's the first start up after the flash. That's all ^^.
Credits: il Duce,brandenk,nephron and Me for broking,experimenting and fixing my phone.

B42iso said:
Rejoice Brothers and Sisters.Thx to GOD, il Duce's support with help and for giving me strenght to not be depressed i made it .
Ok so I entered Fastboot mode and started command prompt.Connected my device to my pc and i showed command prompt the directory of adb for me it was
"B:\android-sdk-windows\tools" i copied from my sd card my nandroid backup files for my old ROM and i put them inside the tools folder.Then i did the following in Command Prompt:
these should take some time and you have to do them 1 by 1
fastboot erase boot
fastboot erase recovery
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash userdata data.img
fastboot flash recovery recovery.img
fastboot reboot
After reboot don't be scared liek i was :| it's only stuck for a litle time because it's the first start up after the flash. That's all ^^.
Credits: il Duce,brandenk,nephron and Me for broking,experimenting and fixing my phone.
Click to expand...
Click to collapse
COOL glad you got it working! I don't really know how I helped, sounds like you did most of the work, but glad I could help

Warning! You were right that ****ing ROM is 1 of the culprits ^^.I couldn't help myself but to try it withouth Adobe Flash player.It lasts as long as you don't power-off and then trun your phone back on.
So this is confirmed.I'm too lazy to report this to Cyanogen u.u... or should I?

Well i succesfully restored my phone again.SO guys with Z71 phones out there don't use Cyanogen 6 RC4 YET,cuase you amy end up like me .
I reported this to Cyanogen.Btw I would laugh hard if this became a famous tutorial lol.

Hi I tried using the method to upgrade my motorola greco xt502 (z71, boston orange clone) to CyanogenMod 6 V6.1.0-RC4 for z71 and now cant even boot into clockworksmod recovery. it says entering recovery with motorola icon and stuck there.Please Help .

nand backup please
B42iso said:
Rejoice Brothers and Sisters.Thx to GOD, il Duce's support with help and for giving me strenght to not be depressed i made it .
Ok so I entered Fastboot mode and started command prompt.Connected my device to my pc and i showed command prompt the directory of adb for me it was
"B:\android-sdk-windows\tools" i copied from my sd card my nandroid backup files for my old ROM and i put them inside the tools folder.Then i did the following in Command Prompt:
these should take some time and you have to do them 1 by 1
fastboot erase boot
fastboot erase recovery
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash userdata data.img
fastboot flash recovery recovery.img
fastboot reboot
After reboot don't be scared like i was :| it's only stuck for a litle time because it's the first start up after the flash. That's all ^^.
Credits: il Duce,brandenk,nephron and Me for broking,experimenting and fixing my phone.
Click to expand...
Click to collapse
happy for you, i have the same problem but i have no nand backup, i'm a noob, can you please upload a nand backup on mediafire or something like that?

saybron said:
happy for you, i have the same problem but i have no nand backup, i'm a noob, can you please upload a nand backup on mediafire or something like that?
Click to expand...
Click to collapse
Sorry man... this was ages ago, i don't have the files anymore, if I do have them then it's on my old desktop that's in another town and I won't be going there soon, cause i have university here.

thanks
B42iso said:
Sorry man... this was ages ago, i don't have the files anymore, if I do have them then it's on my old desktop that's in another town and I won't be going there soon, cause i have university here.
Click to expand...
Click to collapse
No problem, thanks man!

Samsung I9103 Galaxy R Repair Dead By USB Cable no need JTAG NO Need Disassembly Phon

Samsung I9103 Galaxy R Repair Dead By USB Cable no need JTAG NO Need Disassembly Phon
Download Links:X0X0X
Password:forum.sptbox.net
how to enter APX mode:
hold "vol up"+"home" then connect usb cable to dead phone
after repair done phone will auto in download mode
full flash it by Odin all will ok
Enjoy free dead repair soft now
=======================
---------------
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=​

iKevinShah said:
also for hard bricked phones :/ ???
Click to expand...
Click to collapse
If you can enter APX Mode then it's rescuablr
Herpderp Defy.

I have use this method and custom kernel = 0.
Nice work! But instruction is now enough full. It took about 3 hours of time to make sure that the phone worked.

Klajnor said:
I have use this method and custom kernel = 0.
Nice work! But instruction is now enough full. It took about 3 hours of time to make sure that the phone worked.
Click to expand...
Click to collapse
Do U mind sharing how to?

I'll try do it, but my english is bad. I thing will be difficult to understand what i mean.

Klajnor said:
I have use this method and custom kernel = 0.
Nice work! But instruction is now enough full. It took about 3 hours of time to make sure that the phone worked.
Click to expand...
Click to collapse
Could you tell what you did in a step by step manner, so that even the others facing the problem can use this method to solve it.

Mini step-by-step instruction:
0) Download and unpack archive to directory like c:\repair
1) Entering APX mode. Turn off phone. Hold Volume Up + Home buttons 10-15 second and plugin phone in usb port.
Install drivers from folder drivers in archive. After installing the device driver is defined as NVIDIA USB Boot-recovery driver for Mobile devices. It is mean that phone in APX mode.
You may try this method to enter APX mode: remove battery and unplug phone from PC. Hold Volumel Up + Home and plug phone to PC. Phone must be in APX mode now. Put buttery in phone.
2) Before do something do do nandroid backup. Copy it to PC.
Backup /efs to safe your IMEI.
3) Enter to APX mode, install driver and start GT-I9103.bat. If you have some errors - try again without rebooting phone. Or unplug-plug USB and try again.
Phone reboot in download mode.
4) Use Odin to flash ogiginal samsung ROM. I used сhinese ZCLA1 2.3.6. You must use PIT file to repartition file system of phone. p5.pit is on archive. If you try flash without PIT process will be fault.
5) When flashing finished load phone in recovery mode. Wipe /cache and try wipe /data.
Load android and format internal memory. Reboor in recovery mode again. Wipe all.
6) Now you have 100% work phone with custom counter equal zero, without yellow triangle and etc.
Take root and restore /efs to restore IMEI.
Take CWM, custom kernel and everything what you need.
Enjoy!
PS I have about 2-3 hours to sure phone work normal. If you know in advance - can be done in 15-20 minutes.
Google translate of my instuction( russian to english):
Training
0. Set unpack, better to go somewhere in the root directory, so in a way no spaces or other characters. But this is only a recommendation based on a small knowledge of Windows, I have a normal flash and the folder e: \ - = Samsung Galaxy R = - \ - = Dead Repair = - \
APX Mode
1.1 The largest shamanism - to be APX Mode. More or less reliable way, which I was able to do it - with the phone off hold down Volume Up + Home and plug the cord into the USB port. This method is reliable if the phone is alive.
If your phone firmware is broken (and it will be so if, immediately after the flash nvflash is not a normal firmware) - will have to catch this moment, because phone might try to get recovery (as it too may not be).
If you can not do it you can do: take out the battery, hold down Volume Up + Home and insert the cord into the computer. Once the phone is switched to battery mode APX return to the place, because flashing at a certain moment the phone off the USB port (just a guess, but without the flash batteries did not work).
1.2 After that, the phone went into the mode of APX, he determined on the computer as a device driver without APX. The driver is included. No problems with installation on Win 7 Pro SP1 x64 I do not have arisen. After installing the device driver is defined as NVIDIA USB Boot-recovery driver for Mobile devices. If you do so - then everything is fine.
2.1 What is necessary to have to start:
Actually set to restore the phone. He is quite self-sufficient.
Any firmware. I sewed the latest version of the Chinese I9103ZCLA1 2.3.6 firmware
Of course, Odin, the phone cord, and so you need to flash.
Be sure to make backup / efs. After nvflash IMEI, I folded to form 000004999900001 (well something like that, do not remember exactly).
If the actions are performed to reset the custom kernels - can be done at the beginning of nand backup. Yes, in general nand backup is needed in any case. Theoretically, such a scheme is possible: backup - nvflash - odin - cwm - restore. We get the phone in the same form but with zeroing counter. I am due to its krivorukost could not verify. In order not to repeat my mistakes - make a copy after the backup on your computer. It was quite unpleasant to lose all the settings over the last month (but then I blame myself, accidentally formatted the card).
2.2 Connecting the phone to APX to a PC, run GT-I9103.bat. If everything went without a problem - the script is complete without error and the phone goes into download mode. If there was a mistake - you can try again to flash.
For example when I have an error like in the image - just twitched and started the lace zanogo bat. I think if the phone was left in the mode of APX. My heart skipped a beat, but the second attempt the phone flashed fine.
Firmware
We sew a 3.1 firmware odin. Most importantly - do not forget to specify the file pit. It is a complete recovery. Bit to bit the same as there, that this firmware.
Without nutrition ask you not to succeed, because file system is a mess of half-dead sections. Sewed only some parts of the firmware. Once downloaded, the phone displays a picture of a bunch of Korean characters and English phrases like "Software update failure".
3.2 After the firmware partition / data, as I understand it, is not formed. I would suggest the following algorithm:
We go in and format the built-in recovery / cache.
Ship, and through him the android usb-format the drive. I then have to format it, just in case a recovery.
I do not know what will be if you try to install the firmware as soon as CWM, try to format all of them, and make recovery backup. I just have no backup at hand (accidentally formatted the same section of CWM / emmc and it was an external card, where to store my backups).
03.03 Well, after much room for activities. CWM and restore from backup or set up from scratch - you decide.
Conclusions:
When the curve could theoretically restore the firmware. Maybe even a bit boot-loader. I got the impression that the APX - a mode of the chip, not software. If iron is not dead - should help. In general, an hour and a half I have had the phone without a flash, probably the same at the time will resize partition to pull the cord and battery.
Resets the counter custom kernels, lost the yellow triangle. In general, if you flash the original firmware - can be easily dragged into service.
The method is not the easiest, there are many pitfalls, such as in the beginning, I forgot about the PIT, could not understand why the work is already in the phone memory is not working correctly, etc.
On the other hand, this method is not much harder than flashing the phone or through the odin cwm. Just add a few points.
Phone neubivaemy. Like my last samsung i780 (where I really made a mistake and did not start flashing in the sequence. And vykovyrivanie three parts of the firmware exe file - also had a very high risk). So much suffering in the firmware, but it is still alive. In general, I would say that acting on the instructions (or at least about following it) phone can not be killed. I love samsung for it.
Click to expand...
Click to collapse

Klajnor said:
Mini step-by-step instruction:
0) Download and unpack archive to directory like c:\repair
1) Entering APX mode. Turn off phone. Hold Volume Up + Home buttons 10-15 second and plugin phone in usb port.
Install drivers from folder drivers in archive. After installing the device driver is defined as NVIDIA USB Boot-recovery driver for Mobile devices. It is mean that phone in APX mode.
You may try this method to enter APX mode: remove battery and unplug phone from PC. Hold Volumel Up + Home and plug phone to PC. Phone must be in APX mode now. Put buttery in phone.
2) Before do something do do nandroid backup. Copy it to PC.
Backup /efs to safe your IMEI.
3) Enter to APX mode, install driver and start GT-I9103.bat. If you have some errors - try again without rebooting phone. Or unplug-plug USB and try again.
Phone reboot in download mode.
4) Use Odin to flash ogiginal samsung ROM. I used сhinese ZCLA1 2.3.6. You must use PIT file to repartition file system of phone. p5.pit is on archive. If you try flash without PIT process will be fault.
5) When flashing finished load phone in recovery mode. Wipe /cache and try wipe /data.
Load android and format internal memory. Reboor in recovery mode again. Wipe all.
6) Now you have 100% work phone with custom counter equal zero, without yellow triangle and etc.
Take root and restore /efs to restore IMEI.
Take CWM, custom kernel and everything what you need.
Enjoy!
PS I have about 2-3 hours to sure phone work normal. If you know in advance - can be done in 15-20 minutes.
Google translate of my instuction( russian to english):
Click to expand...
Click to collapse
Nice!
Now many people in this forum should be able to get their Galaxy R back to life from the dead thanks to you!
Just one suggestion brother, keep on monitoring this thread if any person has any doubts or is facing any problem while trying to solve using your instructions, you could help them better.
I am going to directly link this post in the FAQ section.
Cheers (with a bottle of super fine Russian Vodka) !

Great job Klajnor! молодец!

'cooleagle' said:
Nice!
Just one suggestion brother, keep on monitoring this thread if any person has any doubts or is facing any problem while trying to solve using your instructions, you could help them better.
Click to expand...
Click to collapse
Ок. I will monitor this theme when it possible

One suggestion: Volume Up + Home doesn't bring any effect. To enter APX mode I had to press Volume Up + Home + Power button. Interesting that this is the way to reach recovery on some Galaxy handsets.

Volume Up + Home + Power button - it is also work. I wrote Hold Volume Up + Home buttons 10-15 second and plugin phone in usb port. I thing this way is more reliable

Hi,tried the above method for I9103 but when i proceed the steps it shows the download mode initialzed and the window shuts up and the fone remain dead,no response on fone. Installed drivers for APX and Iam using XP Sp3.

What window shuts up? bat script? If you mean bat - then that normal. If you want see result of it work use cmd.exe to run script.
Turn on phone in download mode( vl_up + home + power or vl_up + home and plug phone in usb) and try flash any firmware via onid (don't remember use pit file from firmware or from repair folder).

After restoration, at me runs not into a downloading mode, and in mode NVFLASH Recovery Mode

Just to report, there is no APX mode on my SGR
Wait is it just black screen?
Yesss it is

how is that possible?

Any chance to create this for P7500 / P7510?

Guys, sorry for OT.
http://forum.xda-developers.com/showthread.php?p=25125344#post25125344
According for the thread link above, does this method helps to solve it?
Thanks for your attention

i want to reset my binary without jig can anyone guide me with proper steps & i dont want to ruin my phone

[Q] Help with update to jb.

I need help to update my phone, I bought this phone from a friend, the phone now has unlocked bootloader. CM10 installed, what steps should I take to upgrade to jb? - also has twrp recovery installed.
Thank you in advance.
--I have the RSD Lite v6.1.4 installed and motorola drivers too, and the file asanti_c_sprint-user-4.1.2-9.8.2Q-122_XT897_FFW-5-6-release-keys-cid9.xml , Downloade. just need help about what to do now!

I am in the same boat. Long time windows mobile user, and jumped ship when the photon Q came along.
Looking for an step by step idiots guide to backing up what I have and how to flash the new.
Would be willing to send a guy a few paypal bucks for your time to write it up.

RSD LIte is a minimal UI, windows app, not much to think about. Plus, this topic has been discussed and explained all over the web (that includes xda forums)
1) boot device to bootloader (power + camera - then select fastboot/bootloader - additional info on how to select is written on bootloader screen)
2) verifiy your device is recognized in fastboot mode
3) select file to flash
4) press start button
5) wait 'till device boots to android
http://www.youtube.com/watch?v=AHaEHjSzvQQ (different device, same procedure)
That simple (if you can get pc/rsd to recognize the device )

mrvek said:
RSD LIte is a minimal UI, windows app, not much to think about. Plus, this topic has been discussed and explained all over the web (that includes xda forums)
1) boot device to bootloader (power + camera - then select fastboot/bootloader - additional info on how to select is written on bootloader screen)
2) verifiy your device is recognized in fastboot mode
3) select file to flash
4) press start button
5) wait 'till device boots to android
http://www.youtube.com/watch?v=AHaEHjSzvQQ (different device, same procedure)
That simple (if you can get pc/rsd to recognize the device )
Click to expand...
Click to collapse
i follow all the steps but i get stuck on, flashing NON-HLOS.bin" partition="modem, It fails right there. any ideas ? thanks
* I need to remove any other line? I have removed the 2 lines required.
never mind!
VICTORY running rooted jelly bean with TWRP recovery!
I think now I learned about motorola phones It is very easy but takes a while, when you know nothing lol. I've always been on the HTC phones.
( SOLVED )

Did I kill my phone?

I'm going to try and encapsulate everything that's going on into this initial thread but I'm sure I'll miss something.
Basically, I undertook to root my phone last night. I followed all the steps in the root thread, and I thought it worked, but then when I went to the root checker to see if I was successful. The test couldn't get a result the first time, and then failed the second time. I've known my phone to be a little temperamental when it comes to stuff like that, so I shrugged it off. Then, everything started running with so much lag that my only option was a reboot. It came back up just fine, but then, apps wouldn't open anymore. Since a reboot fixes everything, I rebooted AGAIN... except no I didn't, because I couldn't move past the white splash screen.
After some time hacking around with TWRP, system restoring my phone and the like, I finally managed to actually load the OS again. I think the phone was rooted at that time, but I don't know for sure, because this was the drawback: I couldn't install ANYTHING. My idea is that the system was rebooted into read-only mode. I tried everything I could think of to revert the system to rewriteable again, but nothing ever panned out. There was just one thing that stood out to me: "Your phone worked properly when it wasn't rooted." So, I got the brilliant idea to use SuperSU to unroot my phone. Stupid, stupid move, because now my phone can't boot past the white splash screen again. As a last ditch effort, I decided that it was time to flash the stock system to the phone. Except I probably did it wrong.
Code:
fastboot flash recovery recovery.img
Code:
fastboot flash recovery system.img
Code:
fastboot flash recovery boot.img
And where I stand now is that my phone will not boot past the white splash screen, and I can no longer access either TWRP or Fastboot.
Is my phone fooked, or can anyone save this?

#1 You can't flash system image via fastboot - it's semi-locked.
#2 You can't use 'flash recovery' command for boot and system images.
#3 For restoring your phone use SP Flash Tool - there's a thread in the General section called 'How to unbrick'.
Try it and let us know.
Cheers

Yeah, I realized afterward that if I were trying to flash the image of the system, I should not have used the "flash recovery" command because I disabled access to the other recoveries, lol. I have tried to use the SP Flash Tool in the past few days, but I could never get any download progress. I think my computer isn't making the VCOM drivers accessible to be able to flash those things to my phone. Do you have any advice on that end? Because I have seen that thread and tried those steps but I'm just not successful.

You should also read all replies to this thread - there are people who solved their problems with SPFT in their own way, that's how I've revived my phone from hardbrick.

Make sure you're phone is disconnected when you start the flash. AFTER you hit the download button in SPFT... then connect your phone...

Fantastic advice from both of you. I'm ready to revive my phone!

Okay, I think I'm making good progress on recovering my phone. I have managed to get back the stock recovery onto my phone, which I then used to install TWRP. But I'm not out of the woods yet. I used fastboot to flash the boot image onto my phone also, but when it came to the system image, I'm having a lot of trouble. The only ROM I can find for the Blu Pure XL is a 7z file. Now, I know how those work, I have 7zip and I extracted it for the system image. When fastboot was available to me, I couldn't push the system image to the phone. Now that I have TWRP and I have no more access to fastboot, I've tried to load the system file onto my phone through my SD card in four different ways:
As a .img file
As a .7z file
As a .zip file that I created by zipping up the image file
As a .zip file that was .7z, but I changed the extension
None of those methods worked. The Blu development thread doesn't point me to a zipped ROM file. One person there said that they had a backup of their files and provided a link, but those images seem to have been removed.
I'm so close, I can see this phone working again in the near future, I just need your help to get me there. Please! :'(
Edit: Also, keep in mind, I'm dumb. I don't think I really did anything super wrong, but I may be missing something ultra obvious. So if you could just keep your answers dumb for me, it would help even more.

I would stop trying to use all of the methods you are using I believe you are slightly confused by them at this time..
At this point what you have done with the random image flashing is get damaged partitions..
Get SPFT. Turn off you phone completely.
Download the full Scatter file for you phone. (put it aside).
Download a file called ALL MTK driver install. ( or something to that effect). Search for it on Google. You will find it. Run it and then reboot your PC completely.. (if you have windows 8 or higher look online on how to install unsigned drivers) --THIS IS THR BIGGEST PROBLEM PEOPLE HAVE--
Extract your full downloaded scatter image to a directory.. (you can download the Gionee E8 image if you want) it is what I am running on my Blu..
Run SPFD read the thread that they pointed out to you. Find the scatter and point SPFD.. Once it is loaded on the program UNCHECK the PRELOADER check box.. (if not you can cause problems) ..
click download and after 10 seconds or so plug in (you completely powered off) phone into the computer..
.Then wait..... and wait... It will tell you it's progress..
Keep trying it, it WILL work.. and ALWAYS unchecked preloaded when flashing with spdf...

I did follow all the steps in the original guide, and I followed the steps that you gave me too, down to using the advanced device manager to remove any MediaTek drivers from the computer and restarting the computer with disabling the driver signature verification, but when I click download, wait, and plug my phone into the computer, just nothing happens. The computer says it's an unrecognized device, and the download never progresses.
I see also that you said keep trying, but every time I try the SPFT, it never sends anything to my phone. And I don't even know how to tell if I'm missing some important step.

OK this happens sometimes. plug the phone in with device manager open.. plug the phone in when it is off..
When it says unrecognized device double click on it really fast( it will disappear fast, try it a couple of times if you don't get it the first time) then hit update driver.. point it to the MTK drivers folder (unzip the MTK drivers folder). It will pick the proper driver. on some computers it loads up so fast it has no time to recognize the driver..
After you load the drivers power off your phone again and follow the instruction I gave.. After you do this once it will load the drivers right after this..

When I double click on the unrecognized device button, it just brings up a notification that my device wasn't recognized because it malfunctioned. I don't have an option to install any drivers.

My problem is finally solved. After starting up SPFT and clicking download, I held Vol - and Power and then connected it, and that pushed the download forward. I got to the Blu animation screen, and it stayed up FOREVER, but then the next time I looked over, it was on the initial setup screen. Good as new.
Thank you guys for all your help. This forum really is an amazing place.

OP7 Pro Fastboot Bootloop! [HELP]

This may be a simple solution, but I am completely puzzled on how to fix this.
SO i recently rooted my phone & used the twrp "twrp-3.3.1-4-guacamole". Installed magisk via that twrp and continued with my day.
I accidentally got a virus by trying to get a full free vpn, me being a terrible pirate, i accidentally got a virus! Silly me.
It was annoying me and I decided to factory reset my phone... not via twrp. I remembered after I clicked "Reset all" on oxygenos that it's not the way how to do it with a root device, and well.. it didn't exactly work.
Every time I power/reboot the phone it just brings me to the fastboot menu of "START", "POWER OFF", "RECOVERY MODE", & "RESTART BOOT LOADER". I thought since TWP is recovery mode I try to access that... no luck, it just brings me back to that fastboot menu. I tried going on CMD via adb by saying "fastboot flash boot twrp-3.3.1-4-guacamole.img". It will say it's finished and successful, but when i reboot and try to access recovery mode it just does not work.
TL;DR: Think I bricked my phone, there is no OS installed and I can only access the fastboot.
Any help? Much appreciated

https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691

trapcoder666 said:
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
Click to expand...
Click to collapse
Thank you for the guap recovery as i didn't know it existed. However, what are the steps? when i go on the MSM download tool it doesn't detect my phone.
that being said, i can't access any of my files through my pc using fast boot. on MSM it's just saying "waiting for device" even when plugged in so thats annoying.

trapcoder666 said:
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
Click to expand...
Click to collapse
I downloaded the one you sent, and after a while as my internet is bad. It still does not work.
Whenever I try to install the qualcomm drivers it never shows up, and when i try and boot it up so the gual recover detects my phone it never works. It's still saying "waiting for device".
Does anyone know how to fix this? it's doing my head in that it's not as easy as it should be.

MOweenSalah said:
I downloaded the one you sent, and after a while as my internet is bad. It still does not work.
Whenever I try to install the qualcomm drivers it never shows up, and when i try and boot it up so the gual recover detects my phone it never works. It's still saying "waiting for device".
Does anyone know how to fix this? it's doing my head in that it's not as easy as it should be.
Click to expand...
Click to collapse
Pretty sure that your phone will not be accessible via adb/fastboot during the msm process. Did you follow the directions in the link above to a T?
A few things to note:
- Works perfectly fine for unbricking GM1917 modeled OnePlus 7 Pros.
- Use the original cable and try to plug it into a USB 2.0 port. I've found that this is the most ideal condition.
- Make sure your device is charged up. If you can't see how much charge it has, leave it charged via the 30W warp charger for 40 minutes and that should be good enough.
- In the L2 drivers folder found in the archive, navigate to the 32 or 64 folder depending on your system's architecture, and click on the file that ends in the extension ".cat". Then, click "view signature", then "View certificate", then "Install." This is IMPORTANT.
- Then, make sure your device is powered OFF, then, plug in the USB-A side of the cable (big head) into your computer and do NOT connect the USB-C (small head) into your phone yet.
- Hold down Volume up AND volume down for five seconds, and while you're continuing to hold, plug the USB-C side into your phone. The drivers should automatically download, and you should see a "Qualcomm QD loader" device in Device Manager. If you see an exclamation mark or you don't see this, you are doing it wrong and you need to repeat the above steps.
- Open up MSMTool.exe as an administrator and click 'start' only. Should take a few minutes, but you will have a good-as-new OnePlus 7 Pro.
Click to expand...
Click to collapse

Krsmqn said:
Pretty sure that your phone will not be accessible via adb/fastboot during the msm process. Did you follow the directions in the link above to a T?
Click to expand...
Click to collapse
I did yes, i pressed all buttons and the power button for 5 seconds and plugged my charger in. Then after that went on the MSM tool and it went straight to the fastboot. I really don't know but it loves this fastboot tool haha

Krsmqn said:
Pretty sure that your phone will not be accessible via adb/fastboot during the msm process. Did you follow the directions in the link above to a T?
Click to expand...
Click to collapse
Add: I made a video showing what I mean with the fastboot. Basically if i do anything with the phone fastboot it will just go back to the menu (sorry for bad quality)
https://www.youtube.com/watch?v=jU8a6kDXNNs&feature=youtu.be

MOweenSalah said:
Add: I made a video showing what I mean with the fastboot. Basically if i do anything with the phone fastboot it will just go back to the menu (sorry for bad quality)
&feature=youtu.be
Click to expand...
Click to collapse
It's one of those things where if someone was there with you, it'd likely get figured out. I've seen this kind of situation hundreds of times on XDA, and with all due respect, the problem is most always at the hands of the user. These phones are cookie cutter made, so there's nothing different (besides individual variants) that would make thee tools not function correctly, unless it's operator error. But that's not set in stone. Just don't give up. Try setting up your camera for an overhead view. I couldn't tell if you were plugging in your cord. And it seemed to reboot, instead of power off. Repeat the steps carefully, and see if you can achieve better results.
Don't give up! We're here for you ?

Make sure phone is powered off before plugging it in. Launch msm tool, Press the vol up and down key for a few seconds then plug in.
Edit : make sure your drivers are up to date too.

I don't know about msm tools never tried it but I know your situation.
Don't do fastboot flash boot twrp-3.3.1-4-guacamole.img
Remove the word flash. You are supposed to boot into twrp then flash the zip file to the phone.
look at this

Command in Fastboot mode is:
Fastboot boot "name of the recovery".img. Phone should boot to twrp. Then flash twrp.zip
or try Fastboot roms:
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
Choose the one for youre phone (region)
MSM tool it's the last option.

Can't you just switch slots from fastboot or did you mess up both?

trapcoder666 said:
Make sure phone is powered off before plugging it in. Launch msm tool, Press the vol up and down key for a few seconds then plug in.
Edit : make sure your drivers are up to date too.
Click to expand...
Click to collapse
Firstly I'm terribly sorry for no response (same goes to everyone else looking into this matter for me. THANK YOU!)
However, I have done this multiple times in the past and it instantly goes back to boot menu. it sucks :/

IronSingh said:
I don't know about msm tools never tried it but I know your situation.
Don't do fastboot flash boot twrp-3.3.1-4-guacamole.img
Remove the word flash. You are supposed to boot into twrp then flash the zip file to the phone.
look at this
Click to expand...
Click to collapse
Okay. I shall go and look into this situation when I receive my phone back (going to explain that in a later quote)

larsdennert said:
Can't you just switch slots from fastboot or did you mess up both?
Click to expand...
Click to collapse
If i'm honest with you.. i'm not sure in the slightest. My only assumption is no because the only thing I can access is only the fastboot. if i attempt to go into recovery mode it will go back to fastboot. when I flash twrp it will flash but it won't boot into it. It's confusing as hell.
Just to add to this whole situation:
Since I have no idea and just wanted it fixed in the day; i was willingly to give money for this phone to be fixed, but thanks to the person, he just made it a slower process by doing things i've already done.. going to pick the phone back up in an hour of this message.
I haven't used the fastboot boot twrp cmd yet, but from how everything else has been so far i feel like that won't work, but i will update everyone on that situation.
Just to add additional things that I may have not mentioned in the past will be below:
- Whenever i type in "ADB Devices" in cmd, it will not show up with anything. However, when I type in "fastboot devices" it shows it's serial and in "fastboot". It will only show as fastboot and i can't access the phone via file explorer in windows.
When i say "ADB Devices" it says *devices attached* and will show none of my phones details, but when i say fastboot devices it will then show the devices.
^ what i said above means I can't use the guap recover, or anything which means the phone has to be detected in windows, because other than fastboot, it won't work at all.
- So far I can't access twrp as a whole, so if anyone knows how to give me a guide on how to install it from where I am at, that would be amazing (if not, i'll try and reiterate what to do with the one given from a previous comment, so thank you )
- There was one time I was allowed in TWRP but i completely forgot how i entered it (so i can't explain), So i feel like there is hope in that aspect. I feel like i entered something via cmd so maybe there's a way?
In terms of hardware my phone is completely fine, there's not a single problem other than the software being a pain in the ***!!
if anyone can just spew out a bunch of help in different explanations it means the world because so far all I can see is that I wasted about £600 on an amazing phone because of dumb *** haha.
Thank you to everyone who has helped, and is helping

From your comments, you are not familiar with how Android functions. Not knowing the difference between adb and fastboot is an indicator that you should just endeavour to have a stock phone until you understand whats going one. It's also hard for people to help as no one has hands on and can see what is broken. Everyone here will be working blind like trying to fix your car for you from across the country.
Start the phone into fastboot and connect it to a pc. From a pc command prompt in your fastboot directory enter the command:
fastboot getvar current-slot
If the current slot is A then:
fastboot --set_active=b
or vice versa
fastboot --set_active=a
then fastboot reboot and see if you boot into the other slot.
Not knowing what phone you have makes it even tougher but I suspect you will have to reflash a clean complete rom via fastboot.
https://forum.xda-developers.com/on...fastboot-roms-oneplus-7-pro-t3931424#poststop

larsdennert said:
From your comments, you are not familiar with how Android functions. Not knowing the difference between adb and fastboot is an indicator that you should just endeavour to have a stock phone until you understand whats going one. It's also hard for people to help as no one has hands on and can see what is broken. Everyone here will be working blind like trying to fix your car for you from across the country.
Start the phone into fastboot and connect it to a pc. From a pc command prompt in your fastboot directory enter the command:
fastboot getvar current-slot
If the current slot is A then:
fastboot --set_active=b
or vice versa
fastboot --set_active=a
then fastboot reboot and see if you boot into the other slot.
Not knowing what phone you have makes it even tougher but I suspect you will have to reflash a clean complete rom via fastboot.
https://forum.xda-developers.com/on...fastboot-roms-oneplus-7-pro-t3931424#poststop
Click to expand...
Click to collapse
I do appreciate the help. If i'm honest with you the only reason I did this is to increase my data speeds (which from look of things is outdated now), and a longer battery life. I don't know much about rooting/jailbreaking but believe me that I have been in the scene for years, but not even knowing everything haha!
that being said.. i'm in twrp! thank you so much mate, i'll try and go and install the rom now. thank you!

Now install the zip twrp

Thankfully.. IT'S FIXED!
I didn't have to install twrp again or any of that. I simply changed the slot from A to B and pressed all buttons when it was showing the "! Your decide is unlocked" orange/black screen.
I had msm tools up and it detected and instantly installed the OS to the latest one and boom. It works again!
I got to thank everyone for helping me because without you people I wouldn't of been able to fix it. I looked everywhere and no help anywhere as I feel like it's pretty dumb to do what I did haha!
Thank you again people!

Oh you gave up on root?
You are supposed to read the instructions and follow them to the letter. When I read your post I realized you tried to install twrp like you would pre Oreo but it changed you have to boot into twrp then install it via zip file.
Anyways just remember that for next time.