I installed deodexed 4.2.2 stock when i was running deodexed 4.2.1 stock. i felt that it was buggy, so i went into cwrecovery and wiped it and i was about to begin reinstalling deodexed 4.2.2 again when i noticed i forgot to put it onto my phone. then i tried to use my phone, and it would be stuck at "unfortunately, system ui has stopped". it never leaves that popup, so i can't enable usb debugging. i can't use recovery mode, because when i do, the android with a triangle caution sign is there, but no options to select from. i can enter fastboot mode, but that's about it.
CM9onmyMoPho said:
I installed deodexed 4.2.2 stock when i was running deodexed 4.2.1 stock. i felt that it was buggy, so i went into cwrecovery and wiped it and i was about to begin reinstalling deodexed 4.2.2 again when i noticed i forgot to put it onto my phone. then i tried to use my phone, and it would be stuck at "unfortunately, system ui has stopped". it never leaves that popup, so i can't enable usb debugging. i can't use recovery mode, because when i do, the android with a triangle caution sign is there, but no options to select from. i can enter fastboot mode, but that's about it.
Click to expand...
Click to collapse
Reflash a factory image in fastboot, flash CWM/TWRP in fastboot, reroot and reflash the dedexed rom. Your phone isn`t even a bit bricked fortunately.
gee2012 said:
Reflash a factory image in fastboot, flash CWM/TWRP in fastboot, reroot and reflash the dedexed rom. Your phone isn`t even a bit bricked fortunately.
Click to expand...
Click to collapse
How can I reflash the factory image? and where can i find instructions? where can i find the link to download the factory image? thanks
CM9onmyMoPho said:
How can I reflash the factory image? and where can i find instructions? where can i find the link to download the factory image? thanks
Click to expand...
Click to collapse
Look in my signature line 2 and 3.
gee2012 said:
Look in my signature line 2 and 3.
Click to expand...
Click to collapse
thanks. will i lose any personal things such as photos?
CM9onmyMoPho said:
thanks. will i lose any personal things such as photos?
Click to expand...
Click to collapse
Everything will be lost. Considering your phone is bricked there is no way to pull the pictures from your device.
Edit: you might not have to flash full stock, just the system.img that will allow you to overwrite the current system and maintain your sdcard.
i do not know if this is the best place to post this considering i am brand new (i hope so) but i have a soft bricked nexus s 4g that i am trying to fix.
it was loaded with the helly bean 4.2.2 custom rom from nexus hacks (sorry no links) after the reboot it went to a black screen.
what ive tried:
odin: flashing a new rom, this resulted in odin not finding the device (usb debugging is not on and i cant turn it on)
fastboot: (i have all the files but i cant seem to get it set up, i type in adb or fastboot (no device recognized)
nexus root toolkit: (wouldnt find the device and found no options to help with usb debugging)
dfs: (couldnt read the device)
plugging in the phone to the computer: it makes the noise that it is plugged in, comes up as f drive but it is greyed out and i cant click on it (says insert disc)
clock work recovery: i did a full data wipe and required wipes cache and delvik or something along those lines: it reboots into the rom and nothing has changed.. my guess is because there is no back up of the original rom and the cfw is trash, it just wipes the bad rom back to factory and that is still a problem.
pda net: wont recognize the device
galaxy nexus toolkit: nothing useful since the usb debugging is not enabled.
ive worked for 6 hours as of last night to figure this out. i have spent most of those hours in forums and delving further into this phone then id imagined (its not mine) so if there is anyone out there that can suggest anything id appreciate it. this has got me stumped and amazed how such easy fix can really be this complicated.. i will thank any and all answers given to me
theblackrose666 said:
i do not know if this is the best place to post this considering i am brand new (i hope so) but i have a soft bricked nexus s 4g that i am trying to fix.
it was loaded with the helly bean 4.2.2 custom rom from nexus hacks (sorry no links) after the reboot it went to a black screen.
what ive tried:
odin: flashing a new rom, this resulted in odin not finding the device (usb debugging is not on and i cant turn it on)
fastboot: (i have all the files but i cant seem to get it set up, i type in adb or fastboot (no device recognized)
nexus root toolkit: (wouldnt find the device and found no options to help with usb debugging)
dfs: (couldnt read the device)
plugging in the phone to the computer: it makes the noise that it is plugged in, comes up as f drive but it is greyed out and i cant click on it (says insert disc)
clock work recovery: i did a full data wipe and required wipes cache and delvik or something along those lines: it reboots into the rom and nothing has changed.. my guess is because there is no back up of the original rom and the cfw is trash, it just wipes the bad rom back to factory and that is still a problem.
pda net: wont recognize the device
galaxy nexus toolkit: nothing useful since the usb debugging is not enabled.
ive worked for 6 hours as of last night to figure this out. i have spent most of those hours in forums and delving further into this phone then id imagined (its not mine) so if there is anyone out there that can suggest anything id appreciate it. this has got me stumped and amazed how such easy fix can really be this complicated.. i will thank any and all answers given to me
Click to expand...
Click to collapse
You need to be in the bootloader for fastboot to work. Reboot to bootloader and try flashing a recovery.img using this command.
fasboot flash recovery recovery.img
It blows my mind when a user gets all this great help and hasn't given any thanks to the helpers.
Sent from my iPad 4
mitchdickson said:
It blows my mind when a user gets all this great help and hasn't given any thanks to the helpers.
Sent from my iPad 4
Click to expand...
Click to collapse
Happens all the time. I'd have 1000 extra thanks if people new how to use the button or were remotely grateful.
estallings15 said:
Happens all the time. I'd have 1000 extra thanks if people new how to use the button or were remotely grateful.
Click to expand...
Click to collapse
i am sorry i was getting sdk tools set up watching an online tut. i am very greatful for your help my problem was that i had not installed java. so if anyone finds that sdk tools is not coming up. install java and it will work like it is supposed to. i will give a thank you just like i have promised. you guys on this site are the best techs hands down
---------- Post added at 05:13 PM ---------- Previous post was at 05:05 PM ----------
is there a thread on here about adb shell and pushing a new rom onto a nexus s 4g? basically the commands?
theblackrose666 said:
i am sorry i was getting sdk tools set up watching an online tut. i am very greatful for your help my problem was that i had not installed java. so if anyone finds that sdk tools is not coming up. install java and it will work like it is supposed to. i will give a thank you just like i have promised. you guys on this site are the best techs hands down
---------- Post added at 05:13 PM ---------- Previous post was at 05:05 PM ----------
is there a thread on here about adb shell and pushing a new rom onto a nexus s 4g? basically the commands?
Click to expand...
Click to collapse
adb push nameofrom.zip /sdcard/
Sent from my Nexus 4 using xda premium
ran sdk tools tried adb shell and nothing it wont read the device. we tried to push the .tar files to the phone using samsung galaxy nexus tool kit. it didnt work so hes going to take it to a repair but i think the device is toast on the account that usb debugging mode is no where in sight. if it does get fixed ill be sure to report how it got fixed. so anyone else who runs into the problem can get this fixed without a 20 dollar repair bill.
heat361 said:
Everything will be lost. Considering your phone is bricked there is no way to pull the pictures from your device.
Edit: you might not have to flash full stock, just the system.img that will allow you to overwrite the current system and maintain your sdcard.
Click to expand...
Click to collapse
will my computer even detect my phone? usb debugging is off and i can't see the phone's storage from my pc.
Related
Hi
Tried to root my new Nexus 7 on 4.2.1
It failed and somehow I managed to delete the OS??????
I can get it into bootlader and can find TWRP.
When I try to reboot it states NO OS installed.
Any suggestions? I have looked on the forums but cant find anything as I prob dont know what I am looking for.
Thank you in anticipation
Regards
capt208 said:
Hi
Tried to root my new Nexus 7 on 4.2.1
It failed and somehow I managed to delete the OS??????
I can get it into bootlader and can find TWRP.
When I try to reboot it states NO OS installed.
Any suggestions? I have looked on the forums but cant find anything as I prob dont know what I am looking for.
Thank you in anticipation
Regards
Click to expand...
Click to collapse
As long as bootloader is viable, you should be fine.
Download the FULL system image from Google:
https://developers.google.com/android/nexus/images#nakasi
Make sure you chose nakasi for WiFi or nakasig for 3G tablet, depending on the one you own.
Download file, extract tgz and extract zip inside of that.
Make sure you have adb/fastboot installed and in your path and that your tablet is connected and recognized. Boot into bootloader mode (which needs to be unlocked). Then do a full flash (you can omit the -w option to prevent the flash from wiping sdcard).
This will restore your device OS back to stock.
Depending on what you did, which you didn't really explain, there is probably a quicker/easier option. But without more info, the only advice I can give you is what I did, which should work fine for all circumstances.
Sticky post above this one is the solution..
It seems like you from your post you used a tool kit and something went wrong or you missed a step. Follow one of the following guides.
I recommend the first one..
Manual adb/fastboot
http://forum.xda-developers.com/showthread.php?t=1907796
Took Kits Automated flashing/ rom install ..
This one is a Windows interface.
......... http://forum.xda-developers.com/showthread.php?t=1766475..........
CMD Interface.
...............http://forum.xda-developers.com/showthread.php?t=1809195..........
I recommend the Manual method But only after reading post in all the threads. This will help you get a better understanding of Android..
Good Luck... the post above mine is also correct if you already have a adb environmental set up
Thank you
Thank you all for your advise
The nexus is once again alive
Have a very happy holiday season
Regards
Thank you
Thank you all for your advise
The nexus is once again alive
Have a very happy holiday season
Regards
how can I access my nexus, when I am in TWRP? windows cant connect to it cause of no driver..
jonny_pasta said:
how can I access my nexus, when I am in TWRP? windows cant connect to it cause of no driver..
Click to expand...
Click to collapse
Get the driver?
______________________________
Sent from my cellular telephone. Battery problems? >>>> http://forum.xda-developers.com/showthread.php?t=2461864
kj2112 said:
Get the driver?
______________________________
Sent from my cellular telephone. Battery problems? >>>> http://forum.xda-developers.com/showthread.php?t=2461864
Click to expand...
Click to collapse
no, you have to get to bootloader, I figured that out, now I'm sutck on "archive does not contain boot.sig" etc..
Hi
I got the same issue....
I can access the fastboot mode and the recovery mode, but not the bootloader. I go back on fastboot mode if I try to load bootloader...
I want to reinstall but windows doesn't recognize my n7 :/ so I'm stuck at this point :/
There is nothing that I can find that pertains to problems with installing Kitkat factory image 4.4 on my nexus 4 so I will state my problem with the hope of some insight.
I have a Nexus 4 that I have decided to sell and as a precautionary measure had decided to flash a fresh copy of Android version 4.3 last week to ensure all files were deleted. I used Nexus root toolkit and all went smoothly.
As the phone has not yet sold, I decided that I would update the currently OS to the latest version 4.4 kitkat to make it more appealing to buyers so I went back to Nexus Root Toolkit and went through the standard procedure of selecting my device and OS, etc. The phone is unlocked. I had no backup and went ahead and told the software to write over version 4.3 with 4.4. I thought all was going well, but the install was too short and didn't work with a message telling my to try "Force Flash" mode. So I tried again using force flash mode and this time the install took longer and the phone rebooted multiple times, only this time the phone wouldn't fully boot. It only boot loops now.
-I can put the phone into fastboot mode.
-The computer can communicate with the phone via USB cable.
-All info such as product name, variant, HW version, etc. is showing in fastboot mode.
I am unable to use Nexus Root Toolkit to fix my phone with or without using Force Flash mode.
I can't mount the phone and the computer can not detect the ADB at all.
Can anyone please tell me what I can do to fix my phone? Are there any other alternatives to flashing a fully functioning version of 4.4 Kitkat?
I have been at this for hours and I can seem to get anywhere with it. Is the phone destroyed?
Any help would be greatly appreciated. Thank you in advance.
saber13 said:
There is nothing that I can find that pertains to problems with installing Kitkat factory image 4.4 on my nexus 4 so I will state my problem with the hope of some insight.
I have a Nexus 4 that I have decided to sell and as a precautionary measure had decided to flash a fresh copy of Android version 4.3 last week to ensure all files were deleted. I used Nexus root toolkit and all went smoothly.
As the phone has not yet sold, I decided that I would update the currently OS to the latest version 4.4 kitkat to make it more appealing to buyers so I went back to Nexus Root Toolkit and went through the standard procedure of selecting my device and OS, etc. The phone is unlocked. I had no backup and went ahead and told the software to write over version 4.3 with 4.4. I thought all was going well, but the install was too short and didn't work with a message telling my to try "Force Flash" mode. So I tried again using force flash mode and this time the install took longer and the phone rebooted multiple times, only this time the phone wouldn't fully boot. It only boot loops now.
-I can put the phone into fastboot mode.
-The computer can communicate with the phone via USB cable.
-All info such as product name, variant, HW version, etc. is showing in fastboot mode.
I am unable to use Nexus Root Toolkit to fix my phone with or without using Force Flash mode.
I can't mount the phone and the computer can not detect the ADB at all.
Can anyone please tell me what I can do to fix my phone? Are there any other alternatives to flashing a fully functioning version of 4.4 Kitkat?
I have been at this for hours and I can seem to get anywhere with it. Is the phone destroyed?
Any help would be greatly appreciated. Thank you in advance.
Click to expand...
Click to collapse
It would have saved you a lot of problems of you had of done it manually, without a toolkit
http://forum.xda-developers.com/showthread.php?t=2010312
Sent from my Nexus 4 using Tapatalk
Same problem !
saber13 said:
There is nothing that I can find that pertains to problems with installing Kitkat factory image 4.4 on my nexus 4 so I will state my problem with the hope of some insight.
I have a Nexus 4 that I have decided to sell and as a precautionary measure had decided to flash a fresh copy of Android version 4.3 last week to ensure all files were deleted. I used Nexus root toolkit and all went smoothly.
As the phone has not yet sold, I decided that I would update the currently OS to the latest version 4.4 kitkat to make it more appealing to buyers so I went back to Nexus Root Toolkit and went through the standard procedure of selecting my device and OS, etc. The phone is unlocked. I had no backup and went ahead and told the software to write over version 4.3 with 4.4. I thought all was going well, but the install was too short and didn't work with a message telling my to try "Force Flash" mode. So I tried again using force flash mode and this time the install took longer and the phone rebooted multiple times, only this time the phone wouldn't fully boot. It only boot loops now.
-I can put the phone into fastboot mode.
-The computer can communicate with the phone via USB cable.
-All info such as product name, variant, HW version, etc. is showing in fastboot mode.
I am unable to use Nexus Root Toolkit to fix my phone with or without using Force Flash mode.
I can't mount the phone and the computer can not detect the ADB at all.
Can anyone please tell me what I can do to fix my phone? Are there any other alternatives to flashing a fully functioning version of 4.4 Kitkat?
I have been at this for hours and I can seem to get anywhere with it. Is the phone destroyed?
Any help would be greatly appreciated. Thank you in advance.
Click to expand...
Click to collapse
I have the same problem ! I have tried everything as you mentioned above. Additionally using the ADB I installed everything using the flash-all.bat and everything went well, however my phone is still in bootloop. Have you find a solution ? Please share if you have ... Thank you so much for posting the issue !
---------- Post added at 01:19 PM ---------- Previous post was at 01:02 PM ----------
priyab said:
I have the same problem ! I have tried everything as you mentioned above. Additionally using the ADB I installed everything using the flash-all.bat and everything went well, however my phone is still in bootloop. Have you find a solution ? Please share if you have ... Thank you so much for posting the issue !
Click to expand...
Click to collapse
Hey the flash-all.bat worked !!!! .. I just waited for like 15 mins after the flash-all.bat was done and viola! its back
This is great find
Those who face this issue can go to safe mode and backup their data while on boot screen just keep pressing up and down volume button for some time phone will get into safe mode and can be backed up.
Hi, I have a fully stock nexus 7 1st gen which is stuck on a boot loop, I am able to get it into fast boot mode where I've tried the wipe data/factory reset and wipe cache partition but it just freezes. I've searched around for solutions I've even tried flashing the stock images with wugfresh toolkit with no luck, most fixes it seems need the debugging enabled on the device which I can't do because I can't get into the menu. If anyone can help me it would be fantastic
mikebolton said:
Hi, I have a fully stock nexus 7 1st gen which is stuck on a boot loop, I am able to get it into fast boot mode where I've tried the wipe data/factory reset and wipe cache partition but it just freezes. I've searched around for solutions I've even tried flashing the stock images with wugfresh toolkit with no luck, most fixes it seems need the debugging enabled on the device which I can't do because I can't get into the menu. If anyone can help me it would be fantastic
Click to expand...
Click to collapse
Hey Mike, it sounds like you have no other option than to restore back to factory using the official Google Factory Images. That will completely wipe your N7, SDCard and all
Go ahead and download the nakasi image of your choice from Google: https://developers.google.com/android/nexus/images#nakasi... make sure that you don't accidentally get the nakasig firmware as it is for the Tilapia 3G model.
Extract it with 7-zip or WinRar (or whatever) and with your tablet plugged in and in Fastboot Mode, (you will also need the fastboot/ADB drivers installed) run the flash-all.bat batch file. (You may need to enable the Windows function "Show File Extensions" to see the .bat part after the file name. There is also a flash-all.sh in the folder as well but that one is for Linux users so you wont be able to use it unless you're on Linux.
Good Luck! :good:
Hi Tim, Thanks for replying,
I'm not too worried about losing data I'm just desperate to get it working again.
I have downloaded the flash image but where would I find the download for the fast boot drivers?
mikebolton said:
Hi Tim, Thanks for replying,
I'm not too worried about losing data I'm just desperate to get it working again.
I have downloaded the flash image but where would I find the download for the fast boot drivers?
Click to expand...
Click to collapse
They should be included in the Wugfresh Toolkit that you downloaded. Just follow the steps to install the device drivers and I believe that the Fastboot drivers installs with it.
How weird, I am fixing my Dad's tonight, exact same issue! Have had it a week or so but just found time to do it now... I will do with you if you like. I already downloaded the wugfresh NRT and worked through the steps, obviously missing out the debug mode parts. Currently downloading the nakasi kot49h which is taking a while, so came on here to see what to do if this fails and saw your post!
Sent from my Nexus 5 using xda app-developers app
---------- Post added at 11:29 PM ---------- Previous post was at 11:24 PM ----------
If you download the nexus root kit v1.8.2 from www.wugfresh.com follow the steps on there to uninstall various drivers, then click the initial setup - full driver installation to get the correct driver for your device.
Sent from my Nexus 5 using xda app-developers app
In the wug toolkit when installing drivers step by step guide to configure MTP drivers you need to disable USB debugging then disable MTP mode then re enable debugging all of which I can't do because I can't get into the menu to do anything
Hi Tom,
I can't seem to figure it out ive tried the wug toolkit a number of time with no results it seems most fixes need you to be able to enable debugging, if you find out how to do it let me know and if I by some miracle get it working I'll let you know
I have just run the flash stock and unroot option on wugfresh in the log everything has been erased but when it has tried to send bootloader is says failed<remote: bootloader is locked.>
Yes, you are up to where I got to. I fixed mine last night eventually. Next I tried a risky extra step which I won't tell as I don't think it did anything, then directly on the left of Flash and unroot there is a button to unlock bootloader. Run that, it gave me an error message but appeared to do the trick because the next time I ran flash + unroot it worked finally. Let us know how you get on!
Sent from my Nexus 5 using xda app-developers app
No it still isn't working everything I try doesn't work it all comes down to the locked bootloader and no matter what I do I can't find a solution to open it
Has anyone come across the same problem and found a solution?
mikebolton said:
No it still isn't working everything I try doesn't work it all comes down to the locked bootloader and no matter what I do I can't find a solution to open it
Has anyone come across the same problem and found a solution?
Click to expand...
Click to collapse
Open a command prompt in the folder with Fastboot. Type in "fastboot oem unlock" without quotes. That will unlock the bootloader and also you to flash factory image.
Doesn't work I've tried it before it just comes up with unlock bootloader screen where you have a choice yes (may void warranty) or no I click yes then I am directed back to fastboot mode with a message at the top left corner saying unlocking now....... but nothing ever happens, I restart device and I'm back to where I started.
Someone must know how to fix this
I left my phone charging and came back to get it. It was stuck on the google logo, I am able to boot into recovery but it says No Installed.
Is their anything else I can do other than flash it again.
I was thinking maybe the wrong partititon was checked, but everything looks fine.
Krooked22 said:
I left my phone charging and came back to get it. It was stuck on the google logo, I am able to boot into recovery but it says No Installed.
Is their anything else I can do other than flash it again.
I was thinking maybe the wrong partititon was checked, but everything looks fine.
Click to expand...
Click to collapse
Assuming that the ROM is still there, you can dirty flash the ROM zip over it, and see if it works. There's no harm in trying that.
But "No OS Installed" simply means that your /system or /boot parition are not detected (means, they are empty). Now of course, the last resort is to flash the ROM all over again.
Krooked22 said:
I left my phone charging and came back to get it. It was stuck on the google logo, I am able to boot into recovery but it says No Installed.
Is their anything else I can do other than flash it again.
I was thinking maybe the wrong partititon was checked, but everything looks fine.
Click to expand...
Click to collapse
You need to provide more information. Are you on the stock ROM or a custom ROM? Stock recovery or TWRP? Had you made any changes to the device recently?
Someone please help. I just rooted my 6P. Did a little bit of doing. Phone would never boot just the round circles. So went into TWRP and tried to wipe to start fresh, not it says no OS installed. I have no ROMS's on the phone. No boot images. Been a while since I've done this. Really need help on this one. Thanks.
Download the dp3 , boot into bootloader, connect to PC run installer script after you unzip the factory image " flash all" sit back and wait for phone to reboot.
---------- Post added at 10:30 PM ---------- Previous post was at 10:29 PM ----------
It's that simple.
Hey thanks a lot. Couple things, and I apologize in advance for not knowing this already.
1) what's dp3
2) how do I run installer script?
I know I shift right click and open a cmd window within fastest - where I'll unzip the file - and I know how to get the phone into Bootloader.
Again, sorry for asking for simple explanations.
StormCell said:
Someone please help. I just rooted my 6P. Did a little bit of doing. Phone would never boot just the round circles. So went into TWRP and tried to wipe to start fresh, not it says no OS installed. I have no ROMS's on the phone. No boot images. Been a while since I've done this. Really need help on this one. Thanks.
Click to expand...
Click to collapse
Download any ROM ( like pure Nexus) and gapps
You can use USB otg to flash the ROM using twrp or transfer the ROM file from your PC to your phone in twrp (it supports mtp)
Simply flash ROM and gapps and viola
Sent from my Nexus 6P using XDA Labs
Ok, I'm gonna tackle this tomorrow. Any recommendations on a good ROM and Kernel (Verizon). I made nice donations long ago to Franco and ROM Manager.
Thank again, everyone!
StormCell said:
Someone please help. I just rooted my 6P. Did a little bit of doing. Phone would never boot just the round circles. So went into TWRP and tried to wipe to start fresh, not it says no OS installed. I have no ROMS's on the phone. No boot images. Been a while since I've done this. Really need help on this one. Thanks.
Click to expand...
Click to collapse
Download the required ROM and gapps, connect your phone to pc , type in google, Mini adb and fastboot, a page on XDA itself will come, download it, its small and install.
Then copy the ROM and gapps package to the location of the installation of the application.
Now open your recovery and tap on adb sideload, and swipe(twrp)
Go to your PC, open adb application a cmd will appear, type adb devices, it will start a daemon then will give you your device number, a number should appear. Then type
Adb sideload """"name of your ROM package""".zip
It will start installing, wait for few minutes.
Do the same for gapps
Adb sideload " name of gapps package ".zip
Then reboot
Its fixed
NOT Sent from my GT-N7100 using the XDA-developers mobile app
i42o said:
Download the dp3 , boot into bootloader, connect to PC run installer script after you unzip the factory image " flash all" sit back and wait for phone to reboot.
---------- Post added at 10:30 PM ---------- Previous post was at 10:29 PM ----------
It's that simple.
Click to expand...
Click to collapse
Why are you telling him to install the Developer Preview? He wouldn't want that unless he's actually asking for it, which he isn't.
StormCell said:
Ok, I'm gonna tackle this tomorrow. Any recommendations on a good ROM and Kernel (Verizon). I made nice donations long ago to Franco and ROM Manager.
Thank again, everyone!
Click to expand...
Click to collapse
Please continue the discussion in the other thread that you posted this question in, as I said, let's not create duplicate discussions.
StormCell said:
Hey thanks a lot. Couple things, and I apologize in advance for not knowing this already.
1) what's dp3
2) how do I run installer script?
I know I shift right click and open a cmd window within fastest - where I'll unzip the file - and I know how to get the phone into Bootloader.
Again, sorry for asking for simple explanations.
Click to expand...
Click to collapse
Developer preview 3 is a Android N preview and it is very fluid, battery life is good on stock and reason I recommend this because it is simple to do, gives you good options within the ROM and is good overall but that's just my opinion.
---------- Post added at 12:35 PM ---------- Previous post was at 12:32 PM ----------
Heisenberg said:
Why are you telling him to install the Developer Preview? He wouldn't want that unless he's actually asking for it, which he isn't.
Click to expand...
Click to collapse
Dude, I'm trying to help. Beats what you said, you going detective mode on him while I'm just giving him an easy solution. Read a book or something
i42o said:
Dude, I'm trying to help. Beats what you said, you going detective mode on him while I'm just giving him an easy solution. Read a book or something
Click to expand...
Click to collapse
Lol. Maybe you missed the title under my name.
The dev preview isn't what he asked for, it isn't an easy solution, it isn't easy to come back from if he doesn't like it, it isn't even remotely what he needs. What he's looking for is a simple way to get his phone booted up and working again (a very simple request), and what you're suggesting is he install a beta OS (a complicated "solution").
If you really have a problem with a moderator requesting that a member posts in one place at a time (as per our rules), then I'm gobsmacked. If you'd care to look at the advice I gave him in the guide thread where he also posted you'd notice that I gave two solutions that:
A) Actually address the simplicity of his problem.
B) Give two simple, easy to execute, solutions that are the most common solutions you'll ever see anyone give a member in his situation. Solutions that don't involve having to install a developer preview that he never asked for.
I get that you're trying to help him, but the "solution" you provided him isn't right for his situation at all. There was no need to become defensive and aggressive when this was pointed out.
Vishal Vignesh said:
Download the required ROM and gapps, connect your phone to pc , type in google, Mini adb and fastboot, a page on XDA itself will come, download it, its small and install.
Then copy the ROM and gapps package to the location of the installation of the application.
Now open your recovery and tap on adb sideload, and swipe(twrp)
Go to your PC, open adb application a cmd will appear, type adb devices, it will start a daemon then will give you your device number, a number should appear. Then type
Adb sideload """"name of your ROM package""".zip
It will start installing, wait for few minutes.
Do the same for gapps
Adb sideload " name of gapps package ".zip
Then reboot
Its fixed
NOT Sent from my GT-N7100 using the XDA-developers mobile app
Click to expand...
Click to collapse
I'm copying files over to my Nexus now using MTP from TWRP. Can't I just copy evrything over and flash that way? Man, this seems so much more complicated than back in the day. Thanks.
Crap, wrong thread! Sorry! Got confused.
StormCell said:
I'm copying files over to my Nexus now using MTP from TWRP. Can't I just copy evrything over and flash that way? Man, this seems so much more complicated than back in the day. Thanks.
Crap, wrong thread! Sorry! Got confused.
Click to expand...
Click to collapse
Sure, this method is for those who do not wanna copy the zip package to the PC/don't have it
Sent from my GT-N7100 using XDA-Developers mobile app
So basically I am not smart and factory reset my phone in settings. The bootloader was unlocked and rooted. First phone I have ever rooted and this is all just a lot of information to take in. Trying to read and look into my problem but nothing I am trying is working.
When I turn my phone on it goes immediately into TWRP. When TWRP came up I wiped the data, cache, and dalvik. Not sure what all I have tried but I can't figure anything out. I am assuming I need to flash a stock ROM back onto my phone? Not sure how to do that. I have a stock rom downloaded. When I try to flash it just says 'waiting for device'. It is plugged in but I am assuming USB debugging is not turned on which is why it doesn't locate it?
Not really sure if my assumptions are correct but I am failing horribly here and would love if someone could explain this to me step by step like I am a cave person. Would even be willing to paypal someone $5 if that kind of thing is allowed for help. Thanks for helping a moron out.
hegro said:
So basically I am not smart and factory reset my phone in settings. The bootloader was unlocked and rooted. First phone I have ever rooted and this is all just a lot of information to take in. Trying to read and look into my problem but nothing I am trying is working.
When I turn my phone on it goes immediately into TWRP. When TWRP came up I wiped the data, cache, and dalvik. Not sure what all I have tried but I can't figure anything out. I am assuming I need to flash a stock ROM back onto my phone? Not sure how to do that. I have a stock rom downloaded. When I try to flash it just says 'waiting for device'. It is plugged in but I am assuming USB debugging is not turned on which is why it doesn't locate it?
Not really sure if my assumptions are correct but I am failing horribly here and would love if someone could explain this to me step by step like I am a cave person. Would even be willing to paypal someone $5 if that kind of thing is allowed for help. Thanks for helping a moron out.
Click to expand...
Click to collapse
Some more information please? Were you on stock rooted or custom rom. Best bet then is clean flashing a custom rom.
GtrCraft said:
Some more information please? Were you on stock rooted or custom rom. Best bet then is clean flashing a custom rom.
Click to expand...
Click to collapse
Pretty sure I was just stock rooted. How would I go about doing that? Like I said, I have a stock rom downloaded on my PC. Tried to flash it but all I get is 'waiting for device' in the cmd window after directing it towards the zip file.
Also as I said, trying to learn and absorb as much info as I can here, never done this before so I am a little slow. =/
just tried using THIS method but when I plug my phone in it is not recognized in RSD Lite. I keep reading I need USB debugging on. I can't turn it on from recovery screen, no? Is there anything I can do?
hegro said:
just tried using THIS method but when I plug my phone in it is not recognized in RSD Lite. I keep reading I need USB debugging on. I can't turn it on from recovery screen, no? Is there anything I can do?
Click to expand...
Click to collapse
Boot to twrp and flash a custom rom zip like lineage os. Or a modified stock rom like stoneware
Yes, wiped phone, put stoneware on my phone, booted to twrp, installed stoneware, reboot, back to twrp. I have to be doing something wrong but I don't know what it is. I have tried doing this with multiple different ROMs, flashing in TWRP.
hegro said:
Yes, wiped phone, put stoneware on my phone, booted to twrp, installed stoneware, reboot, back to twrp. I have to be doing something wrong but I don't know what it is. I have tried doing this with multiple different ROMs, flashing in TWRP.
Click to expand...
Click to collapse
I had this issue when I did (like a idiot) a Ota update. Only fix I got was running g5 plus tool kit and flashing stock Rom though it by following instructions on the program..
Factory reset shouldn't have caused this issue.. Unless you formated your data in twrp.. But if the boot is altered or damaged and you just put a custom Rom on top I think you might find you won't have a baseband (no mobile network).. The original stock Rom is available via links in the windows toolkit 1.6 gig
Go into fastboot and just type fastboot continue
fixed
alevity said:
I has this issue when I did (like a idiot) a Ota update. Only fix I got was running g5 plus tool kit and flashing stock Rom though it by following instructions on the program..
Factory reset shouldn't have caused this issue.. Unless you formated your data in twrp.. But if the boot is altered or damaged and you just put a custom Rom on top I think you might find you won't have a baseband (no mobile network).. The original stock Rom is available via links in the windows toolkit 1.6 gig
Click to expand...
Click to collapse
So I ran the tool kit and put on a stock rom. My phone turns on now! Except when I turn it on it says that the device is unlocked and can't be trusted. ID: bad key.
hegro said:
So I ran the tool kit and put on a stock rom. My phone turns on now! Except when I turn it on it says that the device is unlocked and can't be trusted. ID: bad key.
Click to expand...
Click to collapse
boot into twrp again and reboot system
it should fix it
next time remember just go into fastboot and type "fastboot continue"
no need to wipe or reflash
power off your phone then volume down and power together until bootloader screen appearing than select factory mode and then press power button to select factory mode
hegro said:
So I ran the tool kit and put on a stock rom. My phone turns on now! Except when I turn it on it says that the device is unlocked and can't be trusted. ID: bad key.
Click to expand...
Click to collapse
That's completely normal we all have that just means it's unlocked bootloader. Enjoy your device normally
---------- Post added at 12:47 PM ---------- Previous post was at 12:44 PM ----------
bornlivedie said:
boot into twrp again and reboot system
it should fix it
next time remember just go into fastboot and type "fastboot continue"
no need to wipe or reflash
Click to expand...
Click to collapse
Why would doing that remove the hard coded warning that the bootloader is unlocked? Op had a functioning phone now and just didn't know the warning boot is perfectly OK.
pretty sure my twrp got replaced? idk but when I try to go to recovery all I get is the little dead android guy with the red triangle.
hegro said:
pretty sure my twrp got replaced? idk but when I try to go to recovery all I get is the little dead android guy with the red triangle.
Click to expand...
Click to collapse
That's stock recovery
alevity said:
That's completely normal we all have that just means it's unlocked bootloader. Enjoy your device normally
---------- Post added at 12:47 PM ---------- Previous post was at 12:44 PM ----------
Why would doing that remove the hard coded warning that the bootloader is unlocked? Op had a functioning phone now and just didn't know the warning boot is perfectly OK.
Click to expand...
Click to collapse
I wouldn't know about "perfectly ok" but I had that bad key thing before, and read the rebooting into TWRP fixes the "issue". It's true, it works. I have N/A now and not "bad key".