Database Develop

rooting issues

so I tried to Root my Dream and choose after a number of failed attempts I have decided to just give up so I want to wipe and restore my phone's OS the factory but when I try though the settings menu the phone restarts then just sits on the "Rodgers" logo for ever so is there anyway to fix that?

Don't give up so soon
I definitely recommend rooting. The rogers firmware sucks by default imo. I did not like my phone at all until I rooted.
Check this guide by HyeProfile, I just used it on a new rogers dream and it worked 100%:
http://forum.xda-developers.com/showthread.php?p=4280573#post4280573
If you really don't want to root, you can follow the steps to try flashing (using the same instructions he gives in that post) with the official rogers radio.img and recovery.img here: http://www.stevebirstok.com/android/losemyroot.zip

well I hate how slow my phone feels so I'm going in for the root again thanks for the push to try again.

ok ran into an issue:
Installing from sdcard...
Finding update package...
E:Can't mount /dev/block/mmcblk0p1 (No such file of directory)
E:Can't mount SDCARD:update.zip
Installation aborted
when trying to apply update.zip

Loading001 said:
ok ran into an issue:
Installing from sdcard...
Finding update package...
E:Can't mount /dev/block/mmcblk0p1 (No such file of directory)
E:Can't mount SDCARD:update.zip
Installation aborted
when trying to apply update.zip
Click to expand...
Click to collapse
that means it can't see your sdcard.
see if dropping into the recovery console(alt+x) and typing
Code:
mount /sdcard
recovery
see if that helps anything since that command will mount your sdcard which it appears to be failing to read.

when I try enter the console all the options are removed form the screen then nothing happens all I see is the yellow text.
The yellow text I'm talking about is the error message I posted.

if you are trying to unroot it, use the same rc package that you use to downgrade it in the bootloader (camera and power) and run the .nbh there

Loading001 said:
ok ran into an issue:
Installing from sdcard...
Finding update package...
E:Can't mount /dev/block/mmcblk0p1 (No such file of directory)
E:Can't mount SDCARD:update.zip
Installation aborted
when trying to apply update.zip
Click to expand...
Click to collapse
Are you sure your sdcard is formatted to FAT32?

I'm going o try that when I get home

