Please help, I've searched and searched and couldn't find anything to help me. I flashed CyanogenMod-6-19Oct2010-EXTBLUE on my sprint hero and didn't like it. I then tried to flash back to Fresh 2.3.3 and kept getting error code can't symlink/system/xbin/zcip Failure at Line 62:symlink busybox SYSTEM:xbin/zcip. I also tried several other roms with the same result. Now the only thing that will flash is CyanogenMod-6. Thank you and if I overlooked a fix for this I'm sorry, I looked all night long and couldn't find anything.
Did you try wiping before flashing back?
Also, wrong forum. Q/A would be better.
I did, wiped everything, can't restore nandroid backup either. Using recovery image 1.6.2. Sorry about posting in wrong forum.
Sent from my HERO200 using XDA App
try the command ‘fastboot erase system' will wipe the entire system partition from adb as g ****s dont like to wipe correctly
Thanks for the info, I tried but with no luck in fastboot. Kept getting error, erasing 'system' ...FAILED<remote: not allow> finished. total time: 0.000s
jbroyles_23 said:
Thanks for the info, I tried but with no luck in fastboot. Kept getting error, erasing 'system' ...FAILED<remote: not allow> finished. total time: 0.000s
Click to expand...
Click to collapse
try this first "fastboot oem unlock"
jbroyles_23 said:
Thanks for the info, I tried but with no luck in fastboot. Kept getting error, erasing 'system' ...FAILED<remote: not allow> finished. total time: 0.000s
Click to expand...
Click to collapse
I had the same problem on my wifes phone. I had to flash the file from this link.
http://forum.xda-developers.com/showthread.php?t=765237
After flashing that restarting and it loading. I then went into fastboot and tried again and it worked like a charm (meaning fastboot commands.)
I got the same error code once. I was trying the firerat mtd partition. It didn't work, would not boot. So I went into boot loader and switched to fastboot. It ran some commands so fast I couldn't see them. After that I couldn't boot nothing but cm6. Everything other rom would come up with that same exact code. But on cm6 I couldn't set cpu, use rom manager, or even terminal. After bout 8 hours of researching aggressively, I abd 'd to check to see if I still had root, I did not. I had to flash the ruu for fastboot. So, what I'm trying to get at is, check to see if you still if you have root. Because, I got that same exact code.
Wow... Glad I didn't flash that one :X
But seriously..
Did you try flashing clockwork mod and using that? That's the only other thing I could suggest but tbh what everyone else has said pretty much has to work unless it had something to do with something that altered recovery... Either that or like nfinitefx gave you should have wiped everything that wasn't there.
I appreciate everyone's help. I think I finally figured out where my problem was, I was trying Firerat's Custom MTD Partitions and after looking through my sdcard, the mtdpartmap.txt file that I had made, like an idiot, I named it mtdpartmap.txt so when it saved, it saved as mtdpartmap.txt.txt. Wish I would have caught it sooner because I reverted back to the .5 stock update and rerooted, but I think all is good now.
Related
I've found only one instance of this so far in the development forum by user malickie but they seem to have just returned the phone and I don't believe it's unfixable.
It all started by my trying to update while retaining root without flashing a stock 2.3.5. I tried the "three lines of code method", editing from within the phone using either FX or ES explorer (one initially wouldn't paste back into /system/bin after I made a backup on the sd card).
When I tried to update it got as far as the recovery image, the android with the folder and arrow, and eventually crashed telling me I had invalid this and that; CDROM, SYSTEM, WEBTOP. Sorry, I don't remember the specifics. I shut it down and it bootlooped as far as the AT&T logo droplet thing.
I launched into forum scrounging mode, got RSD Lite 5.6, the FXZ, the update.zip, and flashed back to 2.3.5. The first time I shut down after this it bootlooped again. So I flashed it again, so far so good, so I figured I'd go ahead and update to 2.3.6. More bad luck as it tells me "insufficient memory please factory reset". I try this, and it goes into fastboot telling me "Invalid CG (cg: recovery)".
So, I've been scrounging all day trying to figure out if this issue has been solved to no avail Does anyone have any suggestions?
ri4naire said:
I've found only one instance of this so far in the development forum by user malickie but they seem to have just returned the phone and I don't believe it's unfixable.
It all started by my trying to update while retaining root without flashing a stock 2.3.5. I tried the "three lines of code method", editing from within the phone using either FX or ES explorer (one initially wouldn't paste back into /system/bin after I made a backup on the sd card).
When I tried to update it got as far as the recovery image, the android with the folder and arrow, and eventually crashed telling me I had invalid this and that; CDROM, SYSTEM, WEBTOP. Sorry, I don't remember the specifics. I shut it down and it bootlooped as far as the AT&T logo droplet thing.
I launched into forum scrounging mode, got RSD Lite 5.6, the FXZ, the update.zip, and flashed back to 2.3.5. The first time I shut down after this it bootlooped again. So I flashed it again, so far so good, so I figured I'd go ahead and update to 2.3.6. More bad luck as it tells me "insufficient memory please factory reset". I try this, and it goes into fastboot telling me "Invalid CG (cg: recovery)".
So, I've been scrounging all day trying to figure out if this issue has been solved to no avail Does anyone have any suggestions?
Click to expand...
Click to collapse
I hate to say it, but it sounds like you might have a bad phone.
But you can try using the beginner thread and use the directions there to flash the fxz, but try unzipping the fxz and then go into RSD lite and click on the "..." button, and then select the xml file and start flashing.
If that does not work, there is another way, but you have to be VERY careful, because this can hard-brick your phone.
Last ditch, but ONLY if the others don't work, do this:
Make sure your have the android sdk installed:
http://developer.android.com/sdk/index.html
Then go grab this, and put in the same directory as the SDK installed to, under platform-tools:
http://forum.xda-developers.com/attachment.php?attachmentid=890596
Then open a command line in the directory that you saved and unzipped the fxz in, then;
put your phone in fastboot mode, connect the USB cable, and:
Code:
[FONT=monospace]
[/FONT]fastboot erase userdata
fastboot erase cache
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash preinstall preinstall.img
fastboot reboot
No guarantees this will work
The first two work fine, returning "OKAY". However, if I try any type of flashing from the cmd prompt I get a "FAILED".
Code:
C:\*\InlineFlashing_etc>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.355s]
finished. total time: 0.356s
C:***>fastboot erase cache
erasing 'cache'...
OKAY [ 0.017s]
finished. total time: 0.020s
C:***>fastboot flash system system.img
sending 'system' (491264 KB)...
OKAY [ 17.982s]
writing 'system'...
(bootloader) Preflash validation failure
FAILED (remote: )
finished. total time: 18.212s
I realize we have a locked bootloader so is there a step I might have missed? I flashed back the updated fxz (that's now 18 steps instead of 20, and PS. this renders me with a functional phone, just not one that can update) and luckily I can seem to get back to at least this state consistently.
Ok, so I tried rooting in this state and used the ADB method from the Beginners' Guide to attempt to retain root through the update. This time there was nothing about insufficient memory, it just downloaded the update and then tried to reboot for the install but instead of going to unzip the package it goes straight back to fastboot flash mode with another failure.
Code:
AP Fastboot Flash Mode (S) (Flash Failure)
0A.65
Battery OK
OK to Program
Connect USB
Data Cable
On the bright side it's not taunting me with invalid partitions but then again it won't boot normally either. I'm stuck on this screen.
Try pulling the battery and then booting into boot selection mode. (Press+hold volume buttons, then power button) and select "normal boot".
If that doesn't work then flash the fxz... again.
Did you do manual or one-click root?
Sent from my MB865 using Tapatalk
Ok, I had to plug it in overnight, making sure not to press the power button because it would go into "AP Fastboot", because my battery ran low. I'm flashing the updated FXZ again right now.
I've only ever done the One-Click Root. The first time I tried to retain root, what started all this, was using only the phone. This last time I used the ADB method and it didn't demand I factory reset.
Interestingly, when I tried that factory reset that's when it told me my recovery image wasn't good. I've noticed that the FXZ doesn't flash recovery.img but it does flash system, boot, and preinstall. So, is it possible I could manipulate that file to perform the steps you, Jim, suggested? I should just need to create an MD5 sum and follow the template of the rest of the time, right?
Hi Xda members,
I've been running Jelly Beans stock OTA (rooted though) since it was released here, and have been working out great so far.
A couple of days ago I got a number of strange notification pop-ups in just a few seconds while I was watching the screen...
The messages read something like "some app is requesting to run as super user" (well, don't remember which app or the exact message). Anyway, as I hadn't start any app at this point I thought it was a bit strange when several of these message popped up.
So I rebooted the mobile to see if it would make the pop-ups stop, but after this the mobile didn't boot up again, it just locked at the first boot screen (showing the Google text and the "Unlocked" symbol)...
I can still boot into the bootloader and the recovery. And I can reprogram the bootloader and the recovery partition through fastboot, but when trying to write to the boot partition through fastboot I get this output:
Code:
fastboot flash boot ./boot.img
sending 'boot' (8192 KB)... OKAY
writing 'boot'... FAILED (remote: Write Fail)
And in the recovery when I try to "choose zip from sdcard" I get "E: Can't mount /sdcard/".
Do you think the internal flash memory might be broken or could it be the partition table, or what else?
Best regards,
Olle
Same problem here...
I've got a similar problem oll3
Last saturday couldnt get my nexus s w/ stock JB to boot up, it just hanged on the Google logo. I thought it was due to a failing charger which I replaced. Then the phone worked fine for some hours until I had to reboot it. Again, stuck on Google logo. I tried booting to recovery and stumbled into the same error "E: Can't mount /sdcard/".
I've tried pretty much everything. Got the sdcard mounted couple of times which was enough to quickly take backups. However the sdcard mounts at random. Not at every boot, and yep, I've tested several old&new versions of recovery's. When the sdcard mounts, if managed to install several different rom's successfully but only to get stuck on the Google logo.
So I think it really can be a internal flash problem. I'll flash a stock rom and take the phone to the dealer for maintenance or replacement...
I'd be grateful if someone would point out how to get pass the google logo
aktuls, thanks for answering.
Unfortunately my guarantee period has passed since a couple of month. Hope you'll get your Nexus fixed, and please update me if you make any progress.
oll3 said:
aktuls, thanks for answering.
Unfortunately my guarantee period has passed since a couple of month. Hope you'll get your Nexus fixed, and please update me if you make any progress.
Click to expand...
Click to collapse
Actually I'm happy report some progress!
After busy night trying and also fiddling with the updates trying to get the JB 4.1.1 original flashed, I stumbled into error that said I have an old bootloader! Ok, I checked up the latest needed for JB 4.1.1 which the adb reported as "i9020XXLC2" and flashed it. Now I got the rom flashed and the phone has been rebooted several times today without any hiccups. :good:
So I suggest you and everyone else, stuck in Google logo, having flashed some JB based rom, to check you bootloader version and update it if needed ! Hope this helps some ! :angel:
If you have a custom recovery, there's also a chance you have that version which can't mount the SDcard. I don't recall the exact version, but one of them won't mount the SDcard with that error. Updating it fixes that.
instead of flashing each partition: boot,...
type: fastboot -w update "image-...-...zip file"
I have now run fastboot update with factory image of different versions. At least it successfully flashed boot partition, but instead it now fails on the writing of system:
Code:
$ fastboot -w update soju-jro03l/image-soju-jro03l.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: I9020XXLC2
Baseband Version.....: I9020XXKI1
Serial Number........: xxx
--------------------------------------------
checking product... OKAY
checking version-bootloader... OKAY
checking version-baseband... OKAY
sending 'boot' (3964 KB)... OKAY
writing 'boot'... OKAY
sending 'recovery' (4308 KB)... OKAY
writing 'recovery'... OKAY
sending 'system' (333431 KB)... OKAY
writing 'system'... FAILED (remote: Write Fail)
Have tried with different bootloader versions, recoveries, different versions of CWM recovery. Nothing seems to get me past the writing of system partition. In cwm 6.0.1.0 recovery I still can't mount/format the sdcard.
Partitioning the sdcard in cwm gives me "Done!", but when looking in the log file it reports some error about "you are not using parted v1.8.8.1.179-aef3!", don't know what that's suppose to mean.
Anything else I should try?
Plug your phone to pc then right click in removal disk, format, fat32, uncheck quick format. It will take some time to finish but eventaully u will fix your sdcard
sent from my Nyan NeXus S
"You're either NEXUS or against us!"
Cascabreu said:
Plug your phone to pc then right click in removal disk, format, fat32, uncheck quick format. It will take some time to finish but eventaully u will fix your sdcard
sent from my Nyan NeXus S
"You're either NEXUS or against us!"
Click to expand...
Click to collapse
Unfortunately I am not able to access the sdcard from my PC as it seems... In cwm recovery when trying to mount USB storage I get "E: Unable to write to ums lunfile (No such file or directory)". Is there some other way?
oll3 said:
Unfortunately I am not able to access the sdcard from my PC as it seems... In cwm recovery when trying to mount USB storage I get "E: Unable to write to ums lunfile (No such file or directory)". Is there some other way?
Click to expand...
Click to collapse
lock and reunlock the bootloader to format it
try that
Cascabreu said:
lock and reunlock the bootloader to format it
try that
Click to expand...
Click to collapse
Locking worked alright, but unlocking fails with message:
Code:
$ fastboot oem unlock
...
FAILED (remote: Erase Fail)
More ideas? : )
Nop sorry. Now that its locked send it to a repair shop and say that it doesnt boot up...
sent from my Nyan NeXus S
"You're either NEXUS or against us!"
Cascabreu said:
Nop sorry. Now that its locked send it to a repair shop and say that it doesnt boot up...
sent from my Nyan NeXus S
Click to expand...
Click to collapse
Thought so too, will try that.
Thanks anyway!
Got a phone from a friend. Said it was bricked.
In bootloader:
*** unlocked ***
doubleshot pvt ship s-on rl
hboot-1.45.0013
microp-0353
emmc-boot
When click recovery, get 3 skateboarders and back to menu.
Tried to load a recovery:
C:\Android>fastboot flash recovery recovery-clockwork-5.0.2.7-doubleshot.img
sending 'recovery' (4754 KB)...
OKAY [ 0.888s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 2.348s
Received above error, should I perform another step first?
Somehow finally got cwm 5.0.2.7 into recovery.
Found this thread and did basically the same thing.
http://forum.xda-developers.com/showthread.php?t=2665472
Downloaded cm-9-1-(3-0-97)-r13.zip
Checked md5sum
Extract contents of ROM to PC(boot.img)
Put the full zip and gapps on SD card
Boot to recovery
Wipe data/factory reset, wipe cache partition
Flash ROM cm-9-1-(3-0-97)-r13.zip. Install successful.
Pulled battery, boot direct to bootloader
Flash kernel with fastboot <<<<< here I get the below error
fastboot flash boot boot.img
sending 'boot' (16384 KB)...
OKAY [ 2.624s]
writing 'boot'...
FAILED (remote: image update error)
finished. total time: 4.085s
Any suggestions?
Try miktouch or another stock based ROM so you don't need to flash kernel
Sent from my Nexus 4 using XDA Premium 4 mobile app
Is there a particular miktouch I should try? Would the below link be good to try?(for some reason having hard time finding)
"cx.com/mycx/share/jzvMU-erEeGfjBICOBql1A/MikTouch-0.7-signed.zip"
And just follow the steps and flash it vs cm9, correct?
Any stock based ROM is easier to flash as you don't need to flash the kernel afterwards through fastboot. Also cm9 is one of the few Roms I have seen issues for people when trying to flash, granted it is one of the better Roms out there, but right now you are just trying to get this working again, so stick with easy.
And I would think that's a good link, but didn't check
Sent from my Nexus 7 using XDA Premium 4 mobile app
installed miktouch 07...i installed the zip from sdcard and it installed and then it rebooted the phone. Stuck at mytouch4g logo screen, left it on this screen 20+ minutes. I took battery out and turned on with the same result.
any suggestions on trying something else?
waynebattle said:
installed miktouch 07...i installed the zip from sdcard and it installed and then it rebooted the phone. Stuck at mytouch4g logo screen, left it on this screen 20+ minutes. I took battery out and turned on with the same result.
Click to expand...
Click to collapse
What ROM were you on before? If its non stock, I would try to fastboot flash the boot.img
Sent from my Nexus 4 using Tapatalk
unfortunately got it from a friend like this, not sure what he had on it.
I flashed boot.img and this is what I received:
C:\Android>fastboot flash boot boot.img
sending 'boot' (3438 KB)...
OKAY [ 0.770s]
writing 'boot'...
FAILED (remote: image update error)
finished. total time: 2.229s
Any ideas?
waynebattle said:
unfortunately got it from a friend like this, not sure what he had on it.
I flashed boot.img and this is what I received:
C:\Android>fastboot flash boot boot.img
sending 'boot' (3438 KB)...
OKAY [ 0.770s]
writing 'boot'...
FAILED (remote: image update error)
finished. total time: 2.229s
Any ideas?
Click to expand...
Click to collapse
On some of my Linux distros I would have to use fastboot flash with a ./ before it would work.
./fasboot flash boot boot.Img
I have no idea why it was like this but it helped me a fee times on the DS. If its anything else I'd have no idea, I haven't messed with this since I sent mine off to a XDA user here.
Sent from my Nexus 4 using Tapatalk
Thanks. Not using linux, but tried .\fastboot with no difference in results. Thanks for trying. Anyone else have any other ideas?
waynebattle said:
Thanks. Not using linux, but tried .\fastboot with no difference in results. Thanks for trying. Anyone else have any other ideas?
Click to expand...
Click to collapse
You said you are able to get into recovery? Try factory resetting there
Download this 1.44.1107 S-Off PG59IMG Hboot. Rename it to PG59IMG.zip. Send it to the sdcard, and reboot into the bootloader. It will then be installed automatically. This may or may not solve the problem. Try flashing a ROM now.
abe5 said:
Download this 1.44.1107 S-Off PG59IMG Hboot. Rename it to PG59IMG.zip. Send it to the sdcard, and reboot into the bootloader. It will then be installed automatically. This may or may not solve the problem. Try flashing a ROM now.
Click to expand...
Click to collapse
dont you need to be locked to do this? i've tried "fastboot oem lock" but it has an error about too many links and the phone shuts off and it shows that it is still unlocked. I tried the PG59IMG.zip anyway and it said parsing and went right back to hboot within a second.. Flashed miktouch rom. Restarted phone, still just stuck on logo screen.
What do you see in the bootloader? Has something changed? Try flashing a recovery this time. The latest Clockworkmod should be fine. Then see what happens.
abe5 said:
What do you see in the bootloader? Has something changed? Try flashing a recovery this time. The latest Clockworkmod should be fine. Then see what happens.
Click to expand...
Click to collapse
I don't see any differences in the bootloader. Is there something specific you think may have changed.
Do you want me to try to reflash the cwm 5.0.2.7 version(currently loaded) or a different version(I didn't see a newer version for 4g slide)?
waynebattle said:
I don't see any differences in the bootloader. Is there something specific you think may have changed.
Do you want me to try to reflash the cwm 5.0.2.7 version(currently loaded) or a different version(I didn't see a newer version for 4g slide)?
Click to expand...
Click to collapse
Alright. This version: http://forum.xda-developers.com/showthread.php?t=2085842
Clockworkmod 6.0.4.6
abe5 said:
Alright. This version: http://forum.xda-developers.com/showthread.php?t=2085842
Clockworkmod 6.0.4.6
Click to expand...
Click to collapse
No luck, (md5 check sum verified) get error when try to flash it:
C:\Android>fastboot flash recovery cwm.img
sending 'recovery' (6338 KB)...
OKAY [ 1.285s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 2.745s
Unfortunately my friend, I believe your emmc is severally corrupt. If you are able to get adb working from within recovery you may be able to try a few more things to bring this back to life but as it stands, with s-on, you may be sol
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
Unfortunately my friend, I believe your emmc is severally corrupt. If you are able to get adb working from within recovery you may be able to try a few more things to bring this back to life but as it stands, with s-on, you may be sol
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
When you say adb working from within recovery, I am able to mount usb storage within recovery and then on pc I can do 'adb devices' and I see the device, is that what you are referring to? Thanks.
Hi Guys,
Hoping you can help me with this.
I was originally running Slimkat 4.4.4 and had the latest TWRP installed.
I downloaded the file for LPX13D and extracted all of the files right down to the Flash-all.bat and the images for bootloader, radio, and the system.
I ran the Flash-all.bat, and it installed everything successfully. The device booted, and voila, I am on 5.0 now.
The problem now, is that when I reboot into recovery, I am instead met with the little android guy laying on his back, with a red triange/exclamation point in his chest.
No problem, I say to myself. I'll just flash TWRP manually.
So I go to the bootloader, and try the command fastboot flash recovery recovery.img (renamed to make it faster to type.)
It goes through the motions, and says it was successful.
But when I go to recovery, it's the same red triange guy still.
I tried pressing volume up, power+volume up, etc. No dice. After about 30 seconds, it reboots on it's own back to system.
When I connect it to the Nexus Root Toolkit, and click on Flash recovery, and then choose TWRP latest, I get a window that pops up that tells me :
______
File Dependency Download
Status: Stock Kernel: Not Present - Need to download (this is in red)
Then a button that says "Download + Update All File Dependencies"
So what's my best option here? Should I let the NRT update the dependencies?
Try to flash cwm and tell me what happens
Isus <3 said:
Try to flash cwm and tell me what happens
Click to expand...
Click to collapse
D:\DOWNLOADS>fastboot flash recovery cwm.img
target reported max download size of 1073741824 bytes
sending 'recovery' (11312 KB)...
OKAY [ 0.561s]
writing 'recovery'...
OKAY [ 0.930s]
finished. total time: 1.491s
D:\DOWNLOADS>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
I then selected recovery, and lo and behold, it worked! I'm in CWM.
So then i flashed TWRP again, and now it's working properly too.
I don't know why it refused to work the first time, but now it seems to be okay. How strange.
Thanks for your time and help. I appreciate it.
deleted
Stupendousman2012 said:
D:\DOWNLOADS>fastboot flash recovery cwm.img
target reported max download size of 1073741824 bytes
sending 'recovery' (11312 KB)...
OKAY [ 0.561s]
writing 'recovery'...
OKAY [ 0.930s]
finished. total time: 1.491s
D:\DOWNLOADS>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
I then selected recovery, and lo and behold, it worked! I'm in CWM.
So then i flashed TWRP again, and now it's working properly too.
I don't know why it refused to work the first time, but now it seems to be okay. How strange.
Thanks for your time and help. I appreciate it.
Click to expand...
Click to collapse
Twrp is not optimized yet well like cwm is for andorid l
Recovery won't work AT ALL no matter what you do until you reflash a KK userdata.img, which also wipes all data in the process.
Lethargy said:
I flashed the new developer preview for 5 minutes or so then went to revert. Recovery wouldn't boot not matter what I flashed, until I flashed a KK userdata.img. So it seems like the new developer preview changes the internal storage/data partition more then the old one.
Click to expand...
Click to collapse
Don't try getting around it. Nothing to do with anything else.
Isus <3 said:
Twrp is not optimized yet well like cwm is for andorid l
Click to expand...
Click to collapse
What? CWM is outdated.
Lethargy said:
Recovery won't work AT ALL no matter what you do until you reflash a KK userdata.img, which also wipes all data in the process.
Don't try getting around it. Nothing to do with anything else.
What? CWM is outdated.
Click to expand...
Click to collapse
Well, Twrp worked until I rebooted and then tried going back to it. Then bam! back to the error dude with the triangle.
So, I flashed cwm again, and that one seems to be persisting after a reboot, so I guess I'm stuck with cwm for now....
I also flashed the boot.img and the supersu update to get root working, and it seems to be going well now.
Cwm tells me that I may have lost root immediately after flashing the supersu update, but when I reboot, root is actually working. What a weird bunch of crap to go through.
Stupendousman2012 said:
Well, Twrp worked until I rebooted and then tried going back to it. Then bam! back to the error dude with the triangle.
Click to expand...
Click to collapse
Flash userdata.img and your TWRP will work properly.
Stupendousman2012 said:
So, I flashed cwm again, and that one seems to be persisting after a reboot, so I guess I'm stuck with cwm for now....
Click to expand...
Click to collapse
It isn't whether its persisting or not. TWRP just won't boot properly until you reflash a KK userdata.img. I don't know why CWM would even boot up, nor why anyone would want to really use it anyways.
Stupendousman2012 said:
Cwm tells me that I may have lost root immediately after flashing the supersu update, but when I reboot, root is actually working. What a weird bunch of crap to go through.
Click to expand...
Click to collapse
It says that because CWM is outdated.
Lethargy said:
Flash userdata.img and your TWRP will work properly.
It isn't whether its persisting or not. TWRP just won't boot properly until you reflash a KK userdata.img. I don't know why CWM would even boot up, nor why anyone would want to really use it anyways.
It says that because CWM is outdated.
Click to expand...
Click to collapse
Okay:
So I extract the userdata from a 4.4.4 stock image, yes? If not, can you point me in the direction of the correct userdata.img
I assume the correct order and syntax is:
fastboot flash userdata userdata.img
fastboot reboot-bootloader
fastbook flash recovery twrp.img
Fastboot reboot-bootloader
Select recovery
Wipe data/Factory reset, and then and reboot system.
Set up phone as normal.
Have I overlooked anything?
Stupendousman2012 said:
Okay:
So I extract the userdata from a 4.4.4 stock image, yes? If not, can you point me in the direction of the correct userdata.img
I assume the correct order and syntax is:
fastboot flash userdata userdata.img
fastboot reboot-bootloader
fastbook flash recovery twrp.img
Fastboot reboot-bootloader
Select recovery
Wipe data/Factory reset, and then and reboot system.
Set up phone as normal.
Have I overlooked anything?
Click to expand...
Click to collapse
Yeah. Don't need to boot into recovery and wipe data since flashing a .img with fastboot while in bootloader erases it first then flashes. Just make sure you backup your stuff, including internal storage, off to a PC first if you have anything important.
Until L is officially released, we're using the below thread
http://forum.xda-developers.com/show....php?t=2796217
Android "L" Developer Preview Help, Troubleshooting, Q&A
Sent from my Nexus 5 using Tapatalk
hey all
so i have to send my 2nd tablet in for my 2nd RMA. it is rooted and running one of the custom roms on here
i want to return it to stock before sending it back (does it matter? do they care? do they check? anyone know? --- this could save me some headaches i suppose)
anyways, i used Philz recovery to wipe all partitions, although data is giving me some issues, saying it cannot mount and cannot unmount.... hmmm... well, i get to fastboot to wipe everything and reflash stock images and it goes a little something like this:
fastboot flash boot boot.img - works
fastboot flash recovery recovery.img - works
fastboot flash system system.img
sending 'system'
FAILED (remote: Insufficient memory.)
Finished. total time: 0.022s
so that doesnt work
fastboot flash userdata userdata.img
sending 'system'
FAILED (remote: Insufficient memory.)
Finished. total time: 0.022s
also does not work.
and then i just dont continue with the rest of the 3 or 4 steps
does anyone have any clue what to do here? is there a corruption of my data partition? anyone know the commands to rebuild the partition (is it possible?). i remember there was some tool or command that was used on the old first gen amazon fire partitions after cwm bricked the devices that people were trying.
does any of this even matter at this point? my new tablet will be here on tuesday, and i can certainly just relock the bootloader so it appears stock, but not booting properly. they will obviously be able to rebuild using their internal nvidia tools i believe.
thoughts? comments? suggestions?
thank you
Are you RMA'ing because of cracks or anything else? They do not care about root, and I'll supposed neither for custom roms. But if the reason is related to battery life or anything elese that could be hooked to software, go back to stock.
Sent from my C6906 using Tapatalk
CM17X said:
Are you RMA'ing because of cracks or anything else? They do not care about root, and I'll supposed neither for custom roms. But if the reason is related to battery life or anything elese that could be hooked to software, go back to stock.
Sent from my C6906 using Tapatalk
Click to expand...
Click to collapse
cracks and wifi issues
ok cool, thanks for the info
I have a 1st gen Kindle Fire. emmc corruption fix?