Hi my friend has Nexus 7 (lte) 2013 = razorg
I helped him to unlock bootloader , flash twrp , and root this **** ( i know N7 is great im jealous )
But hew wanted so badly cyanogen rom so he dv-d cyanogen and flashed it everything were fine , till 1 day ago he had force closes in Settings when trying to enter wirless & networks more / mobile networks - he got " settings stopped working and nothing more happened
also he got that kind of fc when entering about tablet / status
and for the final problem he got his network unable to connect like there were no sim card " inser the sim and reboot tab ".
He asked me what to do sim was fine so i told him to flash cyan rom again via Twrp and here we go :
He , did backup, had cyanogen rom already and As im a GT2 7" user i told him by routine to wipe system, cache , dalvik cache , n DATA -.- my bad now he has unlocked bootloader , working twrp , windows recognize an "Android device" but Adb devices shows nothing what to do now , im not in to twrp im hard user of cwm so i dont rlly know what i can do with twrp to help him.
I think there are 2 options :
1. try adb **** on other laptop
2. Force flash stock image
What do you think ? If u can answer as fast as you can i hope there is an easier way to mount data part and just transfer rom.zip to dhis **** .
Twrp version : 2.6.3.1
And silly q why twrp when trying to copy log to sd shows unable to write otg but "success saved to data/.... " ?
rudy1221 said:
Hi my friend has Nexus 7 (lte) 2013 = razorg
I helped him to unlock bootloader , flash twrp , and root this **** ( i know N7 is great im jealous )
But hew wanted so badly cyanogen rom so he dv-d cyanogen and flashed it everything were fine , till 1 day ago he had force closes in Settings when trying to enter wirless & networks more / mobile networks - he got " settings stopped working and nothing more happened
also he got that kind of fc when entering about tablet / status
and for the final problem he got his network unable to connect like there were no sim card " inser the sim and reboot tab ".
He asked me what to do sim was fine so i told him to flash cyan rom again via Twrp and here we go :
He , did backup, had cyanogen rom already and As im a GT2 7" user i told him by routine to wipe system, cache , dalvik cache , n DATA -.- my bad now he has unlocked bootloader , working twrp , windows recognize an "Android device" but Adb devices shows nothing what to do now , im not in to twrp im hard user of cwm so i dont rlly know what i can do with twrp to help him.
I think there are 2 options :
1. try adb **** on other laptop
2. Force flash stock image
What do you think ? If u can answer as fast as you can i hope there is an easier way to mount data part and just transfer rom.zip to dhis **** .
Twrp version : 2.6.3.1
And silly q why twrp when trying to copy log to sd shows unable to write otg but "success saved to data/.... " ?
Click to expand...
Click to collapse
You should be able to transfer a ROM.zip to the tablet with the adb push command then flash it thru twrp. Just factory reset thru twrp before flashing the ROM, a standard wipe should suffice, no need for any advanced wiping.
Make sure you have ADB, and the SDK+ the proper drivers setup on the computer.
Also, make sure you are in fastboot mode to use adb (volume down+power), you should see an android with his insides exposed, and the word start with a green box around it.
If you want to restore it to stock (stock recovery+ROM) follow this guide
http://forum.xda-developers.com/showthread.php?t=2382618
If you still encounter problems you can use wugs fresh toolkit to restore it to stock.
http://www.wugfresh.com
Good luck, sound like y'all are gravy tho
thisguysayswht said:
You should be able to transfer a ROM.zip to the tablet with the adb push command then flash it thru twrp.
Make sure you have ADB, and the SDK+ the proper drivers setup on the computer.
Also, make sure you are in fastboot mode to use adb (volume down+power), you should see an android with his insides exposed, and the word start with a green box around it.
Click to expand...
Click to collapse
I know i should be able to do so , and i know that i need to enter fastboot mode. The only problem is that adb dont see device , ill try it on my clean and "everything works" laptop and weell see mayby he did smth to drivers or other ****
Im not as dumb as i sound
rudy1221 said:
I know i should be able to do so , and i know that i need to enter fastboot mode. The only problem is that adb dont see device , ill try it on my clean and "everything works" laptop and weell see mayby he did smth to drivers or other ****
Im not as dumb as i sound
Click to expand...
Click to collapse
Lol totally not trying to say you sound/are dumb, don't know you from Adam, sorry if I came off that way, just going thru the basics, you never know with the people on the interweb
Since adb won't recognize it, I would just use the wugs fresh toolkit. There is an option to "flash stock+unroot", it should get y'all back to square one, and it will also reflash twrp and root the tablet, with a couple clicks.
That was rather a silly joke by me I know u did not wanted to say im dumb cuz some ppl re just forgetting about simple things like turn your phone on to call a friend im thinking about wugs toolkit but i dont like (personally ) toolkits that are doing smth by 1 click i have briked that way my 1st phone with wm by instaling rom throught 1 click installer and since nexus isnt mine im just carefull about what im doing and saying now but thx ill jump to mah friend morning and try to fix his problem
I've used wugs toolkit a few times and it works like a charm.
Related
Hello everyone!
First of all, I would like to apologize, as these kind of issues have probably been talked about and solved a gazillion of times before, but the thing is, I'm having a hard time grasping the start and the end of this issue myself, as the phone that is stuck in a boot-loop isn't mine - it belongs to a friend of mine who somehow managed to get the whole thing bricked.
Anyhow, I'll start off with what I know;
His goal was to flash a new ROM (http://forum.xda-developers.com/showthread.php?t=1601543). He unlocked the bootloader and rooted the phone using these instructions; http://onexroot.com/one-x-root/how-to-root-one-x/). He succeeded in doing so and decided to move onto flashing the rom.
But the problems started when he read that he's first supposed to flash "Android Fastboot kit 2.1" onto the device, prior to flashing the device. And so he did. Or well, tried - what he told me was that he booted the phone into fastboot mode, then ran the "Install Boot.img" bat file inside the Fastboot Kit folder he downloaded and after that, the phone got bricked.
Now, my knowledge in this area isn't too great either, but I've flashed a few ROMs in my life before, so, I decided I'd do my best to help. But I have no clue on what steps he should take from here on.
To my understanding, he was running the official 1.29 version and he is still able to access the boot-loader as well as Clockwork Recovery mod. To my understanding, he didn't create a back-up of his previously working ROM and the phone won't show up in Windows Explorer while connected via USB either.
To my limited understanding, I should now try and install the rom onto his phone and once done, the whole thing should work - the only problem with that is the fact I can't get the ROM zip onto the SD Card right now, as explorer won't recognize it. So far, I tried using ADB to push the ROM file onto the phone, but every time I use the command "adb shell mount /sdcard" I get a "Device not foound" error. So, I'm kinda stuck here right now. If this even is the right way to solve the issue, that is.
So, like I said, I'm having a hard time grasping the start and the end of this issue myself, and if there is any additional information needed, I'll do my best to find out more about it - I do have the phone in my possession at the moment as well.
Thanks a lot to anyone who'll offer any kind of help!
Atraeh said:
Hello everyone!
First of all, I would like to apologize, as these kind of issues have probably been talked about and solved a gazillion of times before, but the thing is, I'm having a hard time grasping the start and the end of this issue myself, as the phone that is stuck in a boot-loop isn't mine - it belongs to a friend of mine who somehow managed to get the whole thing bricked.
Anyhow, I'll start off with what I know;
His goal was to flash a new ROM (http://forum.xda-developers.com/showthread.php?t=1601543). He unlocked the bootloader and rooted the phone using these instructions; http://onexroot.com/one-x-root/how-to-root-one-x/). He succeeded in doing so and decided to move onto flashing the rom.
But the problems started when he read that he's first supposed to flash "Android Fastboot kit 2.1" onto the device, prior to flashing the device. And so he did. Or well, tried - what he told me was that he booted the phone into fastboot mode, then ran the "Install Boot.img" bat file inside the Fastboot Kit folder he downloaded and after that, the phone got bricked.
Now, my knowledge in this area isn't too great either, but I've flashed a few ROMs in my life before, so, I decided I'd do my best to help. But I have no clue on what steps he should take from here on.
To my understanding, he was running the official 1.29 version and he is still able to access the boot-loader as well as Clockwork Recovery mod. To my understanding, he didn't create a back-up of his previously working ROM and the phone won't show up in Windows Explorer while connected via USB either.
To my limited understanding, I should now try and install the rom onto his phone and once done, the whole thing should work - the only problem with that is the fact I can't get the ROM zip onto the SD Card right now, as explorer won't recognize it. So far, I tried using ADB to push the ROM file onto the phone, but every time I use the command "adb shell mount /sdcard" I get a "Device not foound" error. So, I'm kinda stuck here right now. If this even is the right way to solve the issue, that is.
So, like I said, I'm having a hard time grasping the start and the end of this issue myself, and if there is any additional information needed, I'll do my best to find out more about it - I do have the phone in my possession at the moment as well.
Thanks a lot to anyone who'll offer any kind of help!
Click to expand...
Click to collapse
The latest Clockwork jobby will allow you to mount the sdcard as USB drive.
Other than that, you seem to be on the right track.
^ he's right
What you want to do is first download the 5.8.4.0 version of the endeavoru CWM recovery.
reboot to your bootloader, make sure you're in fastboot and flash the new recovery img.
After you have successfully flashed the new recovery, well... go to the recovery
On the recovery, tap mounts and storage, then tap Mount USB. VOILA!!!!!
Yeah, I forgot to mention that I've already tried mounting the SD Card via Clockwork Recovery - I get an error saying "Unable to open ums lunfile (No such file or directory exists). So that doesn't seem to be an option either, unless you have an idea on how to counter this?
EDIT: Ah, I see - he's using an older version. I'll get the latest one on board and give it a go. Will have to wait a bit for the phone to charge up first it seems though. Not enough battery to do it right now .
Thanks!
And voila! The phone is operational.
Thanks a lot for the help and, I just hope I never manage to half-brick my own HOX .
Hello guys,
I had my Nexus 7 2013 (Wi-fi) for almost an year running stock rom and I decided to install CM12+ElementalX. It was all good untill yesterday when I returned it back to stock 5.0.2. When i started the tablet a message popped about 5.1 update and I started the update, but in the middle of the process it said "ERROR". I rebooted the device and now its stuck on the screen where you have to choose your language, with two errors constantly popping up - "PHONE HAS STOPPED WORKING" and "NFC Service has stopped working". I press OK like mad trying to skip some of the steps,but the "touch and go" (i think thats the name) is as far as i can go.
Is there any way I can flash the stock 5.1 without USB Debug Mode. There is no way i can get in the tablet's menu. I also saw some of the othere topics with this kind of problems, but i didn't find the answer.
You don't need USB Debugging to flash the factory images... use fastboot.
Telyx said:
You don't need USB Debugging to flash the factory images... use fastboot.
Click to expand...
Click to collapse
Can you please explain with few steps. I tried everything and i don't know what am I missing
P.s. I dont have custom recovery and i cant turn debug mode on
Ramirezz27 said:
Can you please explain with few steps. I tried everything and i don't know what am I missing
P.s. I dont have custom recovery and i cant turn debug mode on
Click to expand...
Click to collapse
I have installed ADB i Android SDK. Everythink is working fine on my Nexus 5 , but i cant do anything with my Nexus 7 which is now constantly rebooting after i managed to go through all the starting steps , when it started to install my 36 apps it rebooted by itself and now it keeps doing it.
i am having similar issue. i have tried the root tool several times with no success. ive been rooting devices since the samsung moment and i cannot get this tablet going at all. with the root tool i am able to flash twrp recovery, but for some reason it will not mount to put a rom on the internal memory. i have even tried pushing a stock rooted rom through adb fastboot and it just hangs. what else can i possibly do? could it be hardware related? this all happened after i was prompted for the latest 5.1.1 update. any tips or suggestions would be greatly appreciated. tia
Hello everybody,
i hope the xdadevs can help me with my problem.
Since two Days i try to recover my Nexus 7 form a bootloop.
A week ago i flashed Kali Nethunter 2.0 via TWRP on my Device (Nexus 7 2003 Wifi) - Everything worked fine till yesterday.
My device run out of energy so i loaded it and startet it shortly after that.
Then i regognized the bootloop. I tried to restart the device but it had no effect.
After that i tried to boot into the Recovery Mode with TWRP to restore my working backup. But it got stucked on the loading screen of TWRP too.
Now i tried to recover some images and fix the problem with some manuals which seemed promising. - no success
After a while i did something incredible stupid and locked my bootloader again (i wanted to try to lock and unlock it since some tools couldnt flash the stock rom).
The situation right now:
I cant boot up normaly: Stuck while "Google" is displayed
I cant boot in Recovery Mode (TWRP): Stuck on the blue TWRP Logo
If i try to use the Skipsoft Toolkit or something else it fails - or do i miss something
Recover the Stock rom by using the "flash-all.bat" fails because of this (pastebin. c0m/ie0dBv1D). I used the stock rom of Android 4.4.4(razor-ktu84p) because every other stockrom says this (pastebin. c0m/Dz31k8qu).
I wonder why the stock rom needs to get the bootloader unlocked... ive red so much about it that it just works out of the box..... am i doing something wrong ?
If i try to unlock again, the selection screen on the tablet shows up. I choose yes and hit the Power button. At the console the output <bootloader> erasing userdata" shows up and "freezes?!"... nothing happens afterwards.
Thats about it and this is where i am stuck. I would really appreciate if someone could help me ! I would even reward or spend some money on help.
I try to fix it meanwhile and update this post if something new happens.
I had to alternate the links because im a new member, im sorry for that !
Thanks in advanced and sorry for the spelling
did you try the nexus root toolkit ?
war your PC detecting (USB) the Nexus prior to this problem?
diehard2013 said:
did you try the nexus root toolkit ?
war your PC detecting (USB) the Nexus prior to this problem?
Click to expand...
Click to collapse
Yeah i tried it but it couldnt fix my problems. Returning to Stock Rom will always tell me that i need the bootloader unlocked... and i cant unlock it.
My PC and Linux Notebook where recognizing before it was bricked. Now it only gets detected in fastboot because it wont start anymore.
Hi XDA, many threads here have helped me in the past so time to ask another (probably stupid) question. It's a bit of a long story so I apologise in advance.
I've been running CM (one of the nightly builds from about 3 weeks back, don't have the file so I can't say which) on my phone for a while with no issues until a couple of nights ago when it was overheating (charging while playing a game, stupid I know) so I decided to turn it off so it could cool down without taking it off charge.
The following morning I turn it back on to find that it's getting to the blue android head logo of CM and getting stuck there. First thing I do is reboot into TWRP and flash my backup from right after I installed CM. Reboot and... same result. Okay, no biggie right? Time to reinstall CM (the latest nightly build from yesterday) and Google Apps (nano package) via TWRP and reboot again. Still stuck at the blue android head logo. The reinstall was handled after using the Wipe-Factory Reset function of TWRP, as the guide here explains.
At this point I decide to do a bit of research and learn that it's called a softbrick or bootloop and apparently flashing the stock rom can fix it. The LG software suite won't even recognise the device but a friend of mine found this guide so I attempted to run through it. All goes well until it comes time for the software to connect to the phone - I pop it in download mode while putting the USB cable in, the program says waiting for connection, runs for 14 seconds and says it's trying to put the phone into download mode, at this point it fails saying the phone can't be put into download mode.
Some of the comments beneath the article offer fixes like using USB 2.0 instead of 3.0, putting the program into compatability mode for Win7 and running in administrator mode. To be thorough I tried every USB port on my machine (both 2.0 and 3.0) and run the program in compatability mode (with and without admin mode) for several versions of windows. Same result every time.
Another friend then suggests that somehow permissions got borked and it might be worth reflashing SuperSU to the system but at this point I'm at a loss for how to do that. I have the one click root script that I got from god knows where (not this one because that didn't work for me) that has a SuperSU zip in it, presumably it flashes that to the phone when it runs (found this out the hard way because I've been a moron in the past and tried installing SuperSU through TWRP and broke the boot previously, fixed by re-running the one click root script - this was ages ago before even installing CM.)
So right now I can put the phone into download mode manually, get into TWRP and use all its functions as well as connect to my PC and use ADB functions while the phone's in TWRP but can't boot into CM or flash a stock rom. Any help would be appreciated, I've spent a whole day reading guides, asking friends and clumsily trying to fix this only to get nowhere.
Have u tried installing the stock via TWRP? Via zip ... Wipe cache delvik also..
jinderation said:
Have u tried installing the stock via TWRP? Via zip ... Wipe cache delvik also..
Click to expand...
Click to collapse
I haven't tried that, I didn't even know it was possible. Could you give me some more detailed pointers on how to do this? I noticed that the stock ROM I have cames as a .TOT file but CM is several files and folders in the zip. Will it install fine from that zipped up TOT file?
Thank you so much for your time.
When the rom is uploaded by the dev its also uploaded in .zip file place it ur system rom just go into twrp recovery flash the the zip file before flashing wipe cache n delvik too its easy as 1,2,3 search here on xda for ur compatible model
jinderation said:
When the rom is uploaded by the dev its also uploaded in .zip file place it ur system rom just go into twrp recovery flash the the zip file before flashing wipe cache n delvik too its easy as 1,2,3 search here on xda for ur compatible model
Click to expand...
Click to collapse
Thank you so much. I got it sorted. I really appreciate you taking the time to help me out with my stupidity.
Hello,
i dropped my phone last night and at first boot phone clock changed and i could not connect wifi. i tried to connect wifi today but it did not worked. Thats why i opened hidden menu by using *#546368#*855# test my phone if there is a hardware problem or not. i clicked first option then second option my phone got reset but i got Secure booting error after that and it stuck. Then i opened twrp by using factory data reset option. i got backup of my data from twrp menu.
What should i do now?
Notes:
- i use twrp + android 6.0 rooted firmware
- i dont know if can can install apk since i cant open android system
- i dont want to install stock rom by a pc because i think i will lose all info on phone and ont be able to get them back without twrp.
juba08 said:
Hello,
i dropped my phone last night and at first boot phone clock changed and i could not connect wifi. i tried to connect wifi today but it did not worked. Thats why i opened hidden menu by using *#546368#*855# test my phone if there is a hardware problem or not. i clicked first option then second option my phone got reset but i got Secure booting error after that and it stuck. Then i opened twrp by using factory data reset option. i got backup of my data from twrp menu.
What should i do now?
Notes:
- i use twrp + android 6.0 rooted firmware
- i dont know if can can install apk since i cant open android system
- i dont want to install stock rom by a pc because i think i will lose all info on phone and ont be able to get them back without twrp.
Click to expand...
Click to collapse
Hello,
You need to install Mr.Bump (click on it to download it) and move it to your Phone (Go to TWRP,connect your phone with your PC,move the file to your phone)Then click install and select "Mr.Bump.zip" file.
Greetings.
thanks you but i bricked my phone last night now it does not even open or charge. Thats i have done so far:
i used auto rec on my lg g3 d855 phone. https://forum.xda-developers.com/lg-g3/development/stock-d855-30b-images-kdz-flashables-t3282012 i had stock lg 6.0 30b firmware provided in this topic. it said succsfull and after the reset phone did not open and it does not respod to any button also dont get charge there is just black screen. is there there any way yo fix this?
do you think something like this topic help this issue?
https://forum.xda-developers.com/verizon-lg-g3/general/how-to-hardbrick-guide-using-test-t3276928
juba08 said:
thanks you but i bricked my phone last night now it does not even open or charge. Thats i have done so far:
i used auto rec on my lg g3 d855 phone. https://forum.xda-developers.com/lg-g3/development/stock-d855-30b-images-kdz-flashables-t3282012 i had stock lg 6.0 30b firmware provided in this topic. it said succsfull and after the reset phone did not open and it does not respod to any button also dont get charge there is just black screen. is there there any way yo fix this?
do you think something like this topic help this issue?
https://forum.xda-developers.com/verizon-lg-g3/general/how-to-hardbrick-guide-using-test-t3276928
Click to expand...
Click to collapse
It would be better not to flash those kdz files.
You could have asked here before proceeding,but it doesn't matter now.
For the topic that you sent,I'm not sure that it will work.
So,can enter in Download mode (Click on it to see how to enter)
If you can,please reply.
Sotiris02 said:
It would be better not to flash those kdz files.
You could have asked here before proceeding,but it doesn't matter now.
For the topic that you sent,I'm not sure that it will work.
So,can enter in Download mode (Click on it to see how to enter)
If you can,please reply.
Click to expand...
Click to collapse
i have done everything on that topic i went ok until last steps but at last i still got black screen and cant enter download mode or boot. but pc recognizes the phone as lge androidnet usb now in device manager. it was Qualcomm 9008 at start.
juba08 said:
i have done everything on that topic i went ok until last steps but at last i still got black screen and cant enter download mode or boot. but pc recognizes the phone as lge androidnet usb now in device manager. it was Qualcomm 9008 at start.
Click to expand...
Click to collapse
Hmm Try this guide Unbrick guide (it's officially for D855)
thanks it worked in second time now i can enter download mode i am flashing with lg flash tool. the problem is i could not install twrp before. i tried 5 roms + autorec, twrp manager and twrp offical app. and all resulted failing to open clock work mode. now i will try with D85530B_00_1217_32G.kdz
i have twrp backup in my sd card that why i am trying to boot into twrp for more than 24 hours. i hope i can do this. i winn never use eutorec i will use offical twrp app next time.
i can open android but i cant open twrp i got error boot vefication failed. i can use phone like that but i want to get my backup. if i cant i will have to install apps one by one and i will also lose some files, contacts, data etc.