Elephone p9000 black screen while flash - Elephone P9000 Questions & Answers

Hi,
ive tryed to root my phone, and did a big mistake.
While flashing the twrp recovery i sneezed and pulled out the usb cable...
Now i have a black screen and its not starting.
In my device manager there is a "MediaTek DA USB VCOM" now.
Is there a way you can help me?

Flash original Rom
Gesendet von meinem P9000 mit Tapatalk

skysauger said:
Flash original Rom
Gesendet von meinem P9000 mit Tapatalk
Click to expand...
Click to collapse
it doesnt start flashing the rom

Any error???
Newest Version oft SP flashtool??
Gesendet von meinem P9000 mit Tapatalk

JaNoxGER said:
it doesnt start flashing the rom
Click to expand...
Click to collapse
Because you're doing it wrong... You need to turn your phone off, press download then connect the USB cable.

Jonny said:
Because you're doing it wrong... You need to turn your phone off, press download then connect the USB cable.
Click to expand...
Click to collapse
My phone is off
there is no way to start it

skysauger said:
Any error???
Newest Version oft SP flashtool??
Gesendet von meinem P9000 mit Tapatalk
Click to expand...
Click to collapse
No, nothink. Just the driver in the device manager.
I've tryed v5.1604

JaNoxGER said:
My phone is off
there is no way to start it
Click to expand...
Click to collapse
There are several stages to the boot process, flashing a ROM only affects the last part of the boot process therefore all the other parts are in-tact. Press download, connect the USB and if you need to give it some help press the power button but you shouldn't need to.

Jonny said:
There are several stages to the boot process, flashing a ROM only affects the last part of the boot process therefore all the other parts are in-tact. Press download, connect the USB and if you need to give it some help press the power button but you shouldn't need to.
Click to expand...
Click to collapse
i tryed the normal flash progress today, and it was working direktly. propably the battery need to be emty and load while flashing after hard brick

JaNoxGER said:
i tryed the normal flash progress today, and it was working direktly. propably the battery need to be emty and load while flashing after hard brick
Click to expand...
Click to collapse
You didn't hard brick your device, you soft bricked it. Hence why flashing from SP Flash Tools worked. It is virtually impossible to actually hard brick a mediatek device unless you are really stupid and start messing round with partitions you shouldn't be touching.

Jonny said:
You didn't hard brick your device, you soft bricked it. Hence why flashing from SP Flash Tools worked. It is virtually impossible to actually hard brick a mediatek device unless you are really stupid and start messing round with partitions you shouldn't be touching.
Click to expand...
Click to collapse
OK, i though its a hard brick because i couldnt start it in recovery or any thing else.
But now i cant root it.
i tryed with the tut online. twrt and su1 su2 and su update, but root checker always called me not rooted

JaNoxGER said:
OK, i though its a hard brick because i couldnt start it in recovery or any thing else.
But now i cant root it.
i tryed with the tut online. twrt and su1 su2 and su update, but root checker always called me not rooted
Click to expand...
Click to collapse
Use these files instead >>> https://mega.nz/#!IlgxgDhS!r6_OpFYLVv07o025ecJ9rDul2db1KMsoWAlZbabWMxI
The tutorial on the Elephone forum uses an older TWRP version that doesn't work properly.

Jonny said:
Use these files instead >>> https://mega.nz/#!IlgxgDhS!r6_OpFYLVv07o025ecJ9rDul2db1KMsoWAlZbabWMxI
The tutorial on the Elephone forum uses an older TWRP version that doesn't work properly.
Click to expand...
Click to collapse
I will try that later

Jonny said:
Use these files instead >>> https://mega.nz/#!IlgxgDhS!r6_OpFYLVv07o025ecJ9rDul2db1KMsoWAlZbabWMxI
The tutorial on the Elephone forum uses an older TWRP version that doesn't work properly.
Click to expand...
Click to collapse
Now i have that error while flashing the twrp from you:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

JaNoxGER said:
Now i have that error while flashing the twrp from you:
Click to expand...
Click to collapse
I don't include a preloader file so thats not an issue with my files. Reflash stock 20160419 full ROM then try again.

Jonny said:
I don't include a preloader file so thats not an issue with my files. Reflash stock 20160419 full ROM then try again.
Click to expand...
Click to collapse
Can i flash the preloader without the full rom?

Jonny said:
I don't include a preloader file so thats not an issue with my files. Reflash stock 20160419 full ROM then try again.
Click to expand...
Click to collapse
I flashed the ROM from 20160419, but there is still the same preloader error.

Can anyone help me plz? I have the same situation. My phone is totaly dad. But battery should have 100%. So I have to wait for weeks?

