I have a 'demo' KF2 that is currently stuck at the white and yellow Kindle Fire logo... I'm trying to use KFFirstAide to restore it to factory, then will try to root/install TWRP/install JB. I have a factory cable (which is how I was able to get it into fastboot) and the ADB drivers appear to be installed correctly.
I am seeing the following error message when doing the restore to factory:
sending 'system' (777953 KB)...
FAILED (remote: data too large)
Any ideas on how to proceed? I get a similar message trying to restore 10.2.3, the system.img is even larger on that version.
Here is the complete output from KFFirstAide:
sending 'boot' (8192 KB)...
OKAY [ 2.059s]
writing 'boot'...
OKAY [ 0.749s]
finished. total time: 2.808s
sending 'recovery' (8192 KB)...
OKAY [ 2.044s]
writing 'recovery'...
OKAY [ 0.733s]
finished. total time: 2.792s
sending 'system' (777953 KB)...
FAILED (remote: data too large)
finished. total time: 0.016s
erasing 'userdata'...
OKAY [116.502s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.016s]
erasing 'cache'...
OKAY [ 30.926s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.010s]
finished. total time: 147.454s
rebooting...
finished. total time: 0.000s
**************************************
* Success!!! The Kindle Fire 2 7" *
*Restored To Software Version 10.2.1 *
**************************************
Press any key to continue . . .
You need to obtain a "sparse" system image OR if you have adb access you can push your system.IMG to the sdcard and use the DD command to write it to your system partition
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Fixed!
I fought this all day, trying to load/reload with the KFFirstAide utility... After a while I tried to load TWRP on it and was able to boot to TWRP and wipe everything. I was then able to mount the device to Windows, copy a JB ROM to it and attempt to flash it. When the flash failed with an error (something like 'can't find tablet') I then realized I had a 1st gen Kindle, instead of what the ad stated on Ebay. Installed the correct JB and all is well... I guess 'data too large' was trying to tell me something
Not a bad deal for $31, but I really wanted 8G.
If I had to do this all over again (and knew it was a 1st gen Demo Kindle), I'd have done it this way:
Install TWRP
Wipe everything (cache, dalvik, system, sdcard)
Mount SDcard with TWRP, format with windows, copy JB and Gapps to SDcard
Install JB and Gapps
enjoy
Need sparse image
I have a mac and am having trouble mounting the system.img to create a sparse image. Is there anyone who has the sparse system.img file? I've been reading and trying to figure this out for 3 days now and any help would be appreciated.
zoey said:
I have a mac and am having trouble mounting the system.img to create a sparse image. Is there anyone who has the sparse system.img file? I've been reading and trying to figure this out for 3 days now and any help would be appreciated.
Click to expand...
Click to collapse
If you download just the batch file from here and open it as text you will find the urls under option1, i believe
http://forum.xda-developers.com/showthread.php?t=2096888
--
Sent from my Kindle Fire 2, CM 10.1
mindmajick said:
If you download just the batch file from here and open it as text you will find the urls under option1, i believe
http://forum.xda-developers.com/showthread.php?t=2096888
--
Sent from my Kindle Fire 2, CM 10.1
Click to expand...
Click to collapse
I downloaded that file and it still says its too big to flash
zoey said:
I downloaded that file and it still says its too big to flash
Click to expand...
Click to collapse
Hm... What is the exact command you are using?
--
Sent from my Kindle Fire 2, CM 10.1
KF2?
zoey said:
I downloaded that file and it still says its too big to flash
Click to expand...
Click to collapse
Are you sure you have a KF2? I had the same 'data too large' error, my tablet was NOT a KF2 (even though the seller on Ebay said it was).
I looked around a bit on Google, found some ways to tell which is which:
On an original KF, there is a 'gear' in the upper left corner you tap on for settings. On a KF2 or HD, you have to 'pull down' the top bar for settings.
On your Home screen, if the first link is Newsstand, you have a first gen KF. If the first link is shop, you have a 2nd Gen.
KF1 version is 6.x.x, KF2 version is 10.x.x
Although none of the above may help you much now that it's non-operational
Larry
Might help him and you. There are a lot more recovery options for the kf1
--
Sent from my Kindle Fire 2, CM 10.1
I know its a kinldle fire 2 it was on 10.2.6 before I started messing with it. I have another kf2 that I rooted and installed cm10.1. I've pulled the images from that and pushed them to this one. All the files worked accept the system.img. I was even able to boot back into twrp but every time I push a file to it it reboots back into recovery automatically when it is finished pushing the file and the file is gone. I know it is pushing the file because I can see it in twrp file manager as it's being pushed through. I've messed with a bunch of different devices and have always been able to bring them back when I've screwed up but this one has got me stumped.
Try to wipe cache, wipe system, I even had to wipe the sdcard and 'android secure' when I hosed my KF.... Then try to mount USB via TWRP. If windoze wants to format the KF2, I would let it do that also.
You have TWRP installed, you're 90% there... I'm sure someone here can figure this out.
Sent from my Kindle Fire that thinks it's a Nexus 7 using xda app-developers app
Yea I tried but I can't mount, wipe or format anything from twrp adb or fastboot I will keep trying though
---------- Post added at 06:41 AM ---------- Previous post was at 05:58 AM ----------
mindmajick said:
Hm... What is the exact command you are using?
--
Sent from my Kindle Fire 2, CM 10.1
Click to expand...
Click to collapse
fastboot -i 0x1949 flash system system.img I've flashed boot and recovery but system doesn't want to work for me. I have a backup of the system.IMG from cm10 and the system file from kf2 10.2.3 and one more I downloaded from here also but can't get any to work.
The only one that will work is the "sparse image" downloaded from the batch file.
You SURE you tried that one with the command above?
AND you downloaded the system.img for the kf2 and not another device (kf2 7" hd for example). Have you tried both the 10.2.3 version and the 10.2.1?
Last question- you're sure it's a kf2, not a kf1 or kfhd? What's the model number on the back of the device?
I know you tried adb... What about adb sideload in the twrp menu? It has to be a flashable zip file..
--
Sent from my Kindle Fire 2, CM 10.1
If you can't wipe via TWRP, I don't think anything else is going to work until you fix that... Can you try mounting the USB via TWRP and trying it on another computer? You won't need to install any drivers or adb stuff on the other computer.
Maybe do a factory wipe, or try installing the latest TWRP. Before doing anything drastic I would have a fast boot cable on hand (I did a factory wipe but can't recall if if cleared TWRP too).
Sent from my KF that thinks its a Nexus 7
Usb mount works on TWRP? I was under the impression it didn't work. Hence the suggestion to adb sideload the cm10.1 rom
If he can't do basic functions on TWRP... dunno. Very weird
I'm at a loss
--
Sent from my Kindle Fire 2, CM 10.1
USB works for me
mindmajick said:
Usb mount works on TWRP? I was under the impression it didn't work. Hence the suggestion to adb sideload the cm10.1 rom
If he can't do basic functions on TWRP... dunno. Very weird
I'm at a loss
Click to expand...
Click to collapse
USB mount via TWRP works for me.... I've used it with versions 2.4.1.0 and 2.4.3.0
You can only see the SDcard, I've copied ROMs to it and used TWRP to install.
I agree, if he can't do a wipe something is really messed up. I'd try the latest version of TWRP first, then try a factory wipe (as long as he has a fastboot cable just in case).
larryf said:
USB mount via TWRP works for me.... I've used it with versions 2.4.1.0 and 2.4.3.0
You can only see the SDcard, I've copied ROMs to it and used TWRP to install.
I agree, if he can't do a wipe something is really messed up. I'd try the latest version of TWRP first, then try a factory wipe (as long as he has a fastboot cable just in case).
Click to expand...
Click to collapse
Ok. Where do i get the updated versions!?!?!!
Wtf?! You have twrp no one else has?
We ONLY HAVE 2.3.3.0 HERE:
http://goo.im/devs/Hashcode/otter2/
Do you even have this device? You people are really getting me confused..
According to your post you have a kf1. Not helpful. Since the devices are different it's better not to advise others when you don't know.
--
Sent from my Kindle Fire 2, CM 10.1
mindmajick said:
The only one that will work is the "sparse image" downloaded from the batch file.
You SURE you tried that one with the command above?
AND you downloaded the system.img for the kf2 and not another device (kf2 7" hd for example). Have you tried both the 10.2.3 version and the 10.2.1?
Last question- you're sure it's a kf2, not a kf1 or kfhd? What's the model number on the back of the device?
I know you tried adb... What about adb sideload in the twrp menu? It has to be a flashable zip file..
--
Sent from my Kindle Fire 2, CM 10.1
Click to expand...
Click to collapse
So I've downloaded both the 10.2.1 and the 10.2.3 images from that link and they arent working. I don't believe either one is a "sparse image" they seem to be the same size as the other system.img files floating around xda for the kf2. I have a mac and i was thinking that might be part of my problem but that wouldn't explain why twrp isn't working. I have the latest twrp installed (2.3.3.0) and I have updated adb also. Usb mount says its working on twrp but my computer can't see it. And also adb sideload says "error closed".
The v10.2.1 and 10.2.3 are sparse images and should flash fine.
Honestly though, I haven't a clue. The only other thing I can suggest is to install Linux or windows on your Mac.
When you say you can't do anything in twrp.. What happens?
At this point I'm just fishing for information, but other than trying a different OS... I haven't any idea
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mindmajick said:
The v10.2.1 and 10.2.3 are sparse images and should flash fine.
Honestly though, I haven't a clue. The only other thing I can suggest is to install Linux or windows on your Mac.
When you say you can't do anything in twrp.. What happens?
At this point I'm just fishing for information, but other than trying a different OS... I haven't any idea
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Well i think i killed it somehow. I tried pushing backup files from my other kindle to this one and it just shut off in the middle of it and now it wont turn back on no fastboot or nothing. and it had a full charge. Sucks, I really wanted to figure this out.
When i tried to do anything in twrp it could never mount data or system or anything so everything failed.
Related
Hey Guys. I don't think the phone is bricked (I have access to Bootloader, CWM Recovery and Download Mode).
I was running Android Revolution HD ROM and out of the blue, the phone rebooted. But from this moment, it does not boot into Android. It just reboots, shows Google Logo, show the Nexus Boot Animation and then hangs for a second and reboots.
I figured it's a boot loop. So I wiped data/factory reset through CWM, wiped Dalvik Cache and flashed Revolution ROM again. Same result. I flashed Modaco iR5 and same result.
What do I do from here? Any help offered would be greatly appreciated. Thank you in advance.
RESOLVED! Thank you to afliopou, enumBoss and zyo (batch file to restore stock images - http://forum.xda-developers.com/showthread.php?t=1373995)
ragflan said:
Hey Guys. I don't think the phone is bricked (I have access to Bootloader, CWM Recovery and Download Mode).
I was running Android Revolution HD ROM and out of the blue, the phone rebooted. But from this moment, it does not boot into Android. It just reboots, shows Google Logo, show the Nexus Boot Animation and then hangs for a second and reboots.
I figured it's a boot loop. So I wiped data/factory reset through CWM, wiped Dalvik Cache and flashed Revolution ROM again. Same result. I flashed Modaco iR5 and same result.
What do I do from here? Any help offered would be greatly appreciated. Thank you in advance.
Click to expand...
Click to collapse
Maybe trying flash back to stock with fastboot following instructions here?
http://forum.xda-developers.com/showthread.php?t=1373995
Edit: and as enumBoss correctly asked which version is?LTE or GSM?
ragflan said:
Hey Guys. I don't think the phone is bricked (I have access to Bootloader, CWM Recovery and Download Mode).
I was running Android Revolution HD ROM and out of the blue, the phone rebooted. But from this moment, it does not boot into Android. It just reboots, shows Google Logo, show the Nexus Boot Animation and then hangs for a second and reboots.
I figured it's a boot loop. So I wiped data/factory reset through CWM, wiped Dalvik Cache and flashed Revolution ROM again. Same result. I flashed Modaco iR5 and same result.
What do I do from here? Any help offered would be greatly appreciated. Thank you in advance.
Click to expand...
Click to collapse
Is this an LTE or GSM device?
If it's GSM, I recommend flashing a different ROM. Probably something more stable. And do the whole thing - not just the rom, but the boot.img, etc. You can find that here: http://code.google.com/android/nexus/images.html
enumBoss said:
Is this an LTE or GSM device?
If it's GSM, I recommend flashing a different ROM. Probably something more stable. And do the whole thing - not just the rom, but the boot.img, etc. You can find that here: http://code.google.com/android/nexus/images.html
Click to expand...
Click to collapse
Hi. It's a GSM Version. I've tried flashing both Android Revolution HD and Modaco Ir5. Same Result. I can try VillainROM but I doubt that will help. (I'm doing that right now. I've just pushed VillainROM using this command: adb push VillainROM_whatever.zip to /data/media. Will try flashing that and report back).
I just tried restoring my nandroid backup and CWM restored the boot image, system and then it says 'Error While Restoring /data'.
Does that mean something is wrong with my internal storage?
ragflan said:
Hi. It's a GSM Version. I've tried flashing both Android Revolution HD and Modaco Ir5. Same Result. I can try VillainROM but I doubt that will help.
I just tried restoring my nandroid backup and CWM restored the boot image, system and then it says 'Error While Restoring /data'.
Does that mean something is wrong with my internal storage?
Click to expand...
Click to collapse
Maybe something wrong with your backup.Try to flash stock rom
afilopou said:
Maybe something wrong with your backup.Try to flash stock rom
Click to expand...
Click to collapse
I'll do that now. Oddly adb doesn't find the device when it's in bootloader mode. It finds it fine when it's in recovery mode and I'll able to push and pull stuff.
I think I'm missing fastboot drivers or something. I'll try flashing stock stuff.
I'm unable to push another ROM so I have to flash stock images. the internal storage is in read-only mode.
ragflan said:
I'll do that now. Oddly adb doesn't find the device when it's in bootloader mode. It finds it fine when it's in recovery mode and I'll able to push and pull stuff.
I think I'm missing fastboot drivers or something. I'll try flashing stock stuff.
Click to expand...
Click to collapse
This is normal.ADB not working when you are in fastboot.Did you try the thread i post you? When you are in fastboot you must first go through cmd in the folder that conatains fastboot.exe and then type in cmd "fastboot devices" .
eg cd C:/root (root is the folder that conatains fastboot)
then type "fastboot devices"
afilopou said:
This is normal.ADB not working when you are in fastboot.Did you try the thread i post you? When you are in fastboot you must first go through cmd in the folder that conatains fastboot.exe and then type in cmd "fastboot devices" .
eg cd C:/root (root is the folder that conatains fastboot)
then type "fastboot devices"
Click to expand...
Click to collapse
Yeap. I read the thread you posted. Downloaded the zip file and extracted it. After which I rebooted into bootloader mode and ran the batch file from the extracted directory.
It flashed the stock images in bootloader mode and rebooted twice and I'm booted into Android now. Thank you very much, kind sir.
For my reference (and to learn), what could have gone wrong? The ROM was up and running fine and I titanium restored only user apps and didn't touch system apps at all. Everything was fine and a random reboot caused the phone not to boot into Android anymore. I've had 3 other Android devices before the Nexus (Galaxy S, SII and G1) and never had such an issue.
ragflan said:
Yeap. I read the thread you posted. Downloaded the zip file and extracted it. After which I booted into bootloader mode and ran the batch file.
I'm booted into Android now. Thank you very much.
For my reference (and to learn), what could have gone wrong? The ROM was up and running fine and I titanium restored only user apps and didn't touch system apps at all. Everything was fine and a random reboot caused the phone not to boot into Android anymore.
Click to expand...
Click to collapse
Who knows? Only the android god
afilopou said:
Who knows? Only the android god
Click to expand...
Click to collapse
Haha amen to that. With Galaxy S and SII, I just used ODIN to flash a firmware. With Nexus, I just have to use that post. Thanks again!
Did you flash a new kernel? If so, that could be (part of) the issue
EddyOS said:
Did you flash a new kernel? If so, that could be (part of) the issue
Click to expand...
Click to collapse
Nope. Well, it was part of the ROM (Modaco and Android Revolution HD). I didn't flash it separately.
EddyOS said:
Did you flash a new kernel? If so, that could be (part of) the issue
Click to expand...
Click to collapse
I've just experienced the exact same thing..
And the ONLY thing I've done today was install NFC Taginfo.
I noticed apps starting to crap out and figured I'd done something wrong and restarted.. got stuck in a boot loop..
went into CWM to restore an old back up and it failed with 'Error while restoring /data' (I'd gotten 'Error while backing up /data' when trying to back it up).
wiped everything (twice).. formatted everything (twice).. tried to restore and still no go.. interesting that it didn't seem to have any issue when formatting /data.
Am only running rooted stock (not even any MODs) so find this all rather peculiar.
Will try and push the stock ROM this evening when I get home.
EDIT: Used the method listed above to flash the original stock image which worked... although it did erase everything on my phone (kinda wish I'd known that before but what can you do). Would really like to know how I went from a seemingly normal phone to a not very useful paperweight!? Thankfully it's resolved.
I'm having the same issue. However, I can't flash stock, as my baseband is different. Can someone please advise? Here is my fastboot flash attempt. Thanks.
C:\itl41f>flash-windows.bat
C:\itl41f>fastboot-windows flash bootloader bootloader-maguro-primekj10.img
sending 'bootloader' (2308 KB)... OKAY
writing 'bootloader'... OKAY
C:\itl41f>fastboot-windows reboot-bootloader
rebooting into bootloader... OKAY
C:\itl41f>fastboot-windows flash radio radio-maguro-i9250xxkk1.img
sending 'radio' (12288 KB)... FAILED (command write failed (Too many links))
C:\itl41f>fastboot-windows reboot-bootloader
rebooting into bootloader... FAILED (command write failed (No such file or direc
tory))
C:\itl41f>fastboot-windows -w update image-yakju-itl41f.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
< waiting for device >
--------------------------------------------
Bootloader Version...: PRIMEKJ10
Baseband Version.....: I9250UGKK7
Serial Number........: 0146914C0C019006
--------------------------------------------
checking product... OKAY
checking version-bootloader... OKAY
checking version-baseband... FAILED
Device version-baseband is 'I9250UGKK7'.
Update requires 'I9250XXKK1'.
C:\itl41f>
Click to expand...
Click to collapse
Fairly noobed to android so need a little help (teething) haha,
I've tried to install a custom rom for my one x unlocked boot loader and installed clockwork mod touch recovery, downloaded android revolution hd and moved wipe script and android revolution zip to sd card, flashed the boot.img and run wipe script no problem.
But when I go to install the zip file I get greeted with
finding update package>opening update package>installing update>installation aborted... then nothing. If I reboot the phone the phone stays in the htc quietly brilliant screen.
Please anyone! Help a fella out, crack this and I'll be forever in everyone debt. Thanks.
Con
ConorL said:
Fairly noobed to android so need a little help (teething) haha,
I've tried to install a custom rom for my one x unlocked boot loader and installed clockwork mod touch recovery, downloaded android revolution hd and moved wipe script and android revolution zip to sd card, flashed the boot.img and run wipe script no problem.
But when I go to install the zip file I get greeted with
finding update package>opening update package>installing update>installation aborted... then nothing. If I reboot the phone the phone stays in the htc quietly brilliant screen.
Please anyone! Help a fella out, crack this and I'll be forever in everyone debt. Thanks.
Con
Click to expand...
Click to collapse
Try to disable the signature check and see if you're able to install it.
Your Rom zip files is corrupted. You have to verify md5 value and then you have to flash.
Goto fastboot and just flash the stock kernel.
Sent from my HTC One X using Tapatalk 2
Tried disabling the signature check with no luck same thing happens..Do you know where could I get the stock kernel from? Thanks again for your patience it is greatly appreciated!
When i try to Flash the stock rom i get this message
sending 'flash' (9792 KB)... OKAY
writing 'flash'... FAILED (remote: not allowed)
xx-xxx-xx-22:bootloader connor$
anyone know what I'm doing wrong?? Thanks..
ConorL said:
When i try to Flash the stock rom i get this message
sending 'flash' (9792 KB)... OKAY
writing 'flash'... FAILED (remote: not allowed)
xx-xxx-xx-22:bootloader connor$
anyone know what I'm doing wrong?? Thanks..
Click to expand...
Click to collapse
Use the automated batch file in ARHD Thread. Like he said it might be a bad download. Re-downloaded it and test it again.
Tried downloading the stock kernel again and same story... How do I use the automated batch file you mentioned? thanks..
Are you trying to flash a .zip in fastboot? What file have you renamed 'flash'?
I haven't renamed any files flash I've just been trying to flash the .zip file...Its been a major fail so far, thanks for everyone patience..
ConorL said:
I haven't renamed any files flash I've just been trying to flash the .zip file...Its been a major fail so far, thanks for everyone patience..
Click to expand...
Click to collapse
Re-download the file to PC
Send file to sdcard
Remove usb cable from HOX
Try again
Hope it helps
I can't get back into the os to move the files over to the sd card, every time i reboot I get the htc quietly brilliant screen...
after i download the file should i rename anything to get it to flash properly from fastboot? I can't get back into the os so i'm in bootloader trying to fix it..Cheers
Go to Bootloader select Fastboot
Download http://www.androidrevolution.nl/downloader/download.php?file=Flash_boot_6.0.0.rar and extract it. Then run the batch file.
Then go into Recovery and your SD card will be automatically mounted to your PC in Recovery mode
So copy the ROM and flash it again.
Make sure you don't select any custom settings on the first boot.
It still looks like your trying to flash a .zip in fastboot.
---------- Post added at 01:05 PM ---------- Previous post was at 01:02 PM ----------
ConorL said:
When i try to Flash the stock rom i get this message
sending 'flash' (9792 KB)... OKAY
writing 'flash'... FAILED (remote: not allowed)
xx-xxx-xx-22:bootloader connor$
anyone know what I'm doing wrong?? Thanks..
Click to expand...
Click to collapse
This. ^^^
Sending 'flash'.
What command did you write to get this error. And what was the filename and extension. It would really help to know what you tried to flash.
I had the same issue on Wednesday where I ran the wipe script then tried to flash the rom and it turned out to be a corrupt download (failed to follow instructions to my peril).
To resolve all that was needed was to re-download the rom, mount the sdcard and copy it over and reattempt the flash. In my case I couldn't mount the sdcard at first, so if you are having issues here I solved it by updating recovery as per this thread "[RECOVERY] TeamWin Recovery Project (twrp) 2.1.7 [2012-06-04]"
under the "One X Android Development section"
To send files to your sd with no os, either install the new recovery that has usb support or use
Fastboot boot name.IMG (this is recovery IMG)
While booting from fastboot like that it allows adb to be used then Just push
adb push Rom.zip /sdcard
That will push the Rom to sd then just install as normal.
You will need the adb files easy enough to find on google.
Sent from my HTC One X using xda premium
i made a compilation thread about this, have a check... might help you out..
http://forum.xda-developers.com/showthread.php?t=1692681
Hi,
First of, I'm sorry if I overlooked a similar thread on XDA, but I'm really in a state of panic.
I bricked my HTC One X today, while I was trying to upgrade to CM 10.1. Please note I am a total noob here, so please don't rage at my stupid mistakes. I'll try to summarize what I did before my phone stopped working.
1. I rooted my phone via this method http://onexroot.com/one-x-root/how-to-root-one-x/
2. I tried installing cm 10.1 via this method http://forum.xda-developers.com/showthread.php?t=1786696&highlight=boot
3. Since I didnt get step 7 in that guide (about flashing boot), and because a bit further he says "boot.img included in the installer zip.", I thought I'd just skip it (I know, really stupid)
4. Obviously it didn't work, restored to where I was before step 2 (tested if I could start my phone, it worked), extracted the boot.img in the pack, and used a command prompt via pc to flash it. It said this
C:\Users\Lukas\Downloads\OneXRoot>fastboot flash boot boot.img
sending 'boot' (4958 KB)...
OKAY [ 0.681s]
writing 'boot'...
(bootloader) Format partition LNX done
OKAY [ 0.507s]
finished. total time: 1.188s
I just put the boot.img in the OneXRoot folder, so I didn't have to rewrite the command.
5. Again, it didn't work. Restored again to same point as before, but now my phone gets stuck on the HTC screen.
I'd like to add that at this moment I haven't found out how to get in the internal storage of my phone, so I can't even download the stock rom, and work from there.
Again, I'm a big noob, this is about the max of my rooting/flashing-skills, so guide me as slowly as possible.
Please help!
Lukas
Oke.....
Go into the recovery and mount the sdcard as a mass storage device. Then you have acces to the sdcard.
What would you like to do in the first place now ? Het CM10.1 or stock ?
If you did a nandroid backup of the stock rom you do this
Mount the sdcard in the recovery
Copy the boot.img from the nandroid backup and flash it in the bootloader with the toolkit or manual commands
Then enter the recovery and perform a full wipe, then you restore the nandroid backup
Okè. You can access internal storage within recovery. Select mounts and storage > plug in usb cable > mount usb storage.
For booting the ROM, there's one thing you missed. Due to DMCA takedown the vendor blobs are missing from builds and that's why they don't boot.
You need to take a look at the cyanogenmod thread in original development and in the first post you can find a link for the vendor installer zip that you need.
Just flash it in recovery after flashing the rom.zip.
Sent from my One X using xda premium
Edit: what an epic ninja you are Hofs... Even started the post with the same word.
TToivanen said:
Okè. You can access internal storage within recovery. Select mounts and storage > plug in usb cable > mount usb storage.
Click to expand...
Click to collapse
When I do this it says: E: Unable to open ums lunfile (No such file or directory)
Your CWM is outdated. DL this: http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-5.8.4.0-endeavoru.img
Rename it recovery.img and flash like this: fastboot flash recovery recovery.img
Man you two are like everywhere...you guys beat me always when i try and help someone out..well done you guys
Goku80 said:
Man you two are like everywhere...you guys beat me always when i try and help someone out..well done you guys
Click to expand...
Click to collapse
Yeah we secretly divide posts in gtalk so we don't get into a fight LOL ......
But its my night off so i have a lot of time. Busy weekend ahead of me .....
Goku80 said:
Man you two are like everywhere...you guys beat me always when i try and help someone out..well done you guys
Click to expand...
Click to collapse
Too much free time that's all haha (i joke) I used to be the same till college got in the way
Sent from my HTC One X using xda app-developers app
Re
It flashed the recovery like you said, and it gives me a new menu (Unmount or Go Back) but it still doesnt work properly. I restarted both my pc and my phone to make sure..
Can you help me any further?
You tap mount as mass storage device once ....then it should pop up in windows
Otherwise you can try this recovery
http://db.tt/iXT4t3NH
RE
Doesn't find it with that one either... Starting to think I messed this one up reaaaalll bad.
Maybe something with my pc settings?
Strange ..... sure you connected the usb cable ......try another port
One of these 2 recoverys must work ...... don't see why not
I wish I were that stupid But no, tried all my ports, doesn't connect. It does make the sound however, so I know it's not that.. In the mean time, I got a single step closer. I downloaded the most recent boot img, and flashed it.
It still doesn't start, but now it doesn't stop at the HTC screen, but the HTC One X screen.. Progress, I guess
Edit: Tried my roommates pc, it catches!!! I'll keep you posted on my progress, but for now, thank you so very much!
Try to push the file you need with adb.
adb push (pathofsourcefile) /sdcard/
For example
adb push C:\files\derp.zip /sdcard/
Sent from my One X using xda premium
Hmm you got a nandroid backup on the sdcard right ? You made that one with cwm ? Flash back cwm 5.8.4.0 now.....what nandroid was it ? stock jb rom ? Give me that info and i will provide a new stock boot.img file ! You can flash that one and restore the nandroid backup....but i need the info asap
FIXED
Guys, thank you so very much!
It is now fixed, although I still don't have cm10.1, I can at least use my phone again. For the people who want to know what I did:
1. Apparently, my pc can't identify the 'mount usb' from CWM, so I had to go to another pc.
2. I searched and found the boot.img that I used in my backup
3. Flashed that img.
And now it's fixed!
Again, thanks very much, it seems these things can make grown men cry...
So it was the pc ! ..... :thumbup:
---------- Post added at 10:24 PM ---------- Previous post was at 10:22 PM ----------
If you want cm10.1 you need the rom.zip, gapps.zip and the vendors file too
Make a full wipe in the recovery and install the rom, gapps, vendors ...don't reboot
Reboot to the bootloader
Adb reboot bootloader
And flash the boot.img from cm10.1
RE
Allright, I will do that, have the files on my phone now. But not until tomorow, I really have to rest from this 4 hour panic-attack
Fair ! And charge the phone to 100% before you start .... may save you from trouble if it doesn't work for some reason. Then you always have plenty battery to restore a nand
So I've been stuck in this situation for about 2 weeks now and have searched XDA extensively so I'm fairly confident this issue hasn't been addressed elsewhere. If it has, I apologize.
So I had rooted my 2013 Nexus 7 shortly after buying it back in August and I had been running a custom ROM (CleanROM I believe). A few weeks ago the OTA update notification appeared in my notification panel and I just kept ignoring it because I didn't have time to flash a new ROM. I think after a few days the OTA Update simply went through without me clicking on it. Since then my device will not boot past the Google logo with the unlock icon below it.
I can boot into the Bootloader and Recovery and both are recognized by adb and fastboot mode in terminal (I use a mac) but if I try to flash anything neither are able to write to any partitions. Using recovery on the device it gives me the error... "Unable to mount system" "Unable to mount boot" "Unable to mount data" if I try to flash anything. I am also getting the "Storage: Internal Storage (0 MB)" message when I just simply try to mount anything in TWRP.
One of the many tutorials I've read has suggested formatting data in TWRP and that then I should be able to write again. Well I've done that multiple times and I still cannot write from recovery or remotely through fastboot.
I am out of ideas and would be open to any suggestions other users have to offer.
Here is the error I'm getting in TWRP when I try to format all data
Updating partition details...
E:Unable to mount '/system'
E:Unable to mount '/data'
E:Unable to mount '/cache'
E:Unable to mount internal storage.
Here is the error message I get when trying to flash a factory image through fastboot
Andrews-iMac:razor-jss15q $ ./fastboot update image-razor-jss15q.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: FLO-03.14
Baseband Version.....: none
Serial Number........: XXXXXX [My serial does show up here, I've just deleted it]
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.004s]
sending 'boot' (6880 KB)...
OKAY [ 0.241s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 90.057s
Andrews-iMac:razor-jss15q andrew$
I get similar (flash write failure) errors when I try to flash individual components separately.
Anyone got any ideas what's going on? I'm afraid the actual memory in my device may be totally borked.
Are you running fastboot with elevated privileges? On unix that would be root which I assume is similar on mac.
The other thing that might have happened is the partitioning got messed up.
sfhub said:
Are you running fastboot with elevated privileges? On unix that would be root which I assume is similar on mac.
The other thing that might have happened is the partitioning got messed up.
Click to expand...
Click to collapse
I've used the adb root command and gotten the response that I'm already running in root mode.
I think you may be right about the partitioning having gotten messed up. Any idea on how to remedy that?
drgonzophd said:
Andrews-iMac:razor-jss15q $ ./fastboot update image-razor-jss15q.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: FLO-03.14
Baseband Version.....: none
Serial Number........: XXXXXX [My serial does show up here, I've just deleted it]
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.004s]
sending 'boot' (6880 KB)...
OKAY [ 0.241s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 90.057s
Andrews-iMac:razor-jss15q andrew$
I get similar (flash write failure) errors when I try to flash individual components separately.
Anyone got any ideas what's going on? I'm afraid the actual memory in my device may be totally borked.
Click to expand...
Click to collapse
I hate to be the bearer of bad news, but to me I believe your internal SD might have gone bad. Try to fastboot flash the stock recovery and do a factory reset with that, but I really have my doubts. I guess just try to get it replaced from ASUS...
fosser2 said:
I hate to be the bearer of bad news, but to me I believe your internal SD might have gone bad. Try to fastboot flash the stock recovery and do a factory reset with that, but I really have my doubts. I guess just try to get it replaced from ASUS...
Click to expand...
Click to collapse
Problem is I can't even re-lock it or flash the factory recovery back onto it. I'm pretty sure that voids any warranty with ASUS.
Could this help?
http://forum.xda-developers.com/showthread.php?t=2381582
Sent from my MIZ Z1 using Tapatalk 4
BradleyW said:
Could this help?
http://forum.xda-developers.com/showthread.php?t=2381582
Sent from my MIZ Z1 using Tapatalk 4
Click to expand...
Click to collapse
Already tried that, a different OSX Toolkit and also applying the terminal commands manually with the specific files included in those tool kits. I keep getting the same 'Unable to write' errors when attempting to flash anything.
I'm afraid I may have an actually bricked device. This is my third android device, I started with the original Moto Droid on launch day and have rooted all three devices and never had an issue.
Anybody know if there is a place to sell bricked devices for parts or for developer use?
drgonzophd said:
Already tried that, a different OSX Toolkit and also applying the terminal commands manually with the specific files included in those tool kits. I keep getting the same 'Unable to write' errors when attempting to flash anything.
I'm afraid I may have an actually bricked device. This is my third android device, I started with the original Moto Droid on launch day and have rooted all three devices and never had an issue.
Anybody know if there is a place to sell bricked devices for parts or for developer use?
Click to expand...
Click to collapse
I wouldn't give up, keep trying!
Sent from my Nexus 7 using Tapatalk 4
drgonzophd said:
Already tried that, a different OSX Toolkit and also applying the terminal commands manually with the specific files included in those tool kits. I keep getting the same 'Unable to write' errors when attempting to flash anything.
I'm afraid I may have an actually bricked device. This is my third android device, I started with the original Moto Droid on launch day and have rooted all three devices and never had an issue.
Anybody know if there is a place to sell bricked devices for parts or for developer use?
Click to expand...
Click to collapse
Hi just wondering if you ended up having this resolved? I have the exact same problem with my Nexus 5. Did you send it back with the unlocked boot loader? If so was it accepted under warranty?
Cheers
Same problem with a Nexus 7 2013 (flo, using omni rom) :crying: but it happened randomly, i was using it normally, rebooted without a reason, take a little bit longer than expected to boot... 10min later another reboot, and then the same thing that happened to you
You ended up selling it for parts/repair or sending it to rma?
someone knows if this can be fixed with jtag?
Had this problem also
I had this problem also. I ended up sending it to Asus for warranty work. They replaced the main board and memory. It is working fine so far. There are other threads with similar issues. I wonder maybe a bad update or a bad hardware batch.
I had the same thing happen with my Nexus 7 2013, I RMA it, and the paperwork said it was a CPU error. I couldn't flash or sideload anything whatsoever. Your chip set could have failed.
Sent from my LG-G2 using xda app-developers app
I have the same problem with my Nexus 7 (2013). I understand that it cannot be fixed in home so I have to send the tablet to its warranty service. But I have unlocked the bootloader and rooted the tablet. I believe they wont fix it and will deny the warranty. So I think I need to pay the cost
Anyone can help with info?
Wow..This just happened to me tonight on the way home on the train.. At least I know I'm not alone. Same situation as far as being unlocked and unable to relock. I guess I'll call RMA on mine too.. Go figure.
I managed to relock the bootloader, with the usual method to do so (fastboot oem lock)...
My problem with rma now is that i bought it used from ebay, i don't know if that would be a problem (because i don't know where it was bought or the date of purchase)... earlier i register it on the asus web site with the date that i bought it from ebay, i hope it works
Also i contacted a guy that have a jtag, but apparently this device isn't supported yet
vite0150 said:
I managed to relock the bootloader, with the usual method to do so (fastboot oem lock)...
My problem with rma now is that i bought it used from ebay, i don't know if that would be a problem (because i don't know where it was bought or the date of purchase)... earlier i register it on the asus web site with the date that i bought it from ebay, i hope it works
Also i contacted a guy that have a jtag, but apparently this device isn't supported yet
Click to expand...
Click to collapse
In six months you may have issues, because the warranty will certainly be based on the original purchase date. That's if the previous person did register it, though, and for now the device is definitely in warranty.
I have another problem, i don't know if the serial number that i used to register the product was the one of my device, cause the ebay seller had a bunch of these tablets and maybe i got the wrong box...
in fastboot i see a serial number but it is just 8 digits, the ssn on the box is 12 digits... :s
I think I killed my flash memory too...
My internal storage has been nearly full for a while now and I haven't got around to cleaning up shop. Tonight I automatically clicked on an update all apps button in the play store and stopped paying attention. During the process the tablet shut off and will not boot into anything except fastboot mode.
I'm pretty sure the internal storage is full. I get write errors for everything that tries to flash or factory reset or write to the device.
At certain points my repair process freezes on stages such as "erasing cache" or "erasing system". It just freezes. I may be wrong but it shouldn't take more than ten minutes to delete the cache through adb? I'm going to do some more research. for the moment I locked the bootloader just in case...
Can anyone give some insight?
Same symptoms as mine (btw, mine was nearly full of movies when it happens and was on 4.4.2)
You should try to relock the bootloader, erase the custom recovery (I erase the whole partition) and ask for a rma ticket
Btw, the rma was super fast, in 3days it got fixed
vite0150 said:
erase the custom recovery
Click to expand...
Click to collapse
please give me some advice about how to do this? My head is spinning with all the different routes I've taken, now that the bootloader's locked I'm not sure how to do anything haha. For clarity the tablet won't get past the white "google" logo so I can't enable USB debugging or things like that
So I have no OS on my Nexus 7, nor can I flash one. All conventional methods of installing an operating system on to this POS have met with utter failure.
Brief histroy:
-Had CM 11 nightly build until it "imploded" (any shortcut would take me to a PIN screen, users deleted profiles deleted themselves, random reboot every 5 minutes) and stopped functioning.
-Decided to return to an earlier of CM, so I dl'd an earlier version and pushed the .zip to CWM recovery. Big mistake. CWM decided to repartition everything in an erroneous manner rather than just wipe Dalvik cache.
-Now CWM will not open any .zip pushed through ADB. Just a generic "failed to open file" message.
-Sheer desperation and four hours of driver Hell finds me in fastboot and trying to flash a stock image.
-Latest Android system image will not flash. Period. Using the flashall.bat script, the error about a missing system.img pops up. I am staring at system.img right next to the .bat.
-Download Android L preview and run flashall.bat, operating system installs after about 30 minutes and numerous errors that the script "seemed" to fix about missing partitions.
-Reflash TWRP
-Android L gets stuck in non-bootable state (spinning colored ball logo thing) after a random restart.
-Now TWRP cannot find any .zip that I manually push through ADB. I can see it in File Manager, but nowhere else. Flashing custom ROM at this point not possible.
-Return to Android KitKat stock image and manually flash system.img through fastboot. Tablet will not boot, goes directly to black screen after bootloader.
So WTF do I do at this point? I have just about had it with all things Android right now. CWM doesn't work. TWRP doesn't work. Stock images don't work. Fastboot doesn't work. What else is there?
Cortimi said:
So I have no OS on my Nexus 7, nor can I flash one. All conventional methods of installing an operating system on to this POS have met with utter failure.
Brief histroy:
-Had CM 11 nightly build until it "imploded" (any shortcut would take me to a PIN screen, users deleted profiles deleted themselves, random reboot every 5 minutes) and stopped functioning.
-Decided to return to an earlier of CM, so I dl'd an earlier version and pushed the .zip to CWM recovery. Big mistake. CWM decided to repartition everything in an erroneous manner rather than just wipe Dalvik cache.
-Now CWM will not open any .zip pushed through ADB. Just a generic "failed to open file" message.
-Sheer desperation and four hours of driver Hell finds me in fastboot and trying to flash a stock image.
-Latest Android system image will not flash. Period. Using the flashall.bat script, the error about a missing system.img pops up. I am staring at system.img right next to the .bat.
-Download Android L preview and run flashall.bat, operating system installs after about 30 minutes and numerous errors that the script "seemed" to fix about missing partitions.
-Reflash TWRP
-Android L gets stuck in non-bootable state (spinning colored ball logo thing) after a random restart.
-Now TWRP cannot find any .zip that I manually push through ADB. I can see it in File Manager, but nowhere else. Flashing custom ROM at this point not possible.
-Return to Android KitKat stock image and manually flash system.img through fastboot. Tablet will not boot, goes directly to black screen after bootloader.
So WTF do I do at this point? I have just about had it with all things Android right now. CWM doesn't work. TWRP doesn't work. Stock images don't work. Fastboot doesn't work. What else is there?
Click to expand...
Click to collapse
Is this an LTE or WiFi model? Do you have the nexus root tool kit installed on your computer and able to get to fastboot?
someolddude said:
Is this an LTE or WiFi model? Do you have the nexus root tool kit installed on your computer and able to get to fastboot?
Click to expand...
Click to collapse
WiFi model, fastboot and adb are fine, no toolkits.
Cortimi said:
WiFi model, fastboot and adb are fine, no toolkits.
Click to expand...
Click to collapse
Get the toolkit by wugfresh and you should be able to restore it.
someolddude said:
Get the toolkit by wugfresh and you should be able to restore it.
Click to expand...
Click to collapse
Nope. Using the Flash Stock + Unroot option gives the exact same error as doing it manually.
Flash Stock + Unroot...
------------------------------------------------------------------
sending 'bootloader' (3911 KB)...
OKAY [ 0.129s]
writing 'bootloader'...
OKAY [ 1.283s]
finished. total time: 1.412s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 754455404 bytes
error: update package missing system.img
Booting up your freshly flashed stock device...
------------------------------------------------------------------
Wait for your device to finish booting up...
- It may appear to be boot looping; just wait...
- It could take 5-10 minutes; please be patient...
When its finally booted back up, please remember
to re-enable USB debugging if you plan on using
the toolkit to perform other operations.
NOTE: If this process was too quick and your device
is still in bootloader mode, then flashing stock may
have failed or been incomplete. Simply check the
log above: if you notice it skipped steps because it
didn't meet certain requirements, like the bootloader
or baseband version, then consider enabling 'Force Flash'
mode in the toolkits options menu and trying the
'Flash Stock + Unroot' processs again. Cheers.
Press any key to exit...
Click to expand...
Click to collapse
Attempting to flash CWM recovery (found here: http://forum.xda-developers.com/showthread.php?t=2583845) results in a stuck bootloader screen. I was able to re-flash TWRP, but it is still useless as it simply does not function in any useful manner whatsoever.
Cortimi said:
Nope. Using the Flash Stock + Unroot option gives the exact same error as doing it manually.
Attempting to flash CWM recovery (found here: http://forum.xda-developers.com/showthread.php?t=2583845) results in a stuck bootloader screen. I was able to re-flash TWRP, but it is still useless as it simply does not function in any useful manner whatsoever.
Click to expand...
Click to collapse
Same problem with mine, cm11 as well.
I like some of the CM features but ever device Ive flashed and had trouble with it has been when Ive went with "Cyanide Mod"
You figure something out, please let me know and I will do the same.
I've got the LTE but my daughter has the WiFi only and is also unlocked. I can make a bone stock backup of here's which is on 4.4.4 if you want to try and restore it to yours.