Database Develop

[Q] Sprint P100 can not wipe

Hi All:
My Sprint Tab P100 got some strange problems.
It's a second hand P100, Once i turn on the tab, it will warning with 3 Beebee, and nook & Amaza Mp3 & Market will report error.
Below warning will show up:
Amazon MP3_nook
“The application XXX has stopped unexpectedly, pls try again”
Market
"Attention:
An Error has occured, Please try again later."
After check, i found the original usr information still there.
(Gmail/Facebook account will try to sync with previous owner's ID. and i can not remove the account.)
What i have tried:
1) I have tried to WIPE using system recovery, after WIPE both data & Cache partition, issue still exist.
2) Perform the Samsung factory reset by enter *2767*3855# in the Memo, problem still there.
3)Format the SD card with Phone & Windows, still got problem
4) Flashed with the stock EA24 Rom from XDA(with Modem,using Odin), the problem still remain the same.
5)Flashed with DJ30, the problem still exist(Base/Fireware EA24).
6)Tried to install CWM, failed to boot up(Rooted before install CWM, after flash the Zimage to Kernal or recovery, some strings flush in the screen, then the tab hung at Samsung logo and reboot.)
I guess those problem was caused by some program information still remain in the internal storage, even after factory reset or flash with other ROM.
Can somebody help on this? Also prefer someone can help on how to install CWM
I am interesting that the OVERcome 2.01 Rom got a version to WIPE the internal storage, but the OVERcome rom are designed for GSMer. Can i tried to use it to clear my internal storage?

just installed Astro, the program will crashed when launch it

Can some one help on this topic?
I am suspecting my internal storage was locked to Non-Writable.
This might result CWM can not access the internal memory caused the failure of the installation.
Is it related to the Flash lock option in the Odin?

Check this thread..
http://forum.xda-developers.com/showthread.php?t=1133053
That has the stock files, and instructions to get root and CWM installed with the stock software. Using Odin to put the stock firmware (EA24) should wipe anything and everything off the tab and restore it to as if it were new out of the box. You also might want to wipe your sd card as it can cause issues with the CWM ext4 conversion.

Hi pvtjoker42 & All:
During the process of Kernel with CWM Recovery, i has been stopped @ step7
1) Download the zip file here
2) Unzip the file. You will need the file named zimage only.
3) Open Heimdall Frontend
4) Select Browse under Kernel and navigate to the file you downloaded in step 1 and select it
5) Press Start
6) The Tab will reboot, but will freeze on the Samsung logo. Turn it off and boot into recovery (Vol Up + Power)
~~~~~~~~~~~~~~~~~~~~
my tab failed here, no matter what you pressed, it doesn't go to CWM. Do u have any idea?
~~~~~~~~~~~~~~~~~~~~
7) CWM Recovery will attempt to back your tab up, but will fail. Don't fret.
8) Do a factory reset in CWM Recovery and reboot
9) You'll freeze on the Samsung logo again Turn it off and boot into recovery.
10) CWM Recovery will back your Tab up successfully.
11) You now have a CWM backup. Reboot.
12) Your auto rotate is broken.
13) Download the rotation file
14) Put it in /system/lib/hw and change the permissions to match the other items.

Can someone helps?
Today i tried 1 more things, Use a update.zip to update the tab from EA24 to EB28,before try this, i have tried OTA to EB28, it never success.
i download the update.zip from <forum.sdx-developers.com/index.php?PHPSESSID=99sdnmh5pm4rtuv39hk80f7du6&topic=13104.0;nowap> it seems to be official one, and the recovery is the stock version, but it failed again.
I start to believe that my internal storage has been locked, and data can not write in.
Is it possible to due to Fstab issue?
Pls helps to save my tab....

There is only one thing to do : return to stock. Carefully follow the guide. Don't do anything else to your tab, until you go through the restock steps :
http://forum.xda-developers.com/showthread.php?t=1133053
[SPRINT] Sprint Tablet Owners Thread (Root, ROM, Flash to stock, CWM Recovery)
The process reformats/repartitions your internal sd card, and sets the correct permissions. If this process fails, there is probably something wrong with the tab.

you might also try to select the option to repartition in Odin when going back to EA24. Then try the steps to get EB28 OTA update, and once you've got that up and running, you can try the update.zip to get to EF17 (gingerbread, as long as you don't need root)

I wouldn't. Try a different sd card
Sent from my Nexus S 4G using Tapatalk

