Database Develop

An annoying issue after upgrading to V4.0.4

After upgrading from V4.0.3 to V4.0.4 (from kies), the main scheen shows the annoying box (only on the 7 main screes, not elsewhere) with some H/W info as screen shot below, I tried to manually download the ROM, perform double wipe and reload the ROM agian, the issue remains, has any one encountered the same problem, any one has any ideas can help me with this ? :crying:
{
"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 didn't experience this to my DXLR5 4.0.4.
Sent from my GT-N7000 using Tapatalk 2

ryn888 said:
I didn't experience this to my DXLR5 4.0.4.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Thanks, I did surf the internet for a while but not able to find any similar problem as I have, that's why I post here to seek some expert support ...

:crying:
I need some help.
These should be someone/expert can sort this out ..
HELP / HELP !!

This is due to broken EFS
If you have EFS backup, restore it.
Otherwise Reflash GB ROM, someone reported it worked by flashing GB ROM with wipe cache and data.

dr.ketan said:
This is due to broken EFS
If you have EFS backup, restore it.
Otherwise Reflash GB ROM, someone reported it worked by flashing GB ROM with wipe cache and data.
Click to expand...
Click to collapse
Thanks, Ketan,
I don't have EFs backup,,,
But when I read some other articles, it says the lost of EFS will have some symptoms , ie: IMEI gone (I can check my IMEI by "*#06#"), no signal (I am OK to make/receive the call)... etc, it seems I may not have EFS issue ??
Also, I did try to downgrade to V4.0.3 when I encountered the issue on V4.0.4, everything is fine
At first I thought there is something wrong with the V4.0.4 ROM (my first upgrade was from Kies directly), so I manually download the ROM (actually I've compared the ROM from Kies and the one I downloaded, they are identical),,,anyway, I used Odin to upgrade again, and the problem comes up again..
that is to say, with V4.0.3, the phone has no any issues, with V4.0.4, the only issue is the annoying H/W info box shown on the 7 main screens....
Any more ideas or detail instruction would be very much appreciated ...

As i said its just broken efs, where still you dont lose imei. But you can try this
Downgrade to lower version where there is no issue, take efs backup.
Then update to newer version and restore backup when issue appear back.
Sent from my GT-N7000 using xda premium

am getting annoyed by another problem. The WiFi switches off automatically and gets connected when i touch the screen..
This is annoying me as all the updates happen while the display is off and it is getting those using 3G and not the WiFi...
Is it just me ?
I did not install any app after the upgrade form 4.0.3 to 4.0.4

Just go to.setting - wifi -advance - keep wifi on during sleep - Change to 'always.'
Then wifi.wont.auto off.
Sent from my GT-N7000 using xda premium

cool.. almost forgot that .. How the Heck did it change to Never.. does the update change the settings ??
One more thing .. now my Apex launcher restarts everytime .. i remember there was a place where we can change the no.of apps running in the background .. Can you tell me where this is ?

You mean
Setting -development -restrict number of background process?
Sent from my GT-N7000 using xda premium

any option like that in Stock ROM which might have been changed by the upgrade ?

As said above?.i have edited
Sent from my GT-N7000 using xda premium

just checked and it is set to default ... no changes there .. humm.. Thanks Again Ketan.. will look for alternate Launchers.. Any suggestions ?
or should i just take the jump and go for Paranoid Android

dr.ketan said:
As i said its just broken efs, where still you dont lose imei. But you can try this
Downgrade to lower version where there is no issue, take efs backup.
Then update to newer version and restore backup when issue appear back.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Hello, Ketan,
I followed your suggestion to downgrade to V4.0.3, of course, it is problem free menaing no annoying box shown on main screen
Then I root to install HC-Ktool and backup efs
and then unroot and upgrade to V4.0.4 again, the annoying box come up ...
Then I root again to run HC-Ktool and restore EFS, and restart
without luck ,,, the annoying box is still there,.,,, any thoughts ?

easternpig said:
Hello, Ketan,
I followed your suggestion to downgrade to V4.0.3, of course, it is problem free menaing no annoying box shown on main screen
Then I root to install HC-Ktool and backup efs
and then unroot and upgrade to V4.0.4 again, the annoying box come up ...
Then I root again to run HC-Ktool and restore EFS, and restart
without luck ,,, the annoying box is still there,.,,, any thoughts ?
Click to expand...
Click to collapse
tell me the procedure you are following in flashing the roms and please try to downgrade to a safe gingerbread rom then root it or use pre-rooted gb rom from DR.KETAN'S GUIDE.

easternpig said:
Hello, Ketan,
I followed your suggestion to downgrade to V4.0.3, of course, it is problem free menaing no annoying box shown on main screen
Then I root to install HC-Ktool and backup efs
and then unroot and upgrade to V4.0.4 again, the annoying box come up ...
Then I root again to run HC-Ktool and restore EFS, and restart
without luck ,,, the annoying box is still there,.,,, any thoughts ?
Click to expand...
Click to collapse
I read some other user's experience on S2 too. But sorry nothing found that works 100%,
It not happens to everyone, so may be it should have relation with previous ROM(even on OTA update it can happen). May be just try to downgrade to GB ROM, root it , wipe cache, data,delvic cache, and use Mobile odin to update 4.0.4. Thouh this is just speculation on basis of clean install. I dont have review that this will work.

shivg86 said:
tell me the procedure you are following in flashing the roms and please try to downgrade to a safe gingerbread rom then root it or use pre-rooted gb rom from DR.KETAN'S GUIDE.
Click to expand...
Click to collapse
I used PC Odlin to flash the PDA only, the ROM was official ROM from http://samsung-updates.com/device/?id=GT-N7000.
note that I upgraded the version through Kies firstly, previously I was on V4.0.3 official rom (rooted) - without this issue
the issue was appeared after the official (kies) 4.0.4 upgrade
I tried to downgrade to V4.0.3 (obtain the ROM from the link said above), the problem gone ...
then I upgrade to V4.0.4 again (as mentioned in my last note, EFS is not a matter here) - problem back again
during several trials, I aslo tried to reset the phone, (try on double wipe as well al reset to syatem default from system setting menu) and redo all those steps, but still unlucky .. None of any actions can help ...
btw : I read other articals saying to refresh kernal and double wipe ,,, no help as well ...
it drives me crazy ...

easternpig said:
I used PC Odlin to flash the PDA only, the ROM was official ROM from http://samsung-updates.com/device/?id=GT-N7000.
note that I upgraded the version through Kies firstly, previously I was on V4.0.3 official rom (rooted) - without this issue
the issue was appeared after the official (kies) 4.0.4 upgrade
I tried to downgrade to V4.0.3 (obtain the ROM from the link said above), the problem gone ...
then I upgrade to V4.0.4 again (as mentioned in my last note, EFS is not a matter here) - problem back again
during several trials, I aslo tried to reset the phone, (try on double wipe as well al reset to syatem default from system setting menu) and redo all those steps, but still unlucky .. None of any actions can help ...
btw : I read other articals saying to refresh kernal and double wipe ,,, no help as well ...
it drives me crazy ...
Click to expand...
Click to collapse
dr.ketan said:
I read some other user's experience on S2 too. But sorry nothing found that works 100%,
It not happens to everyone, so may be it should have relation with previous ROM(even on OTA update it can happen). May be just try to downgrade to GB ROM, root it , wipe cache, data,delvic cache, and use Mobile odin to update 4.0.4. Thouh this is just speculation on basis of clean install. I dont have review that this will work.
Click to expand...
Click to collapse
Tried on this ROM SGN_XX_OXA_KJ1_FACTORYFS, no issue, then follow the instruction ,,, root it , wipe cache, data,delvic cache, and use Mobile odin to update 4.0.4,, that annoying box still happens ... My Goooooood ....

I had talk with samsung service centre guy(who is really noob, and owner sending his device to me to root ), he said he had email regarding this. I am planning to go to SSC to read mail what exactly he got information, really here in my town very small service centre. he couldn't even find out what set of instruction exactly there on mail
Lets see if anything special. This is likely ROM bug, b'coz some one who have updated from OTA, also get this.

[Q] [HELP !] Bricked my GT-P1000 ?

Hello right here,
Got an big issue on my GT-P1000 :crying:, hope i'll find help and answers around :angel:.
First of all, i'm french, so please apologize my english if it's not as good as i'd like to (and feel free to correct me if necessary, it'll help !)
So, i bought a few years ago a GT-P1000.
Trying to change the rom, the official one was too slow .
First of all, rooting, yet some problems : all the processes i followed told me it was OK, and when i ran Root Checker, it told me the opposite (not root access). After a few tries, i thought Root Checker was the probleme, so news step : CWM installation.
Nickel, all good.
Last step : download and install Cyanogen Mod 10.2 (Android 4.3) following this tuto : computechips (can post a link )
And the result is : the tab won't boot any more. I restored it, and same thing, stays sticked on the "samsung" welcome screen, no more movements.
I still can go to the Recovery Mode, but there are messages telling that no drive can be mounted :
Code:
E: unknown volume for path [/system]
E: Unable process volume ! skipping ..
Checking /data..
E: unknown volume for path [/data]
E: unknown volume for path [/data]
E: Unable process volume ! skipping ..
Checking /cache..
E: unknown volume for path [/cache]
E: unknown volume for path [/cache]
E: Unable process volume ! skipping ..
Done !
And so on ..
Any idea on this issue ?
Thx !
Oliv.

Download the Overcome Recovery http://forum.xda-developers.com/showthread.php?t=1881981
Install the SAMSUNG_USB_Driver_for_Mobile_Phones_x86.exe
The Odin3 v1.7 is the Windows Software Flasher for all Samsung Devices.
There will be a number of different Folders each with a different "modem.bin" File in them. Unless you have a very specific version of the P1000 that requires such a unique modem.bin File (i.e. You have a CDMA Phablet). You should just use the standard JPZ (GSM) modem.bin version.
So after you have installed the USB Driver(s)
On your Phablet press the Volume Button DOWN + the Power Button till you see this Screen
{
"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"
}
Then start Odin3 v1.7 and connect your Phablet to your Computer
Pit -> gt-p1000_mr.pit
PDA -> GB_Stock_Safe_v5.tar
Phone -> modem.bin**
This should drop you back to v2.3.3. Gingerbread again.
Word of advice stick to only CM10 Builds! ALL CM10.1, AND CM10.2 BUILDS CONTAIN MASSIVE BUGS IN THEM, that kill off either the (Front) Camera, or the Bluetooth Radio Stack, or in most cases BOTH! Pretty much all of the CM10 Mods I've tried DO NOT have these problems and both the (Front) Camera, and Bluetooth are working.
**VERY IMPORTANT DO NOT FORGET TO ADD THIS FILE OR YOU WILL TRULLY SOFT-BRICK YOUR PHABLET!
If you do this I'm not sure if you can get back to the Download mode anymore or not. I think that I was able to on occasion though. in this case though just assume that you'll need the Heimdall One-Click Unbrick though.
http://forum.xda-developers.com/showthread.php?p=15330252

Ichijoe said:
Download the Overcome Recovery http://forum.xda-developers.com/showthread.php?t=1881981
Install the SAMSUNG_USB_Driver_for_Mobile_Phones_x86.exe
The Odin3 v1.7 is the Windows Software Flasher for all Samsung Devices.
There will be a number of different Folders each with a different "modem.bin" File in them. Unless you have a very specific version of the P1000 that requires such a unique modem.bin File (i.e. You have a CDMA Phablet). You should just use the standard JPZ (GSM) modem.bin version.
So after you have installed the USB Driver(s)
On your Phablet press the Volume Button DOWN + the Power Button till you see this Screen
Then start Odin3 v1.7 and connect your Phablet to your Computer
Pit -> gt-p1000_mr.pit
PDA -> GB_Stock_Safe_v5.tar
Phone -> modem.bin**
This should drop you back to v2.3.3. Gingerbread again.
Word of advice stick to only CM10 Builds! ALL CM10.1, AND CM10.2 BUILDS CONTAIN MASSIVE BUGS IN THEM, that kill off either the (Front) Camera, or the Bluetooth Radio Stack, or in most cases BOTH! Pretty much all of the CM10 Mods I've tried DO NOT have these problems and both the (Front) Camera, and Bluetooth are working.
**VERY IMPORTANT DO NOT FORGET TO ADD THIS FILE OR YOU WILL TRULLY SOFT-BRICK YOUR PHABLET!
If you do this I'm not sure if you can get back to the Download mode anymore or not. I think that I was able to on occasion though. in this case though just assume that you'll need the Heimdall One-Click Unbrick though.
http://forum.xda-developers.com/showthread.php?p=15330252
Click to expand...
Click to collapse
Thx Ichijoe, very much !
I try this right now (as soon as all files are dl). Simple question : Odin3 v1.7 ou v 1.85 (the one on the post you gave me), same thing ?

Olif5978 said:
Thx Ichijoe, very much !
I try this right now (as soon as all files are dl). Simple question : Odin3 v1.7 ou v 1.85 (the one on the post you gave me), same thing ?
Click to expand...
Click to collapse
It shouldn't matter, I think latter versions of Odin3 have more options in them that may confuse newer users, (i.e. Bootloaders) besides its not like you have to use the latest version to do this.
Needless to say you do NOT want to go f***ing round with the Bootloaders unless you have a way to recover. You can do almost anything you like to your Phablet. just DO NOT play with the Bootloader otherwise your "Soft-Brick" will instantly turn into a "Hard-Brick", and then you can go and find a JTAG Programer on Fleabay!
So your better off just sticking to Odin3 v1.7 for now.

Thx !
Ichijoe said:
It shouldn't matter, I think latter versions of Odin3 have more options in them that may confuse newer users, (i.e. Bootloaders) besides its not like you have to use the latest version to do this.
Needless to say you do NOT want to go f***ing round with the Bootloaders unless you have a way to recover. You can do almost anything you like to your Phablet. just DO NOT play with the Bootloader otherwise your "Soft-Brick" will instantly turn into a "Hard-Brick", and then you can go and find a JTAG Programer on Fleabay!
So your better off just sticking to Odin3 v1.7 for now.
Click to expand...
Click to collapse
Hello here !
I just wanted to thank you, ichijoe, as i managed to restore my tab following your advice :good:.
I tried once more to pass the 10.2 cyanogen mod rom, unsuccessful, exactly the same issues.
I'll try to pass the 10.1 one of these days ...
Anyway, thanks a lot for your help, i wa sreally afraid to lose my tab ...
Olif

Olif5978 said:
Hello here !
I just wanted to thank you, ichijoe, as i managed to restore my tab following your advice :good:.
I tried once more to pass the 10.2 cyanogen mod rom, unsuccessful, exactly the same issues.
I'll try to pass the 10.1 one of these days ...
Anyway, thanks a lot for your help, i wa sreally afraid to lose my tab ...
Olif
Click to expand...
Click to collapse
My advice is to just stick to the lastest CM10 Release 20130203
for now as this ROM if not, working @ 100%! then most certainly @ 99.9% as far as both the Camera and Bluetooth are concerned!
At this point we're better off waiting for KitKat ROMs then updated Jelly Baean Ones. AFAIK (And, TBH I'm just as new to this "Game"!), these Problems have been around as long as CM10.1, and CM10.2. i.e. for almost a whole Year now!
So I for One am not, holding my breath that this will be fixed soon-ish, at least not for CM's 10 .1 & .2...

