Related
Hi
I made a very stupid mistake
I used the tool to root my xoom wifi model
I used the tool in this thread
http://forum.xda-developers.com/showthread.php?t=1011196
I tried to post this issue in the thread but I did not have the permissions.
by mistake I used the root of the 3G model
I followed the steps and everything was ok
I tried the unroot and here is the deadly (hopefully not) mistake
the xoom stops and first screen and refuses to boot
Did I brick my device??
Is there a way to resolve this problem??
Thanks
Yes, you have bricked it. Fastboot won't work at this point, so your only option is probably to return it.
-Jim (who's on his 2nd xoom)
Sent from my Xoom using Tapatalk
nawialkair said:
Hi
I made a very stupid mistake
I used the tool to root my xoom wifi model
I used the tool in this thread
http://forum.xda-developers.com/showthread.php?t=1011196
I tried to post this issue in the thread but I did not have the permissions.
by mistake I used the root of the 3G model
I followed the steps and everything was ok
I tried the unroot and here is the deadly (hopefully not) mistake
the xoom stops and first screen and refuses to boot
Did I brick my device??
Is there a way to resolve this problem??
Thanks
Click to expand...
Click to collapse
what does the first screen say? failed boot image?
BeagleBoy said:
Yes, you have bricked it. Fastboot won't work at this point, so your only option is probably to return it.
-Jim (who's on his 2nd xoom)
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
That's the thing I did not want to hear but expected it.
============================================
znfrazier said:
what does the first screen say? failed boot image?
Click to expand...
Click to collapse
No
I am stuck at the motorola logo and the word dual core technology
When I press Volume up or down (fanrkly I could not get into that menu again) I get a list
it includes the following:
Fast Boot
If I choose it I get
Starting Fastboot protocol support
nawialkair said:
That's the thing I did not want to hear but expected it.
============================================
No
I am stuck at the motorola logo and the word dual core technology
When I press Volume up or down (fanrkly I could not get into that menu again) I get a list
it includes the following:
Fast Boot
If I choose it I get
Starting Fastboot protocol support
Click to expand...
Click to collapse
Can you see the xoom in /fastboot devices? See if you can access you xoom from the computer. I actually did the same thing and got mine in working order.
nawialkair said:
That's the thing I did not want to hear but expected it.
============================================
No
I am stuck at the motorola logo and the word dual core technology
When I press Volume up or down (fanrkly I could not get into that menu again) I get a list
it includes the following:
Fast Boot
If I choose it I get
Starting Fastboot protocol support
Click to expand...
Click to collapse
Try doing this real quick, the best that can happen is that you can turn this around. You may NOT in fact be bricked. I made the mistake of doing this also, but I figured it is just like when I was using the Danger SPL on the G1 and I had to at least find a way.
So, do this real quick if you know how.
1. Power on and press Vol - at the same time
2. Open a command prompt to your ADB file and type in fastboot oem unlock
3. If this lets you in (it may not) go through the regular procedure of pressing Vol -+-+
4. It will format and you should know if it is in fact bricked or not because it won't boot up.
5. ******
6. Profit???
Let us know how it goes.
znfrazier said:
Can you see the xoom in /fastboot devices? See if you can access you xoom from the computer. I actually did the same thing and got mine in working order.
Click to expand...
Click to collapse
Yes I can see it
Thank you
stevenege said:
Try doing this real quick, the best that can happen is that you can turn this around. You may NOT in fact be bricked. I made the mistake of doing this also, but I figured it is just like when I was using the Danger SPL on the G1 and I had to at least find a way.
So, do this real quick if you know how.
1. Power on and press Vol - at the same time
2. Open a command prompt to your ADB file and type in fastboot oem unlock
3. If this lets you in (it may not) go through the regular procedure of pressing Vol -+-+
4. It will format and you should know if it is in fact bricked or not because it won't boot up.
5. ******
6. Profit???
Let us know how it goes.
Click to expand...
Click to collapse
I did that
and it started the format
After the boot, it stopped at the same place
Motorola's Logo and Dual Core
What's next??
thanks
root using the instructions in this thread it should fix your problem
http://forum.xda-developers.com/showthread.php?t=1010568
nawialkair said:
Yes I can see it
Thank you
I did that
and it started the format
After the boot, it stopped at the same place
Motorola's Logo and Dual Core
What's next??
thanks
Click to expand...
Click to collapse
you should try flashing the boot.img used to root i believe its tiamat 1.1.6 and the system.img for wifi. i have the stock system.img if you need it. hopefully that would git ya to boot atleast. MAKE SURE THAT IT IS WIFI ONLY.
Go here and follow the second post I posted. This will help you do this without downloading the files because they are already there.
Give it a shot at least
stevenege said:
Go here and follow the second post I posted. This will help you do this without downloading the files because they are already there.
Give it a shot at least
Click to expand...
Click to collapse
did they fix the boot prob with the one click? i haven't tried it.
znfrazier said:
did they fix the boot prob with the one click? i haven't tried it.
Click to expand...
Click to collapse
Yes, it has all been fixed. There still seems to be an issue with SU rights until you download BusyBox and no clue why.
I have been testing the WiFi one constantly and have not had any major hickups.
stevenege said:
Yes, it has all been fixed. There still seems to be an issue with SU rights until you download BusyBox and no clue why.
I have been testing the WiFi one constantly and have not had any major hickups.
Click to expand...
Click to collapse
good good. ill have to check it out. i still need to try out the pimp my xoom. ill post over there haha. gotta stay on topic.
Thanks ALL
I flashed Tiamat 1.1.6 boot.img
the problem is that when using this command:
adb remount
I get
error: device not found
The xoom is defined in the device manager as
Android adb Interface
nawialkair said:
Thanks ALL
I flashed Tiamat 1.1.6 boot.img
the problem is that when using this command:
adb remount
I get
error: device not found
The xoom is defined in the device manager as
Android adb Interface
Click to expand...
Click to collapse
Sounds like you are probably bricked :-/
Can I get the stock boot image
I just want to try that last option
I flashed the stock img and system img
It works fine
Yaaaaa
Thanks very much
Thanks very much
nawialkair said:
I flashed the stock img and system img
It works fine
Yaaaaa
Thanks very much
Thanks very much
Click to expand...
Click to collapse
Told ya haha, save those files on your computer for next time. I keep them in close reach just incase something happens. if you have any other problems give me a holla. glad everything is working again.
I think I'm more screwed than OP because I was already unlocked and rooted. Then locked my wifi xoom with the 3g one click tool. Yes I know that was very stupid but I was wondering what are my options?
Take it back to Amazon?
Use the following method in this thread?
Wait for SBF?
Thank you your time and sorry if I hijacked this thread.
jarretf said:
I think I'm more screwed than OP because I was already unlocked and rooted. Then locked my wifi xoom with the 3g one click tool. Yes I know that was very stupid but I was wondering what are my options?
Take it back to Amazon?
Use the following method in this thread?
Wait for SBF?
Thank you your time and sorry if I hijacked this thread.
Click to expand...
Click to collapse
It relocked? Yikes... I don't trust those 1-click things. I need to know what's going on step by step. My first Xoom got bricked when I thought I had untainted OEM image files and relocked it. There's really no reason to relock a Wifi Xoom right now.
Anyway, if it relocked, you might have been in the same boat I was where the computer wouldn't recognize the Xoom in Fastboot mode or RSD mode. And I went and got it exchanged at that point.
Oh, if RSD Lite can't see your Xoom in RSD mode, you might be out of luck. SBF won't help if RSD Lite can't see your Xoom. BUT, if it does see it, it sounds like you can flash the 3G/4G SBF from Motorola/Verizon and to get sorta running, then use Fastboot to overwrite the boot and system partitions.
G'day guys,
I was trying to install a custom recovery after unlocking the bootloader and something horribly went wrong
during the install, phone seemed to hang, gave it a good amount of time to do it stuff but nothing happend.
Didn't think much of it as i thought i could just start again with the install, but had no joy. Then somehow in
my panic i have managed to lock the bootloader again really making it difficult to do anything.
As it stands at the moment, i can do the following with the phone.
Can get into the fastboot screen
Cannot get into recovery.
Will start normally and show the powered by android screen then will just sit there as if it was starting (which it doesn't)
I was using the following guide :http://forum.xda-developers.com/showthread.php?t=2788632 for the process.
I must also stress that this isn't the 1st time i have tried to root android phones and have successfully rooted my S2,S3 and note 2.
That being said i have totally rooted this OPO.
I have spent the last 3 days basically reading any thread in this forum with the hope of reversing this cockup
and have tried many but to no avail. Basically road blocked i think by the locked bootloader.
The only thing i haven't tried yet is using a computer with Win xp as Win 7 is a pain in the arse for drivers.
Any of you guys got some idea whether this fixable or should i just give up and bin it? I don't want too and would love to be able to get
it back up running but this has really done my head in.
Cheers
U can flash factory images from fastboot:http://forum.xda-developers.com/oneplus-one/orig-development/discussion-cyanogenmod-11s-t2840305
ashishv said:
U can flash factory images from fastboot:http://forum.xda-developers.com/oneplus-one/orig-development/discussion-cyanogenmod-11s-t2840305
Click to expand...
Click to collapse
Not with a locked bootloader.
Transmitted via Bacon
---------- Post added at 07:09 PM ---------- Previous post was at 07:07 PM ----------
Moatmonster said:
G'day guys,
I was trying to install a custom recovery after unlocking the bootloader and something horribly went wrong
during the install, phone seemed to hang, gave it a good amount of time to do it stuff but nothing happend.
Didn't think much of it as i thought i could just start again with the install, but had no joy. Then somehow in
my panic i have managed to lock the bootloader again really making it difficult to do anything.
As it stands at the moment, i can do the following with the phone.
Can get into the fastboot screen
Cannot get into recovery.
Will start normally and show the powered by android screen then will just sit there as if it was starting (which it doesn't)
I was using the following guide :http://forum.xda-developers.com/showthread.php?t=2788632 for the process.
I must also stress that this isn't the 1st time i have tried to root android phones and have successfully rooted my S2,S3 and note 2.
That being said i have totally rooted this OPO.
I have spent the last 3 days basically reading any thread in this forum with the hope of reversing this cockup
and have tried many but to no avail. Basically road blocked i think by the locked bootloader.
The only thing i haven't tried yet is using a computer with Win xp as Win 7 is a pain in the arse for drivers.
Any of you guys got some idea whether this fixable or should i just give up and bin it? I don't want too and would love to be able to get
it back up running but this has really done my head in.
Cheers
Click to expand...
Click to collapse
I'm assuming that all subsequent attempts to unlock the bootloader again (fastboot oem unlock) are failing?
Transmitted via Bacon
timmaaa said:
Not with a locked bootloader.
Transmitted via Bacon
---------- Post added at 07:09 PM ---------- Previous post was at 07:07 PM ----------
I'm assuming that all subsequent attempts to unlock the bootloader again (fastboot oem unlock) are failing?
Transmitted via Bacon
Click to expand...
Click to collapse
Yeah, thats right timmaaa, no joy at all in unlocking again.
It just hangs on the powered by android screen after hitting enter.
Moatmonster said:
Yeah, thats right timmaaa, no joy at all in unlocking again.
It just hangs on the powered by android screen after hitting enter.
Click to expand...
Click to collapse
Let me search for something that might help, leave it with me.
Transmitted via Bacon
Cheers mate.
What build of CM11S are/were you on?
Transmitted via Bacon
timmaaa said:
What build of CM11S are/were you on?
Transmitted via Bacon
Click to expand...
Click to collapse
Pretty sure it was 38R ?, i definitely updated just after i got the phone in early October.
Moatmonster said:
Pretty sure it was 38R ?, i definitely updated just after i got the phone in early October.
Click to expand...
Click to collapse
Ah, that's a shame, the method I was thinking of won't work since that update. This is it:
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
It relies on you being able to boot a recovery as opposed to actually flashing it, and then flashing a script with that recovery. I'm 99.9% sure that you can't do that since the 38R update though. It's worth a try, connect your phone in fastboot mode and try to boot a recovery (the following command assumes that you have 'openrecovery-twrp-2.8.1.0-bacon.img' in your fastboot folder).
Code:
fastboot boot openrecovery-twrp-2.8.1.0-bacon.img
Like I said, it probably won't work, but it's worth a shot.
Transmitted via Bacon
Will have a crack when i get home, thanks for your help.
No good mate as you said.
Moatmonster said:
No good mate as you said.
Click to expand...
Click to collapse
Bummer. @zephiK, do you have any ideas?
Transmitted via Bacon
Edit: After looking through some oneplus forums, looks like they have tried to issue out a patch for this issue. Have you tried this? I would try it out first and see if it helps. Again, the below one people were really bricked, hope it helps.
I haven't had to use this, and the thread is long, but a very good read. Please go to this thread. A lot of people were able to get their devices working again by using a few tools on windows machines xp win7 and win 8.1. Basically bricked device like the one you are looking at, then installing color OS somehow brought it back to life. The drivers are in chinese, but just clicking next gets them installed correctly. Mostly everyone there is in QHUSB_Bulk mode, not sure if you are or not, but worth a shot.
I have seen this come up many times as a question.. Probably needed a post of it's own...
Download this and move it to your ext-sd card (not in any folder) using htc file manager. Rename it to 0P6BIMG.zip
- https://www.androidfilehost.com/?fid=95916177934537454
Then reboot to bootloader and allow it to flash. This will give you back the latest TWRP. Boot back up and delete that zip off your sd card. IF you don't delete or rename it you won't be able to get to recovery via bootloader (it will keep trying to load that zip).
Then download this (doesn't matter to where-just remember where).
http://download.chainfire.eu/696/Sup...erSU-v2.46.zip
Reboot to TWRP manually and flash it. Bam... done.....
I accepted the OTA Lollipop update ( stupid ) and it broke root on me. I was S-off and unlocked. Did the above method and re-gained root
This works on 5.0.1
Thanks so much,
John
help!!
jjmstang said:
I accepted the OTA Lollipop update ( stupid ) and it broke root on me. I was S-off and unlocked. Did the above method and re-gained root
This works on 5.0.1
Thanks so much,
John
Click to expand...
Click to collapse
Hey so were you able to apply these steps using verizon m8 5.0.1 (lollipop), I really appreciate if you can get back to me ASAP. thanks :good:
viscocho13 said:
Hey so were you able to apply these steps using verizon m8 5.0.1 (lollipop), I really appreciate if you can get back to me ASAP. thanks :good:
Click to expand...
Click to collapse
Yes..that's what I wrote this for. Need to be s-off though
need s-off
dottat said:
Yes..that's what I wrote this for. Need to be s-off though
Click to expand...
Click to collapse
I looked for methods to s-off and I can't find the appropiate method, can you please help here! thanks in advance... :laugh:
viscocho13 said:
I looked for methods to s-off and I can't find the appropiate method, can you please help here! thanks in advance... [emoji23]
Click to expand...
Click to collapse
If on lollipop your only option right now is to have someone with a Java card do it for you.
Thank you so much for posting this. I've been looking for it endlessly.
I'm not all that experienced with flashing and I think I made a mistake somewhere.
I downloaded the first file, renamed it as specified, and placed it on the highest level of my external SD card. I rebooted using power + vol down and let it do its thing with the vertical loading bar. I suppose that means it flashed the file.
Then I rebooted, deleted the first file, and put the second file on the highest level of the external SD card. I rebooted again, selected "recovery", and was taken to the stock recovery, not TWRP.
Disregard this I goofed.
Sent from my HTC6525LVW using Tapatalk
PiperCub49 said:
Thank you so much for posting this. I've been looking for it endlessly.
I'm not all that experienced with flashing and I think I made a mistake somewhere.
I downloaded the first file, renamed it as specified, and placed it on the highest level of my external SD card. I rebooted using power + vol down and let it do its thing with the vertical loading bar. I suppose that means it flashed the file.
Then I rebooted, deleted the first file, and put the second file on the highest level of the external SD card. I rebooted again, selected "recovery", and was taken to the stock recovery, not TWRP.
Click to expand...
Click to collapse
You usually have to confirm flashing the zip. Can you verify it asks you to flash zip 1?
I'm not getting a confirmation message. Hmmm...
---------- Post added at 03:59 AM ---------- Previous post was at 03:12 AM ----------
When I reboot into the bootloader, I immediately get a message saying that it's loading 0P6BIMG.zip. There is a loading bar. Once the loading finishes, I get a message saying to press power to reboot, which I do. I plug my phone in and put the second file on the SD card. When I reboot into the bootloader, I select "Recovery" and it loads the stock recovery.
PiperCub49 said:
I'm not getting a confirmation message. Hmmm...
---------- Post added at 03:59 AM ---------- Previous post was at 03:12 AM ----------
When I reboot into the bootloader, I immediately get a message saying that it's loading 0P6BIMG.zip. There is a loading bar. Once the loading finishes, I get a message saying to press power to reboot, which I do. I plug my phone in and put the second file on the SD card. When I reboot into the bootloader, I select "Recovery" and it loads the stock recovery.
Click to expand...
Click to collapse
If your fastboot is working on your PC put the phone in fastboot mode.
Fastboot oem rebootRUU
Fastboot flash zip nameofzip.zip
Fastboot reboot-bootloader
Now try to boot to recovery
dottat said:
If your fastboot is working on your PC put the phone in fastboot mode.
Fastboot oem rebootRUU
Fastboot flash zip nameofzip.zip
Fastboot reboot-bootloader
Now try to boot to recovery
Click to expand...
Click to collapse
First of all, I wanted to thank you for your help with all of this. I really appreciate it.
I'm getting somewhere, but I'm not there yet. When I enter the 'fastboot flash zip nameofzip.zip' command, I get stuck at '<waiting for device>'. I've waited for over a half hour on a computer with a USB 3.0 port, and then the same on another computer with a 2.0 port. It's stuck there. I'm doing some research to see if I can find what is causing it to get stuck here.
PiperCub49 said:
First of all, I wanted to thank you for your help with all of this. I really appreciate it.
I'm getting somewhere, but I'm not there yet. When I enter the 'fastboot flash zip nameofzip.zip' command, I get stuck at '<waiting for device>'. I've waited for over a half hour on a computer with a USB 3.0 port, and then the same on another computer with a 2.0 port. It's stuck there. I'm doing some research to see if I can find what is causing it to get stuck here.
Click to expand...
Click to collapse
I'm thinking you should do two things. First unplug and reply your usb cable while it's waiting. Secondly check device manager and make sure it shows the correct driver for your phone is installed when your phone is in ruu mode. Each mode loads its own driver instance.
I did some more work and ton more research and took another couple steps forward. I watched a video of some guy flashing an RUU and noticed the prompt asking him to confirm flashing the zip, which I'm not getting. The process should be simple.
Before I go any further, will this method work with a locked bootloader? I'm s-off, but have a locked bootloader. If it won't work with a locked bootloader, I'm out of luck since there's really no way of unlocking the bootloader on the Verizon m8, right?
PiperCub49 said:
I did some more work and ton more research and took another couple steps forward. I watched a video of some guy flashing an RUU and noticed the prompt asking him to confirm flashing the zip, which I'm not getting. The process should be simple.
Before I go any further, will this method work with a locked bootloader? I'm s-off, but have a locked bootloader. If it won't work with a locked bootloader, I'm out of luck since there's really no way of unlocking the bootloader on the Verizon m8, right?
Click to expand...
Click to collapse
Install team viewer on your PC and shoot me the login info via pm and a good time later tonight to catch up and resolve this.
First thing I'm doing is unlocking that boot loader which should not be locked.
dottat said:
If on lollipop your only option right now is to have someone with a Java card do it for you.
Click to expand...
Click to collapse
I had spoken to scotty1223 about me getting an M9 and having him do the Java card trick but it looks like I may only get the M8 now.... The same card and process works ?
scotty1223 and I live in the same town (I think) or very, very close.
hallstevenson said:
I had spoken to scotty1223 about me getting an M9 and having him do the Java card trick but it looks like I may only get the M8 now.... The same card and process works ?
scotty1223 and I live in the same town (I think) or very, very close.
Click to expand...
Click to collapse
Yep. Works the same. We have a couple users too that have Java cards myself included. Scotty1223 will take fine care of you.
Verizon htc one m8 lollipop
Hi there, I'm stuck with the verizon htc one m8 on lollipop after taking the update without going s-off. Is there any way that someone can help me out with a Java card?
Thanks in advance!
emineh17 said:
Hi there, I'm stuck with the verizon htc one m8 on lollipop after taking the update without going s-off. Is there any way that someone can help me out with a Java card?
Thanks in advance!
Click to expand...
Click to collapse
Pm me and I will see who is closest to you
Root and S-off Verizon M8 5.0.1
Hello everyone,
I am quite new to this and although this is all a bit overwhelming, I appreciate everything I'm learning. I'm trying to get my Verizon M8 to work on gsm so that I can use a metro pcs sim. I'm running 5.0.1 and can't seem to find a way to root my phone and get s-off to even begin the process. Any pointers?
Hi all, did anyone build a recovery? I would do it but I haven't got a computer that runs Linux and I am not firm with it at all.
Edit: I couldn`t use any method that I found to create a custom recovery, is there anyone with more success?
Also I could not use SP-Flash tool to make a backup, did anyone succeed and how?
Thanks
Sent from my HTC One A9 using XDA-Developers mobile app
new device ordered hopefully we see some development in this section soon =)
i also hope but i think this was not the interessted phone for developper...
Is there nobody to do this recovery?
Brainwasher34 said:
Is there nobody to do this recovery?
Click to expand...
Click to collapse
We gotta wait
If anybody cares about this and is willing to test some blind builds of TWRP, let me know (by replying here).
Captain_Throwback said:
If anybody cares about this and is willing to test some blind builds of TWRP, let me know (by replying here).
Click to expand...
Click to collapse
I am interested in testing some builds of twrp on my a9s, are your offer still available?
Greetings.
patrixs94 said:
I am interested in testing some builds of twrp on my a9s, are your offer still available?
Greetings.
Click to expand...
Click to collapse
Well, a month has passed, and I've forgotten everything I knew about this device, but I'll give it a shot when I have a chance. Stay tuned.
EDIT: It seems a month ago I built a test recovery for this device, but was waiting for a response before posting it. So @patrixs94 I'm attaching it here. Give it a try and let me know if it boots, and if so, I'll need a recovery log from it.
Ok, I will test it. Have one question - is it safe? In case of bootloop occurs, do you have any idea how to exit it? Can't find any RUU in web - that was the way I ever exit it, and by this way I was restoring official software. Is there any another way?
Captain_Throwback said:
Well, a month has passed, and I've forgotten everything I knew about this device, but I'll give it a shot when I have a chance. Stay tuned.
EDIT: It seems a month ago I built a test recovery for this device, but was waiting for a response before posting it. So @patrixs94 I'm attaching it here. Give it a try and let me know if it boots, and if so, I'll need a recovery log from it.
Click to expand...
Click to collapse
---------- Post added at 01:19 PM ---------- Previous post was at 12:56 PM ----------
Ok, I founded one, but it does not fit to my mid/ cid . And I dont have s-off :/
patrixs94 said:
Ok, I will test it. Have one question - is it safe? In case of bootloop occurs, do you have any idea how to exit it? Can't find any RUU in web - that was the way I ever exit it, and by this way I was restoring official software. Is there any another way?
Click to expand...
Click to collapse
patrixs94 said:
Ok, I will test it. Have one question - is it safe? In case of bootloop occurs, do you have any idea how to exit it? Can't find any RUU in web - that was the way I ever exit it, and by this way I was restoring official software. Is there any another way?
---------- Post added at 01:19 PM ---------- Previous post was at 12:56 PM ----------
Ok, I founded one, but it does not fit to my mid/ cid . And I dont have s-off :/
Click to expand...
Click to collapse
Flashing recovery shouldn't bootloop your device. Recovery is an entirely separate partition. You can try using "fastboot boot recovery.img" to see if that works, as that won't change anything on the device, but not all devices support it.
Honestly though, if you're not comfortable enough to test this, then there's no reason for me to work on this. Like I said, I know next to nothing about this device, so I need someone that can help me debug and provide logs, etc. Otherwise this exercise is futile.
Tested
Hi,
thank you, it´s great you are working on TWRP for this phone! I have tried to use it. After download it says booting on notebook and Start downloading on phone:
C:\fastboot\ fastboot boot recovery.img
downloading `boot.img`......
OKAY (1.453s)
booting...
After hard restart the phone works again.
Does it helps you?
T.
Captain_Throwback said:
Flashing recovery shouldn't bootloop your device. Recovery is an entirely separate partition. You can try using "fastboot boot recovery.img" to see if that works, as that won't change anything on the device, but not all devices support it.
Honestly though, if you're not comfortable enough to test this, then there's no reason for me to work on this. Like I said, I know next to nothing about this device, so I need someone that can help me debug and provide logs, etc. Otherwise this exercise is futile.
Click to expand...
Click to collapse
vejda said:
Hi,
thank you, it´s great you are working on TWRP for this phone! I have tried to use it. After download it says booting on notebook and Start downloading on phone:
C:\fastboot\ fastboot boot recovery.img
downloading `boot.img`......
OKAY (1.453s)
booting...
After hard restart the phone works again.
Does it helps you?
T.
Click to expand...
Click to collapse
All that tells me is that your device doesn't support fastboot boot. So you'll need to flash it to test whether it works or not.
Code:
fastboot flash recovery recovery.img
Thx. Flashed, after booting to recovery mode there is start screen, but I am not able to swipe to unlock it. Where can I find the log? Is it something like db.fatal.dbg?
Captain_Throwback said:
All that tells me is that your device doesn't support fastboot boot. So you'll need to flash it to test whether it works or not.
Code:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
vejda said:
Thx. Flashed, after booting to recovery mode there is start screen, but I am not able to swipe to unlock it. Where can I find the log? Is it something like db.fatal.dbg?
Click to expand...
Click to collapse
/tmp/recovery.log
Is adb working? If so, you can adb pull the above file. Then I can at least see how much is working (besides touch being broken).
Yes, ADB works, but the file doesn´t exist (with the way /tmp/recovery.log). Only general bugreport, attached.
Captain_Throwback said:
/tmp/recovery.log
Is adb working? If so, you can adb pull the above file. Then I can at least see how much is working (besides touch being broken).
Click to expand...
Click to collapse
vejda said:
Yes, ADB works, but the file doesn´t exist (with the way /tmp/recovery.log). Only general bugreport, attached.
Click to expand...
Click to collapse
The recovery log has to exist while in TWRP.
ADB doesn´t run while TWRP, screen attached.
Captain_Throwback said:
The recovery log has to exist while in TWRP.
Click to expand...
Click to collapse
vejda said:
ADB doesn´t run while TWRP, screen attached.
Click to expand...
Click to collapse
That error is on the computer side, not on the device. Fix your adb on your computer and then try adb in TWRP again.
Ok, thx. I am not expirienced user of it, but try to solve it Where are all the others? Hey!!
Captain_Throwback said:
That error is on the computer side, not on the device. Fix your adb on your computer and then try adb in TWRP again.
Click to expand...
Click to collapse
Here it is!
Here is the log, I was using old ADB.
Captain_Throwback said:
That error is on the computer side, not on the device. Fix your adb on your computer and then try adb in TWRP again.
Click to expand...
Click to collapse
I installed Osmos Os 7.1.1 thru TWRP and when I did that I then went and flashed Aroma installer( probably not the best idea) and installed pretty much all the apps, which was stupid. Now I don't have root( and can't reroot via kingroot, it fails every time).
When I tried to get back into recovery I get the sleeping Android with the exclamation mark with the "No Command".
I just want to get back into recovery so I can restore my last backup.
Any help would be greatly appreciated!
Excavator2015 said:
I installed Osmos Os 7.1.1 thru TWRP and when I did that I then went and flashed Aroma installer( probably not the best idea) and installed pretty much all the apps, which was stupid. Now I don't have root( and can't reroot via kingroot, it fails every time).
When I tried to get back into recovery I get the sleeping Android with the exclamation mark with the "No Command".
I just want to get back into recovery so I can restore my last backup.
Any help would be greatly appreciated!
Click to expand...
Click to collapse
Can you get into download mode? If you can do that, ill upload the files you need to get your phone to a rooted functional state.
Yes I can , but, when I go into download mode on the while on the computer, it doesn't read download mode and that the drivers weren't installed correctly it detects that something was connected but goes straight to the drivers weren't installed correctly.... I feel like there's no hope with this phone, I'm stuck on a 7.1.1 rom with no root, no sim card detection and no recovery. Ugh!If you think you can get me into a rooted state, then awesome!
Shadow Assassin said:
Can you get into download mode? If you can do that, ill upload the files you need to get your phone to a rooted functional state.
Click to expand...
Click to collapse
Thank you man, that would be greatly appreciated if you could send those files, just at a loss right now. I was actually looking at phones to buy if I couldn't get this fixed! But if you might have a solution then awesome, that would save me some money!
Excavator2015 said:
Yes I can , but, when I go into download mode on the while on the computer, it doesn't read download mode and that the drivers weren't installed correctly it detects that something was connected but goes straight to the drivers weren't installed correctly.... I feel like there's no hope with this phone, I'm stuck on a 7.1.1 rom with no root, no sim card detection and no recovery. Ugh!If you think you can get me into a rooted state, then awesome!
Click to expand...
Click to collapse
Your not stuck, its a soft brick, i once had that same driver problem. Give me some time to compile everything into a single zip for you to download with instructions. To fix your driver issue, ill include the lg g3 driver kit for you to install, it may still give a driver error, but youll just have to manually assign them and ill help you with that if it comes up.
Ok man, thanks, now what I didn't mention was that I can still boot up into Osmos Os, I just don't have recovery root or radio...It's like when I flashed Aroma and installed all those apps, it broke my recovery and root...I don't understand it. So is that still classified as a soft brick? Just can't do anything with trying to restore my last backup, which I still have in my TWRP folder, but with no recovery I can't restore it, along with the root issue...I mean I tried to reroot with Kingoroot and king root, but nothing. I'm hoping what you are providing me with will get me back up and running. Thank you again man. I do have ADB and fastboot working, just can't make things work in dl mode.
Excavator2015 said:
Ok man, thanks, now what I didn't mention was that I can still boot up into Osmos Os, I just don't have recovery root or radio...It's like when I flashed Aroma and installed all those apps, it broke my recovery and root...I don't understand it. So is that still classified as a soft brick? Just can't do anything with trying to restore my last backup, which I still have in my TWRP folder, but with no recovery I can't restore it, along with the root issue...I mean I tried to reroot with Kingoroot and king root, but nothing. I'm hoping what you are providing me with will get me back up and running. Thank you again man. I do have ADB and fastboot working, just can't make things work in dl mode.
Click to expand...
Click to collapse
Yea, as long you can get into download mode, then its only a soft brick. The Stump Root apps is a collection of exploits and when in doubt it can sometimes use a brute force attack to gain root. Its how i rerooted my g3 after it got corrupt.
Ok cool, so is it different than the mobile version? Because I tried the mobile version and it instantly popped up with it saying that it can't root my phone.
Excavator2015 said:
Ok cool, so is it different than the mobile version? Because I tried the mobile version and it instantly popped up with it saying that it can't root my phone.
Click to expand...
Click to collapse
Ok, then your phone is patched. So youll have to do the full restore and root. I sent the link in a PM
PM me if you need more help or if its successful or fails.
Never got the pm.
Excavator2015 said:
Never got the pm.
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B4FtiSFGCyvHaUlJSGREYm5RRnc/view?usp=drivesdk
When the zip is done downloading, youll extract the folders and files and run through the guide I put in there.
Ok. Thank you, now on the computer, I can't login to XDA because my wife is signed into Google plus and it's her computer. I'll take the zip and transfer it to her desktop.
Alright man, I'm copying the zip over to the computer. Are you going to be on for a while in case I need you?
When I went into download mode the computer still didn't recognize it. It told me the drivers weren't installed successfully. When I unplugged the phone from the computer they automatically installed correctly.
Now when I went in to look at the device connected, there was a yellow exclamation mark, and it said that the drivers weren't installed correctly and it gave me a "Code(10)device cannot start". I'm so lost right now, please help me out man..Lol can it be done thru ADB? I know that I don't have download mode working so fastboot is out of the question. Ugh!
Excavator2015 said:
When I went into download mode the computer still didn't recognize it. It told me the drivers weren't installed successfully. When I unplugged the phone from the computer they automatically installed correctly.
Now when I went in to look at the device connected, there was a yellow exclamation mark, and it said that the drivers weren't installed correctly and it gave me a "Code(10)device cannot start". I'm so lost right now, please help me out man..Lol can it be done thru ADB? I know that I don't have download mode working so fastboot is out of the question. Ugh!
Click to expand...
Click to collapse
Go to your device manager and uninstall all lg drivers then run the installation of the multidriver pack i included.
---------- Post added at 07:24 PM ---------- Previous post was at 07:12 PM ----------
Excavator2015 said:
When I went into download mode the computer still didn't recognize it. It told me the drivers weren't installed successfully. When I unplugged the phone from the computer they automatically installed correctly.
Now when I went in to look at the device connected, there was a yellow exclamation mark, and it said that the drivers weren't installed correctly and it gave me a "Code(10)device cannot start". I'm so lost right now, please help me out man..Lol can it be done thru ADB? I know that I don't have download mode working so fastboot is out of the question. Ugh!
Click to expand...
Click to collapse
Now if reinstalling all the drivers doesnt work, Ill set up a guide to do a full cleaning of lg drivers and fresh install. The error codes your getting are apparently just outdated or corrupt drivers, so its not a lost cause, just a bump in the road that can be fixed.
Got it fixed!!! Back to stock rooted. Now I'm flashing super su. Now I can do that thru flashify right? You left out one major detail tho...I had to check Mark board, in LG flash tool...I was stuck in the factory reset 2 screen for like 2 hours until I finally had the computer recognize download mode again. But hey, that did do the trick!! Thank you very much man!!
Excavator2015 said:
Got it fixed!!! Back to stock rooted. Now I'm flashing super su. Now I can do that thru flashify right? You left out one major detail tho...I had to check Mark board, in LG flash tool...I was stuck in the factory reset 2 screen for like 2 hours until I finally had the computer recognize download mode again. But hey, that did do the trick!! Thank you very much man!!
Click to expand...
Click to collapse
Crap, sorry for the two hour headache but glad to hear you got it running. The guide for the restore was from another forum but its instructions are on a bunch of other sites and i forgot i had the same problem you did trying to figure out why it wouldnt recognize. So idk really know where to throw credit to, I just tried to compile everything to together for ya.
---------- Post added at 01:14 AM ---------- Previous post was at 01:12 AM ----------
Shadow Assassin said:
Crap, sorry for the two hour headache but glad to hear you got it running. The guide for the restore was from another forum but its instructions are on a bunch of other sites and i forgot i had the same problem you did trying to figure out why it wouldnt recognize. So idk really know where to throw credit to, I just tried to compile everything to together for ya.
Click to expand...
Click to collapse
And i would suggest using flashfire. Flashify has been a headache on the g3 for me but no mattef what, make a backup first.
Hey, no problem man, you really helped out! And now because of that tutorial and the detail you put in, I have recovery and root again! It actually was really easy initially!
I had someone else help out before you, and we spent hours upon hours of trial and error to try and get me back to this state, now he suggested lg root tool but I told him I couldn't get DL mode working as well. So all in all, if it wasn't for people on this site helping each other out, none of us would have what we have now , or fix things on their devices.
Thanks again!:good:
My name is Ty by the way, what's yours?
Excavator2015 said:
Hey, no problem man, you really helped out! And now because of that tutorial and the detail you put in, I have recovery and root again! It actually was really easy initially!
I had someone else help out before you, and we spent hours upon hours of trial and error to try and get me back to this state, now he suggested lg root tool but I told him I couldn't get DL mode working as well. So all in all, if it wasn't for people on this site helping each other out, none of us would have what we have now , or fix things on their devices.
Thanks again!:good:
My name is Ty by the way, what's yours?
Click to expand...
Click to collapse
Just call me shadow.
You got it man!
So what 7.1 ROM do you like the best so far? Any of them you like as a DD?