Hi All:
Thanks for the advice.
I have tried to back to stock EA24 using odin, but the situation still ramain the same.
And it fail to OTA to EB28, the EB28 upgrade program will reboot the machine, and enter recovery model. but it will complete the program. also i have tried to put EB28 update.zip in the SD card, but also fail to upgrade to EB28.
I have repartition the phone by P100 serveral time using odin, also tried update Pit file. All failed.
I have format the SD card in Windows & then in Android, useless.
Now i have some clues:
In P1000 rom Roto-JME, there is Movinand.bin, this one got same name as the internal storage IC from samsung. i am thinking that file could be a file similar to partition table.
Can someone help to dump a "movinand.bin" for me from P100?
steps:
1)Get back to stock EA 24
2)Wipe Cache & factory data
3) Root it (Using superone click , you can find it here http://forum.xda-developers.com/showthread.php?t=803682)
4)Install terminal (i use better terminal) or using a ADB to connect to shell.
5)Type "su", check whether "$" change to "#" in the shell
6) Type “dd if=/dev/block/mmcblk0p2 of=/sdcard/movinand.bin bs=4096”
7) Find the Movinand.bin in the SD card
You can sent it to me by drop a email to [email protected]
If there is anything wrong, pls help to correct me
Thanks in advance

as some people is asking how did i fix the issue, just publish the information here.
I fixed the issue by replaced the internal storage (the chip), cost about US$ 30(RMB 200)
If anyone have better solution, just post here to share

[ROM] STOCK - FULL ICS IMM76D.LP10 for Verizon i815 LTE Tab (only!) *UPDATE 10/16*

UPDATE: My hosting I had for XDA related work expired, so I re-uploaded everything here: http://www.mods4cars.com/pub/xda
Hi everyone. As pretty much everyone of us who got suckered into buying this excellent (hardware) tab from Verizon knows, their update strategy has been very slow and on top of that, glitchy. Finally, 4 months after the other editions of this tab, we're getting ICS... BUT the update is an incremental OTA update that fails on 99% of the tabs, because it expects a version FD01b instead of the FD01 most of us have. The update seems to have gone through for only 2 or 3 lucky users who must somehow have had FD01b on their tab when they got it.
So after one of the best collaboration efforts on the "Tab 7.7 General" forums, I am happy to present to you
The CWM flashable "full stock" ROM for the SCH-i815 - ICS IMM76D.LP10
First up, let me stress again that this is a HACK and that this is RISKY and that if something goes wrong you MAY end up with a BRICK that will require complicated revival ceremonies! Unfortunately I *have* to say here, that whatever you do here, you do AT YOUR OWN risk, I can not be held liable for anything!
Prerequisites:
Verizon SCH-i815 LTE Tablet (ONLY this version!) with Honeycomb (everyone should have FD01 at this point)
Windows PC with Samsung USB drivers installed, meaning when you connect the tab, you should be able to copy files to it.
A micro-SD Card 2GB or bigger, preferable BLANK, FAT32 formatted.
Step 1: Prepare the SD card
Connect the SD card to your PC and copy the ROM files to it.
ROM Choices:
Original Cloned ROM (First version with direct partition image copy, requires >1GB space on SD card which has caused issues for some)
http://electron73.org/XDA/i815/electron_ICS-LP10_i815.zip
Update 10/12:
NEW ROM with full ext4 optimizations. System, Cache and Data (only in wipe version) will be cleared, formatted and "fsck -Dfy" checked!
DO NOT WIPE ANYTHING IN CWM!!! Just choose the ROM file appropriately.
Non-Wipe Version (This one leaves existing data partition alone, only checks it for errors)
http://electron73.org/XDA/i815/electron_ICS-LP10_i815_nowipe.zip
Wipe Version (THIS ONE WILL FORMAT DATA PARTITION, ALL USER DATA WILL BE LOST!)
http://electron73.org/XDA/i815/electron_ICS-LP10_i815_wipe.zip
Step 2: Download the Odin CWM Recovery pack and get ready to flash
Odin Pack: http://electron73.org/XDA/i815/electron_i815_odin_pack.zip
This ZIP contains everything you need now and later during this process. Extract it in any folder you like (Desktop/Odin or C:\Odin).
Run Odin3 v1.85.exe
Step 3: Bring the tab into Odin mode
Hold down the power and volume down buttons on your tab continuously until you see the big warning. Press volume UP to enter flash (odin) mode. Connect USB. In Odin the leftmost ID:COM field should now be yellow. Click the PDA button and select the cwm-6.0.1.1-i815.tar file. Leave everything else as-is. Click start to flash and when it says rebooting immediately grab the tab and hold down power and volume UP until you see the blue CWM screen! If you don't do this and let the tab boot, then it will automatically kill CWM (yes, bastards!), so don't let it boot the regular ROM!
Step 4: Flash the ICS ROM
Insert the card into the tablet, then in CWM go to install zip from sdcard, then choose zip from external sdcard. Select the electron_ICS-LP10_i815_v2.zip.
It will flash the kernel, the radio (LTE modem), the factory fs (/system) and preload partitions. The whole flash will take about 5 min. Especially on the last two steps be patient, it takes a while to extract 800mb and then flash the full filesystem image. Turning off power here (or running out of battery juice!) will make the rom unbootable and will require a full re-do. IMPORTANT: This requires the use of an external SD card! Using internal storage will not work!
WARNING: DO NOT wipe or factory reset in CWM! You can simply install ICS over an existing Honeycomb setup! Choose the correct ROM version: One erases everything and the other one preserves user data. Since this was originally an OTA, it knows how to convert your saved data. So all your emails, save games etc. will still be there! We had too many reports of problems when wiping/factory resetting with CWM. So for now the best advice for anyone looking into installing the ROM is DO NOT WIPE!
UPDATED PROCEDURE as of 10/16 - NO NEED to flash the old 3e recovery any more! Much easier and quicker baseband update below...
Step 5: Download and flash the baseband modem.bin with ODIN
Download the baseband update: http://electron73.org/XDA/i815/electron_ICS-LP10_i815_modem.zip
Bring the tab back into ODIN mode the same as before. Extract the modem.bin file from the modem.zip and drop it in the PHONE section (not PDA!) in ODIN this time. Click start and let it flash and reboot. Done. Under settings/about device you should now have Baseband Version i815.04 V.LP10 / I815LP10
B]Step 6: Optional: Keep CWM or go all stock[/B]
If you would rather like to be full stock than keeping CWM as the recovery program, then bring the tab back into ODIN mode one last time (pwr + vol down) and Connect USB, then flash LP10_recovery.
The ROM is pre-rooted. SuperSU is pre-installed as part of the ROM.
Trouble?
If the tab for some reason gets stuck in a boot loop with the Verizon animation playing over and over, don't fret! Give it AT LEAST 10 full minutes to start with and if it still doesn't show the home screen after that, hold down power and vol up until you're in CWM and wipe data/factory reset (yes, that will completely kill all user data and the tab will be "like new").
Trickier: If you see any warnings in CWM or 3e stock recovery, that there was an error mounting /data, then you lost the data partition and need to do extensive hacking before the tab will ever boot again. We fixed exactly this problem beginning on the very bottom of the page here http://forum.xda-developers.com/showthread.php?t=1927392&page=16 so don't panic! This repair surgery thanks to the excellent guide by Androguide.fr here: http://forum.xda-developers.com/showthread.php?t=1862294
Thanks
Thanks to everyone involved in making this happen! Especially asenduk for dumping the image backups from his tab, rayjr13 for bringing this whole thing to my attention and sending me the first OTA bin file.
Every use of the thanks button is greatly appreciated