CM11 KitKat
Ichijoe said:
My advice is to just stick to the lastest CM10 Release 20130203
Click to expand...
Click to collapse
I had a very hard time trying to flash something newer on my TAB, but finally I managed to have CM11 up and running. The latest nightlies now seem quite stable. I have created user profiles for my kids so as they cannot simply download any app and the device, uncluttered by games, is pretty fast now. It feels like a new tablet!

ha5x said:
I had a very hard time trying to flash something newer on my TAB, but finally I managed to have CM11 up and running. The latest nightlies now seem quite stable. I have created user profiles for my kids so as they cannot simply download any app and the device, uncluttered by games, is pretty fast now. It feels like a new tablet!
Click to expand...
Click to collapse
Hello ha5x,
What a good news !
I'm very interested in this solution. Would you mind making me a little how-to, with the good links to DL all it needs ?
Every time i try, there's a corrupted file, or a missing (404) file on the list ...
Regards,
Olivier.

Cannot remember how I did it
Olif5978 said:
Hello ha5x,
What a good news !
I'm very interested in this solution. Would you mind making me a little how-to, with the good links to DL all it needs ?
Every time i try, there's a corrupted file, or a missing (404) file on the list ...
Regards,
Olivier.
Click to expand...
Click to collapse
Hi Olivier,
I do not volunteer to write a how-to. In fact, I cannot remember how I did it. I myself had LOTS of such difficulties, errors, missing files, there were even several hours while I thought I had bricked the device which was responding to anything... It took me nearly three days flashing, cursing and flashing, cursing and flashing and cursing.
But what I have found is that you need to go step by step, flashing one ROM after another until you find one which comes with a recovery compatible with CM... I vaguely remember that a key step was flashing the "Overcome ROM", which then let me great step further.
Sorry.

