Related
I really hate to join under such a condition (it's an amazing site which I thought I would join for better reasons when time permitted), but my new Galaxy Nexus just went to hell on me after flashing the (apparently) popular Jelly Belly mod.
I started with a rooted 4.1.1 Jelly Bean OS with ClockworkMod Recovery, and now it looks like disaster after using that to flash Jelly Belly - what happens now is my phone boots up to the point where it flashes that colored Google "X", but it never proceeds beyond this point. I cannot put a different mod on my phone because there is no connection with my computer, and I can't stop my device from thrashing without a battery-pull. Is there any way save this phone and put plain Jelly Bean back on it?
bluroot said:
I really hate to join under such a condition (it's an amazing site which I thought I would join for better reasons when time permitted), but my new Galaxy Nexus just went to hell on me after flashing the (apparently) popular Jelly Belly mod.
I started with a rooted 4.1.1 Jelly Bean OS with ClockworkMod Recovery, and now it looks like disaster after using that to flash Jelly Belly - what happens now is my phone boots up to the point where it flashes that colored Google "X", but it never proceeds beyond this point. I cannot put a different mod on my phone because there is no connection with my computer, and I can't stop my device from thrashing without a battery-pull. Is there any way save this phone and put plain Jelly Bean back on it?
Click to expand...
Click to collapse
the proper term to use here is bootloop
ur phone bootlooped and u need to flash back the stock firware via odin
go back in the dev section and find somethng relatd to odin
remmbr bfre flashing any rom u shud always backup ur rom via clockworkmod
u must have done something wrng while flashng jellybean mod...take the steps crrctly
EDIT:- http://forum.xda-developers.com/showthread.php?t=1827685
heres the link to fix ur phone
properly take the steps plzz
bluroot said:
I really hate to join under such a condition (it's an amazing site which I thought I would join for better reasons when time permitted), but my new Galaxy Nexus just went to hell on me after flashing the (apparently) popular Jelly Belly mod.
I started with a rooted 4.1.1 Jelly Bean OS with ClockworkMod Recovery, and now it looks like disaster after using that to flash Jelly Belly - what happens now is my phone boots up to the point where it flashes that colored Google "X", but it never proceeds beyond this point. I cannot put a different mod on my phone because there is no connection with my computer, and I can't stop my device from thrashing without a battery-pull. Is there any way save this phone and put plain Jelly Bean back on it?
Click to expand...
Click to collapse
Are u able to boot into CWM recovery, Power and both volume up and down?
garner said:
Are u able to boot into CWM recovery, Power and both volume up and down?
Click to expand...
Click to collapse
When I do, I have that "Downloading..do not turn off the target!" message. Why this - I did remove the supersu file, although I think I left my clockworkmod file on the root because now you have to re-flash that every time you use it. Now I have no option other than "Start" - any chance of breaking through now?
bluroot said:
When I do, I have that "Downloading..do not turn off the target!" message. Why this - I did remove the supersu file, although I think I left my clockworkmod file on the root because now you have to re-flash that every time you use it. Now I have no option other than "Start" - any chance of breaking through now?
Click to expand...
Click to collapse
thats not fastboot, thats odin mode. use vol up and down and power button to get to fastboot mode
the entire reason your phone is behaving the way it did is because you didnt wipe data/cache before flashing the rom.
you really need to do some reading before you start modifying your phone
Zepius said:
thats not fastboot, thats odin mode. use vol up and down and power button to get to fastboot mode
the entire reason your phone is behaving the way it did is because you didnt wipe data/cache before flashing the rom.
you really need to do some reading before you start modifying your phone
Click to expand...
Click to collapse
Do you mean that I need to continually rock the Volume key up and down while holding the Power button? Volume Up with Power put it in boot mode, and when I tried rocking it a couple of times I got the same result. It I understand you correctly, the idea sounds tricky. Is this supposed to work on a Galaxy Nexus?
press and hold both ends of the volume button and the power button... its really not that hard.
Zepius said:
thats not fastboot, thats odin mode. use vol up and down and power button to get to fastboot mode
the entire reason your phone is behaving the way it did is because you didnt wipe data/cache before flashing the rom.
you really need to do some reading before you start modifying your phone
Click to expand...
Click to collapse
What I really should have done was slow down, or quit while I was ahead to get some rest last night! I had researched the root process for my phone ad nauseum, which I know is why I succeeded at getting ClockworkMod safely installed. By the time that was done I was tired, but I counldn't stand the thought of living without my files loaded on my phone - I was in the bad state of needing too much to complete what I had intended to do. I see I had the wrong impression that ClockworkMod would take care of the whole process once I had that working, guess it didn't. When you've been through the process of installing a hundred versions of Windows and Linux on a PC, which never needs to be pre-wiped (the new OS does that), who would have thunk it's that much different with a phone computer?
Did you get this solved? Just reboot into recovery (hold down power, volume-up, and volume-down simultaneously to get into bootloader, choose recovery using volume buttons, select using power button), full wipe (system, data, cache), and reflash your ROM.
bananagranola said:
Did you get this solved? Just reboot into recovery (hold down power, volume-up, and volume-down simultaneously to get into bootloader, choose recovery using volume buttons, select using power button), full wipe (system, data, cache), and reflash your ROM.
Click to expand...
Click to collapse
This is another thing I never would have guessed without being told specifically, that it's even possible to hold down both ends of a rocker switch and have it do a different function - I tried this, and now it works! I had used my PC to root my phone last night, and right now I'm at work, where there will be time to go through this in a couple of hours. I took a brief look at the tutorial recommended by Zepius, and am wondering if I am set to proceed. I plan on using my work PC, not the one at home with the drivers I used to root my phone. Nobody else uses it and I have never used it for anything phone-related. Can I presume any drivers which I'm warned should be uninstalled would be on the PC which is used, and not the phone?
bananagranola said:
Did you get this solved? Just reboot into recovery (hold down power, volume-up, and volume-down simultaneously to get into bootloader, choose recovery using volume buttons, select using power button), full wipe (system, data, cache), and reflash your ROM.
Click to expand...
Click to collapse
Sorry, I had to work, but now there's time and I thought I would try my work PC, which is virgin (so to speak) of mobile devices and drivers. It's a Windows XP system, and right now it's not looking good because when my phone is plugged in, there isn't a "Portable Devices" or "Mobile" category under Device Manager. Do I have a better chance of this working on my home Windows 7 system?
bluroot said:
Sorry, I had to work, but now there's time and I thought I would try my work PC, which is virgin (so to speak) of mobile devices and drivers. It's a Windows XP system, and right now it's not looking good because when my phone is plugged in, there isn't a "Portable Devices" or "Mobile" category under Device Manager. Do I have a better chance of this working on my home Windows 7 system?
Click to expand...
Click to collapse
I guess that's a never-mind, I should have had my phone on! It's in Fastboot mode now, but I still don't know if what I see in Device Manager is good for what I'm trying to do. No portable device, phone, nor galaxy nexus, but what did change is I have "Broadcom Nextreme 57xx Gigabit Controller" appearing under "Network Adapters". Is this a problem to be dealt with differently when your phone is bricked?
bluroot said:
I guess that's a never-mind, I should have had my phone on! It's in Fastboot mode now, but I still don't know if what I see in Device Manager is good for what I'm trying to do. No portable device, phone, nor galaxy nexus, but what did change is I have "Broadcom Nextreme 57xx Gigabit Controller" appearing under "Network Adapters". Is this a problem to be dealt with differently when your phone is bricked?
Click to expand...
Click to collapse
1) your phone is not bricked. dont call it that
2) best way to check if your drivers are installed correctly
open a command prompt in the folder where your fastboot.exe is and type: fastboot devices
if you get a device ID, your drivers are setup properly for fastboot
3) at this point, just return to stock: http://forum.xda-developers.com/showthread.php?t=1626895
Zepius said:
1) your phone is not bricked. dont call it that
2) best way to check if your drivers are installed correctly
open a command prompt in the folder where your fastboot.exe is and type: fastboot devices
if you get a device ID, your drivers are setup properly for fastboot
3) at this point, just return to stock: http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
I got a device ID (long string of characters) on that fastboot command, but I'm still concerned that my phone won't talk to Device Manager at all. Windows 7 doesn't pop up a connection window when it's plugged in, should that be expected?
What I mean by "not talking to Device Manager" is that the only item under Portable devices is just E:\ - no device listed here! The tutorial in your signature hinges on there being a device listed "without thde yellow exclamation point", for the installation of new drivers, therefore I don't know how to follow it from here. The adk drivers which were used to root my phone (they were good, the problem began when I tried to flash a rom and missed a step or three) are stil there, but I'll replace them if I can find a process which can talk to my phone in it's present state.
On a side note (and only because it held me up in responding tonight from my Windows system), is this site partial to Firefox? I am able for the first time to login, and I wonder if it isn't because I quit trying to through my Windows 7 system. It has only Windows IE, and Chrome (which couldn't even browse this site). I am currently on my Ubuntu system with Firefox.
good lord... you have a device ID so just use the fastboot commands... start at part D
Zepius said:
good lord... you have a device ID so just use the fastboot commands... start at part D
Click to expand...
Click to collapse
I said much the same myself.
For the fastboot devices test, I have a string of characters, but no device name, only "fastboot" on the single output line with those characters. Is this a valid device ID?
"...just use fastboot" Ok, but how? Should (can I) even do this use fastboot to transfer files to my phone under it's somewhat anonymous status with Windows? Since last night's fiasco nothing was named under "Portable Devices", only "E:\" was displayed. I have no graphical display in the file manager, so how am I supposed to transfer the necessary files to the root of my phone? I don't even see a way of addressing it to install drivers now.
I will need drivers because I attempted to follow this tutorial (which doesn't account for what I am (not) seeing on my system. I got as far as uninstalling the good drivers which I used last night in favor of what was offered for use with the tutorial, and now Device Manager doesn't even have a Portable Devices category. The "Universal Naked Driver" was to replace my uninstalled drivers, and interestingly the contents of it's expanded folders don't even contain fastboot (the adb package which I used last night did). In light of this, how am I supposed to have even fastboot?
I hate to be a PIA about this, but I guess I'm more a n00b than was presumed in this tutorial - it's either that or my situation really is too different that I can use it as is. Could I please get a few clues in light of what the tutorial doesn't address? Do I have any means of installing anything and transferring files with my device-PC communications as they are, and if so how can I do it? I'll give it a run if I understand how.
Thanks.
Zepius said:
good lord... you have a device ID so just use the fastboot commands... start at part D
Click to expand...
Click to collapse
I see now that Part D calls for flashing JO03C from my PC, not the device root, ok.
Also, after rebooting my laptop, the E:\ is back under Portable Devices in Device Manager. When I double-click this I get the statement
Device: Portable Devices
Manufacturer: Generic-
Location: on UMBus Enumerator
I don't think this looks better than the Microsoft default, but is it good enough for what I need to do?
I still have the driver package android-sdk-windows, which contains adb and fastboot, so perhaps I should just use this according to Part D and see what happens?
bananagranola said:
Did you get this solved? Just reboot into recovery (hold down power, volume-up, and volume-down simultaneously to get into bootloader, choose recovery using volume buttons, select using power button), full wipe (system, data, cache), and reflash your ROM.
Click to expand...
Click to collapse
Seriously I respect the fact that your a noob we was all here once but if it your device is boot-looping all you need to do is the above
garner said:
Seriously I respect the fact that your a noob we was all here once but if it your device is boot-looping all you need to do is the above
Click to expand...
Click to collapse
Good god, I never should have read Zepius's tutorial - I didn't need my PC at all! If I understood what bananagranola had said, I could have saved a lot of time!
Oh, no, now I can't connect with the server!
Could I have possibly lost my radio from what I did earlier? I was able to boot up, and I was upgraded to 4.2.1 when I did the data wipe. Starting over, I should have had a prompt to connect with gmail and download my contacts, but this didn't happen. My People app is unpopulated, so I chose to connect to "sign into an account". While I am sure of my login input, it didn't recognize this, and then the process ended with a "couldn't finish - couldn't open connection with the server" error. Any clue where to go from here?
Some standard apps are missing too, including the Play Store app!
I realized there aren't any guides [in English] around here to help rooted folks that soft bricked their LG PRO to restore it back to factory settings. This should be useful if you got your phone stuck on the AT&T or the LG logo. Especially now that we don't have an unlocked bootloader or a recovery to reocver our soft brick.
Anyway, to start, a little disclaimer: I hold no responsibility if this method renders your phone completely useless, or burns and makes some nice fireworks. I'm simply writing this to document the process that worked for me. Use at your own discretion.
Dislcimaer 2: this method will wipe out your internal sdcard, apps data, everything! It'll restore the phone back to the way you got it from AT&T. Might even lose your cell unlock status (not verified). so keep these unlock codes handy just in case.
Note to linux users like myself: get your a** on windows or run it from a VM. VirtualBox with Win7 works fine.
Steps:
Download
1. LGFlashTools v1.5. Anything less won't work. Mirror: HERE
2. DLL file for LGE980
3. Drivers
4. The stock image file
Thanks to IOMonster for hosting these biga** files.
Install
1. Install the LG drivers downloaded above.
2. Install LGFlashTools v1.5 (but don't run it)
3. Extract the DLL and the TOT files from above and put them in a nice tidy directory
Drivers initialization
1. Put the phone into download mode. (Turn off device, keep pressing volume down while plugging in the micro usb cable. If this doesn't work, try holding both volume keys instead)
2. Let the phone initialize and install the drivers. Once done, in Device manager, you should see the LG phone listed under COM ports (something along these lines).
3. Find that LG entry in Device Manager, click on Properties, Advanced and then change the COM port to COM41 and close/save.
4. Unplug your phone! Important step.
LGFlashTools
To get this tool to work, you'll need to do a few tricks.
1. Set the computer's date to some time in July 2012 or before.
2. Disconnect the internet
3. Find a serial number or register key from somewhere on the web (a google search for lgflashtools serial will yield some results). Can't help you here and please don't share any keys in this thread or get us in trouble.
4. Execute the LGFlashTools. It should ask you for a key, put it in. Now you should see a dialog where you can load the DLL file and the TOT files that you extracted earlier. Put them both in here. Click ok
Flashing
5. There is a yellow arrow on the top left. Click on it to initialize the process. Once done, it should say "ready/finished" or whatever.
6. Put the phone in download mode again, and plug it into the USB port. LG FLash Tools should start flashing it automatically. When it's done, it'll automatically reboot into your stock AT&T rom and all of your data and internal sdcard files are gone.
Profit
Thanks again Mac !
MrNa5ty said:
Thanks again Mac !
Click to expand...
Click to collapse
sure thing I'm probably going to refer to it myself someday.
madmack said:
sure thing I'm probably going to refer to it myself someday.
Click to expand...
Click to collapse
Thanks .... great info!!!!!
Nice. Hopefully they sticky this.
Welp, just bricked the phone again but was able to flash the tot... very simple and quick lol ur the man mac
this worked perfectly fine for me. i 1st tried it on w8 but after plugging in the e980 and letting the drivers and such install, it did not show up under com in the device manager. in fact, there was no com section. it did show up under devices and printers and i tried and could not find a com setting there. i went ahead and tried to flash but since i could not change to the proper port, the flash tool never found my e980.
so instead i just did it all on a w7 box, the device was listed under com, and i went along with the flashing.
thank you.
Think this will fix the bricks that are happening when they try to mess around with the bootloader?
Sent from my LG-E980 using Tapatalk 4 Beta
jprosek said:
Think this will fix the bricks that are happening when they try to mess around with the bootloader?
Sent from my LG-E980 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Nope. Mess with the bootloader and you'll risk losing download mode.
nvm
This needs to be stickied!!!
Sent from my LG-E980 using xda app-developers app
My friend just bricked his and the wi9ed the system. I can get ir into download mode for him but thats it. I tried recovery mode but trying to do that or boot regularly it just shows lg the an android with the spinning symbol on it the lg again then lg 2 more times and just stays there. Can this be fixed with only download mode? Again I plugged it in and im not sure its being seen by the computer.
Make sure you have the drivers installed and use pc suite to get back the firmware
rob219 said:
My friend just bricked his and the wi9ed the system. I can get ir into download mode for him but thats it. I tried recovery mode but trying to do that or boot regularly it just shows lg the an android with the spinning symbol on it the lg again then lg 2 more times and just stays there. Can this be fixed with only download mode? Again I plugged it in and im not sure its being seen by the computer.
Click to expand...
Click to collapse
it doesn't hurt to try. I'll bet it will because I was left with something similar and this method got me back on stock.
smaybe said:
Make sure you have the drivers installed and use pc suite to get back the firmware
Click to expand...
Click to collapse
Pc suite? Do you mean lg flash tools? I downloaded it but it wants me to log in to use it. I havent found a log in for it yet.
Download lg pc suite it have lg flash tool in it
Then you search a little in menus for firmware urgence recovery something like that and if it don't work try update in the same menu
And if all of that didn't work I'll find you a link to flash a kdz
Deleted
I seem to have an issue with my E980, i cant get data my apn directory is empty and cant seem to add an apn it will just not save! anyone else have this issue or know what i can do? thanks!
Reboots to recovery only
Ok, I flashed the recovery in this post using the dd method http://forum.xda-developers.com/showpost.php?p=43460298&postcount=208
The value pack was trying to download on my phone and instead of cancel, I pressed install. Now the phone only boots into that recovery. I have everything from the op downloaded, but instead of download mode it only boots into the recovery, any ideas?
When it boots up, It says the following for a couple of seconds:
Code:
Secure booting error
Cause: Device Unlock, so boot success!!
Edit: Got it into download mode by holding down both volume keys and plugging into usb. Thanks!!
apascual89 said:
Ok, I flashed the recovery in this post using the dd method http://forum.xda-developers.com/showpost.php?p=43460298&postcount=208
The value pack was trying to download on my phone and instead of cancel, I pressed install. Now the phone only boots into that recovery. I have everything from the op downloaded, but instead of download mode it only boots into the recovery, any ideas?
When it boots up, It says the following for a couple of seconds:
Code:
Secure booting error
Cause: Device Unlock, so boot success!!
Edit: Got it into download mode by holding down both volume keys and plugging into usb. Thanks!!
Click to expand...
Click to collapse
I'm glad you got it resolved! I just edited the OP with this information.
hi. I encountered a problem on my phone that doesn't boot properly.
When i tried to switch on my phone it showed at first the welcome msg "Samsung S4 mini gt-i9192" then after that, a pitch black screen, could not properly boot. But i learn that it does not turns off after the screen turns all black, i have to press the power button first to turn off the phone.
This problem started when i installed an app with some compatibility problems.
I wanted to root my phone hoping that can solve the problem, but then again a problem occurred when i tried to connect my phone to my laptop. It fails to install MTP usb device to my computer. I tried connecting it again provided that samsung kies was installed but again failed to connect my phone. Therefore i cant root my phone because i cant copy the files needed to root to my phone sd card.
I tried reinstalling kies, installing mtp drivers but nothing happened. I tried also restoring the previous boot image, restoring factory settings using recovery mode. But then problem still exist.
And fyi my phone can't mount any external sd card using recovery mode. And i think it was not in a debugging mode.
Phone: samsung s4 mini gt-i9192
firmware: i dont know
So basically, the problem is:
my phone wont boot,
i cant connect it to my pc
and i cant root it.
How should i root or even flash my phone when i cant connect to my computer? Do you have any idea on how to solve this problem? Any solutions or suggestions would be much appreciated. tnx.
champagneerantja
emzgames said:
snipped.
Click to expand...
Click to collapse
Have you tried putting the phone in download mode (Volume Down + Home + Power) and then connecting it your p,c , if not give this a shot it should pick up the drivers , once done , take out the usb cable hold the power the button to shut down and boot up .
since you have not mentioned your OS am assuming it is windows , try taking out Kies via some software like revo uninstaller which will remove all directories plus all registry entires then reinstall it if you really need it.
dovakinn said:
Have you tried putting the phone in download mode (Volume Down + Home + Power) and then connecting it your p,c , if not give this a shot it should pick up the drivers , once done , take out the usb cable hold the power the button to shut down and boot up .
since you have not mentioned your OS am assuming it is windows , try taking out Kies via some software like revo uninstaller which will remove all directories plus all registry entires then reinstall it if you really need it.
Click to expand...
Click to collapse
tried both yet still unable to connect.
emzgames said:
tried both yet still unable to connect.
Click to expand...
Click to collapse
dial *#0808# from your cell this would take you in usb settings, tick both mtp+adb , reboot , if they art already ticked uncheck them and check them again.
dovakinn said:
dial *#0808# from your cell this would take you in usb settings, tick both mtp+adb , reboot , if they art already ticked uncheck them and check them again.
Click to expand...
Click to collapse
im afraid i cant do this coz i cant boot my phone properly, up to welcome msg only then screen black out, but not power off.
emzgames said:
im afraid i cant do this coz i cant boot my phone properly, up to welcome msg only then screen black out, but not power off.
Click to expand...
Click to collapse
ohhh best take your cell to your nearest service center then . if you can't flash anything and usb is not getting detected i don't see any other option , maybe someone more experienced here can help.
dovakinn said:
ohhh best take your cell to your nearest service center then . if you can't flash anything and usb is not getting detected i don't see any other option , maybe someone more experienced here can help.
Click to expand...
Click to collapse
yah, thats what im thinking. i just brought this here hoping to solve this problem without going to a shop. thanks anyway.
aac. To me put your phone in download mode then use moborobo(a windows software) . Just open it and it will install the driver. If it dies not work then use adb installer . Remember you should have only any one of the software at one tim means either moborobo or kies or adb installer
Sent from my GT-I9001 using xda app-developers app
btw have you tried to boot the phone in safe mode ?? if it boots in safe mode it is still fixable without going to service center. power down , power up+ tap the menu button 3 or 4 times at THE same time to boot into safe mode if it boots into safe mode that means the hardware and OS is fine if it does not well then your out of luck.
dovakinn said:
btw have you tried to boot the phone in safe mode ?? if it boots in safe mode it is still fixable without going to service center. power down , power up+ tap the menu button 3 or 4 times at THE same time to boot into safe mode if it boots into safe mode that means the hardware and OS is fine if it does not well then your out of luck.
Click to expand...
Click to collapse
tnx man, but no luck..
Tried flashing a custom rom?
I accidentally formatted bootloader, and now my device unable to detect,boot or anything. Is there anything I can do of ?
(might try everything to work it out )
Can you boot into the preloader with volume up and power pressed?
flash ROM via FlashTool
BlueFlame4 said:
Can you boot into the preloader with volume up and power pressed?
Click to expand...
Click to collapse
no, i could not
Kittehdispenser said:
no, i could not
Click to expand...
Click to collapse
Sounds like a hard brick, which means your phone is destroyed. What exactly did you do?
BlueFlame4 said:
Sounds like a hard brick, which means your phone is destroyed. What exactly did you do?
Click to expand...
Click to collapse
welp, i tried to install custom rom ( which need to download the rar and paste it into INTERNAL) but i accidentally paste it to my SD card. Then i start to install it.
Then i said it's uninstallable, I just restart my phone and everthing went normal buy my wallpaper screen turns black and unable to read it tho USB ( Just the standby screen shows wallpaper)
Then my brothers came out and said that all you need to do is format it again and reinstall. We tired countless times . But then it have another option which above Format everything but not bootloader and another is Format everything and bootloader.
Then my bro press it and ... It became bricked.
it's still warrantyable so .. I plan to play dumb to the warranty company if I can't fix it.
( even if i play dumb idk what reason I need to come off, if i say yesterday the battery from 70% drop to 0% then it unable to open again )
PS: before this happen my battery happens from 70% drop to 0%, after charged. it's fine
PPS: give me a good excuses to play dumb C::
Wait, wait. How did you format the bootloader? No recovery should have this option! The only possible option to hard brick the P8000 is to pull out the USB cable in the exact moment when the SPFlash Tool writes it. So, can you elaborate a bit more about what you've done? I'm pretty sure you're missing something.
Soft Bricked HTC Desire 616
BlueFlame4 said:
Wait, wait. How did you format the bootloader? No recovery should have this option! The only possible option to hard brick the P8000 is to pull out the USB cable in the exact moment when the SPFlash Tool writes it. So, can you elaborate a bit more about what done? I'm pretty sure you're missing something.
Click to expand...
Click to collapse
Hi,
I did something similar with my HTC Desire 616. I choose "Format All + Download" option with SP Flash Tool. The phone soft bricked. Later I tried "format whole flash (including bootloader)". It's still soft bricked...
Is there a way to revive my phone back??? :crying:
I had the same problem - but it is possible to set the phone to a special bootloader mode called META mode - see this video: https://www.youtube.com/watch?v=A3TmXtOA0IA
To do so you have to open the phone and disconnect the battery. You can find a howto easily on youtube.
Then set up everything to flash the phone (SP-Flashtool, scatter file, etc.) and push the volume down button while connecting the phone to the computer. This switches the phone to META mode, the computer can recognize the phone, installs the preloader driver and finally flashes the phone
Maybe you have to do the procedure twice because on the first connection only the preloader driver will be installed.
This worked for my P8000(B) which I treated with SP-Flash Tool and "Format All + download"
Be aware that you formatted the NVRAM and lost your IMEI's
FrauHofrat said:
P8000(B)
Click to expand...
Click to collapse
What the meaning of (B)? Just asking because i have (W)
Tecno spark 3 pro clone flash file mt6570 android 9.0 firmware
Hi
I need your assistance, please help me find the firmware for the above phone. I recently tried to flash it with a Spark 3 clone firmware i got online but it gives an error STATUS_PARTITION_NOT_FOUND and also i accidentally formatted the bootloader on SP Flash Tool so the phone is a brick, it can't charge, and it can't turn on. I have screenshots of the About section when the phone was working, which contains the phone's features model and build but on opening the back cover of the device, i realized its a clone phone and i cannot determine its real model to get the exact right flash file.
Thanks
Hello.
I own a Note II which lately seemed to have some problems.
In the last few months, it used to restart somewhat spontaneously (it seemed that it rebooted when its processor or RAM were too busy, but this wasn't a rule). During one night it probably rebooted and next morning I found it stuck on the first boot screen (the one with "Samsung Galaxy Note II").
When stuck on the boot screen, if I press the power button for a few seconds, it turns off. If closed, it gets to the boot screen and gets stuck there when I press the power button. When plugged to power, it gets stuck at the screen with the empty battery that has a loading icon in the middle.
I manage however to get it into recovery mode, however, in this situation, it can't be seen by the PC, unless I put it in adb sideload mode. When stuck on the logo screen, it is seen as mtp device.
In the recovery mode screen, there are many errors (can't/failed to mount /efs, /system, /cache, /cache/recovery/last_recovery, /data, /data/log/recoverylog.txt, /cache, /cache/recovery/log, last_log, last_install.
In Windows, the PC doesn't recognize the model, however, in a virtual machine that runs Linux, it is correctly seen as Note II when in adb sideload mode, but Linux is not able to mount its storage.
I have also deleted cache, tried Samsung Kies and Note II Toolkit.
What I would like to do is recover the data on it. Do you think it is possible, and if yes, how?
Thank you.
Sounds like a failed memory chip to me.
any answer now?
i want get ROM-not2-7100
Can you make it more clean and what do you want ? I want help to you but i dont understand what are you talking about So can you have acces to twrp ?
same problem
hi
i have same problem
i can go download mode but cant go recovery mode
using odin to flash twrp and cwm it said pass but problem exist
DarkMountain said:
Can you make it more clean and what do you want ? I want help to you but i dont understand what are you talking about So can you have acces to twrp ?
Click to expand...
Click to collapse
No, I don't have access. What I want is to recover the files on it, if possible.
This may be a problem with the power button. if you can go into download by pressing only the menu button + volume down is because the power button is always pressed.
eton3 said:
This may be a problem with the power button. if you can go into download by pressing only the menu button + volume down is because the power button is always pressed.
Click to expand...
Click to collapse
No, I need to use the power button too.
calindiaconu said:
No, I don't have access. What I want is to recover the files on it, if possible.
Click to expand...
Click to collapse
Sorry i think your partitions broked. I think you cant recover your data. There is has only one solution. Odin and Format....
My device too has pc cant detect my phone. I tried different cable without samsung usb drivers. Pc succesfully detected the my device.
By the way i installed lg usb driver because of someone's phone is lg and they need format.
I think there's no way to recover your data now.
BTW what recovery are you using?