ok so it's weird.
E:Multiple firmware images
E:can't store hboot images
E:failure at line 1
write_hboot_image PACKAGE:hboot.img
install aborted
ok so now it just sits on the "Rogers" logo and wont enter any mode (camara+power)
edit: looks like that means I biked the thing hope they will replace it (i'll just blame it on their firmware update thing)
edit2: calling rogers to try get a replacement

will it it read an .nbh in the bootloader?

I don't know how can I test that or see if it will?

I was refering to the dreaimg.nbh from either rc29 or rc7 that you use to downgrade your phone in order to root it, that use the bootloader camera + power

no it wont enter any mode at all just sits on the rogers logo so a new phone should show up in the next 3 to 5 days

this kinda scares me off from trying again but I want to so I might.

got a all new phone and it still wont mount the Sd card like last time

ok so i helped some one root their rogers phone last night. are you trying to flash the radio, or have you followed all of the fastboot commands in the "rogers heres your real root" thread? the guy i was helping couldn't flash the radio but we got it with the fastboot commands

no I'm past loading recovery.img with fastboot and I'm trying to apply the update.zip

thats very odd. so you did all the fastboot commands and still can't get it to work?
is it any rom you try to flash?

well I was following the guide in one of the first posts

Problem with NookColor, need quick advice!

I'm trying to update my bro-in-laws nook from an old CM7 nightly (somewhere around 23 I think??) to 7.0.3 but I'm having a problem with clockwork recovery...I downloaded RomManager and flashed ClockworkMod. I then tried to backup and update my rom, but as soon as it restarted in recovery, it says
E:Can't mount /cache/recovery/command
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 /cach/recovery/last_log
and won't allow me to do anything with it....I try to backup manually and it says can't access data or something like that. any advice would be great and hopefully fast, he's only in town for another 2 or 3 hours!

I had this happen before when I chose the wrong CWR to flash to recovery. From within ROM Manager, select 'flash clockworkmod recovery'. When asked to select your device, choose 'nook color', NOT 'nook color old'. The option for 'nook color old' isn't even available on the newer versions of Rom Manager, but it was there on older versions. Make sure you update Rom Manager, then reflash CWR as above, and it should then work.

Thank you! your post reminded me that the older versions of Nightly's (pre 7.0.1) had the problem of not showing all the apps in the market, so Rom Manager wasn't there, so I didn't think it needed updating...once I updated it allowed me to install the newest version of CWR and fixed (almost) all the problems!

[Q] Stuck on Samsung logo, recovery says can't mount /dev/block/mmcblk0p1

Hi.
I'm trying to fix my boss' tab, SPH-P100 (Sprint).
I have tried all kinds of things and nearly bricked it (got the phone ! computer symbol, but it still accepted uploads, so I was OK).
Here's the issues:
- Continuous loop of Samsung logo on boot
- From Recovery screen, I performed a factory reset, but it didn't help - same logo loop
- In the Recovery screen, I get errors similar to the ones quoted above:
E:Can't mount /dev/block/mmcblk0p1
(No such file or directory)
E:Can't mount CACHE:log/recovery.log
E:Can't open CACHE:log/recovery.log
E:Can't mount /dev/block/mmcblk0p1
(No such file or directory)
I read all kinds of posts about simply flashing the stock ROM, and I found the ROM that was mentioned multiple times in these forums to be the right one for this tab (it did change the first boot animation, though...). The ROM I used is tab_sprint_noModem_20101226.tar inside Tab_Stock_-_No_Modem.rar.
I tried:
-ODIN with the stock ROM posted in this thread. It works, but it doesn't fix anything. I tried with and without the PIT file (one thread specifically warned NOT to use the PIT file, but in the end I tried it anyway - I think I did NOT hit Repartition, so it probably didn't do anything...).
-Heimdall doesn't seem to work at all for me. I found version 1.3.1, and the instructions in post 21 of the thread linked above don't seem to apply to this version. I finally figured out that I need to be in the FLASH tab, but I can't add files without the PIT file, it won't let me add the zImage file for recovery (or at least complains that there's no .bin file ending), and when I checked "Repartition", I got the error:
ERROR: Partition corresponding to -21 argument could not be located
Ending session...
Yes, I installed the drivers that came with Heimdall.
-Following other posts with very similar errors, I formatted the SD card in Windows using FAT32 - no change.
-I looked into another thread talking about parted, but I don't have root on that device, and I'm not sure what my boss would think about me rooting his pad... I also don't know enough to figure out which rooted ROMs would go with it - I'm scared enough with the "official stock rom" I'm using
I'm fairly tech savvy, know a little about Linux and have used adb to root my own phone, but otherwise a lot of the things I read here only make enough sense to me to follow the instructions and not get lost.
Maybe there's a different version of Heimdall that I should be using, or maybe I did something else wrong, but I'm sure I followed the instructions here.
Any help would be greatly appreciated!
Thanks in advance!
(PS, I originally posted this at the end of the thread I mentioned here but did not get an answer - I'm sorry, I had not read the post about not asking questions in that forum, even if it was attached to another post where similar questions were asked and answered, so I'm moving this post here instead.)

Update:
Found a different Rom in this thread - same situation:
I can flash it, but nothing changes, and I still get the error message I showed. The main change is that this ROM is the first I have found that has the same Sprint boot animation that the tab originally had.
The new information is that once it resets after flashing, it briefly shows a few messages - one said that if failed to wipe the cache, and I think the others showed the same error about /dev/block/mmcblk0p1 but I can't be sure (tried to get video of it, but I was too slow, and it's blurred - I'll try again later to get the exact error messages).
Update 2:
Found yet another ROM in this thread and tried it, and this one doesn't seem to work at all with this tab (tried with and without pit/re-partitioning) - the boot fails and immediately boots into Recovery by itself and shows the following:
-- bootmode=7 from cmdline
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/command
-- Wiping data...
Formatting /data...
E:format_volume: rfs format failed on /dev/block/mmcblk0p2
Formatting /dbdata...
Formatting/cache...
E:format_volume: rfs format failed on /dev/block/mmcblk0p1
Data wipe failed.
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/recovery_kernel_log
E:copy_kernel_file :: Can't open /cache/recovery/recovery_kernel_log
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (No such file or directory)
Click to expand...
Click to collapse
Will try to flash the other ROM again to try and get a precise look at its error message...
UPDATE 3:
Flashed the first ROM again - no error message, just the same Samsung logo cycle that freezes briefly and then starts over.
Flashed the second ROM again (the one that has the correct Spring animation), and this time I got the error messages on video.
-- Wiping DATA:...
Formatting DATA:...
DATA: wipe failed.
-- Wiping CACHE:...
Formatting CACHE:...
CACHE: wipe failed.
--Wiping DBDATA:...
Formatting DBDATA:...
E:Can't mount /dev/block/mmcblk0p2
(No such file or directory)
E:Can't mount /dev/block/mmcblk0p1
(No such file or directory)
E:Can't mount CACHE:log/recovery.log
E:Can't open CACHE:log/recovery.log
E:Can't mount /dev/block/mmcblk0p1
(No such file or directory)
Rebooting...
Click to expand...
Click to collapse
Still hoping for ideas, but I think I'm at the end of what I can try...
Is it likely or possible that the internal memory got damaged?
I don't know exactly what my boss did to the tab, but he mentioned something about "the cold" meaning Minnesota winter cold - we had about 12 degrees last week, so maybe that's the cause...

Have you found and tried the EA24 stock flash tool?
Sent from my SPH-P100 using xda premium and ICS

Thanks for the reply!
If that's this file:
Sprint Galaxy Tab EA24 Flasher.zip
Then I have tried the ROM in it with Odin, but not the actual tool that came with it.
I'll see if I can get my boss to give me another shot with it (unless he's already returned it - I've had it for a few days already...).
Thanks!

has anyone found a solution to this? I am having the exact same issue...
Not sure why or how it happened everything was fine one day and next day wont go past logo and keeps rebooting.

Same problem here
My P100 started this problem last night, which was the first time it's been turned in in several days. It's fully stock, never had any rooting or flashing performed on it.
Booting into recovery mode shows failed mounts on everything it tries to do, and all the options for recovery also fail - except for "reboot system now", which does reboot it, but then it just sits on the pulsing Samsung logo endlessly. And I do mean endlessly, I let it go four hours last night, after which the battery ran out. Plugged it in after that, and it's right back to the same thing.
Every other thread I've found with this problem listed it as an after-effect of having attempted to flash a new ROM, but that is not the case with mine...
Hoping someone has the answer...
Thanks!
-mike

Same exact symptoms, and when I tried CM9 or other ICS ROMs this errors lead into the dreaded "Encryption Unsuccessful" bug.
At this point I'm just trying to get the device to boot consistently.

ChrisCTX said:
Same exact symptoms, and when I tried CM9 or other ICS ROMs this errors lead into the dreaded "Encryption Unsuccessful" bug.
At this point I'm just trying to get the device to boot consistently.
Click to expand...
Click to collapse
Did you try to do full restock (include bootloader and repartition)?
or you can try CM9 again with a fixed kernel by cdesai or jt. look at this conversation:
http://forum.xda-developers.com/showpost.php?p=28584567&postcount=2320

yappoe said:
Did you try to do full restock (include bootloader and repartition)?
or you can try CM9 again with a fixed kernel by cdesai or jt. look at this conversation:
http://forum.xda-developers.com/showpost.php?p=28584567&postcount=2320
Click to expand...
Click to collapse
I'm on it ASAP, thanks a ton for that
Edit: If possible mind giving a link to that specific kernel (or flashable .zip with it)?

Do you have this on your screen:
http://forum.xda-developers.com/attachment.php?attachmentid=1193979&d=1342124106
If so, we're in the same boat
Btw, I used a full repartition and boot following this thread:
http://forum.xda-developers.com/showpost.php?p=17817287&postcount=2
and same error occurs.

Bump in hopes of solving this issue.

My tab is basically bricked. I have this same issue after putting CM9 on it. Those errors consistently pop up. and thats it.
I guess its a paper weight now.

you may try flashing pit file and stock rom with micro SD inserted during flashing. that's what I did to my Samsung GT-I9003 when it failed to read the internal SD. At first, the camera may not work. Just root the device after flashing pit/ROM and do SD Swap Mod (external SD as internal SD).
Not sure if it's gonna work with Galaxy Tab. Give it a try. Hope this helps.

Hey guys, it appears JimRich is working on a solution for the CDMA (verizon and sprint) versions of thsi device, keep checking and be sure to let him know there are other people with this problem. http://forum.xda-developers.com/showthread.php?t=1789728

Problem with kernel (2.6.32.61 and 2.6.32.60)

My goal was to install the ROM JB-4.1.2.
I've rooted my phone with flashtool, uncloked the bootloader also with flashtool and since then everything went great.Next step which wasn't hard at all was to flash the kernel via flashtool and it also happened with great result.The problem appeared when I was turning phone on, the system haven't turned up and my phone had showed only CWM Recovery.I knew that something went wrong but I made full wipe, cache and dalvik cache and installed JB-4.1.2. The CWM has said that system has been installed but when I've tried to boot phone JB didn't show up; again there was only CWM.
I've tried few times the procedure ( installing stock 2.1 android from Update Service, rooting phone with Flashtool, and flashing the kernel) but I'm facing the same problem with CWM.
Maybe I did something wrong, but don't know exactly what; or maybe my phone is not suitable for kernel?
I'm waiting for help!

Did you format the partitions before flashing the rom?

Yes, I did and nothing has changed.I again saw a screen with CWM and under options to choose at CWM I had a message from CWM like that:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
E:Can't open /cache/recovery/last_log

Can anybody help with that odd problem?

/cache error

Hi,
I managed to root a stock Straighttalk (verizon fascinate) Showcase running GB 2.3.6. Then managed to flash a CM 10.1 (StraightTalk.showcase.cm-10.1-20130723-NIGHTLY-fascinatemtd.zip), and it seemed to run 'ok'. Then I read about HellyBean, but could only find the kernel. The other mirrors for it no longer exist, and the developer no longer has copies.
The file I flashed from CWM 4.0.1.0 recovery was: Devil4.2_galaxysmtd_20130624.zip. It said something about reparitioning. I figured what the heck and said flash anyway. It did but now will only boot into that. Trying to flash back to CM 10.1 I get a /cache error:
ClockworkMod Recovery 4.0.1.0
E:Can't mount /cache/recovery/command
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
I have tried numerous methods suggested in two year old (dead) threads: flashing pit with odin and original rom (atlas_v2.2.2.pit, Odin3 v3.07.exe, CI500_VZW_EH03_GB_CM.tar.md5) yet keep running into the /cache error, or it won't flash or whatever. It comes back to that error.
I bought another phone for the time being, but I would like to get this one working.
EDIT: didn't realize the i500 and i9000 were different phones. Going to the Fascinate forum...

Here's the fix
THIS IS ONLY FOR THE FASCINATE/SHOWCASE/SCH-I500 or SCH-S950C
MODERATOR PLEASE MOVE THIS THREAD to the Fascinate forum.
THIS WILL NOT WORK IN THE I9000. In fact, flashing i9000 kernels (like Der Teufel / The Devil kernel, CAUSED THIS PROBLEM).
Fire up ODIN (I used ODIN 3.07 on Windows 10 (12/2015 patch level))
**Uncheck Auto-Reboot!! in ODIN before flashing.**
Use the PIT from EZbase (others might work)
and flash cwm4_fixed_for_cm7-ODIN.tar
https://www.dropbox.com/sh/fk25duo59iyn33g/AADm6xkLJCOiprqe37e4TOMia?dl=0
I put them on dropbox. Although you can find them in other threads/places. I did not keep track of where I found the copies, but I found them on 12/2015, so you should be able to also.
Unplug the phone and remove the battery. It will turn off.
Remove the SDCARD and put in http://download.cyanogenmod.com/get/jenkins/35557/cm-10.1-20130723-NIGHTLY-fascinatemtd.zip (the latest nightly CM10.1 Android 4.2.2x)
Boot up the phone by holding the Vol Up & the Vol Down key, and press Power until you see SAMSUNG, then release the Power button. It will boot up into a 4.0.1.0 recovery. YOU MAY STILL SEE A CACHE ERROR... IGNORE IT.
Choose the option to load a ZIP from the SDCARD.
Flash cm-10.1-20130723-NIGHTLY-fascinatemtd.zip
It will reboot into the newer recovery, then continue with the update.
You should be done now.
No more /cache/ mount errors, no more stl11 errors.
I found a quote at http://forum.xda-developers.com/showthread.php?t=1190668
"All Samsung Roms run on top of BML/RFS, CyanogenMod 7 does NOT.
It runs on MTD/yaffs2 (like Nexus One) which means you'll not able to flash just any kernel or run just any other filesystem you want. Use it as it is if possible, otherwise confirm with the kernel developer that you are trying to install whether it would work with CM. We do not support other kernels and know nothing about their capabilities or compatibility. Only the data partition, which is on movinand, is ext4 like on speedmod or voodoo ("lagfix"). No "lagfix" is necessary because this does not use any Samsung proprietary file systems."
IT RUNS ON MTD/yaffs2... etc etc, it's clear that this repartitions/reformats the device. A lot of the struggle I had for days, a week, was trying to set the PIT over with Heimdall or ODIN, and restoring to stock. Unfortunately once one of these i9000 type kernels or ROMs 'touch' your Fascinate, you can't go back to the stock, at least not from being stuck with the /cache/ mount errors. You *might* be able to go back after flashing the nightly Cyanogenmod linked above.