You have to flash CM 7, then CM9, and finally CM 10 or 11. Your choice. Just make sure you have the right recovery installed and CWM version. I would skip the gapps til the last version you flash. Follow the directions for each CM version on xda.
Sent from my SCH-I800 using xda app-developers app

This is how i flash CM11..
Go to download mode
1) Restock using Overcome method..(via Odin) http://forum.xda-developers.com/showthread.php?t=1881981
-just the stock safe with my support modem..which is JPZ modem..no need to flash the Overcome Rom
-let it boot
Go to download mode again
2) Flash the Overcome Kernel..for root access and custom recovery..(via Odin)
-let it boot
(Step 1 and 2 is not necessary if you already using custom rom..but i like to do a clean flash..and if you still using the official firmware..step 1 and 2 is necessary..)
Go to Recovery
Do a clean wipe..(data,partition,dalvik,cache ect)
3) Flash CM10.2 for Kernel 3.0.x...(via custom recovery) Any CM10.2 With Kernel 3.0.X
-3x flash (first for CMW recovery..second for partition layout..third for CM10.2 Rom)
-let it boot
Go to Recovery
Do a clean wipe..(data,partition,dalvik,cache ect)
4) Flash the CM11..
5) Flash gapps..
6) Reboot
done..my p1 is running CM11..
and i did it without any problem..no crash or anything..
and i'm using storm31 CM1120131203..
with a few bug like front camera ect.(newer build already fix some of the bug)
or you can always go to the CM11 thread and read the OP for their instruction..
but always remember..
CREATE BACKUP
READ THE OP..and maybe a few comment first before you try to flash any rom..
just to make sure what are you going to experience..
i even read the whole thread before i start to flash any rom..
with that being said..
DO AT YOUR OWN RISK.. and Good Luck..:good:

