Related
Hey guys i used rom manager to flash clockwork recovery but i keep on getting the red triangle and then an error message after clicking power/volume up and cant load zips like bacon bits.
So i think this is a recovery image problem so how can i load it properly...
thanks
Go back into Rom manager and reflash the recovery for the G2. I had to flash it twice. If it gives you a list of other phones then I suggest press Menu and clear download cache. Turn off phone and then power back on. Go back into Rom Manager and try to flash recovery. You should see G2 only. If not make sure you have good connection. I suggest Wifi.
Sent from my T-Mobile G2 using XDA App
Ya i have done that a couple times to no avail.
The only option i see is tmobile g2 but for some reason i just cant get the recovery to work properly...
Sent you pm's
Sent from my T-Mobile G2 using Tapatalk
renn9420 said:
Sent you pm's
Sent from my T-Mobile G2 using Tapatalk
Click to expand...
Click to collapse
I am having the same issue. the device is permanently rooted, i have installed ROM Manager, Only G2 comes up when i hit flash recovery, once selected CWM is installed successfully but when i reboot into recovery all i see is red triangle with !.
Is there another way to install clockwork mod or any other recovery image?
I'm having the same problem. I've looked for a fix but havent found anything. Is there a fix or a way to manually install Clockwork Recovery???
I must sound like a broken record but never ever leave the ROM Manager app without having flashed the recovery WITHIN THREE seconds. If it takes more than 6 seconds its broken. Just keep flashinng it so you get "successfully flashed like one a couple seconds after you select the phone model.
Besides, thats the easy way. Real men do it in fastboot. I liken flashing recovery to taking a shower.... rom manager = taking a shower in recycled ****-water in boston harbor (said **** emanating upcoast from NYC). fastboot = asian massage parlor quality steam bath hot sauna little lady and happiness. Pick your "recovery" wisely.... its the only thing to save you when you need it most.
If you have adb set up -- look in your tools or platform tools folder and tell me if you ihave a Fastboot.exe in that folder. If you do... then you are in luck. Connect your phone and put it in fastboot mode -- (white screen with FASTBOOT USB text)
"fastboot devices"
(should return a H-sometrhing. If it doesnt return anything you need to fix your sdk/fb setup)
second.... you want to erase recovery fully --
"fastboot erase recovery"
itll do it in like .003 seconds
third -- download the correct recovery and extract it or place the .img file (in the same folder as your fastboot/fadb files... (may want to rename it something easy like "recovery.img" (must be xxxxxx.img)
then do
"fastboot flash recovery xxxxxxx.img"
itll flash it in maybe three seconds.
Then "fastboot reboot" or get phone into recovery and check it.... that is the best way to flash your recovery. cleanest possible way.
this is the last time i post about fastboot. folks.... READ THE DAMN WIKIS. stop thinking we are sitting around waiting for you to put up your problem. jeez... the intelligence level of this forum has dropped from super-hackoid to Idiocracy in one year.
just read the wiki. this is very elementary. very very elementary. Like kids should learn this before they learn to tell time on a two-handed clock.
Just checking, but you do have S-OFF, right ? Because you need S-OFF to flash a custom recovery, root on its own is not enough.
You also mentioned that you hit Power and Volume "UP." Correct combo to access recovery is Power and Volume Down.
No need to bump ancient threads like this.
To clear any confusion though:
Power + Vol down will get you to bootloader whn your phone is off, but if you are in stock recovery, Power + Vol UP will get to the recovery menu options.
-Nipqer
I rooted the tablet and it updated fine. I then reboot it and it is now stuck in boot loop. It says bootloader version unknown when I press power and volume button. What do I do?
Update. I have been able to successfully make my tab bootloop three times and three times have brought it back to life. All three times it has been because of an app that I guess is not compatible with 3.1. Because of my low thread post count I can't provide links or post into the development forum but my method has worked all 3 times.
A little background. First time I hadn't changed recovery and it was a bit easier. Second and third times I had cwm recovery and it was harder because adb wasn't recognizing my tablet.
First you need to have adb installed into your computer. I installed the sdk and then added the adb option. I then went into this post in the development forum: Re: [Solution] HC 3.1 OTA Difficulties 13% + Stock ODIN. In that post you'll find the Odin application for your computer and the appropriate PDA file for your tab. The PDA file contains the stock recovery, bootloader, and rom.
Whether you have stock recovery or cwm the next instructions are the same.
1. Connect the tab to computer.
2. Holding power button and volume down button, get into screen where you can choose fastboot or download mode. Choose download mode.
3. Once in download mode, on your computer open the Odin application.
4. Where it says PDA file, click the browse option to look for the PDA file you downloaded. Open it and it will be listed in the PDA section. Also the box next to PDA will be checked. Don't change any other settings.
5. Now you can press the button to run Odin. Don't touch tablet until it's done.
6. Now you can try rebooting it but it will still bootloop. Difference now is that you can adb into it.
7. With tab connected, go into cmd mode on your computer and type: adb reboot recovery
8. The tablet should reboot into stock recovery. From there wipe data and cache.
9. Reboot tablet and it should work! The tablet will be reverted back to 3.0.1. Just run the update again and enjoy.
Couple of notes. I tried the fastboot method mentioned in some posts but it never worked for me. This method that I've done has been flawless for me. I do have I/O version so I'm not sure if it is different from retail version. I think bootloops occur because some apps are not ready, stable, or compatible with 3.1. Something in the bootloader and recovery has changed in 3.1, whether it is changed via the apps or the update itself I'm not sure. I do know that the problem apps work great in 3.0.1, never causing bootloops, thus my conclusions.
Same thing happened to me. Fastboot -w did the trick. It wipes the tablet though.
Thanks. It's weird. My tablet was rooted but I hadn't changed anything. I ended up connecting it to my pc, adb'd into recovery. I wiped cache and data and it eventually worked. Only thing was that it went back to 3.0.1. I then did the update again and now it's working flawlessly with 3.1
Sent from my PC36100 using XDA Premium App
Help needed Samsung galaxy tab 10.1 stuck in boot loop
Hi,
I faced a similar situation, I upgraded by Samsung Galaxy Tab 10.1 to HC 3.1 and it had been working fine .
Unfortunately I did not use it for the past 2 days, the battery drained out and after that I tried to recharge and start itup.
It goes in a boot loop .
And also display's Entering upload mode, cause undefined .
Is fastboot the only way to recover the system now .
saviressej said:
Thanks. It's weird. My tablet was rooted but I hadn't changed anything. I ended up connecting it to my pc, adb'd into recovery. I wiped cache and data and it eventually worked. Only thing was that it went back to 3.0.1. I then did the update again and now it's working flawlessly with 3.1
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
How did you ADB it while it was in a bootloop?..
I'm stuck with this same issue! Everything was fine, I was on version 3.1 and I had rebooted it several times. Then one time it just got stuck on a bootloop and I can't figure out how to fix it. This is the google i/o version and I haven't done anything to it other than update to version 3.1.
I've been googling for an hour or so, but I have no idea what i'm suppose to be looking for. =\
you can recover.
i have posted detailed instructions in the OTA thread on xda.
sramasub said:
Hi,
I faced a similar situation, I upgraded by Samsung Galaxy Tab 10.1 to HC 3.1 and it had been working fine .
Unfortunately I did not use it for the past 2 days, the battery drained out and after that I tried to recharge and start itup.
It goes in a boot loop .
And also display's Entering upload mode, cause undefined .
Is fastboot the only way to recover the system now .
Click to expand...
Click to collapse
+1, i have the same problem. drained battery, recharged, stuck in boot loop. also got the "entering upload mode; cause undefined" message too.
I experienced the "upload mode / boot loop" problem a couple days ago and wrestled with it for hours. I finally found a combination of things to do that would allow me to enter fastboot to fix the issue, see the following post:
http://forum.xda-developers.com/showpost.php?p=14832831&postcount=122
Some of the steps may not be required, but what I listed should get you into the bootloader without issue. Once inside, simply do a "fastboot -w" to fix the bootloop. Interestingly, after doing a fastboot wipe I am now able to enter the bootloader without all of the complicated gymnastics listed in my post above. It doesn't quite make sense to me, but it's certainly the case.
_avatar said:
I experienced the "upload mode / boot loop" problem a couple days ago and wrestled with it for hours. I finally found a combination of things to do that would allow me to enter fastboot to fix the issue, see the following post:
http://forum.xda-developers.com/showpost.php?p=14832831&postcount=122
Some of the steps may not be required, but what I listed should get you into the bootloader without issue. Once inside, simply do a "fastboot -w" to fix the bootloop. Interestingly, after doing a fastboot wipe I am now able to enter the bootloader without all of the complicated gymnastics listed in my post above. It doesn't quite make sense to me, but it's certainly the case.
Click to expand...
Click to collapse
Yeah, I found your post a couple days ago, but couldn't get it to work. Once plugged into the wall charger, I couldn't get the charging icon to show up. I've tapped the power button, held it down for half a second, a full second, several seconds... it either does nothing, or tries to boot up.
I was able to get into Odin3 download mode and flash a ROM (see this thread: http://forum.xda-developers.com/showthread.php?t=1130216#2), but now my USB doesn't work and adb won't recognize it, so as a development device it's not very useful to me. I can't seem to get into the bootloader so I can't flash with adb or fastboot (when I boot into USB mode, adb doesn't recognize the device). I need to figure out how to flash an original I/O image, but can't seem to figure it out...
I've also had some difficulty getting to the "charging" screen, the trick is to be patient. Make sure the device is really off, plug it in, and walk away for a good while -- like 5 minutes.
When you say you're able to get it into USB mode what does that mean? Sounds like you are actually able to get it into fastboot mode. What operating system are you running? On my Mac the fastboot binaries I found floating around the net didn't work, I had to compile one from source. If you're able to get into fastboot mode but it's not detecting your device, and you have a Mac, I can send you the version I compiled from AOSP and you can try that. Let me know...
Try this...
http://forum.xda-developers.com/showthread.php?p=14791689#post14791689
Works for this guys.
I have a solution for the bootloop in my first post.
Sent from my GT-P7510 using XDA Premium App
I had a similar problem. Looks like Clockwork recovery can sometimes trash your /data partition and its format/wipe option won't fix it. I recovered by booting into stock recovery and formatting /data from there. Be forewarned that you'll lose your "sdcard," which really lives on /data.
Nice guide, thanks!
Hello all,
Any help with this would be seriously appreciated. I rooted my Nexus 10 a while back, maybe two years ago. I'm not very proficient with this stuff. Anyhow I decided to do the OTA upgrade to 5.0...I was concerned something would go wrong unless I went to stock first, but I read that the only thing that would happen is root would be removed.
Anyhow, the tablet appears stuck while booting. I see the Google screen first with the unlocked indicator on the bottom. A few seconds later is the Android logo on its back, a red triangle over it with an exclamation point and "no command" written below". It stays that way for a minute or so, tries to reboot and goes back to the no command screen. I can't even power off, when I try to do so it just powers back on by itself and ends up at the no command screen again.
I tried booting into recovery (power, volume up, volume down). My options from here are either Start, Restart Bootloader, Recovery Mode or Power Off. Every option I choose leads to the No Command Screen (except power off, which powers off). No idea what to do from here.
Any help at all would be appreciated. As you can probably tell I don't have much experience with this and just wanted to go back to unrooted stock. If you have advice, please be clear. I can follow directions well enough, just don't have much experience here. Thanks in advance.
Same here, bootloop.
Same thing here. A seemingly short download of Lollipop (even though I have 50Mbs internet). Installation, reboot, and now it loops endlessly. I can get to the bootloader or into Download mode, but that's all. Recovery mode just reboots. I was rooted and had TWRP installed. Other than that, I was running stock 4.4.4.
I've rooted all my devices, and installed various ROM's on several devices. I have the full ADB installation. I have the Nexus Root Toolkit installed. The problem is, the device will not show up under "Devices" on the computer itself. I've installed every USB driver there is (and uninstalled each one after it does not work, so no I do not have several USB drivers installed). Of course nothing shows up using "adb devices" either. Nexus Root Toolkit also cannot find any devices. I've read everything on this subject I can find, and there are no answers out there. Anyone have ANY ideas??
Thanks
Guys, if your device is connected in fastboot (try "fastboot devices") then you can flash roms or recovery (and then flash rom) from there. There are multiple threads with the same problems out there which were fixed. E.g: http://forum.xda-developers.com/nexus-10/help/bricked-t2948546
In my example, I flashed TWRP recovery from fastboot, then installed custom ROM from recovery (official ROM failed to install for some reason). Try this, it might help.
danweis said:
Same thing here. A seemingly short download of Lollipop (even though I have 50Mbs internet). Installation, reboot, and now it loops endlessly. I can get to the bootloader or into Download mode, but that's all. Recovery mode just reboots. I was rooted and had TWRP installed. Other than that, I was running stock 4.4.4.
I've rooted all my devices, and installed various ROM's on several devices. I have the full ADB installation. I have the Nexus Root Toolkit installed. The problem is, the device will not show up under "Devices" on the computer itself. I've installed every USB driver there is (and uninstalled each one after it does not work, so no I do not have several USB drivers installed). Of course nothing shows up using "adb devices" either. Nexus Root Toolkit also cannot find any devices. I've read everything on this subject I can find, and there are no answers out there. Anyone have ANY ideas??
Thanks
Click to expand...
Click to collapse
Go to Fastboot mode (pwr+both volumes), Than select recovery after a while an android with Exclamation mark appears which is a stock recovery screen. To access the stock recovery menu press and hold power than press one of the volume keys so the menu will appear. Than do a factory reset and clear caches. You can than reboot and wait for boot animation to finish (it wont take long this time) and you will boot.
If this doesnt work you can flash a stock factory image easily from fastboot again.
Aresmar said:
Go to Fastboot mode (pwr+both volumes), Than select recovery after a while an android with Exclamation mark appears which is a stock recovery screen. To access the stock recovery menu press and hold power than press one of the volume keys so the menu will appear. Than do a factory reset and clear caches. You can than reboot and wait for boot animation to finish (it wont take long this time) and you will boot.
If this doesnt work you can flash a stock factory image easily from fastboot again.
Click to expand...
Click to collapse
I also had the same problem... I followed these instructions and now my Nexus 10 can boot normally (it took a long time to boot).
Only problem is all my data was deleted.... stup*d f*cking sh*t!!!!!!!
Hi, I don't have enough posts to ask this in the actual DirtySanta thread.
I meticulously followed the steps in the DirtySanta thread making sure I had all the correct software, all the pre-requisites, all files in my ADB folder (except SuperSU zip, which is on the SD card on the phone). Suffice it to say that I did all the steps exactly as written in the guide. I was prompted when to run the next batch files each time, etc. Entered the proper commands in the terminal utility, and so on. Everything as written.
After clicking on step3.bat, the phone immediately rebooted to a Fastboot screen. In the meantime, the batch files disappeared off my desktop.
So, for the past 15 minutes or so the phone has been sitting on Fastboot and vibrating away.
Here's what I see in the small Fastboot screen:
Fastboot Mode (in red)
stuff like Product_name, Variant, HW_Version, etc. up until it says LOCK_STATE.
Ok, after all of that basic stuff, it says:
[1090]
[1140] Fastboot mode started
[1670] fastboot: processing commands
[17600] usb_read() transaction failed; txn_status= -1
[17650] usb_read: DONE: ERROR len=64
[1700] fastboot: oops!
[17750] fastboot: processing commands
And that's where it sits, doing seemingly nothing and vibrating away.
Can anyone assist?
Try a different usb port. then rerun step 3.
me2151 said:
Try a different usb port. then rerun step 3.
Click to expand...
Click to collapse
Will do...was just thinking of doing that since it said "usb read error". Will report back.
Heyitsrick said:
Will do...was just thinking of doing that since it said "usb read error". Will report back.
Click to expand...
Click to collapse
First off, a big thanks for helping me.
Update: OK, changing the USB port worked I re-ran Step3.bat. I have made it through getting to TWRP, and have done these steps:
Verizon(VS995) and ATT(H910):
4.1) Flash SuperSU.zip
4.2) Go back to Main-menu > Wipe > [Format Data] > Type ?Yes?
4.3) Go back to Wipe > Advanced > Check Dalvik, Data and Cache > Slide to wipe
4.4) Go back to Main-menu > Reboot > System
So, with that all complete, it's rebooted to a Verizon screen (horizontal progress dots) and a low buzzing.
I did try what you mentioned in the guide to get over the wait time by pulling the battery, reinserting with vol down key pressed and re-attaching the USB to flash boot2.img via fastboot, but it didn't get back to fastboot after the battery/voldown/usb. It went back to the same Verizon screen after the obligatory "Corrupt" screen came on.
Can I assume that I can wait this out for 20 minutes, or did I miss something in how to interrupt this waiting period for first setup? I do want to (and know I have to) flash boot2.img.
EDIT: wasn't holding vol key down long enough to get into fastboot. Doh. Just flashed boot2.img and rebooted.
Looks like I made it! It's at the "Prepare your Phone Screen". Fingers crossed.
Heyitsrick said:
Looks like I made it! It's at the "Prepare your Phone Screen". Fingers crossed.
Click to expand...
Click to collapse
Are you still stuck?
I ran into this EXACT same issue on my brand new Verizon v20 on step 3 (both 13a and 12a firmware gave me this issue) and I had to figure out my own solution, even tho I read that 'dirty santa root' thread a thousand times front to back.... (no disrepsect to the OP/Devs of that thread btw!)
Anyways, below, is the link to my solution on my brand new Verizon v20, in case you're still stuck. I've actually reflashed (via LGUP) back to stock a couple times, then re-root/unlock to test out 13a and 12a firmwares to benchmark various battery life/performance markers for a tech site I write for. Ultimately, I have to go through the exact same steps everytime for my Verizon v20.
I know I wasn't too specific in my post below... but if you have any questions, don't hesitate to ask
https://forum.xda-developers.com/showpost.php?p=71371141&postcount=24
NegativeX said:
Are you still stuck?
I ran into this EXACT same issue on my brand new Verizon v20 on step 3 (both 13a and 12a firmware gave me this issue) and I had to figure out my own solution, even tho I read that 'dirty santa root' thread a thousand times front to back.... (no disrepsect to the OP/Devs of that thread btw!)
Anyways, below, is the link to my solution on my brand new Verizon v20, in case you're still stuck. I've actually reflashed (via LGUP) back to stock a couple times, then re-root/unlock to test out 13a and 12a firmwares to benchmark various battery life/performance markers for a tech site I write for. Ultimately, I have to go through the exact same steps everytime for my Verizon v20.
I know I wasn't too specific in my post below... but if you have any questions, don't hesitate to ask
https://forum.xda-developers.com/showpost.php?p=71371141&postcount=24
Click to expand...
Click to collapse
I read your "fix" post to see exactly where you got stuck, as I got stuck first due to the USB port not being able to work correctly and had to switch USB ports on my pc before I could re-run step3.bat.
I see now that you're talking about the long Verizon logo screen with progress dots issue after rebooting post-running step3.bat that I ran into, as well.
OK, what worked for me was much easier in the end than what you did. After step3.bat and the reboot, it would just sit there on the Verizon logo with the progress dots, as you know. There is a notation on the first page of the DirtySanta thread that in order to get around this, unplug the USB cable and remove the battery.
This is the actual note from the DirtySanta thread for Verizon users with the long Logo screen issue:
*****VERIZON USERS******
It has come to my attention that some users have encountered abnormally long first boot time(over 20 minutes before first time setup)
To resolve this issue:
Boot into bootloader by pulling the battery and reinserting it and holding VOL- and phugging in the phone. then typing:
Code:
fastboot flash boot boot2.img
fastboot reboot
**************
Click to expand...
Click to collapse
Once I removed the battery and usb cable, the phone was completely off, of course. Then, I just needed to get it back into "fastboot" on the phone, itself, in order to flash boot2.img via ADB on the PC. When the phone was on the never-ending Logo screen with progress dots, I found that ADB could see the phone ok via the adb devices command, but if I tried to flash anything at that point, it would just say something like "pending", as if it were waiting for the device to be free to flash. So, that wasn't going to work, obviously. I needed the phone to be in the flashboot screen, not the logo screen. I did a ctrl-c to cancel out of the adb flash command, and then set out to pull the battery/usb cable and then reconnect the battery, and while holding the Vol Down button reinserting the USB cable.
The first time I tried this, it booted up fine, but it went right back to the Logo screen. Doh! I figured perhaps I wasn't waiting long enough with the Volume Down button so I tried it again. What happened the first time when it rebooted to the Logo screen is I released the Volume Down button the moment the phone started to turn on (you feel the vibration). That's when it booted back to the Logo. This second time, I removed the battery again while it was on that never-ending Logo screen to power it off and disconnected the USB cable again. I put the battery back in, then with the Volume Down button pressed down, I reconnected the USB cable. The difference this time is that I did not release the Volume Down button this time UNTIL I saw it was in the Fastboot screen and not the Verizon Logo.
So, at this point the phone was on the Fastboot screen and I saw it was it was ready to go, so I initiated the ADB command to flash boot2.img. It went through its paces and once it got back to the ADB command prompt, I did an ADB Fastboot Reboot command. It rebooted, first with the obligatory corrupt warning, then the Verizon Logo and progress dots, but then after a short while I got the "Hello" screen in red and I knew it was actually going to finish. Whew! Relief! At that point I was eventually at the phone's setup screen for a new user, and I finished setting up the phone, reinstalling apps, etc.
One caveat in this: I don't know why, but even though I had gone through all the steps in "4" section of the instructions, when I checked Root, I wasn't rooted! Huh?
In other words, I had already gone through this part:
Verizon(VS995) and ATT(H910):
4.1) Flash SuperSU.zip
4.2) Go back to Main-menu > Wipe > [Format Data] > Type ?Yes?
4.3) Go back to Wipe > Advanced > Check Dalvik, Data and Cache > Slide to wipe
4.4) Go back to Main-menu > Reboot > System
Click to expand...
Click to collapse
After setting up the phone and reinstalling my apps, I opened up the SuperSU app, and it said there was no executable installed. In other words, it didn't recognize that I had flashed it in step 4.1. Perhaps flashing boot2.img overwrote that? Not sure, but at this point, I set about to figure out how to boot into TWRP Recovery on the phone (not fastboot) to flash it from there (again).
It took me a while to find the instructions on how to boot into TWRP, lol, and it's a little unnerving that before it boots to TWRPyou are warned that all your data is going to be overwritten before you can boot to it, but it did get me back into TWRP. Once in TWRP, I re-flashed Supersu-blahblah.zip and rebooted via the system reboot. (did not wipe any caches again, though).
After reboot, I checked root again, and this time after a bit SuperSu brought up the permissions screen for the Root app that I had to allow, and it brought back a successful Root message.
I then set about to do what I really wanted to do with root - bypass the Verizon entitlement check for hotspot usage, and got that working fine.
All in all, I have to say this was the diciest rooting I've ever had to go through. I guess that's because of Nougat and that there can't be (at least not yet) a "one-click" root. But man, was I worried when I was at the point where I first posted in this thread. I bought this phone as a "new-resale" (never used) phone from Swappa.com for $450, so if I bricked it, I was out of luck. But it seems to be ok now.
Heyitsrick said:
I read your "fix" post to see exactly where you got stuck, as I got stuck first due to the USB port not being able to work correctly and had to switch USB ports on my pc before I could re-run step3.bat.
I see now that you're talking about the long Verizon logo screen with progress dots issue after rebooting post-running step3.bat that I ran into, as well.
OK, what worked for me was much easier in the end than what you did. After step3.bat and the reboot, it would just sit there on the Verizon logo with the progress dots, as you know. There is a notation on the first page of the DirtySanta thread that in order to get around this, unplug the USB cable and remove the battery.
This is the actual note from the DirtySanta thread for Verizon users with the long Logo screen issue:
Once I removed the battery and usb cable, the phone was completely off, of course. Then, I just needed to get it back into "fastboot" on the phone, itself, in order to flash boot2.img via ADB on the PC. When the phone was on the never-ending Logo screen with progress dots, I found that ADB could see the phone ok via the adb devices command, but if I tried to flash anything at that point, it would just say something like "pending", as if it were waiting for the device to be free to flash. So, that wasn't going to work, obviously. I needed the phone to be in the flashboot screen, not the logo screen. I did a ctrl-c to cancel out of the adb flash command, and then set out to pull the battery/usb cable and then reconnect the battery, and while holding the Vol Down button reinserting the USB cable.
Click to expand...
Click to collapse
I saw that 'fix' and it never worked for me at the point in the rooting process I was in... sadly. You have to be able to even get to TWRP, do the SU install then format/wipe, then you can flash the boot2.img to speed up the booting process. In my case, I was never able to even get to TWRP. Trying to flash boot2.img before being able to get to TWRP, would soft brick my phone with the 'password' screen on bootup and I was never able to get around it, requiring me to LGUP back to stock and try again. Luckily I was able to still figure it out.
As you said, definitely the 'diceist' rooting process I've ever encountered... and I've been rooting phones since the original Motorola Droid 1/Milestone phone. Good times tho! Haha
NegativeX said:
I saw that 'fix' and it never worked for me at the point in the rooting process I was in... sadly. You have to be able to even get to TWRP, do the SU install then format/wipe, then you can flash the boot2.img to speed up the booting process. In my case, I was never able to even get to TWRP. Trying to flash boot2.img before being able to get to TWRP, would soft brick my phone with the 'password' screen on bootup and I was never able to get around it, requiring me to LGUP back to stock and try again. Luckily I was able to still figure it out.
As you said, definitely the 'diceist' rooting process I've ever encountered... and I've been rooting phones since the original Motorola Droid 1/Milestone phone. Good times tho! Haha
Click to expand...
Click to collapse
Late response - sorry.
There must be something we each did differently, as we both have the same phones, same carrier, same software revision (13a). I was able to get to TWRP via the button method on the phone. Didn't use ADB for that. I was presented with an ominous white screen about all files will be wiped/deleted, but when accepting that (and hoping for the best, lol), it just went to TWRP. So, again...something or some step(s) must be done differently to get to that point on your end from what I did.
I'm guessing you're through with doing the flashing on this thing, so this is all moot now.
Hey guys i actually was having the same issues as you were now however after the SU install the wipe etc i reboot to TWRP no matter what i do even when i restart through bootloader or take the battery off it keeps booting to the same place instead to the verizon wizard help please
kratos380 said:
Hey guys i actually was having the same issues as you were now however after the SU install the wipe etc i reboot to TWRP no matter what i do even when i restart through bootloader or take the battery off it keeps booting to the same place instead to the verizon wizard help please
Click to expand...
Click to collapse
Called a twrp loop. Easy fix. Been posted a lot. Look around for it
me2151 said:
Called a twrp loop. Easy fix. Been posted a lot. Look around for it
Click to expand...
Click to collapse
I have been looking for 2 days haha literally have like 30 tabs open shifting through i dont know what to do next, i backed up wiped my cache data etc installed SU which had no problems wiped again/ rebooted system and back to twrp, i read that you might need to flash a system.img but i dont know where to find one, would appreciate the help kind sir
kratos380 said:
I have been looking for 2 days haha literally have like 30 tabs open shifting through i dont know what to do next, i backed up wiped my cache data etc installed SU which had no problems wiped again/ rebooted system and back to twrp, i read that you might need to flash a system.img but i dont know where to find one, would appreciate the help kind sir
Click to expand...
Click to collapse
Look at team digitals ROM thread. Stockish one. Look at post 3. If you still can't find it I'll quote it directly later. I'm busy right now
me2151 said:
Look at team digitals ROM thread. Stockish one. Look at post 3. If you still can't find it I'll quote it directly later. I'm busy right now
Click to expand...
Click to collapse
Couldnt find it sorry im new to this forum please link it when you are free thanks again for the help much appreciated
kratos380 said:
Couldnt find it sorry im new to this forum please link it when you are free thanks again for the help much appreciated
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=70393155&postcount=3
Sorry for the constant posts but i followed the steps on that thread, deleted the misc/fota files and it stopped it going to twrp and booted to the lg logo with the black screen, i waited there for about 2-3 hours to no avail rebooted into bootloader tried the fastboot img 2 and the same thing happened it was just stuck at the lg logo now when it boots to the fastboot screen however adb doesnt recognize the device anymore but fastboot does. Is it time to kdz and start over ?
So, about 6mos ago, my Nexus 10 stopped working and I couldn't get it back working...eventually moved onto a new tablet, which now I hate....
Anyway, I figured I'd head back to my N10 because I loved it. However, one of the reasons I left it was because it was stuck in bootloop and I was pretty sure it was bricked.
The bad news, I have followed MANY, if not ALL, of the suggestions on getting it back, I just cannot get it to boot. The good news, fastboot connects with the tablet. So, some specifics:
The tablet WILL boot into fastboot and I can send commands and the tablet is unlocked (also, I believe someone said they had issues because they had an older version of ADB and Fastboot. I'm pretty sure I downloaded the 'most current' version 1.4.3). So, with that, I was able to do the fastboot erase functions, such as cache, userdata, system, etc... and then also load the bootloader (mantafm01) and also send the stock .zip file (image-mantaray-....) and the tablet appears to load everything fine. Thumbs up, right? However, when it reboots it stops at the 'erasing' android bot and will not pass that. I left the tablet in that state for a few minutes all the way up to 3 days...no success.
I also tried the above using Wugfresh only to have the same thing occur. So, basically, I am stuck at 'erasing' and I don't know what to do. I feel confident that the tablet has the ability to be brought back to life, I just cannot figure out how/why all of the attempts lead to the same issue.
What I can also tell you is that while fastboot 'sees' the tablet, the tablet does not appear as a device in "My Computer" like it normally did when connecting via USB. I am using the original USB cable and have tried on multiple computers, all to no avail. I've downloaded/installed the drivers, as instructed on many links. Also, while I can get to the 'Recovery Mode' by pressing Power, Volume Up, Volume Down, if I choose "Recovery Mode" on the tablet, it reboots and goes to the 'erasing' screen. I have tried flashing TWRP on the tablet using fastboot as well. And, sometimes, not all the time, the TWRP blue/black screen appears but it will not progress past that screen (i.e., it doesn't go into recovery).
So, if you can, please help. I believe I have followed all of the instructions, but I have to be missing something or not following something correctly. I'm stoked that it looks like it's only soft-bricked, I just can't get it un-bricked.
Thanks in advance!
Looks like you are trying hard to find a solution. I think it may be helpful if you try to manually install the o/s rather that using Wugfresh and report back any errors. See
https://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/ At step 11 I would flash the individual image files and also follow the instructions re erasing and flashing userdata.
AFAIK you will not see an Android device when using Fastboot - Android hasn't loaded at this stage.
Thanks peterk-1. Unfortunately, this does not work. I followed the steps, with the exception of the radio file as my Nexus 10 is wi-fi only. It goes through the stock image update perfectly fine and reboots itself. At that point, it's back to the moving android at the 'erasing' screen.
One thing to note with the link you provided; no where does it indicate flashing a recovery, stock or custom. Now, I've tried flashing stock, TWRP and CWM and none seem to work. TWRP comes closest with the black/blue splash screen, but will not open further.
Any other suggestions would be appreciated.
You did go to the posted link? I quote:
Step 8: We now want to wipe the device. Use the following commands in order:
........
fastboot erase recovery
............
Step 11: We will now flash the system, boot, and recovery ..........................................
fastboot flash recovery recovery.img
Unfortunately, same result...