Hi, thank you so much for these instructions and all the help. I was wondering does that 6.0.1.1 protect you from the brick bug and I saw that you hosted the V2 file in the original thread but here you have the regular file hosted. Is the V2 better?

johnny13oi said:
Hi, thank you so much for these instructions and all the help. I was wondering does that 6.0.1.1 protect you from the brick bug and I saw that you hosted the V2 file in the original thread but here you have the regular file hosted. Is the V2 better?
Click to expand...
Click to collapse
What is this brick bug people speak of? Bricking during a flash or bricking when you're sleeping at night and doing nothing to the tab?
Thanks again for this Rom electronic73! Hopefully some devs will take this as a base and run with it!
Sent from my SCH-I815 using xda premium

johnny13oi said:
Hi, thank you so much for these instructions and all the help. I was wondering does that 6.0.1.1 protect you from the brick bug and I saw that you hosted the V2 file in the original thread but here you have the regular file hosted. Is the V2 better?
Click to expand...
Click to collapse
Yes the 6.0.1.1 (as far as I know!) is safe. No need to wipe anyway. The v2 included more files that turned out to be not necessary. The files posted here along with the updated, safer method of flashing, should be the best and quickest way to get to full stock ICS.
The v2 was mainly an attempt to bring user ice's tab back to life after his data partition got killed.

Newbie question of the day - where is the IMEI stored on the 7.7? If it's in /system, won't this result in *everyone* flashing this image ending up with the same IMEI (which causes a whole set of problems of its own)?
Rodney

Thank you so much, and I do plan on doing a wipe to clear out my Tab to bring it to a clean slate. Just didn't want it to be a broken state lol.

rhester72 said:
Newbie question of the day - where is the IMEI stored on the 7.7? If it's in /system, won't this result in *everyone* flashing this image ending up with the same IMEI (which causes a whole set of problems of its own)?
Rodney
Click to expand...
Click to collapse
IMEI and such is stored in the mmcblk0p1 partition which (along with 2 and 3 which are the bootloader) we don't touch. So no, we only flash the factory fs, lte modem and kernel. CDMA modem.bin via the new method.