[Q] Working Copy of CWM ?

I've gone through a few different files of CWM and none of them seem to work / boot into it. Version 2.3, version 3.0. Both are utter disaster. Only can get twrp to work but then it won't install a working copy of EMUI 3.0.
From what I read only CWM can install 3.0...
I could use a little help here, 5 hours bashing my head against this and still no luck.
My phone is on a continuous reboot as of now :crying:
downloading few files to see if i can go back to 2.3 but at my connection, it will be a few hours, i've all the files for 3.0 so I would really like to see if i can get CWM to work before I go back to 2.3.
Any help would be appreciated, thank you.

Hi, cwm only works together with emui 3.0. So you have to be at least at B602 to install cwm. That means you have to update manually from 2.3 to 3.0(if you are on 2.3 install the 2.3 stock recovery and update with the three-button-methode to B609 or another emui 3.0 firmware). Now you should be able to run cwm correctly...

l3Nni said:
Hi, cwm only works together with emui 3.0. So you have to be at least at B602 to install cwm. That means you have to update manually from 2.3 to 3.0(if you are on 2.3 install the 2.3 stock recovery and update with the three-button-methode to B609 or another emui 3.0 firmware). Now you should be able to run cwm correctly...
Click to expand...
Click to collapse
I wish this info was more easily accessible, the lack of a solid collection of info on dealing with Huawei phones is unbelievable. I had to learn through trial and error and finally got to have a working phone. I'm just lucky I've managed to get proper stock working on it for now. I do not feel adventurous with my phone for now
Thank you for the advice

