Related
Hi, I am new to all of this, but Im a quick learner. I rooted my phone and have superuser permission. I have installed multiple applications that will help me to perform ROM installs all of which still do not help. I even tried the three button solution, however I am still getting the same message when I go into recovery mode. It is as follows: E: failed to varify whole-file signature then under that I get: E: signature verification failed, instalation aborted.
I tried applying sdcard update. zip, wiped out cache partition, factory reset, etc...
I have tried everything. I tried using Mod Manager, I get the downloads but then when i try to install after I make sure to click backup rom and clear cache, it boots to the rom screen, (not really sure what you guys call it, sorry) and I get that same message, the signature failed, et...
my phone info is as follows: SCH-I500, I500 Commercial Package_DL9 To EA28 (I think verizon automaticly updated for the emergency dial) code 200
hardware version i500.04 firmware version 2.1update.1, baseband version S:i500.04 V.EA28, kernel version 2.6.29 and last but not least build number SCH-I500.EA28
Now saying all of that, I tried all of the above steps prior to this automatic update and it still did not work. I still received the signature message.
I even tried Voodoo, as well as DL30, Superclean, none of which will pass the signature autentacation. I want to try to get past this as I am having my phone replaced due to burn in and want to get the steps right so I do not BRICK my phone after it has been replaced. If this one bricks, it wont matter to much because I will have the new one on Monday.
Any help would be greatly appreciated. I love this tecky stuff and want to be knowagable on how to get past this message so I can go full force on Monday.
Thanks,
EssyG
Also I checked the site and tried everything but still won't work.
Sent from my SCH-I500 using XDA App
You will need to flash a new Recovery via ODIN which you can find below for your Samsung Fascinate:
http://forum.xda-developers.com/showthread.php?t=782204
&
Also read this http://forum.xda-developers.com/showthread.php?t=790004
Thank you, up and running 2.2, will post screen latter! Now I need to get my old phone back to stock so I can send it back to veriazon. YOU ARE THE BEST!!
P.S. I love your idea about the 10 post allowence to post on other forums.
Essy G
If o.k. I will post what I did and that way new users will be able to follow directions. I am a newbe but have become addicted to this stuff. THANKS!!
now I bricked my phone... lol
Now let me start by saying I loved 2.2, no problems with it at all. but when battery ran out I wanted to clean stats in cwm green and the screen would not come up, sd would not mount any how I tried to start over, flashing oden, all the steps, but my drivers will not stay for some reason after flashing I need to uninstall the reinstall drivers or they are not recognized, really sucks, any how I got frustrated so while in odin I pulled the plug, lol literally, and now have a pic of a "phone" then ".." then triangle with (like my icon here)"!" then ".." picture of "computer". I called verizon and there sending me yet another phone. lol my question is, will they be able to unlock it and see that I had 2.2 on it? does anyone know what they do with the phones we send back? Basicly I want to know if they can unlock that being I can't. and if so, will they see the 2.2? Any sugestions?
Anyone there?
Any one there? Also I am debating, do I wait for official release. I heard it was coming out 2/22/11. If I put dl30 on new phone again and they release the update, will I still get the automatic update via verizon? If so will I lose root? Any comments on post #5? I can't believe I had it running I totally messed it up. Thank goodness when I called verizon I got two girls at tec support, lol while I am a girl, I am a tech lover, I acted like I had no idea what happened, well they didn't either, lol So just waiting on new phone to come in, yet again so I am getting everything ready to quickly install dl30 to new phone again. Hopefully I do not lose drivers again, as it seems that once I flash in odin, the hardware icon disappers as if drivers are not installed. any how, I was just wondering if anyone had an answer to post #5 so that when I return the phone, I am not caught, lol that would really stink! Plus I am board, took off of work because my kids are sick and now I have a bad cold also, so any comments would be great!! Besides I need to be here to sign for new phone.
Thanks,
Essy g
Hi, i`ve owned an infuse for a couple months now and i`m loving it. I bought it off somebody and it came pre-rooted. Superuser was working great, i was running rooted apps and everything was pretty awesome. However, i`ve just recently wanted to try something new. Such as flashing a new rom. I downloaded the zeus rom (i also have others), went into rom manager and tried to install. That didn`t work. So i tried to manually boot into clockworkmod recovery and install. That didn`t work. I think the main problem is how do i get into clockworkrecovery? Whenever i boot into it i lack very many options that i keep seeing from others. Everytime i try to boot into it it says
Copying media files
Successfully copied meida files
Manual Mode
Appling Multi-CSC
Installing Multi-CSC
can't access to system/csc/RWC/system/
Successfully applied multi-csc
and the options are
Android system recovery <3e>
Samsung Recovery Utils for BML
Enter: Power Key, Select: vol up/ vol down
reboot system now
apply update from sdcard
wipe data/factory reset
wipe cache partition
Everytime i try to apply update from sdcard it says:
Failed to verify whole-file signature
Installation aborted.
I can't remember all of it but you get the just of the idea
I can't seem to figure this out and i dont think this is clockwordrecovery. I've tried various methods of rebooting using the CWM app, Rom Manager app, and the button pressing.
All i want to do is flash a new rom! Can anyone help?
P.S. It isn't a typo when i put "Successfully copied meida files", they actually spelt it meida.
Xparks said:
Hi, i`ve owned an infuse for a couple months now and i`m loving it. I bought it off somebody and it came pre-rooted. Superuser was working great, i was running rooted apps and everything was pretty awesome. However, i`ve just recently wanted to try something new. Such as flashing a new rom. I downloaded the zeus rom (i also have others), went into rom manager and tried to install. That didn`t work. So i tried to manually boot into clockworkmod recovery and install. That didn`t work. I think the main problem is how do i get into clockworkrecovery? Whenever i boot into it i lack very many options that i keep seeing from others. Everytime i try to boot into it it says
Copying media files
Successfully copied meida files
Manual Mode
Appling Multi-CSC
Installing Multi-CSC
can't access to system/csc/RWC/system/
Successfully applied multi-csc
and the options are
Android system recovery <3e>
Samsung Recovery Utils for BML
Enter: Power Key, Select: vol up/ vol down
reboot system now
apply update from sdcard
wipe data/factory reset
wipe cache partition
Everytime i try to apply update from sdcard it says:
Failed to verify whole-file signature
Installation aborted.
I can't remember all of it but you get the just of the idea
I can't seem to figure this out and i dont think this is clockwordrecovery. I've tried various methods of rebooting using the CWM app, Rom Manager app, and the button pressing.
All i want to do is flash a new rom! Can anyone help?
P.S. It isn't a typo when i put "Successfully copied meida files", they actually spelt it meida.
Click to expand...
Click to collapse
You don't have cwm recovery yet.
Don't use ROM manager.
I made a thread on "how to." It's a collection of some things I've learned.
Start there.
The link is on my signature line
So where should i start? At the flashing part?
Xparks said:
So where should i start? At the flashing part?
Click to expand...
Click to collapse
Start here:
[REF] [HOW TO] [ROM Installation] Where to start?
Xparks said:
So where should i start? At the flashing part?
Click to expand...
Click to collapse
yes..follow gtg's CWM instruction set
So. I already started with the odin UCKD5 one. http://forum.xda-developers.com/showthread.php?t=1092021
and i already started into download mode. However, it now says downloading. and my computer was like "installing new hardware" then "could not install new hardware" and now my phone is stuck in the downloading screen that says do not turn off target. Odin has yet to pick up my phone....what now?
if you have root you can flash a cwm enabled kernel with sgs kernel flasher.
if you have froyo use the defuse or community kernel. or use gtgs thread for cwm without flashing a kernel.
if you have gingerbread then you will need to flash one of the custom kernels such as entropy dd, hellraiser, or infusion. gtgs cwm thread will not work on gingerbread.
My phone is rooted and running on gingerbread. But um. i have a more pressing concern at the moment....this downloading screen is freaking me out...
okay well i can't seem to figure any of this stuff out. any noone has replied so i just reset my phone so i can actually use it.
Some more information for those who can help is that the firmware is 2.3.3
Baseband version is I997RUXKG3
Kernel version
2.6.35.7-I997RUXKG3-CL366622
Build number
Gingerbread.uxkg3
Xparks said:
okay well i can't seem to figure any of this stuff out. any noone has replied so i just reset my phone so i can actually use it.
Some more information for those who can help is that the firmware is 2.3.3
Baseband version is I997RUXKG3
Kernel version
2.6.35.7-I997RUXKG3-CL366622
Build number
Gingerbread.uxkg3
Click to expand...
Click to collapse
that's Rogers firmware. use kernel flasher (easiest) and flash one of the popular gingerbread kernels. entropy dd is popular. once the kernel is on there You will have red cwm. that will allow you to flash whatever.
if you flash a rom it will include a kernel so don't worry about the minor incompatibilities that exist with att based roms.
So i'm currently on this thread
http://forum.xda-developers.com/showthread.php?t=1212795
with this in the other tab
http://forum.xda-developers.com/showthread.php?t=1289460
I'm not sure which kernel to download. But i'll try flashing a couple anyway
also i tried using heimdall/odin or whatever. It wouldn't pick up my phone in download mode. and thus couldn't install drivers.
well. I tried flashing one of the kernels. specifically
DD_02162012_A.zip - [Click for QR Code] (5.16 MB, 118 views)
So i flashed it using SGS kernel flasher. it said flashing....rebooting. And now it's stuck at the rogers logo. I have no clue what to do and i think it might be bricked. So if i could get someones help, perhaps step-by-step as i obviously cannot do this following the other instructions.
Xparks said:
well. I tried flashing one of the kernels. specifically
DD_02162012_A.zip - [Click for QR Code] (5.16 MB, 118 views)
So i flashed it using SGS kernel flasher. it said flashing....rebooting. And now it's stuck at the rogers logo. I have no clue what to do and i think it might be bricked. So if i could get someones help, perhaps step-by-step as i obviously cannot do this following the other instructions.
Click to expand...
Click to collapse
You are stuck in bootloop. Not bricked or even close to it. Read infused rom and flash it. If you cannot figure that out you should not be flashing. It's dead simple. Promise. Search it. It's in the dev thread. Called infused by gtg
Sent from my SAMSUNG-SGH-I997 using Tapatalk
thanks for the help so far. but i went here. http://forum.xda-developers.com/showthread.php?t=1116251
and the link no longer works. so what now. I can't get the files and therefore can't put anything into odin.
sigh. so i downloaded the files from someone who uploaded it again. Did everything. Succesful. only to have it be stuck in bootloop and samsung screen. Did what it said. pulled battery, replace, vol buttons and power key until recovery shows up. That doesn't happen. Instead i notice that instead of a rogers screen it says at&t and then goes to samsung screen. and then restarts again by going back to at&t. If i let go of the buttons it goes back to begin stuck at the samsung one. This has made so many problems for me.... just by trying to get clockworkmod. what do i do now?
Xparks said:
thanks for the help so far. but i went here. http://forum.xda-developers.com/showthread.php?t=1116251
and the link no longer works. so what now. I can't get the files and therefore can't put anything into odin.
Click to expand...
Click to collapse
Xparks,
You really should read up a bit. If you looked toward the end of that thread,
you will see that the file has been uploaded by another user to another site:
http://forum.xda-developers.com/showthread.php?t=1116251&page=40
i got that one already. i've passed that step. I'm now stuck in bootloop with at&t and samsung logo. Bootloop was supposed to be a rare occurence...and the instructions to work around it aren't working right now. I can't access recovery mode. Or anything for that matter.
Xparks said:
i got that one already. i've passed that step. I'm now stuck in bootloop with at&t and samsung logo. Bootloop was supposed to be a rare occurence...and the instructions to work around it aren't working right now. I can't access recovery mode. Or anything for that matter.
Click to expand...
Click to collapse
Download the drivers for the phone on the computer. If it does not work then, try heimdale. If you can not do this, then just ask me for the jtag guy, ill give you the link to the website. Mobiletechvideos uses jtag to recover the phone (taking it apart, hooking it up with a ton of wires lol). Keeps personal data, just recovers rom, or you can pay a little extra for him just to install whatever rom. It worked for me, you may have a broken usb controller like me all of a sudden.
I have kies but when i start it up it says please connect your mobile phone. And it doesn't pick up my phone. It probably shouldn't seeing how my phone is stuck. But i went to menu in kies and pressed install driver. But i'm not sure how to download my exact driver if kies can't even pick up my phone. But i ran the "zazig" program. and i'm installing the drivers from there. And i'm going to attempt to reflash using that since Odin didnt work before. The link is this http://forum.xda-developers.com/showthread.php?t=1331381
And it did that. But i don't what to do. I've been on xda reading forums all day and the only thread i can see relevent to mine is someone advising them to bring it back under warranty. Mines rooted. no warranty for me. I hope if it ever works again i can use it on rogers still because it says AT&T.....and i'm afraid to try and unlock it. because we know the last time i tried to do something.....
Odin can still detect it and i tried reflashing the unbrick stuff. No dice.
I am new here so please bear with me.
I have a "rooted" Nexus S i9020. When I bought it it had Android 4.0.4 installed. Recently I have been receiving a message telling me that a system update to Android 4.1 is ready to be installed. I have tried accepting the update, but halfway through it stalls and all I see is a triangle with an exclamation mark in it. The phone will then not respond and requires removal and refitting of the battery to restart it. Luckily, it has returned to working order with 4.0.4 still installed.
Is the phone not accepting the update because it is rooted?
Can I get the OTA update without erasing all data and settings?
I have an app. called Superuser v.3.1.3 on the phone. It has a box to tick marked "temp unroot" and another "OTA survival".
Would either of these tools be any use?
I have tried to understand all the information given on the forum posts but there is just too much to take in.
Can someone explain what I have to do to get the phone updated without "bricking" it?
When I enter Bootloader mode it says:
FIRST BOOT MODE
PRODUCTNAME HERRING
HW VERSION REV 11
BOOTLOADER VERSION I9020 XXKL1
BASEBAND VERSION I9020 XXKI1
SER.NO etc.
LOCK STATE LOCKED
Is this information helpful? I have read about "clockwork mods" and "Roms", but I don't know what you mean.
Thank you in advance.
Clockworkmod replaces your stock recovery and then giving you options to flash ROMs etc. If you want to learn more... start with the sticky threads in development.
Your phone is rooted so if you want to get the update you need to temp. Unroot using the superuser app like you mentioned. Try to get the update. Please report back if it helped
Sent from my Nexus S using xda app-developers app
so far no brick...
kwibis said:
Clockworkmod replaces your stock recovery and then giving you options to flash ROMs etc. If you want to learn more... start with the sticky threads in development.
Your phone is rooted so if you want to get the update you need to temp. Unroot using the superuser app like you mentioned. Try to get the update. Please report back if it helped
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
I ticked the "temp unroot" box and tried installing the update again. Same result. Install stops with exclamation mark triangle and grinning android. Restart by taking out the battery. Ok, I still have a phone. Running Android 4.0.4, but now there is no upgrade available and I will have to wait until they get around to offering it again before I can experiment further. If I check for updates, it tells me that I am up to date.
I wish that there was more information. I mean, what's the point of a triangle with an exclamation mark? Why can't it tell me what the problem is? Then I might be able to fix it.
Thank you for taking the trouble to reply.
PS. This device cost me £150, I really don't want to break it, and I would like to be in control of it. If I brick it, then I suppose I will sigh, then go down to Carphone Warehouse and sign a contract for a locked, dumbed down, boring, toe-the-line Samsung SIII. But I would much rather be the master of a rogue, rooted, rough and ready-for-anything Nexus S.
monkey shoulder said:
I ticked the "temp unroot" box and tried installing the update again. Same result. Install stops with exclamation mark triangle and grinning android. Restart by taking out the battery. Ok, I still have a phone. Running Android 4.0.4, but now there is no upgrade available and I will have to wait until they get around to offering it again before I can experiment further. If I check for updates, it tells me that I am up to date.
I wish that there was more information. I mean, what's the point of a triangle with an exclamation mark? Why can't it tell me what the problem is? Then I might be able to fix it.
Thank you for taking the trouble to reply.
PS. This device cost me £150, I really don't want to break it, and I would like to be in control of it. If I brick it, then I suppose I will sigh, then go down to Carphone Warehouse and sign a contract for a locked, dumbed down, boring, toe-the-line Samsung SIII. But I would much rather be the master of a rogue, rooted, rough and ready-for-anything Nexus S.
Click to expand...
Click to collapse
The triangle with an exclamation mark is most likely your stock recovery, that somehow got restored. Re-flash CWM or TWRP, then try to apply the OTA again.
Can't you be rooted and not have cwm?
Sent from my Nexus S using xda app-developers app
Install rom manager... the cwm 6.0.1.0 applies the ota.
Make sure you tick ota survival in superuser and after the ota cwm will ask you is you want to keep the stock recovery for next boot or keep the cwm.
Then it asks you to fix root rightz..select fix . And now you got the 4.1.1 rooted by ota
Sent from my Nexus S using xda app-developers app
monkey shoulder said:
I am new here so please bear with me.
I have a "rooted" Nexus S i9020. When I bought it it had Android 4.0.4 installed. Recently I have been receiving a message telling me that a system update to Android 4.1 is ready to be installed. I have tried accepting the update, but halfway through it stalls and all I see is a triangle with an exclamation mark in it. The phone will then not respond and requires removal and refitting of the battery to restart it. Luckily, it has returned to working order with 4.0.4 still installed.
Is the phone not accepting the update because it is rooted?
Can I get the OTA update without erasing all data and settings?
I have an app. called Superuser v.3.1.3 on the phone. It has a box to tick marked "temp unroot" and another "OTA survival".
Would either of these tools be any use?
I have tried to understand all the information given on the forum posts but there is just too much to take in.
Can someone explain what I have to do to get the phone updated without "bricking" it?
When I enter Bootloader mode it says:
FIRST BOOT MODE
PRODUCTNAME HERRING
HW VERSION REV 11
BOOTLOADER VERSION I9020 XXKL1
BASEBAND VERSION I9020 XXKI1
SER.NO etc.
LOCK STATE LOCKED
Is this information helpful? I have read about "clockwork mods" and "Roms", but I don't know what you mean.
Thank you in advance.
Click to expand...
Click to collapse
Unlock your bootloader first (will erase SD card) How to is in these.
http://forum.xda-developers.com/showthread.php?t=1007782
http://forum.xda-developers.com/showthread.php?t=1623481
after that do this
http://forum.xda-developers.com/showthread.php?t=1785672
this is hard...
thank you all, i am working on it, but i still don't understand.
Jayjay: I downloaded the SDK and followed the instructions in the guide you suggested, but my PC does not recognize the Android device.
When I try to browse for the driver software I get a Hardware Update Wizard, and then I'm up to my ass in alligators. "Choose Hardware Type" it says but none of them are accepted. There is no choice called "Android Bootloader Interface". There are 2 folders, one for i386 and one for amd64, my PC is athlon64X2 so I look in there, and there are 3 "dll"s but nothing with that name.
Anyway I thought my phone was already rooted, why do I have to root it again? Must it be done in a certain way so that you can be sure that it was done properly?
I will keep trying, but this is bloody hard work.
are you sure?
raducux said:
Install rom manager... the cwm 6.0.1.0 applies the ota.
Make sure you tick ota survival in superuser and after the ota cwm will ask you is you want to keep the stock recovery for next boot or keep the cwm.
Then it asks you to fix root rightz..select fix . And now you got the 4.1.1 rooted by ota
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
I have read this on another forum:
Please note that you cannot flash clockwork on Samsung Phones using ADB, or ROM Manager (you'll hard brick the device). If there is a version of clockwork (specific to that particular Samsung device) it must be flashed using Odin.
So what do I believe?
monkey shoulder said:
Jayjay: I downloaded the SDK and followed the instructions in the guide you suggested, but my PC does not recognize the Android device.
When I try to browse for the driver software I get a Hardware Update Wizard, and then I'm up to my ass in alligators. "Choose Hardware Type" it says but none of them are accepted. There is no choice called "Android Bootloader Interface". There are 2 folders, one for i386 and one for amd64, my PC is athlon64X2 so I look in there, and there are 3 "dll"s but nothing with that name.
Anyway I thought my phone was already rooted, why do I have to root it again? Must it be done in a certain way so that you can be sure that it was done properly?
I will keep trying, but this is bloody hard work.
Click to expand...
Click to collapse
So you didn't get through part 1 in this? http://forum.xda-developers.com/showthread.php?t=895545
This can help you with the drivers. Install and run.
http://junefabrics.com/android/download.php
I heard people using this, I've never tried it http://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s-or-nexus-s-4g-new/ or http://forum.xda-developers.com/showthread.php?p=23573589
You are rooted but your bootloader is locked so you have to unlock it to reflash a rom, including 4.1.1. You can't do the OTA in the current state of your phone. http://forum.xda-developers.com/showpost.php?p=29519097&postcount=11
More info http://dottech.org/tipsntricks/2153...ows-computer-for-use-with-your-android-phone/
Hope this helps.
monkey shoulder said:
I have read this on another forum:
Please note that you cannot flash clockwork on Samsung Phones using ADB, or ROM Manager (you'll hard brick the device). If there is a version of clockwork (specific to that particular Samsung device) it must be flashed using Odin.
So what do I believe?
Click to expand...
Click to collapse
clockworkmod website. Pick nexus s http://www.clockworkmod.com/rommanager/
Getting tired...
jayjay3333 said:
So you didn't get through part 1 in this? http://forum.xda-developers.com/showthread.php?t=895545
This can help you with the drivers. Install and run.
http://junefabrics.com/android/download.php
I heard people using this, I've never tried it http://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s-or-nexus-s-4g-new/ or http://forum.xda-developers.com/showthread.php?p=23573589
You are rooted but your bootloader is locked so you have to unlock it to reflash a rom, including 4.1.1. You can't do the OTA in the current state of your phone. http://forum.xda-developers.com/showpost.php?p=29519097&postcount=11
More info http://dottech.org/tipsntricks/2153...ows-computer-for-use-with-your-android-phone/
Hope this helps.
clockworkmod website. Pick nexus s http://www.clockworkmod.com/rommanager/
Click to expand...
Click to collapse
When I plug the phone into the PC a "New Hardware Wizard" starts. I guided it to the "\\android-sdk\extras\google\usbdriver" folder and it "cannot install this hardware because it cannot find any software". The folder "USB driver" has a file called "android_winusb.inf", which appears to contain information specifically relating to the Nexus S, but the sub folders contain .dlls which are not recognized by the wizard, and there is no file called "Android Bootloader Interface" anywhere.
So I tried again. This time I let the wizard search for software, and it found an Acer USB driver which it installed. But when I connect the phone it is still not recognised, and the wizard wants to run again.
Ok this time I try the PDA net software that JayJay recommends. I'm not sure what it's supposed to do, but when I try to connect my phone the PC says "Error 2DAnet driver is either not installed or must be reset, try to reboot you computer", which I do, with no improvement. Oh and a pop up from the systray sez "Broadband error 13"
I am assuming that when the phone is "recognized", I will have full access to the file system. At the moment, when I connect, it calls the phone " usb mass storage device, drive J " and is treating it as if it is a memory stick. I have successfully backed up photos, music and downloaded files to the PC. One of the things I have been trying to do is get at the wallpaper photo which I have read is in "data\data\com.android.settings\files\wallpaper.jpg" but I cannot find such a folder on my phone, so I assume it must be one of those things you get to see when you've got this "android debug bridge " thing.
I am getting tired now I have been at this for hours.
Tomorrow I will try the "ROM Manager"
Goodnight.
Progress
So I download the ROM Manager. On the first Run the screen goes black and stays black. A great start. I reboot and get Rom manager. It is trying to sell me google chrome. No thank you I want Android 4.1.
Rom manager tells me that my ROM "is not set up to receive over the air updates - please contact ROM developer." Who might that be? Is it called Herring? I have no idea who supplied the 4.0.4 ROM for this device. I try to backup the current ROM and Rom manager wants to reflash the ClockworkMod recovery.
Now I have discovered that I have CWM installed already. (It must have been there for the previous owner to have installed ICS.) I have CWM 5.0.2.0.
Still, best to have the latest version...and so I flash the CWM.
This fails 3 times and I have to reboot each time. I then try updating Superuser to the latest version. This also fails and hangs the phone, just a screen saying "downloading manifest". No sign of progress, no status bar, no rotating thingy. Eventually I reboot and try again. ( I am getting confident about this reboot game, I've had to do it lot's of times and so far it hasn't let me down, and brings me back to a working phone.)
When Superuser has finally settled down to v3.1.3, su binary v3.1.1 I have another shot at flashing CWM from ROM manager. Yeah! This time it sticks!
I now have CWM 6.0.1.0
So I back up my ROM...this seems ok apart from a message "no sd-ext found"... but I don't know what that means so I ignore it.
Now I try applying the 4.1.1 update. All looks good for a while with a little android with a dodecahedran or something in its belly. Then..clunk!
The little android is on it's back with it's legs in the air. There is a report that I send to rommanager. It is long, (would you like me to Post it?)
basically it says:
" can't open /dev/tty0: no such file or directory"
"unable to get recovery.fstab info for datadata fstab generation"
"failed to verify whole file signature"
"failed to open /sys/class/android-usb/android0/state: no such file or directory" - this over and over again...
Now I think I have a BIG problem.
I get the feeling that something is corrupted and there are bits missng from my file structure. This would explain why I could not find a "data/data" directory and a whole lot else.
Actually beginning to enjoy this, I may end up with £150 paperweight, but I am learning a lot about code. Like when I got the SDK ADB installed and typed help then found that I couldn't send the output on the Command Line to the printer so I had to look it up on Wikipedia...
I am still learning. I think I need to know where to get the true Google Android 4.1.1 from if I cant get it over the air.
I have read about a thing called Nexus Root Toolkit by a chap called Wug fresh or something, I am not unfamiliar with DOS but my command line skills are a bit rusty.
I started with Algol 60 you know.
Goodnight
Close but no cigar...
OK. I have backed up my rom, using Titanium Backup.
I have "unlocked" my bootloader using the downloaded Android SDK ADB fastboot.exe ( It's in "platform tools" now, not "tools")
I have CWM 6.0.1.0 , Superuser 3.1.3 with OTA survival ticked.
Now all I have to do is wait until the OTA upgrade is offered again. ( It seems to come round randomly, every few days.)
Ssh! wait.. Yes! After leaving the phone overnight, the upgrade was waiting for me in the morning. I tap install..
...and fail again.!
This time its:
E: failed to verify whole file signature
E: error in /cache/9ZGgDXDi.zip (status 7)
installation aborted.
Why do you guys make it sound so easy?
I clear my cache ( if there is an error in it, it makes sense to clear it.)
I'll try again tomorrow.
monkey shoulder said:
OK. I have backed up my rom, using Titanium Backup.
I have "unlocked" my bootloader using the downloaded Android SDK ADB fastboot.exe ( It's in "platform tools" now, not "tools")
I have CWM 6.0.1.0 , Superuser 3.1.3 with OTA survival ticked.
Now all I have to do is wait until the OTA upgrade is offered again. ( It seems to come round randomly, every few days.)
Ssh! wait.. Yes! After leaving the phone overnight, the upgrade was waiting for me in the morning. I tap install..
...and fail again.!
This time its:
E: failed to verify whole file signature
E: error in /cache/9ZGgDXDi.zip (status 7)
installation aborted.
Why do you guys make it sound so easy?
I clear my cache ( if there is an error in it, it makes sense to clear it.)
I'll try again tomorrow.
Click to expand...
Click to collapse
Ok now just get the proper factory image. You are a Nexus S i9020 just check if you are a T or an A (look under the battery). Flash Android 4.1.1 (JRO03E). Follow part 1 of this guide http://forum.xda-developers.com/showthread.php?t=1785672
Then flash clockwork and super su
Stock, rooted, profit!
stick with it...
monkey shoulder said:
OK. I have backed up my rom, using Titanium Backup.
I have "unlocked" my bootloader using the downloaded Android SDK ADB fastboot.exe ( It's in "platform tools" now, not "tools")
I have CWM 6.0.1.0 , Superuser 3.1.3 with OTA survival ticked.
Now all I have to do is wait until the OTA upgrade is offered again. ( It seems to come round randomly, every few days.)
Ssh! wait.. Yes! After leaving the phone overnight, the upgrade was waiting for me in the morning. I tap install..
...and fail again.!
This time its:
E: failed to verify whole file signature
E: error in /cache/9ZGgDXDi.zip (status 7)
installation aborted.
Why do you guys make it sound so easy?
I clear my cache ( if there is an error in it, it makes sense to clear it.)
I'll try again tomorrow.
Click to expand...
Click to collapse
Its a bit confusing to begin with mate, but read and re-read the many tutorials and guides on here, take it slowly and step by step and youll get there in the end.
Youll be flashing custom ROMs before you know it! (take your time and always backup)
Is worth it. :good:
S
It is good that in the process you learnt lot of things. Now you have fastboot working and you know how use fastboot.
Now that the OTA is giving errors, the best way is to flash the Jelly Bean factory image which is available from Google. As per suggestions from
jayjay3333 said:
Ok now just get the proper factory image. You are a Nexus S i9020 just check if you are a T or an A (look under the battery). Flash Android 4.1.1 (JRO03E). Follow part 1 of this guide http://forum.xda-developers.com/showthread.php?t=1785672
Then flash clockwork and super su
Stock, rooted, profit!
Click to expand...
Click to collapse
Go to the link to download the image files first, then flash the 3 files using the fastboot commands provided. The overall process of flashing the factory images does not take more than 5 mins.
Best of luck.
nearly there...
jayjay3333 said:
Ok now just get the proper factory image. You are a Nexus S i9020 just check if you are a T or an A (look under the battery). Flash Android 4.1.1 (JRO03E). Follow part 1 of this guide http://forum.xda-developers.com/showthread.php?t=1785672
Then flash clockwork and super su
Stock, rooted, profit!
Click to expand...
Click to collapse
Ok I downloaded the jro03e file it is 191Mb
The download is a .tar file not a tar.gz It is called soju_jro03e_factory_c9f5a67d.tar. It is196,458 kb
The instructions say I should 'extract' it, using 7zip, which gives me a file with the same name but no extension! Windows identifies it as a ".file". It is now 207,410 kb.
The instructions say there is a folder inside which I should extract. No such thing is visible.
The next part of the instructions says I should modify the file names before running. Does that mean:
fastboot flash bootloader bootloader-crespo-i9020xxkl1.img
fastboot reboot-bootloader
fastboot flash radio radio-crespo-i9020xxki1.img
fastboot reboot-bootloader
fastboot -w update image-soju_jro03e_factory_c9f5a67d.tar
Is that right? Shouldn't all those hyphens be underscores?
Is that xxkl1 or xxki1 the same or different? ( looks like a typo).
Does only the last bit change?
Ready when you are!
oops silly me...
Well it looks like I don't understand 7Zip very clearly.
After a bit of fiddling about I "extracted" the .tar file, then "extracted" the resulting file to get a folder with a bootloader image, a radio image and an image-soju-jro03e.zip
I tried to follow the XDA instructions given here http://forum.xda-developers.com/showthread.php?t=1785672
but it seems I don't understand how to use ADB fastboot either, because when I entered the commands all I got was a list of options, a sort of helpfile for the fastboot command.
I am just not comfortable with the command line, you make one mistake and you've got to enter it all again.
Anyway I decided to try the "Nexus Root Toolkit" http://www.wugfresh.com/dev/nexus-root-toolkit/
After ensuring that my drivers were OK, I pointed the toolkit at the files and executed them individually. ( There is a "flash-all.sh" , but I don't understand how to use that. )
first of all I flashed the bootloader... Success! I now have bootloader crespo i9020xxlc2.
I didn't bother with the radio, I already have radio-crespo-i9020xxki1.
So I try to flash the jro03e.zip... Damn! The toolkit cannot find my device! Funny, it was perfectly happy before the bootloader flash...maybe that has changed something. I start again, reboot everything, check drivers... yes all ok. This time the toolkit is happy and offers to install the .zip, I include a full nandroid backup and drag and drop the image-soju-jro03e.zip to the install/flash.zip box.
TWRP v2.2.0 does it's thing and after a lot of stuff happens on the phone screen I get a menu, from which I access a report that basically says: "Error flashing zip". My heart sinks...
Other attempts with different settings result in the same:
"signature verification failed"
"no MD5 file found"... etc... etc...
So I reboot again and am relieved to find that I still have a phone.But it is still 4.0.4.
Ah! but now it has the image.zip on the SD! Progress! My heart soars with new hope!
This time I use ROM Manager to install the .zip from SD... But no such luck, "installation aborted", the little green android is flat on its back again.
Rom Manager generated a recovery log. (would you like me to post it?) Basically it says:
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
Preparing to install ROM...
about to run program [/cache/dowipedalvikcache.sh] with 1 args
mount: mounting /dev/block/mtdblock4 on /cache failed: Device or resource busy
mount: can't find /sd-ext in /etc/fstab
umount: can't umount /sd-ext: Invalid argument
run_program: child exited with status 1
Installing update...
Installation aborted.
result was NULL, message is: assert failed: install_zip("/sdcard/!ReadyToFlash/image-soju-jro03e.zip")
Have you any idea what that all means?
Will I ever get JB 4.1 on this phone?
Its beginning to look like there is something fundemental missing.
Please help!
S.
its gone quiet...
This thread doesnt seem to be getting attention anymore so I shall start a new one.
Is that ok? Its a new question "what does this recovery log tell me?", but it is still the same problem. The trouble is there are too many questions and it is very difficult to know what to ask.
I am still trying to get Android 4.1 on my phone. I have read the various instructions and tried to follow them but they did not work in the way I expected. Part of the problem is that I do not understand what I am doing. I don't understand the tools I am using.
I think it would help a great deal to see the file structure on my phone.
Is there a program that can look at that like windows explorer? Then I might be able to see what I am doing. At the moment I have no idea what is on my "SD card". The Nexus S doesnt actually have one of course, but I understand that it has 16Gb of storage that work like an SD card.
Now In the course of this project, I have "Backed up" with Rom Manager, but I don't know where that backup is, or what it is called. I did a "Nandroid backup" with the Nexus Root Toolkit but I have no idea where that is (is it on PC, or on the phone somewhere?) or what it is called. I assume it will be found automatically by the software when it needs to restore it. I have not backed up with "Titanium Backup" beause I am not sure how to do it. When I select "Backup/Restore" it displays a long list of files, some in red some in green, which say they are not backed up yet. Which ones do I select? All of them? I have no idea.There are so many options in the menus that I am terrified of Titanium, and don't know where to start, and it is going to take days to read the helpfiles. Is Titanium saying they are not backed up because it didn't back them up, or because it can't recognise the backups that were made with Rom Manager? If I backup everything with Titanium, is it going to make backups of the backups that another program made?
I'd like to be sure that I have just one good copy of the backup, that I havent filled my memory with useless junk.
S
I've searched & found 'How to....' threads on here but TBH I'm not a techy and most of it doesn't make sense to me.
I did try to upgrade from 4.0.4 to 4.1 this week and almost succeeded until some 'signature not recognised' message appeared. So I'm going to attempt another way (if possible/allowed) and ask if there's anybody out there who'd be willing to root (whatever that means), flash (ditto) and upgrade to 4.1 for me in return for payment.
I really hope this isn't against forum rules - it's a genuine, last-ditch attempt.
I live in the West Mids but travel a big chunk of the country each week so could possibly deliver the thing.
Here's hoping for an avalanche of replies.....
Can anyone tell me why I get the 'signature not verified' message please?
I've downloaded the upgrade from an October thread on this forum.
Which xoom do you have (wifi, 3g/4g, international, family)? Are you rooted yet?
dfib1 said:
Which xoom do you have (wifi, 3g/4g, international, family)? Are you rooted yet?
Click to expand...
Click to collapse
Thanks for replying!!
It's the wi-fi model. As for 'is it rooted?' - I would say not. One, because it's hardly been used and two, because I have no idea what 'rooted' means.
junctiontwo said:
Thanks for replying!!
It's the wi-fi model. As for 'is it rooted?' - I would say not. One, because it's hardly been used and two, because I have no idea what 'rooted' means.
Click to expand...
Click to collapse
Sorry I took so long to answer.
As for being rooted if you are the only one to have own the xoom and don't know what it means then you are most likely not rooted. Root is like getting administrator rights in windows. It gives you the ability to customize your device, install custom roms and also completely screw up your device .
You should be able to go to settings-about tablet--update (or system update) and it will check for your update and ask you to start the download and install. If this does not happen then you can flash back to Honeycomb (which I can walk you through this will also wipe all your data or maybe for a fresh start) and let your device automatically update to ICS (4.04) and the JB (4.1).
I can also walk you through rooting and installing a custom JB rom like you asked for free.
dfib1 said:
Sorry I took so long to answer.
As for being rooted if you are the only one to have own the xoom and don't know what it means then you are most likely not rooted. Root is like getting administrator rights in windows. It gives you the ability to customize your device, install custom roms and also completely screw up your device .
You should be able to go to settings-about tablet--update (or system update) and it will check for your update and ask you to start the download and install. If this does not happen then you can flash back to Honeycomb (which I can walk you through this will also wipe all your data or maybe for a fresh start) and let your device automatically update to ICS (4.04) and the JB (4.1).
I can also walk you through rooting and installing a custom JB rom like you asked for free.
Click to expand...
Click to collapse
Please don't apologise - you're the only one to answer!
I've tried the system update and have been told that there are none. (In my ignorance I actually thought it would update to 4.1.2 automatically!).
Your offer to walk me through the rooting & upgrade is extremely generous and I accept without hesitation.
If it's flashed back to HC, will it default back to ICS or move to JB?
A huge 'Thanks'.
James
PS. Having tried numerous times very recently to upgrade there's no data to erase so that's not an issue....
I am going to give you the steps to unlock your xoom, install a recovery, root, install CWM Rogue Touch recovery (better than the one you used to root) and then install stock JB.
Now that we are talking root I am going to ask a moderator to moved this thread to the root section.
Here is how I rooted my xoom.
follow the directions here but instead of doing step 1 follow this for adb install http://www.support-4-you.com/main/i...ged-adb-installation&catid=40:how-tos&Itemid= it is a 1 click adb install then follow from step 2 on.
When you are done there you can install CWM Rogue Touch screen recovery
Download CWM Rogue Touch zip and put on the root of your external sd card. ( if you don't have a sd card we will do it another way just let me know)
Boot into recovery by turning your xoom off.
1. press power
2. when the moto dual core logo comes on wait 3 seconds and press volume down
3. recovery should be displayed across the top press volume up.
You can skip steps 1- 3 now that you are rooted if you download Quick Boot open it, select recovery and the grant Super user permission
4. go to install zip from sd card (just like when you rooted) and find the CWM Rogue Touch Zip and install
5. reboot your xoom
6. you now have CWM Rogue Touch installed.
To install JB on your xoom you do need an sd card for this part
DownloadJB stock for wifi xoom and copy to your sd-card
Here is the thread discussing this [JB]Stock Android 4.1.1 JRO03H, Root, via CWM Recovery (US Wi-Fi MZ604) and also there steps for installing it but I will post them for you here.
boot into recovery
select backup and let it backup your current system (a Parachute)
then select wipe factory/data ( I Can't remember excactly what it says because I use a different one)
then select install zip from sd card
locate the JB rom you copy to your sd-card and install.
reboot system (it will take some time the first time)
sign in to android with your gmail account.
You are on JB
Good luck and don't worry if something goes wrong we can get you out of 99.99% of any issues that arise.
dfib1 = I cannot thank you enough.....
The frustrating thing is I'm about to leave the house and am working away until the weekend so can't try it until then! I'll let you know the outcome.
Have a great day :good:
If you need help with his excellent guide just post here or hit with a pm
Sent from my Xoom using xda app-developers app
Ok, a quick mid-procedure question....
(I'm doing something fundamentally wrong because I can't quite finish the upgrade).
Do I install the folders onto the Xoom from the SD in a zipped or un-zipped state? I've tried both but no luck so far in completing the task.
I've rooted successfully as my PC recognizes the device. I believe I've installed CWM ok - is there a way to confirm this?
On the final 4.1 install I get the 'installation aborted' message as 'signature not verified'. One thing I may be doing wrong is installing the wrong files? On selecting the JRO03H folder I'm then given file choices and I'm clicking on what I think are the most obvious. I can post a list of the choices if it helps?
Sorry to be such a newbie pain - I realize that these questions are irritating to those 'in the know'!
did you reboot after fastbooting the recovery? the recovery says clockwork at the top. It should also be touch screen controlled
When you move the zip over leave it as a zip on you xoom and when you flash the recovery will unzip it for you.
what step are you up to?
Sorry for the late update. I've tried the whole procedure several times from the very beginning, even removing previously installed Rogue & JB software, but STILL get the same error messages as previously described. I've re-booted at the right time according to the instructions but this still makes no difference, and have checked the 'USB de-bugging' option.
I did make a couple of basic errors in the Command function to begin with but realised these & corrected them. My device serial no. appeared so I assume I rooted successfully? I'm able to change Developer settings which I couldn't before. I even installed the USB drivers independently via the Motorola website.
I have a free day today so am going to make a bucket of coffee, make myself comfortable and start again.
One quick point - I'm in the UK and assume you two helpful guys are in the US? Looking at numerous sites it seems our respective Xoom models have different procedures which is maybe why this isn't working?
Thank you again for your seemingly endless patience.......
i believe you are getting these issues because you might still be running the stock recovery.
lets just backup and start fresh.
You followed the instructions mentioned before and I assume you have adb and fastboot installed.
Connect your xoom and make sure usb debugging is on.
open up a command line and type adb reboot bootloader
I'm going to assume because of the previous steps you unlocked the bootloader if not type in the command line fastboot oem unlock
You can download the recovery from here http://bit.ly/iLRAIV
If unlocked at the bootloader type fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img Note:make sure the img file is in the same folder where your fasboot.exe is in the sdk
after it has been flashed reboot device by hold volume up and power.
Move the JB stock rom into your sd card. you can download the rom from here http://www.mediafire.com/?qhbhlbvu859bv0f
after the device restarts type adb reboot recovery
in recovery Wipe everything except the sd card. Then flash the above jb rom. In theory everything should work. If you keep getting the error get back to us because Im going to give up and guide you through the install of the Team EOS Jellybean 4.1 rom that I know works without issues. PM if you want to have my direct contact info for gtalk so we can discuss further for any issues.
OK I've just tried another 8 times to root the thing, c-a-r-e-f-u-l-l-y following the instructions step-by-step.
1. I don't have the 'from SD card' option, instead have 'from USB drive'. I have a 16Gb flash drive connected via an adaptor for the Xoom which doesn't appear to prevent anything as it reads the contents of the card just fine, unless you can tell me otherwise?
2. In Recovery I get these options:
* reboot system now
* apply update from USB drive
* wipe data/factory reset
* wipe cache partition
3. Even when trying the very first install (Rogue), I get:
--Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E: signature verification failed
Installation aborted
I love a challenge and always get a buzz when I manage to do something that is foreign to me i.e computers. On this occasion however I'm fast getting to the stage where I think it'd be easier to leave things at 4.0.4.
My reason for wanting the upgrade in the first place is because I'm comparing this tablet to my work-supplied Galaxy Tab 2 running 4.1.1. Realistically I don't think the two will ever be comparable and I'm probably foolish to think this could be the case. It only remains to say that I am so very grateful to both of you for taking so much time & effort in talking me though the procedures.
I consider myself pretty 'switched on' but this has me foxed!
Cheers guys - have a great weekend. Hope the snow doesn't cause you problems!
here are the outline of the steps
1. unlock your xoom
2. fastboot a recovery to install custom recovery on your xoom
3. reboot into new recovery
4. flash universal root zip to root your phone
5. reboot phone that is now rooted.
6. reboot phone into custom recovery again
7. flash jb update
I think you have missed step 1 or 2.
When you type fastboot oem unlock what does it say?
Hmmm, I MAY be one step closer?
After typing' fastboot oem unlock' the tablet has gone into 'Starting Fastboot protocol support' but appears to be stuck. Do I wait until it's done it's thing?
OR would it be a whole lot easier for all concerned if we tried your other suggestion dfib and flashed back to HC and then to JB?
What if you type adb devices? Does a bunch of numbers show up or does it say waiting for device?
Hold the front page!!!!!!!
I just watched a video on how to unlock and it's worked. You were quite correct - I had missed your point 1 above and probably point 2. I'm moving onto the next bit now....
Great let us know what happens. I will be around for a while.
Hey guys!
To start, I want to say what an amazing place XDA is and how much information and knowledge you can get from here and how awesome the moderators are. I don't think I could ever find another amazing and/or helpful community such as those found here! Thanks to all who have helped me out with my Android issues!
Now to my issue and I apologize ahead of time if there is another thread (or related thread) found in the forum.
As the title states, I have a 2013 Motorola Moto G XT1031 Boost Mobile device. I had upgraded it to Lollipop 5.0.2 or 5.1 when it came out (I can't remember which one it was) and I had then decided to root it. I can say that I believe I was successful in rooting the device because I was able to install Supersu and use RootChecker to verify the install. Everything was going okay until i decided to research and eventually install a custom recovery and attempt to install a custom ROM. Well, let's just say that the recovery install was a bust...
In doing my research for a custom recovery, I found that TWRP had a custom recovery for my phone and apparently for my firmware via TWRP's app on the Play Store. So, I searched for my device in their in-app search for a custom recovery, downloaded it and installed it from the app. Now, my gut told me that this probably wouldn't work and that I should probably be installing a custom recovery via CLI. Nope. I didn't do this. Instead, like I said, I installed a custom recovery from the app itself. That screwed things up for me. I have no idea if it was the install, but my phone began to act incredibly strange. When in the TWRP recovery, my screen had this line that would continuously scroll from top to bottom. It wasn't a completely solid line, but it was transparent, almost like an empty thermometer glass stick was going down the screen. It was weird and not normal. I figured the phone's software was partially broken. It only did this in the TWRP recovery. Nowhere else did this happen. It was slightly annoying.
Later on I decided to install a custom ROM. Again, I did the necessary research to find out if there were any ROMs available for my phone (using XDA of course and others) and found that there were a few out there. So, I downloaded one (wish I could remember which one) and attempted to install it...keyword there. After attempting the install, my phone would not boot. Like at all. Dead. So back to the drawing board I went to try and reverse the damage. Using XDA (ironically) and a plethora of other sites, I tried to resurrect my phone and bring it back to life. After countless hours of trying and trying and trying and more and more research, I just gave up. The phone is dead. Great. $170 spent on a phone to break it a year later.
It's been roughly 4-5 months since I have attempted to redo the process and after another minor attempt, somehow I was able to remove the root completely, including the custom recovery and ROM. I don't know what the heck I did, but it worked....sort of. The phone is now stuck in a bootloop on the logo and sometimes the "bootloader has been unlocked" screen when try and factory reset the phone from the default recovery. When trying to reinstall the stock firmware, I read everywhere that I need the phone to have USB-debugging set and to have this and that. I have this and that installed on my PC, but obviously cannot enable USB-debugging which is needed for ADB and fastboot to recognize my device.
So, my question for anyone who would like to help me out is this: what are my options? Is the phone recoverable? Is there any way I can get ADB/fastboot to see my device and finally install the stock firmware on the phone? I have the proper drivers installed and ADB/fastboot are on my PC. Any help would be amazing, even if you have to tell me to junk it.
blckdragn22 said:
When trying to reinstall the stock firmware, I read everywhere that I need the phone to have USB-debugging set
Click to expand...
Click to collapse
This is incorrect, where did you read that? To reinstall the stock firmware using fastboot, you must be able to boot to the bootloader menu only.
I heard this from a few websites actually, although I could never find a situational fix for my phone. I am trying to restore back to Lollipop without a custom recovery, because within the past hour I found out TWRP was never fully removed when I tried booting into recovery from the AP Fastboot menu when doing to power+vol down option. The TWRP logo shows for about 10 seconds and then the phone tries booting normally, showing the unlocked bootloader warning.
So, yes I can boot into the bootloader menu all day long with no problems. It's just an selection I make doesn't get me anywhere. My question I guess now is: how do I go about reinstalling stock firmware via the bootloader menu. I have Minimal ADB and Fastboot installed on my PC. If I need the full ADB, I can download that. And of course I'd need the firmware, too.
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
_that said:
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Click to expand...
Click to collapse
This thread had the firmware I was looking for thank you. I believe I have the flashing stock firmware process down, I hope. I'l refer to the guide if I need help. Thank you so much!
_that said:
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Click to expand...
Click to collapse
I am trying to follow the steps listed here http://forum.xda-developers.com/showthread.php?t=2542219&page=35 and for some reason I cannot run any of the commands pertaining to the sparsechunks. This is what I get:
Is there anything you could tell me about that?
Edit: I was able to figure what the issue was when trying to write the sparsechunks. I had to insert a "." after 'sparsechunk' because that is how the file is named in the folder. However, now I am getting a new error, but it takes place on the phone screen. Every time I attempt to write a sparsechunk, it will initiate the process of doing so, but on the phone I'll get what appears to be an error saying, "Image is too large" in pink lettering. Why does this happen? Each sparsechunk file is at least 4MB less than the max-sparse-size according to the ADB and my phone, which is set to 256MB. Is there any way to change that?
blckdragn22 said:
However, now I am getting a new error, but it takes place on the phone screen. Every time I attempt to write a sparsechunk, it will initiate the process of doing so, but on the phone I'll get what appears to be an error saying, "Image is too large" in pink lettering. Why does this happen? Each sparsechunk file is at least 4MB less than the max-sparse-size according to the ADB and my phone, which is set to 256MB. Is there any way to change that?
Click to expand...
Click to collapse
Check which sparsechunk files you have and make sure you flash all of them in ascending order. If it still fails, copy/paste the contents of your command prompt window (no screenshots please).
_that said:
Check which sparsechunk files you have and make sure you flash all of them in ascending order. If it still fails, copy/paste the contents of your command prompt window (no screenshots please).
Click to expand...
Click to collapse
I will try that. There was a ...sparsechunks.0 as well apart from sparsechunks.1, sparsechunks.2 and sparsechunks.3. Shall I include that, too?
And adding the screenshot was an amateur mistake. My bad.
@_that this worked like a charm. Phone is 100% working ans usable now. Incredibly helpful. Thank you so much!