Problem updating to Android 4.0.3 R1A
Hello! I have a rooted tablet. I'm trying to update it to Android 4.0.3 R1A from Android 4.0.3, but I can't. I am using AiO version 4.0 with adb 1.0.29. I get to the point where it asks for putting the tablet in recovery mode. When I do it, the process starts, but it fails. I've read it's normal, so I continued and tried to install "install.zip". During the verification it said "Erohibit update as a result of checking version or base sku", and the AiO tool remained with three dots. In my SD Card there are only two files: install.zip (created during the attempt to update) and the Android R1A zip of my region. I've tried everything that appears in other similar topics without luck. How can I solve these problems?
This is the picture I took when it failed.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
pepito1 said:
Hello! I have a rooted tablet. I'm trying to update it to Android 4.0.3 R1A from Android 4.0.3, but I can't. I am using AiO version 4.0 with adb 1.0.29. I get to the point where it asks for putting the tablet in recovery mode. When I do it, the process starts, but it fails. I've read it's normal, so I continued and tried to install "install.zip". During the verification it said "Erohibit update as a result of checking version or base sku", and the AiO tool remained with three dots. In my SD Card there are only two files: install.zip (created during the attempt to update) and the Android R1A zip of my region. I've tried everything that appears in other similar topics without luck. How can I solve these problems?
This is the picture I took when it failed.
Click to expand...
Click to collapse
What tool/application are you using to update and is the update unrooted?
Sent from my Sony Tablet S using xda premium
pepito1 said:
Hello! I have a rooted tablet. I'm trying to update it to Android 4.0.3 R1A from Android 4.0.3, but I can't. I am using AiO version 4.0 with adb 1.0.29. I get to the point where it asks for putting the tablet in recovery mode. When I do it, the process starts, but it fails. I've read it's normal, so I continued and tried to install "install.zip". During the verification it said "Erohibit update as a result of checking version or base sku", and the AiO tool remained with three dots. In my SD Card there are only two files: install.zip (created during the attempt to update) and the Android R1A zip of my region. I've tried everything that appears in other similar topics without luck. How can I solve these problems?
This is the picture I took when it failed.
Click to expand...
Click to collapse
AIO changed something, without the instructions changing lol.
Follow the link in the 2nd post of my FAQ link (in signature)
Cat McGowan has a good tuit there.
Chur
Stifilz
pepito1 said:
Hello! I have a rooted tablet. I'm trying to update it to Android 4.0.3 R1A from Android 4.0.3, but I can't. I am using AiO version 4.0 with adb 1.0.29. I get to the point where it asks for putting the tablet in recovery mode. When I do it, the process starts, but it fails. I've read it's normal, so I continued and tried to install "install.zip". During the verification it said "Erohibit update as a result of checking version or base sku", and the AiO tool remained with three dots. In my SD Card there are only two files: install.zip (created during the attempt to update) and the Android R1A zip of my region. I've tried everything that appears in other similar topics without luck. How can I solve these problems?
Click to expand...
Click to collapse
Hola pepito,
I received the same error, the problem it was when the tablet went to recovery mode, my PC (winXP) didn't recognize the phone, so I had to use another PC (laptop with W7) and after that every went smooth. Be sure when tablet is in recovery mode, your PC recognize the device has "ADB composite", if not, install the drivers.
good luck
AIO changed something, without the instructions changing lol.
Follow the link in the 2nd post of my FAQ link (in signature)
Cat McGowan has a good tuit there.
Chur
Stifilz
Click to expand...
Click to collapse
I followed the FAQ and the Cat McGowan instructions, but I still have that problem.
wer55 said:
Hola pepito,
I received the same error, the problem it was when the tablet went to recovery mode, my PC (winXP) didn't recognize the phone, so I had to use another PC (laptop with W7) and after that every went smooth. Be sure when tablet is in recovery mode, your PC recognize the device has "ADB composite", if not, install the drivers.
good luck
Click to expand...
Click to collapse
I tried to do it with another computer, but I had the same error again. When tablet is in recovery mode, windows doesn't recognize the tablet, it fails when searching a driver.
I wiped the tablet, but still no luck. I have tried several things, but none of them worked. "adb devices" finds the tablet when it's in normal boot, but it doesn't when it's in recovery mode; and, if I boot the tablet in recovery mode without connecting it to the computer, the same as shown in the picture of my first post (I don't know how to put it correctly, but if you open it in a new tab it will appear), E:Error in /tmp/desklunvr/desklunvr.zip (Status 7), etc. What can I do?
I discovered the problem! When I updated from Honeycomb to prerooted ICS, my region changed to US (I saw it in the build.prop). I changed it back to my region and could update without any problems.
Related
Hi all ,
i had installed an official galaxy s2 4.1.2 rom ,and it worked perfectly. However ,all of a sudden ,it looked like it automatically updated ,and got stucked at "Optimizing app 2 of 9" or something like that . I waited for a while ,when nothing changed i have pulled out the battery and tried restarting it. So it just showed the samsung logo and didnt boot. When i tried entering the recovery mode ,it just stucked with the green JB icon..basically i could just login to download mode . I have tried flashing the rom again via odin ,but it got stucked at "factory.img" and eventually wrote "FAIL" in red . I have tried numerous roms ,stock roms but nothing seemed to work.(same problem). Now when i power up the device ,it says "Firware upgrade encountered an issue. Please select recovery mode in Kies and try again." I have tried flashing just the ClockworkMOD recovery ,but it also got stucked at "NAND Write Start!" and did nothing...
Another thing is ,that im afraid that i was running a really low space on my internal storage (16 gb) and im afraid that this is why nothing can be installed on my device..Could it be possible?
If so ,is there some way to access my storage somehow without booting up my device? Or in a worse case , how can i wipe my storage before the odin flashes?
Thanks in advance.
Listen to this guy right here:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And this kid:
Feel free to try another usb socket as well.
Let us know what happens.
:laugh:
Thanks for the reply.
I have tried flashing Siyah via odin 1.85 ,but it got stucked at "NAND Write Start!!" ...
Any ideas?
Sipovka said:
:laugh:
Thanks for the reply.
I have tried flashing Siyah via odin 1.85 ,but it got stucked at "NAND Write Start!!" ...
Any ideas?
Click to expand...
Click to collapse
Try another odin version/usb cable/usb port/another pc/laptop.
I have tried different usb ports ,different computer and also different Odin version.
When i am trying to flash a complete rom ,it stucks at factoryfs.img,and if i am flashing just a kernel ,it stucks at "NAND Write Start" ...I have only one usb cable though , but it should be working fine because i was able to transfer files with it not long ago.
Could it be that lack of storage on my internal card is causing this kind of problem...?
Which sgs2 model do you have? (I9100, I9100G, I9100M, I9100P, I9100?, etc etc etc).
Which specific rom/files did you flash? (link)
These are the questions you should have answered in your first post prior to writing anything else. Without this info anything else you write is useless.
Can you provide screen shot of ODIN before clicking flash button.
Thanks for reply ,i will post soon the screenshot ,just need to gain one more post (10 or more
for posting screeshots.
I have a I9100 model and i tried a bunch of official roms for that model from different countries ,which did work for me in the past for sure ,because some of them i have kept on my hard drive.
Anyway ,here is the download link : http://www.sammobile.com/firmware/?page=3&model=GT-I9100&pcode=PTR&os=1&type=1#firmware
I am downloading the 4.03 version PDA I9100JHLPC CSC I9100PTRLPD
http://www.hotfile.com/dl/177046516/65bd55e/I9100JHLPC_I9100PTRLPD_PTR.zip.html - actual download link
This is the screenshot of my odin before the flash :
And this is the image after the flash ,where it gets stucked :
Sipovka said:
I have a I9100 model and i tried a bunch of official roms for that model from different countries ,which did work for me in the past for sure ,because some of them i have kept on my hard drive.
Anyway ,here is the download link : http://www.sammobile.com/firmware/?page=3&model=GT-I9100&pcode=PTR&os=1&type=1#firmware
I am downloading the 4.03 version PDA I9100JHLPC CSC I9100PTRLPD
http://www.hotfile.com/dl/177046516/65bd55e/I9100JHLPC_I9100PTRLPD_PTR.zip.html - actual download link
This is the screenshot of my odin before the flash :
And this is the image after the flash ,where it gets stucked :
Click to expand...
Click to collapse
Try flashing jb leak (phone, csc & modem, nothing else).
If that doesn't work, we could be talking nand corruption.
Thanks dude ,i will try it now.
What does it mean ,"nand corruption"?
Sipovka said:
Thanks dude ,i will try it now.
What does it mean ,"nand corruption"?
Click to expand...
Click to collapse
device's internal memory corrupted, can't write/read it.
That's what partitions (pit files) are for.
Well ,that didnt work as well...same scenario. I tried flashing just the rom via pda ,i tried all 4 files at the same time ,i tried just the pit...always got stucked.
I guess i will take it to my mobile service provider ,unless there is something else i could try?
P.S - If my internal card is corrupted , will they be able to see i flashed a custom rom and rooted the device?
Sipovka said:
Well ,that didnt work as well...same scenario. I tried flashing just the rom via pda ,i tried all 4 files at the same time ,i tried just the pit...always got stucked.
I guess i will take it to my mobile service provider ,unless there is something else i could try?
P.S - If my internal card is corrupted , will they be able to see i flashed a custom rom and rooted the device?
Click to expand...
Click to collapse
Lol, don't just flash pit files.
Read something about pit files first. There are a lot of threads regarding this topic.
Still stucked in boot right? no back up whatsoever?
Flash different siya's versions, see if you can get to recovery. When you do, try flashing a rom via CMW.
htc one x+ bricked how do i unbrick it
help needed.
elithegill said:
htc one x+ bricked how do i unbrick it
help needed.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
elithegill said:
htc one x+ bricked how do i unbrick it
help needed.
Click to expand...
Click to collapse
LLOIR IS BACK EVERYBODY!!! HAHAHAHAHA
Well mate to start off, 90% of the time people mistake bricking the phone for something else. If you can see the screen light up, its not "bricked". Bricking, means that whatever you do you can not fix that phone, meaning you actually can only use it as a "BRICK" as a stone. Who ever made up the word is a genius.
Anyway, Common issues:
Wiped phone no rom [NOT bricked]
Wiped SDCard no rom [NOT bricked]
Broke the screen [NOT bricked]
Phone stuck in bootloop [NOT bricked]
Phone is hot [NOT bricked , Well I honestly can't say for sure since if the phone is waaay too hot it burns your motherboard.. so]
INSERT SOMETHING HERE [NOT bricked]
Well we all have an S-ON bootloader (except the people with the devs phones), so basically you can't brick your phone. Except if you throw it into the water or something.
PrsRep suffre
Ghand0ur said:
LLOIR IS BACK EVERYBODY!!! HAHAHAHAHA
Well mate to start off, 90% of the time people mistake bricking the phone for something else. If you can see the screen light up, its not "bricked". Bricking, means that whatever you do you can not fix that phone, meaning you actually can only use it as a "BRICK" as a stone. Who ever made up the word is a genius.
Anyway, Common issues:
Wiped phone no rom [NOT bricked]
Wiped SDCard no rom [NOT bricked]
Broke the screen [NOT bricked]
Phone stuck in bootloop [NOT bricked]
Phone is hot [NOT bricked , Well I honestly can't say for sure since if the phone is waaay too hot it burns your motherboard.. so]
INSERT SOMETHING HERE [NOT bricked]
Well we all have an S-ON bootloader (except the people with the devs phones), so basically you can't brick your phone. Except if you throw it into the water or something.
Click to expand...
Click to collapse
your above message gives me a hope that I can still use reuse my phone....
basically I have hox+ and rooted my phone on 15th may to install call recorder. have used instruction from this site.
used CWM as recovery and it worked fine till recently when I tried to apply official android 4.2.2 update
after I started getting error mounting sdcard during installation of official update, I flashed CWM recovery and tried different options
and realized that my sdcard has been wiped off.
I do have the backup of "boot.img", "recovery.img", "nandroid.md5" that I took on 15th May as well as the official ROM 4.2.2
but not sure how to get it deployed and make my phone working
current state is that when I restart my phone it shows all network mode , network operators in disabled mode. even Wi-Fi doesn't turn on
while connecting through usb, it just shows my device name as HTC OneX+ and nothing else
if I try to click on the name to view folder details. it says (not responding)
therefore I would need advice from the experts here to enable my HOX+ back in working mode
please help...
just an update here
downloaded sdk 4.3 and tried with ADB command
was able to sideload the zip file to my hox+ but fails with following exception. if someone has faced this issue before please guide
starting ADB sideload feature...
installing '/data/media/sideload.zip'...
checking for MD5 file...
skipping MD5 check: no MD5 file found.
Verifying zip signature...
E:zip signature verification failed: 1
MyHOX said:
your above message gives me a hope that I can still use reuse my phone....
basically I have hox+ and rooted my phone on 15th may to install call recorder. have used instruction from this site.
used CWM as recovery and it worked fine till recently when I tried to apply official android 4.2.2 update
after I started getting error mounting sdcard during installation of official update, I flashed CWM recovery and tried different options
and realized that my sdcard has been wiped off.
I do have the backup of "boot.img", "recovery.img", "nandroid.md5" that I took on 15th May as well as the official ROM 4.2.2
but not sure how to get it deployed and make my phone working
current state is that when I restart my phone it shows all network mode , network operators in disabled mode. even Wi-Fi doesn't turn on
while connecting through usb, it just shows my device name as HTC OneX+ and nothing else
if I try to click on the name to view folder details. it says (not responding)
therefore I would need advice from the experts here to enable my HOX+ back in working mode
please help...
Click to expand...
Click to collapse
---------- Post added at 01:06 PM ---------- Previous post was at 12:21 PM ----------
signature verification can be disabled in TWRP menu under settings....
but now I encounter another problem
E:error executing updater binary in zip''/ata/mdedia/sideload.zip''
not sure if it because of official 4.2.2 release. might be it looks for pre-existing binaries of 4.1.1
will try to download other ROM and try...
MyHOX said:
just an update here
downloaded sdk 4.3 and tried with ADB command
was able to sideload the zip file to my hox+ but fails with following exception. if someone has faced this issue before please guide
starting ADB sideload feature...
installing '/ata/mdedia/sideload.zip'...
checking for MD5 file...
skipping MD5 check: no MD5 file found.
Verifying zip signature...
E:zip signature verification failed: 1
Click to expand...
Click to collapse
hi,
plz help
mine is rooted hox+ devices which is rooted
not able to connect with usb port now, doesn't show anything on my windows file explorer
moreover my mobile shows white screen with htc logo and just hangs
I tried factory reset, even though of no use
I used all-in-ont-tool-kit-2.3
please advice and help to recover my device
Ghand0ur said:
LLOIR IS BACK EVERYBODY!!! HAHAHAHAHA
Well mate to start off, 90% of the time people mistake bricking the phone for something else. If you can see the screen light up, its not "bricked". Bricking, means that whatever you do you can not fix that phone, meaning you actually can only use it as a "BRICK" as a stone. Who ever made up the word is a genius.
Anyway, Common issues:
Wiped phone no rom [NOT bricked]
Wiped SDCard no rom [NOT bricked]
Broke the screen [NOT bricked]
Phone stuck in bootloop [NOT bricked]
Phone is hot [NOT bricked , Well I honestly can't say for sure since if the phone is waaay too hot it burns your motherboard.. so]
INSERT SOMETHING HERE [NOT bricked]
Well we all have an S-ON bootloader (except the people with the devs phones), so basically you can't brick your phone. Except if you throw it into the water or something.
Click to expand...
Click to collapse
MyHOX said:
just an update here
downloaded sdk 4.3 and tried with ADB command
was able to sideload the zip file to my hox+ but fails with following exception. if someone has faced this issue before please guide
starting ADB sideload feature...
installing '/data/media/sideload.zip'...
checking for MD5 file...
skipping MD5 check: no MD5 file found.
Verifying zip signature...
E:zip signature verification failed: 1
---------- Post added at 01:06 PM ---------- Previous post was at 12:21 PM ----------
signature verification can be disabled in TWRP menu under settings....
but now I encounter another problem
E:error executing updater binary in zip''/ata/mdedia/sideload.zip''
not sure if it because of official 4.2.2 release. might be it looks for pre-existing binaries of 4.1.1
will try to download other ROM and try...
Click to expand...
Click to collapse
corrupt download try again. Also try a different usb cable if you have one
Lloir said:
corrupt download try again. Also try a different usb cable if you have one
Click to expand...
Click to collapse
thanks for ur response
now I am stuck in boot looping
and moreover my device is not recognized by windows 7 device manager
tried updating drivers but get code 10 error
seems like I am in loop myself
MyHOX said:
thanks for ur response
now I am stuck in boot looping
and moreover my device is not recognized by windows 7 device manager
tried updating drivers but get code 10 error
seems like I am in loop myself
Click to expand...
Click to collapse
Did you "fastboot flash boot boot.img" ? And you can't use OTA updates of the official rom while being rooted and with an unlocked bootloader as far as i know .
Ghand0ur said:
Did you "fastboot flash boot boot.img" ? And you can't use OTA updates of the official rom while being rooted and with an unlocked bootloader as far as i know .
Click to expand...
Click to collapse
thanks for the note
I did realize that, but now I am desperate to get my phone back in working condition
appreciate any help from experts out here
Hello people,
I just tried to install CyanogenMod 11 on my RAZR MAXX. I had an error with installed Google App, so I struggled to fix ... while was tryin to fix gapps error I have accidentally installed new CM11 over my Stock ROM :crying:
After I rebooted phone I have realized... now I cant run any ROM, I cant run even recovery. My phone just display dead android icon and keep on restarting phone every 2 min. Dead android is not responding to any try to open recovery...
I tried to flash fastboot from my PC, but RSDLite do not recognize my phone!!!
I am not sure do I have right drivers since I have reinstalled system on my PC recently, so I have downloaded and installed:
motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481/action/auth
But stil RSDLite cant recognize my phone... idk what to do, probably its because my phone keep on restarting...
PLEASE HELP ME! I dont know what to do
UPDATE:
I think that main problem is USB driver, since my PC cant recognize device. It always show me message:
The last USB device conected to this computer is malfunctioned windows can not recognize it.
Recommendation:
Try reconnecting device. If Windows stil does not recognize it, your device may not work properly.
I tried to download new Motorola drivers million times. I have also downloaded motohelper drivers and result is still the same. I tried to change PC and still the same. Always the same message!
How could I fix this? If my PC could just detect device I would be able to use RSDLite and fastboot android again...
UPDATE 2:
When I have dead android picture and keep on pressing buttons (there is no rule, not power and volume +/- , just by random pressing) I could enter to this recovery menu:
-reboot system now
-apply update from external storage
-apply update from ADB
-wipe data/factory reset
-wipe cache partition
I tried all options but always the same. Only applying update left, but I cant connect device with my computer
UPDATE 3:
I tried apply update from external storage where I have put CM11 zip file and I got this:
-- Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
Installation aborted
----------------------------------------------------------------------------------------------------------------------------------------
[1] RSD Lite Fastboot - doesnt work -> PC doesnt recognize device
[2] ADB -> doesnt work -> PC doesnt recognize device
[3] sd card -> installation aborted!!!
[4] ...
Is there any other way in which I could fix my phone? Someone please help me.
New post... for some new info, since previous got messy
Since I can only access Fast boot menu I tried to update from external storage the same version which I had previously installed.
I wasnt sure will it works since I have installed this version: Blur_Version.672.180.41.XT910.Retail.en.EU.zip
by following instructions on this link: http://forum.xda-developers.com/show...48&postcount=1
And finally Installation wasnt aborted after verifying update package... Installation started and I got this error:
Code:
assert failed: file_getprop("/system/build.prop", "ro.build.fingerprint") =="RTGB/XT910_RTGB/umts_spyder:4.0.4/6.7.2-180_SPU-19-TA-11.6/1342417437/:user/release-keys" || file_getprop(("/system/build.prop", "ro.build.fingerprint") == "motorola/XT910_rtvfde/umts_spyder:4.1.2/9.8.20-124_SPUEM-14/1362039991:user/release-keys"
restoring configuration START..
restoring configuration END..
Installation aborted.
Im not sure is that connected with Voodoo OTA Rootkeeper, SU or other steps which are listed in instructions... since now I cant do anything since start update from external storage? Anyone help please?!?
So after you got blur to install did you go back into Fastboot with power+ volume down and wipe then try a reboot?
Sent from my KFTT using Tapatalk
control187 said:
So after you got blur to install did you go back into Fastboot with power+ volume down and wipe then try a reboot?
Sent from my KFTT using Tapatalk
Click to expand...
Click to collapse
But blur installation is aborted, not finished?
I tried to wipe and reboot and repeat installation but always the same.
But now I did one good thing... first I uninstalled all drivers and Motocast and manager. And in fastboot menu I connected USB charger and my PC recognize and have successfully installed FASTBOOT SPIDER DRIVER!!!! So now RSD Lite can recognize my device.... it see that something is connected. But it cant read any info from it:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In Fastboot Flash mode its says:
Code:
0A.77
eMMC Info> Size 16G
To return to normal mode / first press power key to power down
Device is LOCKED. Status Code: 0
Battery Low
Cannot Program
Connect USB
Data Cable
Anyway am I able to fastboot new stock, if I have installed this blur version on my phone?
And how to fix this bug with RSD Lite?
EDIT:
My battery is getting low and I cant recharge it
I read some posts about making "factory recharging cable" but I dont have tools for that, and it sounds too dangerous to me
Is there any way I could just fix installation abort from previous post?
When I did it, I had to fastboot back to JB. I don't remeber the link where I got the file, But you go into rsdlite and uncompress the stock zip file, RSD does the rest.
Sent from my XT912 using Tapatalk
---------- Post added at 09:50 AM ---------- Previous post was at 09:50 AM ----------
If you already have a low battery you may have to get the special cable that charges a soft bricked phone.
Sent from my XT912 using Tapatalk
control187 said:
When I did it, I had to fastboot back to JB. I don't remeber the link where I got the file, But you go into rsdlite and uncompress the stock zip file, RSD does the rest.
Sent from my XT912 using Tapatalk
---------- Post added at 09:50 AM ---------- Previous post was at 09:50 AM ----------
If you already have a low battery you may have to get the special cable that charges a soft bricked phone.
Sent from my XT912 using Tapatalk
Click to expand...
Click to collapse
But RSD Lite cant recognize my phone. It recognize file which I uploaded, but for Device properties its N/A everywhere.
Can you post a screenshot from RSD?
Sent from my XT912 using Tapatalk
control187 said:
Can you post a screenshot from RSD?
Sent from my XT912 using Tapatalk
Click to expand...
Click to collapse
I did, 2 posts above
Sorry, didn't load earlier. What is the rest of that fail message? Is it about the battery? If the battery is low and that's why RSD won't recognize you will need to get one of those cables.
Sent from my XT912 using Tapatalk
JoLoLo said:
But RSD Lite cant recognize my phone. It recognize file which I uploaded, but for Device properties its N/A everywhere.
Click to expand...
Click to collapse
It's recognized,it doesn't matter what is written there,after the flash everything should be ok.
And from your screenshot it looks to me that you are trying to flash the wrong version rom.What was your stock,ICS or JB?
Since you don´t have the factory cable,maybe THIS is a solution
And HERE is a video tutorial how to make the factory cable.
Sent from my Razr XT910
welder73 said:
It's recognized,it doesn't matter what is written there,after the flash everything should be ok.
Sent from my Razr XT910
Click to expand...
Click to collapse
So if not needed to show Device properties to work properly then ok... I got error in first step: Phone returned FAIL.
Is this posible because my battery is low, and in Fast boot its written:
Battery Low
Cannot Program
?
JoLoLo said:
So if not needed to show Device properties to work properly then ok... I got error in first step: Phone returned FAIL.
Is this posible because my battery is low, and in Fast boot its written:
Battery Low
Cannot Program
?
Click to expand...
Click to collapse
It´s possible...
Did you try what I suggested? I edited my post,maybe you didn´t saw.
welder73 said:
It´s possible...
Did you try what I suggested? I edited my post,maybe you didn´t saw.
Click to expand...
Click to collapse
Oh I didnt saw the edited part.
I was using JB. But I used some version which doesnt allow me to go down to ISC (this thread: http://forum.xda-developers.com/showthread.php?t=2192532 ).
So I guess that I need to pick JB firmware?
This file: Android 4.1.2 - Blur_Version.982.124.14.XT910.Retail.en.EU
right?
Or I screw up everything by installing the version from link above?
P.S.
I need to get tools for making that factory cable. I will try to collect all that tomorrow.
Originally Posted by welder73
It´s possible...
Did you try what I suggested? I edited my post,maybe you didn´t saw.
Click to expand...
Click to collapse
Oh I didnt saw the edited part.
I was using JB. But I used some version which doesnt allow me to go down to ISC (this thread: http://forum.xda-developers.com/showthread.php?t=2192532 ).
So I guess that I need to pick JB firmware?
This file: Android 4.1.2 - Blur_Version.982.124.14.XT910.Retail.en.EU
right?
Or I screw up everything by installing the version from link above?
P.S.
I need to get tools for making that factory cable. I will try to collect all that tomorrow.
Click to expand...
Click to collapse
Oh,it's NOT POSSIBLE to go back to ICS,that's a well known fact.
And yes,that's a good version if you are from Europe.
Sent from my Razr XT910
Back to basics. I can only advise based on what I use. First of all, BMM for recovery. It works. I know nothing about SafeStrap.
Second I've run Linux exclusively and know little about Windows. I would install Linux on some machine and begin repairs with fastboot.
Also, it's been a long time since I've had problems with my Razr, so I've pretty much forgotten all the repair details.
I just made it!!!!! Factory cable saved me!!!! Woooooohoooooo...
Tnx everyone for helping me. After I created factory cable and pluged it into phone everything gone pretty easy... RSD Lite finaly completed fastbooting, battery status was ok and here we go:
I love happy endings.
Last year i tried to disassembly the phone to fix a probably broken audio conector, then i decided to flash a new rom; since then, i'm facing bootloop. I tried to enter into recovery and simply doesn't go there. Download Mode works just fine, so i decided to flash a new stock rom and a TWRM (latest) and the system almost worked. I could enter Recovery Mode, but when i was about to try a factory reset, the touch stopped working. So i rebooted again, then a white screen (that first one that appears, with AT&T logo on it) appeared my phone rebooted.
I flashed a stock recovery but didn't had any sucess either...
Now i'm with a galaxy note 3 (n900) and my phone is in the shelter, completely useless.
Try an emergency recovery with kies.
440bro said:
Try an emergency recovery with kies.
Click to expand...
Click to collapse
Thanks for answering, but it was no use for me.
I can only enter download mode now and my device didn't shown on that list.
Thanks, though.
You only need to be in download mode for kies to work.
Don't use kies 3 that the note 3 uses. Use the original one. Make sure it's up to date. Reinstall the i717 drivers from Samsung. Put phone on download mode and plug into pc. Open kies and click "emergency firmware recovery" type in all caps SGH-I717. Then type in serial number and let it do it's thing!
440bro said:
You only need to be in download mode for kies to work.
Don't use kies 3 that the note 3 uses. Use the original one. Make sure it's up to date. Reinstall the i717 drivers from Samsung. Put phone on download mode and plug into pc. Open kies and click "emergency firmware recovery" type in all caps SHG-I717. Then type in serial number and let it do it's thing!
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here's a screenshot of what it looks like when i do EXACTLY as you told me to.
Also, it's a recently formatted computer, so isn't any driver conflict or thinks like that.
Here's a screenshot of what it looks like when i do EXACTLY as you told me to.
Also, it's a recently formatted computer, so isn't any driver conflict or thinks like that.[/QUOTE]
Try clicking "Firmware upgrade and initialisation" instead of "emergency recovery". I might of told you wrong. I apologize. It's been awhile since I've needed to fix my i717. I moved on to note 3.
440bro said:
Here's a screenshot of what it looks like when i do EXACTLY as you told me to.
Also, it's a recently formatted computer, so isn't any driver conflict or thinks like that.
Try clicking "Firmware upgrade and initialisation" instead of "emergency recovery". I might of told you wrong. I apologize. It's been awhile since I've needed to fix my i717. I moved on to note 3.
Click to expand...
Click to collapse
Firmware upgrade is what you want. The only problem I had was Kies didn't like my serial number. Luckily my wife has a OG Note and I used her sn with no problems Good luck!
Here's a screenshot of what it looks like when i do EXACTLY as you told me to.
Also said:
440bro said:
Here's a screenshot of what it looks like when i do EXACTLY as you told me to.
Also, it's a recently formatted computer, so isn't any driver conflict or thinks like that.
Click to expand...
Click to collapse
Try clicking "Firmware upgrade and initialisation" instead of "emergency recovery". I might of told you wrong. I apologize. It's been awhile since I've needed to fix my i717. I moved on to note 3.
Click to expand...
Click to collapse
Just did that and still the same problem.
Type in SGH-I717 not SHG-I717. Hopefully you caught that typo.
Agoattamer said:
Type in SGH-I717 not SHG-I717. Hopefully you caught that typo.
Click to expand...
Click to collapse
Whoops! Good eye!!
i am also having same issue .. kies says SGH-I717 not support initializing
Agoattamer said:
Type in SGH-I717 not SHG-I717. Hopefully you caught that typo.
Click to expand...
Click to collapse
Unfortunately, it wasn't the case. I double check it before installing.
Maybe it's soft bricked.
Using odin to get you into download mode (not recovery), and flash a stock .tar file to get up and running again. Unless you have a hardware issue inside the phone.
If you want a decent tutorial on doing this, YouTube search "unbrick i717 odin" and the first video listed (for me anyway) is a video by Qbking77 on how to do this step by step. He gives links to odin files and .tar stock files for the i717.
So tried downloading the 6.0 ota. after it installed it, it got stuck in a bootloop. tried doing factor reset and deleting cache and data.
nothing has worked so far.
heres the rub, i never unlocked my bootloader and i cant get into the OS to set the developer options. it seems my only solution is to RMA it. but im hoping maybe there is a hack of some sort.
heres to hoping.
My N9 wouldnt allow me to even attempt to flash anything when it was locked. One of the first things I had to do was a fastboot oem unlock (which also required me to boot into the OS to toggle that developer option). When you flashed 6.0 did you use the "flash-all" script?
WoodroweBones said:
My N9 wouldnt allow me to even attempt to flash anything when it was locked. One of the first things I had to do was a fastboot oem unlock (which also required me to boot into the OS to toggle that developer option). When you flashed 6.0 did you use the "flash-all" script?
Click to expand...
Click to collapse
No it was an OTA update. got the notification this morning and had it install the update. it obviously didnt take. i have not rooted my tablet or done anything like that. its actually the first device ive ever not rooted....
I had the exact same problem. I installed the OTA last night, and now it sits at the boot animation for hours. I tried to wipe cache, but I got an error saying it couldn't mount the partition. I tried to sideload it, and it failed, saying it couldn't mount it. I just (reluctantly) performed a wipe and hopefully that will work, but I'm not optimistic.
Update: no luck. So I permanently deleted a lot of stuff for no reason. =/
Yeah my problem is I can't sideload because my computer doesn't recognize it . I mean this whole unlocking the boot loader from within the OS thing is the stupidest design I've ever seen.....
since i can still get into hboot and fastboot can i side load the OTA? adb isnt seeing it in recovery but it sees it in fastboot.
I was not able to sideload anything. I could see the device, I could start the process, but it would fail every time. I talked to HTC last night and they are going to replace it.
Weirdly, when I was talking with them, they had me try to clear the cache and it actually worked, so I'm going to try and sideload it one more time tonight and if it doesn't work, just swap it out.
I'm caught in the boot loop as well after having downloaded the OTA... I must say, over the past couple weeks I was stuck in boot loops on several occasions, and only after a bunch of restarts would it load fully (and "update apps").
When this device works properly, I have no qualms. But it's incredibly irritating for a $600 tablet to be so shoddy...
stevesmithis said:
I was not able to sideload anything. I could see the device, I could start the process, but it would fail every time. I talked to HTC last night and they are going to replace it.
Weirdly, when I was talking with them, they had me try to clear the cache and it actually worked, so I'm going to try and sideload it one more time tonight and if it doesn't work, just swap it out.
Click to expand...
Click to collapse
Yeah I was able to clear the cache I was even able to format the user data the problem is is there is no OS loaded. At least with the fastboot says under os it says N/A.
HTC said they'll replace it I just have to send it in to them problem is I'm a truck driver so I'm never at home.
-Wes-
Sent from my SM-N910T using Tapatalk
wesmagyar said:
Yeah I was able to clear the cache I was even able to format the user data the problem is is there is no OS loaded. At least with the fastboot says under os it says N/A.
HTC said they'll replace it I just have to send it in to them problem is I'm a truck driver so I'm never at home.
-Wes-
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
I had the same problem: even after wiping the cache and formatting the user data, the tablet wouldn't boot, and fastboot said "OS: N/A". However, I went into recovery and sideloaded the OTA file with adb. The update went fine and now my Nexus 9 works again. If you are using Windows and the computer doesn't recognize the tablet you should install the appropriate drivers, I guess (look up "Google USB Driver"). I use a Mac so drivers weren't a problem for me.
xworld21 said:
I had the same problem: even after wiping the cache and formatting the user data, the tablet wouldn't boot, and fastboot said "OS: N/A". However, I went into recovery and sideloaded the OTA file with adb. The update went fine and now my Nexus 9 works again. If you are using Windows and the computer doesn't recognize the tablet you should install the appropriate drivers, I guess (look up "Google USB Driver"). I use a Mac so drivers weren't a problem for me.
Click to expand...
Click to collapse
Will I'll be a mother effer I was able to get it to recognize my device by installing the Samsung ADB driver and from there I was able to sideload the OTA and it is now working.......
The very first thing I'm doing as soon as I actually get it start it is I am going to enable OEM unlock. Everybody who has one of these devices should do that immediately.
Thank you so much man you are awesome
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SM-N910T using Tapatalk
I tried again and it failed. Sadness. Guess I'll just have to swap it out.
I can't figure out how have my device appear when entering "adb devices" ... when i'm in fastboot, i "fastboot devices" and it shows with the serial number. when i'm in recovery, though, "adb devices" shows nada. When I'm in TWRP after selecting "ADB Sideload", my device appears in my Device Manager under Nexus 9, but I can't update driver info to anything that seems to work.
I've got the most up to date drivers via SDK.
Any ideas how I can get my device to be recognized by my PC so that I can sideload the OS?
Thank you all.
thegeneralfamily said:
I can't figure out how have my device appear when entering "adb devices" ... when i'm in fastboot, i "fastboot devices" and it shows with the serial number. when i'm in recovery, though, "adb devices" shows nada. When I'm in TWRP after selecting "ADB Sideload", my device appears in my Device Manager under Nexus 9, but I can't update driver info to anything that seems to work.
I've got the most up to date drivers via SDK.
Any ideas how I can get my device to be recognized by my PC so that I can sideload the OS?
Thank you all.
Click to expand...
Click to collapse
I was having the same problem I installed the Samsung ADB driver, , and all of a sudden my computer recognized my Nexus 9 in a adb mode
Sent from my SM-N910T using Tapatalk
Mine wouldn't show up until I was in recovery and actually picked the "install from adb" or whatever from the menu.
yeah it doesn't actually go into adb mode until you select the sideload option. just as it doesn't go into fastboot untill you are in fastboot.
I was able to download the OTA from android authority. just made sure that the upgrade matched the one that i was upgrading from, i have a galaxy note so when i couldnt get windows to recognize the nexus 9 in adb mode i selected search my computer for the drivers and selected select from installed drivers and out of sheer desperation selected the Samsung ADB driver and sure enough the worked. from there i was able to adb sideload the update and install it and it rebooted into beatiful android 6.0 tablet has been working fine so far with no issues.
First thing i did however was allow unlocking of the bootloader in the developer options.
Edit: nvm
stevesmithis said:
Edit: nvm
Click to expand...
Click to collapse
Yeah I was going to say because I'm the op, I had no access to the operating system either but I was able to accomplish two steps I laid out above and it fixed my problem.
Sent from my SM-N910T using Tapatalk
Also also misread your post. I thought you were saying that unlocked the bootloader before you fixed it. Lol