Related
Basically I unlocked bootloader and tried to load ROM. I tried the Desire and Cynagen. I was not successful at either. I manage to do a factory reset and the phone is working, except my wi-fi is shot, and when i recieve the initial OTA update it starts to download and then stops and I get the triangle of death as I call it with the lil android guy. I realy dont know what the hell Im doing and I need inch by inch restoring ROM for dummies instruction. I would like to go back to stock.I have been in threads but i get lost on certain things. I dont know what a adb is or how to acess it. I did read the noobies guide.. Please help as I am ready to chuck this thing out the window, i love my N1
I have searched the ORIGINAL SHIPPING TUTORIAL
and one other thread but i guess i cant post links.
please help!!!
do a search for adb for dummies on this site. it should help
Buck Shot said:
Basically I unlocked bootloader and tried to load ROM. I tried the Desire and Cynagen. I was not successful at either. I manage to do a factory reset and the phone is working, except my wi-fi is shot, and when i recieve the initial OTA update it starts to download and then stops and I get the triangle of death as I call it with the lil android guy. I realy dont know what the hell Im doing and I need inch by inch restoring ROM for dummies instruction. I would like to go back to stock.I have been in threads but i get lost on certain things. I dont know what a adb is or how to acess it. I did read the noobies guide.. Please help as I am ready to chuck this thing out the window, i love my N1
I have searched the ORIGINAL SHIPPING TUTORIAL
and one other thread but i guess i cant post links.
please help!!!
Click to expand...
Click to collapse
did you try to load rom in the recovery img? This also happened to me (triangle with the android guy) and I thought I couldnt flash custom roms. For some reason the regular reboot to recovery mode gives me the triangle of death as you call it.
I got around this by loading in into bootloader mode then going to my command console, getting to my skd tools folder, and then typing
fastboot boot (whatever recovery img you used)
Then everything worked perfectly.
They are going to move this to General....
You did not follow the steps correctly it sounds.
Did you Load Amon Ras Recovery?
IF YES,
GO into Recovery
WIPE data
Flash Cyanogen's Latest ROM
Flash Google Apps available on Cyanogen's front page Post
In future ALWAYS nandroid Backup...
If you did not load Amon Ra's Recovery, you should go do this from fastboot.
I'll try to explain it to you:
1. The Bootloader is unlocked (you see the open lock at the first screen)? If you don't see the lock this is the first you should do or send it directly in for repair!
2. Then you have to flash the Recovery ROM (http://forum.xda-developers.com/showthread.php?t=611829) This you need to flash an update.zip Exact instalation guide is in the Link.
3. The ROM. If you want Stock then here you'll find it as an update.zip: http://android.modaco.com/content/g...-online-kitchen-optional-root-insecure-himem/
Choose one without includet Radio ROM!!! (See below why!)
4. Copy the ROM to your SD Card Root
5. Go into Recovery ROM (Vol Down with Power and then select recovery with the Volume button). There you select wipe and choose the first entry there (wipe data and cache)
6. Stay in Recovery ROM and selct Flash from update.zip and select the update.zip. Wait until everything is done and you are promted to reset your N1.
(DON'T MESS AROUND WITH THE RADIO ROM IF YOU DON'T KNOW EXACTLY WHAT YOU ARE DOING. DON'T UNDERSTAND ME WRONG, I THINK YOU HAVE NO GLIMPS WHAT YOU ARE DOING SO BETTER LEAVE THE RADIO ROM ALONE!!! YOU MAY BRICK (DESTROY) YOUR PHONE WITH IT!!! If you dont believe: http://android.modaco.com/content/g...odaco-com/303716/nexus-cannot-on-after-flash/)
7. There should be no 7. Everything should be fine by now.
Hope I could help.
** 100 Posts **
Stheoft u are my hero!!! Now hold do I get the multitouch update? lol sorry
DID YOU EVERY KNOW THAT UR MY HERRRRRRROOOOO
edit: i got it, im back to square one... thanks alot for all ur help
@ Buck Shot, this is a development forum... threads with question shud go in the general forum... these are making the development forum a mess....
I'll be as descriptive as possible.
I must have did a bad flash with CWM, so I tried to reflash with CWM, TWRP, and even the OEM recovery. When attempting to boot to recovery, the screen goes blank. My pc attempts to connect every drive letter I've got when I plug in the usb. Among which, I can access an image folder on the device. Can't figure out how a bad recovery flash does this, but I can't find a fix for the life of me. Phone works as it should. My problem is anything involving recovery will give me a black screen, so factory wipe will not work.
Any ideas would be well appreciated.
Thanks
I tried following this guide: http://forum.xda-developers.com/showthread.php?t=2471370
The program get's stuck at analyzing device and doesn't flash or download anything. It would be nice if I can perform at least a factory reset in case something wants to blow up in my face. If anyone has some ideas (ridiculous or not), feel free to let me know.
slicknessessity said:
I'll be as descriptive as possible.
I must have did a bad flash with CWM, so I tried to reflash with CWM, TWRP, and even the OEM recovery. When attempting to boot to recovery, the screen goes blank. My pc attempts to connect every drive letter I've got when I plug in the usb. Among which, I can access an image folder on the device. Can't figure out how a bad recovery flash does this, but I can't find a fix for the life of me. Phone works as it should. My problem is anything involving recovery will give me a black screen, so factory wipe will not work.
Any ideas would be well appreciated.
Thanks
Click to expand...
Click to collapse
Hey man you could try just using Flashify to flash a recovery...its a app...then boot to recovery
I tried using that method. It gives me the same thing. Maybe somewhere in the recovery location (or associated locations) seem to may have gotten damaged somehow during the bad flash? Flashing the phone completely I'm sure would do the trick. I came from the droid 4, so sbf/fastboot flash would solve all my problems. Searching around landed me to a kdz, which seemed to be an equivalent, but isn't working or maybe I'm doing something wrong? Any advice on this would be greatly appreciated.
I went and did a full flash using this method: http://forum.xda-developers.com/showthread.php?t=2448960. Since I couldn't find a recovery fix per se, I decided to flash the whole thing and start fresh (oh well).
It downgraded to 11A in the process, so the same can probably be said for 10B for compatible custom builds.
First want to say hi and that this site is full of knowledge so any help with my subject will be great.
Got a att s4 sgh-i337 phone. I rooted it before the lollipop ota update was out and everything went fine. Then the lollipop update came out and I followed one of the methods on keeping root and updating to 5.0.1 lollipop on the phone. Everything went fine with that. Still showed root status and never did the phone brick or have any issues in the updating.
At some point though, I did run triangle away because I would have the custom logo and opened padlock when the phone would boot up. I knew it wasn't a huge deal but the counter showed correct and never could just figure out how to get it to go away. Either way, I did run it and I think rebooting twice, the factory loading image came back to it. Now it shows my current status as 0 for the counter and the binary is Official.
I have not tried to load any roms or nothing like this to the phone, just followed the instructions to give it root access so I could run a few different apps and adaway for when I listen to Spotify.
One day, I was trying to install a new version of Words with Friends and it failed because I think wwf was open, but I did go back and install it. For some reason now, my phone never notifies my with a wwf notification when somebody plays me. Every now and then, it might pop up when I restart the phone but that is it. I don't think facebook notifies me everytime also but was more worried about words with friends.
Searching google, it says to go into recovery mode and flash the cache of the phone there. I have done the cache memory in the phone but that has not fixed my problem. When trying to go to recovery, it never works, it would always show, recovery booting and then load the phone up as normal.
I have download quick boot and rom manager since they all have an option to boot into recovery rather than pressing the buttons but it always does the same thing. Reading the web though, it seemed like I needed to install a different recovery than the factory I guess, so using rom manager, I tried twrp and that didn't work so I installed ClockworldMod 6.0.4.7. Rom manager shows that as the current recovery method.
When I try to boot into recovery, it still shows that recovery is booting and then goes straight to loading the phone as it should normally.
Now though, every time I restart my phone, it says recovery is trying to boot but never does.
How do I fix my phone to be able to boot into recovery and it not try to boot every time it powers on. I have tried searching google but I just just can find an answer to my direct problem. I know how to hold the buttons and go to recovery but does not work, and I also know how to get to it from the different app programs(rom manager and quick boot) but they do not work either. It would be nice to get the wwf notifications to work properly again also.
If you need any information from my phone, please ask. Thanks for any help on my matter,
Charlie
Odin stock and start over.
Apparently, you are not aware that the boot loader is locked, preventing the installation of a custom kernel. You can not use twrp, or rom manager. Rom manager itself may cause issues.
I agree you should flash back to stock and start over to get a clean install. Hopefully, this will solve the issues with notifications as well. You can use the "[GUIDE]Odin to Stock, Updating, Rooting, and Installing Safestrap" by guut13 in the general forum for files and instructions.
creepyncrawly said:
Apparently, you are not aware that the boot loader is locked, preventing the installation of a custom kernel. You can not use twrp, or rom manager. Rom manager itself may cause issues.
I agree you should flash back to stock and start over to get a clean install. Hopefully, this will solve the issues with notifications as well. You can use the "[GUIDE]Odin to Stock, Updating, Rooting, and Installing Safestrap" by guut13 in the general forum for files and instructions.
Click to expand...
Click to collapse
Thanks for the replies guys, I really don't know a whole lot about rooting other than following instructions about it. I was unaware you could not use the twrp or cwr as a recovery. My recovery did not work before so that is why I was trying to install those. I knew you could not install custom roms but I did not know that you could not use rom manager to install custom recoveries.
I appreciate the help so far and I will look into that thread you mentioned. I haven't read it but will this take me back to stock lollipop 5.0.1 and I just reinstall apps or will I have to re-root the phone.
Charlie
please delete, sorry
Charlie
You have to go back to 4.4.4, to the nb1 base, root with towelroot, and then use the keeproot method to get back to 5.0.1 rooted. The instructions are in the guide, and also a link to the keeproot thread is there.
By the way, for future reference, questions, help and troubleshooting issues should go in the Q&A forum, not the general forum.
not having any luck
Ok guys,
I am trying to follow the guide but not having much luck.
I downloaded the I337UCUFNB1_4.4_Stock_Odin_tar and put it in the AP Odin file. I'm not sure if I should be using it or the other file named I337UCUFNB1_4.4_Rootable_Stock_Odin_tar to begin with. The instructions said to use the first one so that is the one I was trying to use.
After putting the first file in the AP slot of Odin and hitting start, it begins to try to do it's thing and then says it fails!
What do I do now? Am I doing something wrong or what because I'm trying to follow instructions but not having much luck.
Please help. Sorry for posting in the wrong area also in the beginning.
Charlie
I'm screwed
Now when I turn my phone on, it says Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again?
doing better now
Pretty sure I got it going finally. I changed cords and then changed ports on my computer and it finally did go back to stock without an error. I'm currently back on Lollipop and rooted so now is the fun of reinstalling contact info and anything else. So far I have not rebooted but it was not showing the recovery booting option when it did reboot. Hoping my notifications work properly now also!
Thanks!!!
Charlie
basically i got stuck cause i cnt boot into the recovery without quick boot , after i restored a old backup , but i forgot it had a fingerprint with a pattern so i did the google FRP to wipe it , it gave me access to the recovery witch i have RC8 twrp but formatting and reinstalling does nothing it just keeps allowing it to do everything but when i try to boot to the normal system it keeps putting me back into recovery ?!?
plzz if anyone know of anything i can do let me know the phone was already rooted and oem unlocked but atm im still just trying to get it back to normal =/
Try this.. Turn off the phone and press and hold volume down and power until you see the Lg logo. Release only the power button for 1 sec and then repress. Once you see the white factory reset screen you can release the buttons. Scroll to yes and then again on the next screen. This will boot to twrp. You need to enter recovery this way and no other way. Once in twrp restore your backup. After finished do.not boot yet. Go to mount and make sure system is mounted then go to the twrp file manager and go to data/system/users/0/fpdata and delete the db file. Then back out to data/system/users/0 and deletes settings_fingerprints.xml and then back out to data/system/users and delete the three files that say locksettings.db. This will remove your Lock screen pin/pattern and allow you to setup new fingerprints. Now try to boot into system.
the thing is when i did the format though googles crap , it delete all my files on the system and my sd card so there went my backup D= , do u have a plan backup or anything else i can do atm i am pretty screwed , if u or anyoone else helps me fix this i dont care about giving 10$ , im quite sad about this , i already can install roms but since it wont get past the boot and goes into recovery its not letting it install anyfile , i can get into the terminal of twrp and the file manager within it but i cant find anything like that , i dunno if its in a different spot or anything
i tryed what u said and nothing happends , i did what u said and it keep going into the recovery , i cant seem to get it to boot to that menu
even a bacup of the system boot may help im worryed i may just have briked my phone but i can get into the twrp recover menu and nothing else besides the fastboot witch its unlocked
im keep trying many things , i dunno if anyone has a backup of the tmobile stock recovery boot or any of those backups made when doing the rooting process , i did have them but stupid thing formatted n i lost everything =/
or if somone can backup there system image boot file and the recovery maybe flashing that may help
if anyone thinks they can help me add me on skype mirajane.takami its a old gaming name i used to use , but im taking my surface tablet to work n gonna keep reshearching ways to fix this cause i have my pc n adb aswell all other tools =/ ima have a spare i can use to chat
just uploaded a vid to show anyone exactly whats happening . this is right after i did a full wipe as well as a factory default though twrp and installed a stock rom i found on here , it just boots to recovery without me doing anything and does that whole flash thing? im not mking it go into recovery its doing it by its self --> vid https://youtu.be/kGQYA0SgdjE
X_wretched_egg_x said:
just uploaded a vid to show anyone exactly whats happening . this is right after i did a full wipe as well as a factory default though twrp and installed a stock rom i found on here , it just boots to recovery without me doing anything and does that whole flash thing? im not mking it go into recovery its doing it by its self --> vid https://youtu.be/kGQYA0SgdjE
Click to expand...
Click to collapse
Have you tried flashing a Rom in the Development Section? You can also go to jcadduono how to root thread. He has a stock img you can flash using TWRP's "Flash Img" feature.
Double0EK said:
Have you tried flashing a Rom in the Development Section? You can also go to jcadduono how to root thread. He has a stock img you can flash using TWRP's "Flash Img" feature.
Click to expand...
Click to collapse
yea i already been rooted and had been flashing roms , but i couldent get into recovery no matter how much i read the instuctions online how to get there with the v20 for some reson it wouldent work , so i restored a backup i had but forgot i had a figerprent on there , so i did tho onlything i could think of cause i could get adb cause i couldent get into the phone n have acces to it , so i did that google fps thing and it let me trigger the factory default reset but it messed witht he phone and it formatted all my data with sucks but o well on that the problem is it delete my backups , so i was like ok just wipe littery everything n start over but this time around after i installed the same rom i had been using it just gives me the boot in the video , i also tryed older roms ive done before on this device but i alwasy get the same results ? i just wanna get it fixed bad i still have access to twrp so i think theres still hope i dont care if i have to pay to get somone to help me honestly i just want it fixed
i didnt know they added that feature into twrp , i found the files i used to root n unlock the bootloader , but i cant find the system.img or the boot.img im thinking those may help if i had the right files i got the recovery.img from there n flaashed it on the recovery section , but nothing changed
did everything in this post http://forum.xda-developers.com/showpost.php?p=69685809&postcount=146
but at the end of it there was no system files in the folder after ? dunno if that may be the cause?
just fixed it /T.T/ this guy posted how he fixed it for himself a while back , ima totally donate to him for this >.</
http://forum.xda-developers.com/v20/how-to/how-fixed-bricked-lg-v20-t3501310#post69705470
this thread can be closed now or just be up if anyone ever runs into a situation like this.
it really saved my phone
Started off by unlocking the bootloader on the December update (just got device the other day)
Used @munchy guide to install twrp and root the device
everything looked great
backed up stock
flashed everything but internal storage
installed lastest version of AOSiP
crashed during install so I thought ok, bad download. did a restore and got an error that system wasn't mounted. unchecked the box under mount, and restored. I reboot and all hell has broken loose. Fore close left and right. I go back to try and get to TWRP, and it's stock Recovery.
Follow guide again and get back into TWRP. I see that all my stuff is still there. So I do some reading and saw some folks having similar problems with TWRP not sticking, so I find some instructions in the TWRP thread that I need to flash the TWRP image to both slots, run the install patcher and should be all set. I do that...wipe again, restore and now I am in a continuous bootloop. I tried to switch slots, do a restore on the other slot....bootloop.
I feel really stupid and really bummed out that even with all my years and experience, I somehow found myself in this noob trap. Is anyone able to help me at least get back to just stock? All I really want at this point is to be back on stock with root so I can run an ad blocker. Thanks everyone
Mods - could you please close? I know have a hardware issue (lol), a rubber ring on the inside of USB port has come out and wedged inside the port, rendering the device defective. Thank you