electron73 said:
Hi everyone. As pretty much everyone of us who got suckered into buying this excellent (hardware) tab from Verizon knows, their update strategy has been very slow and on top of that, glitchy. Finally, 4 months after the other editions of this tab, we're getting ICS... BUT the update is an incremental OTA update that fails on 99% of the tabs, because it expects a version FD01b instead of the FD01 most of us have. The update seems to have gone through for only 2 or 3 lucky users who must somehow have had FD01b on their tab when they got it.
So after one of the best collaboration efforts on the "Tab 7.7 General" forums, I am happy to present to you
The CWM flashable "full stock" ROM for the SCH-i815 - ICS IMM76D.LP10
First up, let me stress again that this is a HACK and that this is RISKY and that if something goes wrong you MAY end up with a BRICK that will require complicated revival ceremonies! Unfortunately I *have* to say here, that whatever you do here, you do AT YOUR OWN risk, I can not be held liable for anything!
Prerequisites:
Verizon SCH-i815 LTE Tablet (ONLY this version!) with Honeycomb (everyone should have FD01 at this point)
Windows PC with Samsung USB drivers installed, meaning when you connect the tab, you should be able to copy files to it.
A micro-SD Card 2GB or bigger, preferable BLANK, FAT32 formatted.
Step 1: Prepare the SD card
Connect the SD card to your PC and copy the ROM files to it.
ICS ROM: http://electron73.org/XDA/i815/electron_ICS-LP10_i815.zip
Modem Upgrade: http://electron73.org/XDA/i815/electron_ICS-LP10_i815_modem.zip
Make sure you have MORE than 1GB of free space left on the SD card when done.
Step 2: Download the Odin CWM Recovery pack and get ready to flash
Odin Pack: http://electron73.org/XDA/i815/electron_i815_odin_pack.zip
This ZIP contains everything you need now and later during this process. Extract it in any folder you like (Desktop/Odin or C:\Odin).
Run Odin3 v1.85.exe
Step 3: Bring the tab into Odin mode
Hold down the power and volume down buttons on your tab continuously until you see the big warning. Press volume UP to enter flash (odin) mode. Connect USB. In Odin the leftmost ID:COM field should now be yellow. Click the PDA button and select the cwm-6.0.1.1-i815.tar file. Leave everything else as-is. Click start to flash and when it says rebooting immediately grab the tab and hold down power and volume UP until you see the blue CWM screen! If you don't do this and let the tab boot, then it will automatically kill CWM (yes, bastards!), so don't let it boot the regular ROM!
Step 4: Flash the ICS ROM
Insert the card into the tablet, then in CWM go to install zip from sdcard, then choose zip from external sdcard. Select the electron_ICS-LP10_i815_v2.zip.
It will flash the kernel, the radio (LTE modem), the factory fs (/system) and preload partitions. The whole flash will take about 5 min. Especially on the last two steps be patient, it takes a while to extract 800mb and then flash the full filesystem image. Turning off power here (or running out of battery juice!) will make the rom unbootable and will require a full re-do. IMPORTANT: This requires the use of an external SD card! Using internal storage will not work!
BTW there is NO NEED to wipe! You can simply install ICS over an existing Honeycomb setup! Since this was originally an OTA, it knows how to convert your saved data. So all your emails, save games etc. will still be there!
Step 5: Flash the old Honeycomb recovery in order to do the modem upgrade
Since CWM does not understand the proprietary command used to flash the "firmware" which is the base modem file, we need to use STOCK recovery for this. The downside is that, of course, the new recovery is now locked down and won't accept unsigned files. So we need to flash the OLD Honeycomb FD01 recovery and feed it the modem update!
When the CWM flash above is finished and tells you to reboot, simple press and hold power and vol down again to get back into ODIN mode. Connect the USB again and this time use Odin the same way as above, but to flash the FD10_recovery.tar. This time uncheck the "reboot" tick mark.
Step 6: Flash the modem upgrade with the old stock 3e recovery
When Odin is done above, hold down pwr and vol up until you see the old school recovery pop up saying *manual mode*. Select flash update zip from sdcard and select the electron_ICS-LP10_i815_modem.zip this time. It will go on for a while in total bling flight. No output apart from rotating gears! This one is tricky. Just wait until it either ends saying that it is done or a yellow exclamation point shows up in the middle of the screen. The flash is done.
Step 7: Choose between Stock and CWM
Now bring the tab back into ODIN mode one last time (pwr + vol down) and Connect USB, then flash either CWM or LP10_recovery if you rather like to be full stock. If you chose CWM then be aware that the ROM will try to overwrite that immediately on first boot!! In order to avoid that, flash it with "reboot" box unticked and manually reset into CWM mode (pwr + vol up) and inside CWM select reboot system. It will then give you a big warning that the ROM has a CWM killer and offers you to disable that, so CWM will stay in place (good for Nandroids etd).
Step 8: Boot the ICS ROM and enjoy!
Once you see ICS, go to the play store and install SuperSU. The rom is pre-rooted and just needs the SuperSU app for full root access control.
Trouble?
If the tab for some reason gets stuck in a boot loop with the Verizon animation playing over and over, don't fret! Give it AT LEAST 10 full minutes to start with and if it still doesn't show the home screen after that, hold down power and vol up until you're in CWM and wipe data/factory reset (yes, that will completely kill all user data and the tab will be "like new").
Trickier: If you see any warnings in CWM or 3e stock recovery, that there was an error mounting /data, then you lost the data partition and need to do extensive hacking before the tab will ever boot again. We fixed exactly this problem beginning on the very bottom of the page here http://forum.xda-developers.com/showthread.php?t=1927392&page=16 so don't panic! This repair surgery thanks to the excellent guide by Androguide.fr here: http://forum.xda-developers.com/showthread.php?t=1862294
Thanks
Thanks to everyone involved in making this happen! Especially asenduk for dumping the image backups from his tab, rayjr13 for bringing this whole thing to my attention and sending me the first OTA bin file.
Every use of the thanks button is greatly appreciated
Click to expand...
Click to collapse
Hey Electron, thanks again for your outstanding work as well as all involved to make this happen. Since I installed your V2 this morning, I can skip the ICS ROM installation and go straight to step 5 right? Or is it better to start over from scratch?
Sent from my Nexus 7 using xda premium

