Database Users

[Q] Nexus 7 2012 Wifi Model Flashing Problem!!!!!

Hello, I have a 2012 WiFi Nexus 7. I recently read a post that has the link to the latest android lollipop 5.0 system image tgz file available which they extracted from the servers of Google, before they updated the website.
Excited, i downloaded the image, and tried to flash it via wugfresh's nexus root toolkit. (i was rooted). I extracted the tgz file and flashed the different partitions one by one via the toolkit. When i tried booting it, it stayed on the google logo. So went back to bootloader and tried to boot into recovery, but it said on the top left corner in small fonts that "could not boot"or something similar to that. worried, i flashed twrp via adb from the toolkit manually and rebooted normally into recovery. The log said it couldnt mount /system and /data. so i formatted the system and cache partition via adb and formatted /data from twrp. i somehow managed to push a slimkat ROM zip in the internal storage and install it. No gapps, no root nothing. its just like that, functioning normally. i have the original 4.4.4 tgz file. should i flash it via android sdk adb?
Can i be sure it wont give me such problems? and why did such a thing happen? please help me out

niranjan_23 said:
Hello, I have a 2012 WiFi Nexus 7. I recently read a post that has the link to the latest android lollipop 5.0 system image tgz file available which they extracted from the servers of Google, before they updated the website.
Excited, i downloaded the image, and tried to flash it via wugfresh's nexus root toolkit. (i was rooted). I extracted the tgz file and flashed the different partitions one by one via the toolkit. When i tried booting it, it stayed on the google logo. So went back to bootloader and tried to boot into recovery, but it said on the top left corner in small fonts that "could not boot"or something similar to that. worried, i flashed twrp via adb from the toolkit manually and rebooted normally into recovery. The log said it couldnt mount /system and /data. so i formatted the system and cache partition via adb and formatted /data from twrp. i somehow managed to push a slimkat ROM zip in the internal storage and install it. No gapps, no root nothing. its just like that, functioning normally. i have the original 4.4.4 tgz file. should i flash it via android sdk adb?
Can i be sure it wont give me such problems? and why did such a thing happen? please help me out
Click to expand...
Click to collapse
Don't use toolkits
Better flash the factory image from 4.4.4 and try again

GtrCraft said:
Don't use toolkits
Better flash the factory image from 4.4.4 and try again
Click to expand...
Click to collapse
So you mean i flash using the adb provided by google?
btw, i uninstalled the nexus toolkit but let the drivers be in the system. do i have to remove those too? if yes then how?
and r u sure my filesystem wont get corrupt again with stock adb? coz i never used the toolkit for my nexus 4 for as many times ive flashed; ive used stock adb.
why did this happen although?

[Q] TWRP Copy Files on Nexus 7

Hey guys,
Maybe the problem was already encountered by some of you, ok here it goes.
I'm trying to flash a F2FS Slimkat rom on my laggy Nexus 7 grouper. I unlocked the bootloader, flashed TWRP 2.8.2 and rooted the tablet, everything went fine.
After that it got a little tricky, I wiped the system and changed the format partition of cache, system and data to F2FS separately but when I try to mount my Nexus to put the zipped rom and the gapps afterwards, it appears on my Desktop but the files can't be transferred on it.
So my question is, how to transfer the zip files onto the Nexus after rooting it and turning all the partitions into F2FS because afterwards I'm not able to copy anything on it.
Thanks in advance
Saltari

I always use adb push without problems (on F2FS in TWRP, too)

Thanks, using adb push worked. I was able to flash both the rom and the gapps but now I'm stuck on a bootloop with the google logo and the black screen. What did I do wrong ?