Need your help with rollback L09 to stock EMUI

Hey,
I need your help with going back from RROS to stock EMUI.
Im trying this since a couple of hours now but I dont get it.
So I started flashing RROS with the new TRWP everything worked fine but the battery drain was to big so I decided to restore to the nandroid backup I did before flashing the custom rom.
But there was the point I did anything wrong so... My device just bootloop now and I dont know what to do.
I tried the dload option to rollback to stock for so many times and in the end I got a bootloop again so can anybody help me with this sh*ty smartphone?
Id be so glad if anyone could please help me, Im so desperate :/

Why you didn't ask first for instructions in the RROS thread - supposidely the RROS authors and users should know how to go back (they are subscribed to and they read their thread)
I'm not sure if DLOAD method works from RROS.
If you still have TWRP, you can try
https://forum.xda-developers.com/showpost.php?p=74913874&postcount=3
or
https://forum.xda-developers.com/showpost.php?p=74169408&postcount=7

zgfg said:
Why you didn't ask first for instructions in the RROS thread - supposidely the RROS authors and users should know how to go back (they are subscribed to and they read their thread)
I'm not sure if DLOAD method works from RROS.
If you still have TWRP, you can try
https://forum.xda-developers.com/showpost.php?p=74913874&postcount=3
or
https://forum.xda-developers.com/showpost.php?p=74169408&postcount=7
Click to expand...
Click to collapse
Thanks a lot Im goona try the first one but Im not sure its really working because I used a nandroid backup of another user from version B384 and flashed OEM info packages.
I dont rollback from full RROS so I dont really know in wich thread I should write.