JaNoxGER said:
Hi,
ive tryed to root my phone, and did a big mistake.
While flashing the twrp recovery i sneezed and pulled out the usb cable...
Now i have a black screen and its not starting.
In my device manager there is a "MediaTek DA USB VCOM" now.
Is there a way you can help me?
Click to expand...
Click to collapse
All you got to do is download sp_flash tool latest version, load the scatter file of rom, then simply go to options and then click to Connection, set usb speed to full speed, and Battery to w/o battery. Then make sure you have selected all the files needed to flash, next click the start button and connect your elephone while holding the volume + button. It will take a quite while but it will be successful. :laugh:

Related

[Q] XPERIA P update 6.2.A.0.400 problem

Hi all,
I've had this problem for a while now, but I've been ignoring it, untill now.
Everytime I try to download this JB update (6.2.A.0.400), everything goes smooth. But as soon as I try to install it, my phone shuts down and tries to install it. some sort of gift box pops up for a second and it boots again. Followed by the message that the update could not be installed.
I've searched google for a solution, but could not find one, so now I'm asking you.
TIA
-Alex
Dutch-Guy said:
Hi all,
I've had this problem for a while now, but I've been ignoring it, untill now.
Everytime I try to download this JB update (6.2.A.0.400), everything goes smooth. But as soon as I try to install it, my phone shuts down and tries to install it. some sort of gift box pops up for a second and it boots again. Followed by the message that the update could not be installed.
I've searched google for a solution, but could not find one, so now I'm asking you.
TIA
-Alex
Click to expand...
Click to collapse
Did you try installing it via flashtool?
DaRk-L0rD said:
Did you try installing it via flashtool?
Click to expand...
Click to collapse
Sorry for the late reaction. I can't update it with flashtool because my phone will only stay in flashmode for about 3 seconds...
Dutch-Guy said:
Sorry for the late reaction. I can't update it with flashtool because my phone will only stay in flashmode for about 3 seconds...
Click to expand...
Click to collapse
Waht is your windows version? It probably isn't the phone but the drives.
Does this happen with flashtool open?
ChikeD said:
Waht is your windows version? It probably isn't the phone but the drives.
Does this happen with flashtool open?
Click to expand...
Click to collapse
I just went back to 7. I installed the drivers from the flashtool folder. They should work right? It does happen with flashtool open.
Dutch-Guy said:
I just went back to 7. I installed the drivers from the flashtool folder. They should work right? It does happen with flashtool open.
Click to expand...
Click to collapse
Flashtool drivers work for me on windows 7, I think,, can't be sure because I have PC Companion installed and I had problems with them at the begging and tried many different solution and can't remember which of them fixed the problem.
Back then when I connected the device, flashmode I think, while looking at device manager, a device cam up with yellow icon then disapeared after a secong or two.
ChikeD said:
Flashtool drivers work for me on windows 7, I think,, can't be sure because I have PC Companion installed and I had problems with them at the begging and tried many different solution and can't remember which of them fixed the problem.
Back then when I connected the device, flashmode I think, while looking at device manager, a device cam up with yellow icon then disapeared after a secong or two.
Click to expand...
Click to collapse
In device manager, it comes up as SEMC Flash Device for a few seconds. What version were you on back then? I'm on 6.1.1.B.1.54
Dutch-Guy said:
In device manager, it comes up as SEMC Flash Device for a few seconds. What version were you on back then? I'm on 6.1.1.B.1.54
Click to expand...
Click to collapse
That version I think, but the problem was the drivers because when I was on Windows XP I didn't have this problem.
Did you flash all 3 drivers from flashtool?
ChikeD said:
That version I think, but the problem was the drivers because when I was on Windows XP I didn't have this problem.
Did you flash all 3 drivers from flashtool?
Click to expand...
Click to collapse
Yes i did. Right now I have managed to keep it in flash mode by first opening emma (the other flash tool) and connecting it in flash mode.
Dutch-Guy said:
Yes i did. Right now I have managed to keep it in flash mode by first opening emma (the other flash tool) and connecting it in flash mode.
Click to expand...
Click to collapse
So it's all good now?
BTW why do you chose to upgrade to 6.2.A.0.400 and not 6.2.A.1.100?
It's an awful version IMO.
ChikeD said:
So it's all good now?
BTW why do you chose to upgrade to 6.2.A.0.400 and not 6.2.A.1.100?
It's an awful version IMO.
Click to expand...
Click to collapse
No it's not yet working...
My phone just got a notification about version 400, I'll try to download version 100 then.
This is what I get when try to run it when my phone is already in flashmode.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Dutch-Guy said:
This is what I get when try to run it when my phone is already in flashmode.
Click to expand...
Click to collapse
Get you get the version for all SEMC flash drive files?
ChikeD said:
Get you get the version for all SEMC flash drive files?
Click to expand...
Click to collapse
I'm sorry, what do you mean?
Dutch-Guy said:
I'm sorry, what do you mean?
Click to expand...
Click to collapse
Right click the driver in device manager and select properties, you will see the diver version, if you click details you can see versions of each of the 3 files of the driver.
Do you have latest PC Ccmpanion installed? Maybe this can fix the issue or might even download 6.2.A.1.100.
ChikeD said:
Right click the driver in device manager and select properties, you will see the diver version, if you click details you can see versions of each of the 3 files of the driver.
Do you have latest PC Ccmpanion installed? Maybe this can fix the issue or might even download 6.2.A.1.100.
Click to expand...
Click to collapse
I've just downloaded the latest version. And it can indeed give me the versions you suggested. But lately I've been wanting to just root my phone and put CM on it.
Dutch-Guy said:
I've just downloaded the latest version. And it can indeed give me the versions you suggested. But lately I've been wanting to just root my phone and put CM on it.
Click to expand...
Click to collapse
I think it's the version I have.
To root the phone I don't think you need flash moed, just fastboot and usb debbugung, but you will need it if you want to reflash or upgrade the firmware.
Sorry I just looked and you do need flash mode, I remembered it was just the kernel but it's an ftf.
ChikeD said:
I think it's the version I have.
To root the phone I don't think you need flash moed, just fastboot and usb debbugung, but you will need it if you want to reflash or upgrade the firmware.
Sorry I just looked and you do need flash mode, I remembered it was just the kernel but it's an ftf.
Click to expand...
Click to collapse
Could it be that .100 is easier to root than the version I've got right now?
Dutch-Guy said:
Could it be that .100 is easier to root than the version I've got right now?
Click to expand...
Click to collapse
It is super easy to root now, just a doubleclick and 2 enters.
http://forum.xda-developers.com/showthread.php?t=2335992
ChikeD said:
It is super easy to root now, just a doubleclick and 2 enters.
http://forum.xda-developers.com/showthread.php?t=2335992
Click to expand...
Click to collapse
Oh wow, thats great news. Thanks a million for all your help. I'm going to sleep now but I'll try it out in the morning and I'll let you know how it went!