bathanr said:
Hey Electron, thanks again for your outstanding work as well as all involved to make this happen. Since I installed your V2 this morning, I can skip the ICS ROM installation and go straight to step 5 right? Or is it better to start over from scratch?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Same here, what steps do I take to flash the updated modem

Awesome!

ice0901 said:
Same here, what steps do I take to flash the updated modem
Click to expand...
Click to collapse
from step 5 on forward. no need to reflash the whole rom if you already have ICS running.
Just odin the old recovery on, flash the modem update zip, then odin the new recovery or CWM back.

boot loop
Not sure whats up. Ive had your rom on all day. No problems. When i went to install the modem update, i entered odin and installed stock recovery, and boom, went into a verizon logo boot loop. i continued any way with the modem install, then put cwm back on, then wiped and data factory reset. waited 10 minutes during bootloop. Gave up, totally reflashed entire V2 Rom, again, stuck on a bootloop...so nwiped and data factory reset again,,,,still a bootloop....
bummer...does it just run until battery dies?

rspong said:
Not sure whats up. Ive had your rom on all day. No problems. When i went to install the modem update, i entered odin and installed stock recovery, and boom, went into a verizon logo boot loop. i continued any way with the modem install, then put cwm back on, then wiped and data factory reset. waited 10 minutes during bootloop. Gave up, totally reflashed entire V2 Rom, again, stuck on a bootloop...so nwiped and data factory reset again,,,,still a bootloop....
bummer...does it just run until battery dies?
Click to expand...
Click to collapse
Weird. OK did the v2 flash go all the way through? Did it finish at some point and say "please reboot" ? Or did it get stuck half way though?
Can you in CWM mount your internal storage? Did you get any errors when you did the full wipe/factory reset? anything saying "error mounting /data" maybe ?

electron73, did you create the .pit file in the cwm zip? It does not seem to match my i815 (which may be my problem, that mine is wrong)

I noticed the latest stock rom is like 550mb opposed to the one you uploaded this morning which was 990mb.. Is there a difference?

almus said:
electron73, did you create the .pit file in the cwm zip? It does not seem to match my i815 (which may be my problem, that mine is wrong)
Click to expand...
Click to collapse
No I didn't create it but it is guaranteed the right one for i815. I know because I messed up my partition table last night and had to use that pit to repartition Lucky I found that. What you would do in order to re-do your pit is open odin, put the CWM in the PDA section as usual and then click PIT and select that pit. That should activate a checkbox "repartition device". Leave that on for this one run and click start.
As a result it should partition, then flash the CWM and you should immediately be able to enter CWM. With CWM running connect USB
and use adb shell to get onto your tab.
IN the root prompt enter parted /dev/block/mmcblk0
and in the parted prompt enter print. If you see the result as in the attached pic (note: no file system in the DATAFS line) then you need to fix that the same way ice got it fixed last night. I think the link to the thread is in the OP

bathanr said:
I noticed the latest stock rom is like 550mb opposed to the one you uploaded this morning which was 990mb.. Is there a difference?
Click to expand...
Click to collapse
Yes the difference is that the preload partition (550mb decompressed) is not included any longer. Not needed. It was never altered in the first place. It only contains a game and useless verizon demonstration videos. I found out later that it had been untouched since Honeycomb FA02c

Yes. V2 went through with no problems.in CWM I can mount efs,cache,system but not data. Then in cwm... OK..wiping data then I get a error mounting data. Skipping format
Sent from my DROID RAZR using xda premium

chefdave12118 said:
What is this brick bug people speak of? Bricking during a flash or bricking when you're sleeping at night and doing nothing to the tab?
Thanks again for this Rom electronic73! Hopefully some devs will take this as a base and run with it!
Sent from my SCH-I815 using xda premium
Click to expand...
Click to collapse
The flash controller in our tablets is buggy. See here http://forum.xda-developers.com/showthread.php?t=1862294