Bluesyle said:
Thanks a lot Im goona try the first one but Im not sure its really working because I used a nandroid backup of another user from version B384 and flashed OEM info packages.
I dont rollback from full RROS so I dont really know in wich thread I should write.
Click to expand...
Click to collapse
First method, HWOTA, does not recover OEM Info - you should have never flashed Nandroid backups from another users.
I would suggest to go anyhow back to stock Android N, then to do rollback to MM and back, by OTAs to Android N (stock ROMs)
Btw, what was your orginal stock ROM, EVA-L09 c432 b384 or what (L19, etc)?

zgfg said:
First method, HWOTA, does not recover OEM Info - you should have never flashed Nandroid backups from another users.
I would suggest to go anyhow back to stock Android N, then to do rollback to MM and back, by OTAs to Android N (stock ROMs)
Btw, what was your orginal stock ROM, EVA-L09 c432 b384 or what (L19, etc)?
Click to expand...
Click to collapse
I got a L09, I dont know my stock and the ROM I moved over to RROS too.
However, Im going back to RROS with the nandroid backup I did before all this **** and then Im trying HWOTA.
Rollback doesnt work, I tried it with the stock and nocheck recovery, two times package errors.
Edit: restoring nandroid backup of RROS failed, with extractTarFork() error 255.
Im starting now with the HWOTA method after flashing the rom again without backup.

Bluesyle said:
I got a L09, I dont know my stock and the ROM I moved over to RROS too.
However, Im going back to RROS with the nandroid backup I did before all this **** and then Im trying HWOTA.
Rollback doesnt work, I tried it with the stock and nocheck recovery, two times package errors.
Click to expand...
Click to collapse
HWOTA method requires that you use ZIP corresponding to your original stock ROM you had.
This is because HWOTA actually uses no-check Recovery to force DLOAD to the chosen stock ROM, but DLOAD does not recover/reflash all partititions, they must be original/in sync. If not, DLOAD (as part of HWOTA) will probably fail.
You should at least know what was your original cust for L09, was it c432, c185 or c636 - to choose the corresponding HWOTA ZIP.

zgfg said:
HWOTA method requires that you use ZIP corresponding to your original stock ROM you had.
This is because HWOTA actually uses no-check Recovery to force DLOAD to the chosen stock ROM, but DLOAD does not recover/reflash all partititions, they must be original/in sync. If not, DLOAD (as part of HWOTA) will probably fail.
You should at least know what was your original cust for L09, was it c432, c185 or c636 - to choose the corresponding HWOTA ZIP.
Click to expand...
Click to collapse
First of all thank you!
So... like I understood your post there ist no way for me any more to use DLOAD or HWOTA because I dont have any part of my stock ROM on my phone. Well, that doesnt sounds so good.
But what can I do then? How can I go to stock when I dont can use DLOAD or stuff like this??

Try with HWOTA and then try with rollback, maybe it will work
And/or try the second method from above (that one I never used).
Actually, that second method also utilzes rollback, to clean/restore all partitions.
Hence, it is important that you reach a point (having, even not fully functional, stock Android N) to execute rollback

connection problem

i had a bootloop problem in my xt1254, fixed it with Computerfreek's ROM, flashed modems and everything but now i've got no connections and cannot setup my phone, no wi-fi or mobile data
mac address is marked as 02:00:00:00
even flashing stock 6.0.1 with RSD Lite doesn't work
help plz

joshua7727 said:
i had a bootloop problem in my xt1254, fixed it with Computerfreek's ROM, flashed modems and everything but now i've got no connections and cannot setup my phone, no wi-fi or mobile data
mac address is marked as 02:00:00:00
even flashing stock 6.0.1 with RSD Lite doesn't work
help plz
Click to expand...
Click to collapse
Which modems did you flash?
Sent via open market LG US998 V30/V30+

ChazzMatt said:
Which modems did you flash?
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
the ones Computerfreek posted in the rom thread (''MCG24.251-5+Radios+BL'')

joshua7727 said:
the ones Computerfreek posted in the rom thread (''MCG24.251-5+Radios+BL'')
Click to expand...
Click to collapse
just realized my mistake, i was flashing de wrong ones
now i flashed ''MCG24.251-5-5+Radios+BL-New'', then flashed Computerfreek 1.0.8 but still got no wifi or mobile data :/

Did you get this fixed?

no :'(

