Related
I have rooted and flashed CM6 on my N1 and the ROM Managers backup tool HAD been working fine. However now I can't flash new Rome or backup. If I try to, it instantly reboots and loads the recovery. I haven't lost any data, but I can't exactly update things or experiment with new ROMs anymore which saddens me.
Any help or suggestions? Anyone else with the same problem?
Sent from my Nexus One using XDA App
fixed!
i dont know what the problem was, but it was something to do with the latest version of clockwork recovery. i just flashed an older one and it worked fine. i guess ill just wait for a fix on that newer version
Hi
I've upgraded to 2.3.3 and my camera doesnt work anymore. The screen comes black for a few seconds and then the message "Camera error. Cannot connect to camera" appears. The flashlight is also doesnt work. I have some MoDaCo firmware HTC Sense before, as I remember...
Help me to fix it, please.
Thanks
Flash newer radio.
Jack_R1 said:
Flash newer radio.
Click to expand...
Click to collapse
Could you tell me how to do it, pls? What is the last version of radio? How to check it?
Settings / About / Baseband
If the version is 4.06 / 5.08 / 5.12 (the version is in the middle of the long string there) - then there's some other problem in the system. If the version is 4.02 or 4.04 - then you need to go to Developers forum, open any Gingerbread ROM thread, and see the instructions for flashing Radio. Or look at my signature.
Jack_R1 said:
Settings / About / Baseband
If the version is 4.06 / 5.08 / 5.12 (the version is in the middle of the long string there) - then there's some other problem in the system. If the version is 4.02 or 4.04 - then you need to go to Developers forum, open any Gingerbread ROM thread, and see the instructions for flashing Radio. Or look at my signature.
Click to expand...
Click to collapse
The Baseband Version is 32.41.00.32U_5.08.00.04
What I'm thinking is could it be the problem because my Nexus had non original firmware before the GB update, and maybe I didnt make some important thing which blocking my camera now? Maybe I need to re-flash the radio with some original image? I'm totally NOOB in all these things...
Your radio is 5.08 - which means it's updated and the problem is elsewhere.
If you didn't upgrade to Gingerbread from a clean FRG83G build, but from some other build - you'll need to reflash the ROM. You can do it if you have unlocked bootloader. Read Wiki, it has the guide for installing custom ROMs - execute it, and use Gingerbread stock build from one of the threads in Development forum.
Jack_R1 said:
Your radio is 5.08 - which means it's updated and the problem is elsewhere.
If you didn't upgrade to Gingerbread from a clean FRG83G build, but from some other build - you'll need to reflash the ROM. You can do it if you have unlocked bootloader. Read Wiki, it has the guide for installing custom ROMs - execute it, and use Gingerbread stock build from one of the threads in Development forum.
Click to expand...
Click to collapse
Thanks for your advices. Just upgraded the radio to 5.12 via fastboot. The camera still not work Will try to flash to original state...
ok, i've tried to rollback to original FRG83, se-flashed boot, recovery, but no luck - camera didnt started. Hovewer, i tried the flashlight torch and it started to work (it didn't like a camera before), so I'm sure now the camera issue is the software now - not a hardware.
Does anybody have some advices?
P0MkA said:
ok, i've tried to rollback to original FRG83, se-flashed boot, recovery, but no luck - camera didnt started. Hovewer, i tried the flashlight torch and it started to work (it didn't like a camera before), so I'm sure now the camera issue is the software now - not a hardware.
Does anybody have some advices?
Click to expand...
Click to collapse
How did you flash frg83? via passimg or you flashed rooted rom from dev section? If you didn't use passimg method you should try wiping everything (cache, dalvik, factory reset) from the recovery.
BTW, if you have custom recovery you should be able to restore nandroid backup (which I assume you did;P ) and see if there is this problem too.
Cheers!
k_myk said:
How did you flash frg83? via passimg or you flashed rooted rom from dev section? If you didn't use passimg method you should try wiping everything (cache, dalvik, factory reset) from the recovery.
BTW, if you have custom recovery you should be able to restore nandroid backup (which I assume you did;P ) and see if there is this problem too.
Cheers!
Click to expand...
Click to collapse
i've flashed frg83 using fastboot. And updated to 2.3.3 via recovery (RA-passion-v2.2.1). And yes, I wiped everything using the recovery. Unfortunately, I do not know what is nandroid backup, so I didnt do it
Hope there is a way to get my camera back to work... Could you tell me what to do, step by step, to make my Nexus fully functional with the 2.3.3 firmware, please!
P0MkA said:
i've flashed frg83 using fastboot. And updated to 2.3.3 via recovery (RA-passion-v2.2.1). And yes, I wiped everything using the recovery. Unfortunately, I do not know what is nandroid backup, so I didnt do it
Hope there is a way to get my camera back to work... Could you tell me what to do, step by step, to make my Nexus fully functional with the 2.3.3 firmware, please!
Click to expand...
Click to collapse
I'd love to, but unfortunately I don't know what causes this problem at the moment I think it wouldn't hurt to try loging what is going on when you open camera.apk. Try adb logcat from your pc or install "alogcat" from market, start camera app and paste here the log file.
Lesson for future always do nandroid backup You can do this from recovery, it will do phone's memory image Then you can always revert back to what you had before flashing new rom
k_myk said:
I'd love to, but unfortunately I don't know what causes this problem at the moment I think it wouldn't hurt to try loging what is going on when you open camera.apk. Try adb logcat from your pc or install "alogcat" from market, start camera app and paste here the log file.
Lesson for future always do nandroid backup You can do this from recovery, it will do phone's memory image Then you can always revert back to what you had before flashing new rom
Click to expand...
Click to collapse
Yeah... backuping is a cool thing.... It is just my first experience with the Android phone... Maybe will find some kind of solution for this...
Well... Problem stays... However I've found few interesting things. As I've mentioned above, after the 2.3.3 update the camera and flashlight doesnt work enymore. But I've installed Z-DeviceTest and found that after the reboot this app (which provides the hardware test) sees the camera and flashlight! But, unfirtunately, doesnt able to test it. Moreover, if to start some torchlight widget directly after the reboot, the flashlight works!!! But it is not after the camera start... So, maybe someone will find this information useful.
@Pomka
have you found the Satu Solution yet ?
mmm. i guess you borrow from somebody the nandroid back up and restore it...
then u will know whether it is a hardware issue or Software Issue.
Logic ?
sevensaints said:
@Pomka
have you found the Satu Solution yet ?
mmm. i guess you borrow from somebody the nandroid back up and restore it...
then u will know whether it is a hardware issue or Software Issue.
Logic ?
Click to expand...
Click to collapse
Stupid actually. Its stay the same, not working....
found the solution!
http://forum.xda-developers.com/showthread.php?t=717870&highlight=frf91
You have go go back to stock ROM.....then camera Happy Trigger Finger!
yeah...
1. Go back to stock through HBOOT
2. Flash back ur fav ROM - mine-MIUI AU
pls click thanks
I need a bit of urgent advice if possible. Having waited patiently for Samsung to release ICS for the P7310 which has never appeared in the UK, I'm trying to flash to JB (latest AOSP version) from the stock 3.2.
I've installed CWMOD 5.5.0.4 ok, and copied the update rom and gapps to the root of the tab. I've gone into CWMOD recover mode, wipe/reset and then selected the rom to install. It starts the install, then fails with the system error 7 message (seems to be fairly common). It obviously started the install but now I don't seem to be able to boot the tab into 3.2 anymore, it just sits at the boot logo and doesn't get any further. I'm happy to try another ROM (maybe CM10), but I need to transfer it to the device first, and ofcourse I can't do this within windows at the moment. Odin still runs and can talk to the tab, but I'm a bit lost at the moment.
I'm a bit new to all this, so could really do with some help.
Flash the stock Rom.with Odin. You can find it at sammobile.com. it'll bring you back to stock.and.you can start over again. You're soft bricked right now.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Cool. Thanks for that. I guess I just select the PDA option in Odin, and let it do its thing.
Any idea why this happens? I'd read a couple of threads about going from HC to ICS first, then to JB. Is this a requirement, or optional?
I'ver had similar problems finding a Rom that works on my i957. Never did find an ics that worked. I'm running jb from nrvate, but I think its specific to the i957. And, yes, flash just like you did the cm recovery.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Really appreciate the replies. I've managed to get the tab back working under 3.2 (stock rom downloaded from SamFirmware), so that's a start. I still want to upgrade to JB if possible (or ICS if not). Am I likely to experience the same problem again? Is it worth going to ICS first? I've downloaded the stock US ICS rom, which i can flash using Odin. I can't see why this wouldn't work on a UK spec 8.9 wifi, but can anyone confirm if it does?
So, I'm back at square one, but really want to try and get this sorted.
Did you do a clean install when you tried to flash the jb Rom? I.e. factory reset, format/clear system and data. If not that probably is the problem. There should not be any benefit of flashing ics before jb. The one difference between the two is you most likely will have to flash a gapps (Google apps) package after the the jb flash. Not sure where you got the Rom, but the developer should have the gapp they recommend and instruction on how to do the flash. Every jb to Rom I've flashed has the gapps package flashed after the Rom and before rebooting.
I'd stick with a Rom specific for your device. I hard bricked my phone with the wrong Rom once. The US Rom probably does not have the correct radio for.you in the UK. I only use WiFi so don't care too much if I have the right radio or.not.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
jd1639 said:
Did you do a clean install when you tried to flash the jb Rom? I.e. factory reset, format/clear system and data. If not that probably is the problem. There should not be any benefit of flashing ics before jb. The one difference between the two is you most likely will have to flash a gapps (Google apps) package after the the jb flash. Not sure where you got the Rom, but the developer should have the gapp they recommend and instruction on how to do the flash. Every jb to Rom I've flashed has the gapps package flashed after the Rom and before rebooting.
I'd stick with a Rom specific for your device. I hard bricked my phone with the wrong Rom once. The US Rom probably does not have the correct radio for.you in the UK. I only use WiFi so don't care too much if I have the right radio or.not.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
I've just tried again, and have hit the same problem, and have tried the AOSP rom and the CM10 rom this time. I did a wipe/factory reset beforehand, but the installer starts then just aborts with 'symlink: some symlinks failed' E:Error in /sdcard/<rom file name> (Status 7). Obviously the tab 8.9 doesn't have an sd card slot, but I thought the rom must be aware of this.
Where am I going wrong?
You might try to flash a different version of cwm I don't remember now how I found this link, but here is a link for Overcome_CWM_Recovery_v5.1.2.6_P73xx.tar
http://www.sendspace.com/file/507gjv
just flash in Odin, like the ROM itself (in PDA section)
I use twrp but don't know where to find a version for your p7310.
Have you tried a different Rom
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
You have a /sdcard directory despite the fact you have no physical external sdcard.
I had the same problem. Found this solution:
http://forum.xda-developers.com/showthread.php?t=1973712
tman24 said:
I've just tried again, and have hit the same problem, and have tried the AOSP rom and the CM10 rom this time. I did a wipe/factory reset beforehand, but the installer starts then just aborts with 'symlink: some symlinks failed' E:Error in /sdcard/<rom file name> (Status 7). Obviously the tab 8.9 doesn't have an sd card slot, but I thought the rom must be aware of this.
Where am I going wrong?
Click to expand...
Click to collapse
harry_fine said:
You have a /sdcard directory despite the fact you have no physical external sdcard.
I had the same problem. Found this solution:
http://forum.xda-developers.com/showthread.php?t=1973712
Click to expand...
Click to collapse
If reading that reply right, one specific stock rom does what's necessary, trouble is, that's a US stock rom, and I'm in the UK. Already had it confirmed that it wouldn't be good to install a US rom on a UK tab. Loads of people has flashed their tabs, so it can't be that difficult! I've just tried Overcome CwM v5.2.1.6 with the same AOSP and CM10 roms, but same error
Ok, silly question time, but does the tab need to be rooted to install these new roms successfully?
You don't need to be rooted, just the recovery installed. Not sure why you're having problems now other than I had a hell of a time getting a Rom installed too. I'd try a different Rom. I tried some yesterday and didn't get any of them to work well. At least you've learned how to recover from a soft brick. I've learned that lesson too, to many times!
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
I'd try to download CM10 again. As i see in the error message there is a problem with the zip, maybe caused by error in downloading?
tman24 said:
If reading that reply right, one specific stock rom does what's necessary, trouble is, that's a US stock rom, and I'm in the UK. Already had it confirmed that it wouldn't be good to install a US rom on a UK tab. Loads of people has flashed their tabs, so it can't be that difficult! I've just tried Overcome CwM v5.2.1.6 with the same AOSP and CM10 roms, but same error
Click to expand...
Click to collapse
Hi, dont know if this will help, but I have flashed the US ICS rom on my Swiss Tab 8.9, with no problems. There should be no issue with worrying about the wrong radio as stated previously, as the 7310 is the WIFI only model, so there should be no issue with 3G. The only thing which causes some issues is the screen flicker issue. If you flash the US gingerbread first, then the ICS, it seems to solve the issue. For mor info check out this thread http://forum.xda-developers.com/showthread.php?t=1573548&page=50
Good luck!
Aaarrgggh! Frustrating, now I'm just getting 'hardware id not found' when I connect the tab to the PC!!! I can browse the device in Windows, but of course, Odin won't connect. How difficult can this really be!
I've already uninstalled and re-installed the Samsung USB drivers, tried a different USB port etc, but same result.
As it stands, the tab is working, but on that horrible v3.2.
I might be getting somewhere, but nothing's easy! I have moved everything over to a laptop we have, and have gone through the whole process again. I installed CwM ok using Odin, copied over the AOSP beta13 for the 7310, and this time when I installed the ZIP, it said completed ok. Good so far.
I then rebooted, and while I see the Samsung logo, the screen then goes black and stays that way. I've left it ages, but it doesn't seem to get anywhere. I can still reboot it and get into download/recovery, so that's ok. Am I doing anything wrong? I did the wipe/reset beforehand, so It's not obvious why this is not working.
Quick update. I can get ICS running (CM9 works), so that's good. It does look like any JB rom (AOSP/CM10) just cause a blank screen on reboot, which is wierd. I've re-downloaded the ROM's just in case, but no dice. Install completes ok, and gapps reports no problems.
I often don't get a boot animation, just the black screen. Every once in awhile the animation comes back. Seems totally random. I'm using nravates jb Rom on the i957. Other than that it runs great.
Sent from my SGH-I727 using xda app-developers app
The phone: HTC vivid, s-on, stock ICS rom unlocked, rooted, faux kernal
The problem: WiFi doesn't seem to scan. It will turn on, get past the "turning on..." phase, but then just flashes between "Scanning" and "disconnected" and doesn't find any networks.
The first mod to the phone a long time ago was to root on the stock ICS rom. Everything worked fine. Eventually I decided to flash Jellybean, then decided to go back to the stock rom because of the call volume issue. Since I've gone back to stock rom, I've been having this wifi issue.
I saw another thread recommend to flash faux kernal. I did that, and had the "turning wifi on..." sticky issue. Fixed that, and now i'm back to the scanning issue.
I also saw a recommendation to flash boot.img but haven't tried that yet because I'm not sure if there is a special one I have to flash to match the kernal, rom, or...?
If someone can tell me which boot.img to flash, or any other suggestions let me know please! Thank you!
NickFu400 said:
The phone: HTC vivid, s-on, stock ICS rom unlocked, rooted, faux kernal
The problem: WiFi doesn't seem to scan. It will turn on, get past the "turning on..." phase, but then just flashes between "Scanning" and "disconnected" and doesn't find any networks.
The first mod to the phone a long time ago was to root on the stock ICS rom. Everything worked fine. Eventually I decided to flash Jellybean, then decided to go back to the stock rom because of the call volume issue. Since I've gone back to stock rom, I've been having this wifi issue.
I saw another thread recommend to flash faux kernal. I did that, and had the "turning wifi on..." sticky issue. Fixed that, and now i'm back to the scanning issue.
I also saw a recommendation to flash boot.img but haven't tried that yet because I'm not sure if there is a special one I have to flash to match the kernal, rom, or...?
If someone can tell me which boot.img to flash, or any other suggestions let me know please! Thank you!
Click to expand...
Click to collapse
You might think about trying Albinoman's KitKat nightlies. Many people (including myself) are getting very good in call volume, and the rom is really good.
My two cents...
cmerlyn said:
You might think about trying Albinoman's KitKat nightlies. Many people (including myself) are getting very good in call volume, and the rom is really good.
My two cents...
Click to expand...
Click to collapse
Good to know, I'll check it out. Thanks
Is there not a boot.img for the stock ICS? This is the guide I've been using.
Wifi scan problem fix
What you need to do, if your phone is S-Off, is to flash the boot.img in the .rar file of the ROM you flashed
1.place the boot.img in root of your SD card or internal
2. reboot to flashboot
3. plugin usb (should say flashboot usb mode)
4. run adb from adbtools (google this if you don't have it) and type in the following commands to CMD
-NOTE: Run CMD on the same folder as the adb files
Command:
flashboot flash boot boot.img
5. restart phone
6. Voila! Fixed Wifi, and other problems u may have
I'm pretty sure you only need to flash the boot.IMG for of you're s-on. S-off will automatically flash it from the zip file.
Sent from my Vivid 4G using xda app-developers app
projectisaac said:
I'm pretty sure you only need to flash the boot.IMG for of you're s-on. S-off will automatically flash it from the zip file.
Sent from my Vivid 4G using xda app-developers app
Click to expand...
Click to collapse
When troubleshooting... Start taking out variables...
Sent from my Vivid 4G using Tapatalk
I am S-on.
I'm stock ICS rooted, used the RUU directly from HTC..this could be the noob in me, but I don't think I flashed a rom that came with a boot.img?
Again, this is the thread I followed:
http://forum.xda-developers.com/showthread.php?t=1416836
Thanks for the help, I would really like to get this working.
Hi, guys:
I really need some help to make my LG G4 H811 work.
I flashed latest lineage-14.1-20170404-nightly-h811-signed.zip but my camera app "Keeps Stop Working". I tried other camera apps, none of them work.
I also flashed cm-13.0-20161010-NIGHTLY-h811.zip, same problem
I even flashed stock (but rooted) ROM, LG-G4-H811-20R-Stock-Debloated-Rooted, still the same problem.
I am using twrp-3.0.3-0-h811.img (the latest version for H811) and flash my phonh using ROMs from SD card.
Before I flash anything, the camera worked fine out of box.
Should I bring back stock ROM with LGUP/KDZ? However, I really need some 3rd party ROM working because I need multiple-user feature which is disabled in Stock ROM.
Any suggestion is very much appreciated.
eruisi said:
Hi, guys:
I really need some help to make my LG G4 H811 work.
I flashed latest lineage-14.1-20170404-nightly-h811-signed.zip but my camera app "Keeps Stop Working". I tried other camera apps, none of them work.
I also flashed cm-13.0-20161010-NIGHTLY-h811.zip, same problem
I even flashed stock (but rooted) ROM, LG-G4-H811-20R-Stock-Debloated-Rooted, still the same problem.
I am using twrp-3.0.3-0-h811.img (the latest version for H811) and flash my phonh using ROMs from SD card.
Before I flash anything, the camera worked fine out of box.
Should I bring back stock ROM with LGUP/KDZ? However, I really need some 3rd party ROM working because I need multiple-user feature which is disabled in Stock ROM.
Any suggestion is very much appreciated.
Click to expand...
Click to collapse
mmmm maybe its twrp.. not sure wich one i used that whenever i flash a rom it gave me errors non stope of camera.. and other stuff... you should use steadyfastx twrp not official.. its a beta..
twrp-3.1.0-0_BETA-h811_h815-steadfasterX-build1.img
only thing is missing that i know is reboot to recovery from recovery...
link here..
try installing twrp.. then flash rom and see i f you get error..if you do KDZ then install this.. and then flash rom good luck
http://forum.xda-developers.com/devdb/project/?id=16696#downloads
raptorddd said:
mmmm maybe its twrp.. not sure wich one i used that whenever i flash a rom it gave me errors non stope of camera.. and other stuff... you should use steadyfastx twrp not official.. its a beta..
twrp-3.1.0-0_BETA-h811_h815-steadfasterX-build1.img
only thing is missing that i know is reboot to recovery from recovery...
link here..
try installing twrp.. then flash rom and see i f you get error..if you do KDZ then install this.. and then flash rom good luck
http://forum.xda-developers.com/devdb/project/?id=16696#downloads
Click to expand...
Click to collapse
thank you for the kindly reply. The issue has been solved by flash Stock 20p KDZ first in download mode then flash the same LineageOS through TWRP. Not sure which step really fixed the issue though.
I do have issues of video recording for 4K and 1080p, which is OK to me for now.