electron73 said:
Yes the difference is that the preload partition (550mb decompressed) is not included any longer. Not needed. It was never altered in the first place. It only contains a game and useless verizon demonstration videos. I found out later that it had been untouched since Honeycomb FA02c
Click to expand...
Click to collapse
Thanks again man.. You have put forth an awesome effort in this work.. Sent you a little something as an appreciation:good:
---------- Post added at 09:43 PM ---------- Previous post was at 08:46 PM ----------
bathanr said:
Thanks again man.. You have put forth an awesome effort in this work.. Sent you a little something as an appreciation:good:
Click to expand...
Click to collapse
I ran into the splash screen just hanging and followed the data retore steps. I keep getting this error when trying to print the print command from the parted prompt.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Flatlinz>f:
F:\>cd 7.7
F:\7.7>cd adb
F:\7.7\adb>adb shell
adb server is out of date. killing...
* daemon started successfully *
~ # ls
ls
boot init sys
cache init.rc system
charger lpm.rc tmp
data preload ueventd.goldfish.rc
default.prop proc ueventd.rc
dev recovery ueventd.smdk4210.rc
efs res vendor
etc sbin
external_sd sdcard
~ # parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Error: Can't have the end before the start!
(parted)
Any ideas?

[Q] Phone state won't change no matter what I do

