I have tried searching forums here and google and am just running in circles with same solutions to every problem except mine, the few times I HAVE seen a problem similar to mine, it has been added to an existing fix and no answer posted.
I have an old NC (stock 1.0.1) and quite a while ago i put a new honeycomb rom on it that worked great for a few days, then black screen. following various guides here I have seen the "need to update CWM" and all the like, but here is what I have and the problem:
I have CWM 3.2.0.1, I have tried a variety of restore to stock and custom roms, but it doesn't seem to matter what i add to the sdcard after writing the CWM image because no matter what I do (tried TWRP and got same results) I always get the following errors:
Turn on while plugged in with sdcard in --
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
When I try to follow directions found in one thread to format data and system --
Formatting /data...
Error formatting /data!
Formatting /system...
Error formatting /system!
When I try to mount sdcard --
Error mounting /sdcard!
When I try to mount USB --
E:Unable to write to ums lunfile (No such file or directory)
I am able to see the device with cmd adb devices...it gives me a bunch of 0's instead of the actual s/n and says "recovery" at the end of that line.
Have i managed to completely brick a NC or is there a way to fix this? I have learned quite a bit since I decided to try and fix the black screen, but nothing I have found has given me a solution to this.
I appreciate you guys being here and thanks in advance for any help you may have!
**UPDATE** 06/18/2012
by following this ( http://forum.xda-developers.com/showthread.php?t=919353 ) guide, i am able to get some result with sudo:
Code:
[email protected]:~$ sudo android-sdk-linux/platform-tools/adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
0000000000000000 recovery
Then I try entering the quoted commands and even attempt to edit them, but the result sucks:
Code:
[email protected]:~$ dd if=/sdcard/boot.img of=/dev/block/mmcblk0p1
dd: opening `/sdcard/boot.img': No such file or directory
[email protected]:~$ sudo android-sdk-linux/platform-tools/adb shell
~ # dd if=/sdcard/boot.img of=/dev/block/mmcblk0p1
dd: can't open '/sdcard/boot.img': No such file or directory
~ # dd if=/boot.img of=/dev/block/mmcblk0p1
dd: can't open '/boot.img': No such file or directory
~ # dd if=/sdcard/system.img of=/dev/block/mmcblk0p5
dd: can't open '/sdcard/system.img': No such file or directory
the reason for this is that I can't mount the sdcard. if i could mount the sdcard, then this would be an easy fix and i never would have posted in the first place. using CWM 3.2.0.1 in place of nookie froyo since EVERY link for nookie froyo i have found has been a dead link or the instructions require mounting the sdcard which is the problem i am having. Also, CWM 3.2.0.1 and TWRP 3.2.0.1 or older are the ONLY things that actually allows the NC to turn on.
XSmoky said:
I have tried searching forums here and google and am just running in circles with same solutions to every problem except mine, the few times I HAVE seen a problem similar to mine, it has been added to an existing fix and no answer posted.
I have an old NC (stock 1.0.1) and quite a while ago i put a new honeycomb rom on it that worked great for a few days, then black screen. following various guides here I have seen the "need to update CWM" and all the like, but here is what I have and the problem:
I have CWM 3.2.0.1, I have tried a variety of restore to stock and custom roms, but it doesn't seem to matter what i add to the sdcard after writing the CWM image because no matter what I do (tried TWRP and got same results) I always get the following errors:
Turn on while plugged in with sdcard in --
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
When I try to follow directions found in one thread to format data and system --
Formatting /data...
Error formatting /data!
Formatting /system...
Error formatting /system!
When I try to mount sdcard --
Error mounting /sdcard!
When I try to mount USB --
E:Unable to write to ums lunfile (No such file or directory)
I am able to see the device with cmd adb devices...it gives me a bunch of 0's instead of the actual s/n and says "recovery" at the end of that line.
Have i managed to completely brick a NC or is there a way to fix this? I have learned quite a bit since I decided to try and fix the black screen, but nothing I have found has given me a solution to this.
I appreciate you guys being here and thanks in advance for any help you may have!
Click to expand...
Click to collapse
Look in my tips thread linked in my signature. There is an updated CWM SD listed there. Try using that. Read items A8 and A10.
Edit: I suspect your internal partitions are somehow corrupted. Search the threads for references to restoring stock partitions.
leapinlar said:
Look in my tips thread linked in my signature. There is an updated CWM SD listed there. Try using that. Read items A8 and A10.
Edit: I suspect your internal partitions are somehow corrupted. Search the threads for references to restoring stock partitions.
Click to expand...
Click to collapse
Ok, first of all, thanks for the fast reply. Second, with CWM 3.2.0.1, I can see the CWM menus and navigate them, however, with the 5.5.0.4 I am left with the black screen. I have so far attempted including restore zips and nothing but the 5.5.0.4 with no success.
I believe that somehow, with all my attempts to fix, the internal may be completely wiped, but I still find it strange that from a NC I can only use the 3.2.0.1 or older CWM or TWRP to get anything besides a black screen.
XSmoky said:
Ok, first of all, thanks for the fast reply. Second, with CWM 3.2.0.1, I can see the CWM menus and navigate them, however, with the 5.5.0.4 I am left with the black screen. I have so far attempted including restore zips and nothing but the 5.5.0.4 with no success.
I believe that somehow, with all my attempts to fix, the internal may be completely wiped, but I still find it strange that from a NC I can only use the 3.2.0.1 or older CWM or TWRP to get anything besides a black screen.
Click to expand...
Click to collapse
I suspect the 5.5.0.4 did not get burned properly and it is not trying to boot from it. It just is still trying to boot emmc which is corrupt. But I'm not sure that it would have done you any good anyway. Like I said in my edit above, I think you need to somehow rebuild your partitions. And that means more than just trying to flash a stock ROM. You have to find a thread that tells you how to use adb to rebuild the partitions.
leapinlar said:
I suspect the 5.5.0.4 did not get burned properly and it is not trying to boot from it. It just is still trying to boot emmc which is corrupt. But I'm not sure that it would have done you any good anyway. Like I said in my edit above, I think you need to somehow rebuild your partitions. And that means more than just trying to flash a stock ROM. You have to find a thread that tells you how to use adb to rebuild the partitions.
Click to expand...
Click to collapse
I used win32diskimager and received no error messages, so i guess it was the long shot.
I have been digging through all kinds of recover partitions threads but have thus far been plagued by dead links. My searches for adb partitioning keeps showing me recovery zips that I have already tried multiple times. Atm I am working on IOMonster's method, but have my doubts.
I will post results and if I manage to find an ADB guide, I will link it or repost it with citations and keywords to make it easier to find
XSmoky said:
I used win32diskimager and received no error messages, so i guess it was the long shot.
I have been digging through all kinds of recover partitions threads but have thus far been plagued by dead links. My searches for adb partitioning keeps showing me recovery zips that I have already tried multiple times. Atm I am working on IOMonster's method, but have my doubts.
I will post results and if I manage to find an ADB guide, I will link it or repost it with citations and keywords to make it easier to find
Click to expand...
Click to collapse
No error messages and being able to read in your PC does not necessarily mean it will boot from it.
But like I said, I'm not sure it would have helped you anyway. Did you look at this thread?
http://forum.xda-developers.com/showthread.php?p=25433167
Your problem is that your partitions have gotten corrupted.... you will need to dd some img's back to the nook... I have all of them available... but for /dev/block/mmcblk0p2 and 0p3 you will need to do some editing... since they are device specific.
If you're lucky... /dev/block/mmcblk0p3 is still "normal" and the device can recover 0p2 from the rombackup.zip on there... if not... editing is in your future.
Anyway... if you need the img files... I can make them available... have helped a few out with this problem.
Thanks guys, I'm gonna dual boot linux and get to work on the harder to do things now, but with my kids running around it'll take me some time to do.
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A
lufc said:
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A
Click to expand...
Click to collapse
Thought i was in the right place given other similar issues posted in same area, thanks for putting me in the right place.
****Moderator please delete this extra post****
So I was randomly flying around on Google today, and I noticed that someone had claimed to root the Kobo Arc, and gave written instructions here -- http : // www . mobileread . com / forums / showthread.php?p=2584491 (Remove the spaces, XDA won't let me post an actual link, since I don't have 10 posts yet). After running through this myself, I went on the Google Play store and used root checker. Much to my surprise, it worked, and my device now has root access. I even tested with Root Explorer, and mounted the system partition as R/W, and I can move things in and out of it. I'm currently working on trying to get a custom ROM working, but I'm worried that I will cause a brick, since Cyanogen doesn't support the Arc. (yet...)
ThunderBird2678 said:
So I was randomly flying around on Google today, and I noticed that someone had claimed to root the Kobo Arc, and gave written instructions here -- http : // www . mobileread . com / forums / showthread.php?p=2584491 (Remove the spaces, XDA won't let me post an actual link, since I don't have 10 posts yet). After running through this myself, I went on the Google Play store and used root checker. Much to my surprise, it worked, and my device now has root access. I even tested with Root Explorer, and mounted the system partition as R/W, and I can move things in and out of it. I'm currently working on trying to get a custom ROM working, but I'm worried that I will cause a brick, since Cyanogen doesn't support the Arc. (yet...)
Click to expand...
Click to collapse
confirmed, was just going to post this but was beaten to it.
http://www.mobileread.com/forums/showthread.php?t=218928
ive attached the file but please go to that website and pay homage to whoever did this work...now to the next stop, a ROM
Device now has a working custom recovery see post 15
Sent from my Arc using xda app-developers app
dazza9075 said:
confirmed, was just going to post this but was beaten to it.
http://www.mobileread.com/forums/showthread.php?t=218928
In terms of a ROM do we not need a compatible boot loader that will allow unsigned ROMs?
ive attached the file but please go to that website and pay homage to whoever did this work...now to find a man about a ROM
Sent from my Arc using xda app-developers app
Click to expand...
Click to collapse
i have absolutely no idea what im doing but I think I have dumped 12 partitions using
dd if=/dev/block/mmcblk0p10 of=/sdcard/p10.img
is there anyone around that fancies a challenge? im in a position where bricking this thing isn't really much of a problem so if someones up for a challenge and wants to help im willing to lend myself and the device to this
Warning : Block of Text Ahead.
dazza9075 said:
confirmed, was just going to post this but was beaten to it.
In terms of a ROM do we not need a compatible boot loader that will allow unsigned ROMs?
ive attached the file but please go to that website and pay homage to whoever did this work...now to find a man about a ROM
Sent from my Arc using xda app-developers app
Click to expand...
Click to collapse
Haha. As soon as I found a thread called "root the Kobo Arc" on Google, I posted it here right away. Sorry if I deprived you of the satisfaction! *troll*
Joking aside, I'm not too sure about the bootloader. I think it's pretty locked down (since I put a nexus 7's cyanogenmod onto the data partition and rebooted. It tried to updated, but said validation failed, or something of that sort). I can't install any custom recoveries either, since I have no idea how to do it in the first place, and there's none made for the Arc.
Also, I analyzed the Arc with the "Droid Examiner" App from the play store (That is a really great app, just so you know), and found that it uses a board called "zeus". The funny thing, though, is that one of Sony's Xperia phones, also has a board called "Zeus", and there's Cyanogenmod for that (albiet not the latest version). However, these two devices have nothing in common. The closest thing to an Arc that has Cyanogenmod is the Nook HD/HD+, which uses the exact same chip (OMAP TI 4470).
If someone is smart enough (not me) to analyze the Cyanogenmod files for the Nook, and see how they work, that may lead into flashing the Arc.
Anyway, I'm resetting the Arc, since I'm having weird cases where the Arc would freeze after booting it from sleep mode, and I'd have to turn it off and on again. I think that was something else I did, since it happened before the root, but neh, I might as well try this all from factory default settings.
Sorry for the block of text, guys!
P.S. Using the stock Jelly Bean boot animation on the Arc looks amazing!:laugh:
Haha, its cool, like yourself I just happened to Google kobo arc root and for once my googe fu was up to the task and the root appeared
I've been looking at starting my own recovery mod branch but its no simple task by the looks of it, if their are similar devices we can use all their data and tweak it to ours which would help a lot!
Oh I think we have fast boot, I held vol down and pushed power on, it just sat at the kobo arc screen, I used the nexus 7 driver from the universal adb/fastboot driver I found on here and it connected up http://forum.xda-developers.com/showthread.php?t=2263822
I stumbled on some to good to be true program on Xda dev that apparently can root anything and unlock any bootloader once your in fastboot mode. I have tried that part and it said it was successful but i have no idea how to test this out yet, the program does a bunch of other stuff too, the adb stuff worked as did apk sending, and the rooting options knew i was rooted, it also has flashing functions, I'll be damed if I can find it now I'm at home though , I'll have another look.
I don't mind doing leg work but if someone can read the map it would be very helpful!
Edit, found it
http://forum.xda-developers.com/showthread.php?t=2399385
http://www.mediafire.com/?vwxpq62pa927s9c
Sent from my Arc using xda app-developers app
dazza9075 said:
Haha, its cool, like yourself I just happened to Google kobo arc root and for once my googe fu was up to the task and the root appeared
I've been looking at starting my own recovery mod branch but its no simple task by the looks of it, if their are similar devices we can use all their data and tweak it to ours which would help a lot!
Oh I think we have fast boot, I held vol down and pushed power on, it just sat at the kobo arc screen, I used the nexus 7 driver from the universal adb/fastboot driver I found on here and it connected up http://forum.xda-developers.com/showthread.php?t=2263822
I stumbled on some to good to be true program on Xda dev that apparently can root anything and unlock any bootloader once your in fastboot mode. I have tried that part and it said it was successful but i have no idea how to test this out yet, the program does a bunch of other stuff too, the adb stuff worked as did apk sending, and the rooting options knew i was rooted, it also has flashing functions, I'll be damed if I can find it now I'm at home though , I'll have another look.
I don't mind doing leg work but if someone can read the map it would be very helpful!
Edit, found it
http://forum.xda-developers.com/showthread.php?t=2399385
http://www.mediafire.com/?vwxpq62pa927s9c
Sent from my Arc using xda app-developers app
Click to expand...
Click to collapse
Um... Okay. I've installed the drivers (I think I installed them correctly), and I booted my device using "volume down + power". I have it connected to my System, but whenever I try to use one of the options in the Android Root Toolkit, it tells me it's waiting for the device. I don't know what I did wrong, but something's clearly not working.
As far as the recovery goes, I think that looking at the Nook Tablet from TWRP would work quite nicely. It runs on a similar processor ( I believe it's a OMAP TI 4430 ), and it seems to be quite similar in specs to the Arc. If only I was a bit better at programming...
ThunderBird2678 said:
Um... Okay. I've installed the drivers (I think I installed them correctly), and I booted my device using "volume down + power". I have it connected to my System, but whenever I try to use one of the options in the Android Root Toolkit, it tells me it's waiting for the device. I don't know what I did wrong, but something's clearly not working.
As far as the recovery goes, I think that looking at the Nook Tablet from TWRP would work quite nicely. It runs on a similar processor ( I believe it's a OMAP TI 4430 ), and it seems to be quite similar in specs to the Arc. If only I was a bit better at programming...
Click to expand...
Click to collapse
im usig the generic android adb driver and the bootloader driver for fast boot
im dumped all partitions and mapped them all out, see below for file system details
But again I'm blindly stabbing in the dark and most tutorials are a bit lacking in depth or not relevant to the kobo :/
Sent from my Arc using xda app-developers app
127|[email protected]:/ # blkid
/dev/block/dm-2: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/dm-1: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/dm-0: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p12: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p11: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p10: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p4: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
[email protected]:/ #
Okay, so I can't even push apps to the Arc using ADB. I think you have to boot into recovery (power + volume up). I don't know how to use the terminal at all (I'm lost, I know D: ), so I don't have that installed on the Arc. I remember being able to do ADB even with my Sony Reader (First gen, PRST1), so I'm not sure why the Arc isn't quite working. I have both drivers installed, BTW.
As for the recovery, I can't even find a method to flash it. I'm still trying everything I can, though. :\
Sent from my Arc using xda app-developers app
ive mapped out the following partitions and any info ive found about each of them, im not in a position to help at the moment, got a big day at work tomorrow, as mentioned above ive used several tools,
SuperSU,
ROM toolbox pro
busybox
remount
Below is a list of all the available partition names and numbers
/dev/block/mmcblk0p1 xloader
/dev/block/platform/omap/omap_hsmmc.1/by-name/xloader
348KB
/dev/block/mmcblk0p2 bootloader
/dev/block/platform/omap/omap_hsmmc.1/by-name/bootloader
1.50MB
/dev/block/mmcblk0p3 cypto
/dev/block/platform/omap/omap_hsmmc.1/by-name/crypto
Completely empty
64KB partition size
/dev/block/mmcblk0p4 EFS
Mounted as /FACTORY
/dev/block/mmcblk0p4:UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/platform/omap/omap_hsmmc.1/by-name/efs /factory ext4 ro,relatime,barrier=1,data=ordered 0 0
20MB
/dev/block/mmcblk0p5 misc
/dev/block/platform/omap/omap_hsmmc.1/by-name/misc
Completely empty
128KB partition size
/dev/block/mmcblk0p6 Bootlogo
/dev/block/platform/omap/omap_hsmmc.1/by-name/bootlogo
Contains kobo arc picture
4MB partition size
/dev/block/mmcblk0p7 Logos
/dev/block/platform/omap/omap_hsmmc.1/by-name/logos
contains the battery charge logo
28MB partition size
/dev/block/mmcblk0p8 recovery
/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery
data contains a GZ file, when decompressed we get a 8.5MB file of unknown type, exact same as in boot
5MB of data
16MB partition size
/dev/block/mmcblk0p9 boot
/dev/block/platform/omap/omap_hsmmc.1/by-name/boot
data contains a GZ file, when decompressed we get a 8.5MB file of unknown type, exact same as n recovery
4.5MB of data
8MB partition size
/dev/block/mmcblk0p10 CACHE
Mounted as /CACHE
/dev/block/mmcblk0p10: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/platform/omap/omap_hsmmc.1/by-name/cache /cache ext4
rw,nosuid,nodev,noatime,errors=panic,barrier=1,nom blk_io_submit,data=ordered 0
0
768MB partition size
/dev/block/mmcblk0p11 SYSTEM
Mounted as /SYSTEM
/dev/block/mmcblk0p11: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/platform/omap/omap_hsmmc.1/by-name/system /system ext4
rw,relatime,barrier=1,data=ordered 0 0
910MB partition size
/dev/block/mmcblk0p12 USERDATA
Mounted as /DATA
/dev/block/mmcblk0p12: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/platform/omap/omap_hsmmc.1/by-name/userdata /data ext4
rw,nosuid,nodev,noatime,errors=panic,barrier=1,nom blk_io_submit,data=ordered 0
0
12GB partition size
Watching with interest. The root works. No frills CPU installed and working. There may be hope for this thing yet:good:
Moved to new thread and more appropriate forum - keep up the good work guys
im not sure that's going to work you know, ive had some permission errors with adb which suggests the root isn't full, terminal on the device works fine, but adb just has some problems, adb shell and the su seems to fix them.
http://www.gadgetsdna.com/android-terminal-adb-shell-command-list/1168/
http://www.addictivetips.com/android/make-nandroid-backups-on-android-without-booting-into-recovery/
im busy today but ive found these useful
i think Clockwork Recovery should be our focus at this point or if you have dumped your partitions(?) attempt to construct a rom for later use
or this should work too
Install any Custom Recovery with flash_image:
Just like the previous method, this method also requires following advanced steps and is not recommended if the first method is working for you. flash_image is a tool for Android devices that lets you rewrite your phone’s system partitions with partition image files and installing it to your device requires ADB. If you don’t already have ADB installed, check out our guide on installing ADB. Once you have ADB installed, flash the custom recovery image as follows:
WARNING: It is very important that the recovery image that you use in this method is compatible with your device. Else it will not work and flashing it could possibly brick your device.
Download flash_image and extract it from the zip file to a location on your computer. We extracted it to the main C drive (not in any folder) and will use that in the next steps.
Copy the recovery image for your phone to a convenient location on your computer, preferably with a short path. We will be placing it on the C Drive directly (not in any folder) and using that in the next steps.
Note: The recovery image should have .img extension. If it is in a zip file, extract the .img file from it.
Enable USB debugging mode on your device from Menu > Settings > Applications > Development.
Connect your device to your computer via USB.
Open a Command Prompt window on your computer and enter the following commands: adb push c:\flash_image /sdcard/adb push c:\recovery.img /sdcard/adb shellsumount -o remount, rw /systemcp /sdcard/flash_image /system/bincd /system/binchmod 777 flash_imageflash_image recovery /sdcard/recovery.imgThis will first transfer flash_image and recovery.img to your phone. Then it will copy flash_image to the /system/bin folder of your Android device and make it executable. Finally, it will flash the custom recovery image to your device using flash_image.
Note that we used c:\flash_image and c:\recovery.img in the first two lines as we had these files extracted at the root of our C drive. If you extracted the files elsewhere, use the appropriate paths and if your recovery image has a different name, use the appropriate name.
Reboot your device once the process is finished and you’re done. You may exit adb and the Command Prompt window on your computer by entering ‘exit’ thrice.
dazza9075 said:
im not sure that's going to work you know, ive had some permission errors with adb which suggests the root isn't full, terminal on the device works fine, but adb just has some problems, adb shell and the su seems to fix them.
http://www.gadgetsdna.com/android-terminal-adb-shell-command-list/1168/
http://www.addictivetips.com/android/make-nandroid-backups-on-android-without-booting-into-recovery/
im busy today but ive found these useful
i think Clockwork Recovery should be our focus at this point or if you have dumped your partitions(?) attempt to construct a rom for later use
or this should work too
Install any Custom Recovery with flash_image:
Just like the previous method, this method also requires following advanced steps and is not recommended if the first method is working for you. flash_image is a tool for Android devices that lets you rewrite your phone’s system partitions with partition image files and installing it to your device requires ADB. If you don’t already have ADB installed, check out our guide on installing ADB. Once you have ADB installed, flash the custom recovery image as follows:
WARNING: It is very important that the recovery image that you use in this method is compatible with your device. Else it will not work and flashing it could possibly brick your device.
Download flash_image and extract it from the zip file to a location on your computer. We extracted it to the main C drive (not in any folder) and will use that in the next steps.
Copy the recovery image for your phone to a convenient location on your computer, preferably with a short path. We will be placing it on the C Drive directly (not in any folder) and using that in the next steps.
Note: The recovery image should have .img extension. If it is in a zip file, extract the .img file from it.
Enable USB debugging mode on your device from Menu > Settings > Applications > Development.
Connect your device to your computer via USB.
Open a Command Prompt window on your computer and enter the following commands: adb push c:\flash_image /sdcard/adb push c:\recovery.img /sdcard/adb shellsumount -o remount, rw /systemcp /sdcard/flash_image /system/bincd /system/binchmod 777 flash_imageflash_image recovery /sdcard/recovery.imgThis will first transfer flash_image and recovery.img to your phone. Then it will copy flash_image to the /system/bin folder of your Android device and make it executable. Finally, it will flash the custom recovery image to your device using flash_image.
Note that we used c:\flash_image and c:\recovery.img in the first two lines as we had these files extracted at the root of our C drive. If you extracted the files elsewhere, use the appropriate paths and if your recovery image has a different name, use the appropriate name.
Reboot your device once the process is finished and you’re done. You may exit adb and the Command Prompt window on your computer by entering ‘exit’ thrice.
Click to expand...
Click to collapse
I've already tried that recovery method (I spent about two hours just googling), and it doesn't work with the Arc. The ADB won't let me push the image over.
As for Cyanogenmod, I tried something yesterday. A person on the Mobileread forums (apparently a Kobo employee) put out an update.zip file for the Kobo Arc. The file was quite old, and it's really just the 4.1.1 update that (I hope) we're all running. He said that as long as you put it on the root of the data partition, the Arc will flash it immediately. When I tried taking a Nexus 7's Cyanogenmod file and sticking it in the same place, the Arc started flashing it, but then just said there was an error with the update. So I personally think that you do require a properly signed ROM.
However, if you open up Kobo's update.zip using Winrar, a sidebar pops up that says "signed by SignApk". I don't know too much about this, but couldn't we use this "signapk" to sign our own ROMS and flash them?
Just a thought.
ThunderBird2678 said:
As for Cyanogenmod, I tried something yesterday. A person on the Mobileread forums (apparently a Kobo employee) put out an update.zip file for the Kobo Arc. The file was quite old, and it's really just the 4.1.1 update that (I hope) we're all running. He said that as long as you put it on the root of the data partition, the Arc will flash it immediately. When I tried taking a Nexus 7's Cyanogenmod file and sticking it in the same place, the Arc started flashing it, but then just said there was an error with the update. So I personally think that you do require a properly signed ROM.
However, if you open up Kobo's update.zip using Winrar, a sidebar pops up that says "signed by SignApk". I don't know too much about this, but couldn't we use this "signapk" to sign our own ROMS and flash them?
Just a thought.
Click to expand...
Click to collapse
I think there is a problem with the setup, I just flashed a CW recovery image and it worked, or didn't rather! but the concept did, transferred, flashed using adb, I had to replace it though as it was totally borked and kept restarting, apparently the touch based recovery methods can be like that, ill have some good time tomorrow night (UK time) if your about, and ill keep at it tonight if I get a chance!
copy recovery to adb location
adb push recovery.img /sdcard/
adb shell
su
cat /sdcard/recovery.img > /dev/block/platform/omap/omap_hsmmc.1/by-name/recovery
exit adb shell and type
adb reboot recovery
fixed it by holding power button and vol down to boot to fastboot recovery
then ran
fastboot flash recovery inputrecovery.img
inputrecovery being my original recovery file taken from partition 8!
ive updated the partition map on the post above with my progress, but it looks like we can flash to them my name so its probably less relevant now
oh ive ditched the drivers I was using and reinstalled the drivers from the official SDK, generic android adb for within android and android bootloader for fastboot
EDIT
Yaaas!! recovery replaced
ok, deleting or renaming /etc/install-recover.sh appears to have stopped custom recovery being changed back to stock after reboot, I used the recovery builder to make a build from partition 8, which it did without error, flashed using the above commands.
Still don't know what im doing though, but progress is progress
ill post a link to the custom recovery ive made soon, we need to make up some fstab file listing all the mounts etc, i tried one but it must be borked as recovery couldnt see anything
ok i have a working recovery http://jenkins.cyanogenmod.com/job/recovery/35325/artifact/
its not quite done, i need to mount the sdcard, its physical location is mounted, ie /data, but its virtual mount isn't /storage/sdcard
I have asked for some help so hopefully someone can help be on this, I think it needs to be symlinked
im going to need some help soon, so if your reading this with a kobo arc, I need you! im needing a hand folks! if your stuck getting this far let me know and we can PM to get it working
oh and recovery is also now persistant by deleting or renaming /etc/install-recover.sh"
Sorted folks!
I have made a stable and thus far, a working custom recovery.
its mounting everything and backing up / restoring works as it should, unless anyone can find any issues I consider this step in building a complete ROM completed,
you must have root, download arctic.apk and install on your tablet, you will need to enable unknown sources In dev options first
you must have android and java sdk also installed, you will need to add the google usb drivers in the android sdk, you will find them in the "extras"
Enable usb debug on the arc and install the generic google adb usb drivers
Delete or rename /etc/install-recover.sh this will make the custom recovery persistent
Copy the recovery.img to the SDCard, either by using drag and drop in windows ( to root of "internal storage") or by adb push, if you use adb push then remember to copy recovery.img to the same folder as adb
adb push recovery.img /sdcard/
The next job is to open up a command window and navigate to adb folder, type the following exactly, even better copy and paste them!
adb shell
su
cat /sdcard/recovery.img > /dev/block/platform/omap/omap_hsmmc.1/by-name/recovery
exit adb shell (ctrl+C) and type
adb reboot recovery
and bobs your uncle, one happy new recovery
Thanks for your hard work. Everything works quite well.
Sent from my Arc using Tapatalk 4
cancuck said:
Thanks for your hard work. Everything works quite well.
Sent from my Arc using Tapatalk 4
Click to expand...
Click to collapse
that's the easy bit, I have a feeling I need to make a couple of changes to the recovery.img but noting major, just a couple of other mounts I may have missed
I probably would like some help with the next bit however.
im just trying to build a development platform, I have a loathing for Linux as a desktop so will need to re educate myself without throwing my laptop out of the window, after that "challenge" the ROM should be easy
Well, I've just done it, and it works. Everything seems to be in order for the time being. I'm going to muck around with the new capabilities, and see what I can do.
Well, first of all.... I made a clean copy of my EFS folder before having this problem but.....using the lovely and simple commands copy and paste and now the files don't have the correct permissions and owners so nothing changes when I copy them back so my question is...
Could you guys please provide me a list with all the N910F EFS files + permissions and owners?
*EDIT*
My IMEI, serial number, baseband..... are all correct.
Thanks:crying:
Have u tried flashing stock rom through odin.Many users have fixed this problem by using the method
Sent from my SM-N910G using XDA Premium 4 mobile app
RISHI RAJ said:
Have u tried flashing stock rom through odin.Many users have fixed this problem by using the method
Sent from my SM-N910G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes, I tried 3 different stock roms, I also downgraded to stock kitkat and then flashed a stock lollipop rom and... same problem.
ANTONIOPS said:
Yes, I tried 3 different stock roms, I also downgraded to stock kitkat and then flashed a stock lollipop rom and... same problem.
Click to expand...
Click to collapse
same problem here also, except, i have original imei intact and can make calls, send sms etc. flashed original firmware through odin and through kies, no luck, efs file 0mb. I have lost finger print scan and my serial number is wrong.
I had a similar problem a while back, came across this info here, the 'dev' files mentioned are for a N910G, just type 'mount' at a terminal to see which 'dev' file the efs partition mounts on. I used Method 1, but Method 2, does essentially the same thing in the end, so which ever you find easiest. Damn saved my phone, I even bought a replacement online before I found this solutionl.
Fix screwed up EFS Partition.
-------------------------------
posted by Steve Lazarus on XDA Dev on 5th October 2013
http://forum.xda-developers.com/showthread.php?t=2471421
(Used METHOD 2 on 09-01-2015, worked a treat, RaSTuS)
(Will try METHOD 1 next time)
METHOD 1
1. Install stock Firmware via Odin then rerun autoroot (to regain root)
2. Install TWRP via Odin, reboot to recovery.
3. Install SuperSU from external SD Card.
4. Do an "adb shell" when phone is in recovery mode to run commands via TWRP.
From the ADB shell: Reset the EFS partition with the following commands:
mke2fs /dev/block/mmcblk0p13 (for N910G Note 4)
mkdir /efs
mount -t ext4 /dev/block/mmcblk0p13 /efs
Do a factory reset, reboot system
Afterwards, no more boot looping, the phone successfully registered on the
mobile network, and my IMEI is there and correct. Seems like the EFS partition
can rebuild itself now I guess...
Gotta love the XDA community !!!
METHOD 2
You can also try just running Commands via TWRP before using Odin to revert to
stock, re-rooting etc..Worked for me while I was doing some restore testing with
Jovy's modded kernel ..Just trying to save you some time..
Using TWRP Terminal Command To Complete this evolution...
1. Reboot to recovery
2. Hit "Advanced" Select "Terminal Command".
3. Hit "Select" (lower right corner) to select root (/) folder.
4. keyboard will open, type in the following commands, make sure you put the
spaces and / where they need to be, it needs to look exactly as outlined.
mke2fs /dev/block/mmcblk0p13 (for N910G Note 4)
Hit Go - The command will run.
Clear the input box, type the following command:
mkdir /efs
Hit Go - The command will run.
Clear the input box, type the following command:
mount -t ext4 /dev/block/mmcblk0p13 /efs
Hit Go - The command will run.
You can now back out of the terminal command, and follow the rest of the
directions.
rastus.rob said:
I had a similar problem a while back, came across this info here, the 'dev' files mentioned are for a N910G, just type 'mount' at a terminal to see which 'dev' file the efs partition mounts on. I used Method 1, but Method 2, does essentially the same thing in the end, so which ever you find easiest. Damn saved my phone, I even bought a replacement online before I found this solutionl.
Fix screwed up EFS Partition.
-------------------------------
posted by Steve Lazarus on XDA Dev on 5th October 2013
http://forum.xda-developers.com/showthread.php?t=2471421
(Used METHOD 2 on 09-01-2015, worked a treat, RaSTuS)
(Will try METHOD 1 next time)
METHOD 1
1. Install stock Firmware via Odin then rerun autoroot (to regain root)
2. Install TWRP via Odin, reboot to recovery.
3. Install SuperSU from external SD Card.
4. Do an "adb shell" when phone is in recovery mode to run commands via TWRP.
From the ADB shell: Reset the EFS partition with the following commands:
mke2fs /dev/block/mmcblk0p13 (for N910G Note 4)
mkdir /efs
mount -t ext4 /dev/block/mmcblk0p13 /efs
Do a factory reset, reboot system
Afterwards, no more boot looping, the phone successfully registered on the
mobile network, and my IMEI is there and correct. Seems like the EFS partition
can rebuild itself now I guess...
Gotta love the XDA community !!!
METHOD 2
You can also try just running Commands via TWRP before using Odin to revert to
stock, re-rooting etc..Worked for me while I was doing some restore testing with
Jovy's modded kernel ..Just trying to save you some time..
Using TWRP Terminal Command To Complete this evolution...
1. Reboot to recovery
2. Hit "Advanced" Select "Terminal Command".
3. Hit "Select" (lower right corner) to select root (/) folder.
4. keyboard will open, type in the following commands, make sure you put the
spaces and / where they need to be, it needs to look exactly as outlined.
mke2fs /dev/block/mmcblk0p13 (for N910G Note 4)
Hit Go - The command will run.
Clear the input box, type the following command:
mkdir /efs
Hit Go - The command will run.
Clear the input box, type the following command:
mount -t ext4 /dev/block/mmcblk0p13 /efs
Hit Go - The command will run.
You can now back out of the terminal command, and follow the rest of the
directions.
Click to expand...
Click to collapse
I tried that and those solutions didn't work because I'm the biggest idiot in this galaxy:laugh:, some time ago I deleted the EFS golden backup in the service menu and I think that's why it didn't rebuild after I erased the main EFS partition but the good thing is that I made a clean backup of it so I can copy the files back to the EFS folder, the thing is that I just copied and pasted them so now all files have root as the owner and I know some of them had system, radio, wifi... as owners but I can't remember which ones, I think I could fix it if I see a list with the files, permissions and owners. Thanks anyway:good::good:
*EDIT*
Oh!! also I forgot to tell you that my imei, baseband, serial number bla, bla, bla are correct.
please help guys i have same problem but my note is n910f
hello ... its my first comment here ... and i whant to ask ...if i have the same phone ...but ... its a n910f ... its working this metods ? please guys i need help ... thx ...
Hi, I have a N910C and my IMEI got changed when i flashed offical lolipop 5.1.1, and now it wont register on any network, the IMEI isn't fake or corrupted i tried imei analyzer and it says its valid but for a 2005 Phone. I tried deleting /efs entirely/ flash diff firmwares / factory reset / clean kies install, nothing worked. my .nv_data.bak/nv_data.bak is missing. Please help
N910F EFS lost
florinhrib said:
hello ... its my first comment here ... and i whant to ask ...if i have the same phone ...but ... its a n910f ... its working this metods ? please guys i need help ... thx ...
Click to expand...
Click to collapse
i'm new too i'm from Algeria, i have a GN4 with no IMEI, i lost the EFS foldier, the wifi and blueth work but no finger print and no health app, please help