Related
i used nexus root tool kit to update nexus 4 from 4.4 to 5.0... all done in pc but mobile is stuck in boot loop. can anyone tell me how can i restore my phone to normal working...
Please help me i am noob here
is there any one who can help me here
i thought i will get ans with in 1hr... still waiting if someone can help
letsnexus said:
i thought i will get ans with in 1hr... still waiting if someone can help
Click to expand...
Click to collapse
This is why we don't recommended using tool kits. You should try flashing the factory image using fastboot.
Sent from my Nexus 9 using XDA Free mobile app
Same here, i tried re-flashing many times. Darn that nexus root toolkit
any suggetion or link which can help me to use fastboot use and install stock rom
thank alot for help
I am currently in the same position ! Used a toolkit too, always have.
This is why you never use a Toolkit, it's always been mentioned around in XDA that this has always been a developer website of learning and knowledge. You must always know what goes on behind than just blindly flashing things. It's a rule of thumb that you're more likely to brick your phone with a Toolkit than by yourself. Easiest step as follows.
1. Download factory image
2. Download ADB files
3. Make a folder and extract the adb files and factory image inside the same folder.
4. Plug the phone in bootloader mode or simply type adb reboot bootloader (Developer options must be enabled and USB Debugging) by exiting the folder, holding shift, right clicking the folder and pressing open command window and typing the command.
5. Every factory image comes with a flashall.bat, double click it and voila. Updates like it should. (User data will be wiped)
If you don't want your userdata to be wiped, simply open flashall.bat with notepad++, erase the '-w' in "fastboot -w update image" and save the file and launch it again.
Sent from my HTC One_M8 using Tapatalk
I will try that way later when I get in, I would have assumed that the toolkit did exactly those steps though, just an easy to use frontend
hazwheel said:
I will try that way later when I get in, I would have assumed that the toolkit did exactly those steps though, just an easy to use frontend
Click to expand...
Click to collapse
Go to stock recovery and do factory data reset and reboot phone. First time boot takes very long time (around 10 to 15 minutes). After successfully boot into android L check for the storage space. If it says only 5 GB available instead of 12 GB (My nexus is 16GB) then Go to Settings > Backup & Reset and select Factory data reset.
I had experienced these issues when upgrading to Lollypop and solved them on my own.
Note: If you were not able to boot into stock recovery, try twrp recovery. you have to install it using fastboot
fastboot flash recovery <filename.img>
letsnexus said:
any suggetion or link which can help me to use fastboot use and install stock rom
thank alot for help
Click to expand...
Click to collapse
although the link is for kitkat but the same method applies to flashing lollipop
http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
moorthidaniel said:
Go to stock recovery and do factory data reset and reboot phone. First time boot takes very long time (around 10 to 15 minutes). After successfully boot into android L check for the storage space. If it says only 5 GB available instead of 12 GB (My nexus is 16GB) then Go to Settings > Backup & Reset and select Factory data reset.
I had experienced these issues when upgrading to Lollypop and solved them on my own.
Note: If you were not able to boot into stock recovery, try twrp recovery. you have to install it using fastboot
fastboot flash recovery <filename.img>
Click to expand...
Click to collapse
OK, I was able to get into recovery with this method, and wipe but I get can't mount cache errors during the wipe , waiting for the phone to reboot now, hopefully it will and get out of the bootloop. stupid thing is I'm not a noob, but stumped by this. Good excuse to upgrade to the N5 I guess
---------- Post added at 03:14 PM ---------- Previous post was at 02:55 PM ----------
Wow, this method worked! Brilliant! Thanks, and dammit, it worked, 10 minutes after she agreed to me getting am upgrade !
For all of you whom are stuck in bootloop a fastboot oem lock comand when in fastboot will solve the problem.
So go into bootloader and run "fastboot oem lock" for some reason on some devices Android 5.0 won't boot with unlocked bootloader.
hazwheel said:
OK, I was able to get into recovery with this method, and wipe but I get can't mount cache errors during the wipe , waiting for the phone to reboot now, hopefully it will and get out of the bootloop. stupid thing is I'm not a noob, but stumped by this. Good excuse to upgrade to the N5 I guess
---------- Post added at 03:14 PM ---------- Previous post was at 02:55 PM ----------
Wow, this method worked! Brilliant! Thanks, and dammit, it worked, 10 minutes after she agreed to me getting am upgrade !
Click to expand...
Click to collapse
OK great. Cheers, I helped someone today in this forum.
bett3rthan said:
For all of you whom are stuck in bootloop a fastboot oem lock comand when in fastboot will solve the problem.
So go into bootloader and run "fastboot oem lock" for some reason on some devices Android 5.0 won't boot with unlocked bootloader.
Click to expand...
Click to collapse
That did NOT work for me, the getting into recovery and wiping the device DID work though.
---------- Post added at 04:05 PM ---------- Previous post was at 04:03 PM ----------
moorthidaniel said:
OK great. Cheers, I helped someone today in this forum.
Click to expand...
Click to collapse
Yes, Thanks, unfortunately, she has withdrawn the offer of an early upgrade :silly:
thax
Misledz said:
This is why you never use a Toolkit, it's always been mentioned around in XDA that this has always been a developer website of learning and knowledge. You must always know what goes on behind than just blindly flashing things. It's a rule of thumb that you're more likely to brick your phone with a Toolkit than by yourself. Easiest step as follow
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Thank you alot, you help in really good manner
and teached us not to use toolkit
will learn more abt rooting and flashing thank you once again
I am hitting this problem now, I got a OTA. After restarting its keep on looping waiting for more than 20mins still it's looping.
Tried going to boot-menu and did factory reset and it booted good after ~10 mins.
sububack said:
I am hitting this problem now, I got a OTA. After restarting its keep on looping waiting for more than 20mins still it's looping.
Click to expand...
Click to collapse
Power off, hold Vol Down + Power, when you get to the Android laying down, press volume up + pwr, then wipe the /cache from the menu (you do not need to do a full factory wipe, just wiping cache will do), and then reboot and wait. It will boot this time properly. @WugFresh is aware of the issue and said will put a fix in 1.9.9 for the N4
Thanks , I have tried clearing the cache and started waiting for an hour. Since it was still looping tried after factory reset/wiping user data. And then after 10min it came good.
I post this on Google Product Forum 2 days ago. Hope it helps
https://productforums.google.com/fo...ce=footer#!msg/nexus/Lv8fHtyJOPQ/wDzRUm4b2UsJ
(updated 29/11/2014)[not perfect but it is a SOLUTION]
The idea of this is to downgrade your nexus 4 without wiping your data, which means stuff you will need includes:
1. adb and fastboot on your computer (I am using mac but you can find it on windows as well. There are tones of website and forums telling you the latest method of getting it onto your computer)
2. factory image of nexus 4(I use 4.4.4, since that's what it was. I don't have the time and energy to try to do the same thing with lollipop. you can try can leave a comment).
update: do NOT try to flash 5.0 rom using this method. You will be stuck at boot loop again
3. usb cable
4. nexus 4 with unlocked bootloader(the process of unlocking bootloader will wipe your device)
5. computer
steps
1. unzip the factory image (something.tgz)
2. for me, after unzipping the .tgz, I still find another .zip inside. unzip that too.
3. hold vol+, vol-, and power button simultaneously to enter fastboot mode
4. open terminal(mac)(it would probably be cmd for windows)
5. connect your nexus 4(in fastboot)
6. to make sure it connect successfully, type "fastboot devices". if something like "005040c0d54bb291 fastboot" appears, you are good. Otherwise, try reconnect your device/boot to fastboot again/use another usb cable
7.now we need to tell the terminal to navigate to the location of the unzipped factory image. to do that, i suggest you put the unzipped folder to somewhere easy to find, like desktop. these are some commands to help you navigate:
"ls" allows you to look at whats inside the current directory of the terminal. For example, this is the output after typing "ls" for me:
some folder Photos
nexus4image.tgz how many folders do you have
5.zip occam-ktu84p
more folder occam-ktu84p.zip
after knowing where you are, use "cd" (below) to go to your folder
"cd" means change directory. For example. "cd Photos" will brings me to the "Photos" folder. And then if I type ls, I will see a whole bunch of photos in my photos. If you go to the wrong folder, type "cd ..", and it will bring you back to the previous folder.
8. flash bootloader.
enter the following command, BUT REMEMBER TO CHANGE THE NAME TO FIT YOURS(DIFFERENT VERSIONS HAVE SLIGHTLY DIFFERENT FILE NAME AT THE END(type ls first to help you type the correct name)
fastboot flash bootloader bootloader-mako-makoz30d.img
9. reboot bootloader. just copy and paste
fastboot reboot-bootloader
10. flash radio
enter the following command, BUT REMEMBER TO CHANGE THE NAME TO FIT YOURS(DIFFERENT VERSIONS HAVE SLIGHTLY DIFFERENT FILE NAME AT THE END(type ls first to help you type the correct name)
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.03.img
11. reboot bootloader. just copy and paste
fastboot reboot-bootloader
12. flash system
system.img is located inside the zip, use ls to help you navigate. This steps takes the longest time, total time on this step is 87 seconds while the others are less then 1 second
fastboot flash system system.img
13. flash boot
boot.img is located inside the zip, use ls to help you navigate.
fastboot flash boot boot.img
14. flash recovery
fastboot.img is located inside the zip, use ls to help you navigate.
fastboot flash recovery recovery.img
15. format cache(not the memory, so everything should be fine)
fastboot format cache
16. reboot and wait
this will reboot your device. You probably have to wait for a while to initialise all the apps. after than you are good to go!
fastboot reboot
credit: my friend for giving me this idea + http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312 + HelpMyNexus
This is the whole situation:
I have Pure Nexus installed on my 6P, running great for months. Suddenly yesterday it rebooted while I was using it and sticking in a bootloop. "No problem", I thought, and wanted to reboot into recovery - but nope, can't access it anymore. So I tried to reflash the recovery when I got home, but I only get errorors
When using the command adb devices the line just stays blank. The same with fastboot commands, besides "Fastboot devices"
After messing around a couple hours with the drivers and so on, I managed to somehow get the fastboot command working again. But no sign for the ADB commands, probably because I didn't turn on USB-debugging.
I am now at the point, where I have reflashed Stock Android with the Nexus Root Toolkit and managed to get back into stock android recovery, but still can't get TWRP to boot. I didn't want to delete my personal data, but I saw no other way and formatted /data in stock recovery. But the problem with the bootloop is still there.
It's not the classic bootloop, it boots as far as the Google Logo, then shuts itself down and begins again. I have now reached the point where I have to say, that the hardware might be damaged too. I'd love to somehow get access to the internal storage at least, but I can't without a working ADB.
Reinstalled TWRP with every available version, none of them worked. I am able to access stock Android recovery, but adb commands aren't working from here anyway.
Is there an option to fix the recovery mode? If I could get this working, the rest would be easy for me.
Edit: The reboot looks like in this Link. Only difference is, my device doesn't even the reach the dots.
StarShoot97 said:
This is the whole situation:
I have Pure Nexus installed on my 6P, running great for months. Suddenly yesterday it rebooted while I was using it and sticking in a bootloop. "No problem", I thought, and wanted to reboot into recovery - but nope, can't access it anymore. So I tried to reflash the recovery when I got home, but I only get errorors
When using the command adb devices the line just stays blank. The same with fastboot commands, besides "Fastboot devices"
After messing around a couple hours with the drivers and so on, I managed to somehow get the fastboot command working again. But no sign for the ADB commands, probably because I didn't turn on USB-debugging.
I am now at the point, where I have reflashed Stock Android with the Nexus Root Toolkit and managed to get back into stock android recovery, but still can't get TWRP to boot. I didn't want to delete my personal data, but I saw no other way and formatted /data in stock recovery. But the problem with the bootloop is still there.
It's not the classic bootloop, it boots as far as the Google Logo, then shuts itself down and begins again. I have now reached the point where I have to say, that the hardware might be damaged too. I'd love to somehow get access to the internal storage at least, but I can't without a working ADB.
Reinstalled TWRP with every available version, none of them worked. I am able to access stock Android recovery, but adb commands aren't working from here anyway.
Is there an option to fix the recovery mode? If I could get this working, the rest would be easy for me.
Edit: The reboot looks like in this Link. Only difference is, my device doesn't even the reach the dots.
Click to expand...
Click to collapse
If you can get fastboot commands to work, just flash the factory image per Heisenberg's guide. Toolkits are more trouble than help. Return it to fresh stock with a full wipe and start fresh.
Sent from my Nexus 6P using Tapatalk
StarShoot97 said:
Edit: The reboot looks like in this Link. Only difference is, my device doesn't even the reach the dots.
Click to expand...
Click to collapse
That vid you linked is an N5 with a stuck power button. It'll do the same thing and reboot recovery as well. It could be your issue but if it is it'll be the first stuck power button I've heard of on a 6P.
When you access fastboot does it stay on in fastboot or does it reboot from it?
theesotericone said:
That vid you linked is an N5 with a stuck power button. It'll do the same thing and reboot recovery as well. It could be your issue but if it is it'll be the first stuck power button I've heard of on a 6P.
When you access fastboot does it stay on in fastboot or does it reboot from it?
Click to expand...
Click to collapse
I said it looks like this, I did not say the button is the reason
When I access fastboot it stays there until I manually select an option
ultyrunner said:
If you can get fastboot commands to work, just flash the factory image per Heisenberg's guide. Toolkits are more trouble than help. Return it to fresh stock with a full wipe and start fresh.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
This is my last viable option, as I'd like to somehow pull my stuff from the phone. Afterwards I'd clean install it anyway.
StarShoot97 said:
This is my last viable option, as I'd like to somehow pull my stuff from the phone. Afterwards I'd clean install it anyway.
Click to expand...
Click to collapse
You contradict yourself a bit so it is difficult to help you. You got to stock recovery but you can't boot into TWRP? If you have stock recovery, of course you can't boot into TWRP. You have wiped your data but you still want to preserve your data ... Huh?
Your phone isn't working so just nuke and pave with the command line and avoid toolkits. They are sometimes part of the problem.
Sent from my Nexus 6P using Tapatalk
ultyrunner said:
You contradict yourself a bit so it is difficult to help you. You got to stock recovery but you can't boot into TWRP? If you have stock recovery, of course you can't boot into TWRP. You have wiped your data but you still want to preserve your data ... Huh?
Your phone isn't working so just nuke and pave with the command line and avoid toolkits. They are sometimes part of the problem.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
When stock recovery is installed, I am from time to time able to access it (most of the times it just ends in a bootloop)
If I flash TWRP I can't access it, no matter how often I try
I have factory reset my phone, the stuff on the internal is still there and I want to reach this, as I have my chats, SMS, university stuff and so on backed up on the internal storage
I am trying everything - all the regular adb methods, toolkits, every driver, nothing is working
Sorry if you don't understand my situation, but I am in a pinch right now
You said you have fastboot working?
Download the factory image zip file. Extract it. Extract the zip file from inside that as well. Move the img files to your platform-tools folder.
Reboot your phone to the bootloader. Hold volume down+power from a powered off state.
Plug into PC, open command line from your platform-tools folder.
Type, fastboot devices
Does it show your serial number? If so, start flashing the following images;
Bootloader-angler-angler-xx.xx.img, radio-angler-angler-xx.xx.img, vendor.img, system.img, boot.img, recovery.img
Flash with fastboot.
Code:
fastboot flash bootloader bootloader-angler-angler-xx.xx.img
Code:
fastboot flash radio radio-angler-angler-xx.xx.img
(Substitute "xx.xx" for the version number shown in the img files you unpacked)
Reboot bootloader
Code:
fastboot flash vendor vendor.img
Code:
fastboot flash system system.img
Code:
fastboot flash boot boot.img
Code:
fastboot flash recovery recovery.img
Once you do that, boot to stock recovery and cache wipe. Reboot and you're stock. If you're still not able to boot after that post back.
Edit: You said you wanted to avoid flashing factory images to keep internal storage in tact. Do it this way and you can have your cake and eat it too.
Edit2: wrong, see my latest reply
RoyJ said:
You said you have fastboot working?
Download the factory image zip file. Extract it. Extract the zip file from inside that as well. Move the img files to your platform-tools folder.
Reboot your phone to the bootloader. Hold volume down+power from a powered off state.
Plug into PC, open command line from your platform-tools folder.
Type, fastboot devices
Does it show your serial number? If so, start flashing the following images;
Bootloader-angler-angler-xx.xx.img, radio-angler-angler-xx.xx.img, vendor.img, system.img, boot.img, recovery.img
Flash with fastboot.
Code:
fastboot flash bootloader bootloader-angler-angler-xx.xx.img
Code:
fastboot flash radio radio-angler-angler-xx.xx.img
(Substitute "xx.xx" for the version number shown in the img files you unpacked)
Reboot bootloader
Code:
fastboot flash vendor vendor.img
Code:
fastboot flash system system.img
Code:
fastboot flash boot boot.img
Code:
fastboot flash recovery recovery.img
Once you do that, boot to stock recovery. Perform a factory reset again like you already mentioned you did as well as a cache wipe. Reboot and you're stock. If you're still not able to boot after that post back.
Edit: You said you wanted to avoid flashing factory images to keep internal storage in tact. Do it this way and you can have your cake and eat it too.
Click to expand...
Click to collapse
I did this already exactly like you wrote, did it again now, and I am still stuck in the reboot loop (boots up to Google Logo, then shuts itself down; repeat)
Can't reach recovery mode either
You said you had access to stock recovery before?
You already did this?
---------- Post added at 12:17 PM ---------- Previous post was at 12:16 PM ----------
If you flashed the factory images and still boot looping you may need to RMA.
Did you restore a TWRP backup?
Edit: Sorry, it's late and I have no sleep. I was wrong. I was thinking TWRP. Factory Reset from TWRP before my steps will keep internal storage I'm tact. Factory Reset from stock recovery will wipe internal storage. Everything. You mentioned you did that already from stock recovery before i made my reply. Your data is already gone as soon as you did that. If not, your emmc is likely corrupted and you need to RMA.
Fastboot twrp 3.0.0-0 then try to access it
RoyJ said:
You said you had access to stock recovery before?
You already did this?
---------- Post added at 12:17 PM ---------- Previous post was at 12:16 PM ----------
If you flashed the factory images and still boot looping you may need to RMA.
Did you restore a TWRP backup?
Edit: Sorry, it's late and I have no sleep. I was wrong. I was thinking TWRP. Factory Reset from TWRP before my steps will keep internal storage I'm tact. Factory Reset from stock recovery will wipe internal storage. Everything. You mentioned you did that already from stock recovery before i made my reply. Your data is already gone as soon as you did that. If not, your emmc is likely corrupted and you need to RMA.
Click to expand...
Click to collapse
Yes, I think so too. I flashed the phone with the full Stock image, the bootloop is still there.
Looks like my precious is dead
At least I have my most important data like phonenumbers, pictures and SMS saved to the cloud
Gonna RMA it tomorrow
Goodybe my precious, I hope you'll be fine :crying:
Got my device back today, the mainboard was damaged, so I had no chance to get my data from the phone
Hey, at least my warranty has been renewed 'till 2018
StarShoot97 said:
This is the whole situation:
I have Pure Nexus installed on my 6P, running great for months. Suddenly yesterday it rebooted while I was using it and sticking in a bootloop. "No problem", I thought, and wanted to reboot into recovery - but nope, can't access it anymore. So I tried to reflash the recovery when I got home, but I only get errorors
When using the command adb devices the line just stays blank. The same with fastboot commands, besides "Fastboot devices"
After messing around a couple hours with the drivers and so on, I managed to somehow get the fastboot command working again. But no sign for the ADB commands, probably because I didn't turn on USB-debugging.
I am now at the point, where I have reflashed Stock Android with the Nexus Root Toolkit and managed to get back into stock android recovery, but still can't get TWRP to boot. I didn't want to delete my personal data, but I saw no other way and formatted /data in stock recovery. But the problem with the bootloop is still there.
It's not the classic bootloop, it boots as far as the Google Logo, then shuts itself down and begins again. I have now reached the point where I have to say, that the hardware might be damaged too. I'd love to somehow get access to the internal storage at least, but I can't without a working ADB.
Reinstalled TWRP with every available version, none of them worked. I am able to access stock Android recovery, but adb commands aren't working from here anyway.
Is there an option to fix the recovery mode? If I could get this working, the rest would be easy for me.
Edit: The reboot looks like in this Link. Only difference is, my device doesn't even the reach the dots.
Click to expand...
Click to collapse
Try flashing TWRP 3.0.2-3 or boot into twrp through fastboot. Using
fastboot boot recovery <twrp filename>.img
I think booting to twrp using this command will work.
And here's the link to Twrp 3.0.2-3 , as its not available on Official Twrp page.
https://idlekernel.com/twrp/nexus/twrp-3.0.2-3-angler.img
I had the same problem with my 5X, nothing worked I tried every possible solution described above and more. Nothing. I figured out that there was nothing to loose and followed directions from YouTube videos (links below) and it worked. Used heat gun at max temp for about 2 mins from each side. It's been about 12 hours since then, phone works flawlessly. Here are the links:
https://www.youtube.com/watch?v=SD25mdrgAys
https://www.youtube.com/watch?v=Cqh2x-TGnCY
Be careful handling the motherboard after you heat the first side, let it cool first before you start working on the second side. The same with the second side do not pick it up until it's cool.
5X, Pure Nexus Rom 7.1.2 June 5th security update, Elemental X Kernel,
has anyone found solution to this?????
I would like to thank this wonderful community for all the help I have gotten over the years, I think this should be my first post.
For technical details of all I have done and learned on recovering the damn phone, skip to below the line, the rest is more of an introduction + some history.
In the past I have had a Canadian (BELL) Samsung Galaxy S2.5 as I like to call it. Specs similar to the S3 but not quite.
That was fairly easy to root thanks to odin.
Anyways, I have an LG G2 that I inherited from my brother, so I have some emotional attachment given he passed away 2 years ago (Age 36)... Reason why it is critical that I fix it.
I feel it's a great phone with excellent specs, with some flaws.
Hardware wise, this phone's digitizer seems to fail after a few years and stops registering touches.
Failed on my brother after 8 months, he got it replaced by videotron.
8 months after my ownership, same issue. I replaced the screen, which is a pain.
I dropped it a year later and broke the screen, replaced again.
Replaced the battery twice (First replacement battery was DOA) and... The internals of this phone are a pain to work with... to my limited experience at least.
The get to the point line as stated above.
___________________________________________________________________________________________
I wanted to flash my 4 year old never reinstalled phone, give it new life.
Researched a bit everywhere, verified in the phone what version it is, even most google results tell me this and the replacement screen is all the same.
it's a D801
After some work and research being clueless about working with this model, I finally installed
Started with getting Dev powers by spamming a specific key, setting usb debugging...
Using some application manager.
Installed
D801_AutoRec.apk
Towelroot.apk
From autorec, I installed the twrp and... fastboot... had no idea what that was.
Here I learned how to recover my phone.
This guy... super helpful.
Youtube link removed to post
So in short Download all the necessary drivers to get the android device detected.
Download those
codefi re link removed
I erased and flashed so often now that I scripted it in a batch file
Notepad, save as (not as text) flash****.bat or whatever you want to call it.
fastboot erase boot
fastboot erase aboot
fastboot erase recovery
fastboot erase laf
fastboot erase dbi
fastboot erase modem
fastboot erase persist
fastboot erase PrimaryGPT
fastboot erase rpm
fastboot erase stl1
fastboot erase tz
fastboot flash boot boot.img
fastboot flash aboot aboot.img
fastboot flash recovery recovery.img
fastboot flash laf laf.img
fastboot flash dbi dbi.img
fastboot flash modem modem.img
fastboot flash persist persist.img
fastboot flash PrimaryGPT PrimaryGPT.img
fastboot flash rpm rpm.img
fastboot flash stl1 stl1.img
fastboot flash tz tz.img
Originally, I only did boot aboot recovery and iaf
After that, my phone rebooted to the LG logo and stuck, but the Download mode is working again.
At that point I did flash a twrp recovery and was able to run it using the command abd reboot recovery
I pushed different roms, but no matter what I do, always back to fastboot.
Found this video later on, originally found a thread here but for the life of me I can't find it anymore (too much history) (How to recover with LG Tools the original kdz
youtube link removed
Now... I could not find the correct firmware
I used this
T-Mobile KitKat D80120A_00
IT worked, my phone restarted as it was before my adventures, but under a tmobile d801
Here I am happy, I get the proper D803_AutoRec.apk
Install the recovery again...
Now I really broke my phone.
Retried the steps above of flashing aboot and so on...
Refuses to work.
So I figured, hey, I recovered it under D801 tmobile... I probably broke it with the D803 recovery.
Back to the download site, made another folder and downloaded all the D801 img's
Ran my script (well that's when I created it from being sick of typing it)
Now I boot Tmobile but it's stuck to All Auto Test - FTM Mode
SUrprisingly on wifi,, shows missed calls and picking up exchange emails...
When I try to Flash as I have before under download, it fails.
SO hey, it found a 300MB tmobile update... why the hell not at this point.
Can anyone link me the proper software I can try to recover the LG Tools ?
csmgdl link removed
and
csmgdl link removed
Don't seem to work
Did I mess it up beyond repair ?
Any recommendations ?
I am hoping for one of the following
If I get tmobile OS working
Retry the D801_AutoRec.apk given it matches the tmobile recovery that somewhat works and then attempt the original goal of setting up CloudyFlex_2.8, CloudyStock_2.7 or cm-12-20150325-UNOFFICIAL-d803
Pretty sure up there, most of those wont work, I just want a working twrp
All I want is this phone wiped with a clean efficient rom to use as a reliable daily.
All I do is phone, text, exchange, camera, some apps... nothing too fancy.
I am off to sleep
Whatever I do, I can't get out of All Auto Test = FTM Mode
Reboot, hold volume up
Down
Up and down
Power up
Power down
Power vol up and down...
Always to all auto test.
Swipe down, get to options, general, do a full factory rest...
Same thing. Grr
Okay dude, take it slow. There's only one way to correctly root/install recovery on this device - that seems to work for everyone.
Tell me if this works. Plug a usb cable from the phone into your PC. Shutdown the phone holding power, release power, hold up. Keep shutting it down and doing this again until you get into "Download Mode". Tell me if you manage this.
Turbine1991 said:
Okay dude, take it slow. There's only one way to correctly root/install recovery on this device - that seems to work for everyone.
Tell me if this works. Plug a usb cable from the phone into your PC. Shutdown the phone holding power, release power, hold up. Keep shutting it down and doing this again until you get into "Download Mode". Tell me if you manage this.
Click to expand...
Click to collapse
I have gone to download mode before to recover an oem image.
Now, I can't get to download mode after trying a number of times.
Ill give it another go tonight. Yesterday I got tired from the research, trial and error.
Thanks for your reply
With a calm mind, I fixed my issue.
https://forum.xda-developers.com/showthread.php?t=2613404
Press and hold power + Vol up and tap normal boot.
Didn't understand that at first.
Now let's see if I will break it again.
Still unsure if I should root it using D801_AutoRec.apk or D803_AutoRec.apk
Reason why I hate this phone.
Videotron LG G2 writes that it's a D801 but I read in other sources that it's a D803.
Now however, it's been restored to a Tmobile Firmware...
Okay, take it really slow. I've just completely rooted, put a custom recovery on and am now on Android N. There's many things which can go wrong - requiring you to restart the process.
Treat it as a D801, as the T-Mobile firmware booted. AutoRec does not root the device. Are you on KitKat or Jellybean? If you're on KitKat, do the following.
You must use IORoot to root the device - it does it in such a way it'll accept custom recoveries.
(You already have the phone's USB drivers obviously)
1) Download IORoot V25 from here.
2) Extract the file.
3) We need to unlock USB debugging, so make sure the phone is not connected to the pc. Settings -> About -> Software -> Tap on "Build" like 8 times fast. Go back into settings and you'll see "Developer Options", tick USB debugging. Now if your device freezes up like mine did when tapping build, then download an app which lets you go directly to developer options.
4) Hook the phone up to the PC, make sure it's not in lock screen.
5) Double click "root.bat" normally (not as admin). Keep going through this process until it brings you to the stock recovery area where you can flash over ADB.
6) It'll walk you through the process where it boots back into Android.
7) Open SuperSU, which it installed.
8) In the settings somewhere, make the grant always accept rather than prompt. My device was bugged not allowing root unless it was forcefully granted like this.
AutoRec - Recovery Install
1) Copy the contents "bumpboot-v1.0-blastagator-signed.zip" and "busybox.apk" and "flashify.apk" onto your device. Download here.
2) Download TWRP for T-Mobile 2.8.6.0 from here, extract recovery.img and copy that onto your device.
3) Copy AutoRec KitKat for T-Mobile here.
4) So you should now have "D801_AutoRec.apk", "recovery.img", "busybox.apk", "flashify.apk", "bumpboot-v1.0-blastagator-signed.zip" on your phone.
5) Proceed to install "AutoRec.apk", ticking unknown sources. Let it boot into recovery. Now reboot.
6) As my recovery didn't stick, install and open "busybox.apk", click install in the program itself. Install and open "flashify.apk", flash recovery, browse using flashify to the location of "recovery.img", let it reboot into recovery. This is where I had to flash "bumpboot-v1.0-blastagator-signed.zip", otherwise I couldn't boot into the OS. So flash that file.
7) Reboot back into the OS. Until we flash lollipop, there wasn't any other way for me to reliably get into TWRP recovery without repeating step 6.
8) Copy over the Bootstack and Stock Rom from here. Don't worry about SuperSU or anything else.
9) Repeat step 6 to boot back into recovery.
10) Wipe everything except internal memory in TWRP.
11) Flash the lollipop bootloader.
12) Flash the lollipop stock rom.
13) Reboot.
14) Now you're able to get back into recovery any time by holding the power + volume down combo, releasing when the screen goes on - and holding it down again.
15) Feel free to flash LineageOS 14.1 or anything afterwards. Make sure to backup your EFS partition at some stage before this - just incase you can't connect to cell towers in the near future.
As you can see, I had to improvise a bit. No guide was good enough to just work in 2017 for my D800. These should work fine for your D801.
Thank you so much for such an amazing and detailed response !!!
After quite a bit more research and work, I got it rooted and got TWRP working.
Once done I uploaded cloudyflex 2.8
Installed it and of course, me being me, chose the wrong install when prompted. It asked Tmobile, other and Canadian 803.
I chose Canadian and after that got back to fast boot.
After that I simply erased boot, aboot and laf, getting ready to restart from scratch but it rebooted on a clean cloudyflex 2.8.
At this point, the phone is running better then stock and I am very happy with it
Your walkthrough is great and I will certainly redo my phone soon again.
For one, practice makes perfect and I certainly like that with your instructions, I will be able to call on the recovery when I want it instead of asking my way into it by adb command.
Thank you again for your time
This community rocks !
Feel free to thumb me. I also have a request for you, I'll PM.
After flashing dirtysanta successfully I wanted to move over to the magisk installation. Following the steps and attempting t use magisk I must have mucked something up very well.
after flashing the initial boot image and twrp from fastboot I hoped that it would fix these issues. Instead it seems to have corrupted fastboot. I did a kdz restore with reset hoping this would help but the touch screen still doesn't work and now I cannot setup the phone to allow adb. Booting from the system menu into usb-debugging mode just boots the phone normally
Currently I can boot into only into android but because I am stuck at the setup screen I can't connect through adb. I am not sure where to go from here.
The only thing that I can think of is getting a usb-otg adapter and connecting a mouse and attempting to allow adb by setting up the phone that way but I still cant flash anything from adb so I wouldn't know what to do from there. Does anybody have any suggestions?
Is there a way to install a boot image without fastboot?
I was very excited to start using this phone and this sucks. Any help would be appreciated
Do u have twrp at all? Some guys used a mouse and got threw the setup with it.
Sent from my LG-H918 using Tapatalk
I can't access twrp at all attempting all methods leads to a normal boot routine. It doesn't even go to the stock page where it asks to wipe data. Just LG logo, black screen (assuming it crashes and restarts), then regular boot
I have successfully restored touch functionality by reflashing multiple different kdz files over and over again.
This has not fixed my inability to enter fastboot. I can enter the default android recovery from the no command screen after using adb reboot recovery but any other command just restarts the phone. Rebooting into bootloader from the default recovery just restarts the phone. I am not sure where to go from here, really upset because any fix requires fastboot
tgtrottier said:
I can't access twrp at all attempting all methods leads to a normal boot routine. It doesn't even go to the stock page where it asks to wipe data. Just LG logo, black screen (assuming it crashes and restarts), then regular boot
Click to expand...
Click to collapse
I guess U didn't wait more than 30sec during the step 3, this is crucial.
---------- Post added at 05:09 PM ---------- Previous post was at 05:07 PM ----------
tgtrottier said:
I have successfully restored touch functionality by reflashing multiple different kdz files over and over again.
This has not fixed my inability to enter fastboot. I can enter the default android recovery from the no command screen after using adb reboot recovery but any other command just restarts the phone. Rebooting into bootloader from the default recovery just restarts the phone. I am not sure where to go from here, really upset because any fix requires fastboot
Click to expand...
Click to collapse
Get into download mode and Use LG bridge to upgrade
hoi_lai said:
I guess U didn't wait more than 30sec during the step 3, this is crucial.
Is this afternoon running step 3 and waiting for boot? Because when I did it I waited around 30 min on the Verizon boot screen before pulling the battery to reboot.
In reference to LG bridge. Is this different than LGUP?
Click to expand...
Click to collapse
tgtrottier said:
hoi_lai said:
I guess U didn't wait more than 30sec during the step 3, this is crucial.
Is this afternoon running step 3 and waiting for boot? Because when I did it I waited around 30 min on the Verizon boot screen before pulling the battery to reboot.
In reference to LG bridge. Is this different than LGUP?
Click to expand...
Click to collapse
I mean you have to wait at least 30 sec for the step "fastboot flash recovery twrp-3.0.2-1-xxx.img", & also have to do it multiple times in order to load the TWRP successfully.
Click to expand...
Click to collapse
The strange thing is that I could access twrp for a while but then after restoring with LGUP I can't access even stock recovery. And flashing the notsostock kernel messed up the ramdisk it seems, because it said it couldn't write over it. The thing that concerns me is restoring with LGUP doesn't make any difference to these two thiñgs
I am suffering with a similar issue, VS995s model. The touchscreen stopped working after the TWRP flash, using OTG I was able to access TWRP. I restored both the dec16 kdz and the feb18 kdz with no affect on the screen. I was able to use OTG mouse and bluetooth mouse to reflash TWRP with dirtysanta and used OTG mouse to flash lineage OS v14.1 this did not solve the issue either. I re-flashed stock and am at a loss on the next possible step.
tgtrottier, you mentioned that it worked again after flashing a bunch of different KDZ files, do you know the specific one? I am looking for a useable touchscreen at this point and can deal with no root.
@frownyface
Did you discover the solution to the touchscreen not working? After flashing TWRP I have the same issue.
Nope i used an otg mouse and reverted to stock and returned the item.
I felt super bad about it, but i didnt have the time to invest in disassembling it to find the cause which i suspect was a loose connection due to the extended vibration during the root process.
Thumbs down sorry i could not be any help,
Hello ALL!
I normally don't message much because usually I can find most of my problems can be fixed by searching threads online. However, this particular case for me has been exhausting because through trial and error I have been unsuccessful in getting my 6T to boot into any rom normally.
I went from a stock T-Mobile to International version to LOS. The reason I did what I did was because I could get a IMEI or SIM to register on LOS. That worked fine on OOS 9.0.11. but as soon a I flash the latest LOS, no sim, bootloader, or IMEI detection.
I was rooted and unlocked. Now I am neither.
While on LOS, someone on another forum suggested to erase the persist partition and reflash to get the sim imei back so the phone would get service, when the phone rebooted it still didn't work and then the second time it rebooted it always gets stuck on the boot screen and never boots into the OS.
I tried to repair and reflash but was unsuccessful.
Since doing all of that, Ive reflashed using msm tool and although that was successful for OOS 9.0.11 and T-Mobile stock rom. It gets stuck on the boot screens for both.
I flashed LOS on A & B so I don't have a stock recovery.
I can't ADB anymore. I can only seem to connect via FASTBOOT but cannot seem to flash anything because the BOOTLOADER is now LOCKED.
How can I get this phone back to its original state? What ever the persist partition is. Removing it had made the phone non-bootable.
What can I do to fix? I greatly appreciate any help to get the phone operational again.
Thank you all!
https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
- Go to the thread linked above and download the latest OOS (.13) stable.
- Download latest Magisk.
- Have the latest TWRP .img downloaded and on-hand, you will use a few times as well as the installer .zip.
- Be sure to have adb/fastboot installed.
***BACK UP DATA, YOUR PHONE WILL BE WIPED. INTERNAL SD AS WELL***
***BACK UP DATA, YOUR PHONE WILL BE WIPED. INTERNAL SD AS WELL***
***BACK UP DATA, YOUR PHONE WILL BE WIPED. INTERNAL SD AS WELL***
- Put your phone into fastboot mode (reboot to bootloader).
- Go to the folder you downloaded in the first step and run the "flash all.bat".
- Ignore errors. If it's get stuck for more than 45 seconds, just hit enter to keep it going.
- OOS will boot. Go to settings, enable developer setting, enable advanced reboot and reboot bootloader again.
- Use "fastboot boot 'twrp-file-name'.img" to boot into TWRP.
- In TWRP, go to Reboot and changed the boot partition to the one NOT CURRENTLY enabled. In other words, switch boot partitions.
- Reboot bootloader.
- Go to the folder you downloaded in the first step and run the "flash all.bat" again.
- OOS will boot. Go to settings, enable developer setting, enable advanced reboot and reboot bootloader again.
- Use "fastboot boot 'twrp-file-name'.img" to boot into TWRP again.
- Move Magisk installer and TWRP installer from steps two and three onto the internal memory of your device.
- Flash TWRP, reboot recovery to make sure it sticks.
- Flash Magisk for root.
- Wipe dalvik and reboot system.
You will have the latest stable OOS on both partitions at this point! I literally just did this yesterday. Good luck!
..Cory.. said:
https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
- Go to the thread linked above and download the latest OOS (.13) stable.
- Download latest Magisk.
- Have the latest TWRP .img downloaded and on-hand, you will use a few times as well as the installer .zip.
- Be sure to have adb/fastboot installed.
***BACK UP DATA, YOUR PHONE WILL BE WIPED. INTERNAL SD AS WELL***
***BACK UP DATA, YOUR PHONE WILL BE WIPED. INTERNAL SD AS WELL***
***BACK UP DATA, YOUR PHONE WILL BE WIPED. INTERNAL SD AS WELL***
- Put your phone into fastboot mode (reboot to bootloader).
- Go to the folder you downloaded in the first step and run the "flash all.bat".
- Ignore errors. If it's get stuck for more than 45 seconds, just hit enter to keep it going.
- OOS will boot. Go to settings, enable developer setting, enable advanced reboot and reboot bootloader again.
- Use "fastboot boot 'twrp-file-name'.img" to boot into TWRP.
- In TWRP, go to Reboot and changed the boot partition to the one NOT CURRENTLY enabled. In other words, switch boot partitions.
- Reboot bootloader.
- Go to the folder you downloaded in the first step and run the "flash all.bat" again.
- OOS will boot. Go to settings, enable developer setting, enable advanced reboot and reboot bootloader again.
- Use "fastboot boot 'twrp-file-name'.img" to boot into TWRP again.
- Move Magisk installer and TWRP installer from steps two and three onto the internal memory of your device.
- Flash TWRP, reboot recovery to make sure it sticks.
- Flash Magisk for root.
- Wipe dalvik and reboot system.
You will have the latest stable OOS on both partitions at this point! I literally just did this yesterday. Good luck!
Click to expand...
Click to collapse
Thank you but how can I flash if my bootloader is locked? Everything I try fails.
I guess the real question is: How can I get the phone to turn on OEM UNLOCK so I can fastboot unlock the Bootloader if it wont boot up the OS?
Is there a way to fix it via the msmdownload tool? Custom file maybe? I've tried the files 9.0.11 & 12 OOS files and all I get is the boot screen white ball logo circling the red ball - stuck in loop and same with stock t-mobile rom.
My friend, sounds like you need to restore your EFS partitions
... I'm trying to figure out how the hell you successfully flashed MSM tool in EDL mode and not have ALL your partitions restored. That tool is supposed to literally write the phone as it came out of the box. Also I think there are different MSM tools for each device respectively, you did use the T-Mobile one right?
Causical said:
My friend, sounds like you need to restore your EFS partitions
... I'm trying to figure out how the hell you successfully flashed MSM tool in EDL mode and not have ALL your partitions restored. That tool is supposed to literally write the phone as it came out of the box. Also I think there are different MSM tools for each device respectively, you did use the T-Mobile one right?
Click to expand...
Click to collapse
My thoughts exactly. So, when it was on LOS I erased the persist partition and that really messed things up. So yes, how can I restore the partition back with a locked bootloader? Every time I've used MSM tool it fixes everything. This time no such luck. I flashed 9.0.11 & 12 and then I did the T-Mobile version. All only boot to the boot screen and hang. In doing so, I wasn't thinking if that failed and it locks the bootloader, then what? I saw an old video somewhere on a oneplus 2 or 3 where the person used the msm tool 3.0 and fixed a bricked locked bootloader phone. Similar to the fastboot method of reformatting. In the msm tool folder he had all the image files for all the partitions not sure if that the same thing as msm tool 4.0 with just one ops image file?
Anyway, is there a way to unlock the bootloader without booting into the OS? Or a way to restore the partitions via msm tool?
defcondoc said:
My thoughts exactly. So, when it was on LOS I erased the persist partition and that really messed things up. So yes, how can I restore the partition back with a locked bootloader? Every time I've used MSM tool it fixes everything. This time no such luck. I flashed 9.0.11 & 12 and then I did the T-Mobile version. All only boot to the boot screen and hang. In doing so, I wasn't thinking if that failed and it locks the bootloader, then what? I saw an old video somewhere on a oneplus 2 or 3 where the person used the msm tool 3.0 and fixed a bricked locked bootloader phone. Similar to the fastboot method of reformatting. In the msm tool folder he had all the image files for all the partitions not sure if that the same thing as msm tool 4.0 with just one ops image file?
Anyway, is there a way to unlock the bootloader without booting into the OS? Or a way to restore the partitions via msm tool?
Click to expand...
Click to collapse
Try this and tell me if it works.
Have you tried this dudes stuff? https://forum.xda-developers.com/oneplus-6t/how-to/op6t-collection-unbrick-tools-t3914746
... Not even sure what it is really, just says collection of unbrick tools.
_Masked_ said:
Try this and tell me if it works.
Click to expand...
Click to collapse
Yes, I did try that. That is what I just flashed with the msm tool. Gets stuck on the OOS boot animation.
Causical said:
Have you tried this dudes stuff? https://forum.xda-developers.com/oneplus-6t/how-to/op6t-collection-unbrick-tools-t3914746
... Not even sure what it is really, just says collection of unbrick tools.
Click to expand...
Click to collapse
Looks like the MSM tool. I'm going to give 9.0.13 a try but I'm thinking I may have the same problem.
Causical said:
Have you tried this dudes stuff? https://forum.xda-developers.com/oneplus-6t/how-to/op6t-collection-unbrick-tools-t3914746
... Not even sure what it is really, just says collection of unbrick tools.
Click to expand...
Click to collapse
Tried 9.0.13. Still gets stuck on OOS boot animation screen. There's got to be something to flash to fix this.
So you're booting EDL mode then flashing the MSM tool that exactly matches the way your phone came stock? At this point I would discontinue trying to convert it to international or upgrade the OS to a more recent version or any of that. I would focus on strictly flashing it to exactly the way you bought it.
Causical said:
So you're booting EDL mode then flashing the MSM tool that exactly matches the way your phone came stock? At this point I would discontinue trying to convert it to international or upgrade the OS to a more recent version or any of that. I would focus on strictly flashing it to exactly the way you bought it.
Click to expand...
Click to collapse
Yes. I did flash the stock T-Mobile ROM via the MSM tool. Freezes at the pink T-Mobile boot screen. Pretty sure the partitions need to be fixed but I thought the MSM tool would do that? I guess not. Is there a more advanced MSM tool where I can see what's being partitioned or is the MSM tool not doing any partitioning and that's why the phone is having the boot problem?
defcondoc said:
Yes. I did flash the stock T-Mobile ROM via the MSM tool. Freezes at the pink T-Mobile boot screen. Pretty sure the partitions need to be fixed but I thought the MSM tool would do that? I guess not. Is there a more advanced MSM tool where I can see what's being partitioned or is the MSM tool not doing any partitioning and that's why the phone is having the boot problem?
Click to expand...
Click to collapse
I know this is a stupid question but have you tried a factory reset in recovery mode? I know its a stupid question but I did not see it asked or noted.
Scott said:
I know this is a stupid question but have you tried a factory reset in recovery mode? I know its a stupid question but I did not see it asked or noted.
Click to expand...
Click to collapse
No stupid questions and I don't mind repeating answers to questions. I have tried that, but it does nothing. I get wipe cache or reboot to fastboot or reboot to recovery. When I choose system wipe, it takes 1 second to finish. It reboots and it gets stuck on the boot screen. Ever since persist partition was deleted it just freezes on startup and now that the bootloader is locked I cant seem to get anything to work. MSM tool I thought was supposed to fix this sort of thing but it has failed. Someone must know a way to get back into the OS so I can turn on OEM Unlock.
How do you know your bootloader is locked?
Causical said:
How do you know your bootloader is locked?
Click to expand...
Click to collapse
Fastboot says bootloader is locked. Shows it on the fastboot screen. Wont let me transfer any files from pc to phone. I can start the transfer process but it fails.
defcondoc said:
Fastboot says bootloader is locked. Shows it on the fastboot screen. Wont let me transfer any files from pc to phone. I can start the transfer process but it fails.
Click to expand...
Click to collapse
So you're able to enter EDL mode with a locked bootloader? How do you know your computer is seeing your device in EDL mode?
I'm going to place this here for myself for now. I'm just trying to understand your situation a little better, but this is just for later.... maybe, depending on your answer. https://forum.xda-developers.com/an...how-to-reboot-to-edl-fastboot-t3394292/page12
ALSO; If you don't mind can you link the thread that contains the original discussion where your problem began?
Causical said:
So you're able to enter EDL mode with a locked bootloader? How do you know your computer is seeing your device in EDL mode?
I'm going to place this here for myself for now. I'm just trying to understand your situation a little better, but this is just for later.... maybe, depending on your answer. https://forum.xda-developers.com/an...how-to-reboot-to-edl-fastboot-t3394292/page12
ALSO; If you don't mind can you link the thread that contains the original discussion where your problem began?
Click to expand...
Click to collapse
The point of EDL is to get around any restrictions or issues with the device, so yes, you can boot to EDL while locked. Your link will not help much because he can already get to EDL. Not to mention he will have no ADB access. Whatever he does, he has to fix it in EDL.
OP: Are you up and running yet? I am willing to try copying out my partition and sending to you.
Let me know...
---------- Post added at 08:12 PM ---------- Previous post was at 08:08 PM ----------
Wait, I just realized that my persist.img would not work because he has no way to flash it.
Nevermind.