Quick SUMMARY (see details below if you've got some minutes to read!)
-> I need HELP!!!
-> Phone is rooted stock GB with jb hboot unlocked bootloader and TWRP v2.2.0, also superCID.
-> Problem is phone apps keep force closing and won't retain any change I make after reboot
-> Last installed program was ROM Toolbox
-> Steps already taken include: Reboots, Fix permission, Wipe (ALL), ROM Update using Windows, RUU using SD card.
Details
I have a Vivid with Stock Gingerbread (Rooted, Bootloader Unlocked, Juopunutbear hboot, SuperCID S-OFF, TWRP Recovery v2.2.0)
I recently removed the SD card on my vivid to use on another phone (SGS III) and when I returned the SD card and started my vivid, I tried using the file manager (ES Explorer) and it force closed, following series of other apps force closing.
I restarted the phone and the force closing didn't stop. I tried uninstalling the most recently installed app (ROM Toolbox) thinking it might be the culprit and nothing changed. I rebooted the phone and noticed every time I rebooted, the phone goes back to the state (installed apps, settings and every other thing) it was before I removed the SD card.
I installed Titanium Backup to make a Backup and flash the phone, but it kept force closing and after several reboots and attempts, it installed but couldn't acquire root.
I restarted to recovery to fix permissions and cleared cache and dalvik cache then rebooted the phone. No luck!!!
I eventually decided to wipe the ROM and do a fresh RUU install. I wiped system and data using recovery but when I restarted the phone, it booted to the (pre-SD card removal) state and was still force closing.
I tried installing ICS using the RUU from att and I got an "Error 155" on the way. I also tried installing the RUU using PH39IMG method with the SD card, it goes through the normal install process and when the phone booted, it's still the same state it was that it takes me to changing nothing.
I've tried all I know and it seems the phone is "write-locked" as it won't retain any change after reboot, suggestions to what I can do to fix this weird problem please.

I am not so sure...
Did the sgs3 reformat your sdcard to a different file system?
Sent from my HTC Holiday using Tapatalk 2

rignfool said:
I am not so sure...
Did the sgs3 reformat your sdcard to a different file system?
Sent from my HTC Holiday using Tapatalk 2
Click to expand...
Click to collapse
No it didn't. I only used the sdcard to copy some files to the sgs3 and I still could access the sdcard on my vivid through Root Browser in ROM Toolbox.

hardware maybe

Interesting... One thing you could do is enable USB debugging, and save a logcat showing your phone hitting some of these FCs so we can see what is causing them.
Once USB debugging is enabled, simply boot your phone, plug into your computer via USB, open a command prompt to where you have ADB tools installed, and type "adb logcat > log.txt
That will stream the log from your phone into a text file. After you get one or two FCs, on the command window hit CTRL + C to close the console, and save the log. Then post it as an attachment here.

ess.boyer said:
Interesting... One thing you could do is enable USB debugging, and save a logcat showing your phone hitting some of these FCs so we can see what is causing them.
Once USB debugging is enabled, simply boot your phone, plug into your computer via USB, open a command prompt to where you have ADB tools installed, and type "adb logcat > log.txt
That will stream the log from your phone into a text file. After you get one or two FCs, on the command window hit CTRL + C to close the console, and save the log. Then post it as an attachment here.
Click to expand...
Click to collapse
Thanks ess.boyer. I've been busy over the past few weeks so just saw your reply now.
The phone is in a pretty bad shape right now, I managed to drop it and the screen is shattered so I can't touch the screen to use it.
But I put it on and did the log. Please find attached.
Thanks for wanting to help!!!

So I think the install is probably botched. I'd recommend wiping EVERYTHING and reinstalling from RUU (maybe try a different RUU even).
However, first, please try wiping your cache and dalvik cache. Most of the errors are from not being able to find symbols in dalvik.
Also, are you restoring apps using Titanium backup or some other such program? If so, that could also be an issue. If you have, and wiping cache & dalvik cache don't work, you may want to try wiping /data entirely, and NOT restoring apps before you can confirm that the FC issues you were seeing are still there.
Give the cache & delvik clean a try, and if that doesn't work, please attach a similar log so I can confirm you're seeing the same issues, then we can go from there.

ess.boyer said:
So I think the install is probably botched. I'd recommend wiping EVERYTHING and reinstalling from RUU (maybe try a different RUU even).
However, first, please try wiping your cache and dalvik cache. Most of the errors are from not being able to find symbols in dalvik.
Also, are you restoring apps using Titanium backup or some other such program? If so, that could also be an issue. If you have, and wiping cache & dalvik cache don't work, you may want to try wiping /data entirely, and NOT restoring apps before you can confirm that the FC issues you were seeing are still there.
Give the cache & delvik clean a try, and if that doesn't work, please attach a similar log so I can confirm you're seeing the same issues, then we can go from there.
Click to expand...
Click to collapse
Please see my steps already taken.
I've wiped cache and dalvik, I've installed RUU thru windows, I've installed RUU from SD card. But whenever the Phone boots up, the phone state does not change at all (all apps are as they are, all settings are as they are).
I even tried to lock bootloader, remove superCID. Just a reboot and it all goes back to what it was.
Thanks

What happens if you reboot the phone without the SD card in it?

ess.boyer said:
What happens if you reboot the phone without the SD card in it?
Click to expand...
Click to collapse
The phone boots up to homescreen normally and the apps installed on SD don't work, with reduced FC

Development of New Hardbrick-Saving App?

Hey folks! :victory:
So I know you're all going to say, "oh, it's some xda noob", but I've got some big ideas for the future. So I had this great idea for an app that I'd like to share with all of you. I recently had my phone (HTC One m7ul) hardbricked by a slip of my fingers while clean-installing Omnirom. Fastboot and adb could not detect it, and therefore, my computer couldn't be used in the process of attempting to restore it. However, I could still access my recovery; and this is where I came up with the idea for this app I think everybody should have installed:
STASIS
This app would be the savior of all those people out there with hardbricked phones.
HOW IT WORKS
The app installs itself into the preexisting legacy partition of your phone, where it lies dormant and safe until needed
The app then recognizes the installation process to be complete and prompts the user to clone their phone into "stasis"
The way it clones the phone into "stasis" works as follows:
It copies the system partition exactly as it is
It then prompts the user for which files/apps it should back up as well
It saves all the selected files and apps in an archive that it names as "Stasis.zip" and then compresses and encrypts the archive with a password of the user's choice
Once complete, the phone reboots itself
Your phone is now INVINCIBLE!
The phone can now be saved from a complete internal storage wipe via commands from the recovery menu.
HERE IS THE TRICKY PART
The only way that this archive can be installed from the recovery partition would be by somehow force loading an extra option in the recovery "advanced" menu or by making it mounted via a series of hardware button presses in the install menu of recovery or a command line. This is ALOT HARDER than it actually sounds.
Prior to your internal storage wipe, your phone can restore via recovery by entering the series of commands and/or hardware button presses to mount the TWRP partition, and therefore flash the stasis.zip.
POSSIBLE OPTIONS?
The stasis.zip could be stored in it's own partition private from the rest of the system and/or recovery.
NOTE THAT I HAVE NO EXPERIENCE IN ANDROID DEVELOPMENT
I just want to see this damn thing made so everybody can have their phone hardbrick and live to tell the tale.
:fingers-crossed:
--flq of xda
P.S. If anybody thinks this app is a good idea, please feel free to join up on it's github!

doesnt a nandroid backup works the same way ?
or similar?

_flq said:
Hey folks! :victory:
So I know you're all going to say, "oh, it's some xda noob", but I've got some big ideas for the future. So I had this great idea for an app that I'd like to share with all of you. I recently had my phone (HTC One m7ul) hardbricked by a slip of my fingers while clean-installing Omnirom. Fastboot and adb could not detect it, and therefore, my computer couldn't be used in the process of attempting to restore it. However, I could still access my recovery; and this is where I came up with the idea for this app I think everybody should have installed:
STASIS
This app would be the savior of all those people out there with hardbricked phones.
HOW IT WORKS
The app installs itself into the preexisting legacy partition of your phone, where it lies dormant and safe until needed
The app then recognizes the installation process to be complete and prompts the user to clone their phone into "stasis"
The way it clones the phone into "stasis" works as follows:
It copies the system partition exactly as it is
It then prompts the user for which files/apps it should back up as well
It saves all the selected files and apps in an archive that it names as "Stasis.zip" and then compresses and encrypts the archive with a password of the user's choice
Once complete, the phone reboots itself
Your phone is now INVINCIBLE!
The phone can now be saved from a complete internal storage wipe via commands from the recovery menu.
HERE IS THE TRICKY PART
The only way that this archive can be installed from the recovery partition would be by somehow force loading an extra option in the recovery "advanced" menu or by making it mounted via a series of hardware button presses in the install menu of recovery or a command line. This is ALOT HARDER than it actually sounds.
Prior to your internal storage wipe, your phone can restore via recovery by entering the series of commands and/or hardware button presses to mount the TWRP partition, and therefore flash the stasis.zip.
POSSIBLE OPTIONS?
The stasis.zip could be stored in it's own partition private from the rest of the system and/or recovery.
NOTE THAT I HAVE NO EXPERIENCE IN ANDROID DEVELOPMENT
I just want to see this damn thing made so everybody can have their phone hardbrick and live to tell the tale.
:fingers-crossed:
--flq of xda
P.S. If anybody thinks this app is a good idea, please feel free to join up on it's github!
Click to expand...
Click to collapse
Your phone wasn't even close to being hard bricked, you wiped your system partition and internal storage at the same time. Leaving you no Rom to install or Backups to restore. This is a soft-brick at best.
In the process your Windows drivers failed stopping you from pushing a Rom which I still don't know weather you sorted or not because you haven't replied in your other thread.
The app you describe would do nothing a Nandroid doesn't do already. And regardless of where you store the Stasis.zip/Nandroid if you wipe the phone it will be gone. There are only 3 flash partitions on the HTC One System, Data and Cache all the other partitions are RAW partitions that require a direct dump.
If you want a separate partition to keep a backup on that can be accessed without the need for a pc, get your self an USB OTG device. Then you can keep a backup or rom on a usb stick and copy it or restore it to your phone using OTG without the need for a pc.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

What Danny said.
A hard-brick state is where you cannot access the kernel or even the bootloader. I'm not so sure if you still can access download or APX mode if you were hard-bricked, probably can still access either of them because it is most likely detached from the boot loader (again, not so sure, but from experience download mode *MAY* become inaccessable).
If your device was really hard-bricked and does not or cannot access any of those modes (I imagine fastboot being inaccessible as well) then all you can really do is JTag it. Problem is that devices like the Sony Tablet S has files which disables JTagging so I believe you have to directly JTag to the flash memory or something for it to work.
I think there is this other connector which can be used to also restore it, but I have forgot since I have not looked into it for a long time now.
I've forgot to mention, the recovery is also inaccessible in a hard-brick as it relies on the boot loader to change the boot path to the recovery or something (recoveries use a kernel as well).

only start screen

after flashing - i need to wipe - afgter this i get only the screen - "Samsung Galaxy SIII mini ,,, " and nothing else
i repeated flashin serveral times

Hi, a bit more info might help here, but anyway, if you are changing roms you need to factory reset & wipe dalvik & cache after flash generally, read op for rom, if u are trying something else, explain more pls
Sent from my GT-I8190 using XDA Free mobile app

ok - i flashed the phone with CM12 (with odin) .
Flashing all ok. Then i go to twrp and wipe Dalviak and Cache.
After system boot only the " Samsung Screeen ..." appears.
After that i try a new flash with CM 11 but allways the same .. " Samsung Galaxy ...) . .. nohing else

are you sure you are not wiping system or data?

i thing i wiped both

Only wipe dalvik & cache after flash, not system and data
Sent from my GT-I8190 using XDA Free mobile app

i do the descriptions on nova fusion with odin3 (cm12)::
...
6) Turn off your phone, and then use VOL- & HOME & POWER buttons combination.
7) If you see Warning screen, use VOL+ button.
8) You should see Android and some information.
9) Connect phone to computer and make sure it is detected by Odin (it will appear as COM device). If it doesn’t, try to use other USB port.
10) Use Start button. Wait until flash process will finish.
11) Your phone will restart, but probably won’t boot. Pull down your battery and use VOL+ & HOME & POWER buttons combo to boot into recovery.
-> all ok -> twrp 2.7.1.0
12) Click on Wipe, then use slider on the bottom to let process begin.
-> here iam not realy sure - i do dalviak and cache wipe
-> i get an error - E:Unable to mount "/system"
13) Click on Home icon, and then Reboot -> System.
Wait for boot. Now you should have ROM installed and ready to use!
-> nothing happens -i have onlythe start screen" Samsung ...."

I always flash roms from zip file with twrp & don't usually have any problems, maybe you should try that method instead
Sent from my GT-I8190 using XDA Free mobile app

Yes you are right , but dont have a chance to put the files on the phone,
because i have only two modus:
1) Modus twrp - how you can put file on the phone ?
2) and the downloading modus - and there i know only odin software
How you then put files on the device ?

Put the file on ext sd card, boot into twrp recovery, factory reset, then select install, install from ext sd, select zip file, wait till installed, then wipe dalvik & cache, reboot system, do full nandroid backup, first just incase so you can go back to previous rom & settings
Sent from my GT-I8190 using XDA Free mobile app

yes i know - but when you say ..Put the file on ext sd card ...
how schould i do this ?
there is no adb, there is no system - only twrp modus or starting screen...

connect the phone to pc & open sd card or put sd card in a card reader & transfer then boot into twrp recovery& do wipes & installation as explained

Did you have any luck with this problem yet?
Sent from my GT-I8190 using XDA Free mobile app