joshua7727 said:
just realized my mistake, i was flashing de wrong ones
now i flashed ''MCG24.251-5-5+Radios+BL-New'', then flashed Computerfreek 1.0.8 but still got no wifi or mobile data :/
Click to expand...
Click to collapse
One, you're sure you have a Droid Turbo and not another Quark like Moto Turbo/Moto Maxx XT1225? Sorry, I have to ask. Because while you can install this ROM on an XT1225 you won't get any mobile signal or Wi-Fi. Which is exactly your symptoms...
If you do have Droid Turbo XT1254, boot into TWRP and flash this Clean Modem file.
Clean_modem_status.zip
https://androidfilehost.com/?fid=24531035584725320
Then, flash THIS modem. It's ONLY the TWRP-flashable MCG24.251-5-5 modem -- not + bootloader like you flashed before. I want you to flash this AFTER you flash the clean modem file.
TheSt33v said:
[ROM] MCG24.251-5-5 100% Stock
By popular demand, here are just the modems: https://mega.nz/#!m9xnwDjD!jvvLXbGpCN9QVzRY1hph6JOyZv8kiBcLs2bsCdIgv8w
Click to expand...
Click to collapse
If that doesn't solve your problems, just as an experiment, flash this Quark custom kernel. It will work with all stock firmware, including this stock-based Computerfreek ROM. Kernel especially controls Wi-Fi, besides modem.
BHB27 custom kernel for Quark
https://androidfilehost.com/?w=files&flid=135512
Check your APN also. I don't know which carrier you have, it's possible the wrong APN settings are preventing connection. That shouldn't affect your Wi-Fi, but I'm looking for solutions.

ChazzMatt said:
One, you're sure you have a Droid Turbo and not another Quark like Moto Turbo/Moto Maxx XT1225? Sorry, I have to ask. Because while you can install this ROM on an XT1225 you won't get any mobile signal or Wi-Fi. Which is exactly your symptoms...
If you do have Droid Turbo XT1254, boot into TWRP and flash this Clean Modem file.
Clean_modem_status.zip
https://androidfilehost.com/?fid=24531035584725320
Then, flash THIS modem. It's ONLY the TWRP-flashable MCG24.251-5-5 modem -- not + bootloader like you flashed before. I want you to flash this AFTER you flash the clean modem file.
If that doesn't solve your problems, just as an experiment, flash this Quark custom kernel. It will work with all stock firmware, including this stock-based Computerfreek ROM. Kernel especially controls Wi-Fi, besides modem.
BHB27 custom kernel for Quark
https://androidfilehost.com/?w=files&flid=135512
Check your APN also. I don't know which carrier you have, it's possible the wrong APN settings are preventing connection. That shouldn't affect your Wi-Fi, but I'm looking for solutions.
Click to expand...
Click to collapse
Well, yes i do have a XT1254.
I wiped the phone for clean installing, flashed both files in order, then flashed Computerfreek 1.0.8
Still got no Wi-Fi, so i tried flashing BHB27's kernel, same result...
Now i remember a similar issue but in a brazilian rom, it boots but you have to flash your own modems, and i think this ones should work
ill keep u updated
(thx btw)

joshua7727 said:
Well, yes i do have a XT1254.
I wiped the phone for clean installing, flashed both files in order, then flashed Computerfreek 1.0.8
Still got no Wi-Fi, so i tried flashing BHB27's kernel, same result...
Now i remember a similar issue but in a brazilian rom, it boots but you have to flash your own modems, and i think this ones should work
ill keep u updated
(thx btw)
Click to expand...
Click to collapse
Tried that, didn't work either
The proccess i'm following is:
- Flash both modem files
- Flash ROM
- Flash Kernel
I dont know if i'm doing somthing wrong or what but plz, i need help

Did you have another ROM other than the stock cf274 before you started flashing? Are you on Verizon?

Well i had RR, then Stock, then Computerfreek
In RR and Stock it worked pretty well
And nope, i ain't in Verizon

joshua7727 said:
Well i had RR, then Stock, then Computerfreek
In RR and Stock it worked pretty well
And nope, i ain't in Verizon
Click to expand...
Click to collapse
OK I think this will work, you will need to clean everything including internal memory, then through twrp file mgr and your PC copy the latest bootloader and radio and cf274 ROM to internal. Be sure to use the ones for the country you are in. Sometimes there are files left over from RR that interfere with going to Cf274 ROM. I had that problem back sometime and by wiping everything a few times and following his instructions for your area it should work. Good luck
Been thinking, what version of twrp are you using? Latest bhb27 one?

