Database Users

[BRICKED!] Flashed faulty boot.img to /dev/block/mmcblk0p2 (boot)

Hey guys,
yesterday i flashed a faulty boot.img (own backed kernel) to my iconia, via recovery. to /dev/block/mmcblk0p2
problem now:
i cant get into recovery...
i tried everything, even hard reset...
has somebody got an idea? i also wrote s2ck (?!), i have backups of all stock (including usb id, part table and so on)

can you try installing rom manager? if that doesn't allow you to download the custom CWM for our phones you may be able to place a zip copy of it in the rom manager updates directory for it to flash...
did acer recovery app from the market not work either?

ROM Manager isn't compatible with the A500. Flashing a ROM with it is a good way to get an expensive tea tray.
OP, wait for sc2k to get back to you. He's the only one that can help you.

thumbs up for sp3dev and s2ck.. they helped me!

[WIP] Ideapad K1 CWM recovery port

Greetings,
I am looking for assistance trying to port CWM recovery to the Lenovo K1.
Where I'm At
I have compiled CWM Recovery from the source and have successfully flashed it to the device with working buttons. The recovery can mount all partitions except /misc. I have successfully flashed update.zip's, and verified the files were in place via adb. The problem is once I boot into CWM (Even if I don't flash anything) I cannot boot back to the OS, without reflashing everything
For example:
1. I flash the Chinese rom with my recovery.img in place via nvflash
2. Once it boots I move a blank update.zip & update.xml to the Download dir on the internal storage
3. Reboot
4. Automatically tries to go into Recovery
5. Get an error image (Blank update.zip wouldn't flash of course). Hold down Power Button until device powers off.
6. Power on and device goes right into CWM.
At this point even if I just reboot the device goes right back into CWM. The recovery is very functional, I am able to flash update.zip's, mount almost all partitions, and access via adb.
According to djmwj there needs to be an update.zip and update.xml file in the /sdcard/Download dir to boot into recovery. These can be blank files. They are deleted on every reboot, so you have to put them back each time.
-This only works for me on the Chinese rom
Partitions
/dev/block/mmcblk0p1 - /recovery
/dev/block/mmcblk0p2 - /boot
/dev/block/mmcblk0p3 - /system
/dev/block/mmcblk0p4 - /cache
/dev/block/mmcblk0p5 - ?? 2MB
/dev/block/mmcblk0p6 - blob
/dev/block/mmcblk0p7 - /data
/dev/block/mmcblk0p8 - /data/temp
/dev/block/mmcblk1p1 - /sdcard
recovery.fstab
# mount point fstype device [device2]
/boot mtd /dev/block/mmcblk0p2
/cache ext4 /dev/block/mmcblk0p4
/data ext4 /dev/block/mmcblk0p7 /dev/block/mmcblk0p8
/mis mtd ??
/recovery mtd /dev/block/mmcblk0p1
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/system ext4 /dev/block/mmcblk0p3
/sd-ext yaffs2 ??
Please let me know if you would like a copy of the recovery.img or the modified files from the CWM source. Also if anyone has any suggestions to get it rebooting to the OS. If I can get that working it should be ready for an initial release.

Would this help?
http://rootzwiki.com/topic/13407-alpha-ideapad-k1-cwm-stock-rooted-rom/
He seems to have it flashing and booting a rooted version of the stock rom. He mentions some issues but doesn't list them (unless you count not having lenovo market as an issue.)

I'm waiting for this to root my K1, any update?
---------- Post added at 12:54 PM ---------- Previous post was at 12:53 PM ----------
gallahad2000 said:
Would this help?
http://rootzwiki.com/topic/13407-alpha-ideapad-k1-cwm-stock-rooted-rom/
He seems to have it flashing and booting a rooted version of the stock rom. He mentions some issues but doesn't list them (unless you count not having lenovo market as an issue.)
Click to expand...
Click to collapse
He is actually the same guy.

leo_bsb said:
He is actually the same guy.
Click to expand...
Click to collapse
That's what I get for not paying any attention. I think he's at the same place as everyone else: They've got a rooted rom but need a copy of the userdata img or all of the original .apks to restore all of the third-party apps.
He just posted Alpha 2.0!
*Edit: I helped him pull the lenovo .apks from my stock K1, so there may be another update soon*

I think I can help you. If you want to launch a recovery and you have root(#) then on the Lenovo you just issue this command "/system/bin/misc_command FOTA" and then reboot. It will launch CWM or the stock recovery. No need to make dummy update.zip files.
Take a look at http://forum.xda-developers.com/showpost.php?p=21309379&postcount=50
You should be able to download that tool, replace the recovery.img in the image folder with your CWM and then flash to 13_13_US. You'll have to comment (change) out the boot sequence so CWM doesn't get replaced on reboots. This is why it only works once for you and then you have to flash it again.
Also, if you get root. You should be able to dd back in the recovery blob without flashing which would work for one reboot and then it gets replaced again with stock.
So you could:
1. dd of=/dev/block/mmcblk0p1 if=/sdcard/Download/recovery.img
2. /system/bin/misc_command FOTA
3. reboot
Note: this assumes you have root and should launch CWM for you. However CWM will be replaced back with the stock recovery on the next reboot unless you comment out those commands in the start up.
Hope this helps, let me know,
TD

Thanks, but I already created an app/widget that reboots into recovery. I watched logcat while applying an OTA update to see what intent was called. The app basically puts a blank update.zip in place and calls the intent. This method does not cause you to reflash the recovery image each time. You reboot to recovery as many times as you would like.
All my work is posted over a rootzwiki

khanning88 said:
Thanks, but I already created an app/widget that reboots into recovery. I watched logcat while applying an OTA update to see what intent was called. The app basically puts a blank update.zip in place and calls the intent. This method does not cause you to reflash the recovery image each time. You reboot to recovery as many times as you would like.
All my work is posted over a rootzwiki
Click to expand...
Click to collapse
Nice, got a link for the download of CWM?

timmyDean said:
Nice, got a link for the download of CWM?
Click to expand...
Click to collapse
http://rootzwiki.com/topic/13407-alpha-ideapad-k1-cwm-stock-rooted-rom-111029-build/

[Q] i9505 /system mount trouble

Hi.
I've searched through a LOT of posts, but only found slightly related (and for me unhelpful) comments.
I have a GT-i9505 (i9505xxuame2), and rooted/flashed it using Odin / modified_cf_root. However, although I have succsessfully installed TWRP - AND have (seemingly) been able to make a full backup to my external sdcard, I am completely unable to install CM 10.1 nightly / AOKP (both i9505 versions).
Whenever i try this (via recovery of course), it always fails, reporting it was unable to mount /system. When restarting the phone, it just 'hangs' on the splash screen. The only solution then is to restore my backup, which works fine... HOWEVER, I suspect that since it has problems with the /system folder, It might not actually have backed this up, and that restore only works because /system happens to be untouced by my attempts to flash it.
Trying various tips & tricks found here on XDA - like manually mounting /system in TWRP, reflashing in Odin etc. has not helped me. I also noticed that when entering download-mode, it states that write protection is enabled (as in this thread - which unfortunatly also did not solve my problem: http://forum.xda-developers.com/showthread.php?t=2267107). I also tried CWM, but using this I'm unable to manually mount both /system, /sdcard AND extSdcard (or whatever extrenal memory was called... don't remember.. ) - and it of course has the same problems trying to flash either ROM.
My feeling is that my unit is not (fully) rooted, but like I said, I've been unable to find a solution. I really hope you can help, because I'd love to have CM on this delightful piece of hardware.

Schildkamp said:
Hi.
I've searched through a LOT of posts, but only found slightly related (and for me unhelpful) comments.
I have a GT-i9505 (i9505xxuame2), and rooted/flashed it using Odin / modified_cf_root. However, although I have succsessfully installed TWRP - AND have (seemingly) been able to make a full backup to my external sdcard, I am completely unable to install CM 10.1 nightly / AOKP (both i9505 versions).
Whenever i try this (via recovery of course), it always fails, reporting it was unable to mount /system. When restarting the phone, it just 'hangs' on the splash screen. The only solution then is to restore my backup, which works fine... HOWEVER, I suspect that since it has problems with the /system folder, It might not actually have backed this up, and that restore only works because /system happens to be untouced by my attempts to flash it.
Trying various tips & tricks found here on XDA - like manually mounting /system in TWRP, reflashing in Odin etc. has not helped me. I also noticed that when entering download-mode, it states that write protection is enabled (as in this thread - which unfortunatly also did not solve my problem: http://forum.xda-developers.com/showthread.php?t=2267107). I also tried CWM, but using this I'm unable to manually mount both /system, /sdcard AND extSdcard (or whatever extrenal memory was called... don't remember.. ) - and it of course has the same problems trying to flash either ROM.
My feeling is that my unit is not (fully) rooted, but like I said, I've been unable to find a solution. I really hope you can help, because I'd love to have CM on this delightful piece of hardware.
Click to expand...
Click to collapse
OMG! same issue here.. exactly, please HELP someone!!!

Format /system in recovery and then try flashing cm. It shouldn't be an issue mounting system if the partition is formated.

live-evil said:
Format /system in recovery and then try flashing cm. It shouldn't be an issue mounting system if the partition is formated.
Click to expand...
Click to collapse
Please elaborate for me,
Wipe does a format of the partition, is that enough or do I need to actually to use Format in the menu, as in kill the whole internal storage?
thanks
Linus

wipe is enough

live-evil said:
wipe is enough
Click to expand...
Click to collapse
thanks for the answer,
I hoped for that and also tried it.
No fun
I think I'll have to go for full format.
Just hope that does nothing bad >.<
Or is CWM maybe a better alternative?

DemonWareXT said:
thanks for the answer,
I hoped for that and also tried it.
No fun
I think I'll have to go for full format.
Just hope that does nothing bad >.<
Or is CWM maybe a better alternative?
Click to expand...
Click to collapse
what error message did you get?

I had the same problem yesterday in twrp 2.5.0.1 I just formated system and preload and factory resteted and then just rebooted and formated system again and it worked.

Grusburk said:
I had the same problem yesterday in twrp 2.5.0.1 I just formated system and preload and factory resteted and then just rebooted and formated system again and it worked.
Click to expand...
Click to collapse
Hehe I well tried that one,
no luck
interesting since 2.5.0.2 it says, unable to mount /system, and then promptly crashes
oh and the same happened in CWM
Hell XD
could I flash AOKP via odin maybe?
not like I like the idea >.<

It generally takes a few goes for the recovery to flash the rom in s4. Until someone works out what causes that bug in the recoviers you kind of just have to reboot and try again and again if necessary until it sticks.

live-evil said:
It generally takes a few goes for the recovery to flash the rom in s4. Until someone works out what causes that bug in the recoviers you kind of just have to reboot and try again and again if necessary until it sticks.
Click to expand...
Click to collapse
Aright, I think I found the way for me
Boot into recovery --> wipe system --> mount system --> if ok --> flash
if not ok --> retry the whole process
Strange stuff, but yay thanks all for your help

Schildkamp said:
Hi.
I've searched through a LOT of posts, but only found slightly related (and for me unhelpful) comments.
I have a GT-i9505 (i9505xxuame2), and rooted/flashed it using Odin / modified_cf_root. However, although I have succsessfully installed TWRP - AND have (seemingly) been able to make a full backup to my external sdcard, I am completely unable to install CM 10.1 nightly / AOKP (both i9505 versions).
Whenever i try this (via recovery of course), it always fails, reporting it was unable to mount /system. When restarting the phone, it just 'hangs' on the splash screen. The only solution then is to restore my backup, which works fine... HOWEVER, I suspect that since it has problems with the /system folder, It might not actually have backed this up, and that restore only works because /system happens to be untouced by my attempts to flash it.
Trying various tips & tricks found here on XDA - like manually mounting /system in TWRP, reflashing in Odin etc. has not helped me. I also noticed that when entering download-mode, it states that write protection is enabled (as in this thread - which unfortunatly also did not solve my problem: http://forum.xda-developers.com/showthread.php?t=2267107). I also tried CWM, but using this I'm unable to manually mount both /system, /sdcard AND extSdcard (or whatever extrenal memory was called... don't remember.. ) - and it of course has the same problems trying to flash either ROM.
My feeling is that my unit is not (fully) rooted, but like I said, I've been unable to find a solution. I really hope you can help, because I'd love to have CM on this delightful piece of hardware.
Click to expand...
Click to collapse
Crap. Have same problem.

I had this problem after flashing MH8 firmware (new bootloader) with Odin.
No matter what I tried in recovery I kept getting an error saying that it failed to mount system.
I had an older version of PhilZ on my ext SD luckily, so I flashed this, rebooted recovery then I could format system and it was mounted again.
then just flashed my newer recovery back and all was good

Hi guys,
it appears I'm having similar issues to you both but after 5 hours of constantly trying to fix this I'm still stuck! I've opened a new thread and I was wondering if you might be kind enough to help me out on there please?
Here's a link to the thread - would really appreciate any help you could provide... http://forum.xda-developers.com/showthread.php?p=46082532
Obagleyfreer said:
I had this problem after flashing MH8 firmware (new bootloader) with Odin.
No matter what I tried in recovery I kept getting an error saying that it failed to mount system.
I had an older version of PhilZ on my ext SD luckily, so I flashed this, rebooted recovery then I could format system and it was mounted again.
then just flashed my newer recovery back and all was good
Click to expand...
Click to collapse

DemonWareXT said:
Aright, I think I found the way for me
Boot into recovery --> wipe system --> mount system --> if ok --> flash
if not ok --> retry the whole process
Strange stuff, but yay thanks all for your help
Click to expand...
Click to collapse
Sh*t! Sorry:laugh: It really works! At least on my LG G2 D802. Thx, man!
---------- Post added at 01:46 PM ---------- Previous post was at 01:12 PM ----------
DemonWareXT said:
Aright, I think I found the way for me
Boot into recovery --> wipe system --> mount system --> if ok --> flash
if not ok --> retry the whole process
Strange stuff, but yay thanks all for your help
Click to expand...
Click to collapse
Sh*t! Sorry:laugh: It really works! At least on my LG G2 D802. Thx, man!

[Q] TWRP 2.6.3.0 Not possible to restore efs backup. What now?

Hello community,
i made a backup with TWRP 2.6.3.0 of my new Note 3 Qualcomm device cause i wanted to test some custom roms. After that i decided to roll back but it isnt possible to restore my backup, even when i check md5 verifying.
So i downloaded the newer release 2.6.3.7. The Restoring this time worked well but my efs folder wasnt restored. U cant check the efs backup which i made with 2.6.3.0 cause the efs backup wont show up.
So now i have a not fully working device which reboots every 30 seconds. My LED touchlights are off and without function.
Guys i dunno how to fix that. Any suggestions?
Max 1

Max One said:
Hello community,
i made a backup with TWRP 2.6.3.0 of my new Note 3 Qualcomm device cause i wanted to test some custom roms. After that i decided to roll back but it isnt possible to restore my backup, even when i check md5 verifying.
So i downloaded the newer release 2.6.3.7. The Restoring this time worked well but my efs folder wasnt restored. U cant check the efs backup which i made with 2.6.3.0 cause the efs backup wont show up.
So now i have a not fully working device which reboots every 30 seconds. My LED touchlights are off and without function.
Guys i dunno how to fix that. Any suggestions?
Max 1
Click to expand...
Click to collapse
I didn't even have 2.6.3.0 out for the international I believe. What file did you flash?

bigbiff said:
I didn't even have 2.6.3.0 out for the international I believe. What file did you flash?
Click to expand...
Click to collapse
I flashed it from this site. Its for the international N9005. http://www.techerrata.com/browse/twrp2/hlte
Flashed with openrecovery-twrp-2.6.3.0-hlte.img.tar restored successfully with openrecovery-twrp-2.6.3.7-hlte.img.tar but it cant restore my efs backup.

possible solution for you:
Installe TWRP 2.6.3.2 via odin, rebooted to recovery
Do an "adb shell" when phone is in recovery mode to run commands via TWRP
From the ADB shell: wipe the EFS partition with the following command:
mke2fs /dev/block/mmcblk0p12
mkdir /efs
mount -t ext4 /dev/block/mmcblk0p12 /efs
do a Factory Reset, the phone will now recover efs by itself
reboot

37_ said:
possible solution for you:
Installe TWRP 2.6.3.2 via odin, rebooted to recovery
Do an "adb shell" when phone is in recovery mode to run commands via TWRP
From the ADB shell: wipe the EFS partition with the following command:
mke2fs /dev/block/mmcblk0p12
mkdir /efs
mount -t ext4 /dev/block/mmcblk0p12 /efs
do a Factory Reset, the phone will now recover efs by itself
reboot
Click to expand...
Click to collapse
Thx 37_, i will try it but im no sure if im able to do it. I´ll try it before im asking again. Are you sure about 2.6.3.2, there isnt 2.6.3.2 for my device n9005 international? Which one should i use instead?

Max One said:
Thx 37_, i will try it but im no sure if im able to do it. I´ll try it before im asking again. Are you sure about 2.6.3.2, there isnt 2.6.3.2 for my device n9005 international? Which one should i use instead?
Click to expand...
Click to collapse
2.6.3.7 is the latest. I am not sure about the EFS issues, but I know the 2.6.3.7 works fine with EFS for qualcomm. I have read formatting like the previous poster fixes EFS issues. You might also need to odin system/boot/cache/recovery and start over.

bigbiff said:
2.6.3.7 is the latest. I am not sure about the EFS issues, but I know the 2.6.3.7 works fine with EFS for qualcomm. I have read formatting like the previous poster fixes EFS issues. You might also need to odin system/boot/cache/recovery and start over.
Click to expand...
Click to collapse
I believe u that EFS works fine with 2.6.3.7. My Problem is i cant see the backup file "efs" which i made with 2.6.3.0 in the latest 2.6.3.7. So it isnt possible to restore the backup file.
I tried the possible solution but somehow i get
List of devices attached
66ee6420 offline.
all the time.
I think im to noob for adb stuff. I think i need a step by step tutorial. Sry for my noobieness
bigbiff said:
...You might also need to odin system/boot/cache/recovery and start over.
Click to expand...
Click to collapse
What do u mean with this sentence. How to do this?

Max One said:
I believe u that EFS works fine with 2.6.3.7. My Problem is i cant see the backup file "efs" which i made with 2.6.3.0 in the latest 2.6.3.7. So it isnt possible to restore the backup file.
I tried the possible solution but somehow i get
List of devices attached
66ee6420 offline.
all the time.
I think im to noob for adb stuff. I think i need a step by step tutorial. Sry for my noobieness
What do u mean with this sentence. How to do this?
Click to expand...
Click to collapse
You need to download the firmware from Sammobile and flash it with odin.

Max One said:
I believe u that EFS works fine with 2.6.3.7. My Problem is i cant see the backup file "efs" which i made with 2.6.3.0 in the latest 2.6.3.7. So it isnt possible to restore the backup file.
I tried the possible solution but somehow i get
List of devices attached
66ee6420 offline.
all the time.
I think im to noob for adb stuff. I think i need a step by step tutorial. Sry for my noobieness
Click to expand...
Click to collapse
You need to enable developer mode by hitting Build number in Settings>About, a few times (around 10) this will allow developer options in settings. Go to dev options in settings and enable USB Debugging.
If you have the latest ADB drivers installed on your PC you should be able to connect, It will ask on your phone to allow the PC to use ADB.... Click allow or yes...
You should now be detected instead of "offline"...
Now do what you need to do...

And maybe try installing latest adb version 1.0.31 to avoid the "offline" message.
Sent from my SM-N9005 using Tapatalk

ultramag69 said:
You need to enable developer mode by hitting Build number in Settings>About, a few times (around 10) this will allow developer options in settings. Go to dev options in settings and enable USB Debugging.
If you have the latest ADB drivers installed on your PC you should be able to connect, It will ask on your phone to allow the PC to use ADB.... Click allow or yes...
You should now be detected instead of "offline"...
Now do what you need to do...
Click to expand...
Click to collapse
I did it as u said, but no chance to make a connection. No popup no nothing. Even the "Samsung Mobile Device MTP" driver fails to install cause my phone keeps rebooting every 30 secs.
CekMTL said:
And maybe try installing latest adb version 1.0.31 to avoid the "offline" message.
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
After installing the latest adb version it shows now "unauthorized" instead of offline.
37_ said:
possible solution for you:
Installe TWRP 2.6.3.2 via odin, rebooted to recovery
Do an "adb shell" when phone is in recovery mode to run commands via TWRP
From the ADB shell: wipe the EFS partition with the following command:
mke2fs /dev/block/mmcblk0p12
mkdir /efs
mount -t ext4 /dev/block/mmcblk0p12 /efs
do a Factory Reset, the phone will now recover efs by itself
reboot
Click to expand...
Click to collapse
List of devices attached
66ee6420 unauthorized
I only see this when the device is on. ( I mean in android os)
When i put it in recovery mode/ADB Sideload
I only see this written.. "List of devices attached" and thats all.
So 37_, i would like to follow ur instructions. But the main problem is to make successfull connection.
Am im doing something wrong? Why is it showing now unauthorized instead of offline?

please check my efs folder. i cant restore nv data files, cuz i dont have it..please check my efs folder and let me know whats missing and what can i do please.
i have only emergency calls, not registered in network..

@leo_hacker82 find any solution?

i dont have this device any more, but maybe u can use any cracked box, like z3x or octopus box..this tools work for wipe efs or repair efs..try it
hit thanks if it help

twrp 3.xx is out! go try to restore using the latest version of twrp

techdude18 said:
twrp 3.xx is out! go try to restore using the latest version of twrp
Click to expand...
Click to collapse
But do look at the dates of the posts you are replying to...

Dejan Sathanas said:
But do look at the dates of the posts you are replying to...
Click to expand...
Click to collapse
._.

[SOLVED] [HELP] unable to mount efs

My phone was initially stuck at the boot animation, so i decided to wipe cache and the "unable to mount efs" message appear. Now I have messed up my phone. It stays black screen after the Samsung galaxy S4 icon.
Can someone help me to solve the mounting and black screen problem?
Note: I have solved the problem by entering code in through terminal (TWRP go to advanced and then terminal), I typed the following:
mke2fs /dev/block/mmcblk0p3
mount -w -t ext4 /dev/block/mmcblk0p3
reboot

Use Odin to flash the stock firmware.
If you don't know how, use a guide. There are several written guides and video guides.

Pwnycorn said:
Use Odin to flash the stock firmware.
If you don't know how, use a guide. There are several written guides and video guides.
Click to expand...
Click to collapse
after flashing stock firmware, I'll have to root it again and start everything over again?

zhenhao97 said:
after flashing stock firmware, I'll have to root it again and start everything over again?
Click to expand...
Click to collapse
Yes.
But if you have a custom recovery at this time, then you can try flashing another ROM - CM or something.

Pwnycorn said:
Yes.
But if you have a custom recovery at this time, then you can try flashing another ROM - CM or something.
Click to expand...
Click to collapse
It appears the failed mount efs message and the phone stays on black screen