Related
Hi forum,
I'm actually in hospital for about 6 weeks and after flashing a custom Rom I want to go back to the previius issue but go back
my samsung n7100 is'nt recognized by windows 8.1 update 1 and doesn't go to recovery mode. I tried to deinstall USB-drivers and did a new Installation of the drivers, but nothing Helms.
I cannnot install any cwm-Rom.
Please help because my smarty is the only connection to my wife and children.
P.s.: sorry for my Bad English. and i wrote this thread in my sickbed.
Thanks a Lot for your patience..
Hubs135 said:
Hi forum,
I'm actually in hospital for about 6 weeks and after flashing a custom Rom I want to go back to the previius issue but go back
my samsung n7100 is'nt recognized by windows 8.1 update 1 and doesn't go to recovery mode. I tried to deinstall USB-drivers and did a new Installation of the drivers, but nothing Helms.
I cannnot install any cwm-Rom.
Please help because my smarty is the only connection to my wife and children.
P.s.: sorry for my Bad English. and i wrote this thread in my sickbed.
Thanks a Lot for your patience..
Click to expand...
Click to collapse
Uninstall the drivers again, then Try using USBDeview and delete all the devices related to android and samsung... this will remove the possibility of any device driver not being reinstalled properly by windows...
USBDeview 32-bit
USBDeview 64-bit
After this restart the pc and try installing drivers and connect the phone to see if it works...
U can try reinstalling samsung kies.
Sent from Samsung Note 2 on Phantom Kitkat Rom via Tapatalk
Windows 8.1 update 1 also can't flash anything to my phone because of drivers. I had tried every driver mtp, Sammy etc.
Here are the latest Sammy if you want to try.
http://forum.xda-developers.com/showthread.php?t=961956
Sent from my GT-N7100 using Tapatalk 2
Hubs135 said:
Please help because my smarty is the only connection to my wife and children.
Click to expand...
Click to collapse
What's the issue with your current rom? If it's working fine don't play with it, if it's not then maybe we can fix the issue.
im using windows 8.1. working & able to flash 4.4.2 with Odin 3.0.9
try install PdaNet & KIES 3
I tried all things you wrote but without any success. At least I did a new installstion of windows 8.1 but also without success. I think if its ossible for me to come into recovery mode I can Flash cwm Version of rom from my sd Card. It seems the onlyest Way to Repair my smarty.
Any tricks to get recovery mode.
Hubs135 said:
I tried all things you wrote but without any success. At least I did a new installstion of windows 8.1 but also without success. I think if its ossible for me to come into recovery mode I can Flash cwm Version of rom from my sd Card. It seems the onlyest Way to Repair my smarty.
Any tricks to get recovery mode.
Click to expand...
Click to collapse
http://stackoverflow.com/questions/21246905/cant-connect-android-device-to-pc-on-windows-8
you might need google help
Sorry, but tried all things you wrote, but without success. I googled too, but all threads say to do it. via Odin or similar but my opiniion the onlyest Way to rescue my smarty is getting in the recovery mode again.
Is there any tricky to do.this?
Bricked???
No tricks. It seems i've bricked my smarty
Nobody any Idea?
Really Nobody any Idea to recscue my smarty.
Then I've lost 336,00€,
**** ....
Hubs135 said:
Really Nobody any Idea to recscue my smarty.
Then I've lost 336,00€,
**** ....
Click to expand...
Click to collapse
Well, what's actually wrong with it, other than Win 8.1.1 not seeing it? You haven't told anyone what problems you're having other than that. It could be just something simple that someone here can help you with; that doesn't mean you have to reflash it...
Bricked - yes or no? - briefing my problem
Briefing my problem for better understanding my problem:
1. i wanted to do clean installation of sammobile rom 4.4.2 by preparing my n7100 before flashing new costum rom by deleting previous rom via a script.
2. after doing this my smartphone isn't recognized by windows 8.1 Update 1 - 64 bit
3. I tried also windows 8.1, 8 and 7 without any success.
4. i'm not be able to flash new custom rom via odin
5. on sd-card i had a cwm of rom and a backup of previous rom version, too
6. i tried to get into recovery mode by pushing sound+, on-switch and home by pushing at the same time
7. i got always immediately into download mode or in bootloop since boot sound starts (it's difficult to reconstruct the exactly way, but i had the problem not to go into recovery mode mot time before. therefore i do it always by "rom manager" appfrom chainfire).
8. i'm not be able to flash new custom rom via recovery mode
9. then i tried all tricks by searching the prroblem by google but all methods didn' work
10.. i'm be able to load my smartphone and the led lights, too.
this is why i think about my n7100 is bricked.
please, please help me!
thanks a lot
So you're bootlooping?
Your best bet is to try to access it from an older version of Windows. Probably you have a bad driver somewhere and it's causing conflicts. I have similar issues from W8, but it's fine on older OS's.
If an older version of Windows can access the device, then you should be able to reflash it. I suggest trying to drop Dr Ketan a PM, he's very knowledgeable and helpful.
see item 3, please.
im on windows 8.1
just download the lastest Samsung Kies (Samsung Kies 3) and install it.
try this
Hubs135 said:
Briefing my problem for better understanding my problem:
1. i wanted to do clean installation of sammobile rom 4.4.2 by preparing my n7100 before flashing new costum rom by deleting previous rom via a script.
2. after doing this my smartphone isn't recognized by windows 8.1 Update 1 - 64 bit
3. I tried also windows 8.1, 8 and 7 without any success.
4. i'm not be able to flash new custom rom via odin
5. on sd-card i had a cwm of rom and a backup of previous rom version, too
6. i tried to get into recovery mode by pushing sound+, on-switch and home by pushing at the same time
7. i got always immediately into download mode or in bootloop since boot sound starts (it's difficult to reconstruct the exactly way, but i had the problem not to go into recovery mode mot time before. therefore i do it always by "rom manager" appfrom chainfire).
8. i'm not be able to flash new custom rom via recovery mode
9. then i tried all tricks by searching the prroblem by google but all methods didn' work
10.. i'm be able to load my smartphone and the led lights, too.
this is why i think about my n7100 is bricked.
please, please help me!
thanks a lot
Click to expand...
Click to collapse
may be your phone has lost root access,try connecting it to kies and use the phone recovery guide if connecting your phone to pc is problem try other usb cables try the thicker shorter ones..
SOLVED !!!
:laugh::good: dr.Kretan was right.. After coming home from hospital i was able to connect my smarty to my home pc and flash kitkat 4.4.2 (france edition by sammobile) via odin.
1000 thanks to all of you for helping to solve my problem :good::good::good:
but one question is open: it's still impossible for me to get into recovery mode i don't understand tihs.any idea?
Hello everybody,
i hope the xdadevs can help me with my problem.
Since two Days i try to recover my Nexus 7 form a bootloop.
A week ago i flashed Kali Nethunter 2.0 via TWRP on my Device (Nexus 7 2003 Wifi) - Everything worked fine till yesterday.
My device run out of energy so i loaded it and startet it shortly after that.
Then i regognized the bootloop. I tried to restart the device but it had no effect.
After that i tried to boot into the Recovery Mode with TWRP to restore my working backup. But it got stucked on the loading screen of TWRP too.
Now i tried to recover some images and fix the problem with some manuals which seemed promising. - no success
After a while i did something incredible stupid and locked my bootloader again (i wanted to try to lock and unlock it since some tools couldnt flash the stock rom).
The situation right now:
I cant boot up normaly: Stuck while "Google" is displayed
I cant boot in Recovery Mode (TWRP): Stuck on the blue TWRP Logo
If i try to use the Skipsoft Toolkit or something else it fails - or do i miss something
Recover the Stock rom by using the "flash-all.bat" fails because of this (pastebin. c0m/ie0dBv1D). I used the stock rom of Android 4.4.4(razor-ktu84p) because every other stockrom says this (pastebin. c0m/Dz31k8qu).
I wonder why the stock rom needs to get the bootloader unlocked... ive red so much about it that it just works out of the box..... am i doing something wrong ?
If i try to unlock again, the selection screen on the tablet shows up. I choose yes and hit the Power button. At the console the output <bootloader> erasing userdata" shows up and "freezes?!"... nothing happens afterwards.
Thats about it and this is where i am stuck. I would really appreciate if someone could help me ! I would even reward or spend some money on help.
I try to fix it meanwhile and update this post if something new happens.
I had to alternate the links because im a new member, im sorry for that !
Thanks in advanced and sorry for the spelling
did you try the nexus root toolkit ?
war your PC detecting (USB) the Nexus prior to this problem?
diehard2013 said:
did you try the nexus root toolkit ?
war your PC detecting (USB) the Nexus prior to this problem?
Click to expand...
Click to collapse
Yeah i tried it but it couldnt fix my problems. Returning to Stock Rom will always tell me that i need the bootloader unlocked... and i cant unlock it.
My PC and Linux Notebook where recognizing before it was bricked. Now it only gets detected in fastboot because it wont start anymore.
Hi there,
Proud owner of a new Pixel XL. Unlocked version. Tried rooting last night (i've rooted all devices i've owned and am not new to this). Followed the instructions to a "t". The device won't get past the white screen and dots leapfrogging each other. Now when going back to fastboot, device isn't recognised by ADB Fastboot etc...
Please help!!!!
My guide should be able to help you get back to the OS and then install root.
Keep in mind you may lose data if you don't remove the -w from the script mentioned in the guide.
http://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478
Did you unlock bootloader?
Then immediately try rooting?
That is one cause for bouncing dots.
You should: flash factory image, then boot into device before any flashing. Setup device until you are at the home screen and OS settled. Use a pattern or pin security. That is needed to make recovery work properly. You need to decrypt at recovery boot. No ask for pin? Then power off and boot TWRP again.
Follow directions in TWRP and SuperSU threads to a Capital "T"...
Versions:
Latest "Q" firmware
Boot TWRP RC1 img, then flash zip installer
Use SuperSU 2.79 SR1.
You'll have no bootloop. I found first rooted boot to take just a few minutes.
Just in case: update SDK platform tools if you haven't cos that screws people up for days too.
Thanks mate. But i get to step 9 and nothing happens. My device is no longer recognised
thanks mate, but the problem is that now the device is simply not recognised by my computer. I can't flash anything
I should clarify.
SDK is 100% up to date.
I am trying on both Windows 10 and Mac.
Device drivers worked fine prior to trying to root.
I'm really worried that i might have just bricked a $1.4k(aud) device
I unlocked my bootloader and got a bootloop when I tried to fastboot to root. Would not recognize the device either. I redownloaded SU 3 as suggested in the third post and it worked. Good Luck.
I used the fastboot to root method and did not install TWRP.
http://forum.xda-developers.com/pixel-xl/help/bootloop-t3498140
Thanks, Mike01680. trying now
When i go into sideload i can see the device listed on adb devices!
Okay. Booted into recovery, found my firmware for NMF26O. Downloaded and ADB Sideloaded it can once again boot. thanks for all of your help!!!
i own an asus zenfone 2 Ze551ml. i had installed lineage os based on android 14.1 official nightly version using twrp recovery.
everything was running fine untill i wanted to update the nightly version.
the update manager would crash whenever i tried to download the update, so i tried downloading the update manually and flashing it using twrp recovery.
i successfully flashed the zip file, but the device went into a boot loop after the install of the update.
i booted back into recovery and tried clearing cache and dalvik cache, but nothing happened.
later while trying to do the same again, i accidentally wiped system partition as well.
now, the device doesnt boot up and stays stuck on the asus boot logo. doesnt show the lineage boot animation as well.
cant boot into recovery mode using the volume button and power button.
i tried to install adb on my windows, but the device is not detected and it shows an error saying device not found.
installing device drivers manually and trying to install adb too didn't help.
someone please help me with this situation :crying:
thanks a lot in advance
If you have hard bricked your phone then this post has all of the information necessary to help you
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
plus some addition information I found on the web:
I gathered from the internet that Asus Flash tool will hang after it reloads the correct serial number. It thinks it is communicating with a phone that has SN 123456789ABC but then at some point the phone switches SN and Asus Flash Tool hangs.
You can get around this hang using several methods
1) restart computer after asus flash tool hangs
2) use second computer to load RAW image after asus flash tool hangs
3) Going into Windows Device Manager and disabling the Android bootloader device then re-enabling it (after asus flash tool hangs)
Click to expand...
Click to collapse
You can tell Asus flash tool is hanging when you run "fastboot devices" command and you see a device that is not serial number 123456789ABC
Answered this problem many times.
You should've powered off within twrp itself.
Waited 15 seconds after switch off, used hard buttons to get to bootloader.
Used giovix modder tool. Return to stock option in modder. Select boot and recovery.
Reunlock bootloader , flashed twrp 3.0.2M1. Root .then flashed 3.0.3.M4 or if possible ...
Power off in twrp itself
Used hard buttons to get to bootloader.
Reflashed new twrp in linos OP.
Reflashed linos or restored any back up
3.03.M4 twrp is in OP for lineage
Search related threads
Twrp bootloop
Phone keeps booting to twrp
So. Recently, I got CyanogenMod 13 on my Gpad. Everything was just fine. Then I installed the Magisk Manager, which, for some reason, disabled the root access on the device. When I uninstalled it, my recovery (TWRP) asked me, if I want to install SuperSU. I selected yes. And that's the moment when everything fcked up. After SuperSU installation, my tablet went into bootloop, and I wasnt't even able to enter recovery via button combination. I tried to flash the stock rom via LG Flash Tool, but failed miserably. I tried multiple stock roms, but the result is till the same: I can't access the Factory Reset via buttons, the system keeps rebooting, and even if it boots for few seconds, the touchscreen isn't responding. I even tried connecting mouse via USB otg, but no success. Is my tablet dead? Is there any chance of repairing it?
Thank you for your help.
EDIT: It's v500 European version.
Czechball said:
So. Recently, I got CyanogenMod 13 on my Gpad. Everything was just fine. Then I installed the Magisk Manager, which, for some reason, disabled the root access on the device. When I uninstalled it, my recovery (TWRP) asked me, if I want to install SuperSU. I selected yes. And that's the moment when everything fcked up. After SuperSU installation, my tablet went into bootloop, and I wasnt't even able to enter recovery via button combination. I tried to flash the stock rom via LG Flash Tool, but failed miserably. I tried multiple stock roms, but the result is till the same: I can't access the Factory Reset via buttons, the system keeps rebooting, and even if it boots for few seconds, the touchscreen isn't responding. I even tried connecting mouse via USB otg, but no success. Is my tablet dead? Is there any chance of repairing it?
Thank you for your help.
EDIT: It's v500 European version.
Click to expand...
Click to collapse
nope, it's not death (yet)... The buttoncombo to enter might be a problem, but keep trying. If really nothing goes, try connecting to your PC and open a commandline. Type : adb reboot recovery (preferably from a linuxbox). However, make sure you got a ROM, GApps and SU system 2.78 or 2.79 ready on the SD. Personally I recommend @adrianom AOSP 7.1.1, OpenGApps micro and SU 2.79 SR2'systemmode.
Cheers
dirlan2001 said:
nope, it's not death (yet)... The buttoncombo to enter might be a problem, but keep trying. If really nothing goes, try connecting to your PC and open a commandline. Type : adb reboot recovery (preferably from a linuxbox). However, make sure you got a ROM, GApps and SU system 2.78 or 2.79 ready on the SD. Personally I recommend @adrianom AOSP 7.1.1, OpenGApps micro and SU 2.79 SR2'systemmode.
Cheers
Click to expand...
Click to collapse
Thank you for your reply.
However:
I am not able to stay in the system.
I am not able to enter the recovery. (because of the brick)
I am not able to enter ADB, because there's just no way how. I have USB debugging disabled by default (because I tried to reset the system using LG Flash Tool) and I can't use ADB in the download mode.
Actually, download mode is the only thing that hasn't broke yet. I still hope that someone that has experienced similar problems help me.
But again, thanks for your (and the only) reply.
Czechball said:
Thank you for your reply.
However:
I am not able to stay in the system.
I am not able to enter the recovery. (because of the brick)
I am not able to enter ADB, because there's just no way how. I have USB debugging disabled by default (because I tried to reset the system using LG Flash Tool) and I can't use ADB in the download mode.
Actually, download mode is the only thing that hasn't broke yet. I still hope that someone that has experienced similar problems help me.
But again, thanks for your (and the only) reply.
Click to expand...
Click to collapse
If you can get into download, you could connect to a PC and start the LG-tools.Use that to restore to the original ROM and start allover again with latedt software (TWRP, ROM, SU)
Cheers