Related
alright i have this problem and i am quite panicking now.
i will set everything straight , i hope someone reading the forums can help me asap !
- have a sgs2 unbranded (hk)
- has ICS 4.0.3 stock rom, rooted.
- i don't remember if usb debug mode was enabled
- i messed up in some way with the file /system/build.prop but there is a backup in /system/ called build.prop.bak
- phone doesn't boot anymore as it's stuck at the logo
- recovery and download modes work however
#need a way to delete the build.prop and replace the bloody file with the one backupped. I would like to avoid having to format the phone as i do not remember when was my last kies backup...
what i tried:
-adb shell: it doesn't work. for some stupid reasons the drivers won't be recognized (i have download android sdk and usb drivers), but when i plug the phone in recovery windows just says Device Unknown and even if i update drivers manually it would say that current ones are functioning so no need to update.
if i connect the phone to usb while it's stuck at boot logo, it would recognize the device through samsung drivers (except MTP of course, that would give error).
in both cases adb shell doesn't list any connected device: even if i kill-server and start-server it still doesn't list anything.
-tried using droid explorer in both frozenboot mode and recovery mode, doesn't see anything.
-tried using that other program called SuperOneClick or something like that, that has a "check drivers" button in advanced: if the phone is in recovery pressing the button doesn't do anyhing; if the phone is in frozenboot it asks to download and install some drivers but when i press yes a message appears with " no more data is available " !
i tried this procedure on both win7x64 and winXPx86: same results. reading around , someone says that adb shell will never work if usb debug is de-actived, like i said i cannot remember if that's the case.
-zip package: i created a package to try and overwrite the file with a custom working one i got. i put the package in the root of the micro sd , put the sd in the phone and booted in recovery.
but when i am in recovery the bloody CWM 5.0.2.7 says error to mount /sdcard, or E: could not mount /sdcard , same if i try to mount/unmount /sdcard. if i go to mount external usb card or whatever it says that a file or a lib (cant remember the exact message) was not found.
i have no more ideas of how to solve this, please be patient :<
edit: is there a way to soft format the system folder so that i don't have to properly wipe all my user data and it only affects the system without other contents?
If adb doesn't work hen you are in trouble, better download some non wipe rom and flash it over the existing rom so that your user data will still be there.
Sent from my GT-I9100 using xda premium
bala_gamer said:
If adb doesn't work hen you are in trouble, better download some non wipe rom and flash it over the existing rom so that your user data will still be there.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
can you expand on this?
give any suggestion/example?
isn't there a soft temp rom for emergencies like this that you can just start, make modifies to fix and reboot (similar to the process to boot ubuntu on windows, fix issues and then restart normal windows? )
i would so like to make adb work.. but how.!!!
probebly will not work but try backing up of your ROM from CWM working or not..then just back up current one...
you can restore apps & data lateron from nandroid backup with some application like titanium backup donated version.
i made a backup . but since the external sd card isn't found by the recovery, now the backup is sitting on the internal memory.
the problem is that, if i flash something with odin now, won't odin wipe everything in the internal memory killing my backup as well?
-marco- said:
i made a backup . but since the external sd card isn't found by the recovery, now the backup is sitting on the internal memory.
the problem is that, if i flash something with odin now, won't odin wipe everything in the internal memory killing my backup as well?
Click to expand...
Click to collapse
nope....it will be there dont worry,
just check one more option, go to storage and mount, there is one option mount usb storage, after connecting your phone to PC just mout that and check, are you able to access the SDcard from the computor ot not, if yes, just copy paste your backup to the computor.
then flash a firmware from ODIN
Did the very same thing myself yesterday.. Most ICS-roms from Samsung is non-wipe, so you can just flash it over again with Odin.. Then you just need to root and make customizations (if any) again
zaheedahmed said:
nope....it will be there dont worry,
just check one more option, go to storage and mount, there is one option mount usb storage, after connecting your phone to PC just mout that and check, are you able to access the SDcard from the computor ot not, if yes, just copy paste your backup to the computor.
then flash a firmware from ODIN
Click to expand...
Click to collapse
nope. i just tried this , and when i "mount /sdcard" it says " Error mounting /sdcard! "
when i try mount USB storage , it says " E: unable to open ums lunfile (no such file or directory) "
mljjlm said:
Did the very same thing myself yesterday.. Most ICS-roms from Samsung is non-wipe, so you can just flash it over again with Odin.. Then you just need to root and make customizations (if any) again
Click to expand...
Click to collapse
could you be more specific on the process ? can you suggest me one to flash with odin ? i need to enter the OS , transfer my backup on my hard disk and then restore the whole thing.
currently my kernel is CF-Root-SGS2_XX_XEO_LPQ-PROPER-v5.4-CWM5.tar
and my firmware is GT-I9100_BRI_I9100ZSLPE_I9100OZSLPE_I9100ZSLPE.tar
-marco- said:
nope. i just tried this , and when i "mount /sdcard" it says " Error mounting /sdcard! "
when i try mount USB storage , it says " E: unable to open ums lunfile (no such file or directory) "
could you be more specific on the process ? can you suggest me one to flash with odin ? i need to enter the OS , transfer my backup on my hard disk and then restore the whole thing.
currently my kernel is CF-Root-SGS2_XX_XEO_LPQ-PROPER-v5.4-CWM5.tar
and my firmware is GT-I9100_BRI_I9100ZSLPE_I9100OZSLPE_I9100ZSLPE.tar
Click to expand...
Click to collapse
you try to reflash once more CF-Root (.TAR)only from odin
then check "E: cant mout...error" is rectified or not.... also check booting or not,
still no hope...you flash the same firmware again and Cf-root, your SD card data will be there for sure as far as our expereicne till now..
first part of your comment: i tried reflashing the kernel; no changes. same errors
second part: shall i try using the same firmware from my previous post then?? not other roms? after that i will put the root and check if internal memory is still there. if it is i will copy it on my hd and restore.
if it is not there anymore..............
so the end of the story.
thanks to anyone who helped.
the resolution was much easier than everything else.
opened odin, pda loaded my same firmware which was the HK stock update to ICS and reflashed.
what it did was apparently and overhaul of the system folder, that's it.
any data was still there, as well as the backup that i did and all my apps etc etc etc.
however especially at first it looked a bit unstable, with processes failing randomly. now it seems it has stabilized a bit, but still when i try to run a Kies backup, the phone kies process dies and the backup gets stopped.
i still don't know how to fix this, but i'll be looking into it.
so, the morale out of this was at least for me: if there is some **** up within the system folder just reflash the same rom installed. i feel so stupid now for having made such a fuss when the solution was so easy and straightforward
NICE that you finaly came across and able to boot , now you make the Titanium back of your all apps and data transfer to PC....forget the system data.
and move to a nice stable ROM
"Unfortunately, wssyncmlnps has stopped"
anybody knows about this?
[SK17i] I can not explore/find my build in ROM (storage)~ Please Help~
I connect my phone to my pc via usb cable, but my pc only can read/explore my SD-Card only.
I flash .58 firmware back to my phone~ but my pc can not read the build in ROM/Memory~
Thanks~ Please HELP me~ =)
aMReY said:
[SK17i] I can not explore/find my build in ROM~ Please Help~
I connect my phone to my pc via usb cable, but my pc only can read/explore my SD-Card only.
I flash .58 firmware back to my phone~ but my pc can not read the build in ROM/Memory~
Thanks~ Please HELP me~ =)
Click to expand...
Click to collapse
You can not read your phone memory without root access. That's what root is for. To read what's in the ROOT of your cell. That is, to read or edit what's in the phone memory of your phone.
Thanks,
Rick
Hit Thanks if I helped in anyway
Sent from my SK17i using XDA
Hi Dragon thank~
I mean build in storage~ My pc only can explore phone card storage only.
http://www.gsmarena.com/sony_ericsson_xperia_mini_pro-3713.php
How can I explore my build in strorage?? 400MB~
and phone is rooted and unlockbootloder~ =)
aMReY said:
Hi Dragon thank~
I mean build in storage~ My pc only can explore phone card storage only.
http://www.gsmarena.com/sony_ericsson_xperia_mini_pro-3713.php
How can I explore my build in strorage?? 400MB~
and phone is rooted and unlockbootloder~ =)
Click to expand...
Click to collapse
Via PC we cannot access build in storage... coz usually build in storage is used to store apps and system folder
That's android fact unless your device has eMMC storage device and configured as internal SD storage(Like Galaxy Note)
aMReY said:
Hi Dragon thank~
I mean build in storage~ My pc only can explore phone card storage only.
http://www.gsmarena.com/sony_ericsson_xperia_mini_pro-3713.php
How can I explore my build in strorage?? 400MB~
and phone is rooted and unlockbootloder~ =)
Click to expand...
Click to collapse
Okay. Built in storage means phone meomory. That is, the root of your device.
Since you say that your device is rooted, you can download an app called Root Explorer (paid), or ES File Explorer (Free. Make sure you turn on root features from settings for this app), and using them, you can navigate and make changes to the files in the root of your phone.
Currently there isn't any way to navigate the phone memory files from pc, as you can do with sd card (as far as my knowledge goes). But you can pull files from the root of your phone to the pc using adb pull, make changes and push it back again using adb push. (search for that to know more).
Thanks,
Rick.
Hit Thanks if I helped you in anyway
Sent from my SK17i using XDA
sss2sssss said:
Via PC we cannot access build in storage... coz usually build in storage is used to store apps and system folder
That's android fact unless your device has eMMC storage device and configured as internal SD storage(Like Galaxy Note)
Click to expand...
Click to collapse
really~ thanks for helping~ =)
DragonClawsAreSharp said:
Okay. Built in storage means phone meomory. That is, the root of your device.
Since you say that your device is rooted, you can download an app called Root Explorer (paid), or ES File Explorer (Free. Make sure you turn on root features from settings for this app), and using them, you can navigate and make changes to the files in the root of your phone.
Currently there isn't any way to navigate the phone memory files from pc, as you can do with sd card (as far as my knowledge goes). But you can pull files from the root of your phone to the pc using adb pull, make changes and push it back again using adb push. (search for that to know more).
Thanks,
Rick.
Hit Thanks if I helped you in anyway
Sent from my SK17i using XDA
Click to expand...
Click to collapse
Thanks~ Rick~ =)
Currently there isn't any way to navigate the phone memory files from pc, as you can do with sd card (as far as my knowledge goes).
Click to expand...
Click to collapse
Google: Droid Explorer
Sent from my Xperia Live using xda premium
Hi,
I don't know how many u guys have figured it out this workaround yet, but I still see many asking questions to the dev's about when UMS is gonna be incorporated in CM10/AOKP builds...
I have accidently found this neat little trick that enables UMS on CM10/AOKP roms..
Till now I have tried and got it working succesfully on Fusions cm10 kangs and Task/Ktoonez AOKP builds , but I do believe it should work on other cm10/aokp roms too..
So steps are fairly simple and here it goes :
1. Download the UMS 1.0 apk which is used as a TPA by many as a replacement. Many of U might have it , but for those who don't : https://www.dropbox.com/s/8490g42b01255t9/USB Mass Storage for JB.apk
2. Install the app. Open it .. it will take few seconds to get SuperUser permission.. then connect the USB connector and a notication will popup with blue androbot.. touch it and it will turn green to ur UMS will be connected.. Ensure that both internal and external SD are connected and accessible (Imp).
3. Turn off UMS and reboot the phone... Once booted up uninstall the UMS app
Reboot the phone again and then try to connect to USB again.. This time you will get prompted like this : (See screenshot)
4. Now u connect to the PC via UMS , and as always bot turns green.. Voila u have UMS now !!!
I do know some of you might have already been using this , and I don't boast it being a great discovery.. just something worth sharing for the unaware..
Cheers !!!
I wonder where that feature went. It don't matter to me because you can still transfer files including video and music to your phones. Without having to do those steps.
I would also assume you would have to do those steps every time you flash a new ROM or updated your old one. But thanks for the info
Sent from my SGH-I777 using xda premium
chibixzero said:
I wonder where that feature went. It don't matter to me because you can still transfer files including video and music to your phones. Without having to do those steps.
I would also assume you would have to do those steps every time you flash a new ROM or updated your old one. But thanks for the info
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
Yes.. u can still transfer videos, music etc using MTP.... but in my case MTP was quite iffy... randomly throwing write errors and sometimes only copying partial files..
Also one more issue that I was facing with MTP was , with every new rom install, I was not able to pre-existing files on External SD .. although it showed certain space as full.. it didn't show the contents.
So I researched and finally got this working this way.. using UMS I never have any issues mentioned above.. Thus this solution maybe more beneficial for guys having this issue like me
And to your question - yes u do have to follow this step with every new ROM install..
I believe the reason for getting rid of UMS was to consolidate internal and external memory to a single "drive" and that's why MTP is used. I don't know if that's completely accurate but that was my understanding. But I agree, I'm no fant of MTP.
kool2zero said:
I believe the reason for getting rid of UMS was to consolidate internal and external memory to a single "drive" and that's why MTP is used. I don't know if that's completely accurate but that was my understanding. But I agree, I'm no fant of MTP.
Click to expand...
Click to collapse
I have no idea why MTP is implemented instead of UMS and I think u may be right on the money for the reason behind this, but I do know this -
MTP is really pain in the ass. U can't copy two files seperately at one time. Hell u can't even delete one file while copying other. Sure it does pull up both drives under same roof, but for cm10 its quite buggy for less fortunate like me
I hear ya brother
With UMS I had no issues. Now when copying over my music it fails with certain tracks stating the device was disconnected. Only those files though. It even warns me before the transfer that certain media files might not be playable. I accept the warning but if one of my tracks plays, they all should. My whole collection was ripped to mp3 personally using the same codec settings for all.
Currently on the CM10 2012.09.24 nightly.
kool2zero said:
I believe the reason for getting rid of UMS was to consolidate internal and external memory to a single "drive" and that's why MTP is used. I don't know if that's completely accurate but that was my understanding. But I agree, I'm no fant of MTP.
Click to expand...
Click to collapse
MTP allows the filesystem to be changed without unmounting it from the operating system. This allows phone apps and processes that use any resources on the volume to continue to use them. With UMS, the volume is unmounted and mounted via USB to the computer. Another 'feature' of MTP is that it doesn't have to be removed like UMS. Since UMS mounts as a USB volume and most operating systems implement some form of write-caching with normal volumes, even though a copy operation 'completes', it may be cached, and not actually have completed copying data.
In Windows, removing the device via the tray icon tells Windows to finish any operations it has pending, close open files, and unmount the filesystem. If you remove the device before doing these things, you CAN get corrupted data. From my experience, this rarely happened, and never with small files. Then you get that annoying dialog every time you reconnect the device that the volume needs scanning, blah, blah...
dev997 said:
Hi,
I don't know how many u guys have figured it out this workaround yet, but I still see many asking questions to the dev's about when UMS is gonna be incorporated in CM10/AOKP builds...
I have accidently found this neat little trick that enables UMS on CM10/AOKP roms..
Till now I have tried and got it working succesfully on Fusions cm10 kangs and Task/Ktoonez AOKP builds , but I do believe it should work on other cm10/aokp roms too..
So steps are fairly simple and here it goes :
1. Download the UMS 1.0 apk which is used as a TPA by many as a replacement. Many of U might have it , but for those who don't : https://www.dropbox.com/s/8490g42b01255t9/USB Mass Storage for JB.apk
2. Install the app. Open it .. it will take few seconds to get SuperUser permission.. then connect the USB connector and a notication will popup with blue androbot.. touch it and it will turn green to ur UMS will be connected.. Ensure that both internal and external SD are connected and
accessible (Imp).
3. Turn off UMS and reboot the phone... Once booted up uninstall the UMS app
Reboot the phone again and then try to connect to USB again.. This time you will get prompted like this : (See screenshot)
4. Now u connect to the PC via UMS , and as always bot turns green.. Voila u have UMS now !!!
I do know some of you might have already been using this , and I don't boast it being a great discovery.. just something worth sharing for the unaware..
Cheers !!!
Click to expand...
Click to collapse
this is already implemented in cm10 you could simply just go to Settings > Storage > hit Menu > select either mtp, mass storage or ptp Connection. what this app do is just to activate the usb mass storage mode. It is already incorporated in cm10. cheers
gorgy76 said:
this is already implemented in cm10 you could simply just go to Settings > Storage > hit Menu > select either mtp, mass storage or ptp Connection. what this app do is just to activate the usb mass storage mode. It is already incorporated in cm10. cheers
Click to expand...
Click to collapse
Strange, it appears to have been left out of Taks's AOKP 9/24 release. Was that added to CM10 recently?
ugoff said:
Strange, it appears to have been left out of Taks's AOKP 9/24 release. Was that added to CM10 recently?
Click to expand...
Click to collapse
And since tasks AOKP isn't built from cm10 it makes sense.
Thanks fr the steps
I have Note 10.1 Model N8000 with JB 4.1.2 (Germany)
Pl tell me if I can install this on my N8000
If anyone has made it work, pl share the steps
Thanks
clive48 said:
Thanks fr the steps
I have Note 10.1 Model N8000 with JB 4.1.2 (Germany)
Pl tell me if I can install this on my N8000
If anyone has made it work, pl share the steps
Thanks
Click to expand...
Click to collapse
No go to the section for your phone.
Sent from my Zanpakuto using Getsuga Tensho!
clive48 said:
Thanks fr the steps
I have Note 10.1 Model N8000 with JB 4.1.2 (Germany)
Pl tell me if I can install this on my N8000
If anyone has made it work, pl share the steps
Thanks
Click to expand...
Click to collapse
Search for the right forum for ur tablet. Type ur model number then xda
Can I flash this on my iPhone 5?
please reupload this
the download link is "dead"
Phalanx7621 said:
Can I flash this on my iPhone 5?
Click to expand...
Click to collapse
yes this app is specially created for iphone 5 )
CaineRau said:
yes this app is specially created for iphone 5 )
Click to expand...
Click to collapse
Yes! Score!
Phalanx7621 said:
Yes! Score!
Click to expand...
Click to collapse
anyway to restore MTP functionality after doing this? MTP option just dissapeared.
and i need it because thats what i use when sincying my music (i mean i need both) but seemes like once i do this theres no turning back.
its either just connected or connected as Mass storage, akso my camera ptp mode disapeared :S
arana1 said:
anyway to restore MTP functionality after doing this? MTP option just dissapeared.
and i need it because thats what i use when sincying my music (i mean i need both) but seemes like once i do this theres no turning back.
its either just connected or connected as Mass storage, akso my camera ptp mode disapeared :S
Click to expand...
Click to collapse
Disclaimer: I have no knowledge of AOSP roms, or of the application in the OP. That being said...
File transfer behavior is governed by the system property /data/property/persist.sys.usb.config. This is a text file containing a single string. The settings are "mass_storage,adb" or "mtp,adb". Since this is a system file, it is necessary for the phone to be rooted, and then this file can be edited using a root file explorer. Change the text in the file to mtp,adb (without spaces), save the file, and reboot the phone. UMS, or USB Mass Storage is the first one. This is true for Samsung firmware.
hello friends
can some one please point me to a thread link or something that helps me in Enabling Mass Storage on my device which is rooted and flashed with jelly bean
ankscorek said:
hello friends
can some one please point me to a thread link or something that helps me in Enabling Mass Storage on my device which is rooted and flashed with jelly bean
Click to expand...
Click to collapse
in setting/storage/advance menu/tick usb mass storage
nitinvaid said:
in setting/storage/advance menu/tick usb mass storage
Click to expand...
Click to collapse
system settings-->storage i see no advance menu only data available for internal storage and apps using space..
there is only one option "Erase SD card"
"Advance menu" is hardware menu key.
przemcio510 said:
"Advance menu" is hardware menu key.
Click to expand...
Click to collapse
yeah i am aware..the hardware key on the left when pressed does not respond and doesnot give me any option
is it a bug?
ankscorek said:
is it a bug?
Click to expand...
Click to collapse
try the solution in the link and see if it wrks for u
USB Mass Storage.Apk
su
setprop persist.sys.usb.config mass_storage,adb
reboot
ty sun90 the link worked...
please przemcio amplify the location of persist.sys.usb.config
it looks like a permanent so9lution
ankscorek said:
hello friends
can some one please point me to a thread link or something that helps me in Enabling Mass Storage on my device which is rooted and flashed with jelly bean
Click to expand...
Click to collapse
Go to settings>Storage>menu key>USB mode> Choose Mass Storage
I had this "problem" before
In Jelly Bean 4.1.2:
Settings/More settings/USB utilities/Connect storage to PC
There is no way in Storage to select something with the menu key
cpl.Bower said:
In Jelly Bean 4.1.2:
Settings/More settings/USB utilities/Connect storage to PC
There is no way in Storage to select something with the menu key
Click to expand...
Click to collapse
Dude..which ROM are you on?
I am on Stock XXELL4 and I cant see "USB Utilities" on "More Settings"
Did you install any mod?
msri3here said:
Dude..which ROM are you on?
I am on Stock XXELL4 and I cant see "USB Utilities" on "More Settings"
Did you install any mod?
Click to expand...
Click to collapse
he already mentioned that he is on Jelly Bean 4.1.2
this is available in Jelly Bean 4.1.2 stock XXLSJ
Jelly Bean 4.2.1 [CM 10.1] and Enabling Mass Storage
ankscorek said:
hello friends
can some one please point me to a thread link or something that helps me in Enabling Mass Storage on my device which is rooted and flashed with jelly bean
Click to expand...
Click to collapse
Look in to this...
http://forum.xda-developers.com/showpost.php?p=29949177&postcount=63213
Sun90 said:
try the solution in the link and see if it wrks for u
USB Mass Storage.Apk
Click to expand...
Click to collapse
Just in case this wasn't seen before, as I already commented on the thread mentrioned here, I'd thought to let people know that Webroot SecureAnywhere found the file installs com.teampassion.stunner.UsbMassStorage, which contains a variant of android.sms.fakeinst trojan!!!
Anyway, none of the solutions here worked, but I finally found two solutions that do under Jelly Bean 4.1.2:
1 - Multi Mount SD Card, the latest version supposedly does not require root, it uses a widget, some features require purchase of the pro version.
2 - SGS3 Easy UMS from right here, requires Root and BusyBox Installer and is freeware/donationware
In both cases, only the external SDCard is accessible. Although the internal memory also shows as a drive, it is NOT accessible by the PC.
To me, however, it finally permits me to do some real file system work and very speedy direct file transfers without date corruption like what happens using the MTP.
przemcio510 said:
su
setprop persist.sys.usb.config mass_storage,adb
reboot
Click to expand...
Click to collapse
Thank you so much for this, przemcio510! After applying this, now when I plug in the USB cable the option to connect a USB mass storage device automatically pops up like it did with previous versions (like JB 4.2.1 even). Before this, nothing would work. I tried selecting the newly-repositioned option under Storage, click Options button, USB connection options, but every time I actually plugged in a USB cable it would automatically revert to the far-inferior media connection option.
I should add that you need to make sure USB Debugging is turned on first BEFORE entering this line of code.
As a note to others who are questioning the need for USB Mass Storage connectivity, besides the significant speed boost (and the fact that Windows actually treats it as a storage device, can give you a measurement of speed and progress, it acts just like a hard drive, etc.), I found there WERE problems with using MTP, primarily that Windows was unable to see all the actual data files in certain Android folders. I wanted to copy over some backups I did using clockworkmod to my home server, and Windows could not SEE half of them! Very strange.
btw I am running JellyBAM 6.5 (JB 4.2.2). This was my only real issue with that otherwise-magnificent ROM, but it sounds like it is some kind of JB 4.2.2 bug.
przemcio510 said:
su
setprop persist.sys.usb.config mass_storage,adb
reboot
Click to expand...
Click to collapse
Hello, I'm having a similar problem connecting. can someone talk me through how to enter this code? I recently rooted my phone to 4.2.2 but I'm new to this. Thanks.
mistystorm said:
Hello, I'm having a similar problem connecting. can someone talk me through how to enter this code? I recently rooted my phone to 4.2.2 but I'm new to this. Thanks.
Click to expand...
Click to collapse
You would need to have a app that allows you access to superuser and that can input command scripts,
or you can simply download "terminal emulator" from the Playstore.
After this, type in exactly what is quoted above.
Note:
You need to have Root access, to check if you do, after you type in "su" into the terminal emulator, the sign "$" show switch to "#" on the following line after you entered the code.
This method works for some devices, but not other all other ones.
Hope this helps.
przemcio510 said:
su
setprop persist.sys.usb.config mass_storage,adb
reboot
Click to expand...
Click to collapse
You, sir, are a kind soul.
Is this a "permanent" fix or is it an operation that has to be performed each time? How is it reveresed? Thanks!
Hello there,
I just registered on this forum to hopefully resolve my problem with the Kobo Arc tablet. I apologize if any similar issue regarding this was posted. So basically, my Uncle bought me a Kobo Arc tablet about 2 months ago and I know quite alot of things about it. Due to my stupidity I couldn't play a game I really wanted to and so I edited my build.prop to make my tablet compatible with the game. In build.prop I changed the product model to: "GT-I9100", product brand to: "Samsung" and product manufacture to: "unknown". After this I restarted my device. As I did, the kobo arc logo appeared and then a never ending start-up boot. I restarted my device many times but still couldn't get my device to fully on. I entered recovery mode by holding the up volume and power button together and tried to reset to factory, but my Kobo Arc just still won't go pass the never ending start-up screen. I even tried to connect it to my computer but it doesn't recognize it. I'm assuming it's bricked, is there any possible fix for this? if so I need to know asap.
Someone please help me, it would be so kind, and I'll appreciate it soo much.
Thanks in advance
SmootZ
Please, I'm in urgent need of help. I really want to go on my tablet again..
Any help to get my kobo arc to its original state and working properly again, I would be sooo grateful.
Do you have a nandroid backup? If so, restore it.
Otherwise, do you still have access to your SD card (probably using an adapter and connecting it to your PC)? Try using AROMA FM to edit build.prop to the original values.
If not, I'd suggest installing ADB (GIYF) and using that to edit build.prop.
For the last two solutions, you'll need to use the shell, and use a text editor such as nano, pico or vi (depending on what's available). BTW, how did you edit build.prop?
You can also flash back stock/any ROM. Restoring to factory settings doesn't restore build.prop AFAIK.
EDIT: Just noticed your PC doesn't recognize your phone. That rules out solution #3. Are you sure the required drivers installed on your PC?
Yes, I'm sure. But when I plug my tablet into my PC through my usb cable it makes a noise connoting its connected but it won't appear.
Could you possibly give me instructions on how to do a nandroid back-up or something that will get my device back with the following condition:
-My device not able to be recognized on my computer
EDIT: When I connect my device to my computer it charges, but it won't appear on my computer or anything, if this helps.
It's too late to make a nandroid backup now. Try using AROMA FM.
GermainZ said:
It's too late to make a nandroid backup now. Try using AROMA FM.
Click to expand...
Click to collapse
Could you possible give any instructions, I'm kinda new to this stuff.
SmootZ said:
Could you possible give any instructions, I'm kinda new to this stuff.
Click to expand...
Click to collapse
Click the link I posted.
Read the first few posts in full.
Ask about the specific part you don't understand.
I cannot even access my device apart from putting it in recovery mode since my device gets stuck at the start-up and loops, In addition I don't know how to access my sd card since my computer doesn't recognize my device as I said. Will this be a problem?and can I still do it?How do I access my sd card?
Sorry if this question seems stupid
Is your device still not detected in recovery mode?
To access your SD card directly from your PC you'll need a special reader/adapter.
Nope, it doesn't recognize it even in recovery mode. What is this "special" reader/adapter and where can I get it? Could you provide me a link or something?
Well, I'm out of ideas. Just Google "SD card adapter".
Actually my device does not offer any external memory card slot. Meaning There is no support for MicroSD or SD cards on my Kobo Arc.
What shall I do now?
Hey Germain or anyone else,
Is there any other possible way I can unbrick my tablet from this? Any solution would be grateful.
SmootZ said:
Hey Germain or anyone else,
Is there any other possible way I can unbrick my tablet from this? Any solution would be grateful.
Click to expand...
Click to collapse
I'm out of ideas you could try yourself. I'd try triple checking the drivers on your PC and see if you can get ADB to work.
Is sending your tablet to repair an option?
EDIT: Can't you update to the latest update using fastboot?
Hey.
First of all, messing with build.prop without backup wasn't the brightest idea in your life, but crap happens, like Forrest Gump used to say.
What is the exact model of your tablet? Kobo Arc? Kobo Arc 10 HD? Maybe Kobo released an update and you can update it directly by fastboot.
If not try to use Linux as it handles ADB much better than Windows, go to system and edit you build.prop back and wipe cache and dalvik cache. You need to have a working ADB to even think about reversing your changes.
Good luck.
Well thanks for the help.
Can I try taking this adb method without my device giving permissions for USB debugging? Since I haven't enabled this in my developer options as far as I know, in addition I cannot really check since my device is bricked but I'm 100% sure it's NOT enabled. Will this stop me from carrying an ADB method?