[Q] Bricked Xperia P [Can not flash stock rom]

Hi all, this is my first message, I always try to find a solution before posting but this time I'm really desperate...
Yesterday I was trying to set back the jelly bean stock rom to my "Xperia P" (I was on nemesis kernel + Enigma rom) device when suddenly flashtool crashed (still don't know why) while flashing, I was very worried because I knew that will probably lead into a brick.
And that happened, the phone is bricked now, and all the info I found talks about re-flashing the stock rom with flashtool but when I try it, it looks like flashtool does not recognise my device (drivers are installed), here I leave a screenshot of what happened when trying to give my P back to life:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The only thing I achieved to do is to set back the nemesis kernel to the phone, so now when I switch on the phone, the nemesis kernel logo is displayed but after that the screen goes black again. [so at least I know the fastboot mode is working]
Thanks for your time and many thanks in advance
Ok so is cwm working? If it is maybe you can try to flash enigma if the rom is on your phone and try and revert to stock.
Sent from my HONAMI THEMED Nexus 5 using Tapatalk 2
AndroidNoob69 said:
Ok so is cwm working? If it is maybe you can try to flash enigma if the rom is on your phone and try and revert to stock.
Sent from my HONAMI THEMED Nexus 5 using Tapatalk 2
Click to expand...
Click to collapse
Nope, CWM is not working... When the Nemesis Kernel logo is displayed I press the - volume button repeatedly but nothing happens... the screen just goes black.
klampenborg said:
Nope, CWM is not working... When the Nemesis Kernel logo is displayed I press the - volume button repeatedly but nothing happens... the screen just goes black.
Click to expand...
Click to collapse
Try volume up?
Sent from my HONAMI THEMED Nexus 5 using Tapatalk 2
AndroidNoob69 said:
Try volume up?
Sent from my HONAMI THEMED Nexus 5 using Tapatalk 2
Click to expand...
Click to collapse
Well... finally I achieved to access to CWM by installing another boot.img via fastboot, so there is a light hehe
From where I am now I don't know how to proceed, should I flash a ROM? If I should, how can I put it in the SD internal partition?
thanks man!
klampenborg said:
Well... finally I achieved to access to CWM by installing another boot.img via fastboot, so there is a light hehe
From where I am now I don't know how to proceed, should I flash a ROM? If I should, how can I put it in the SD internal partition?
thanks man!
Click to expand...
Click to collapse
Any rom that you can flash? Like on your phone now?
Sent from my HONAMI THEMED Nexus 5 using Tapatalk 2
AndroidNoob69 said:
Any rom that you can flash? Like on your phone now?
Sent from my HONAMI THEMED Nexus 5 using Tapatalk 2
Click to expand...
Click to collapse
I have no rom zip files on the SD card and the mount SD option of cwm menu seems that is not working (the device is not recognised in the windows device manager) maybe is an issue related to drivers? I thought that with pc companion installed the drivers were installed too...
klampenborg said:
I have no rom zip files on the SD card and the mount SD option of cwm menu seems that is not working (the device is not recognised in the windows device manager) maybe is an issue related to drivers? I thought that with pc companion installed the drivers were installed too...
Click to expand...
Click to collapse
Windows version?
Edit: i got to go to bed now cant help you for now.
Sent from my HONAMI THEMED Nexus 5 using Tapatalk 2
AndroidNoob69 said:
Windows version?
Edit: i got to go to bed now cant help you for now.
Sent from my HONAMI THEMED Nexus 5 using Tapatalk 2
Click to expand...
Click to collapse
XP, okay thank you for your help!
@klampenborg
Your the best choice would be to repair with PC Companion or SUS.
Once you are done build your own FTF file
http://forum.xda-developers.com/showthread.php?t=2188129
http://mytechencounters.wordpress.c...eate-an-ftf-file-of-your-xperia-ics-firmware/
Then you can flash whatever you want.
ChikeD said:
@klampenborg
Your the best choice would be to repair with PC Companion or SUS.
Once you are done build your own FTF file
http://forum.xda-developers.com/showthread.php?t=2188129
http://mytechencounters.wordpress.c...eate-an-ftf-file-of-your-xperia-ics-firmware/
Then you can flash whatever you want.
Click to expand...
Click to collapse
I've tried that too but SUS tells me that the phone has installed software not supported by sony and does not allow me to continue with the process.
klampenborg said:
I've tried that too but SUS tells me that the phone has installed software not supported by sony and does not allow me to continue with the process.
Click to expand...
Click to collapse
OK that's because the unlocked bootloader.
You can begin repair with PCC and when it ask you to connect the phone in flash mode, quit and build the FTF, than flash it with flashtool.
Well, finally I managed to flash my phone to 6.2.A.1.100 I don't know how but I did the same on another computer with windows 7 and it worked.
I finally flashed the ftf file with flashtool and worked like a charm, I've lost the root access but at least my phone is alive again
Thanks to all of you!
No prob man
Sent from my HONAMI THEMED Nexus 5 using Tapatalk 2

(ROM) OFFICIAL 4.4.2 V500 Update & Go back to 4.2.2!

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello All, this will update your V500 to 4.4.2, as is mine. This is based off the leaked 4.4.2 tot file.
Thanks AICJOFS for sending me the link to the leaked 4.4.2 official update tot.
Install the Drivers
Be sure usb debugging is ON!
Download the 4.4.2 .TOT file from here:
https://drive.google.com/file/d/0B34qnFE3O_HbX2t6elg5UXZFNEk/edit?usp=sharing
or here
http://www.androidfilehost.com/?fid=23329332407581518
(Thanks DrGravy for the mirrors!)
or here:
http://goo.gl/BIiHT0 and yes one more for good measure
http://goo.gl/QHrcKm
- I strongly suggest using a download manager like IDM to download this file
in case you have an error with your internet etc, It's 2GB+ in size
that way if you do, it'll continue to download this once you regain your internet connection. Trust me, it's worth it.
Download the .dll file you'll need last here:
https://drive.google.com/file/d/0B34qnFE3O_HbVnJ3WEEtUU12NFE/edit?usp=sharing
DO NOT EXTRACT the .tot file, leave it alone!
Download and install LGFlashTool from here: https://drive.google.com/file/d/0B34qnFE3O_HbcHM5LWFKcU84WjA/edit?usp=sharing
or here: http://goo.gl/qO1tqB
Download the MegalockDLL file for LGFlashTool here: https://drive.google.com/file/d/0B34qnFE3O_HbdkpkcmV6Z3ZpYmc/edit?usp=sharing
or here http://goo.gl/oUa37Q
After the LG Flash Tool is installed, do NOT launch it.
-Extract MegaLock.dll from the zip and copy MegaLock.dll to C:\LG\LGFlashTool, replacing the old MegaLock.dll file
Power off your Gpad, plug in the usb into your Gpad (not your computer yet)...
Holding vol Up & Down, plug it into your computer and you should now be in DOWNLOAD mode,
Wait for the drivers to finish installing, after they are, open Device Manager
Scroll down and click Ports, now Right click LGE AndroidNet USB Serial Port (COM2), then properties, then Advanced,
Now change the port # to 41, save and close out device manager
Now unplug your G Pad again from your computer.
Open LG Flash Tool
Select Manual Mode
Click on Add button on S/W field and load the V500 4.4.2 .TOT file
Then click the .DLL field and add the DLL file here. NOT the megalock.dll the First one you downloaded with the tot file.
NOW CLICK THAT YELLOW ARROW up top.
Wait for it to say READY. Once it says Ready plug in your G Pad again, in download mode.
Now As soon as you plug in your G Pad, In Download mode, it'll begin to flash, WAIT for it to say Pass in Blue, and it's done!
You now have a LG G Pad V500 with 4.4.2 Stock Kit Kat
Everything is working as it should be. Including ART!Quick Smooth and Zippy with no lag for me.
Your Welcome.
JESSICA
**** Yes you can have root with this, I used kingo because it was quick and easy ****
--P.S. Since people have been asking me via PM:
**---*** TO GO BACK TO 4.2.2 STOCK EVERYTHING yes including the bootloader, use my new thread HERE:
http://forum.xda-developers.com/showthread.php?p=51466048
Jessooca said:
Your Welcome.
JESSICA
Click to expand...
Click to collapse
Thanks a lot, I'll try it ASAP.
Awesome!!!!!!
Any chance for someone to make a flashable zip in recovery ?
Also Ashby changes to q remote?
Sent from my LG-V500 using Tapatalk
Wow....lemme try too. Fingers crossed.
Edit: can u post a screenshot?
Sent from my LG-V500 using XDA Premium 4 mobile app
Thanks a lot for the detailed tutorial!
But I think I'll stay with AOSP for now
I hope this can somehow help the GPE ROM, can it?
Sent from my iPhone using Tapatalk
yep, when sources will be released
Inviato dal mio Nexus 5 utilizzando Tapatalk
TOT link dead. :crying:
Edit: web page not available when i click download.
Great job!
Jessooca said:
Links have been updated, in the original post, everything is now available on my Google Drive to download.
https://drive.google.com/file/d/0B34qnFE3O_HbQVlMZnc5YlBRT3M/edit?usp=sharing
https://drive.google.com/file/d/0B34qnFE3O_HbVnJ3WEEtUU12NFE/edit?usp=sharing
https://drive.google.com/file/d/0B34qnFE3O_HbX2t6elg5UXZFNEk/edit?usp=sharing
https://drive.google.com/file/d/0B34qnFE3O_HbcHM5LWFKcU84WjA/edit?usp=sharing
https://drive.google.com/file/d/0B34qnFE3O_HbdkpkcmV6Z3ZpYmc/edit?usp=sharing
Click to expand...
Click to collapse
Can this be rooted? And is there a working recovery we can install? Thanks a lot.
Sent from my LG-V500 using XDA Premium 4 mobile app
jchenny said:
Can this be rooted? And is there a working recovery we can install? Thanks a lot.
Sent from my LG-V500 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Standard root works but it looks like it doesnt persist after cold reboot. Also (while no one has tried it) this is patched for the loki exploit so custom recovery is not possible (just like the G2).
nightanole said:
Standard root works but it looks like it doesnt persist after cold reboot. Also (while no one has tried it) this is patched for the loki exploit so custom recovery is not possible (just like the G2).
Click to expand...
Click to collapse
How did you get root?
As someone else mentioned, I believe this update breaks the Loki Bootloader exploit, meaning no more TWRP or custom kernels.
I'll look into this.. Maybe it's possible to install without updating Bootloaders through a custom recovery zip.
Great, thanks a lot! Could you please upload a system dump? I'm trying to extract the tot file in linux and I can't manage to do it.
Wonderful
Jessooca said:
For some reason, not sure why, but the pre existing Root method, didn't work, yet I used kingo and it's rooted, even after multiple reboots with no issues of any sort.
Click to expand...
Click to collapse
Outstanding job! What a breakthrough.
But I can't get root - even with Kingo. The app goes into a loop of downloading and waiting. This is with USB debugging enabled and the Pad connected as an MTP device. I also tried it connected with LG Software but got the same loop.
Never mind, the upgrade is wonderful.
id10terror said:
As someone else mentioned, I believe this update breaks the Loki Bootloader exploit, meaning no more TWRP or custom kernels.
I'll look into this.. Maybe it's possible to install without updating Bootloaders through a custom recovery zip.
Click to expand...
Click to collapse
please research the G2, Same thing happened with the G2, but once the source kernel was released they found a way to flash KitKat and keep their current custom recovery. I am sure it will be the same. One thing the G2 had going for it is you could go back to 4.2.2 at any time which works with Loki(as far as i know this is unconfrimed with the g pad). I am sure this will be the same.
But if you simply remove the recovery from the update it wont boot.
zahir32 said:
Outstanding job! What a breakthrough.
But I can't get root - even with Kingo. The app goes into a loop of downloading and waiting. This is with USB debugging enabled and the Pad connected as an MTP device. I also tried it connected with LG Software but got the same loop.
Never mind, the upgrade is wonderful.
Click to expand...
Click to collapse
Reboot an try again. I had the same problem. Now i have tried it again. Now it works. ROOTED.
But I dont get TWRP installed.
Miracast?
It has miracast?
Thanks
Perfect!
smoki3 said:
Reboot an try again. I had the same problem. Now i have tried it again. Now it works. ROOTED.
But I dont get TWRP installed.
Click to expand...
Click to collapse
Thank you! Worked fine after the reboot. Great help.
jsevi83 said:
Great, thanks a lot! Could you please upload a system dump? I'm trying to extract the tot file in linux and I can't manage to do it.
Click to expand...
Click to collapse
Don't have a windows computer around? This extracted it fine.
http://forum.xda-developers.com/showthread.php?t=2600575
Have any One found a possiblity to downgrade to 4.2
Gesendet von meinem HTC One mit Tapatalk

[Tutorial] Make any Gear S rootable

Hello everyone. This is my first tutorial with Gear S so I hope it will help someone.
First of all
I am not responsible for any damage done to you device​I saw in this Tutorial thread: http://forum.xda-developers.com/gear-s/development/definitive-guide-to-rooting-gear-s-t2973455, that some people have unsupported firmware versions and they can't root they'r device. It is not true. You can root your device, if you will follow this simple guide.
What do you need:
1) Gear S
2) Charging cradle with USB cable
3) PC running Windows (because windows is only OS I know XD)
4) Odin 3.09: https://drive.google.com/open?id=0B4xXHWEm81OleU0wckt0S2pjSU0
5) supported firmware downloaded from here: http://www.sammobile.com/firmwares/database/SM-R750/ (it is just on you which one do you pick, but it must be supported in the root thread)
6) Drivers: https://drive.google.com/open?id=0B4xXHWEm81OlT1ZBeXdHYXZqQTA
If you have everything downloaded you can proceed to the tutorial it self​Step by step firmware changing guide:
1) Unzip downloaded software and install drivers
- you should end with one .MD5 file and one .dll file (I am not sure, if the .dll is needed)
2) Open Odin 3.09
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- Here you have to Tick AP, click on AP and select your .MD5 file
-you should start to see something like this (wait until it says leave CS..)
- you can continue if you see this
3)Untick Auto reboot
4) Enable USB-Debugging on Gear S
- Settings -> Gear Info -> USB Debugging
5) Put your gear S into download mode
https://www.youtube.com/watch?feature=player_embedded&v=qwcf79m9ycw
- credits go to cipherswitch
6) Connect your gear S to PC
- you should see this
7) Click start and wait till it is done
- when it is done you will see this
8)Wait till Gear S reboot
- Now just look at the firmware page and there should be new software version
If you have an error
-repeat everything but with different firmware version
P.S.: Sorry if you can't see pictures, so if you have problem just look into attachment they are listed here
My tmobile gear is on a newer firmware. So do i just roll back to an earlier firmware then root?
Thanks
***firmware version R750TUVU1APC1
Sent from my SM-N930T using XDA-Developers mobile app
louforgiveno said:
My tmobile gear is on a newer firmware. So do i just roll back to an earlier firmware then root?
Thanks
***firmware version R750TUVU1APC1
Sent from my SM-N930T using XDA-Developers mobile app
Click to expand...
Click to collapse
I downloaded the exact same one from sammobile then I flashed the AOA7 root file from the root thread and it works fine. The software version will still be AOA7 but I think the baseband will be APC1 but mine is working flawlessly. Also you could still flash stock AOA7 first then root but theres no need as I've tested it.
i can't root my gearS R750XXU2BOK1_KTC ( korean) . Who will help me to root my gear ? i did look like that but it can't. please help me
vitdiesel said:
i can't root my gearS R750XXU2BOK1_KTC ( korean) . Who will help me to root my gear ? i did look like that but it can't. please help me
Click to expand...
Click to collapse
did u tried different supported rom?
Kubas_inko_CZ said:
did u tried different supported rom?
Click to expand...
Click to collapse
because my gear was from KTC carrier, so i am afriad to tried other room to lock sim.? if u know how i can root that, plz help me.
as long as i know, changing stock rom does not affect carrier, but if u are scared, dont try it (i would try it for sure), because u can go totally back by flashing your stock rom.
Do anyone have the root files still ?
Sent from my SM-N950U using Tapatalk
mr pnut said:
Do anyone have the root files still ?
Click to expand...
Click to collapse
I have the same question...
sonay705 said:
I have the same question...
Click to expand...
Click to collapse
As i do to, really in need of those files, i some o e find them give me a shout... thankx
Sent from my SM-N9300 using Tapatalk
sonay705 said:
I have the same question...
Click to expand...
Click to collapse
Alright guys i have the file rootfs.tar...
Give me a bit, i'll get it uploaded
Here's the root file....enjoy!
Hit the Thanks Buddy Button !
Lol
https://mega.nz/#!MYE1kSSS!PHy1-fa0Qdoy4lLVWDORcJ5CXqq8B_aBXXUiJx2C78w
louforgiveno said:
Here's the root file....enjoy!
Hit the Thanks Buddy Button !
Lol
https://mega.nz/#!MYE1kSSS!PHy1-fa0Qdoy4lLVWDORcJ5CXqq8B_aBXXUiJx2C78w
Click to expand...
Click to collapse
Thanks mate this will make the difference, flash with odin and push files trough adb right? Or is there a file explorer included. Thanks again most appreciated...
Sent from my SM-N9300 using Tapatalk
PTHugo said:
Thanks mate this will make the difference, flash with odin and push files trough adb right? Or is there a file explorer included. Thanks again most appreciated...
Click to expand...
Click to collapse
Sorry, sounds right...can't remember the steps off hand.
Inside the .tar is an image file, might need to be unpacked, sorry just don't remember the steps.
Just follow the guide and use this file.
Best of luck.
louforgiveno said:
Sorry, sounds right...can't remember the steps off hand.
Inside the .tar is an image file, might need to be unpacked, sorry just don't remember the steps.
Just follow the guide and use this file.
Best of luck.
Click to expand...
Click to collapse
Thanks again , i'll figure it out eventually, we always got stock to clean the mess when we **** the bed, [emoji4] can't thank you enough it's been long since someone played with this device but i just keep coming back to it, i really like it a lot... All the best, thanks once more [emoji4]
Sent from my SM-N9300 using Tapatalk
louforgiveno said:
Here's the root file....enjoy!
Hit the Thanks Buddy Button !
Lol
<url> ...
Click to expand...
Click to collapse
Which FW rooted?
sonay705 said:
Which FW rooted?
Click to expand...
Click to collapse
Good question.....all i know it was in a folder named latest created late in 2016.....not sure if that helps at all...
Maybe the info is somewhere in the "image" file...sorry been a long time since i used the files.....
louforgiveno said:
Good question.....all i know it was in a folder named latest created late in 2016.....not sure if that helps at all...
Maybe the info is somewhere in the "image" file...sorry been a long time since i used the files.....
Click to expand...
Click to collapse
Okay it is a custom binary but still write protected shows anther firmware version, now i miss something and coz the beginning of the thread was deleted i'm not quite sure what is i mean is rooted (at least i think it is coz the binary now shows custom), now the deal is there must be or should be some kind of file manager or su manager on the watch i already tryed to push using adb and fastboot but it doesn't work so how did you push tose? Was it by flashin some other thing with odin, please try to remember i realy am trying to get this thing available to other samsung's high end phones, i'm trying to get it working with any phone brand so i really need to get in the hart of the thing to make a few changes, i already (think) i got a way to do it, sorry to trouble you mate you already did someting awsome thanks
Sent from my SM-N9300 using Tapatalk
PTHugo said:
Okay it is a custom binary but still write protected shows anther firmware version, now i miss something and coz the beginning of the thread was deleted i'm not quite sure what is i mean is rooted (at least i think it is coz the binary now shows custom), now the deal is there must be or should be some kind of file manager or su manager on the watch i already tryed to push using adb and fastboot but it doesn't work so how did you push tose? Was it by flashin some other thing with odin, please try to remember i realy am trying to get this thing available to other samsung's high end phones, i'm trying to get it working with any phone brand so i really need to get in the hart of the thing to make a few changes, i already (think) i got a way to do it, sorry to trouble you mate you already did someting awsome thanks
Sent from my SM-N9300 using Tapatalk
Click to expand...
Click to collapse
I'll rack my brain to try to remember....but from what i do remember it wasn't like root for a phone.....no su app (tizen os) ...just able to execute admin commands via adb.
If you were to load android os well then su will probably be available.
I'll look back through my files, looking for any guides when i get a chance.
Sent from my SM-G950U using Tapatalk
louforgiveno said:
I'll rack my brain to try to remember....but from what i do remember it wasn't like root for a phone.....no su app (tizen os) ...just able to execute admin commands via adb.
If you were to load android os well then su will probably be available.
I'll look back through my files, looking for any guides when i get a chance.
Sent from my SM-G950U using Tapatalk
Click to expand...
Click to collapse
Thanks mate, i've still got trouble to get adb to list i eventry on download mode (we now that's only for odin) i read somewhere that some samsung devices do work that way (well i don't think they do coz download mode puts the device listening only) anyway coz we are always learning something i gave that a shot has we already knew nop it doesn't go, so thanks once more for your help it's very important and welcome, i'm very grateful for your effort...
Sent from my SM-N9300 using Tapatalk

Question Unbrick Device - Corrupted bootloader

Hi Team, I Need help with unbricking my device. I'm in a panic state. I had already unblocked my bootloader and downgraded to Oxygen OS 11.3 via MtkClient.
For some weird reason it stuck to bootloader animation and I flashed ROM files again via MTKClient, but it was still on the bootloader screen. Then I thought of flashing preloader files from the backup preloader files I saved before via MTKclient. Now it seems like I have bricked my device. Nothing is showing up.
This is my first post on this forum, Please help me out.
Thanks and apologies for breaking any forum rules.
It seems to be not charging ( I can't tell if it's charging when I'm using my regular charge adapter) and now it's not even showing up on MTKClient.
Hi, First question do you have a warranty?
Kabbutino said:
Hi, First question do you have a warranty?
Click to expand...
Click to collapse
No, this device issues issued for official work :-(
thecreat0rnew said:
Hi Team, I Need help with unbricking my device. I'm in a panic state. I had already unblocked my bootloader and downgraded to Oxygen OS 11.3 via MtkClient.
For some weird reason it stuck to bootloader animation and I flashed ROM files again via MTKClient, but it was still on the bootloader screen. Then I thought of flashing preloader files from the backup preloader files I saved before via MTKclient. Now it seems like I have bricked my device. Nothing is showing up.
This is my first post on this forum, Please help me out.
Thanks and apologies for breaking any forum rules.
Click to expand...
Click to collapse
PS: I also have backups of all partitions including the bootloader in a separate folder created via MTKClient. I hope the device is recoverable given its bootloader is unlocked but I'm worried that It's now not detected in MTKclient not sure if the charge is depleted and charming a device is not possible without valid bootloader???
thecreat0rnew said:
No, this device issues issued for official work :-(
Click to expand...
Click to collapse
Yeah, obviously
When you buy your phone?
thecreat0rnew said:
PS: I also have backups of all partitions including the bootloader in a separate folder created via MTKClient. I hope the device is recoverable given its bootloader is unlocked but I'm worried that It's now not detected in MTKclient not sure if the charge is depleted and charming a device is not possible without valid bootloader???
Click to expand...
Click to collapse
If you have a backup with mtkclient you can restore that
Kabbutino said:
If you have a backup with mtkclient you can restore that
Click to expand...
Click to collapse
But for some weird reason, MTKclient is unable to detect my device after the bootloader flash operation. Is there any further troubleshoot option to see battery percentage etc or some other operation?
thecreat0rnew said:
PS: I also have backups of all partitions including the bootloader in a separate folder created via MTKClient. I hope the device is recoverable given its bootloader is unlocked but I'm worried that It's now not detected in MTKclient not sure if the charge is depleted and charming a device is not possible without valid bootloader???
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Above are the files from Preloader backup operation from MTKclient. What file I should flash to fix preloader?
thecreat0rnew said:
But for some weird reason, MTKclient is unable to detect my device after the bootloader flash operation. Is there any further troubleshoot option to see battery percentage etc or some other operation?
Click to expand...
Click to collapse
Can you flash other backup of oos 11.3 and unlock the bootloader?
Kabbutino said:
Can you flash other backup of oos 11.3 and unlock the bootloader?
Click to expand...
Click to collapse
Again, I can but MTKclient doesn't detect my device anymore after pressing Volume +- Plus I don't thin flashing other partition backup would solve the issue cause all of this started to occur as I flashed preloader from the backup files
Can you send the log of mtkclient?
Kabbutino said:
Can you send the log of mtkclient?
Click to expand...
Click to collapse
There is nothing showing up on logs as well. Is it possible due to empty battery it's unable to go into bootrom mode? Below is the logs I was getting after flashing preloader and trying to launch MTKclient.
F
thecreat0rnew said:
There is nothing showing up on logs as well. Is it possible due to empty battery it's unable to go into bootrom mode? Below is the logs I was getting after flashing preloader and trying to launch MTKclient. View attachment 5878273
Click to expand...
Click to collapse
Why do you flash preloader?
And which os do you use?
Kabbutino said:
And which os do you use?
Click to expand...
Click to collapse
Oxygen OS 11.3, I thought the preloader is the issue where I was stuck in boot animation. I think the mobile was not charged enough and hence it got corrupted.
Is there any way to charge the device now?
Do you see the bootanimation of oneplus and the unlock bootloader message
Kabbutino said:
Do you see the bootanimation of oneplus and the unlock bootloader message
Click to expand...
Click to collapse
As of now, nothing is showing up. It's just a black screen.
I was able to get MTKClient to work after the one-plus animation screen.

Categories

Resources