Hello all,
I left a similar post in a couple other threads, and thought maybe someone here might have some insight into my problem.
Been running AICP rom (no custom kernel except the one that comes with AICP) with f2fs on /data and /cache for several months on 16GB grouper. About a month or so ago, the wife installed a game that wouldn't run on this hardware (King's Paradise Bay), and I uninstalled it. It left a file in /data/data/....etc that couldn't stat in TWRP, so no nandroid backups since then. I figured I'd just backup user data with TiBkp and wipe with fresh install of latest AICP when time permitted.
The other night I noticed the N7 was boot looping, getting to the stage where the boot animation dims. The boot anim would hang and after several seconds the Google unlock splash screen would come up and the N7 would try to boot again.
I can get into TWRP and bootloader with no problem. However, when TWRP comes up, the log shows the red entries for 2 files that can't stat, which has been this way since that game was uninstalled. I cannot seem to wipe *any* partition, and when I attempt to format or wipe userdata in TWRP, the N7 spontaneously reboots. Manually attempting to wipe/format/etc. via FastBoot doesn't work, with error message showing after trying to flash bootloader. Also, I can't change /data or /cache back to ext4. I am able to successfully read, write, and delete files on the N7 via computer USB MTP connection.
If the N7's flash memory has somehow become corrupted, is there a way to completely erase/format/whatever so that this wonderful device can become usable again? Any help would be greatly appreciated.
Thanks in advance.
Hello,
don't flash Bootloader via Fastboot. You should do this commands:
Code:
fastboot erase cache
fastboot erase userdata
fastboot erase system
fastboot erase boot
Trafalgar Square said:
Hello,
don't flash Bootloader via Fastboot. You should do this commands:
Code:
fastboot erase cache
fastboot erase userdata
fastboot erase system
fastboot erase boot
Click to expand...
Click to collapse
Yes, I have attempted all these commands, followed by flashing with either fastboot or TWRP with no success. Fastboot reports success, but partitions are not erased.
I have the same problem. The Nexus Root Toolkit can not flashign. It succeeds only boot TWRP. In TWRP computer sees the files from the tablet.I could not rename and delete. Wipe the TWRP and stock recovery displays the status OK, and the files are deleted. Fastboot shows that uploads, but all files remain unchanged.
Related
My N7 is unlocked, I upgraded to 4.2.2 factory stock, rooted, and flashed ClockworkMod Recovery 6.0.2.3 touch recovery. I ran into a very strange issue; if I flash the custom recovery on the tablet, then the tablet boots into a screen that asks me to type my password to decrypt storage not allowing me to enter the homescreen until I do so. Later, I found out that flashing back to stock recovery fixes the problem and my N7 is functional again. I've tried everything while on the custom recovery: erasing, formatting, writing userdata to the device without success.
I'm not really sure what question you are asking. Also, I think you might be leaving something out which ought to be clarified, the way you describe things seems to have some pieces missing. (And, you really should not be starting yet another thread on this)
You shouldn't be able to flash custom ROMs with a stock recovery; so, are you saying that you:
- flash a ROM with a custom recovery
- try and boot it -- but it fails with the "enter password" prompt (you mention "won't let me enter the homescreen")
- flash the stock recovery into place
- perform a factory reset with the stock recovery
- now the ROM boots?
Also, do you get the same result with TWRP?
bftb0 said:
I'm not really sure what question you are asking. Also, I think you might be leaving something out which ought to be clarified, the way you describe things seems to have some pieces missing. (And, you really should not be starting yet another thread on this)
You shouldn't be able to flash custom ROMs with a stock recovery; so, are you saying that you:
- flash a ROM with a custom recovery
- try and boot it -- but it fails with the "enter password" prompt (you mention "won't let me enter the homescreen")
- flash the stock recovery into place
- perform a factory reset with the stock recovery
- now the ROM boots?
Also, do you get the same result with TWRP?
Click to expand...
Click to collapse
It's a help/troubleshooting post. I know it wasn't good to start another thread, but I felt that people that had already browsed my thread the first time wouldn't come back and now I found the reason behind my issue. I didn't flash a custom rom with stock recovery; I used fastboot on my pc to issue commands. My phone has the factory stock rom on it - then if I flash clockworkmod recovery, the next time I reboot, there's a screen that says I need to type a password to decrypt storage and I'm not able to access anything. If I go back into the bootloader and erase and write the stock recovery, I'm able to boot into the homescreen without the issue. Everything I've flashed to the tablet is done through my pc via fastboot. I never tried TWRP, but I don't like that recovery anyways.
UnlockedNand said:
It's a help/troubleshooting post. I know it wasn't good to start another thread, but I felt that people that had already browsed my thread the first time wouldn't come back and now I found the reason behind my issue. I didn't flash a custom rom with stock recovery; I used fastboot on my pc to issue commands. My phone has the factory stock rom on it - then if I flash clockworkmod recovery, the next time I reboot, there's a screen that says I need to type a password to decrypt storage and I'm not able to access anything. If I go back into the bootloader and erase and write the stock recovery, I'm able to boot into the homescreen without the issue. Everything I've flashed to the tablet is done through my pc via fastboot. I never tried TWRP, but I don't like that recovery anyways.
Click to expand...
Click to collapse
OK, read and understood. Very bizzare, however. Almost sounds more like something caused by the bootloader (during the fastboot write) rather than it mattering which custom recovery is sitting there (it's not clear from the above, but it almost sounds like it is not even necessary to have ever booted the custom recovery from the device's recovery partition for the problem to appear)
Are you also saying that you can not flash a custom ROM from the custom recovery without this "enter password" phenomenon happening, or is it only this combo of pure stock ROM + recovery flashed via fastboot that exhibits the problem?
I have a lightly-rooted JDQ39 Stock (4.2.2) ROM with a custom recovery - no such troubles. But mine was installed by using factory-via-fastboot of 4.2.1, followed by a manually-triggered OTA to JDQ39, and then followed in turn by a fastboot flash of the recovery partition (TWRP 2.4.1.0). That last flash was certainly performed by the 4.18 bootloader.
No troubles, but that is certainly a different installation path.
Two more small questions for clarification purposes: when you installed the factory 4.2.2 ROM via fastboot, did you follow the exact sequence of the install-all.sh script:
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-4.18.img
fastboot reboot-bootloader
sleep 10
fastboot -w update image-nakasi-jdq39.zip
... or did you omit anything (e.g. one or more of the erases, the bootloader flashing, etc)?
Yeah, it's like the bootloader writes bad information to the userdata partition if the recovery isn't stock. I haven't flashed a custom rom from the custom recovery, but I'm assuming the type your password issue would appear again. Yes, it's a combo of pure stock rom + custom recovery when this problem occurs. No, when I installed the 4.2.2 factory stock rom, I unzipped all the image files and typed these commands.
Code:
fastboot oem lock
fastboot oem unlock
fastboot flash bootloader <bootloader name>.img
fastboot flash boot <boot name>.img
fastboot flash system <system name>.img
fastboot flash userdata <userdata name>.img
fastboot reboot-bootloader
fastboot erase cache
fastboot reboot
I've also gone back and manually erased, formatted, and wrote the userdata partition again. Maybe I should try downgrading the bootloader to 4.2.1, reflash userdata, and flash the custom recovery?
UnlockedNand said:
Yeah, it's like the bootloader writes bad information to the userdata partition if the recovery isn't stock. I haven't flashed a custom rom from the custom recovery, but I'm assuming the type your password issue would appear again. Yes, it's a combo of pure stock rom + custom recovery when this problem occurs. No, when I installed the 4.2.2 factory stock rom, I unzipped all the image files and typed these commands.
Code:
fastboot oem lock
fastboot oem unlock
fastboot flash bootloader <bootloader name>.img
fastboot flash boot <boot name>.img
fastboot flash system <system name>.img
fastboot flash userdata <userdata name>.img
fastboot reboot-bootloader
fastboot erase cache
fastboot reboot
I've also gone back and manually erased, formatted, and wrote the userdata partition again. Maybe I should try downgrading the bootloader to 4.2.1, reflash userdata, and flash the custom recovery?
Click to expand...
Click to collapse
Hmmm. Well, I can't say for sure, but I am willing to gamble that the bootloader relocates itself into a load-offset address so that it runs out of RAM rather than running directly out of Flash Memory. Much quicker that way. The implication of that is that once it is fully loaded into RAM and operational, you could actually erase the bootloader and suffer no ill effects - until you powered off the device. Then you would be in real trouble.
The point is, in the Google factory sequence, all of the partition flashing is done by the new bootloader (4.18), whereas in your case none of it is done that way - except for the custom recovery flash. Here's the Google sequence:
- erase all partitions using currently installed bootloader (4.13)
- flash new bootloader and boot into it ( 4.13 -> 4.18 )
- flash all 4.2.2 ROM partitions using new bootloader
whereas your sequence looks like:
- (no explicit erasures)
- flash partitions with old bootloader (4.13)
- reboot into new bootloader ( 4.13 -> 4.18 )
- erase cache
- flash recovery with new bootloader ( 4.18 )
very different!
Also, the "-w" switch used in the google sequence causes partition erasure and re-formatting (depending on partition type) prior to each partition's flashing.
Without going through the lock/unlock procedure, I suppose it would be possible to reflash all the partitions with 4.18 to see if the problem disappears. But, now that I said that, I realize my tab - which had an OTA upgrade - is sort of similar in that the partitions & files patched by the OTA were all initially flashed by 4.13 (by me), patched by the OTA, and then finally I flashed only the custom recovery with the 4.18 bootloader.
Doing further experimentation might mean attempting a bootloader rollback flash. I can't say that I've seen reports here of anybody trying it. And I can't say I blame them - there could be dragons hiding in that process.
Ah, I see. The sequence I followed flashing the partitions would erase and write the partitions automatically done by the fastboot script. The only instance where I erased, formatted, and flashed the partition was the userdata when I was troubleshooting. From reading other threads before, I believe people have done bootloader rollbacks without consequences to the rest of the partitions. The bootloader updates contain fixes, but aren't explicitly required for the rom to run, am I correct?
I'm selling my Nexus 7 and I think I got a little click happy while clearing it out.
I had reinstalled 4.3 and then for some reason I formatted the data. Got stuck in a boot loop.
When I try to install the image again I get the following:
Updating partition details...
E:error opening '/data/media'
E:error: no such file or directory
Any help would be appreciated!
"90% of the time, when someone says something's bricked, the only brick is their head." - Koush
All this means is that your userdata partition got all jacked up. It's restored when you boot into a rom, but of course you can't boot into a rom cause something else must have also went awry. So I suggest you wipe everything and start over. Follow along with me, this will be fun!
Boot into fastboot, send fastboot unlock command if your bootloader isn't already unlocked "fastboot oem unlock." Accept on screen. Reboot back into bootloader/fastboot. Issue FASTBOOT ERASE USERDATA, FASTBOOT ERASE RECOVERY, FASTBOOT ERASE CACHE, FASTBOOT ERASE SYSTEM. Then flash TWRP recovery using FASTBOOT FLASH RECOVERY [NAME OF TWRP GROUPER IMG]. Then adb push your rom and gapps back to your tablet using ADB PUSH [FILE] /SDCARD, then flash your rom and enjoy a fresh clean tablet!
That's why I prefixed with 'possible'...
Thanks - I followed this guide later in the evening and got it all up and going again.
http://goo.gl/BsiewY
0vermind said:
"90% of the time, when someone says something's bricked, the only brick is their head." - Koush
All this means is that your userdata partition got all jacked up. It's restored when you boot into a rom, but of course you can't boot into a rom cause something else must have also went awry. So I suggest you wipe everything and start over. Follow along with me, this will be fun!
Boot into fastboot, send fastboot unlock command if your bootloader isn't already unlocked "fastboot oem unlock." Accept on screen. Reboot back into bootloader/fastboot. Issue FASTBOOT ERASE USERDATA, FASTBOOT ERASE RECOVERY, FASTBOOT ERASE CACHE, FASTBOOT ERASE SYSTEM. Then flash TWRP recovery using FASTBOOT FLASH RECOVERY [NAME OF TWRP GROUPER IMG]. Then adb push your rom and gapps back to your tablet using ADB PUSH [FILE] /SDCARD, then flash your rom and enjoy a fresh clean tablet!
Click to expand...
Click to collapse
Ok, so this is an odd issue. I've had my N7 Grouper unlocked and have been running custom roms for a long time now, and about 6 months back I tossed on the All-F2FS version of Slimkat. Everything was running fine and has been since then, up until the last few days. Now the device just reboots randomly after it gets into the system. It runs fine in bootloader or recovery so I know it's not a loose battery connector as I've read about. I'm at a loss as to why and I gave up trying to find out.
I've since been trying to simply wipe my tablet and reset back to a clean install of the All-F2FS Slimkat as I've had or even tried a stock restore now. Nothing I do works at all. I've tried everthing from the modified All-F2FS TWRP 2.7.0.0 that I installed as a part of the move to F2F2 but although it reports that it's wiped everything fine, or flashed a new rom fine, it does nothing in truth. After a quick reboot its as if nothing happened at all. I've then tried to run things from adb/fastboot and I'm even after running all the commands in fastboot which all say they run fine (flashing, reformatting partitions, etc.) nothing at all actually happens to the N7.
Anyone else seen this or have any ideas?
Hello,
please try this command's:
Code:
fastboot erase cache
fastboot erase system
fastboot erase userdata
fastboot erase recovery
fastboot erase boot
Then flash a FactoryImage! At least root and flash again.
Trafalgar Square said:
Hello,
please try this command's:
Code:
fastboot erase cache
fastboot erase system
fastboot erase userdata
fastboot erase recovery
fastboot erase boot
Then flash a FactoryImage! At least root and flash again.
Click to expand...
Click to collapse
I've tried all of those commands multiple times. I'm an old hat at rooting, unlocking, and running custom roms on Android so I've been doing literally everything I can think of. Every command shows that it completes successfully but nothing actually happens. I've tried fastboot erase commands, fastboot format commands, fastboot flash commands, and many many more. I've run six different versions of the factory image, everything from 4.0.0 to 5.1.1. The only errors I've ever seen while working with the tablet is while attempting to erase/format partitions within the recovery there are some errors about not being able to access the cache. I'll update this with the specific errors.
Anyone? I'm at a loss here. I've run everything I can think of and the commands always complete successfully, then don't actually work at all.
Hi,
I have a Nexus 4 which was flashed with Lollipop 5.1.1.
My problem started when, after letting the battery completely drain and then trying to turn the phone on again, I got stuck on the message "Android is starting... optimizing apps" for days. I tried rebooting and factory format with no success.
I also tried formatting it through TWRP, but I got the message "Unable to mount /cache". After that, I tried flashing older factory images but only got my phone to work with the oldest version of jelly bean available by google developers page (4.2.2). After I got it to work, I tried to OTA update it to 4.3, but the same message "Android is starting ... optimizing apps" came back.
I had no other choice but to fastboot format it and flash it again with 4.2.2.
Any ideas on what could possibly be causing this? I thought it might be some problem in the cache partition but haven't found a way to fix it or if it's even possible to. Apparently everything's working with 4.2.2 but I'd love to go back to 5.1.1!
Thanks in advance!
dont dirty flash the factory image. make a clean factory image flash
After flashing stock KK or LP, are you also flashing userdata.img and then booting into stock recovery to format/wipe data before booting the ROM for the first time?
audit13 said:
After flashing stock KK or LP, are you also flashing userdata.img and then booting into stock recovery to format/wipe data before booting the ROM for the first time?
Click to expand...
Click to collapse
Haven't tried that, I'll give it a go and post the results here!
I've also noticed the phone isn't receiving any signal and it doesn't display the IMEI anymore..
The lack of an imei is a definite problem. Try flashing the stock LP or KK ROM and check for the imei.
audit13 said:
The lack of an imei is a definite problem. Try flashing the stock LP or KK ROM and check for the imei.
Click to expand...
Click to collapse
Did a clean factory image flash of Lollipop 5.1.1, booted into twrp recovery (I'm not sure how to go back to stock recovery) to wipe the data and got the following message:
E: UnMount: Unable to find partition for path '/sdcard'
E: Mount: Unable to find partition for path '/sdcard'
Updating partition details...
E: Unable to mount '/cache'
...done
E: Unable to mount '/cache'
Full SELinux support is present
E: Unable to mount '/cache'
E: Unable to mount '/cache'
MTP Enabled
Formatting Data using make_ext4fs function.
Ypu may need to reboot recovery to be able to use /data again.
Updating partition details...
E: Unable to mount '/cache'
...done
After that I rebooted the phone and it's been stuck on bootloop again since then.
When you flash a stock ROM, did you flash the recovery.img? Sometimes, I find that only stock recovery can properly format the cache. When flashing my Nexus 5 to stock from a custom ROM, I get an error message when I boot into stock recovery that the cache has an invalid format. Once I perform a factory wipe, the cache is properly formatted and wiped.
audit13 said:
When you flash a stock ROM, did you flash the recovery.img? Sometimes, I find that only stock recovery can properly format the cache. When flashing my Nexus 5 to stock from a custom ROM, I get an error message when I boot into stock recovery that the cache has an invalid format. Once I perform a factory wipe, the cache is properly formatted and wiped.
Click to expand...
Click to collapse
Yeah, I flashed the images for boot, recovery, system, userdata and cache separately. I'll look up how to get back into stock recovery now and I'll try what you've said!
If recovery.img was flashed, the phone should not have TWRP, it should be a stock recovery. If stock recovery cannot be flashed, this leads to me believe that something is wrong with the memory chip.
audit13 said:
If recovery.img was flashed, the phone should not have TWRP, it should be a stock recovery. If stock recovery cannot be flashed, this leads to me believe that something is wrong with the memory chip.
Click to expand...
Click to collapse
I tried it again, flashed everything including recovery, went into stock recovery mode and wiped the data. Apparently its back to being stuck on bootloop
Use fastbot commands to erase cache and userdata. Then use fastboot to flash the userdata.img file, boot directly to recovery, and wipe again.
audit13 said:
Use fastbot commands to erase cache and userdata. Then use fastboot to flash the userdata.img file, boot directly to recovery, and wipe again.
Click to expand...
Click to collapse
Did it, still stuck on bootloop... Not sure if it can be somehow related but I got this message when I booted into recovery
The recovery screen looks correct because, after flashing userdata.img, you must format in stock recovery.
I am at a loss as to why 4.2.2 works while kk and LP do not.
audit13 said:
The recovery screen looks correct because, after flashing userdata.img, you must format in stock recovery.
I am at a loss as to why 4.2.2 works while kk and LP do not.
Click to expand...
Click to collapse
Ah, thanks for the help, anyway!
If someone else knows what to do.. The phone is now back to the initial message "android is starting... optimizing apps". Kinda of losing hope now
I've done this to my Nexus 5 once, too.
You basically screwed your cache partition.
Boot into the bootloader. Hook the phone up to your pc and open the command prompt.
Enter these commands:
fastboot erase cache
fastboot format cache
fastboot reboot-bootloader
When successful boot into recovery and the errors should be gone.
You should be able to flash a new rom now.
playitlouder said:
I've done this to my Nexus 5 once, too.
You basically screwed your cache partition.
Boot into the bootloader. Hook the phone up to your pc and open the command prompt.
Enter these commands:
fastboot erase cache
fastboot format cache
fastboot reboot-bootloader
When successful boot into recovery and the errors should be gone.
You should be able to flash a new rom now.
Click to expand...
Click to collapse
This got rid of the unable to mount cache error, flashed the rom again but it's still stuck on bootloop :/
thafuchs said:
This got rid of the unable to mount cache error, flashed the rom again but it's still stuck on bootloop :/
Click to expand...
Click to collapse
Okay. Progress
You have probably already nuked all your data. So I would suggest erasing and formatting everything again and then flash the newest factory image.
Enter bootloader again, on your pc do the following:
fastboot erase system
fastboot format system
fastboot erase data
fastboot format data
fastboot reboot-bootloader
Then grab the factory image, open the flash_all.bat file in an text editor (either use windows notepad, or grab notepad++).
You have to "cd" to the directory of your factory image. I would suggest to type "c:" *press enter* then cd *pull the folder that contains the factory image into the command prompt* *press enter*.
If you type "dir" now you should get your factory image directory.
Now just type in every command from the flash_all.bat one by one. Report, if there are any errors.
playitlouder said:
Okay. Progress
You have probably already nuked all your data. So I would suggest erasing and formatting everything again and then flash the newest factory image.
Enter bootloader again, on your pc do the following:
fastboot erase system
fastboot format system
fastboot erase data
fastboot format data
fastboot reboot-bootloader
Then grab the factory image, open the flash_all.bat file in an text editor (either use windows notepad, or grab notepad++).
You have to "cd" to the directory of your factory image. I would suggest to type "c:" *press enter* then cd *pull the folder that contains the factory image into the command prompt* *press enter*.
If you type "dir" now you should get your factory image directory.
Now just type in every command from the flash_all.bat one by one. Report, if there are any errors.
Click to expand...
Click to collapse
Okay, got some errors on the way... trying to erase data failed (Remote: partition table doesnt exist), format data failed too (formatting is not supported for filesystem with type ' '.)
Also, on the last command:
.\fastboot -w update .\image-occam-lmy48t.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
[...]
checking version-bootloader
FAILED
Device version-bootloader is 'MAKOZ10o'
Update requires 'MAKOZ30f'
Rebooted and its now stuck on google logo
Sorry, you should have typed: (it obviously cannot format something that is not there )
fastboot erase userdata
fastboot format userdata
Have you flashed the bootloader?
Have you rebooted after flashing the bootloader?
fastboot flash bootloader bootloader-mako-makoz30f.img
fastboot reboot-bootloader
Don't forget to also flash the radio.
These "does not contain" errors are normal.
playitlouder said:
Sorry, you should have typed: (it obviously cannot format something that is not there )
fastboot erase userdata
fastboot format userdata
Have you flashed the bootloader?
Have you rebooted after flashing the bootloader?
fastboot flash bootloader bootloader-mako-makoz30f.img
fastboot reboot-bootloader
Don't forget to also flash the radio.
These "does not contain" errors are normal.
Click to expand...
Click to collapse
Okay, I've flashed bootloader, rebooted, flashed radio, rebooted, typed the update command but the checking of bootloader version failed again.. rebooted and its back to being stuck on google logo
It started acting weirdly after shutting down while it was updating some apps. First, it would only function normally when on the charger (it was really erratic off it, shutting down when turning on the data/wifi).
After one day it got briefly stuck in a bootloop, and afterwards it would just display the Google logo and shutdown (or, if on charger, reaching the "Optmizing apps.." screen, and shutdown).
I attempted a "wipe cache", "Factory Reset", and flashed different stock ROMs using the Skipsoft Toolkit, all for no avail.
Is there anything else that can be done?
I suggest manually flashing each partition, including the userdata.img file. After flashing the userdata.img file, boot directly into recovery from fastboot, factory wipe, reboot. Hopefully, this will allow the phone to boot.
audit13 said:
I suggest manually flashing each partition, including the userdata.img file. After flashing the userdata.img file, boot directly into recovery from fastboot, factory wipe, reboot. Hopefully, this will allow the phone to boot.
Click to expand...
Click to collapse
Thanks. I flashed each partition manually, but it then gives mount erros on mount/cache/recovery/log and the boot never ends. These are the steps I took:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot flash bootloader "name of bootloader"
fastboot reboot-bootloader
fastboot flash radio "name of radio"
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot erase userdata
fastboot flash userdata userdata.img
I also tried directly fastboot -w update "zipfile", but it then shutdowns after booting.
After flashing userdata.img, you boot straight to recovery without trying to boot the rom? For mine phones, it's normal for there to be an cache mount error in recovery. After performing a factory wipe in the stock recovery, everything gets formatted and the phone is able to boot.
audit13 said:
I suggest manually flashing each partition, including the userdata.img file. After flashing the userdata.img file, boot directly into recovery from fastboot, factory wipe, reboot. Hopefully, this will allow the phone to boot.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2160124 try this, but be careful
I am not the person having a problem with the nexus 4.
ftkg said:
It started acting weirdly after shutting down while it was updating some apps. First, it would only function normally when on the charger (it was really erratic off it, shutting down when turning on the data/wifi).
After one day it got briefly stuck in a bootloop, and afterwards it would just display the Google logo and shutdown (or, if on charger, reaching the "Optmizing apps.." screen, and shutdown).
I attempted a "wipe cache", "Factory Reset", and flashed different stock ROMs using the Skipsoft Toolkit, all for no avail.
Is there anything else that can be done?
Click to expand...
Click to collapse
oh sorry, bump op
always first post is full-sized so I didn't see
mesaj said:
http://forum.xda-developers.com/showthread.php?t=2160124 try this, but be careful
Click to expand...
Click to collapse
Thanks, but maybe you intended to refer to this? http://forum.xda-developers.com/showthread.php?t=2099784
I'm not sure of the purpose of converting from 8G to 16G of internal storage
ftkg said:
Thanks, but maybe you intended to refer to this? http://forum.xda-developers.com/showthread.php?t=2099784
I'm not sure of the purpose of converting from 8G to 16G of internal storage
Click to expand...
Click to collapse
This is the same, I posted for N4 which is basically the same as G but G is more detailed. Try it it should format your device, helped me after similar brick issue. Btw. I used NRT instead Skipsoft.