My a100, which was running Flex, froze up night before last and I powered down, thinking that would take care of it like it has before. Wrongo! Now all I can do is boot into recovery. Will not mount anything in the system. Any help to fix this would be greatly appreciated.
Try erasing CWM recovery (fastboot erase recovery), place the update.zip (of the official rom) on your external SD card (via card reader, etc.), then attempt to boot into recovery (it should flash the rom).
Theonew said:
Try erasing CWM recovery (fastboot erase recovery), place the update.zip (of the official rom) on your external SD card (via card reader, etc.), then attempt to boot into recovery (it should flash the rom).
Click to expand...
Click to collapse
That's the thing, I can't get it to mount anything including the external sd when I boot into recovery.
j.price said:
That's the thing, I can't get it to mount anything including the external sd when I boot into recovery.
Click to expand...
Click to collapse
CWM recovery will not be there to do that. Maybe the default will be able to.
Theonew said:
CWM recovery will not be there to do that. Maybe the default will be able to.
Click to expand...
Click to collapse
If you have adb pull the recovery log that will show any errors in the fileaystems. I woukd say dump it but if it cant mount external sd that wont work. You verified failed mounting in the mounts menu in recovery?
Tapatalked from my Galaxy S II.
That is correct. Will not mount anything other than the recovery partition.
j.price said:
That is correct. Will not mount anything other than the recovery partition.
Click to expand...
Click to collapse
And did you try adb? Try it from whatever pc you used to get cwm or twrp or whatever recovery on there. It's not really possible for it to only mount recovery or you wouldn't boot at all. In cwm go to mounts and make sure your internal sd and /data does or does not mount. And try to get that log it'll pretty much solve it without random flashing.
Tapatalked from my Galaxy S II.
Won't pull the logs, but I can show you pictures I took of the tablet in Recovery with the errors. Also, if I did what was suggested and tried to run a Stock Recovery what would happen if I did that and went back to full stock or atleast attempted to
j.price said:
Won't pull the logs, but I can show you pictures I took of the tablet in Recovery with the errors. Also, if I did what was suggested and tried to run a Stock Recovery what would happen if I did that and went back to full stock or atleast attempted to
Click to expand...
Click to collapse
I need to see the log not the error on screen, that just says error I need to see what causes it, in the log.
If you go back to full stock its like how Acer intended. You'll need to root and unlock the boot loader again and install cwm or twrp again, if you choose to. I'm not one to throw flashes at a device that isn't working correctly but sometimes that's the only fix. Still haven't mentioned if adb works. If you want to send pics I guess go into mounts and try to mount internal SD or external SD and take a pic of the error. Go ahead and post or send the pics of the error you took already, may explain things enough there.
Tapatalked from my Galaxy S II.
Unintentionally misspoke. Tablet is recognized by ADB in recovery but will not pull the log to my PC. That is why I offered the pictures. But as the log is better, could you just reconfirm first the commands needed to pull the logs via ADB> Maybe I am screwing something up. This is the first time I have had any major issues with Android.
j.price said:
Unintentionally misspoke. Tablet is recognized by ADB in recovery but will not pull the log to my PC. That is why I offered the pictures. But as the log is better, could you just reconfirm first the commands needed to pull the logs via ADB> Maybe I am screwing something up. This is the first time I have had any major issues with Android.
Click to expand...
Click to collapse
Ok if ADB is working then we can fix this. The command is
adb pull /cache/recovery/last_log > last_log
This will pull the log to whatever directory your ADB is launched from, if you have the SDK then it will be in your platform-tools folder. You can either post it here, or send it to me directly.
On your device, in recovery (of course at this point lol) attempt to mount each partition, cache, system, data, internal sd, external sd. Then run that command from your command prompt/terminal depending on what OS you use.
My email is [email protected], you can use this for gtalk if we need to start throwing commands at it, that will be the easier way vs posting and waiting. You can also email me that log directly if you choose. Once this is resolved you or I can post the fix back here for others should they need it.
Once this is done hit me up on gtalk if you can, usable through the gmail website as well, I have to make a phone call or 50 so I won't be checking here for a little bit.
adb gives me the error
C:\Program Files\Android\android-sdk\platform-tools>adb pull /cache/recovery/las
t_log > last_log
The system cannot find message text for message number 0x5 in the message file f
or System.
Click to expand...
Click to collapse
Now it is saying
remote object 'cache/revocery/last_log' does not exist
Click to expand...
Click to collapse
I'm also experiencing this issue where Relix rom froze on me and now recovery can't mound /sdcard/ Any ideas?
A100 won't mount emmc or SD Card
any solution to this??
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I also had this problem, most forums say its a bad emmc. I chatted with an acer rep before sending it in, they received it yesterday, hopefully they wont give me problems because of the "unlocking"
UPDATEThey fixed it!! Only thing I can advise is to get on the site and chat with a rep to confirm that its a bad emmc, maybe they dont even boot it up once thats on the ticket
brick
sorry for my bad english, i have this problem im from venezuela and here the guarantee not cover me i send to acer venezuela and his say that is the logic card, why you fix you brick tablet? plsss i need help im trying to solve this brick since 4 month am i love mi tablet!!
etoxz said:
sorry for my bad english, i have this problem im from venezuela and here the guarantee not cover me i send to acer venezuela and his say that is the logic card, why you fix you brick tablet? plsss i need help im trying to solve this brick since 4 month am i love mi tablet!!
Click to expand...
Click to collapse
Its been verified there is a fault in the emmc. There is currently no way to repair it other then sending it to Acer, sorry to say. Acer locked us out of what we need to fix this.
Tapatalked from my Galaxy S II.
I had a similar issue it would load cwm or twrp but it would not load a recovery. it kept saying that files were missing i had to send it back for repair they replaced the main board it is an issue with the hardware not the software. Mine just froze then it died. sorry man. I can say mine was unlocked and they covered it under warranty.
pio_masaki said:
Its been verified there is a fault in the emmc. There is currently no way to repair it other then sending it to Acer, sorry to say. Acer locked us out of what we need to fix this.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
So, has anyone experienced this emmc fault outside of the Relix rom? I'm just curious--I had my tablet for 10 months and this rom for 1 week, and this happened. I loved the rom, but will definitely stay away from it if it's breaking emmc. (I'm a total noob -- not sure if the issue with emmc is hardware vs. software).
eatnosenuggets said:
So, has anyone experienced this emmc fault outside of the Relix rom? I'm just curious--I had my tablet for 10 months and this rom for 1 week, and this happened. I loved the rom, but will definitely stay away from it if it's breaking emmc. (I'm a total noob -- not sure if the issue with emmc is hardware vs. software).
Click to expand...
Click to collapse
Mine happened on a personal build of CM10, other's on CM9, etc. Its a fault with the emmc firmware, not ROM or Kernel dependant.
Related
I was copying my SD Card to my computer. At some point I forgot I was transferring files and disconnected the usb cable. I reconnected the cable and all seemed right. So I continued on and rebooted my phone.
After a few minutes I noticed the green notification light blinking and assumed I had a text or mail. When I hit the power button on top to wake the phone the screen never came on. I pulled the battery and tried to reboot the phone. It would just vibrate 5 times and the screen would stay blank. So i tried recovery and it would work only with the USB cord plugged in. But it wouldn't do a nandroid backup or even see the sdcard.
when in recovery I get the error E:Can't mount /dev/block/mmcblk1p1 (or /dev/block/mmcblk1)
I tried getting a adb shell but it says no device connected
I tried using fastboot flash boot boot.img and fastboot flash system system.img
they would error with FAILED (remote: signature verify fail)
anyone have any suggestions?
oh in windows device manager it say ADB bootloader only when I am in HBOOT when in fastboot it says nothing but since it did push the system image I assume it does work.
if i go into recovery though (Windows7 Enterprise 32bit) it asks for a Qualcomm CDMA driver real quick(2 seconds) then goes to Unknown Device
fader01 said:
oh in windows device manager it say ADB bootloader only when I am in HBOOT when in fastboot it says nothing but since it did push the system image I assume it does work.
if i go into recovery though (Windows7 Enterprise 32bit) it asks for a Qualcomm CDMA driver real quick(2 seconds) then goes to Unknown Device
Click to expand...
Click to collapse
Sounds like you corrupted a partition or two. Just get an RUU PB31IMG.zip, copy it your card (you may have to take it out and fix it in windows first), and let bootloader see it. There are ways to manually NANDroid your phone in ADB/Recovery, but it doesn't sound like you want to go that deep nor do I know how to tell you to do it from the command line.
Good luck!
Thanks for the reply. The phone will not mount or see the SD Card. I put the sd card in my storm and it formatted it I put it into the Incredible but it still will not mount the SD Card.
I did go to the verizon store and my hopes where they had some way to format the partitions and force the OS on it. The guy looked at the phone and said we dont have a recovery console for the Incredible so I will have a new one sent to you probably will be Tuesday.
I thought the Dallas Cowboys boot screen and fastboot screen would tell him something wasnt right but he didnt know or he didnt care. I also thought it was odd he gave me the phone back. Shouldnt he have kept it to send back in?
I have ran into the same issue. Basically my phone was bootlooping after a bad rom install(my guess). Then when I tried my nandroid recovery backup, I got to this black screen and the phone would vibrate 5 times! I have never had this issue before.
I have tried various RUU PB31IMG.zip's to flash back to a stable system and nothing works. I have noticed after flashing different RUU images(stock 2.2, stock 2.1), the phone will either vibrate 3, 4 or 5 times. I believe these could be error code messages of some kind.
Has anyone else gotten this black screen, and the 5 vibrations????? This seems like it should be called the black screen of death because it honestly makes me want pull my hair out in frustration! Any knowledge would be greatly appreciated. thanks.
google this error: E:Can't mount /dev/block/mmcblk1p1 and there should be a link to a cyanogen forums thread and a link to an xda thread. those two will contain the information necessary to repartition your internal storage so you can boot into the OS again
illalliance said:
I have ran into the same issue. Basically my phone was bootlooping after a bad rom install(my guess). Then when I tried my nandroid recovery backup, I got to this black screen and the phone would vibrate 5 times! I have never had this issue before.
I have tried various RUU PB31IMG.zip's to flash back to a stable system and nothing works. I have noticed after flashing different RUU images(stock 2.2, stock 2.1), the phone will either vibrate 3, 4 or 5 times. I believe these could be error code messages of some kind.
Has anyone else gotten this black screen, and the 5 vibrations????? This seems like it should be called the black screen of death because it honestly makes me want pull my hair out in frustration! Any knowledge would be greatly appreciated. thanks.
Click to expand...
Click to collapse
I got the 5 vibration deal when I was trying to boot into recovery.....but was pressing volume up/power, instead of vol down/power......the 5 vibrations are a Qualcomm diagnostic test.
SLOflatlander said:
google this error: E:Can't mount /dev/block/mmcblk1p1 and there should be a link to a cyanogen forums thread and a link to an xda thread. those two will contain the information necessary to repartition your internal storage so you can boot into the OS again
Click to expand...
Click to collapse
I had googled that before making this post, nothing I found had helped me. I cannot say, for sure, that I found the post you are referring to though. I did finally manage to get the system to see the sdcard and PB31IMG.zip. I took the rom.zip from the Froyo RUU and I renamed it pb31img.zip. It went through and flashed everything but still nothing. When I later tried to do the same thing with the rom.zip from the 2.1 RUU the system said that it was an older version and would not flash it. So this seems to me that the flash went OK. Its like the main OS partition isn't bootable or something the system knows the OS is there it just cannot boot to it.
You said it. The main partition is corrupt, I will try and find the link to the thread about how to restore it just give me a second.
Here is the link Talk to Ciwrl; he is a very smart person when it comes to these problems.
tdavis42 said:
You said it. The main partition is corrupt, I will try and find the link to the thread about how to restore it just give me a second.
Here is the link Talk to Ciwrl; he is a very smart person when it comes to these problems.
Click to expand...
Click to collapse
I trashed my internal partitions yesterday and used this method to fix it.....had to end up un-rooting and starting over after I got the partitions back in order....but it did fix the problem.
tdavis42 said:
You said it. The main partition is corrupt, I will try and find the link to the thread about how to restore it just give me a second.
Here is the link Talk to Ciwrl; he is a very smart person when it comes to these problems.
Click to expand...
Click to collapse
Thanks a lot. I will work on it after work tonight.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ClockworkMod Recovery - Modified for Motorola Xoom​
OK, so this recovery will skip /data/media (Internal storage) when performing nandroid backups and also when you perform a factory reset.
This means that we can now perform nandroid backups without backing up our internal media and removing it everytime you want to do a backup.
Thanks to Bigrushdog and MadIndustries for helping out with the concept of the solution for skipping /data/media.
Also thanks to Koush and all the other developers that have contributed to clockworkmod, without you guys the android world would be completely different.
Thanks also to everyone in #xoom that tested this.
The source code for all changes etc are available through the github repository. The two other projects that have been modified to make this recovery possible can also be viewed through my github account.
Even though this recovery has been tested, I am not liable for any loss of data or any damages done by this recovery.
==============================================
General Notes
When I refer to /data/media, this is the same as /sdcard when the xoom is booted into honeycomb. So any data that is stored in here should be untouched by this recovery.
If you encounter a problem with the filesystem on /data like it has become corrupt, place a blank file called "eraseData" (without the quotes) in the clockworkmod folder on your external sdcard. This will revert to the old way of formatting /data. NOTE: by doing this you will lose everything that you have in /data/media.
Versioning of recovery images:
At the moment I don't have a version number as such, instead each recovery image is timestamped in the format of DDMMYY-HHYY. So the file recovery-solarnz-120511-2030.img was produced on 12 May 2011 at 8:30 PM. This versioning is also shown in recovery when it starts.
==============================================
Downloads
SLOW DOWN AND RELAX
Make sure you download the correct version depending on how you want to flash. I have seen at least two xooms bricked now because they have tried to flash the zip file through fastboot.
Recovery Zip (solarnz-R4c-100611-1150) FLASHED THROUGH CWM
MD5: 1ad409db4030635734b27df02b7e7c1a
Recovery Image (solarnz-R4c-100611-1150) FLASHED THROUGH FASTBOOT
MD5: 20575d4b62bf697f77abca9093877ea3
==============================================
Installation Instructions
Method 1 Flashing through CWM
Download the recovery zip file
Place the recovery zip on the sdcard where clockworkmod can read it.
Reboot into recovery using "adb reboot recovery" or any other method
In recovery, select flash zip from sdcard and select the recovery zip you downloaded
Sit back and relax while recovery flashes the new recovery and reboots into it.
Click to expand...
Click to collapse
Method 2 Without CWM
Download the recovery image (not the zip file)
Pull up your command prompt, then
Code:
adb reboot bootloader
fastboot flash recovery recovery-solarnz-XXXXXX-XXXX.img
fastboot reboot
Let your Xoom boot up. Then to check out your shiny new recovery,
Code:
adb reboot recovery
Click to expand...
Click to collapse
Also, you can grab Rom Manager or QuickBoot from the market for easy access to recovery.
==============================================
Changelog
Code:
[url=http://bit.ly/k7cZxJ]3.2.0.0 (R4c-100611-1150)[/url]
- Rebuilt recovery, the previous recovery was built off of bad device files.
[url=http://dl.dropbox.com/u/13093938/XDA/Recovery/recovery-solarnz-R4b-060611-1300-cwm.zip]3.2.0.0 (R4b-060611-1300)[/URL]
- Disabled partitioning the sdcard as per request.
[url=http://dl.dropbox.com/u/13093938/XDA/Recovery/recovery-solarnz-R4-050611-1515-cwm.zip]3.2.0.0 (R4-050611-1515)[/URL]
- Included changes from koush's sources upto clockworkmod 3.2.0.0
- Implemented Advanced backup. This allows you to choose what partitions you want to backup.
[url=http://dl.dropbox.com/u/13093938/recovery-solarnz-120511-2030.zip]3.0.2.8 (120511-2030)[/url]
- Fixed mounting the sdcard for some users
[url=http://dl.dropbox.com/u/13093938/recovery-solarnz-080511-1630.img] 3.0.2.8 (080511-1630)[/URL]:
- Modified to skip /data/media or /sdcard in nandroid backups.
- Modified formatting /data to remove directories and folders so we can keep media.
- Place a file called eraseData in the clockworkmod directory on your EXTERNAL sdcard to revert to the normal restoration method.
Great job guys!!!!
Sent from my HTC HD2 using XDA Premium App
You da man solarnz! Also, you can grab step 1 from my 3.1 thread. That zip will flash recovery from recovery! Mods, please unsticky my Recovery thread and lock and replace with this one. This is recovery we will support going forward.
Win
Sent From My Evo
Great job folks!!!
We've gotten used to BRD's awesome formatting of his posts and super clear instructions, would be real nice if we can get this on the new sticky
bigrushdog said:
You da man solarnz! Also, you can grab step 1 from my 3.1 thread. That zip will flash recovery from recovery! Mods, please unsticky my Recovery thread and lock and replace with this one. This is recovery we will support going forward.
Click to expand...
Click to collapse
might be a stupid question but just to clarify: we would obviously not want to flash any recoveries in rom manager thus not having any need for rom manager at at this point correct?
jland22 said:
might be a stupid question but just to clarify: we would obviously not want to flash any recoveries in rom manager thus not having any need for rom manager at at this point correct?
Click to expand...
Click to collapse
Rom manager is still nice as you can quickly reboot to recovery etc from it. It also allows you to select the operation to do in recovery and then restart it will automatically restart and perform the action.
If you flash recovery from Rom Manager, you will end up with the official 3.0.2.5 recovery from Koush that doesn't contain the method of skipping /data/media
bigrushdog said:
You da man solarnz! Also, you can grab step 1 from my 3.1 thread. That zip will flash recovery from recovery! Mods, please unsticky my Recovery thread and lock and replace with this one. This is recovery we will support going forward.
Click to expand...
Click to collapse
What's the difference between this and the one on bigrushdog thread. (3.1)
Sent from my Xoom using XDA Premium App
lokko21 said:
What's the difference between this and the one on bigrushdog thread. (3.1)
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
No difference, BRD used this modified 3.2.8 in his first step on that thread. But this will be the go-forward recovery from now on.
What folder do i need to flash this too?
b0ricua said:
No difference, BRD used this modified 3.2.8 in his first step on that thread. But this will be the go-forward recovery from now on.
Click to expand...
Click to collapse
Gotcha so I'm cool, thanks.
ok just flashed, looks good
Solarnz, thanks for formatting the OP and adding clear instructions!!
You da man!
very cool, but would it be complicated to just make an "exclude" menu before backing up? That way people can just exclude whatever they want ...
thanks to everyone who contributed. We dont always think about how great CWM is and all the wonderful things it does for us until we dont have it anymore I didnt like the feeling of walking around with that stock recovery
running into a problem. I have a wifi only xoom. I had the old 3.0.2.8 recovery installed which i still had after 3.1 update no problems with it at all. I just flashed the 3.0.2.8 one using fastboot but now when i reboot into recovery. All i see is the android with the exclamation mark i do not see clockwork. I have reflash more then once with no luck still.
Edit: wanted to add that if i flash the clockwork from Rom manger which i see is the version 3.0.2.5 i am able to do a adb reboot recovery into recovery with no problems.
Edit2: for some reason the zip flashing in the old recovery works fine and updated to the new recovery. no clue why fastboot is not working. I tried fastboot 5 times every flash said it finished fine but it boots with a android and a exclamation mark. only the zip flashing in recovery works for me.
maybe this is a stupid question, but i dont even see a "media" folder on my xoom. there are folders for music and video. i have my own folder for movies, one for comics, ect. do i have to create a media directory and move everything into it in order to make sure that it doesnt get included? and if so, where does it go?
Prod1702 said:
running into a problem. I have a wifi only xoom. I had the old 3.0.2.8 recovery installed which i still had after 3.1 update no problems with it at all. I just flashed the 3.0.2.8 one using fastboot but now when i reboot into recovery. All i see is the android with the exclamation mark i do not see clockwork. I have reflash more then once with no luck still.
Edit: wanted to add that if i flash the clockwork from Rom manger which i see is the version 3.0.2.5 i am able to do a adb reboot recovery into recovery with no problems.
Edit2: for some reason the zip flashing in the old recovery works fine and updated to the new recovery. no clue why fastboot is not working. I tried fastboot 5 times every flash said it finished fine but it boots with a android and a exclamation mark. only the zip flashing in recovery works for me.
Click to expand...
Click to collapse
Ok, I'm assuming you are on android 3.1 without a modified kernel.
The issue you are having is that with the default boot image, it flashes back the stock recovery every single time you reboot.
Code:
adb shell rm /system/recovery-from-boot.p
adb shell rm /system/etc/install-recovery.sh
(Thanks Berzerker7)
ltracte said:
maybe this is a stupid question, but i dont even see a "media" folder on my xoom. there are folders for music and video. i have my own folder for movies, one for comics, ect. do i have to create a media directory and move everything into it in order to make sure that it doesnt get included? and if so, where does it go?
Click to expand...
Click to collapse
Ok. on our xooms, /sdcard is actually a symlink (think of a shortcut) to /data/media.
So when I say /data/media, you can think of /sdcard (the internal storage).
random one again - will this be available via ROM Manager? it's still 3.0.2.5 there
thanks!
E: can't mount /sdcard/update.zip
or error mounting /sdcard
anyone has encountered this problem plz?
thks
I wanted to try Merruk's kernel so I download the 4 files that are to be used. I flashed KernelUpdate.zip first and rebooted twice. A friends required urgent help so i didnt continue the process. After waking up in the morning, I decided to continue the process. I flashed the next file i was supposed to after formatting /cache and Dalvik cache.
Now i cant boot. The phone stay stuck at the galaxy y splsh screen. I can boot into recovery. It says /cache/recovery/log cant be open. Also, it cant mount /cache/recovery/last_log
Cant open /cache/recovery/last_log
I have ADB but it seems I didnt enable the USB debuggin option. If that was possible, I could have flashed a stock kernel and tried again.
Are you sure you cant enter download mode (HOLD power+home+volume DOWN)? Remove backcase if you have, remove the battery , keep aside for 5 min, then put it back and hold the download mode combination
DiGtal said:
I wanted to try Merruk's kernel so I download the 4 files that are to be used. I flashed KernelUpdate.zip first and rebooted twice. A friends required urgent help so i didnt continue the process. After waking up in the morning, I decided to continue the process. I flashed the next file i was supposed to after formatting /cache and Dalvik cache.
Now i cant boot. The phone stay stuck at the galaxy y splsh screen. I can boot into recovery. It says /cache/recovery/log cant be open. Also, it cant mount /cache/recovery/last_log
Cant open /cache/recovery/last_log
I have ADB but it seems I didnt enable the USB debuggin option. If that was possible, I could have flashed a stock kernel and tried again.
Click to expand...
Click to collapse
just flash back to stock via odin
i advise you not to use the "ext4.zip"
use only the system 1.0.8 zip <-- extract to sdcard
hitme987 said:
Are you sure you cant enter download mode (HOLD power+home+volume DOWN)? Remove backcase if you have, remove the battery , keep aside for 5 min, then put it back and hold the download mode combination
Click to expand...
Click to collapse
So THATS how you enter download mode
leodasal2 said:
just flash back to stock via odin
i advise you not to use the "ext4.zip"
use only the system 1.0.8 zip <-- extract to sdcard
Click to expand...
Click to collapse
Well, I flashed my backup and it rebuilt the /cache. All is fine. Thank you.
A new problem has risen. I was trying to flash Creed v4.0.
I had Merruk's Kernel.
I did a reset and tried flashing the ROM. It started wiping the /system partition and came across with an error in /boot(Error 7). Im guessing its due to the kernel. It aborted.
I tied again by doing a data reset again thinking that there might have be a random error in the wiping process.
It started cleaning /data. The progress bar never moved. I waited for 15 mins and did a battery pull. When i try to boot into the recovery mode, it stays at the Galaxy Y logo.
Dowload mode works. Adb doesnt detect my device though. I wonder why.
DiGtal said:
So THATS how you enter download mode
Well, I flashed my backup and it rebuilt the /cache. All is fine. Thank you.
A new problem has risen. I was trying to flash Creed v4.0.
I had Merruk's Kernel.
I did a reset and tried flashing the ROM. It started wiping the /system partition and came across with an error in /boot(Error 7). Im guessing its due to the kernel. It aborted.
I tied again by doing a data reset again thinking that there might have be a random error in the wiping process.
It started cleaning /data. The progress bar never moved. I waited for 15 mins and did a battery pull. When i try to boot into the recovery mode, it stays at the Galaxy Y logo.
Dowload mode works. Adb doesnt detect my device though. I wonder why.
Click to expand...
Click to collapse
There is no Creed 4 for galaxy y...re flash to stock and flash Creed 3.5
I cant boot into recovery. How do I use the download mode to do so?
Edit: I installed the correct drivers for my phone while it was trying to restart(it didnt ofcourse). I booted into download mode and connected odin. Odin is not showing any signs of it connecting to the phone.
Edit2: Got it working(v1.85). I need bootloader, CSC, Modem and phone tar balls. i downloaded 2 rar files but they dont have Phone and bootloader tar balls
DiGtal said:
I cant boot into recovery. How do I use the download mode to do so?
Edit: I installed the correct drivers for my phone while it was trying to restart(it didnt ofcourse). I booted into download mode and connected odin. Odin is not showing any signs of it connecting to the phone.
Edit2: Got it working(v1.85). I need bootloader, CSC, Modem and phone tar balls. i downloaded 2 rar files but they dont have Phone and bootloader tar balls
Click to expand...
Click to collapse
Hi. Make sure you have the the drivers installed correctly. Try the one from this thread. http://forum.xda-developers.com/showthread.php?t=961956 credits to SamHaLeKe. if you have an existing driver uninstall if first, reboot your pc then install the new one. you can download stock ROMS from this thread and its complete. http://forum.xda-developers.com/showthread.php?t=1465800 credits to Doky73. If everything is ok when your phone is in download mode ODIN should be able to detect it.
Thank you all!
You have been of great help.
My phone is running fine now.
Just waiting for Merruk's kernel to get overcloking capability.
DiGtal said:
Thank you all!
You have been of great help.
My phone is running fine now.
Just waiting for Merruk's kernel to get overcloking capability.
Click to expand...
Click to collapse
Nope. There is no stable overclocking capability yet and merruk is outdated. I recommend to use kuros kernel or savies rev 73
Phone Not booting
hitme987 said:
Nope. There is no stable overclocking capability yet and merruk is outdated. I recommend to use kuros kernel or savies rev 73
Click to expand...
Click to collapse
Hello,
I have same problem,When I want to Install Stock ROM with ODIN error shows ""
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
""
and when I go to "Android System Recovery" (vol up + home bot + power bot) and choose Wipe data/factory reset OR wipe cache partition, Error Show "Failed to mount /Cache (invalid argument) " & "Can't mount /cache/recovery/lastlog"
What should I do?
Stock+
The mission of this ROM is to keep fairly close to the stock experience while unlocking certain features and limitations.
Furthermore my plan is to remove useless or intrusive customizations done by the manufacturer or carrier.
The kernel will have few commits, but those that are there will be for stability, battery life.
Click to expand...
Click to collapse
FEATURES
Prerooted.
Deodexed.
APNs are unlocked.
Preload data is restored.
Zipaligned.
CarrierIQ removed
**Stock kernel until I get time to pull the latest source.**
wp_mod for stock kernel thanks to @flar2
Insecure ADB (Always runs as root).
Tether Enabled
Click to expand...
Click to collapse
INSTALL
Data wipe is not required if you are coming from stock, BUT if you do wipe data do it BEFORE flashing the ROM.
Wipe /data/... or not.
Flash with TWRP.
Go into APNs and change the Default from IPV6 to IPV4.
Click to expand...
Click to collapse
Again, Thanks to @flar2 for his wp_mod.
DOWNLOAD
Latest:
HTC 1.57 OTA
OLD:
Stock+v1.01 SHA1: bc39bda6f656e323ea725f77dca0c4a3212d1044
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Please do not PM me with images of farm equipment.
CHANGELOG:
1.01 -> 1.1 (unreleased)
Added init.d support.
Full write perms to external SD.
Rebuilt framework-res with the APN changes cooked in.
Email without exchange policy enforcement. (This will probably be a flashable option.)
1.0 -> 1.01
Fixed an issue with a symlink breaking wifi. Thanks to @Andromorphone for sitting on IRC for testing the fix for this with me.
1.0
Initial release.
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
Thank you so much for this!!
EDIT: Are the links broken?
EDIT 2: Downloading now. Thanks again!
Sent from my HTC One M8
VolcanicSkunk said:
Thank you so much for this!!
EDIT: Are the links broken?
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
They were indeed. It's fixed now.
Annnd It's back to bed for me. I'll repost the mega mirror in the morning.
EDIT 2: This issue was solved. Did not brick my phone. Didn't want this post to scare anyone away from a great ROM.
Think I just bricked my phone flashing this. Downloaded, confirmed hash sum, flashed via TWRP 2.7.0.2. Now phone is stuck at HTC splash screen. No amount of holding the power button will turn it off.
EDIT: Got a tip that said to hold the power and volume down buttons under a light source to try to get it to boot to bootloader. No luck.
VolcanicSkunk said:
Think I just bricked my phone flashing this. Downloaded, confirmed hash sum, flashed via TWRP 2.7.0.2. Now phone is stuck at HTC splash screen. No amount of holding the power button will turn it off.
EDIT: Got a tip that said to hold the power and volume down buttons under a light source to try to get it to boot to bootloader. No luck.
Click to expand...
Click to collapse
Hold power button and volume up, untill the phone shuts off
LIL_ROOKIE said:
Hold power button and volume up, untill the phone shuts off
Click to expand...
Click to collapse
Got pretty much the same advice in a thread I made in Q&A. Thanks for the tip though. That's exactly what I had to do. Don't know if the light source makes a difference though.
Finally got it to work. I had to hold volume up + power under a light source to get the phone to reboot. When the screen turned black I changed to the volume down while still holding the power button. This booted me to HBOOT. Then I was able to select recovery and boot there just fine. I am now restoring to my stock backup.
VolcanicSkunk said:
Got pretty much the same advice in a thread I made in Q&A. Thanks for the tip though. That's exactly what I had to do. Don't know if the light source makes a difference though.
Finally got it to work. I had to hold volume up + power under a light source to get the phone to reboot. When the screen turned black I changed to the volume down while still holding the power button. This booted me to HBOOT. Then I was able to select recovery and boot there just fine. I am now restoring to my stock backup.
Click to expand...
Click to collapse
Well, that certainly should not have happened, I am downloading from the link right now. I'll see if I can reproduce the error.
*EDIT*
So, I just did both a dirty flash, and a flash with a /data/ wipe. (A FULL data wipe, sadly.)
Phone booted fine in both cases.
Are you flashing over from a completely stock ROM?
What is your s-off satatus?
If you didn't flash from a fullty stock ROM, and did not wipe /data/ then the system was probably choking on a different SQLite schema. Doing a /data/ wipe before flashing the zip should do the trick.
Fenny said:
Well, that certainly should not have happened, I am downloading from the link right now. I'll see if I can reproduce the error.
*EDIT*
So, I just did both a dirty flash, and a flash with a /data/ wipe. (A FULL data wipe, sadly.)
Phone booted fine in both cases.
Are you flashing over from a completely stock ROM?
What is your s-off satatus?
If you didn't flash from a fullty stock ROM, and did not wipe /data/ then the system was probably choking on a different SQLite schema. Doing a /data/ wipe before flashing the zip should do the trick.
Click to expand...
Click to collapse
Hmmm.... That's strange.
I am coming from the stock operating system. I haven't restored the preload data yet. That was one of the reasons I was flashing this (so I didn't have to restore it manually). I am S-Off using Dev Unlock, TWRP + SuperSU & Root, then Firewater.
Here is my flash process:
Download from link in OP with phone to internal storage (/storage/emulated/legacy/download/)
Confirm hash using Hash Droid from Play Store
Reboot to Recovery using Quick Boot from Play Store (TWRP 2.7.0.2)
Select Wipe
Select Advanced
Checked options for system, data, Dalvik cache, cache
Slid to wipe
Repeated wipe with same options
Pressed home button
Selected Install
Chose internal memory
Navigated to /download/
Installed ROM
Since I'm at work I stopped paying attention to the screen after that since last night I had successfully flashed ViperOneM8. I didn't like the UI changes to ViperOneM8, so I restored my stock TWRP backup.
VolcanicSkunk said:
Hmmm.... That's strange.
I am coming from the stock operating system. I haven't restored the preload data yet. That was one of the reasons I was flashing this (so I didn't have to restore it manually). I am S-Off using Dev Unlock, TWRP + SuperSU & Root, then Firewater.
Here is my flash process:
Download from link in OP with phone to internal storage (/storage/emulated/legacy/download/)
Confirm hash using Hash Droid from Play Store
Reboot to Recovery using Quick Boot from Play Store (TWRP 2.7.0.2)
Select Wipe
Select Advanced
Checked options for system, data, Dalvik cache, cache
Slid to wipe
Repeated wipe with same options
Pressed home button
Selected Install
Chose internal memory
Navigated to /download/
Installed ROM
Since I'm at work I stopped paying attention to the screen after that since last night I had successfully flashed ViperOneM8. I didn't like the UI changes to ViperOneM8, so I restored my stock TWRP backup.
Click to expand...
Click to collapse
I'll try again following your process precisely. Perhaps dexopt is cowardly refusing to build the dalvik cache when /cache/ has been wiped. (This happens from time to time if there was a bad deodex.) I'll let you know how it goes.
Fenny said:
I'll try again following your process precisely. Perhaps dexopt is cowardly refusing to build the dalvik cache when /cache/ has been wiped. (This happens from time to time if there was a bad deodex.) I'll let you know how it goes.
Click to expand...
Click to collapse
Thanks so much for checking into it! I'll try it again tomorrow when I've got a lot more time on my hands. I'm just too used to flashing on the fly.
VolcanicSkunk said:
Thanks so much for checking into it! I'll try it again tomorrow when I've got a lot more time on my hands. I'm just too used to flashing on the fly.
Click to expand...
Click to collapse
Well, I did exactly the same thing as you did. I even went and downloaded the same rebooter app. The phone booted with no issue.
@Andromorphone Come back me up here. I KNOW you got it booting as well.
Whelp, I really must have done something screwy. Lol. Like I said, I'll try it again tomorrow (or late tonight if I get a chance). I'm just glad that everything works! I was hoping that no one else had the same problems I did. When I try it again I'll post back with my results. Hopefully it goes well without any hitches.
VolcanicSkunk said:
Whelp, I really must have done something screwy. Lol. Like I said, I'll try it again tomorrow (or late tonight if I get a chance). I'm just glad that everything works! I was hoping that no one else had the same problems I did. When I try it again I'll post back with my results. Hopefully it goes well without any hitches.
Click to expand...
Click to collapse
Ha! Figured it out. Disable zip signature verification. It looks like it didn't sign right but as long as the sha1 matches you should be fine.
*EDIT*
The link in the OP has a valid signature again.
Fenny said:
Well, I did exactly the same thing as you did. I even went and downloaded the same rebooter app. The phone booted with no issue.
@Andromorphone Come back me up here. I KNOW you got it booting as well.
Click to expand...
Click to collapse
indeed, flashed the initial v1.0 and subsequent version 1.01 and never had any issues booting. in fact it's working great, and very happy to be rid of carrierIQ and to have working tether.
Sent from my HTC One_M8 using Tapatalk
I am able to replicate this freeze several times.
Steps:
Downloaded ROM onto PC
Powered phone off
Ejected MicroSD card
Plugged MicroSD card into computer (USB 2.0)
Checked SHA1 hash via MD5 & SHA Checksum Utility 2.1
- Returned "SHA-1 Hash matched."
Transferred ROM to root of MicroSD card
Checked SHA1 hash again
- Returned "SHA-1 Hash matched."
Properly ejected MicroSD from PC
Reinserted MicroSD card into my M8
Booted phone and waited for it to settle
Connected phone to PC via stock USB
Confirmed Connection using "adb devices"
Rebooted phone to recovery using "adb reboot recovery"
In recovery performed the same wipe process outlined earlier
- Checked: Dalvik Cache, System, Cache, Data
- Repeated
Installed ROM from MicroSD card
Pressed Wipe Dalvik/Cache button
Phone rebooted to splash. Hung for 2+ minutes.
Rebooted to recovery via HBOOT.
Wiped again. This time included internal memory.
Installed ROM from MicroSD card
Received an Install Successful message
Pressed Reboot System
Received a warning there was no OS installed
Accidentally pressed reboot anyway
Prompted to install SuperSU since it wasn't detected (lol)
At hanging splash screen rebooted to HBOOT then recovery again
Performed single wipe
Installed from MicroSD card (again)
Install process took significantly longer than prior
Received Install Successful message
Pressed Reboot System
Screen froze while Reboot System button was highlighted
Phone booted through splash to boot animation
I am now sitting at the Welcome screen
I'm not sure if the fact that I was wiping a second time was causing some issue, but this was just a weird process. lol. After the first or second hang (I don't remember which) I exported the recovery log to the MicroSD card. I attached it to the post so hopefully it might shed some light as to what was going on.
Everything seems to have worked though. I'll go through the setup process and get back with you if there are or aren't any issues.
Thanks again for going through the same process I went through so I knew it was probably a fluke. Hopefully this is an isolated incident.
Anyway... :highfive:
VolcanicSkunk said:
*snip*
In recovery performed the same wipe process outlined earlier
- Checked: Dalvik Cache, System, Cache, Data
- Repeated
Installed ROM from MicroSD card
Pressed Wipe Dalvik/Cache button
Phone rebooted to splash. Hung for 2+ minutes.
Rebooted to recovery via HBOOT.
Wiped again. This time included internal memory.
Installed ROM from MicroSD card
Received an Install Successful message
Pressed Reboot System
Received a warning there was no OS installed
*snip*
Click to expand...
Click to collapse
Okay, I think there may be some sort of problem with TWRP and mounts/storage.
This tells me that your system partition was completely blank upon the last boot reboot:
/system | /dev/block/mmcblk0p45 | Size: 2641MB Used: 42MB Free: 2599MB Backup Size: 42MB
I have two working theories at the moment. The first is that IO was hanging when reading from your ext-sd, and then the system locked up IRQ style.
The second I think is more likely and involves the /system/ mount point. I wonder if after the second wipe, the /system/ partition was not actually mounted. It would mean that the script would flash to the tmpfs that is created for the root partition, and the files would go precisely nowhere.
The second could be proven by looking at the /data/preloads folder right after a non-booting scenario. If it exists and there are files there, then the data partiton mounted just fine, while the system partition did not.
*EDIT*
Battery is looking gooood.
Anyone not able to send or receive mms when apn switched to ip4/ip6?
Sent from my HTC One_M8 using Tapatalk
Same here
Sent from my HTC One_M8 using XDA Premium 4 mobile app
After wiping my phone to re-install the ROM i am using (due to issues) i am getting the e /system not mounted error when flashing. I am on a SM-705 using TWRP 2.8 recovery
What i tried so far:
1) Reboot to recovery and try again
2) Reformat the system partition in TWRP
I read somewhere that installing CWM may help.
I also read that installing the stock rom (which i cannot find) via odin will also resolve the issue.
I am unsure on how to proceed, please help!
1H4X3R said:
After wiping my phone to re-install the ROM i am using (due to issues) i am getting the e /system not mounted error when flashing. I am on a SM-705 using TWRP 2.8 recovery
What i tried so far:
1) Reboot to recovery and try again
2) Reformat the system partition in TWRP
I read somewhere that installing CWM may help.
I also read that installing the stock rom (which i cannot find) via odin will also resolve the issue.
I am unsure on how to proceed, please help!
Click to expand...
Click to collapse
2) Reformat or wipe?
ashyx said:
2) Reformat or wipe?
Click to expand...
Click to collapse
Reformat, Wipe --> System (checked) --> Reformat --> FAT
1H4X3R said:
Reformat, Wipe --> System (checked) --> Reformat --> FAT
Click to expand...
Click to collapse
FAT? It should be Ext4.
ashyx said:
FAT? It should be Ext4.
Click to expand...
Click to collapse
Thanks. I just tried Ext4 format but it didn't help either. I was following this guide: https://www.youtube.com/watch?v=VJRKuQf0puE
Anything i can do to resolve this?
1H4X3R said:
Thanks. I just tried Ext4 format but it didn't help either. I was following this guide: https://www.youtube.com/watch?v=VJRKuQf0puE
Anything i can do to resolve this?
Click to expand...
Click to collapse
What is telling you it cannot mount system? Post your recovery.log after getting this error.
Sent from my SM-T280 using XDA-Developers mobile app
Not sure how to do that so i took some screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You need to post the recovery.log. Hit the advanced button then save recovery log.
Post it here as a file or on pastebin.com
Also you realise you are using an outdated version of twrp?
Sent from my SM-T280 using XDA-Developers mobile app
This is the only version of TWRP i could find for my Tablet. It worked just fine for ~ 5 times (installing ROMs 5 times). If you know where i could find a newer version for a SM-705 Tablet please let me know.
Here is the recovery.log file (clicking the attachment pin didn't seem to do anything so i uploaded it this way): https://puu.sh/qgqUb/c0db2985d3.log
1H4X3R said:
This is the only version of TWRP i could find for my Tablet. It worked just fine for ~ 5 times (installing ROMs 5 times). If you know where i could find a newer version for a SM-705 Tablet please let me know.
Here is the recovery.log file (clicking the attachment pin didn't seem to do anything so i uploaded it this way): https://puu.sh/qgqUb/c0db2985d3.log
Click to expand...
Click to collapse
You're a bit behind the times. I have updated twrp several times since.
http://forum.xda-developers.com/showthread.php?t=3074633
I have looked at your recovery log.
Your system partition is not mounting.
This is probably due to incorrect formatting.
You should be able to format it with the wipe options in twrp. Ensure you select ext4 as the partition type.
Wipe>advanced wipe>system>repair or change file system>change file system>EXT4
After formatting try and mount the system partition.
If you can't post the recovery.log again before rebooting.
Sent from my SM-T280 using XDA-Developers mobile app
ashyx said:
You're a bit behind the times. I have updated twrp several times since.
http://forum.xda-developers.com/showthread.php?t=3074633
Sent from my SM-T280 using XDA-Developers mobile app
Click to expand...
Click to collapse
Ok. I will try this and let you know if i am still getting the error. Thanks.
1H4X3R said:
Ok. I will try this and let you know if i am still getting the error. Thanks.
Click to expand...
Click to collapse
See my edits.
Sent from my SM-T280 using XDA-Developers mobile app
ashyx said:
You're a bit behind the times. I have updated twrp several times since.
http://forum.xda-developers.com/showthread.php?t=3074633
I have looked at your recovery log.
Your system partition is not mounting.
This is probably due to incorrect formatting.
You should be able to format it with the wipe options in twrp. Ensure you select ext4 as the partition type.
Wipe>advanced wipe>system>repair or change file system>change file system>EXT4
After formatting try and mount the system partition.
If you can't post the recovery.log again before rebooting.
Sent from my SM-T280 using XDA-Developers mobile app
Click to expand...
Click to collapse
After flashing to the new TWRP and reformatting system i made a log file. However, when i insert the SD card in the computer no .log file is there. On TWRP it does say that a log file has been created on the microSD card so idk what is going on.
Update 1: I managed to get a log file after trying to copy log multiple times (this is not after a reformat, that log will come shortly): http://puu.sh/qgLxV/0619e7bb21.log
Update 2: Here is the log from right after the reformat: http://puu.sh/qgLMB/bd38991df8.log
Update 3: When reformatting, i used to receive the error: could not mount system (or similar) but this time i didn't. So i tried to install a ROM but i got the same error as before:
I also got this message twice (now i don't get it anymore):
Your system partition is now mounting.
Make sure 'keep system read only' is not checked under MOUNT.
Your zip should now install.
Sent from my SM-T280 using XDA-Developers mobile app
ashyx said:
Your system partition is now mounting.
Make sure 'keep system read only' is not checked under MOUNT.
Your zip should now install.
Sent from my SM-T280 using XDA-Developers mobile app
Click to expand...
Click to collapse
Well i just tried again, (making sure that system read only is unchecked) and now i am getting the red failed to mount system again. Here is a link to the log (after reformatting and getting the red error message): https://puu.sh/qhotb/348f762b45.log
I tried once again after a restart to reformat but i get the same error (in red text), i did not get this the last few times but i did get this before.
When trying to install the ROM this time, i get no failed to mount error BUT it is still stuck, as in it doesn't install the ROM but rather is stuck at extracting package.
Here is an image of the problem:
You are actually waiting for it to extract the files to system?
Just because it doesn't show progress it doesn't mean it's not happening.
Sent from my SM-T280 using XDA-Developers mobile app
ashyx said:
You are actually waiting for it to extract the files to system?
Just because it doesn't show progress it doesn't mean it's not happening.
Sent from my SM-T280 using XDA-Developers mobile app
Click to expand...
Click to collapse
I let it run overnight and it was still stuck on the same screen when i checked in the morning (typically the blue bar fills up slowly from 0-100%, now it is just stuck at 0% solid blue color bar).
I just tried again and i am getting the "unmount of /system failed" error again. When i try to reformat i get a very similar error in red text.
1H4X3R said:
I let it run overnight and it was still stuck on the same screen when i checked in the morning (typically the blue bar fills up slowly from 0-100%, now it is just stuck at 0% solid blue color bar).
I just tried again and i am getting the "unmount of /system failed" error again. When i try to reformat i get a very similar error in red text.
Click to expand...
Click to collapse
Can you post your recovery.log AFTER trying to install the rom?
Sent from my SM-T280 using XDA-Developers mobile app
ashyx said:
Can you post your recovery.log AFTER trying to install the rom?
Sent from my SM-T280 using XDA-Developers mobile app
Click to expand...
Click to collapse
I can only get a recovery.log after a restart as i cannot exit the installer without completely shutting down the device. I can however provide you with a log of after an attempted reformat (which i have done already).
(Huge) Update: I found a recovery file on my computer for the tab that is super old, back when i used to run a 4.4.2 custom ROM on it and i restored from that and it works. However, that specific custom ROM does not have a networking driver (or something of that sort, i cannot connect to my cellular provider) and i want to install the newer 5.0.2 custom ROM i was using before but i don't want to risk another error mounting /system :/ The ROM i used is this one, hope you can help me find a way to get cellular service: selambA ROM.
Update 2: I cannot connect to any google services or anything related to google when i restored the selambA ROM.
Update 3: I tried to reinstall the 5.0.2 ROM but i am getting the same, unmount of /system error :/
1H4X3R said:
I can only get a recovery.log after a restart as i cannot exit the installer without completely shutting down the device. I can however provide you with a log of after an attempted reformat (which i have done already).
(Huge) Update: I found a recovery file on my computer for the tab that is super old, back when i used to run a 4.4.2 custom ROM on it and i restored from that and it works. However, that specific custom ROM does not have a networking driver (or something of that sort, i cannot connect to my cellular provider) and i want to install the newer 5.0.2 custom ROM i was using before but i don't want to risk another error mounting /system :/ The ROM i used is this one, hope you can help me find a way to get cellular service: selambA ROM.
Update 2: I cannot connect to any google services or anything related to google when i restored the selambA ROM.
Update 3: I tried to reinstall the 5.0.2 ROM but i am getting the same, unmount of /system error :/
Click to expand...
Click to collapse
You can pull the log from cache/recovery/last_log after rebooting, but it may not get created if you are hard resetting the device.
Do you know how to use adb?
Sent from my SM-T280 using XDA-Developers mobile app