My Current Model is Google Android One Sprout 4.
Hey. My phone started getting system app crashes. So I used Philz Recovery to wipe cache and dalvik cache.
so I got error in wipe cache.
I tried rebooting and it booted by now all the apps just keep crashing . So I went into Recovery again and Tried Format Cache.
Thing is that my cache did format yet the error can't mount cache/logs persisted.
Earlier I had fix such problem by just using SP tool to reinstall stock rom.
I have SP Tool. So I used it to flash stock rom again with scatter files all ok.
But it did not turn on nor did the charging screen came on.
So I tried Lollipop version scatter of sprout4 and both kitkat version using sp tool.
sprout_reference_pack_1379542-KPW53_ALPS.KK2.AOSP.SPROUT.SP.p52-mmx
sprout_reference_pack_1783956-LMY47O_ALPS.L1.SPROUT.SP.p76_user_4g-mmx
Karbonn_Sparkle_V_1783956_Lollipop
Now here is the problem. Sp Tool detects the phone, it flashes using download only. Gets 100% done. But the phone does not saves the rom inside even after it said it wrote successfully.
Tried Format, Format + download. and Download only. But Nothing works even after it's successfully completes.
The Phone does not start except When i plug in my phone even with battery I keep hearing the Connecting and Disconnecting sound constantly every 2 seconds. Do you guys have any idea what could be the cause?
Has Internal memory failed? Or Reading section of motherboard is failed.
Jexboxer said:
My Current Model is Google Android One Sprout 4.
Hey. My phone started getting system app crashes. So I used Philz Recovery to wipe cache and dalvik cache.
so I got error in wipe cache.
I tried rebooting and it booted by now all the apps just keep crashing . So I went into Recovery again and Tried Format Cache.
Thing is that my cache did format yet the error can't mount cache/logs persisted.
Earlier I had fix such problem by just using SP tool to reinstall stock rom.
I have SP Tool. So I used it to flash stock rom again with scatter files all ok.
But it did not turn on nor did the charging screen came on.
So I tried Lollipop version scatter of sprout4 and both kitkat version using sp tool.
sprout_reference_pack_1379542-KPW53_ALPS.KK2.AOSP.SPROUT.SP.p52-mmx
sprout_reference_pack_1783956-LMY47O_ALPS.L1.SPROUT.SP.p76_user_4g-mmx
Karbonn_Sparkle_V_1783956_Lollipop
Now here is the problem. Sp Tool detects the phone, it flashes using download only. Gets 100% done. But the phone does not saves the rom inside even after it said it wrote successfully.
Tried Format, Format + download. and Download only. But Nothing works even after it's successfully completes.
The Phone does not start except When i plug in my phone even with battery I keep hearing the Connecting and Disconnecting sound constantly every 2 seconds. Do you guys have any idea what could be the cause?
Has Internal memory failed? Or Reading section of motherboard is failed.
Click to expand...
Click to collapse
Greetings and welcome to assist. It may be a hardware issue but is your bootloader locked ? I found this useful thread of guides
https://forum.xda-developers.com/cr...ser-roms-recoveries-kernels-mods-how-t2908298
and this thread of firmwares if it helps
https://forum.xda-developers.com/cr...wnload-links-sprout-4-android-m-otas-t3219057
Good Luck
Sawdoctor
Related
My P5100 had CM10 nightly on it and was running fine until I upgraded to the latest version of CM10 after wiping the cache & Dalvik cache. After the upgrade I couldn't get Google Play to run even after wiping its data and fixing permissions so I tried to do a CWM restore. Unfortunately there was a fault restoring the Data partition and now my tablet is stuck at the animated bootscreen. If I long-press the power button it powers off but immediately restarts. There is no way to start in in recovery or flash mode. I've plugged it into my PC and the Samsung Android ADB interface is showing but the other references to the tablet all have a yellow triangle in Device Manager. I'm hoping some clever person can help me rescue the tablet with ADB. Thanks!
dwl99 said:
My P5100 had CM10 nightly on it and was running fine until I upgraded to the latest version of CM10 after wiping the cache & Dalvik cache. After the upgrade I couldn't get Google Play to run even after wiping its data and fixing permissions so I tried to do a CWM restore. Unfortunately there was a fault restoring the Data partition and now my tablet is stuck at the animated bootscreen. If I long-press the power button it powers off but immediately restarts. There is no way to start in in recovery or flash mode. I've plugged it into my PC and the Samsung Android ADB interface is showing but the other references to the tablet all have a yellow triangle in Device Manager. I'm hoping some clever person can help me rescue the tablet with ADB. Thanks!
Click to expand...
Click to collapse
IF CWM is not working use Odin to flash CWM again then use CWM to flash CM10,
You may need to do a factory reset (full wipe) from CWM.
If all else fails use Odin to flash stock JB ROM
DigitalMD said:
IF CWM is not working use Odin to flash CWM again then use CWM to flash CM10,
You may need to do a factory reset (full wipe) from CWM.
If all else fails use Odin to flash stock JB ROM
Click to expand...
Click to collapse
Thanks but Odin cannot see the tablet to re-flash the recovery.
Downlods mode
Then flash new firmware
sembre said:
Downlods mode
Then flash new firmware
Click to expand...
Click to collapse
That's the problem - I cannot access download mode
UPDATE - it just started in download mode! I can manage from here!!
Just for the record you can install adb on the pc and run the command 'adb reboot recovery'. This will force the tablet to reboot in recovery mode.
Sent from my GT-I9300 using xda app-developers app
Jeez, this has taken up most of the day to fix. I came across many problems I have not previously experienced:
1. When the tablet was stuck at the boot animation and I tried to turn it off by long-pressing the power button it immediately restarted. The only way I could get it to turn off was by long-pressing the power button whilst it was connected to my PC.
2. Flashing the stock ROM with Odin appeared to complete successfully but it would never fully boot, it always got stuck at the black & white Samsung screen. Same problems turning it off as above.
3. Flashing CWM with Odin caused the tablet to reboot into the stock ROM which would not load, in the end I had to untick the "reboot" button in Odin, power it off then manually restart with the Vol- & power buttons.
4. The only way I could get a bootable ROM was by flashing CM10 with CWM. I tried to restore 2 previous CWM backups but on each occasion there was an error restoring the Data partition and I got stuck at the scenario at (1). The backups were made to the external SD card with CWM Touch - is the Touch version unreliable?
I would be really interested if anyone could shed any light on any of this stuff!
For how long did you let it install during the first reboot? It happened to me too, and it took about 10 minutes, maybe even more...
Also, did you try in the "Mount and storage" cwm menu the options "format system", "format data", "format cache" and "format preload" options, prior to re-flashing a ROM? I have read somewhere that for a clean install it's better to do this, as it really clears everything that could mess up the system between two different bases ROMs (like CM and stock).
What I do everytime is using in CWM these 4 "format" options, plus "wipe" system, cache and dalvik, then immediately after this I flash with cwm the new "zip" copied on the card. Then the first reboot is much longer than usual, as at this stage it installs the files, rebuild the dalvik cache etc.
Good luck
dwl99 said:
2. Flashing the stock ROM with Odin appeared to complete successfully but it would never fully boot, it always got stuck at the black & white Samsung screen. Same problems turning it off as above.
Click to expand...
Click to collapse
I think I gave it a good 20 mins to boot. When I got up this morning there was an error message saying that there was no room to install any more apps even though I had very few installed. Settings -> Storage would not calculate the space available so I figured that the partitions had become corrupted. I did the step by step format you described and reflashed & it all seems to be OK now.
HELP PLEASE! MY PHHONE HAS BEEN DEAD FOR 2 DAYS. ERROR MOUNTING EMMC!
My phone is stuck at bootloop and it goes to black screen and comes again. But my phone won't turn on.
problem began when i tried to increase my app storage space. I did a backup but restoring couldn't read data saying error. Then i tried to install a custom rom my phone was running on. Installation was succesful. But again as i said it was stuck at bootloop.
i google for bricked solution and tried almost everything. I even tried to flash stock rom with windows sp flash tool. Didn't work.
when i was trying everything in CMW recovery(like wipe data,cache,dalvec cache n everything individually) and i tried to mount emmc and it said
error mounting /emmc
otherwise everything worked
then i thought trying to increase app storage may have broken my partition
phone's warranty just expired 1 month ago
CAN ANYBODY FIND A SOLUTION FOR THIS?
Hi Guys,
I found evertyhign started to crash one day all the apps and msgs start to popup e,g this and this process has stopped.
First i went to recovery and Wipe advanced ( Delvik , Cache , Data , System) it wiped it fast and sucessfull but when i boot to rom my corupted rom is still there where my SD card is full wiped and blank( i had my rom in it) .
I tried to wipe flash anything using recovery TWRP 2.8 everything says sucessfull but nothing happes still old corupted rom.
I went to Factory mod and try to clear eMMC but when i press to clear it shows Formating/Data and then reboot right quickly.
I m so fadeup with this since for past 2 days i tried each and everysingle thing menioted on any forum.
Kkindly see the video in youtube to understand more of the problem.
Please Help
Hello i recently use SlimLP rom until suddenly it was stuck on boot loop . I thought that it must be the problem of the custom ROM and i try to flash other ROM but it seems that i can't proceed to the procedure of wipe data/factory reset because it kept restarting after i checked that option . wiping dalvik cache is fine though . I also did format/data on my solo attempt to fix it but still it won't work.After reading some forum I decided to flash stock firmware but it kept failing on Odin . anyone know what might be the problem of this ? Did I just hardbricked my tab to the point of can't be repaired ? thanks in advance
Try to delete everything in data manually through twrp file manager (Advanced->File Manager)
john99ap said:
Try to delete everything in data manually through twrp file manager (Advanced->File Manager)
Click to expand...
Click to collapse
Im using CWM recovery T.T
iqbaladeee said:
Im using CWM recovery T.T
Click to expand...
Click to collapse
Then, install the latest common twrp by Andi from here: http://andi34.github.io/recoveries_tab2.html
and try it (first try also to wipe data with twrp)
iqbaladeee said:
Hello i recently use SlimLP rom until suddenly it was stuck on boot loop . I thought that it must be the problem of the custom ROM and i try to flash other ROM but it seems that i can't proceed to the procedure of wipe data/factory reset because it kept restarting after i checked that option . wiping dalvik cache is fine though . I also did format/data on my solo attempt to fix it but still it won't work.After reading some forum I decided to flash stock firmware but it kept failing on Odin . anyone know what might be the problem of this ? Did I just hardbricked my tab to the point of can't be repaired ? thanks in advance
Click to expand...
Click to collapse
I can't change my rom, wipe / format doesn't work. Nothing changed after flashing with Odin.
16 GB Tab 2 have a known faulty EMMC (MAG2GA). It can happen, that your EMMC get “read only”, so you can’t perform any write actions (also you can’t format) anymore.
From the EMMC data sheet:
5.1.7 End of Life Management:
The end of device life time is defined when there is no more available reserved block for bad block management in the device. When the device reaches to end of its life time, device shall change its state to permanent write protection state. In this case, write operation is not allowed any more but read operation are still allowed.
But, reliability of the operation can not be guaranteed after end of life.
On a faulty EMMC firmware it happens a lot faster.
What are the symptoms?
Uninstalled apps and deleted files are back after a rebootFormating the storage doesn’t work (after reboot the old rom and apps are back)You can flash whatever you like via Odin - it showes “passed” but after reboot nothing changed (e.g. still no StockRom or still the old Recovery you had previously installed)… there might be some more, but only to mention some …
In most cases, the issue can be fixed by a EMMC firmware update, but you need someone who’s able to do it (possible via ISP, nothing you can do esylie at home yourself). In some bad cases you need to find someone who can replace your EMMC.
source: http://andi34.github.io/faq.html
Hello all,
Hopefully you will be able to help me with this problem as I am currently without a phone until I can resolve this.
To run you through the process, I flashed Nitrogen OS, rebooted to recovery, flashed gapps and all was well. I decided to attempt to encrypt the device once I had setup my Google account. The battery was 100% and plugged into the charger. Shortly after the process started, the phone went into a bootloop. Since, I have attempted to wipe system , cache, dalvik and data, then reflashed Nitrogen OS, but it is still in a bootloop.
When I wipe system , cache, dalvik and data, I also get the error "Unable to mount storage" in TWRP.
I have even attempted to restore the backup I took before flashing Nitrogen OS, with no luck.
Any ideas?
SOLVED.
If anyone else has this problem and looking for a solution, you need to completely reflash stock firmware via fastboot. PM me if you need any help or info regarding this.
OPO_UK said:
SOLVED.
If anyone else has this problem and looking for a solution, you need to completely reflash stock firmware via fastboot. PM me if you need any help or info regarding this.
Click to expand...
Click to collapse
i have yureka plus facing same problem.I was using aex5.2 rom .Once all the apps kept starting and so i rebooted. After that message came showing that your data is encrypted and you need to factory reset.I tried factory resetting through twrp but did not help.Error shows unable to mount system storage and cache.Tried all possible things through twrp bt no use.Did not use fastboot mode as my pcb is damaged.(only charging occurs, no data transfer.).Willing to use fastboot. please help.