Saltari said:
Thanks, using adb push worked. I was able to flash both the rom and the gapps but now I'm stuck on a bootloop with the google logo and the black screen. What did I do wrong ?
Click to expand...
Click to collapse
I don't know, but here are some things you could try:
full wipe & flash only the rom without gapps
repair the file systems (same menu as reformat) and reflash
try other/smaller gapps (maybe the beta gapps from slimroms? they work for 4.4 although they're labeled 5.0)
try another rom

From Philz to Flyme (official firmware) MX4

Good evening everyone.
I write because I have a problem with the installation of the CM on my meizu MX4.
I ran perfectly the procedure of unlocking the bootloader, and once unlocked, I flashed the recovery Philz. Later I tried to flash the CM with adb, but in at end it always says "Installation Aborted". I tried with the patched recovery and with cofface, but I just can not flash it.
I then tried to do a wipe cache but no with any recovery that I flashed always appears to me:
"E: Can not mount / cache / recovery / command
E: Can not mount / cache / recovery / log
E: Can not open / cache / recovery / log
E: Can not mount / cache / recovery / last_log
E: Can not open / cache / recovery / last_log "
I read here http://forum.xda-developers.com/meizu-mx/general/tutorial-bootloader-unlocking-mx4-m1-t3201715 that I could flash the patched rom deleting the file uboot.img and preloader.bin but I can not find anywhere the second file, and also I'm afraid to brick the phone ... someone has already done it?
Tell me that at least in the future I will be able to install the CM. Loved and hated Flyme.
Sorry for the English and thanks in advance for your reply.

Why you don't install CM from the recovery?
Sent from my D6603 using Tapatalk

I has this problem also when try to wipe cache. I fix cache mount with "wipe for new rom" option in wipe menu on philz recovery.
After that install cyanogen .zip with recovery.
Now i'm back to flyme but i flash patched flyme4.5.6i-twrp.zip found on 4pda forum, with twrp recovery for mx4.
Here is link for tutorial *4pda.ru/forum/index.php?showtopic=689760&st=780#entry43612111*
My MX4 is now on Flyme international version (original was A firmware) and i still have unlocked bootloader and custom recovery.
Everything works fine without any bug.

artlov I installed the recovery and then I did:
1) install zip
2) install zip from sideload
3) MX4 connect to pc
4) open CDM and write "adb devices" enter
5) "adb sideload cm12 ect * enter *
6) sull'mx4 appeared the word "installation aborted" after loading on pc
Now i have flyme 4.2.8.2A with philz recovery.
mmdag82 i don't find on philz the option "wipe for new rom"

"Clean to Install a New Rom" is exactly name of option under Wipe menu

And then i can try to flash CM? By terminal or with file zip on mx4's memory?
Thank you for your answers!

With zip file on mx4 memory

did you tried factory reset because you must do that befor adb sideload and i woildn't do Clean to Install a New Rom because it will delete everything about current system

Yeeah! CM installed! Thanks a lot guys!

MX4 not read sim card with CM...

federicolucchesi said:
artlov I installed the recovery and then I did:
1) install zip
2) install zip from sideload
3) MX4 connect to pc
4) open CDM and write "adb devices" enter
5) "adb sideload cm12 ect * enter *
6) sull'mx4 appeared the word "installation aborted" after loading on pc
Now i have flyme 4.2.8.2A with philz recovery.
mmdag82 i don't find on philz the option "wipe for new rom"
Click to expand...
Click to collapse
There is a solution. Try to reflash the patched recovery.
Now reflash 4.2.1.2 with clean.
Reboot, and reroot, reinstall flashify and terminal.
Do again the tuto step by step.
Try and tell me
Edit : Sorry, i didn't saw you have done ^^

I've done! Not reads SIM but i think is problem of card, cause i tried other SIM that weren't chopped from old SIM card and them run perfectly!

Hey,
hope somebody can help me.
I wanted to install flymeos on my arale until the cm-version is usable for me.
I am only able to install version 4.0.4 i or a but i cannot upgrade nor directly flash a version later than that...
I tried several recoveries (philz, cofface, twrp) and several versions (4.2.8.2i/a, 4.5.6i). Any ideas?
-----------------
EDIT: Recovery logs always tell me that there is no space on /custom left. Do i have to reformat my arale with a android scatter? I installed 4.0.4 and ran fastboot -w. Thought this would be sufficient. /custom is only 4.8M big...

[Nexus 6P] Wiped System Partition in TWRP -- "No OS Installed" Help.

Hi, all.
I accidently wiped the system partition of my Nexus 6P in TWRP. I have a Pure Nexus ROM and gapps on my computer, that I've been trying to flash via adb sideload. The sideloading goes successfully, and it seems like the ROM is flashed. But when I go to reboot, I get a warning from TWRP: "No OS Installed". How is there no OS installed when I've flashed a ROM? Isn't that the OS?
What steps should I take to unbrick my phone? Thanks in advance.

It sounds like you're only putting the image on your phone, only the first half of the resolution?
Either use USB to move the file over to the internal storage, or ADB push the file, and then use TWRP to flash the ROM as normal.

lineage recovery Issue/error?

After successfully installing Android 11 on a brand-new nexus 4 i got, i then went to try the same thing on a used one (for my dad)
The phone now as it stands is stuck on lineage recovery and i get this message.
error: android failed to bind mount /mnt/staging/emulated/media/0
I choose wipe cache/data etc because it was running an older rom i think Droid 7 or 8
Then after reboot just stuck in recovery and can't use adb on pc or anything
I can't even use ADB it doesn't list the device
So what do i do? anyway i can install a stock rom if so how?
I fear my dads Nx4 is BRICKED lol

Going to use the nexus rootkit to bypass that crap and install a stock rom for my dad