Hi All,
I recently purchased a Nexus 7 (2013). Its my first Android device and so far I've been really enjoying using it.
I managed to root it and installed Multi-rom. I have two roms on it. Stock 4.4.2 and another Kali based rom.
Anyway recently I saw an update for 4.4.3 and I tried to install it from my stock 4.4.2 rom ( I'm thinking this was a mistake?)
Anyway it download and the booted into recovery mode. I wasn't sure what to do and I just rebooted it again and opened up my Stock image.
The issue is now I cannot turn on Wifi for some reason. From the Wireless conections page it just says 'turning on wifi' but never does. If I boot into my other rom wifi works fine.
The version of Android on the stock rom still says 4.4.2. My Kernel version is 3.4.0-g80964c2 and the build number is KOT49H.
I'm kind of new to all of this and don't know how to proceed. If anyone could help me it would be very much appreciated.
Cheers.
MarcG
Just use this: http://forum.xda-developers.com/showthread.php?t=2389107
It will even download the correct images for you.
k3lcior said:
Just use this: http://forum.xda-developers.com/showthread.php?t=2389107
It will even download the correct images for you.
Click to expand...
Click to collapse
Thanks k3lcior!
I guess I can use this to get back to a clean known state with the 'Flash Stock + Unroot' option.
However I was wondering is there a way to update my internal ROM when I've got multirom installed? Trying to update from within 4.4.2 seems to have gotten me into this mess in the first place, so I'm trying to learn how I should update my internal stock rom in the future?
cheers.
I have no idea as i've never used MultiRom so dont want to speculate.
Couple of new tabs were recently released into the wild with some "revisions". Those who went thru Groupon, Frys, and Best Buy received tabs with 5.0.1 pre installed out of box.. Because of this you couldn't go back to any 4.x.x builds as the bootloader wouldn't allow it. After posting this and finding out about this issue some XDA members were able to find a fix and confirmed that this solution is a working solution.
TL;DR
Any Custom Recovery had problems mounting SD/Partitions making flashing roms, zips, ect a problem.
**WARNING**
I AM NOT RESPONSIBLE FOR ANY MISFORTUNE YOU RECEIVE BY APPLYING ANY INFO PAST THIS POINT. YOU TAKE SOLE RESPONSIBILITY FOR YOUR ACTION AND NO ONE HERE BUT YOURSELF IS ACCOUNTABLE.
I have included both LTE (DEB) and WIFI(FLO) setups that are currently working and are confirmed working by XDA members here. Apply based on your device. This works for both 5.0.1 and 5.0.2. ADB or Wugs program is sufficient enough to complete this task.
WIFI (FLO) https://drive.google.com/file/d/0B3fHxCdm5V_Mc2szNnFzT1I0eVk/view?usp=sharing
LTE (DEB) https://drive.google.com/file/d/0B3fHxCdm5V_MU1hfXzV6dFlEZ2c/view?usp=sharing
**NOTE**
The only way so far to root tab is to use cf-auto root. Google it and follow directions.
ADB setup:
Download recovery img and place into location where you ADB resides (or leave in download folder and open CMD in downloads for global ADB users)
make sure ADB is working and confirm that you Nexus is recognized
Code:
Code: adb devices
After confirmation get tab into bootloader mode
Code:
adb reboot bootloader
Flash recovery image (Depending on tab version)
FLO:
Code:
fastboot flash recovery TWRP_multirom_flo_20150328.img
DEB:
Code:
fastboot flash recovery TWRP_multirom_deb_20150328.img
Once flash is complete confirm by booting into recovery and check to see if SD/Partitions mounted. Click the small square in the bottom and see if everything mounted correctly. if you see any red status stating mount error in (system, userdata, system -w, cache, ect something went wrong repeat process)
From this point your are good to go. Be advised flashing roms has a very particular setup that needs to be followed, reported by several members. I will show below
Wugs Nexus Toolkit
http://forum.xda-developers.com/showthread.php?t=2389107
Download your recovery image
Open Wugs Nexus Toolkit
Setup device preference
Go into advance
Click flash recovery
choose recovery image file
Let toolkit do its thing and when complete click boot recovery to confirm everything went ok
On device
Use cf-auto root to root your tab. Google it as it not hard to find. Once you confirmed root you can then download your image file on device and use flashify, TRWP Manager, (anything you can flash recovery on device)
Example:
Once root is confirmed use Flashify to select recovery image to flash. Once flash is complete boot into recovery by any means. confirm no error are present.
**FLASHING ROMS**
When installing any ROM disable "inject multirom after installation" & after installation just hit reboot system (don't hit "MultiROM: Inject curr. Boot sector) once you hit reboot you should be fine!
Direct link to files and some info for recovery
http://forum.xda-developers.com/showthread.php?t=2457063
Good Luck and hope everything works out.
Ok so here goes my issue. I just got my Nexus 7 2013 in the mail yesterday. I bought it specially to install in my Mitsubishi Lancer. Well going thru the motion that nay flasher would go thru I got machine environment setup (drivers, adb/fastboot, wugs program).
I unlocked thru Wugs OEM unlock procedure then followed with root + custom recovery
Thats where my problems start. Root was not sticking correctly/at all. I got all kinds if error thru TRWP about it unable to mount emmc, boot, userdata, system,....
I have restored thru Wugs program several timers now. I have full access to the tab as far as ADB and Fastboot. I have tried
Phliz Rcovery
CWM
TRWP
In All recoverys I get errors that I cannot mount any partitions and reads 0MB available. I have found cf-auto root to root my Nexus 7 so at least theres that but Im trying to flash either Timurs Kernel or Elemental but cant due to recovery cannot mount anything.
What I have done so far...
OEM Unlock -Pass
Wugs root + custom recovery - failed due to mounting issues
cf-auto root - Pass
Fastboot Erase: System -w, system, userdata, boot, recovery, cache - Pass
Fasboot format: System -w, system, userdata, boot, recovery, cache - Pass
stock recovery factory reset/cache wipe - Pass
At this point am i just SOL and just return my tab ( got it thru Groupon for $149.99 brand new) or is there hope and maybe im just not getting it right which i doubt as I did the same for my Nexus 6 and unlocked/rooted.
--------------
I dont know if this will help but my Tab came in out of box 5.0.1. When booted up an update for 5.0.2 was available so I took it.
here are some screenshots to help better explain. These are off TWRP and CWM. Also got a pic of my computer telling me that im on a wrong system setup even though I havent changed anything.,
So I went ahead and did flashed stock recovery. I am able to wipe cache and factory reset. Im still wondering if it just any custom recovery Im flashing that is preventing any kind of mounting.
Starting to see a trend now. Anyone who somehow if you got your tab with 5.0.1 out of the box and either updated to 5.0.2 you may run into issues with custom recovery not being able to mount partitions and what not.
Posting as much info as I can to see if anyone can help me as well as the thread either above me or below with trwp issues. So i tried loading up CM Installer as usually thats my sure fire way to install a custom rom should something be wrong on my end. CM Installer went thru the motion of getting everything setup and right after is indicates to plug in device for prepping and flashing a service warning comes up saying that
"Firmware unsupported for your device at this time"
Then big blue button to close application. So Im not sure what do at at this time as I am currently exhausting all my resources and Google maybe be getting tired of all my Nexus 7 search request.
Also update on what other "procedures" that I attempted
Download terminal from Play store. Tried setting sd as full mount - FAILED
^^ this actually made my tab go full retard as boot up and then kept booting into recovery(TWRP) and if I tired to reboot system or shutdown it would just boot back into TWRP. I had to use WUGS to full flash stock.
Same when trying chmod commands to force mount or force -rw
Booted into recovery and attempted to "ADB Shell" in recovery. Commands were recognized but denied due to mounting issues.
As much abuse I send to it I can still recover from it. I am kinda concerned that if I abuse it to much I may break it. Heres a weird thing
I tried cf-autoroot and watched the commands go thru and saw that cf-auto root can mount /system and /data and declare full mount and root device. After that you see that it puts files in their respected places
So looks like twrp updated there recovery today gonna see if this fixes anything
Well the the TWRP 2.8.6.0 didn't work either. I'm not sure what to do at this point as I've tried as many things as I can google and can't figure it out. I'm afraid that if try to claim replacement by group on I may get another tab that is similar to this which means I may have problems progressing forward with my goals.
I'm in the same boat, I was surprised to see that the cf autoroot went through without a *****.
I also tried to flash a 4.4.4 image and it wouldn't boot up or go past the google logo.
If anyone has any insight to this,it would be greatly appreciated.
I'm going to try flashing from otg when my cable comes in. I'll report back after.
Having the same issue too. Unboxed mine today, and went to look how to root, I can unlock it fine but whenever I go in recovery I can't do anything. Android still boots fine...
fragon69 said:
I'm in the same boat, I was surprised to see that the cf autoroot went through without a *****.
I also tried to flash a 4.4.4 image and it wouldn't boot up or go past the google logo.
If anyone has any insight to this,it would be greatly appreciated.
I'm going to try flashing from otg when my cable comes in. I'll report back after.
Click to expand...
Click to collapse
Did your tab out the box come 5.0 or higher. Seems like anyone who got there tab recently had 5.0 or later factory installed. Also with bootloaders you cannot go back when you pass a certain update in this case you if you ever hit 5.0.1 or higher then you cannot go back to anything 4.x.x. Also depends on what your tab shipped with
TrentB said:
Having the same issue too. Unboxed mine today, and went to look how to root, I can unlock it fine but whenever I go in recovery I can't do anything. Android still boots fine...
Click to expand...
Click to collapse
Yeah same here. I wanna get a video of me trying to complete everything. I mentioned this earlier but I am thinking thinking that any tab recently received and has 5.x.x out of box may have a problem. I'm trying to get devs to look I to this but all I'm getting is just get another tab or buy a used one. It doesn't solve the fact that you can still pick up a new one in stores and the ones coning out now are on 5.x.x I'm not trying to buy a second tab from Craigslist when I have a brand new first owner tab in front of me. **sigh first world problems.
TrentB said:
Having the same issue too. Unboxed mine today, and went to look how to root, I can unlock it fine but whenever I go in recovery I can't do anything. Android still boots fine...
Click to expand...
Click to collapse
When you setup your nexus did were you on 5.0.1 and asking for update when you were done with setup
Yeah, I got mine from Groupon too. 5.0.1 out of the box. Running it now on 5.0.2 stock and it is OK so I may put off rooting for a while until it gets settled.
DEVICE build DATE2014.12 later
android.googlesource.com/kernel/msm.git/+/fa842060088619d2de9986c5c5d588d0f40534e3%5E%21/
.......TWRP2.8.6 no FIX X(
masterchiefb117 said:
Ok so here goes my issue. I just got my Nexus 7 2013 in the mail yesterday. I bought it specially to install in my Mitsubishi Lancer. Well going thru the motion that nay flasher would go thru I got machine environment setup (drivers, adb/fastboot, wugs program).
I unlocked thru Wugs OEM unlock procedure then followed with root + custom recovery
Thats where my problems start. Root was not sticking correctly/at all. I got all kinds if error thru TRWP about it unable to mount emmc, boot, userdata, system,....
I have restored thru Wugs program several timers now. I have full access to the tab as far as ADB and Fastboot. I have tried
Phliz Rcovery
CWM
TRWP
In All recoverys I get errors that I cannot mount any partitions and reads 0MB available. I have found cf-auto root to root my Nexus 7 so at least theres that but Im trying to flash either Timurs Kernel or Elemental but cant due to recovery cannot mount anything.
What I have done so far...
OEM Unlock -Pass
Wugs root + custom recovery - failed due to mounting issues
cf-auto root - Pass
Fastboot Erase: System -w, system, userdata, boot, recovery, cache - Pass
Fasboot format: System -w, system, userdata, boot, recovery, cache - Pass
stock recovery factory reset/cache wipe - Pass
At this point am i just SOL and just return my tab ( got it thru Groupon for $149.99 brand new) or is there hope and maybe im just not getting it right which i doubt as I did the same for my Nexus 6 and unlocked/rooted.
Click to expand...
Click to collapse
rsusami said:
DEVICE build DATE2014.12 later
android.googlesource.com/kernel/msm.git/+/fa842060088619d2de9986c5c5d588d0f40534e3%5E%21/
.......TWRP2.8.6 no FIX X(
View attachment 3231340
Click to expand...
Click to collapse
Hmmmm I just checked mine and its 2015/02. I got another yesterday and that one is 2015.01. FML looks like new Nexus 7 coming out made a revision.
Yea mine was from 2014.12, from groupon too
fragon69 said:
Yea mine was from 2014.12, from groupon too
Click to expand...
Click to collapse
TrentB said:
Yeah, I got mine from Groupon too. 5.0.1 out of the box. Running it now on 5.0.2 stock and it is OK so I may put off rooting for a while until it gets settled.
Click to expand...
Click to collapse
Kinda weird that Groupon selling nexus on deals a d they for some reason no work right. Lol
One more with same issue
Bought from Groupon as will, came with 5.0.1. Haven't updated to 5.0.2 yet.
Unlocked bootloader and installed TWRP. It cannot mount anything (tried 2.8.6.0, 2.8.2.2, 2.8.1.0).
I hope this is a fixable issue. Would hate to return the tablet.
texag said:
Bought from Groupon as will, came with 5.0.1. Haven't updated to 5.0.2 yet.
Unlocked bootloader and installed TWRP. It cannot mount anything (tried 2.8.6.0, 2.8.2.2, 2.8.1.0).
I hope this is a fixable issue. Would hate to return the tablet.
Click to expand...
Click to collapse
Looking at other forums reporting that all Nexus 7 bought from Groupon having the same problems. I bought 2 more, 1 from Frys and another from Best Buy. They are also having issues. Something that they are shipping with them that is making it a problem.
Yesterday, my Samsung Grand Duo i9082 (GI9082, GT-i9082_CU) @ CM 10.1 decided to keep freezing on chinese logo screen. Booting into Odin still possible, but no matter what recoveries I tried to flash, nothing changes. For example, flashing philz_touch_5.15.0-i9082.tar.md5 via Odin software tells me it was a success, then reboots my device and I'm back at Odin mode - no clockworkmode in sight, nothing changed!
I used to install Odin and then CM 10.1, since those work with the chinese version of the Grand Duo which wasn't updated to 4.2.2. But sadly the download link (http://forum.xda-developers.com/showthread.php?t=2231953) expired, and while the source code is available on this link I have no clue on how to create a rom from it. Couldn't find any current ROMs that work with Odin and 4.1.2, hence I tried to install CMW and several others as recoveries instead.
Out of ideas and it's a shame because it seems to have a fine connection to the PC @ Odin recovery, but for some reason no recovery file I tried had any effect.
edit: That feeling, when after a whole day of trying and not having any success you finally got a step forward ........... damn. Found this thread: http://forum.xda-developers.com/showthread.php?t=2315529 and http://www.droidviews.com/best-custom-roms-for-samsung-galaxy-grand-duos-gt-i9082/, flashed CMW 6.3.0.2 with Odin and apparently you have to press volume up + home + power in order to enter CMW. God damn Let's see if this will lead to final success...
edit 2: All I need now is any ROM for 9082 v4.1.2. Hmm.
edit 3: Found the xperia mod whose older version works with 4.1.2: http://forum.xda-developers.com/showthread.php?t=2304492. Trying it tomorrow. This is intense.
All the best mate.
Looking at your situation, I would have suggsted you to upgrade to 4.2.2, but then it seems you have found a solution.
BTW, I love CM10.
vdbhb59 said:
All the best mate.
Looking at your situation, I would have suggsted you to upgrade to 4.2.2, but then it seems you have found a solution.
BTW, I love CM10.
Click to expand...
Click to collapse
Don't think I can upgrade to 4.1.2, wouldn't know how. But I don't care anymore because I got a working phone again )))))
I found out that the original installation files including the 10.1 rom were still on the sd card. Simply reinstalled it.
But really odd, for the phone suddenly freezing for no apparent reason ...
edit: I just looked at the settings, and it's version 4.2.2. That's interesting, I could have sworn I had trouble updating it back then and gave up at some point back then. Hmm. That means I could install the latest CM even, I guess .... but then again, never change a running system, ay?
Lastedit: Trying to update to CM 14 did not work, it ended in a simple boot-loop. I'm back on good ol' 10.1 now
Quick-howto for future me: 1)keep volume-up, home + power pressed to enter Clockworkmod 2) wipe cache/reset to factory 3) install cm 10.1 4) install gapps 5) done.
misterioes said:
Don't think I can upgrade to 4.1.2, wouldn't know how. But I don't care anymore because I got a working phone again )))))
I found out that the original installation files including the 10.1 rom were still on the sd card. Simply reinstalled it.
But really odd, for the phone suddenly freezing for no apparent reason ...
edit: I just looked at the settings, and it's version 4.2.2. That's interesting, I could have sworn I had trouble updating it back then and gave up at some point back then. Hmm. That means I could install the latest CM even, I guess .... but then again, never change a running system, ay?
Lastedit: Trying to update to CM 14 did not work, it ended in a simple boot-loop. I'm back on good ol' 10.1 now
Quick-howto for future me: 1)keep volume-up, home + power pressed to enter Clockworkmod 2) wipe cache/reset to factory 3) install cm 10.1 4) install gapps 5) done.
Click to expand...
Click to collapse
If you are on 4.2.2 then try CM11 and CM12.1 (Jan build).
Same pattern.
Edit: CM11: http://forum.xda-developers.com/showthread.php?t=2563557
CM12.1 (Only the ROM File link): http://forum.xda-developers.com/gal...cm-12-1-pawitp-jan-april-build-files-t3450122
I have Oneplus One with CyanogenMod 13.x. As of now, there's no CyanogenMod anymore, so I decided to leap to another ROM so I can keep using this toy for a while longer.
Now I have an issue with Paranoid Android 6.0.2 and 7.2.1 (two of the earliest latest roms in site). I'm stuck in bootloop.
I unlocked the bootloader, flashed TWRP in, flashed Paranoid Android. Both of these PA ROMs decided to get stuck in loading screen between device boot and OS. Should I flash GApps before booting, or should it boot without them? I have a feeling that it should. But if not, then I have another issue. I was dum-dum enough to download full open-GApps package. This results in "error 70" during GApps flash because system partition "has insufficient space". :silly:
Do I really have to go and sideload smaller GApps in there? Just for the record, I'm not flashing things first time. Only confirming my own speculations.
UPDATE #1: Never mind. I *think* I found the cause. I always rooted my phone after flashing. It seems that I had bad SuperSU and it messed up with the flash. I flashed LineageOS and decided to not root. It works neatly (well, as neatly as nightlies can work). Tomorrow I'll try same with PA and see how it goes. My guess is, that it will work just as neatly.