newbe1droidx said:
OK I think this will work, you will need to clean everything including internal memory, then through twrp file mgr and your PC copy the latest bootloader and radio and cf274 ROM to internal. Be sure to use the ones for the country you are in. Sometimes there are files left over from RR that interfere with going to Cf274 ROM. I had that problem back sometime and by wiping everything a few times and following his instructions for your area it should work. Good luck
Been thinking, what version of twrp are you using? Latest bhb27 one?
Click to expand...
Click to collapse
i use twrp 3.1.1-mod_2
i've done this a lot of times
but i was playing around with TWRP's terminal and found this out
{
"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 don't know if its useful but seems interesting

Good correct twrp, regretfully I don't write code yet so it doesn't help me, hopefully someone who does can chime in on that.

joshua7727 said:
Well, yes i do have a XT1254.
I wiped the phone for clean installing, flashed both files in order, then flashed Computerfreek 1.0.8
Still got no Wi-Fi, so i tried flashing BHB27's kernel, same result...
Now i remember a similar issue but in a brazilian rom, it boots but you have to flash your own modems, and i think this ones should work
ill keep u updated
(thx btw)
Click to expand...
Click to collapse
Yes, on that Brazilian ROM posted over here you have to flash your own modem, like the one I linked to. BUT on that ROM you can only use the kernel listed in that thread. It's an older BHB27 kernel but it's compatible with that ROM. You cannot update the kernel without issues.
newbe1droidx said:
OK I think this will work, you will need to clean everything including internal memory, then through twrp file mgr and your PC copy the latest bootloader and radio and cf274 ROM to internal. Be sure to use the ones for the country you are in. Sometimes there are files left over from RR that interfere with going to Cf274 ROM. I had that problem back sometime and by wiping everything a few times and following his instructions for your area it should work. Good luck
Been thinking, what version of twrp are you using? Latest bhb27 one?
Click to expand...
Click to collapse
Yeah, wiping everything in TWRP never hurts, for a really clean install. Just make sure you have all your materials (stored on PC) handy to drag over from PC to TWRP to install again. You don't want to be searching for stuff with a dead phone on your hands that you can't reboot. Test your PC-to-TWRP connection before wiping.
One more suggestion. Flash back to stock completely, see if it works. Then try to flash to the ComputerFreak ROM?

ChazzMatt said:
Yes, on that Brazilian ROM posted over here you have to flash your own modem, like the one I linked to. BUT on that ROM you can only use the kernel listed in that thread. It's an older BHB27 kernel but it's compatible with that ROM. You cannot update the kernel without issues.
Yeah, wiping everything in TWRP never hurts, for a really clean install. Just make sure you have all your materials (stored on PC) handy to drag over from PC to TWRP to install again. You don't want to be searching for stuff with a dead phone on your hands that you can't reboot. Test your PC-to-TWRP connection before wiping.
One more suggestion. Flash back to stock completely, see if it works. Then try to flash to the ComputerFreak ROM?
Click to expand...
Click to collapse
i have done that many times, none of them successful

joshua7727 said:
i have done that many times, none of them successful
Click to expand...
Click to collapse
Maybe you have a hardware issue . I don't know.

ChazzMatt said:
One, you're sure you have a Droid Turbo and not another Quark like Moto Turbo/Moto Maxx XT1225? Sorry, I have to ask. Because while you can install this ROM on an XT1225 you won't get any mobile signal or Wi-Fi. Which is exactly your symptoms...
If you do have Droid Turbo XT1254, boot into TWRP and flash this Clean Modem file.
Clean_modem_status.zip
https://androidfilehost.com/?fid=24531035584725320
Then, flash THIS modem. It's ONLY the TWRP-flashable MCG24.251-5-5 modem -- not + bootloader like you flashed before. I want you to flash this AFTER you flash the clean modem file.
If that doesn't solve your problems, just as an experiment, flash this Quark custom kernel. It will work with all stock firmware, including this stock-based Computerfreek ROM. Kernel especially controls Wi-Fi, besides modem.
BHB27 custom kernel for Quark
https://androidfilehost.com/?w=files&flid=135512
Check your APN also. I don't know which carrier you have, it's possible the wrong APN settings are preventing connection. That shouldn't affect your Wi-Fi, but I'm looking for solutions.
Click to expand...
Click to collapse
Good day friend, I have that same problem, just that I have the bootloader blocked, is it solvable ?, I've already tried flashing with different radio fastboot, but it does not work. XT1254 , Not have BASEBAND.
---------- Post added at 03:02 PM ---------- Previous post was at 02:13 PM ----------
joshua7727 said:
Tried that, didn't work either
The proccess i'm following is:
- Flash both modem files
- Flash ROM
- Flash Kernel
I dont know if i'm doing somthing wrong or what but plz, i need help
Click to expand...
Click to collapse
Did you solve it?